Global midi map not remembered

Nobody got any ideas about getting Pianoteq to recall a personalised global midi map at startup?

I've just tried overwriting the Minimalistic map with my version and it's not possible sadly.

One thing which can make your custom MIDI file NOT load, is if it contains a parameter which is "invalid". "I swear that I loaded the file!" - yes, I did, but it contained an error - it won't load until the error is cleared.

Got me caught a few times. Just scroll down the interface looking for that word and change value to something recognised. Not saying it's def the problem you're having but it could be.

There's is of course more..

Posted recently about how to save your MIDI setups in Pianoteq.

You can save your MIDI custom files as "G" (of course, global by default), or by clicking on the G, you then see "P" (just per preset).

Look for the little G icon in the left side of the interface (eg. lines beginning with 'controller' 'pitch bend') when saving out your custom MIDI file.

If you save a custom MIDI file by clicking the G so it becomes P, then it will load automatically any time you switch over to that preset.

There's some detail in that above link.

To solve A/B testing issues, I always right-click the save icon and 'save as' a new preset. This allows me latitude for loading custom MIDI (IF I want to A/B that - otherwise, it doesn't matter 99.999%). If working A/B on exact same preset, it will only allow the custom MIDI you saved to work (if you set custom MIDI, save "P" style, use as A, then also use same preset for B, then when you edit B's MIDI but don't save it to preset, of course the A's saved MIDI will load when A/B between the two. Again, solved by saving "P" style only (forget global defaults unless you know you want that).. then you save a clone to work on as your B

So, best thing to do IMO to cover all bases, is save "P" per preset.

Sure make a global sane one by all means if it's useful, and/or just keep using the existing global one for startup (probably what most will benefit from). On all pianos you use and want your MIDI file, just load your MIDI file and save the preset while it's loaded in

Pianoteq will just go ahead and load the default - then make additions/subtractions in MIDI which exist now for your preset. Great if you want your Harp set up like a piano (pedals etc).. you never have to again flop around looking for files to load. Make your change (pedal up instead of down etc) and it's attached to the preset. If there's another preset you want to attach those changes to, come to that bridge and cross it by loading your file and saving that preset.

It's more work - but if you only need one global file, go that way. Caveat, if you're altering MIDI setups for different environments, chances are trying to have a selection of different global files might end up just as, or more work.

I've tested around all the above etc.. but if I'm mistaken - always love to learn - feel free to let me know.

Thanks. It loads okay, just not automatically by default. It was most annoying when I was A/B'ing demo instruments and having to do it manually every time I restarted Pianoteq (every 20 minutes) when I was working out which other instrument I was going to buy alongside the Bechstein earlier in the week!

I tried it both with appending something with an underscore and also just giving the new map a single word name. Both times it loads fine manually but isn't recalled at restart, despite clicking "Set as default".

Many thanks for that tip, I'd never spotted the G or P before. Sadly, that's not the issue :-( The controller mapping I've added for the A/B switch is set as G, part of the global midi map I wish to set as default.

At the moment, the only thing I've added is the ability to A/B from my controller, modwheel on my Keystation or one of the X/Y levers on the SL88 grand, both work fine with the same addition to the Minimalistic map, CC 1, v= 0, flick back and forth once to switch. This is so I can either quickly switch with a minimum of effort between two different acoustic pianos, or have for instance an acoustic on layer A and a Rhodes on layer B when I'm writing and not have to get into changing midi channels.

I think a single global map is all I need, at the moment anyway. I might get into P-level mapping later but I can't see any personal need at the moment. And this is the problem, either Pianoteq isn't "just go[ing] ahead and load[ing] the default", or it's not correctly setting the map I've just loaded manually as the default to load automatically next time I start the software. I've just noticed that it even appends "(default)" to the map name when I've selected it as the default, but when I restart, there's the Minimalistic one again (which, oddly, never says it's the default).

Interesting Gilles - just updated my Linux install to the current Pianoteq ver. and it works as intended/described - as did also my old Pianoteq version 5 before updating.

@Jorvik, thanks for extra data and sorry it didn't help straight up. Not knowing what you've attempted already..

Is it possible to update to the latest Pianoteq version 6.4.1 (just noticed it's superseded 6.4.0) - on the chance it alights you of the issue.

2 other quick ideas..

#1

Maybe chmod the file's permissions to 644 (or directory and below).

#2

or add yourself to 'audio' group? (some will prefer this - arguably safer and may similarly fix the same issue across all audio apps).

Also, maybe search online for similar things to:

"set Linux audio permissions"
"custom MIDI permissions audio"
"load MIDI custom file fail Linux"

(try subst. your distro name for the keyword linux)

do those kinds of searches online in your search engine of choice or at your distro's forum.

It may be something rare (maybe rel. Jack/Alsa/Pulse too?) but hopefully! those 2 above could do it though if not already tried.

#2 seems most preferred and arguably safer and Pianoteq may be able to open that file without user intervention after that - anyway just my instinct - could be wrong on both counts.

If you're happy to post more data here, knowing some more of those details might spark a few more sculpted solutions from those with more Pianoteq experience in Linux than myself.

Hope you get it singing soon - keep us posted.