John Darrow

2 minutes ago, msmcleod said:

Maybe it's a Windows UWP issue

I think it is. Strange that I only see incorrect PC messages. Everything else behaved as expected.

I FOUND THE FIX!!!

The bug went away when I changed the  MIDI Driver Mode to MME (in MIDI Playback and Recording preferences). It was previously set to UWP.

I don't know why this fixes it. Does anyone else see this problem?

Many thanks for everyone's contributions. 

11 hours ago, sjoens said:

S7 = Sonar 7.

If both S7 & CbB projects are set up exactly the same using the same .mid file with different results, wouldn't one conclude the 2 programs are handing things differently?

Yes. This exactly describes my experience. Identical files, two different results.

11 hours ago, msmcleod said:

Ok, it's as I suspected.  The track's MIDI Program change is being sent out as well as the one in the MIDI clip.

Setting the Track's MIDI Program change to none fixes the issue:

 

Not for me.  I know that the PC message is sent out twice but each time 2 messages are sent out on my system, 4 in total. The second and fourth messages are always PC 0

I saved my file as a MIDI file and looked at it in hexadecimal. The doubled PC message is not in the file.

6 minutes ago, Kurre said:

Could it be a virtual midicable active and interfering somehow?

That did cross my mind but as far as I know there are none active.

56 minutes ago, chris.r said:

I'm right now going through the ugly covid.

Sorry to hear that Chris. I just had the jab, thankfully. 

I get the same results that you see except for the addition PC message. All PC messages are always immediately followed by C0 00 (PC message patch 0). I never see a single message.

3 hours ago, msmcleod said:

@John Darrow - can you PM me a copy of your project so we can take a look?

 I started with a blank project, adding a single MIDI track and no midi data. The file below was made like that. Clicking on a patch name in the header sends the two PC messages. Inserting a single PC event using INSERT : Bank/Patch change  from the menu gives the same result. It appears as one event in the list but two are transmitted. All of my external hardware is disconnected. If I capture the raw data via MIDI-OX it receives C0 0B ,  C0 00

I really appreciate your efforts to assist me. I now think that I have an unusual installation problem and you will not be able to duplicate it. I have tried uninstalling/reinstalling. Next I will try a complete uninstall, removing registry entries.

MidiPCTest.cwp

9 hours ago, John Vere said:

What happens when you delete that Normal from the event list. My guess is it will now work. I've never used that event. You set the Bank to NONE in the inspector. Choose a patch and it should work. Works for me on Yamaha, Roland and Korg outboard synths. 

Unfortunately it doesn't make any difference.

It cannot be ins file related. The format of the message that is sent is incorrect with any ins I have tried, including the default general midi file. Also, as I said before, the message is correct when sent from Sonar 7 using the same default general midi ins file.

What is the S7 project?

16 minutes ago, chris.r said:

So when you change the bank select method then you're getting the correct vibraphone patch but with the bank data added, followed by the phantom piano PC? Is that one also coming with bank data? I started wondering if there is any sort of a MIDI loopback in your setup? 

Same as in my original post but preceded by the bank bytes. No bank data before the ‘phantom’ piano PC.

2 hours ago, John Vere said:

Just looking at your screen shot 

Is it the vibraphone patch you wanted?  
And what does the  “normal “ patch mean. It should be a number did you type that in?  So what I’m seeing is 2 conflicting PG messages. 
 

‘Normal’ send the message without bank data. Choosing other bank methods sends bank data (msb,  lsb) before the PC message. The vibraphone patch is what I expected but it is immediately followed by Patch 0, ( acoustic piano).

Both PC messages have exactly the same time stamp. It could be that 2 data bytes are sent instead of 1, with the second byte always zero. I haven’t checked to see if the entire message is repeated or just an additional data byte. Midi-ox doesn’t show the raw data.

There is no other track. I opened a new,  empty project, create only a midi track and then output a single PC message.

If I delete the entire clip so that there are no events in the event list and then I change the patch via the header, the same thing happens - 2 PC messages. Very strange. I beginning to think that I may have an installation problem. I uninstalled and reinstalled but it hasn’t fixed it.

Thanks for your reply. Everything looks normal to me. BL is definitely sending MIDI messages C0 0B (PC: Vibraphone) followed by C0 00 (PC Acc. Grand Piano)

There seems to be a bug with the MIDI program change message in Bandlab. I have a MIDI  .cwp file that works correctly with my old copy of SONAR 7 but it doesn't work with Bandlab. Both use the same default general midi .ins file.

I checked the MIDI being sent to my external synth using MIDI-OX. Bandlab sends an extra PC message, C0 00. This causes the program change to be overridden and always changed to the first patch. SONAR sends the message correctly.