tricky way to recover when audio engine stopped and refused to start again

Author
Piotr
Max Output Level: -86 dBFS
  • Total Posts : 208
  • Joined: 2014/12/25 20:30:44
  • Status: offline
2017/11/10 14:21:52 (permalink)

tricky way to recover when audio engine stopped and refused to start again

Just by accident I discovered way to recover from some situations when audio engine stopped (with drop) but refused to start again...
No matter how many tries I did. Pressed start/stop engine play project but it was not running, no error, nothing, like it would be empty... Removed all vst, tried again, nothing...
Normally in such case I would close project and start again what is super annoying. But just tried to run some undo/redo and magically it cured engine and even restored my vst... :)
 
Probably not to be used in every case when engine don't want start but maybe worth to try before reloading everything.

Regards,
Piotr
Sonar Platinum Lifetime
#1

11 Replies Related Threads

    John T
    Max Output Level: -7.5 dBFS
    • Total Posts : 6783
    • Joined: 2006/06/12 10:24:39
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/10 18:05:46 (permalink)
    Interesting!

    http://johntatlockaudio.com/
    Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
    #2
    Cactus Music
    Max Output Level: 0 dBFS
    • Total Posts : 8424
    • Joined: 2004/02/09 21:34:04
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/10 19:49:33 (permalink)
    Usually the audio engine stops because something is going on in the background and has interrupted the engine. It can't access buffers etc. If you wait long enough what ever was doing this will finish and sort things out. 
    So you keep clicking you actually only make things worse as your stacking more tasks. 
    What you really need to do is run Latency Monitor and find out why your loosing the audio engine. 
    On a properly set up PC you should never have this issue unless you exceed your systems capacity, then you just upgrade components to fix that. 

    Johnny V  
    Cakelab  
    Focusrite 6i61st - Tascam us1641. 
    3 Desktops and 3 Laptops W7 and W10
     http://www.cactusmusic.ca/
     
     
    #3
    Piotr
    Max Output Level: -86 dBFS
    • Total Posts : 208
    • Joined: 2014/12/25 20:30:44
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/10 22:24:20 (permalink)
    Johnny, I am afraid is not such simple.
     
    1. If it were as you described why just closing and reopening project would solve issue?
    2. Waiting longer time should also resolve issue (and let start ) but it is not case.
    3. When trying to start play nothing is happening... No error message but also no any action...
     
    BTW, I was not just clicking 10times per second in buttons ;)

    Regards,
    Piotr
    Sonar Platinum Lifetime
    #4
    Cactus Music
    Max Output Level: 0 dBFS
    • Total Posts : 8424
    • Joined: 2004/02/09 21:34:04
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/11 00:00:34 (permalink)
    OK that's different.. like I said "usually" 
    So next place to look is your Audio interface and drivers. What do you have? and which driver mode. 
    Also a common issue is HDMI audio drivers taking over. Most people find disabling that in device manager a good move. 
     

    Johnny V  
    Cakelab  
    Focusrite 6i61st - Tascam us1641. 
    3 Desktops and 3 Laptops W7 and W10
     http://www.cactusmusic.ca/
     
     
    #5
    Piotr
    Max Output Level: -86 dBFS
    • Total Posts : 208
    • Joined: 2014/12/25 20:30:44
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/11 01:45:46 (permalink)
    I am using on this machine RME FF400 and its ASIO drivers. Audio from monitor disabled at device manager.

    Regards,
    Piotr
    Sonar Platinum Lifetime
    #6
    panup
    Max Output Level: -50 dBFS
    • Total Posts : 2538
    • Joined: 2006/05/23 09:34:35
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/11 18:41:07 (permalink)
    One method that works sometimes for me: power off your soundcard for a while(!).
    SONAR will notify that it has found a new audio driver and asks if it may stop the playback. Yes => audio engine is alive again.
     
    This is not any generic fix method but may help sometimes.
    My interface: RME UFX / ASIO, USB mode.
     
    #7
    Piotr
    Max Output Level: -86 dBFS
    • Total Posts : 208
    • Joined: 2014/12/25 20:30:44
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/11 22:27:14 (permalink)
    Thanks, Panu, sounds promiscuous for such cases.

    Regards,
    Piotr
    Sonar Platinum Lifetime
    #8
    MFanning
    Max Output Level: -86 dBFS
    • Total Posts : 205
    • Joined: 2005/02/06 14:37:09
    • Location: Tempe, Arizona
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/11 23:26:59 (permalink)
    Piotr
    Thanks, Panu, sounds promiscuous for such cases.

    Hey! did you mean "having or characterized by many transient sexual relationships?" 
    #9
    Piotr
    Max Output Level: -86 dBFS
    • Total Posts : 208
    • Joined: 2014/12/25 20:30:44
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/11 23:59:47 (permalink)
    MFanning
    Piotr
    Thanks, Panu, sounds promiscuous for such cases.

    Hey! did you mean "having or characterized by many transient sexual relationships?" 


    Well, looking deeper at disconnecting and connecting audio interface one could have different associations :)
    With all my poor English I only hope nobody feels insulted by me :)

    Regards,
    Piotr
    Sonar Platinum Lifetime
    #10
    Leee
    Max Output Level: -75 dBFS
    • Total Posts : 783
    • Joined: 2004/12/21 11:31:00
    • Location: The Great NorthWest
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/12 01:29:12 (permalink)
    For me, sometimes all it takes is just pressing the play button on the transport bar.  As soon as I start the song playing again, the audio engine comes back.  It's either that or hit the audio engine button.  That works MOST of the time.  But as was already mentioned, the reason for the audio engine to stop in the first place can be caused by many things, so one solution doesn't always work for everyone.

    Lee Shapiro
    www.soundclick.com/leeshapiro
     
    Welcome BandLab and thank you for giving Cakewalk and Sonar a new lease on life.
    #11
    Piotr
    Max Output Level: -86 dBFS
    • Total Posts : 208
    • Joined: 2014/12/25 20:30:44
    • Status: offline
    Re: tricky way to recover when audio engine stopped and refused to start again 2017/11/12 10:48:16 (permalink)
    Exactly, Lee. This is first thing I always try. Pressing play and tries restart audio engine by pressing its icon. Unfortunately, the thing is it is often not enough to recover the engine to life. Closing and re-opening project again is annoying or in worst case scenario closing/starting Sonar but at next time I will try also what Panu suggested.

    Regards,
    Piotr
    Sonar Platinum Lifetime
    #12
    Jump to:
    © 2024 APG vNext Commercial Version 5.1