Hi all

I am at a loss
I can no longer seem to change my thru voice,
Its stuck on trumpet I’m sure it worked in 2016 and I thought I had done it in 2017 at least prior to the last update 456
I can hear the trumpet even with transport stopped so that seems to have been fixed.

But I cant select another patch if I say select Acoustic piano from the pull down menu in thru track the box disappears the text does not change .
I seem to remember in the past it did not show until you restarted the song again
But even this does not work and it still sits there on and plays trumpet.
Perplexed
Mike

Yes, that was a new feature in BIAB 2017 at user request.

I'll test the other problem.

Hi again

Thanks Mat I thought that was the case.
Still got the other problem though.

Some thing else odd going on as if I load a midi file into the melody track with the simple open command . it loads as a multi track multi channel midi in that track .
This is normal behaviour . I know,

The strange thing is that which ever instrument is on ch 5 of the midi in the melody track becomes my playable voice from my input keyboard and the thru trumpet no longer plays, that is once the transport is running and the song playing
.In fact once the transport has been run this voice holds even on stop,

I can clearly see this as the instrument on ch5 in the sequencer melody view,
This shows pizzicato strings on ch 5 and that’s what I get as my now playable voice not the through trumpet

As a point of interest
In Real Band everything works fine .
The selected mid track in a multi track midi plays its patch through to my selected midi synth output device,
So no problem here.


Your thoughts would be appreciated
Best regards
Mike

Mike, I think you are onto something. I created a new song then tried changing my MIDI patch on the Thru channel and could not. It's stuck on electric jazz guitar. The only clue I received occurred when I tried to use a patch from the higher banks (for my external Roland hardware synth) and I got an error message that this was a COMBO and I had to select a different patch for one of the first three tracks (including piano, bass). But that didn't work either.

I'm reporting this to the developers.

EDIT: I do have a workaround for you. Go to Preferences, Channels. You can see that the Thru Chn (bottom row) is on Channel 5 as you said. Now look at the third column (Patch), bottom row (Thru Chn). Change the number there to change the GM MIDI patch (1 = piano, 33 = acoustic bass, 57=trumpet etc.). The button marked "GM Patches" in the bottom left shows all the codes. That should hold.

Hi Mat
Thanks a million for your help I thought it was just me and have been going round in circles for days,
I will try your work around.
Just should say I am using the old GUI not that that should make any difference.
Best regards
Mike

OK. I'm using the new GUI. I only tried this via the mixer, which I believe I read from PG Music was now supposed to be identical in the old and new GUI, so you are correct - it should not make a difference.

HI Mat
Works a treat thank you so much I can work with that for now.
best regards
Mike

Hi Mike, a question if I may. Are you using an ASIO driver? I ask because several of us have reported this problem was not fixed, using asio4all or for the dedicated ASIO driver associated with the audio interface. This is under Win10x64, BB 2017.456, with "ASIO Always On" enabled, and with "Route Midi through to Midi driver" enabled. (The problem is NOT in RealBand with comparable settings.)

I'd assume you are using ASIO, because most people find the latency with MME prohibitive, but would appreciate if you could confirm. If there is sound under these circumstances, are you sure it originates from the softsynth and not a default synth on an internal sound card? (That possibility can be eliminated by making sure the Microsoft Wave Table synth is not selected in the Midi Output Driver pane of the MIDI/Audio Drivers Setup window.)

Thx, -Ron

BTW, I have that other problem too. I'm sure they'll fix it soon.

EDIT - Ah, I see you are on Win7x64. I suppose that could make a difference, not sure.

Hi RON

My Problem that I was dealing with at the time was not being able to change the Thru voice in the mixer,

So to eliminate the known driver problems with Asio 4 all, and dedicated Asio drivers , I switched to MME for the purpose of the above test on the forum.
..
As I said with the work around from Mat I can now change my thru Patch,

I was sending my Thru and all midi to my Yamaha CVP405 Clavinova Hardware and needed to be able to change the thru patch to play along as a choir patch 53 gm
Obviously I was working with an all midi style and drums,
Latency was not an issue as I was using hardware.

I do agree MME is a pain to have to use all the time ,and does give me latency when using soft synths or virtual midi synths like coolsoft and a sound font.

ASIO 4 all has is limitations as well as it is only a wrapper and also, only allows one instance in use at any time.

Will do some test later and let you know

Best regards
Mike

Hi All

I am pleased to say that this problem has been fixed in build 457
Although it is not listed in the fixes list.
Great to have it working again from the mixer Thru track window’
Thanks guys
Mike

Great!

Good to hear, as changing the thru voice is a pretty important feature.

I'm thankful too that the mixer's midi thru assignment is fixed.

BUT unfortunately, the issue I mentioned above is not fixed in BB2017.457. Still can not trigger the default soft synth via Midi Thru using ASIO driver with transport stopped. I don't understand why this is so hard to fix when it works in RealBand, and it worked in BB2016.

-Ron

This really needs to be fixed. If I'm working out a part on the keyboard, I don't necessarily need the chord progression going, but I do want to hear the solo instrument. Once I work it out, then I'll hit either play or record, but I need to be able to hear the instrument without the accompaniment playing.

If I have ASIO always active, then it should be able to process what is coming through the Thru track, whether the song is playing or not. What makes it different just because I hit "play" or "record"? Seems this should be a simple fix.

And going to MME is not an option because of latency.