MOMdeck Connection Issues [Sequoia]
Heya!
Same issue that I've seen others had but wanted to start a new thread instead of just reviving an old one.
Updated to Sequoia in the studio, 15.3.1, updated DADman to 5.8.0.8, soundflow 5.10.3.
Double checked sound flow permissions, Accessibility granted, Full Disk, Local Network.
DADman the same, Accessibility, Full Disk, Local Network.
I tried out the solution from Soundflow app opens, but there is nothing on the screen. I can't see any apps, etc. #post-15 but that didn't seem to solve anything for us.
DADman seems ok with finding other devices on the network (MTRX, DADmom). Stream Decks seem to find decks ok. Things just lock up when DADman try to find the MOMdeck.
- OOlivier Nijs @Olivier_Nijs
Same problem here. For some reason the Momdeck is not found on the network more than often. Restarting DadMan sometimes works, sometimes not. Rebooting system works, sometimes not. Why does it seem so unstable?
In reply toCameron_Frankley⬆:Ron Aston @Ron_AstonI just wanted to add that I've been dealing with this exact same issue for more than a week now. I just assumed that it was something with my PT system, suddenly and couldn't figure out what might've changed. Then I found this thread.
I can sometimes get it to work by trying different things but so far that hasn't been a a consistent way of making it work again. Up until now it's been fantastic as well as reliable. I'm running Sequoia 15.4.1 and all of my software is up to date as well as the firmware in my StreamDeck Plus. HELP!
In reply toCameron_Frankley⬆:Andrew Scheps @Andrew_SchepsHi all,
Sorry I missed this thread the first time around. I know a bunch of people who aren't having the issue, so we're looking at something specific. One thing is it hasn't been tested in OS 15.4.1, so while that may not be the issue I can't confirm that it would work.
Can you all tell me whether you are running MOMDeck on the same machine as Dadman, and any other network type stuff that may help point me in the right direction? It's working fine here so it's hard to troubleshoot...
- In reply toCameron_Frankley⬆:Ron Aston @Ron_Aston
Hi Andrew - In my case, I have a 2 computer setup. My M1 Mac Studio Ultra is my main computer and my M2 MacMini Pro runs DaDman and MoMdeck. Both computers are running MacOS 15.4.1. I have no firewalls or other network protection enabled currently. I don’t know what changed here but this all started for me a little more than a week ago.
Andrew Scheps @Andrew_SchepsCan you try running MOMDeck on the same computer as Dadman?
- In reply toRon_Aston⬆:Andrew Scheps @Andrew_Scheps
When did you upgrade to 15.4.1?
- In reply toCameron_Frankley⬆:Ron Aston @Ron_Aston
Ahh yes. I forgot to mention that the MoMdeck IS running from the same computer as DaDman same as it was from day 1 and had worked great ever since. I updated to 15.4.1 approximately 2 weeks ago and everything seemed fine after that update. I think things might’ve started going south after updating the MoMdeck software from the SF store download, but I can’t say for sure.
- Andrew Scheps @Andrew_Scheps
When you start Dadman and MOMDeck, what does the Dadman device list look like?
- In reply toCameron_Frankley⬆:Ron Aston @Ron_Aston
When I startup the DADman Mac mini Pro, the MoMdeck is showing the default 'factory' button assignments....Spk1, Spk2, etc. When I launch DaDman (like I just did), it can't seem to find my devices, like Cameron posted above.
When I hit Cancel and open the Device list, all that appears there is just the MTRX Studio.
I've also noticed that there's evidently a fan issue but the unit has been functioning fine.
I've tried various methods to eventually get the MoMdeck to appear in the Device list including quitting DaDman and Soundflow and the relaunching SoundFlow, then Dadman and sometimes the MoMdeck will suddenly appear in the Device list after DaDman successfully loads without getting stuck, but it only works every so often. I'm also running DaDman 5.8.0.8.
- In reply toCameron_Frankley⬆:Ron Aston @Ron_Aston
Also....Here's a screenshot of my MoMdeck Monitor Profile for layer 1. I'm using 3 of the 4 layers.
- OIn reply toCameron_Frankley⬆:Olivier Nijs @Olivier_Nijs
I'm running 15.4.1. Dadman and Momdeck on the same machine. Different Vlans for Eucon, Dante, etc. Total of 4 Vlans on my main machine. I have DAdman starting automatically when logging in. I noticed that that seems to interfere with Soundflow booting properly. Sometimes Momdeck is found when I restart Dadman.
- Andrew Scheps @Andrew_Scheps
I'm on 15.3.2 here, so it could be 15.4 and beyond. I've got 3 vlans + wifi and it's really solid here. I'll see if I can find anybody running something later than 15.3.1 to try it out.
- In reply toCameron_Frankley⬆:Ron Aston @Ron_Aston
I wish it was working in any way here. I just updated a 2nd volume of my Mac mini Pro (DADman computer) the was formerly a Ventura Startup volume and brought it up to 15.3 as well as updated all of the software that's involved with Dante, DaDman, DVS and I also decided to install SoundFlow 5.10.4 on both computers, being that 5.10.5 didn't help me. Marco suggested doing that because he was having the same problem as I'm having. The one thing that I had him try was restarting his computer and trying to get a MoMdeck connection in DaDman. It had broken again for him just like it's been doing to me during the few times that I was able to get MoM to be seen by DaD.
I personally think that there are overall connection issues with the most recent sound flow releases because I need to also quit SoundFlow on my main PT computer and restart it again before SF appears on my 2 iPad decks. I think it's an Apple problem that's causing it. WiFi is not enabled on either computer. Unfortunately MoMdeck is the thing that's killing me at the moment where all of the other SF functionality is working fine once I restart it after booting up my Main Mac Studio Ultra. VERY frustrated!
- Andrew Scheps @Andrew_Scheps
Hi @Ron_Aston , I'm a little confused when you talk about one computer and then say "both" computers. I'm updating a machine to 15.5 so I can test now, but with 15.3.1 here's what I see.
For everybody on this thread:
Launch Dadman, doesn't matter if you load a profile or anything else, just launch it. Open the Device List (shift-command L). Then launch MOMDeck on the same machine. It shouldn't matter, but for troubleshooting launch the 3x5 deck that comes from the package. To completely mirror what I'm doing launch it on the screen, not on a stream deck.As soon as I launch it it shows up in the device list. And I mean immediately. When I toggle the checkbox on the device the deck status changes from "Searching for DADman" to "No Profile Attached". This is assuming you're not loading a profile that uses it. If you are, checking the box would load the profile.
This is with SoundFlow 10.5.5 and Dadman 5.7.0.1 and Mac OS 15.3.1. I don't think these software versions matter a whole lot, but that's what I'm testing with at the moment.This would be the most basic connection test, and if that isn't working then at least we've severely narrowed down the variables and we can look at mac networking settings. If it does work then we can start adding variables.
I'll let you know about OS 15.5 later today.
Thanks!
Andrew
- In reply toCameron_Frankley⬆:Andrew Scheps @Andrew_Scheps
Ok, I've updated to 15.5 and it's still working fine on SF 5.10.5.
Please make sure SoundFlow has permissions to access the network (try switching on and off.
If that doesn't fix it then it must be something else interfering. I would go through your login items and see if you can disable some stuff. I have tons of things running including Little Snitch and no issues here.
- In reply toCameron_Frankley⬆:Ron Aston @Ron_Aston
Thanks a lot for this additional info, Andrew. It's great to know that MoMdeck is working on 15.5. Thanks for confirming that info. Now I can eliminate that possibility. I've now gone back to my 15.5 startup volume on my Mac mini Pro (DaDman computer) and I checked the Local Network settings and everything there is on and has been on. Then I discovered that SoundFlow wasn't listed in the 'Full Disc Access' list so I added it and suddenly my MoMdeck settings loaded again when I launched DaDman the next time. I've save those DaDman settings and the Profile.
NOW the only thing that I can't do is restart or shutdown and restart that computer again and have my MoMdeck settings load again when I launch DaDman. I can make it work if I go back into the 'Full Disk Access' window and disable SoundFlow and then re-enable it again and the launch DaDman again. Then the MoMdeck will appear again in the Device list and show up on my Streamdeck Plus. Can you do me a favor and shut down your DaDman computer and boot it again to see if your MoMdeck is available when you launch DaDman. When Marco tried this the other night he couldn't get MoMdeck to show up in DadMan, just like what's happening here. I'd be interested to know if it works for you. Once again, you're more than welcome to log into my DaDman MacMini if you'd like to take a look. I don't know what else I can try. I shut my computers down most nights and I've never had these issues with MoMdeck functionality until recently. Thanks again for all or your help!
- In reply toCameron_Frankley⬆:Andrew Scheps @Andrew_Scheps
Ok, I think I have finally got a repro case. I need to make sure the steps are 100% repro and then I'll file it. It's some sort of SoundFlow bug I think, so I doubt there's anything I can do on my end. I'll keep you posted!
Ron Aston @Ron_AstonAwesome!!!!! Thank you Andrew.
- In reply toCameron_Frankley⬆:Andrew Scheps @Andrew_Scheps
Can you guys all try rolling back to SF 5.10.4 and seeing if that keeps things working for you? It definitely does here.
- CCameron Frankley @Cameron_Frankley
Hey Andrew!
Im a little late to the party, was very happy to log on and see all the replies!
Just for Reference,
(Mac Studio) MacOS 15.3.1, DADMan 5.8.0.8, Soundflow 5.10.4, Still nothing here.
I was previously on 5.10.3, just saw the update and Went up to 5.10.4.
Double Checked and confirmed settings: Full Disk, Local Network, Accessibility all granted for sound flow.
On the initial install of 5.10.4, Momdeck showed up! and everything was working great.
Then I restarted the computer, and it was gone from the device list and no longer working....
- Ron Aston @Ron_Aston
This is exactly what I've been experiencing for almost 2 weeks now. I was just about to post that I tried reverting back to SF 5.10.4 several days ago when Marco and I were trying to get to the bottom of this issue. At first it worked for him until I asked him to restart his computer where he also discovered that MoMdeck was no longer showing in the DM Device list. I also feel that there's an overall connection issue with SoundFlow, possibly due to an Apple security update or maybe something else.
I'm happy to hear that it might not be a MoMdeck issue after all because, as you know, I love MoMdeck and I've never had this kind of issue before. Please keep us posted and thanks again for giving this your attention. Also, FYI...This is also happening on MacOSs 15.3 and 15.3.2 for me.
- CIn reply toCameron_Frankley⬆:Cameron Frankley @Cameron_Frankley
Just to note, maybe this is also partly a DADman issue?
I have 2 DADman devices on the network. on the MOMdeck computer, I have one of the DADman devices loaded (the only one I care about for MOMdeck)
But, after the Soundflow reinstall, I noticed that the second Dadman device was ALSO showing up in dadman.
I didn't think anything about it until after I restarted both the Momdeck device AND the second DADman device disappeared.... So maybe it's a DADman local network bug?
confirming that DADman does have local network access... but maybe that's a possible direction for investigation?
- In reply toCameron_Frankley⬆:Andrew Scheps @Andrew_Scheps
Just to be specific about what is consistently working for me here. We need to be super specific. This isn't the only configuration that works for me, but system 1 is:
One computer with both Dadman and MOMDeck on it
OS 15.3.2
SF 5.10.4
MOMDeck 1.0.10
Dadman 5.7.2.1
No Dadman devices at all other then MOMDeckWhen I have a SF version greater than 5.10.4 installed, after shutting down and starting back up MOMDeck won't show up in the Dadman device list. If I then install SF 5.10.4c and launch MOMDeck it shows up. Every once in a while I need to launch Dadman, launch MOMDeck, close both, then relaunch both and then it shows up every time. With 5.10.4 installed, after that it shows up after a restart or shut down/startup.
I will check OS 15.5 later.
As far as a Dadman networking issue, it's possible, but one Dadman is really good at is bridging every single network you have hooked up to your computer together, so it will usually find a MOM as soon as it shows up on any network.- Andrew Scheps @Andrew_Scheps
@mbernardo Could you try the steps above and see what happens?
- In reply toCameron_Frankley⬆:Andrew Scheps @Andrew_Scheps
Could you each respond to this with anything you are seeing that is different? For troubleshooting I think it would be a good idea to run SF and MOMDeck on the same computer as Dadman. Once we get that solid we can branch out to remote setups (which also work for me...)
- SShawn Honsberger @Shawn_Honsberger
Hi @Andrew_Scheps, I am having the same issue as all of the above. SoundFlow 5.10.5, macOS 15.5, DADman 5.8.1.6, MOMDeck 1.0.4, and all recommended permissions have been given and re-applied to SoundFlow. While I believe that this started happening more for me in 15.4.1, it has persisted or worsened in 15.5. When this first started happening in 15.2 (due to a macOS issue unrelated to SF, later resolved in DADman), a log out and log in resolved it. Now, a fresh login or restart does not. The only thing that seems to work is re-adding SF to all appropriate macOS tcc permissions. Everything runs on one machine in my setup.
System Details:
Apple Mac Studio M2 Ultra 24 Core CPU, 60 Core GPU, 192GB Unified Memory, 4 TB SSD
Apple iPad Pro M2 (12.9-inch) (6th generation)I/O + Control Surfaces:
AVID Pro Tools | MTRX Studio (TB3 Native)
AVID Thunderbolt 3 Option Module:
RTL (96k): 1.2ms at 32 samples, 1.8ms at 64 samples
RTL (48k): 2.3ms at 32 samples, 3.6ms at 64 samples
AVID S1 EUCON Controller
Elgato Stream Deck XLSoftware:
AVID Pro Tools Ultimate Perpetual 2024.10.2
AVID EUCON 2025.3
AVID Control 2025.3
AVID MTRX Studio Firmware 1.1.5.1
AVID DADman 5.8.1.6
AVID DADTBDriver CoreAudio 1.2.2
Dolby Atmos Renderer 5.3.1
Apple macOS 15.5
Apple Logic Pro 11.1.2
SoundID Reference for Multichannel 5.12.1
SoundFlow 5.10.5
Scheps MOMDeckDolby Atmos 9.1.4 Monitoring:
Kali Audio IN-8 V2 (9)
Kali Audio WS-12 V2 (1)
Kali Audio IN-5 (4)Great tool! Thank you!
Shawn- Andrew Scheps @Andrew_Scheps
Hi @Shawn_Honsberger ,
OS 15 is turning out to be a nightmare for networking all around, but for some reason SF and MOMDeck have been affected more than some other apps. A very odd thing is that most users aren't having issues. I know that doesn't help, but is worth mentioning.
All that said, what exactly do you mean by
The only thing that seems to work is re-adding SF to all appropriate macOS tcc permissions? Which permissions do you mean? And is this workaround 100% for you? The more data I can gather the more likely we can figure out the root cause and try to find some way around it.One other thing to try, though it only seems to work for some people, is to try going back to SF 5.10.4 (https://soundflow.org/account/downloads). You'll have to do your workaround the first time, but it's possible that this will make it hold. There's no reason it should work considering the changes between 5.10.4 and 5.10.5 have nothing to do with networking, but it's worth a try...
I know none of this completely fixes it for you, but the more data we have the better.
Thanks!
Andrew- SShawn Honsberger @Shawn_Honsberger
Hi @Andrew_Scheps. Thanks for your response. I mean that after a reboot, if I go into System Settings Privacy & Security > and toggle off and on permissions for Accessibility, Full Disk Access, and Local Network, DADman will see the Soundflow Mom in the Device List. Until I do that, it hangs unless I cancel the "Connecting to devices" dialog in DADman. This does seem to work 100% of the time, but is tedious.
I have tried reverting to 5.10.4 as well as 5.10.3 to no avail.. However, I will try again. The only thing I haven't done is reset the tcc database for SoundFlow as referenced below e.g.
tccutil reset All org.soundflow.sfsx, which I may do if I have no luck. It has helped me with other SF issues before.https://soundflow.org/docs/getting-started/install-soundflow/known-issues
https://eclecticlight.co/2023/02/09/should-you-reset-its-database-or-delete-it-the-woes-of-tcc/Thanks,
Shawn- Andrew Scheps @Andrew_Scheps
Definitely let me know if that helps!!!
The most frustrating thing is I was only able to reproduce this once and since then it just works for me. At the moment I couldn't troubleshoot within the OS anyway, but...
I know the workaround is a pain, but with all of the different workarounds people have I'm hoping we can find the common thread.
- SShawn Honsberger @Shawn_Honsberger
@Andrew_Scheps Sadly, following the SF article and resetting the tcc database for SF didn't work. 5.10.4 didn't either. Thanks.
- Andrew Scheps @Andrew_Scheps
But your original, pain in the butt, workaround still works? Also, because I’m ignorant, what does tcc stand for?
I really wish I could repro any of these issues here. I’m on 15.3.2 with no issues. I have a machine on 15.5 and so far I haven’t been able to break it consistently but I’ll keep trying.
- SShawn Honsberger @Shawn_Honsberger
@Andrew_Scheps It only works until I restart. Then I have to repeat it. TCC stands for Transparency, Consent and Control, a macOS concept mentioned in the SoundFlow and Eclectic Light articles above. It allows users to opt in to allow things such as local network, full disk access, accessibility, etc.
- In reply toCameron_Frankley⬆:Andrew Scheps @Andrew_Scheps
Also, just to rule things out that do network stuff, if you have Eucon on the machine with Dadman and SF go ahead and quit it while troubleshooting. I doubt it's part of the problem but it is a variable that does things on the network.
- CIn reply toCameron_Frankley⬆:Cameron Frankley @Cameron_Frankley
(UPDATE: As of 5.27.2025 The steps taken in this post no longer work as a workaround)
(Previous Post)
Finally have a somewhat working system!I do wonder if Eucon did have something to do with it....
System:
OS 15.3.1
SF 5.10.4
MOMDeck 1.0.10
DADman 5.8.0.8Connected to DADman: Avid MTRX, DADmom, MOMDeck
Eucon Turned off, WS control Active. DADman and MOM deck on same computer.Steps to get things working (for my specific case):
On Computer start Quit DADman, Quit
Wait for WS control (and all other Login Items to initialize, Stoped Econ from loading at login)
Load up DADman, wait for Dadman to finish loading everything except Momdeck
Load up Soundflow, Dadman finds Momdeck and loads happily....
If I do anything other than that exactly... it won't work...
- Andrew Scheps @Andrew_Scheps
Once it's hooked up can you run Eucon?
- CCameron Frankley @Cameron_Frankley
Yep!
Once it's connected its stable. and I can start up Eucon and it's fine.However, If Eucon is on at all, before it's connected, it won't connect....
- Andrew Scheps @Andrew_Scheps
That's a great data point! I'll try to repro that here. The more we narrow it down the more we might be able to get it fixed for good!
- CCameron Frankley @Cameron_Frankley
Update! (An unfortunate one....)
This all suddenly.... just stoped working. No changes on my end, just full stop nothing will get it to connect again:
I saw there was a MomDeck update, after it stoped working I figured Id give that a shot, but still not working. My above workaround no longer works, reseting the permissions like Shawn was talking about above also doesn't work.
Just for kicks.... I took a dive into the Soundflow logs, there is an error that popped up for me... but uncertain if it's a useful one? Or if it's just a normal sound flow thing:
27.05.2025 12:03:52.93 [Backend]: [OfficialPackageManager] Fetching official packages from server ...
27.05.2025 12:03:52.93 [Backend]: [SF_FIREBASE_WS]: Received 43 bytes. Total received: 1612
[WebsocketDatabaseSubscription]: [L_2] Received OK
[SF_FIREBASE_WS]: Received 43 bytes. Total received: 165527.05.2025 12:03:52.93 [Backend]: [WebsocketDatabaseSubscription]: [L_3] Received OK
27.05.2025 12:03:52.93 [Application]: [BackendSessionUpdate] SessionReady
27.05.2025 12:03:53.12 [Backend]: [OfficialPackageManager] Result received27.05.2025 12:03:53.18 [Backend]: [ConfigurationController] LoadConfigurationAsync user effective changeType 'Root' reason 'AuthStateChanged' changedPath '' hasCloudPro: True: AuthenticationState changed (soundflow-cloud-pro)
[ConfigurationController] Sending new ZIP packages to sfgui
[StreamDeck] Loaded configuration first time. Handle Device Connected events.
#StreamDeck.DeviceConnected: "" -> Clip Colors 8x427.05.2025 12:03:53.18 [Backend]: Effective Active User Profile:
27.05.2025 12:03:53.23 [Backend]: #StreamDeck.DeviceConnected: "" -> MOMDeck for Stream Deck Plus
27.05.2025 12:03:53.23 [Backend]: >> Command: Clip Colors 8x4
#StreamDeck.DeviceConnected: "" -> Clip Colors 8x4
#StreamDeck.DeviceConnected: "" -> MOMDeck for Stream Deck Plus27.05.2025 12:03:53.23 [Backend]: #StreamDeck.DeviceConnected: "" -> Clip Colors 8x4
#StreamDeck.DeviceConnected: "" -> MOMDeck for Stream Deck Plus27.05.2025 12:03:53.23 [Backend]: [AxDeckInstance] Setting up render frequency at 15 frames/sec, equalling 66 ms per render
27.05.2025 12:03:53.24 [Backend]: [AxDeckInstance] InstanceShow: (Clip Colors 8x4) Device: 'CL04L2A03559'
[AxStreamDeckDevice id#1] Device 'CL04L2A03559' -> ShowDeckInstance:
<< Command: Clip Colors 8x4Command: MOMDeck for Stream Deck Plus
27.05.2025 12:03:53.24 [Backend]: [AxDeckInstance] Setting up render frequency at 15 frames/sec, equalling 66 ms per render
[AxDeckInstance] InstanceShow: (MOMDeck for Stream Deck Plus) Device: 'A00WA3141PCZHI'
[AxStreamDeckDevice id#2] Device 'A00WA3141PCZHI' -> ShowDeckInstance:
<< Command: MOMDeck for Stream Deck Plus
Command: Clip Colors 8x427.05.2025 12:03:53.24 [Backend]: [AxDeckInstance] InstanceShow: (Clip Colors 8x4) Device: 'CL04L2A03559'
[AxStreamDeckDevice id#1] Device 'CL04L2A03559' -> ShowDeckInstance:
<< Command: Clip Colors 8x4Command: MOMDeck for Stream Deck Plus
[AxDeckInstance] InstanceShow: (MOMDeck for Stream Deck Plus) Device: 'A00WA3141PCZHI'
[AxStreamDeckDevice id#2] Device 'A00WA3141PCZHI' -> ShowDeckInstance:27.05.2025 12:03:53.24 [Backend]: << Command: MOMDeck for Stream Deck Plus
Command: Clip Colors 8x4
27.05.2025 12:03:53.25 [Backend]: [AxDeckInstance] InstanceShow: (Clip Colors 8x4) Device: 'CL04L2A03559'
[AxStreamDeckDevice id#1] Device 'CL04L2A03559' -> ShowDeckInstance:
<< Command: Clip Colors 8x4 [user:ckp49i4j60000a2100yfwywgf:ckvm5h3kl00021d10dcx5hpel]
Command: MOMDeck for Stream Deck Plus [user:clk7h33ft00006j10modx927s:clg3tcy8l0000b110m59h5jzm]27.05.2025 12:03:53.25 [Backend]: [AxDeckInstance] InstanceShow: (MOMDeck for Stream Deck Plus) Device: 'A00WA3141PCZHI'
[AxStreamDeckDevice id#2] Device 'A00WA3141PCZHI' -> ShowDeckInstance:
<< Command: MOMDeck for Stream Deck Plus [user:clk7h33ft00006j10modx927s:clg3tcy8l0000b110m59h5jzm]27.05.2025 12:03:53.26 [Backend]: [ConfigurationController] Sending new ZIP packages to sfgui
27.05.2025 12:03:53.35 [Backend]: [TimerServiceInstance #2] Constructed
27.05.2025 12:03:53.35 [Backend]: [TimerServiceInstance #2] Setting up timer service
[TimerServiceInstance #2] Timer enabled: False
[TimerServiceInstance #2] Timer set up, enabled=False27.05.2025 12:03:53.35 [Backend]: [BasicServiceInstance #3] Constructed
27.05.2025 12:03:53.35 [Backend]: [BasicServiceInstance #3] Setting up basic service
27.05.2025 12:03:53.35 [Backend]: [NetServiceInstance #1] OnSetup 1 (parentInvocation=)
[NetServiceInstance #1] OnSetup 627.05.2025 12:03:53.35 [Backend]: [NetServiceInstance #1] OnSetup 2
27.05.2025 12:03:53.35 [Backend]: [TimerServiceInstance #5] Constructed
27.05.2025 12:03:53.35 [Backend]: [NetServiceInstance #1] OnSetup 3 (parentInvocation=)
27.05.2025 12:03:53.35 [Backend]: [TimerServiceInstance #5] Setting up timer service
27.05.2025 12:03:53.37 [Backend]: Logging unknown error in action (02) UdpRequestAction: Broken pipe
27.05.2025 12:03:53.37 [Backend]: Error running Js Callback: 'Broken pipe' (Jint line 313)
[ServiceRegistrationContext] Fired OnSetup callback with error: Broken pipe (__ Service: DADmom: Line 313)
[NetServiceInstance #1] OnSetup 4
[NetServiceInstance #1] OnSetup 5
[TimerServiceInstance #5] Timer set up, enabled=True- Andrew Scheps @Andrew_Scheps
Argh! It is 99% sure a Sequoia thing. I'm working with the SoundFlow team to try and track this down. I' forwarded this but I'll see if they want you to log a bug the normal way so they get the full logs.
- In reply toCameron_Frankley⬆:Andrew Scheps @Andrew_Scheps
Ok, please use Help/Issue in the SoundFlow menu to log a bug. Put MOMDeck Sequoia Connection Issue in the title.
Thanks!
- CCameron Frankley @Cameron_Frankley
Just did so!
- In reply toCameron_Frankley⬆:Ron Aston @Ron_Aston
Just seeing this now. Here's my Pro Tools/Dadman 2 computer system info...
Main Mac = M1 Mac Studio Ultra - MacOS 15.5
SF 5.10.52nd Mac = M2 Mac mini Pro - MacOS 15.5
SF 5.10.5
MoMdeck 1.0.10
DaDman 5.8.1.6 (latest)As I mentioned before, I've tried with OS 15.3 and 15.3.2 along with SF5.10.4 on the Mac mini (DaDman computer) with no luck. I've been running DM 5.8.1.6.through all of these tests. Perhaps I should roll back to DM 5.2.7.1 or 5.8.0.8
The only way that way that I can get MoM to show up in DM after a MacMini restart or cold boot is to go into system prefs on that computer and either enable or disable SF in the Full Disk Access window. I know...sounds crazy but either way works depending on the previous on/off state of SF in that window. At least I have a 100% reliable workaround now.
Also...NO Eucon in my life on either computer.
- In reply toCameron_Frankley⬆:Ron Aston @Ron_Aston
No luck with DM 5.7.2.1. Going back to 5.8.1.6.
- S2In reply toCameron_Frankley⬆:SoundFlow Bot @soundflowbot
This issue is now tracked internally by SoundFlow as SF-1868
- S2In reply toCameron_Frankley⬆:SoundFlow Bot @soundflowbot
This report was now added to the internal issue tracked by SoundFlow as SF-1867
In reply toCameron_Frankley⬆:Kitch Membery @Kitch2025-05-28 21:52:55.121Z@Cameron_Frankley, @Olivier_Nijs, @Andrew_Scheps, @Shawn_Honsberger, @mbernardo,
Hi all, I did a troubleshooting session with @Ron_Aston today (Thanks for your time, Ron). During the Zoom session, we found a way (on his system) to make his MomDeck device appear in the Dadman device list page.
It would be great if you could each see if the steps below work on each of your systems. (Note: The first 4 steps may not be needed.)
Quit and restart SoundFlow
- Quit SoundFlow
- Quit DadMan
- Start SoundFlow
- Start Dadman
Toggle Accessibility Settings
- In DadMan, open the device list (MomDeck is not visible)
- Open System Settings
- Click on Privacy and Security in the left column
- Click on Accessibility in the right column
- Toggle SoundFlow's Accessibility off
- Wait a moment
- Turn SoundFlow back on
- If the Quit and Reopen option is displayed, click "Quit and Reopen". (Mom Deck should connect)
Toggle App Management Settings
- Go to Privacy and Settings
- Go to App Management
- Toggle SoundFlow's App Management "off"
- If the Quit and Reopen option is displayed, click "Quit and Reopen".
- Toggle SoundFlow's App Management "on"
- If the Quit and Reopen option is displayed, click "Quit and Reopen". (After toggling, Mom Deck should connect.)
I'd love to hear if these steps work for each of you, at least as an interim workaround.
Marco Bernardo @mbernardo2025-05-28 23:22:47.188ZI'm not seeing the issue anymore on my end, since I reinstalled Rosetta. btw I don't have access to 5.11.preview11
Kitch Membery @Kitch2025-05-28 23:36:29.725ZHi @mbernardo, I heard you were able to get it working by reinstalling Rosetta. Glad that worked for you.
The steps above are for others who are not using Rosetta. :-)
Also, afaik right now SoundFlow 5.10.5 is the latest stable version.
- In reply toKitch⬆:SShawn Honsberger @Shawn_Honsberger
Hi @Kitch This works, until you restart the device. Then you have to repeat the process each time a restart or shutdown is done. Thanks! Shawn
- Kitch Membery @Kitch2025-05-29 21:06:23.883Z
- In reply toShawn_Honsberger⬆:Andrew Scheps @Andrew_Scheps
Yeah, it’s all about workarounds until we can get the OS stuff working. Sequoia is a real nightmare for permissions.