Hi, I have put 2 different presets in A/B switch (Pianoteq 8), 1 for A and 1 for B, it works as expected in manual mode (with the mouse) but seems not to save when I re-open my Mainstage or Logic project where I now can see the same preset in A and B and the icon beside shows now = and no longer ≠ after saving.
Any ideas ?
Thanks for help,
Dan
Maybe it's a general DAW issue. I can't seem to get the A/B state to save in Reaper, either (on the next opening it just defaults to the preset which was active on the last save).
Maybe it's a general DAW issue. I can't seem to get the A/B state to save in Reaper, either (on the next opening it just defaults to the preset which was active on the last save).
I think it's a Pianoteq plugin issue, can someone confirm ?
Thanks
I think it's a Pianoteq plugin issue, can someone confirm ?
Thanks
Pianoteq saves only the current state (A or B) when saving a project in a DAW, not the whole A/B state.
Dan_ wrote:I think it's a Pianoteq plugin issue, can someone confirm ?
ThanksPianoteq saves only the current state (A or B) when saving a project in a DAW, not the whole A/B state.
Wow, scaring when you think that 99,99 % of people work with DAW no ?
julien wrote:Dan_ wrote:I think it's a Pianoteq plugin issue, can someone confirm ?
ThanksPianoteq saves only the current state (A or B) when saving a project in a DAW, not the whole A/B state.
Wow, scaring when you think that 99,99 % of people work with DAW no ?
Modartt are bound to sort this in a future update.
Not at all scary. I don't suppose this is how most people make patches in Pianoteq. I know it's there but I have never used the a/b function either in the standalone or within the DAW and I've made lots of presets.
I keep saving a preset in development without ever having to compare to the old preset.
Dan_ wrote:julien wrote:Pianoteq saves only the current state (A or B) when saving a project in a DAW, not the whole A/B state.
Wow, scaring when you think that 99,99 % of people work with DAW no ?
Modartt are bound to sort this in a future update.
Not at all scary. I don't suppose this is how most people make patches in Pianoteq. I know it's there but I have never used the a/b function either in the standalone or within the DAW and I've made lots of presets.
I keep saving a preset in development without ever having to compare to the old preset.
I use Pianoteq for live purpose in Mainstage and need to change presets on the fly, so...
..
I use Pianoteq for live purpose in Mainstage and need to change presets on the fly, so...
Okay, that's an unusual use for the preset comparison function. I think we can do much better.
So if you only want two sounds why not have two sounds on two different MIDI channels?
That way you could have a switch on your keyboard that changes midi channels, or alternatively have two (or more) keyboards with different instruments on them. These days Pianoteq allows up to three different instruments simultaneously on different midi channels.
Dan_ wrote:..
I use Pianoteq for live purpose in Mainstage and need to change presets on the fly, so...Okay, that's an unusual use for the preset comparison function. I think we can do much better.
So if you only want two sounds why not have two sounds on two different MIDI channels?
That way you could have a switch on your keyboard that changes midi channels, or alternatively have two (or more) keyboards with different instruments on them. These days Pianoteq allows up to three different instruments simultaneously on different midi channels.
That's an idea indeed, but not as fast as programming a CC with this feature of A/B :-)