[solved!] DP 11.11 not saving prg changes via Patch List

[peter]

Hi,

when I use [CMD + W] to only close the song I'm working on, everything is fine when I open it again. The Patch List I created with Cherry Picker (thanks again CharlzS for recommending) will show up in all the right places and DP is sending the expected patch changes to my HW-Synth.

Whenever I quit DP completely with [CMD + Q] and then load the song the PATCH field in Track view will be empty and DP doesn't send patch changes. It happens every single time, so whatever is going on there can be reproduced.

Any ideas on this?

Thanks for helping.

[CharlzS]

Insert the patch change at the beginning of the track in the Sequence Editor. Then in 'Event Chasing' make sure patch changes are chased.

[peter]

Thanks CharlzS, will try. Where do I find the settings for event chasing?

[peter]

Ok I rtfm and found it. Thanks for your help, appreciated!

[peter]

Still the question remains: why is DP behaving like this? What exactly is the function behind the "patch" entry in Track View or Sequenz View? Why does DP behave differently depending on how I close the program / song?

Any ideas? Not nitpicking, I love DP, just trying to understand what's going on.

[CharlzS]

Still the question remains: why is DP behaving like this? What exactly is the function behind the "patch" entry in Track View or Sequenz View? Why does DP behave differently depending on how I close the program / song?

Any ideas? Not nitpicking, I love DP, just trying to understand what's going on.

Maybe tech support is the way to go on your questions. As far as I can remember, I have put patch changes in the SE along with track automation. Why, I don't remember, but maybe similar problem to what you're experiencing. I have the Patch and Default Patch columns hidden in the Tracks Overview, so they're not ever considered.

[peter]

Alright, thank you for your help!

[peter]

Bevor I consult tech support: Could someone please test and confirm?

[James Steele]

First of all, Cherry Picker is unsupported. The only reason we have Version 3 is that I personally reached out and contacted the author to ask to to release that version, which he had no plans to release because the app generated certain errors that end users won't see and I don't think he just didn't want to deal with fixing it or having to support it. So with the understanding that it was UNSUPPORTED and you use at your own risk, he allowed me to host the download here.

That said, I believe that what might be happening is that if your custom patch list isn't showing up consistently, it may be that you didn't assign designate which MIDI instrument that patchlist would be assigned to within Cherry Picker. And as I said, Cherry Picker is a little bit squirrelly and you might have to fumble around through it and try things multiple times. Just like the original author, I have no desire to be technical support for the app either, so I'm just throwing that out there as a potential suggestion/solution.

Cherry Picker is pretty much abandonware and the understanding all along with the author is that he'd release it, but you're on your own.

[bayswater]

If you have a small number of patches you need to keep, you might consider recording the sysex data for them. E.g. you could set up a template, put a MIDI track into record, and set the synth to send the patch change info as it would to any sysex recording. You could put each patch on a separate track, or just put them all in one track, each in a clip. Mute the track. Save it with the template. When you open the template, you can unmute the track and play the sysex clips you need to set up the synth, or copy the clips you want to the start of the MIDI track that will play the patch.

I used to do this with a K2000 that had the usual 200 factory patches, and another 100 that I made. It was a bit tedious recording them at the start but after that it’s quite easy.

[CharlzS]

James, I don't think this was a criticism of Cherry Picker. The OP's problem with the patch list was solved by Cherry Picker. The gripe was with the way the default patch in the Tracks Overview was handled in DP.

[peter]

James, I don't think this was a criticism of Cherry Picker. The OP's problem with the patch list was solved by Cherry Picker. The gripe was with the way the default patch in the Tracks Overview was handled in DP.

What more can I say? Yes CharlzS, you're right.

@JamesSteele: Thank you for making it possible that we can have this tool here on MOTUnation, which does exactly what I want it to. And thank you for providing some hints for narrowing down the problem, but my problem is not with Cherry Picker. It's not the end of the world, I will try to figure out what's going on there.

[peter]

If you have a small number of patches you need to keep, you might consider recording the sysex data for them. ...

Thanks bayswater for your suggestion. The unit we're talking about doesn't send sysex, and it is also a box full of presets which, apart of some RPNs and NRPNs, cannot be changed much. So all I need is some regular Patch Change commands. I will cross check DPs behaviour with some of my other synths, I'm sure I can narrow it down. Culprit - be warned!

Have fun

[bayswater]

Bonne chance Peter, and let us know what happens.

[peter]

Ok, I checked it with the Patch List for Rolands M-GS64 that comes with DP. The behaviour is exactly the same:

If I quit the song and leave DP open everything will be fine when I open the song again.

If I shut down DP completely and open the song again the Patch entry in Track View is empty.

So, what is this Patch entry in Track View supposed to do? Does it only *show* me the patch changes I have inserted in Sequence View - or should I be able to *change* patches in Track View while having NO patch changes inserted in SV?