search

Vampouille / superboucle

Loop application synced with jack transport
GNU General Public License v3.0
35 stars 10 forks source link

Losing midi controls, except from clips start/stop #78

Open manucontrovento opened 4 years ago

manucontrovento commented 4 years ago

HI everyone, in latest days testing several sessions, I found this further problem: midi controller is fully working, then something happens and the only buttons working in midi controller are the clips start/stop buttons. Transport buttons, line buttons etc. don't work no more, while from the transport buttons on screen all is working. The only way to get the buttons working again is to re-do the midi learning, creating a new controller. Also loading a saved controller doesn't work, nor setting None controller and selecting it back again.

This time Jack latency is ok, 1024 or 2048 and period = 2

So I reloaded the session, using the debug SB version, and I found that there's an error, but I don't know if it could be related:

qt5ct: using qt5ct plugin qt5ct: D-Bus global menu: no port_registration: jack.OwnMidiPort('Super Boucle:input') True port_registration: jack.OwnPort('Super Boucle:input_L') True port_registration: jack.OwnPort('Super Boucle:input_R') True port_registration: jack.OwnMidiPort('Super Boucle:output') True port_registration: jack.OwnPort('Super Boucle:Main_R') True port_registration: jack.OwnPort('Super Boucle:Main_L') True graph_order graph_order port_connect: jack.OwnPort('Super Boucle:Main_L') -> jack.Port('system:playback_1') True graph_order port_connect: jack.OwnPort('Super Boucle:Main_R') -> jack.Port('system:playback_2') True graph_order port_connect: jack.MidiPort('a2j:APC Key 25 [20] (capture): APC Key 25 MIDI 1') -> jack.OwnMidiPort('Super Boucle:input') True graph_order port_connect: jack.OwnMidiPort('Super Boucle:output') -> jack.MidiPort('a2j:APC Key 25 [20] (playback): APC Key 25 MIDI 1') True graph_order qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1088, resource id: 10668666, major code: 40 (TranslateCoords), minor code: 0

is it enough to understand something about the problem? have a nice day manu

Vampouille commented 4 years ago

@manucontrovento Did you try to turn off and on your midi controller ? I will check the learning code to see if there is some reset message sent.

manucontrovento commented 4 years ago

@Vampouille I tried, but nothing changes

manucontrovento commented 4 years ago

Hello, yesterday I noticed a similar kind of issue, but at reverse: only clips buttons were detected and working, while transport buttons were not working anymore

Vampouille commented 4 years ago

@manucontrovento I think I found a bug is the process that map midi event to action. I will try to push the fix as soon as possible.

Vampouille commented 4 years ago

@manucontrovento I push a new commit in the debug branch : https://github.com/Vampouille/superboucle/commit/56ac7786e6402c80ad78d8eaae566c617a698873

Can you re-test device mapping with this commit it should fix most of the bug in device mapping ?

manucontrovento commented 4 years ago

@Vampouille Sure! I think I'll test it tonight.

manucontrovento commented 4 years ago

@Vampouille yeah man! using debug version, seems to be working!

manucontrovento commented 4 years ago

I did some tests, imho you could load this fix in master branch. Or maybe you prefer to wait and update master branch when you'll have a bunch of some other fixes/features ?

Vampouille commented 4 years ago

I did some tests, imho you could load this fix in master branch.

yes

manucontrovento commented 4 years ago

Hi @manucontrovento ! Should I close the issue? Or should I wait the fix in master branch? have a nice day

Vampouille commented 4 years ago

needs #83