16 posts

RELATED
PRODUCTS

Audio system issues - Fixed in 1.0.3! 2014-03-27T20:29:16+00:00 I just posted this in this thread about the audio interfaces not showing up, but I figured it deserved a topic to itself because if Bitwig sees this.. I have all the answers about how to fix their engine so these issues won't happen anymore! Okay so the issues are two-fold and I'm pretty sure they are only aware of one of them. When the Bitwig engine is queried to find what audio devices exist the resulting XML is not valid. Example: <?xml version="1.0" encoding="UTF-8"?> <Io> <HostApis> <HostApi id="0" name="ASIO" deviceCount="4" defaultInputDevice="0" defaultOutputDevice="0" /> <HostApi id="1" name="Windows WASAPI" deviceCount="23" defaultInputDevice="20" defaultOutputDevice="4" /> </HostApis> USB\VID_23E8&PID_0100\0001002008080 USB\VID_23E8&PID_0100\0001002008080 </Io> The lines with USB\VID in them break this XML, so whatever XML interpreter Bitwig is using freaks out and basically returns nothing - in this case you get no selectable Audio Systems in the preferences. Due to a response on that other thread, I believe Bitwig is already aware of this issue.. but.. This is not the only issue! They also aren't sanitizing inputs, which means in some cases you get things like... <AudioDevice id="3" name="FirePod ASIO x64" hostApi="ASIO" numInputs="10" numOutputs="10" defaultInputLatency="0.017415" defaultOutputLatency="0.017415" defaultSampleRate="44100.0" supportedSampleRates="44100,48000,88200,96000"> <BufferSize min="768" max="768" preferred="768" granularity="0" /> <Inputs> <Input name="LineIn 1&2 left" /> Anyone see the issue? Probably not. The Input listed here has name="LineIn 1&2 left", well you're not allowed to have ampersands within values in XML. This issue will only happen with devices that return names with ampersands.. so it's not going to happen to everyone. When this happens it will make it so you can't select any audio interfaces. Again, the engine freaks out at the invalid XML and crashes. I wrote a quick script (windows only) that patches this issue by redirecting all calls to the bitwig engine through my script and then manually fixes these issues with regular expressions. This isn't a solution though! I can't provide this script to you guys because it only works due to me custom coding it for my specific issues. The crux of the problem is that I can't just remove/replace ampersands within the resulting XML because that could also replace ampersands getting returned from other parts of the engine or in places where they are valid - and that would screw things up in a whole different set of ways. To prove I'm not just making this stuff up - here's me adding in my patch script and you can see the resulting XML is fixed (no more USB\VID lines) http://i.imgur.com/SI3qicT.gif And after doing that the problems are completely fixed! http://i.imgur.com/mkDGw6F.png Another interesting thing.. after fixing this I reverted the engine exe's back to their original version and somehow it's still working in Bitwig. Perhaps they are caching the results of these queries? TL;DR: The issues people are having with not being able to select things within the Audio Interfaces window in the preferences are due to the Bitwig engine generating invalid XML. trappar https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=325394

Costa Rica Costa Rica https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=325281: KVRist; 97 posts since 25 Mar, 2014 from Bitwig Box

Post by Costa Rica » Fri Mar 28, 2014 10:42 pm

0
Quote

Not bad. Not bad. However, these are beta bugs. Still not too impressed.

Post Reply

16 posts

Return to “Bitwig”