Does Receptor block MIDI Start, Stop, Continue ?

[gregh1]

Can anyone confirm if Receptor blocks MIDI Start (code 0xFA), Continue (code 0xFB), and Stop (code 0xFC) from getting through to VSTs ?

It seems that it does block them, but it would be better if they were not blocked...

[philosorhymes]

Have you clicked the 'Route CC's to plugin' box?

[gregh1]

'Route CCs to plugin' is checked, but perhaps FA/FB/FC are not considered CCs. Muse may not have thought of Receptor as a sequencer...

[thesoundsmith]

Do you have a plug that will let you examine the midi stream? I have installed Midi Monitor, sometimes it works, sometimes it loads ut sees nothing (perhaps because I'm sending via USB) and somtimes it resets (crashes!) the Receptor. I hope there is a better one out there, but haven't seen it so far. But if you can get it (or one similar) to work, you can tell for sure if Receptor sees the numbers.

Don't know why they WOULD, it's easier to ignore it than filter it out, and should make no difference to the VSTs, AFAICT.

[gregh1]

I agree - I also don't know why they would block FA/FB/FC, but it seems that they do.
I just set up a configuration on my PC with a host (Bidule) containing Phrazor. I'm able to send Phrazor FA/FB/FC from an external hardware box, and Phrazor responds.
The same config (Phrazor on Receptor) does not respond to FA/FB/FC.
I'm willing to be proven wrong. Please!
Until then: MUSE, PLEASE STOP BLOCKING FA/FB/FC.
I've been working for over a year trying to get sequencing and Jamstix fully running on Receptor, and it looks like this is the last piece of the puzzle.

[thesoundsmith]

sounds like a plugorama tech support issue. They respond pretty quickly and are friendly. Give them a try.