• SONAR
  • Opening an older project crashes SPlat...[SOLVED!!]
2015/09/28 09:43:21
Mesh
Hi all,
I tried to open an older project which was done in X1 and got an error message stating (something like) the audio format is not supported/compatible etc......something to that effect.
 
I went into Preferences and noticed the bit depth was greyed out & set at 16bits. Of note, I've always keep it set at 24 ever since Sonar 7/8 and never changed from that.......so, don't really know how this setting was changed.
 
 Anyway, I clicked on the ASIO panel (within the same screen in Preferences to check my soundcard settings) and SPlat crashed with a Sonar.exe stopped working  etc......error. This happened every time I tried to open that project/procedure and don't know how to change the bit depth from 16 to 24. All the other projects open up fine. I also have the latest drivers for my Focusrite Scarlett 2i4.
 
Any thought on how to fix this?
 
TIA,
Mesh
 
  
2015/09/28 12:11:15
robert_e_bone
That grayed out bit-depth is NOT where you would go to change the bit-depth for recordings.
 
For that, go to Preferences>File>Audio Data, and you will see it there in about the middle of the dialog window.  After changing it and clicking Apply, this will set it for future projects - I always alter my system to use a sample rate of 48 K. as well.
 
Hope that helps, 
 
Bob Bone
 
2015/09/28 12:31:13
scook
Yes, Bob describes how to set the project bit depth for future projects. The problem here is a different issue. The fixed 16bit audio driver is the problem. I do not believe that is normal for the Focusrite Scarlett 2i4 assuming that is the interface defined in SONAR. Double check the device settings in SONAR. Make sure the interface is selected and ASIO driver mode is set. It is not unusual for the driver to have a fixed bit depth but I doubt the Focusrite driver is fixed at 16bit. You may need a driver update.
2015/09/28 13:05:26
Mesh
Yes Scook, that's the issue I'm having.
 
IIRC, I've confirmed all that you've stated (using the 2i4, ASIO etc..) , but it's good to see it in writing and will also double check tonight.
 
I must confess that I didn't manually check for updated drivers at Focusrite, and just going with what my recent upgrade to Win 10 says. So, hoping an updated driver is what's needed.....will post back with my findings. Thanks Bob & Scook.  
2015/09/28 13:10:04
scook
I am not on Win10 yet and do not have a focusrite interface. If you appear to have the correct driver and it is still fixed at 16bit,  consider uninstalling the driver and installing fresh. Is this one of the interfaces that uses MixControl? If so, that may be an issue. Hopefully someone with Win10 and the same interface will contribute here.
2015/09/28 13:29:18
Mesh
scook
I am not on Win10 yet and do not have a focusrite interface. If you appear to have the correct driver and it is still fixed at 16bit,  consider uninstalling the driver and installing fresh. Is this one of the interfaces that uses MixControl? If so, that may be an issue. Hopefully someone with Win10 and the same interface will contribute here.


No, this unit doesn't use MixControl.  
 
Focusrite's site shows their last driver update to be 8/8/2013......which is also the one I currently have, but I'm also inclined to think that an uninstall/re-install of the driver should fix it.
2015/09/28 13:33:25
Doktor Avalanche
So I assume it's 2.5.1?
http://us.focusrite.com/answerbase/windows-10-compatibility
 
Yup removal, reboot, reinstall, reboot.
2015/09/28 18:29:29
Mesh
Yep, the reinstall fixed it. 
 
Thanks Scook & all!! 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account