Zebra - Presets\Program Changes need DAW reboot for recall

[gwok]

hey, I don't know if anyone has noticed this, but changed\saved presets don't get recalled properly by program changes unitll the DAW your working has been rebooted.

This is extremely difficult to work with to say the least, if one is using program changes for anything beyond rudimentary use. Planning to use Zebra for a live dance set, but having to reconsider, as working on synth patches\mixs is almost impossible, as it takes rebooting Ableton constantly to hear proper playback between different sections of songs.

Really hoping this can be fixed!!

thanks

g

[xh3rv]

It should only take reloading the plug-in, this does mean every instance of Zebra has to be removed from the set however - not sure if that's intended or not.

The reason it works this way - Zebra reads MIDI programs from a copy of the folder that's loaded into RAM when Zebra is loaded. This means the hard drive never has to be accessed from a MIDI program load, as spinning up the HD can be too slow to keep up with MIDI.

[gwok]

It should only take reloading the plug-in, this does mean every instance of Zebra has to be removed from the set however - not sure if that's intended or not.

Thanks for the response, though even if what you say did work (which it doesn't I'm pretty sure - on osx anway), I dont think I could fathom doing that everytime I tweaked a patch - losing cc assignment, automation etc etc. As well having to delete every other Zebra in the project to do it! LOL - no way

The reason it works this way - Zebra reads MIDI programs from a copy of the folder that's loaded into RAM when Zebra is loaded. This means the hard drive never has to be accessed from a MIDI program load, as spinning up the HD can be too slow to keep up with MIDI.

Still, I don't see why there couldn't be a command to flush and update the RAM. Then it would still not be reading from the HDD, but updates would be accessable.

g

[Urs]

Yep, that's true. The first instance of Zebra stores compressed versions of the MIDI programs in memory, which can then change instantaneously, i.e. without accessing the hard drive from a timer.

We're however evaluating a timer based solution, or a solution that allows for rescanning the MIDI Programs.

[xh3rv]

Thanks for the response, though even if what you say did work (which it doesn't I'm pretty sure - on osx anway)

I tested it on Live / OS X before posting just to make sure, seemed fine here as long as every instance got removed Sounds like it might not quite match your workflow anyway ... Urs's ideas certainly would!

[gwok]

We're however evaluating a timer based solution, or a solution that allows for rescanning the MIDI Programs.

great! so glad to hear that.

k"]

I tested it on Live / OS X before posting just to make sure, seemed fine here as long as every instance got removed Sounds like it might not quite match your workflow anyway ... Urs's ideas certainly would!

maybe so, thought I tested that as well, though maybe I had a lurking zebra I wasn't aware of

g

[Urs]

Some hosts might keep a hidden instance open, I don't know. I sometimes have the suspicion that some hosts don't unload the binary when the last instance is closed... dunno...

[tryptaform]

I would also very much appreciate being able to recall a program change without rebooting the DAW. One solution you might like to consider would be to reload the program change bank into ram every time a patch is saved (or a patch saved to the midi programs folder). This way it wouldn't be on a timer (and getting reloaded while performing) and then you also wouldn't have to press a button to reload the bank.

cheers
Keith

[SaganTech]

My idea for this was similar as I don't know why you need a timer to do this. There is already a function in Diva/Zebra and ACE whereby you right-click on the folder list in the patch(es) tab and select 'refresh folder list'. It would make sense to me that refreshing the folder list would also refresh the MIDI program change list.

[gwok]

just wondering if there is a fix for this on the horizon?

[Urs]

just wondering if there is a fix for this on the horizon?

I'm still on vacation and now Clemens is out of office too. Hence I haven't been able to check into this at all.

There won't be any quick fix I'm afraid, any workaround involves a whole beta testing cycle along with other features, additions and changes. We hope to release an update to Zebra around July 2012, but that also depends on the time we need to get some other pressing matters sorted.