search

angeloBerlin / MIDI-Automator

MIDI Automator is a desktop software for automating user actions (i.e. opening files, clicking buttons) triggered by midi messages.
http://midi-automator.com
MIT License
18 stars 3 forks source link

Set List Position Resets to position 1 on CC 102 #78

Open TheMattyBoy opened 5 years ago

TheMattyBoy commented 5 years ago

Hi Angelo,

Have found a bug which is a bit of a showstopper for me..

I send Midi Msg to Midi Automator from my novation SL61 MKII. I've mapped the previous and next buttons to buttons on the SL61, which work fine. However, if I press play on the SL61 transport, the setlist in Midi Automator always moves back to the first song in the setlist, and opens it!

I've attached a gif which shows what's happening. The moment I press the 'Play' button on the SL61 Transport, the setlist moves and opens the song in position 1.

Setlist Position Reset

Play Midi Message

Thanks again for creating such an awesome program!

Matt

angeloBerlin commented 5 years ago

Hi Matti,

I am unable to reproduce this. Can you send me an export of your set list via File->Export ?

TheMattyBoy commented 5 years ago

Hi Angelo,

Might be good news that you can't reproduce, although I can't see anything obviously wrong with my config.

Setlist is attached - I'm using Win 10, Midi Automator v1.8.2

Thanks, Matt

Setlist Reset.zip

angeloBerlin commented 5 years ago

Hi Matti, does that only occur if you send the "NEXT" command via Midi or also if you click on "NEXT"?

TheMattyBoy commented 5 years ago

Hi Angelo, clicking the red and green arrows on the app work as expected (moving the setlist position up/down by 1), they also work as expected when sending the learned midi commands. It's just when I press the play button on the transport, the setlist immediately moves from whatever song it is on to the first song and opens it.

angeloBerlin commented 5 years ago

Hi Matty, so it seems as if your "play" button sends a Midi Message. I have sen that you have learned a dedicated message for each Song in the set list. Can you "Midi Unlearn" the message from your first song and see what happens if you hit play?

TheMattyBoy commented 5 years ago

Hi Angelo,

I haven't midi learned any of the songs - well, not consciously! However I just created a new small set with three songs, where I added each file via the 'Add' button only. The same behaviour happens, as soon as I press 'Play' the setlist moves to position 1 and opens the file. I wondered if there was any extra messages being sent from the keyboard, but I recorded it in midi-ox, and there was just the single message shown above.

Short List.zip

angeloBerlin commented 5 years ago

Hi Matty, Unfortunately I am unable to reproduce this behavour. I can only guess that the MIDI message from the play button is interpreted as message for song number one (For whatever reason). Can you maybe do the opposite and explicitly MIDI learn an unused Message for song No1 one and see what happens then?

Cheers, Angelo

TheMattyBoy commented 5 years ago

Hi Angelo,

When I midi learn the first song in the setlist to a button on the keyboard, that works as expected. I press the button, and the song loads. However pressing play still moves to and opens the first song, regardless of the current setlist position - exactly the same as if I pressed the learned midi button.

I can see this may be difficult to investigate if you're not able to reproduce the problem. Next weekend I am borrowing a friends master keyboard, and I can try some more tests with that keyboard to see if the same issue happens - that way we can try and rule out some weird hardware issue with my SL61, rather than you chasing ghosts... Hopefully a different keyboard will provide a clue as to what the issue is. I'll let you know the details once I've tested. Thanks again for your help with this!

Short List with mid learn on song 1.zip

TheMattyBoy commented 4 years ago

Hi Angelo,

Sorry for the delay in getting back to you on this, some family stuff happened...

After more testing, I've found that the transport control on the Novation Keyboard was sending an on / off button press command using the CC Number 102.

image

If I changed this to use a different CC Number, e.g. 103, then the setlist position would not reset to the start when the button was pressed.

So, it seems I can easily work around this problem by mapping the transport play button to a CC Number different to 102, and mapping my DAW play command to this message.

Seems strange, but at least it's a solution for me!

Anyway, feel free to close the issue if you don't think it's worth looking into - I'm sure you have more exciting things to do than look into this, and there is an easy workaround.

Again, thanks again for your time, and for creating such a great tool - it's really useful and I make a point of recommending it!

Matt

angeloBerlin commented 4 years ago

Hi Matty,

thanx for figuring this out. Something in my head reminds me that I used CC 102 for something... but I can not remember what it was. Maybe it was some kind of undocumented "hidden" feature or I left something in the code that was meant for debugging. I will leave that ticket open in case I want to progress the development or if someone else is going to join as developer.

Guys like you push the development and the quality of open source software, so thank you very much for sharing your research.

Cheers,

Angelo