MIDI Program Change trigger does not work?
Hi!
In my rehearsal basement I use Pro Tools as backing track player and with my Nektar Pacer MIDI foot controller I´m able to remote control transport functions.
The Pacer also controls my guitar rig with MIDI program changes which change presets and snapshots on the HX Effects.
Now also want that the MIDI program changes also trigger Soundflow to set the playhead to a memory location.
Now the problem: it seems that Soundflow does not react on MIDI program changes.
is this a bug or ain't it possible?
Thanks
Claus
- Christian Scheuer @chrscheuer2022-10-22 14:25:27.346Z
Hi Claus,
Thanks for taking your question here. This does indeed sound like a potential bug. If you use the MIDI "learn"/record button in your MIDI trigger, can you then get it to react to the PC messages?
We might need to ask you to file a help/issue report so we can see your log files - see here for those steps:
- CClaus Czadilek @Claus_Czadilek
Hi Christian and thanks for your answer!
Yes, that‘s exactly the problem! When i enable the record button i can send various MIDI messages like note on, control changes etc, they all work exept program changes. They either can‘t be read by SF or the IAC Bus can‘t send them.
I tried it with PT sending PC to SF via IAC BusChristian Scheuer @chrscheuer2022-10-23 03:44:47.986Z
Hm ok, thank you. I'll log a bug report for this so we can take a deeper look. Thanks for the details so far.
- In reply tochrscheuer⬆:
Christian Scheuer @chrscheuer2022-10-22 14:33:46.271Z
One way to troubleshoot this would be to make a generic MIDI trigger where you just select the device, but keep it at All Channels and All Events, like so:
Then put this in the script:
log(event.trigger.midiBytes.join(', '));
This should log every time SF receives any MIDI from that device. You should be able to use this to troubleshoot if SF receives PC messages properly.
- CIn reply toClaus_Czadilek⬆:Claus Czadilek @Claus_Czadilek
Hi!
That's what I didi, All Channels and All Events but program changes don't work.
I can see that the MIDI program change does go out from Pro Tools via IAC Bus, I use the application MIDI Monitor and this shows the PC.
Any other MIDI data like CC#, pitch bend, note on, mod wheel work. But not PCs. Strange...to the script - I have no idea where to put it. do I need to convert the SF macro to script and add this in there? That's what I tried and id did not work...
Christian Scheuer @chrscheuer2022-10-23 03:35:15.760Z
To troubleshoot it, you'd have to create a new script, post the contents I made above and add that trigger. Then follow which things get logged.
- CClaus Czadilek @Claus_Czadilek
Hi Christian!
Any news on this?
Thanks!
Christian Scheuer @chrscheuer2022-11-08 23:13:35.443Z
Hi Claus,
How exactly are you sending your Midi PC commands? You're saying they're sent via the IAC driver, but which software sends to the IAC driver in the first place?
It will be easier for us to test this way.
I am seeing some weirdness on how SF (or macOS) handles some MIDI messages of non-standard length.
Unfortunately, I don't think this is an easy fix, but the first step would be able to reproduce a reliable way of producing PC messages in the same shape that you're doing it.
Any info you can share, including sharing photos of MIDI MOnitor and exactly how you're sending data back and forth would be helpful.
- CClaus Czadilek @Claus_Czadilek
Hi Christian!
Thanks for your reply!
Here´s what I do for testing:
I created a Pro Tools session with a MIDI track and put a Program Change message and a MIDI note onto the timeline. MIDI output of the track is IAC Bus.
MIDI Monitor and Soundflow are both listening to this port.
When I play the PT timeline MIDI Monitor receives three MIDI messages (Program Change, Note On and Note Off) but Soundflow only recognizes the Note On (pretty sure it gets Note Off too but this is not necessary for this test).
I made a screen recording of what I do. This is not my real world scenario but in general this is what I try to accomplish, in need Soundflow to react to Program Changes.you can download it here -> https://www.icloud.com/iclouddrive/0a7KCFbGhRdxdKeQSmYJqNjpw#Program_Change
Thanks for the support
- SIn reply toClaus_Czadilek⬆:SoundFlow Bot @soundflowbot
This issue is now tracked internally by SoundFlow as SF-683
- CIn reply toClaus_Czadilek⬆:Claus Czadilek @Claus_Czadilek
Hi!
How is this issue going? Is there a solution in the pipeline?
Thanks
ClausChristian Scheuer @chrscheuer2022-12-05 15:22:17.148Z
Hi Claus,
Thanks for checking in here. We have this scheduled to be worked on together with some other MIDI related issues, but we don't have a timeline for when we can get to it right now.
- In reply toClaus_Czadilek⬆:Christopher Barnett @Christopher_Barnett
Heh Claus, I am also trying todo this, did you work out a workaround to trigger macros via midi?
- CClaus Czadilek @Claus_Czadilek
Hi!
Trigger macros with MIDI does work here, only MIDI Program Changes don‘t work. other MIDI data work such as note, CC, pitch bend…
- CIn reply toClaus_Czadilek⬆:Claus Czadilek @Claus_Czadilek
tried the latest release. still not working.
Christian Scheuer @chrscheuer2022-12-29 13:02:56.099Z
Hi Claus,
As mentioned, we'll update this thread when there are news in a public release. We are working on quite a few MIDI changes and fixes for 5.3, so this should likely be among the fixes for 5.3.
Christian Scheuer @chrscheuer2023-08-14 22:01:52.368Z
Hi Claus,
I wanted to update this thread. We have a new MIDI parsing engine in the latest builds of SoundFlow, so I expect this bug to be fixed now. Please let me know if SoundFlow 5.4.6+ still has this issue for you.
- SIn reply toClaus_Czadilek⬆:SoundFlow Bot @soundflowbot
The linked internal issue SF-683 has been marked as Done