![]() ![]() ![]() (I got the 19 7f / 19 40 sequence when I wrote my bug report #8960.) It seems my device was in one of the “MCU” modes (the Faderport manual names them “Logic”, “Cubase/Nuendo” and “Live”), as can be gleaned from the MIDI messages that are sent when the “Next” button is pressed. In short: when some of the controls on your Faderport work, but others don’t, or you even get a crash after pressing something, try switching to Studio One mode. (How to switch to Studio One mode: power the Faderport off, press and hold “Next” while switching it back on, buttons start blinking, hit “Solo”. Switching the device to “Studio One” mode made it work as expected. #9 0x00007f332f3fa624 in ArdourSurface::FP2::FaderPort8::midi_input_handler(Glib::IOCondition, boost::weak_ptr) () from /opt/Ardour-7.1.0/lib/surfaces/libardour_faderport2.so #7 0x00007f3353fb4de4 in ARDOUR::AsyncMIDIPort::read(unsigned char*, unsigned long) () from /opt/Ardour-7.1.0/lib/libardour.so.3 #3 0x00007f332f3fa4ea in ArdourSurface::FP2::FaderPort8::controller_handler(MIDI::Parser&, MIDI::EventTwoBytes*) () from /opt/Ardour-7.1.0/lib/surfaces/libardour_faderport2.so #2 0x00007f332f43b1c4 in ArdourSurface::FP2::FaderPort8::encoder_navigate(bool, int) () from /opt/Ardour-7.1.0/lib/surfaces/libardour_faderport2.so Using ALSA backend with raw MIDI (but already tried with external JACK and different MIDI systems) #0 _GI_raise at. I’ll start with basic system information and the top of the stack trace from the core dump. Please, any hint is appreciated! And please ask me anything you’d like to know. What could be causing these crashes? How do I narrow the cause down? Or even solve it, I’d like to use the Faderport!īut I’ll need some help, as I have no idea where I should start looking. Now, I already opened a bug report a while back ( #8960) but as it seems that the Faderport is generally regarded to be working perfectly I think it has to be a problem with my system in particular, and I might as well try to narrow it down myself. I get this behaviour with Ardour-6.9 as well as Ardour-7.1. But when in section mode (“section” button is lit), Ardour becomes unresponsive and crashes (dumps core). I get MIDI events from it, seen in the MIDI tracer.Īnd it works PARTIALLY: hitting the Faderport’s “Prev” Button, the track above gets selected as expected, the fader moves on the device.īut hitting the “Next” Button does NOT work: in master mode (“master” button is lit) it just does nothing that I can see. I have a Presonus Faderport-2 connected and configured as active control surface in Ardour. Hello there, can somebody please help me track down a problem with my Faderport-2? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |