![]() |
![]() ![]() ![]() ![]() ![]()
|
next newest topic | next oldest topic |
Author | Topic: WaitUntil mysteries | |
phillipm Member |
![]() ![]() ![]()
Any rule of thumb I should be learning? Should I just learn to ignore the error messages in the Status window, if the sound is actually OK? =m.p.= IP: Logged | |
SeanFlannery Member |
![]() ![]() ![]() Hey there, a WaitUntil is usually used in a timeline to my knowledge. What were you trying to achieve with the WaitUntil in a sound? IP: Logged | |
phillipm Member |
![]() ![]() ![]() I usually work on sounds first, then put them in a TimeLine. There were no differences in results when I put these sounds into a TimeLine, so I thought putting all the sounds into one file would be easier to deal with on the forum. Even when simply testing a sound like a CrossFilter with a short capture time and a live input it's sometimes helpful to have a WaitUntil so the capture time doesn't expire between the time you start the sound and you start playing. [This message has been edited by phillipm (edited 29 July 2013).] IP: Logged | |
SSC Administrator |
![]() ![]() ![]() Hi Mark, Another way to do this would be to paste your amplitude threshold Sound into the Capture field of the CrossFilter. That way, it won't start to write the Response until the amplitude threshold is exceeded (and you won't need the WaitUntil). IP: Logged | |
phillipm Member |
![]() ![]() ![]() quote: Yes. That's what I did in the original sound. But then I wanted to create a TimeLine where the whole TimeLine would wait until the threshold was exceeded. And that's when things got wonky. I ended up dividing the sound into two TimeLine tracks, which works fine. ;-) IP: Logged |
All times are CT (US) | next newest topic | next oldest topic |
![]() ![]() |
This forum is provided solely for the support and edification of the customers of Symbolic Sound Corporation.