[Solved] Sonar Platinum audio thread won't terminate

I believe the issues here are due to ASIO4ALL, and not caused by Sonar.
 
Many many folks have had issues with ASIO4ALL - sometimes just literally having it installed on the computer, even without specifying it.
 
While some number of people are able to use it and Sonar together, it is in my opinion at best a band-aid, and frequently an impediment to stability.
 
If you DO use it, I would suggest you only have Sonar point to ASIO4ALL, and NOT have the Windows Default Audio Device set to also use ASIO4ALL.
 
Bob Bone
 

Kill ASIO4ALL if you can...

I managed to get ASIO4ALL to work on a Lenovo laptop years ago, but it was hard work configuring it. On a more modern Acer it was hopeless.

If you want a reliable DAW laptop you need one built for the job or something like a high-end HP Z series (there's an article on Cakewalk's website somewhere where they say which model of that series they use and it's far from cheap). Plus an external USB interface. Then beat the PC's bloatware, bluetooth and wireless networking into submission.

Or just get a Macbook and run Logic.

Try disabling Windows sounds. If that uses your sound device, whatever it it you will be locked into 16 but 44.1 kHz because that's what windows sounds are set to and windows gets first grab at your sound device.

This is getting stranger and stranger. The Mic input is 16-bit and the Realtek internal mixer is 16-bit, but the audio chip is a 24-bit DAC which seems bizarre.
 
I've tried enabling and disabling things in various ways. I always restart after a change to be sure the system initialized with that state.
 
When I disable the Mic and system sounds and then start Sonar, there is a constant loud random noise on the output which does not show up on the Sonar output bus (set to -90db).
 
Under some settings Sonar will only come up in 16-bit mode even though the Wave Profiler lists things properly. That may be when the Realtek mixer and Mic are enabled as inputs. In some of these settings, the output bus will show fluctuating white noise at about -80db.
 
Since I rarely will use Sonar on the laptop (as I mentioned it was mainly just an excuse to download a clean install of Platinum without messing up my major DAW desktop) I think I will cop and and just kill Sonar upon exiting. All other settings seem to be worse.
 
I really need to get back to the main DAW and set up Platinum there.
 
For the record, though, here is where I left things:
 
In the Sounds Control Panel:
----------------------------------
 
Speakers - Realtek High Definition Audio; 24-bit, 48kHz; Exclusive mode boxes both checked. I think this is the default.
 
Mic and Mixer - default settings - 16-bit, 48kHz.
 
Windows Sounds - default sounds settings, Play startup sound.
 
In Sonar Platinum:
-----------------------
 
Audio Devices - only the Realtek Speakers are selected, Mic and mixer not checked.
 
Device Settings - Audio bit depth 24; 64-bit Audio engine (I do use 64-bit Wave files); 48kHz sample rate; 624 samples (13 ms buffer size) - (from Wave Profiler)
 
Playback and Recording - WASAPI mode, Pow-r 3 dither; Share drivers; Use multiprocessor engine; Use MMCSS; Always stream through FX
 
With these settings I can share my DAW projects with the laptop and use my virtual MIDI devices: VMPK - keyboard; VMIDIJOY - joystick controller; Fractal Tune Smithy midi generator - through LoopBe30.
 
Sonar will not quit on closing in this case, but it the simplest arrangement I can come up with for now. All the Sonar threads left dangling are waiting for something in the audio drivers. Waiting for many minutes is to no avail.
 
The laptop audio drivers are the latest as of yesterday - Realtek HDA release 2.74 driver 6.0.1.7246
All other laptop drivers are up-to-date according to Driver Detective, Acer and Gateway website and Windows Update.
 
In all other issues, Sonar Platinum works great - the Touch screen is kind-of cool to use on the mixers.
 
I have no laptop issues with anything else I use. The base OS was ruthlessly excised from vendor bloat. Only the power handling and touchpad drivers were left over. I image with Acronis, do not use Restore points, removed the Recovery partition and installed Linux there to have an emergency (non-UEFI) boot. I use Perfect Disk for defragmenting. Ethernet and Bluetooth disabled, Services optimized per Black Viper advice (http://www.blackviper.com/service-configurations/black-vipers-windows-8-service-configurations/)
 
The system is much faster than when I bought it a month ago.

I was not trying to sound negative and I was not aware that this was much talked about. On, for example, the Native Instrument forums, ASIO4ALL was often recommended as a reasonably good driver and it is updated now and then.
 
I will drop this with one last data dump. When Sonar does not terminate, there are 11 threads that remain running.
Some are duplicates, but the unique thread stacks look like this. As the threads are running, the exact values may be changing:
 
 

Thread Start Address: 
Symbol Name: Line Number: PC:
SONARPLT.exe ! int audioConv(wchar_t *,wchar_t * *,struct IFile *,unsigned int,unsigned int,unsigned int,unsigned int,unsigned int,double *,int *,int volatile *,struct tAudioConvCom volatile *,int (*)(unsigned __int64,int,int,int,void *,void *,void *,void *),int (*)(void),unsigned int,unsigned long,struct tDspVolItem *) + 0x311d8 ------ 1406ADFD8
                                                                                                                                                                                                                                                                                                                                                                            
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! NtWaitForSingleObject() + 0xa ------ 7FFF07430C8A13FB50
KERNELBASE.dll ! WaitForSingleObjectEx() + 0x98 ------ 7FFF0485111813FB58





Thread Start Address: 
Symbol Name: Line Number: PC:
wdmaud.drv ! midMessage() + 0xfe10 ------ 7FFEFCB08C60
                                                                                   
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! ZwWaitForMultipleObjects() + 0xa ------ 7FFF074311FA379FA50
KERNELBASE.dll ! WaitForMultipleObjectsEx() + 0xed ------ 7FFF048513ED379FA58





Thread Start Address: 
Symbol Name: Line Number: PC:
SONARPLT.exe ! l9_ippsCos_64f_A53() + 0x5502e0 ------ 140670660
                                                                                
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! NtWaitForSingleObject() + 0xa ------ 7FFF07430C8A4E5FE60
KERNELBASE.dll ! WaitForSingleObjectEx() + 0x98 ------ 7FFF048511184E5FE68




Thread Start Address: 
Symbol Name: Line Number: PC:
gdiplus.dll + 0x28C0 ------ 7FFEFD8D28C0
                                                                                   
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! ZwWaitForMultipleObjects() + 0xa ------ 7FFF074311FA504FAD0
KERNELBASE.dll ! WaitForMultipleObjectsEx() + 0xed ------ 7FFF048513ED504FAD8



Thread Start Address: 
Symbol Name: Line Number: PC:
combase.dll ! CoGetProcessIdentifier() + 0x3c0 ------ 7FFF04B512C0
                                                                                   
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! ZwWaitForMultipleObjects() + 0xa ------ 7FFF074311FAA57F8F0
KERNELBASE.dll ! WaitForMultipleObjectsEx() + 0xed ------ 7FFF048513EDA57F8F8
ntdll.dll ! RtlValidSecurityDescriptor() + 0x85 ------ 7FFF073E3A35A57F918




Thread Start Address: 
Symbol Name: Line Number: PC:
MSVCR120.dll ! _endthreadex() + 0x90 ------ 7FFEFA135024
                                                                                
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! NtWaitForSingleObject() + 0xa ------ 7FFF07430C8ABB4FCF0
KERNELBASE.dll ! WaitForSingleObjectEx() + 0x98 ------ 7FFF04851118BB4FCF8
mfc120u.dll + 24EA54 ------ 7FFEEAD0EA54BB4FD08
SONARPLT.exe ! l9_ippsCos_64f_A53() + 0x31c7c5 ------ 14043CB45BB4FD18




Thread Start Address: 
Symbol Name: Line Number: PC:
ntdll.dll ! RtlFreeUnicodeString() + 0x1370 ------ 7FFF073D33A0
                                                                                  
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! NtWaitForWorkViaWorkerFactory() + 0xa ------ 7FFF0743273A100DFB70
ntdll.dll ! RtlFreeUnicodeString() + 0x1ab6 ------ 7FFF073D3AE6100DFB78
ntdll.dll ! RtlFreeUnicodeString() + 0x1370 ------ 7FFF073D33A0100DFB80

 
arachnaut, I don't think kakku is in the right thread.  He posted the same thing in response to a post that was critical of the new membership model - nothing at all to do with this topic. 
 
He may not have even realized he did it.  (EDIT:  Yep, see above).
 
 
 
 
 

arachnaut
I was not trying to sound negative and I was not aware that this was much talked about. On, for example, the Native Instrument forums, ASIO4ALL was often recommended as a reasonably good driver and it is updated now and then.
 
I will drop this with one last data dump. When Sonar does not terminate, there are 11 threads that remain running.
Some are duplicates, but the unique thread stacks look like this. As the threads are running, the exact values may be changing:
 
 

Thread Start Address: 
Symbol Name: Line Number: PC:
SONARPLT.exe ! int audioConv(wchar_t *,wchar_t * *,struct IFile *,unsigned int,unsigned int,unsigned int,unsigned int,unsigned int,double *,int *,int volatile *,struct tAudioConvCom volatile *,int (*)(unsigned __int64,int,int,int,void *,void *,void *,void *),int (*)(void),unsigned int,unsigned long,struct tDspVolItem *) + 0x311d8 ------ 1406ADFD8
                                                                                                                                                                                                                                                                                                                                                                            
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! NtWaitForSingleObject() + 0xa ------ 7FFF07430C8A13FB50
KERNELBASE.dll ! WaitForSingleObjectEx() + 0x98 ------ 7FFF0485111813FB58





Thread Start Address: 
Symbol Name: Line Number: PC:
wdmaud.drv ! midMessage() + 0xfe10 ------ 7FFEFCB08C60
                                                                                   
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! ZwWaitForMultipleObjects() + 0xa ------ 7FFF074311FA379FA50
KERNELBASE.dll ! WaitForMultipleObjectsEx() + 0xed ------ 7FFF048513ED379FA58





Thread Start Address: 
Symbol Name: Line Number: PC:
SONARPLT.exe ! l9_ippsCos_64f_A53() + 0x5502e0 ------ 140670660
                                                                                
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! NtWaitForSingleObject() + 0xa ------ 7FFF07430C8A4E5FE60
KERNELBASE.dll ! WaitForSingleObjectEx() + 0x98 ------ 7FFF048511184E5FE68




Thread Start Address: 
Symbol Name: Line Number: PC:
gdiplus.dll + 0x28C0 ------ 7FFEFD8D28C0
                                                                                   
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! ZwWaitForMultipleObjects() + 0xa ------ 7FFF074311FA504FAD0
KERNELBASE.dll ! WaitForMultipleObjectsEx() + 0xed ------ 7FFF048513ED504FAD8



Thread Start Address: 
Symbol Name: Line Number: PC:
combase.dll ! CoGetProcessIdentifier() + 0x3c0 ------ 7FFF04B512C0
                                                                                   
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! ZwWaitForMultipleObjects() + 0xa ------ 7FFF074311FAA57F8F0
KERNELBASE.dll ! WaitForMultipleObjectsEx() + 0xed ------ 7FFF048513EDA57F8F8
ntdll.dll ! RtlValidSecurityDescriptor() + 0x85 ------ 7FFF073E3A35A57F918




Thread Start Address: 
Symbol Name: Line Number: PC:
MSVCR120.dll ! _endthreadex() + 0x90 ------ 7FFEFA135024
                                                                                
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! NtWaitForSingleObject() + 0xa ------ 7FFF07430C8ABB4FCF0
KERNELBASE.dll ! WaitForSingleObjectEx() + 0x98 ------ 7FFF04851118BB4FCF8
mfc120u.dll + 24EA54 ------ 7FFEEAD0EA54BB4FD08
SONARPLT.exe ! l9_ippsCos_64f_A53() + 0x31c7c5 ------ 14043CB45BB4FD18




Thread Start Address: 
Symbol Name: Line Number: PC:
ntdll.dll ! RtlFreeUnicodeString() + 0x1370 ------ 7FFF073D33A0
                                                                                  
Thread Stack:: 
Symbol: Line Number: PC:Stack Frame:
ntdll.dll ! NtWaitForWorkViaWorkerFactory() + 0xa ------ 7FFF0743273A100DFB70
ntdll.dll ! RtlFreeUnicodeString() + 0x1ab6 ------ 7FFF073D3AE6100DFB78
ntdll.dll ! RtlFreeUnicodeString() + 0x1370 ------ 7FFF073D33A0100DFB80

I'm afraid all this shows is that Sonar has crashed and there is something going on at kernel level. Without source code you could factor in absolutely anything as the cause.

CakeAlexS
 
 
I'm afraid all this shows is that Sonar has crashed and there is something going on at kernel level. Without source code you could factor in absolutely anything as the cause.

Actually Sonar has not crashed, it is just stuck in a wait loop and never gets the semaphore or token it needs to quit fully.
 
My post was only to allow others to see if they get a similar result. Even the symbols might be erroneous - I don't know how they get determined - maybe they are in the loader image.
 
I have seen a lot of the wait loops in NI products (NIHardwareSErvice) on termination. They are not technically crashes.
 
I suppose you could say the code might look like this:
 
done = false;
while (!done) {
    done = Check(something);
    suspend (100 ms);
}
 
 
and perhaps could look like this:
 
done=false;
start_timeout(10 seconds); // or whatever
while (!done and !Timed_out()) {
    done = Check(something);
    suspend (100 ms);
}
 
The error or misunderstanding is that some of these signals will always be sent, so no timeouts are made.
It not so unusual in the termination steps to find stuff like this, because the steps and variations don't happen so often in the test environment.
 

Saw MSVCR120.dll. Do you have the latest C++ runtime libraries installed?
You wouldn't be running Visual Studio next to Sonar would you?
Did you get rid of ASIO4ALL? If not do it I suggest. Total uninstall (apparently it can be hard to get rid of?).

Ta.

CakeAlexS
Saw MSVCR120.dll. Do you have the latest C++ runtime libraries installed?
You wouldn't be running Visual Studio next to Sonar would you?
Did you get rid of ASIO4ALL? If not do it I suggest. Total uninstall (apparently it can be hard to get rid of?).

Ta.

MSVCR120.dll is 12.00.21005.1 dated 2013-10-04 11:59 PM. I don't know if that is the latest.
I don't have Visual Studio.
ASIO4ALL is uninstalled. No traces left.

D*mn you. Alex.
I just bought a Scarlett Solo.
Don't tell my wife.
 
 

The Scarlett Solo is very nice.