In Reason 10, SampleTank plugin only recognizes midi ch1

[ToddStudio79]

OK...This one I REALLY can't figure out
I open SampleTank as a stand alone and it recognizes any midi channel I choose on the M-Audio Keystation 49es. So everything works perfectly...right
Now when I use it as a plugin in Reason 10, it will only recognize midi channel 1.
No matter what midi channel I select on the Keystation, only CH1 is recognized in SampleTank.
I have already done the midi tests and the Keystation is working perfectly.
What am I doing wrong?

Frustrated
Todd Patterson

[ToddStudio79]

Sorry...just to clarify
It is SampleTank 3

[DarkStar]

Can you add some sort of MIDI Monitor in Reason to check what channel Reason is sending the MIDI to ST3?

Many DAWs can be set to change the MIDI channel of incoming MIDI messages.

[ToddStudio79]

I'm not sure how to do that but I'll give it a try.
You think the problem is with Reason?

I'll see what I can do

Thanks for the reply!

[DarkStar]

insertpizhere here does a MIDI Monitor VST:
https://www.thepiz.org/plugins/?p=midiMonitor

Or, you could create a MIDI clip with notes on various channels and see if ST3 will play all of them.

[ToddStudio79]

Tried every variation
Piz wont work in Reason 10

[zzz00m]

If the MIDI channel selection works in standalone mode, but not in Reason, that implies that Reason (the host) is controlling the MIDI channel sent to the plugin.

I don't use Reason, but in Studio One I can select the MIDI channel from the track inspector. The ST3 plugin in the instrument track responds on whatever channel I send it. Simple.

However, in Ableton Live an instrument track with ST3 only responds on channel 1, but if I create a separate MIDI track for my controller I can route that to any ST3 channel 1-16 on that instrument track. That MIDI track works like an effective MIDI switchboard that can translate any incoming MIDI channel from my controller to any outgoing MIDI channel to a plugin target, in this case ST3.

So in either case I can work with one instance of SampleTank in the DAW, and as many MIDI tracks as I need covering MIDI channels 1-16 as desired.

[DarkStar]

VST compatibility in Reason
• Reason 9.5 and later supports the VST 2.4 plugin format.
! VST 3 plugins are not supported.
• Both Windows and Mac VSTs are supported.
! Since Reason is a 64-bit application, only 64-bit VSTs are supported.
! Multitimbrality in VSTs is currently not supported - only one sound per VST can be played back at a time. If you are using a multitimbral VST it will only receive on MIDI Channel 1.

[zzz00m]

! Multitimbrality in VSTs is currently not supported - only one sound per VST can be played back at a time. If you are using a multitimbral VST it will only receive on MIDI Channel 1.

I have avoided Reason since the beginning of time simply because of the lack of VST support.

Appears that Reason has missed the boat completely with the recent VST update regarding multitimbral VSTs. So that also rules out Kontakt, Halion, Falcon, Omnisphere, etc.

[DarkStar]

Well, give them a chance

[zzz00m]

Well, give them a chance

Been giving them a chance for 17 years. Still waiting...

[synthesized1]

I really love Reason 10. Especially with the light nature of the program. The main think I like is that it doesn't crash every time there's a new update (which seems to happen every time there is a Cubase update).

But really, How hard would it be for them to add a midi channel to a selected track. Port assignment is there. Why not add Midi channel assignment. When copying track and device, just copying the track data if its the same VST being used. Dump the midi data but keep the VST. Then make the second track a different midi channel.

Kind of kills the whole purpose of a Multitimbral plug in like ST3 from being used.

I'm not a coder but it seems this shouldn't be that difficult of a task. Steinberg has this even on their watered down versions of Cubase (like Ai).