Cakewalk delete Patch Change whwn saving

[Jan Iversen]

When I save a midi file after making various corrections, Cakewalk deletes the Program Change in the Event list.
Anyone have an explanation?
See attached video
/Jan

[Jan Iversen]

In fact it delete th Control CC7 and CC10 Pan too.

[57Gregy]

I'm not completely familiar with what data is saved in a .mid file, but maybe those CCs are not included.
Sounds ridiculous, I know.
I don't even know how I can check it.
Sorry.

[David Baay]

When you open a .MID file, Sonar will read any initial program change, CC7 and CC10 messages into the Bank, Patch, Volume and Pan controls in the track and remove them from the MIDI sequence. I you save as a normal project, that situation will persist - i.e. Sonar will contue to store those initial values as track control settings. But if you subsequently re-save as a MIDI file, those values will be written back into the file.

[Jan Iversen]

8 hours ago, David Baay said:

Når du åbner en .MID-fil, læser Sonar alle initiale programændringer, CC7- og CC10-meddelelser ind i Bank-, Patch-, Volume- og Pan-kontrollerne i sporet og fjerner dem fra MIDI-sekvensen. Hvis du gemmer som et normalt projekt, vil denne situation fortsætte - dvs. Sonar vil fortsætte med at gemme disse startværdier som sporkontrolindstillinger. Men hvis du efterfølgende gemmer igen som en MIDI-fil, vil disse værdier blive skrevet tilbage i filen.

Hi
Maybe I don't quite understand.
I always save as .mid format 1 as the file needs to be loaded into my Yamaha Keyboard which doesn't understand other formats.
Could you please elaborate a bit 🙂
/Jan

[Promidi]

I use patch change events all the time for my outboard Yamaha gear (SW1000XG). 

The majority of my client projects are saved as MIDI file (can be type 0 or 1) 

I never have any issues with Patch change Events in MIDI files with Sonar.

I make sure any MIDI tracks have the initial patch set in the MIDI track’s inspector.  Any subsequent patch changes are in the track itself (if required).

When a MIDI file is loaded into Sonar, it processes each MIDI track as follows. The first Patch Change event encountered in a given track gets placed into the MIDI track’s inspector and removed from the track.  Any subsequent Patch Change events in the MIDI track does not change.  This occurs for type 0 and type 1 MIDI files. (I tested this).