You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've managed to get the driver to crash. It was at a fairly random point, while using REAPER. There was a drum track and a bass track, going out to the same synth module, the drum track was on channel 10, and the bass on channel 1.
I'm going to try running REAPER in a VM because this way I can capture the output of the kernel panic, via a virtual serial port, and get some sort of stack trace.
The text was updated successfully, but these errors were encountered:
I am going to leave this issue open since I never figured out how to get it to crash again, but have not confirmed that it is stable either. Just in case anyone finds a crash, the way you would debug it is you would enable serial console in GRUB and capture the output with another computer's serial port (any old computer would work). I think it's better to have a hardware serial port instead of an USB adapter, I've only tried with a hardware port. Some modern motherboards (such as my MSI) still have a serial port header.
I have stopped using the MOTU with Linux, I setup a windows machine for music editing so I am no longer testing this module.
@lost-bit0 @vampirefrog
I've managed to get the driver to crash. It was at a fairly random point, while using REAPER. There was a drum track and a bass track, going out to the same synth module, the drum track was on channel 10, and the bass on channel 1.
I'm going to try running REAPER in a VM because this way I can capture the output of the kernel panic, via a virtual serial port, and get some sort of stack trace.
The text was updated successfully, but these errors were encountered: