Send CC69 message to helix from forscore

[cfossen]

I'm trying to figure out what the format of a hex command I need to send a snapshot change.

I've tried

B0 69 2

for example to set snapshot 3.

I can send program changes fine so basic connectivity is there.

I've tried Forscore support with no response yet.

[codamedia]

4 hours ago, cfossen said:

I've tried

B0 69 2

 

That should be right for Snapshot 3. 

However some devices require 0xB0 instead of just B0... it should be safe to try that. 

 

Also... keep in mind that in B0... the 0 stands for the midi channel - in this case Midi Channel #1. Make sure the Helix is set to receive on that channel, or change that value accordingly. 

 

It wouldn't hurt to contact line 6 support through your account and the ticket system... explain the problem and ask them what the Helix needs to see. 

 

At the same time... wait for word from forscore, then give them crap for not simply providing options for CC values. Forcing people back to HEX for MIDI is archaic! I haven't seen that since the 80's! 

 

Good luck... and please keep us updated. I'd like to know how this turns out. 

[cfossen]

On 1/10/2020 at 10:13 PM, codamedia said:

 

That should be right for Snapshot 3. 

However some devices require 0xB0 instead of just B0... it should be safe to try that. 

 

Also... keep in mind that in B0... the 0 stands for the midi channel - in this case Midi Channel #1. Make sure the Helix is set to receive on that channel, or change that value accordingly. 

 

It wouldn't hurt to contact line 6 support through your account and the ticket system... explain the problem and ask them what the Helix needs to see. 

 

At the same time... wait for word from forscore, then give them crap for not simply providing options for CC values. Forcing people back to HEX for MIDI is archaic! I haven't seen that since the 80's! 

 

Good luck... and please keep us updated. I'd like to know how this turns out. 

Yes, I should have stated that the Helix is set to receive on channel 1 (which works for the program changes) and using snapshot 3 as an example. I'll try the 0x. They didn't have any examples and I assumed they wanted values in hex and not in decimal.

Forscore's response was less than helpful.

Thanks!

[codamedia]

Just to confirm.... 

Sending a CC 69 command via HEX is not working... but you CAN send a Program Change in HEX? 

 

Can you provide a sample of the Program Change HEX you are using? 

 

[cfossen]

On 1/15/2020 at 7:15 AM, codamedia said:

Just to confirm.... 

Sending a CC 69 command via HEX is not working... but you CAN send a Program Change in HEX? 

 

Can you provide a sample of the Program Change HEX you are using? 

 

Yes, I can send a Program Change in hex.

Using the MIDI learn function in Forscore, I see that Helix sends

B0 00 00

B0 20 05

C0 14

To select patch 06A (020).

I can send that exact set of codes and it works.

[cfossen]

I finally got it working with Forscore.

In Forscore, send:

Program Change: 1 0 5 20 // Channel 1 Setlist 6 Preset 20

Delay: 500 ms // Delay needed when changing from a "distant" patch

Hex Codes: B0 45 02 // Snapshot 3

I should have realized 69 was decimal (doh!). Also, the leading zero is needed.

I had tried 45 earlier but without the leading zero on the value.

[codamedia]

8 hours ago, cfossen said:

I should have realized 69 was decimal (doh!).

 

You and me both.... complete oversight on my part.

 

Thanks for the update... glad you got it working.

[cfossen]

8 hours ago, codamedia said:

 

You and me both.... complete oversight on my part.

 

Thanks for the update... glad you got it working.

Your questions gave me ideas to try which helped narrow in to the problem.

It was also helpful to create a MIDI CC command in the command center. Sending it with a snapshot change, I could then see the format of the command in Forscore.

 

Thanks!