I’ve been slowly ramping up my big custom laser installation robot thing over the past few months, but it’s finally hitting critical mass and the pressure is now on to get this properly working finally.
I’ve always had weird sound issues in liberation, it really doesn’t seem to like the MOTU ASIO driver. You added the ability to set samplerate in the past few releases, but I’ve never been able to get it to work. That is to say, I select the motu output, set the samplerate to 44100 to match the interface settings - but never get audio in or out to work. Nothing happens
Where this is really causing issues now is I desperately need LTC In from Chataigne to syncrhonize them, so I set the LTC timecode window to use my interface, the correct input channel, and the right samplerate - but it does not pick up the sound at all - I’ve verified it’s there with other programs.
The worst is after I do this and close liberation, it will never open again. Opening it now that it has the LTC In set to my motu asio, it immediately crashed before even showing the GUI. I have to manually go in and edit the settings.cfg for liberation and remove the motu reference to get liberation to start again at all. Below is the crash log from when I try to start it with the motu set for LTC in:
=== Crash Detected ===
Crash code: 0xc0000005
Address: 0x00000001415F14D5
Stack trace:
xmlXIncludeProcessNode [0x1415f14d5]
xmlXIncludeProcessNode [0x1415e5b0b]
xmlXIncludeProcessNode [0x141860e68]
xmlXIncludeProcessNode [0x141861b29]
xmlXIncludeProcessNode [0x1414187b4]
xmlXIncludeProcessNode [0x14140c192]
xmlXIncludeProcessNode [0x1414901da]
xmlXIncludeProcessNode [0x14141e000]
xmlXIncludeProcessNode [0x14141076a]
xmlXIncludeProcessNode [0x14140d9d7]
xmlXIncludeProcessNode [0x14134ad15]
xmlXIncludeProcessNode [0x1412d9219]
xmlXIncludeProcessNode [0x141806cdd]
xmlXIncludeProcessNode [0x141815395]
xmlXIncludeProcessNode [0x1418247ba]
xmlXIncludeProcessNode [0x14185f19a]
xmlXIncludeProcessNode [0x14185ef9f]
xmlXIncludeProcessNode [0x141820044]
xmlXIncludeProcessNode [0x141405317]
xmlXIncludeProcessNode [0x1418892e6]
BaseThreadInitThunk [0x7ffd9c497374]
RtlUserThreadStart [0x7ffd9d0fcc91]
sometimes the crash on launch is also this:
=== Crash Detected ===
Crash code: 0xc0000005
Address: 0x0000000000000000
Stack trace:
to rule out 44.1khz related issues/bugs I switched my interface back over to 48khz, and set liberation to match, but same behavior and exact same error log content. I’m willing to assist however needed to get this solved, I can provide remote access to the PC or anything else needed!
