Hi all
Problems with thru voice again.

I seem to be constantly have problems with the Thru voice patch
Recently sorted 2 problems in BIAB 2017 now partially resolved.
Now problem in Realband 2017 build 4

In RB preferences / midi settings, you can choose thru patch to be track specific
This works fine and the Thru voice patch follows that of the selected midi track .
Therefore if you select the trumpet track to edit or work on you get a trumpet sound to work with great,
This works fine as long as you send the midi to an external synth.

Unfortunately if you reroute the midi in midi setting, to the default dxi/vst synth for playback. (even the simple coyote wave table). The thru voice no longer is track specific and defaults to the piano WHY????

Help frustrated
Mike

Edit silly me see below!!!!

Hi all

Ok after further test I have concluded that in fact the Thru voice never gets sent to the DXI / VST ever, only to what ever is connected to midi port 1 via the midi output dialogue.

I was able to do this by setting my midi output to a non synth midi device like my controller keyboard (this has no voices of its own but does appear as an output device)
From where I could pass it on should I want to..

Think I have finally got my head round what the THRU can and cant do,

Happy days
Mike

Hi Mike,

You might want to make wish list requests (two requests, one for RealBand and one for Band-in-a-Box) to have the thru channel user manual descriptions updated to more completely reflect what midi data is transmitted and to what internal or external ports the data is transmitted. You may want to reference the forum threads you've started so they will have a good idea why clarification is needed.

Today a midi port might physically be an ethernet, usb, five-pin, wi-fi or bluetooth connection. Also, it is common for a computer to have multiple midi ports. With all that in mind it is important for manual descriptions to be as complete and comprehensive as is possible.