Terrible lag with Soundflow in Pro Tools-Part 2
Terrible lag with Soundflow in Pro Tools-Part 2
System Information
SoundFlow 4.3.5
OS: darwin 18.6.0
ProductName: Mac OS X
ProductVersion: 10.14.5
BuildVersion: 18F132
Steps to Reproduce
Expected Result
Actual Result
Workaround
Other Notes
Hi, I have made some interesting descoveries.
11:18 Opening a big session called "Sommelier..." Everything works great.
Group command is fast and responsive. Also Teezio plugin loader works as expected.
11:20 Opening another big(but similar)session called "Scars..."
Now creating groups has a 5+ second delay.
Same with Teezios plugin loader.
11:24 Going back to the first session called"Sommelier..."
Now the Group command is slow on this session as well!
Same with Teezios loader.
So it seems that the problem might be triggered from a certain "problem session" but the problem then spreading to a "healthy session".
But these two sessions are very similar. About the same number of tracks.
Extremely similar in what plugins I used. Can´t see any difference that could cause the difference in behaviour.
Links
User UID: mqPTKVvimwZEtaPkj8sWEmCINcW2
Feedback Key: sffeedback:mqPTKVvimwZEtaPkj8sWEmCINcW2:-MkBs-bTjDAum8qtJ2HF
Christian Scheuer @chrscheuer2021-09-22 09:43:47.415ZHi Stefan
That's wonderful progress!
From what I can tell from the log - this included - the delays are happening inside Pro Tools.
What happens is that every time SF needs to do something, it happens this way:
-> SF tells macOS we need something from PT
-> macOS talks to PT
-> PT's main thread becomes free to do work
-> PT processes the event
-> PT responds to macOS
-> macOS forwards that response to SFIf the PT main thread is constantly blocked by other things then this part could take a long time:
"-> PT's main thread becomes free to do work"
Christian Scheuer @chrscheuer2021-09-22 09:47:11.625ZDo you have any commands in your account that work outside of Pro Tools?
The best way to confirm that this is specific to PT would be to double check if you can run any other SF commands that are not for PT to test if they have the proper, fast speed, at the same time as everything's being slow in PT. This would confirm the issue to be a PT issue.
I have noticed before that having many AudioSuite windows open can cause the PT main thread to hang, which is why I suggested to send us a screenshot and to close any open AS windows. Does that make a difference?
Another way to troubleshoot this could be to:
- Open the good session. Confirm things are normal
- Close the good session.
- Open the good session again. Confirm things are still normal (that is, confirming the error is not just about different sessions)
- Close the good session
- Create a new empty session. Confirm things are normal
- Gradually import tracks from the bad session until things start breaking.
- SStefan Boman @Stefan_Boman
Thanks for the super fast response!
Good thinking.
I tried to open the healthy session. everything works good.
Closed it and opened the same session. Now there's a long delay on everything.
So it doesn't seem to be as simple as good and bad sessions.
WAIT!
Tried something while typing and I might have found something!
I have a second screen that I like to have certain master chain plugins on.
I opened the healthy session a second time(slow response) closed the plugin window for"bx_limiter True peak"and the response is normal again!
Weird since I have that open on all sessions.
Now the behaviour seems replicable back and forth. If its open its slow, closed and its normal again.
So now I have a workaround at least!Thanks for the great support! :)
- Christian Scheuer @chrscheuer2021-09-22 18:16:21.299Z
That's awesome, thanks for reporting back :)