patch name BUG in Zebra ?
-
- KVRist
- 208 posts since 8 Aug, 2010 from London, UK
I have 6 instances of zebra running 6 edited versions of an original patch. I saved those edits and renamed them, but here's the problem. Every time I open the GUI of a saved edited version, the patch has changed back to the original. What the hell is going on here ?
Last edited by iamyourfather on Mon Jun 25, 2012 11:29 am, edited 2 times in total.
-
- KVRist
- Topic Starter
- 208 posts since 8 Aug, 2010 from London, UK
I have even deleted the original from the folder and it still loads even tho it does not exist anymore... I am seriously confused here
-
- KVRist
- Topic Starter
- 208 posts since 8 Aug, 2010 from London, UK
It seems to be just the name that is bugged, the sound remains the edited version, so while it's not a total disaster, it does make life very difficult navigating between 6 different version that all have the same WRONG name.
-
- KVRAF
- 1617 posts since 11 Dec, 2008 from Minneapolis
Just a stab at it, could be on the wrong track -
What host? It sounds like when you're opening the GUI it's actually opening a host's saved version of Zebra, which will capture a very live snapshot of Zebra including the patch name, even if no actual patch still exists with that name.
What host? It sounds like when you're opening the GUI it's actually opening a host's saved version of Zebra, which will capture a very live snapshot of Zebra including the patch name, even if no actual patch still exists with that name.
-
- KVRist
- Topic Starter
- 208 posts since 8 Aug, 2010 from London, UK
it's reaper, but I thought of that and tried it in a clean project, closed the gui and reopened and the name had changed. So it must be somewhere in the H2p file. Maybe it got bugged on a save and has the wrong patch name or something, I'd look at it myself, but have no idea what to look for.xh3rv wrote:Just a stab at it, could be on the wrong track -
What host? It sounds like when you're opening the GUI it's actually opening a host's saved version of Zebra, which will capture a very live snapshot of Zebra including the patch name, even if no actual patch still exists with that name.
-
- KVRist
- Topic Starter
- 208 posts since 8 Aug, 2010 from London, UK
I think I may be onto something.
My original patch is named "tekno bass sustain 6" and the edit versions "tekno bass sustain 6.0" "tekno bass sustain 6.1" etc. I wondered if the point was something to do with it and renamed it to "test name" and the problem is gone.
So it seems that using an X.y naming convention causes this.
*waits for someone to mention that everyone knows this already and it in the manual*
My original patch is named "tekno bass sustain 6" and the edit versions "tekno bass sustain 6.0" "tekno bass sustain 6.1" etc. I wondered if the point was something to do with it and renamed it to "test name" and the problem is gone.
So it seems that using an X.y naming convention causes this.
*waits for someone to mention that everyone knows this already and it in the manual*
-
- KVRAF
- 4141 posts since 11 Aug, 2006 from Texas
It's news to me. I tend to use just "00...15" at the end separated by a space for variations. Or I use something like -long tail, -grit, -closedfilter at the end.iamyourfather wrote:*waits for someone to mention that everyone knows this already and it in the manual*
Period is probably one of the symbols that should be auto-converted to '_' like ":" and a few others.
-
- u-he
- 30189 posts since 8 Aug, 2002 from Berlin
Your saving with the "backup and save" option which renames the existing preset to the next avaiable number counting up. Then the current preset is replaced.iamyourfather wrote:I think I may be onto something.
My original patch is named "tekno bass sustain 6" and the edit versions "tekno bass sustain 6.0" "tekno bass sustain 6.1" etc. I wondered if the point was something to do with it and renamed it to "test name" and the problem is gone.
So it seems that using an X.y naming convention causes this.
*waits for someone to mention that everyone knows this already and it in the manual*
The song/project file stores the preset name and Zebra thinks that the newly save file is still the very first one when you open the browser, even though it has changed and is now called PresetFile.1.h2p
-
- KVRist
- Topic Starter
- 208 posts since 8 Aug, 2010 from London, UK
You've lost me a bit there, I saved them as new patches with the .1 .2 naming convention, it sounds like you are saying that's what back up and save does and I've accidentally copied it's naming convention with my new saves making them appear as backups ?
-
- u-he
- 30189 posts since 8 Aug, 2002 from Berlin
Ah. ok... sorry...iamyourfather wrote:You've lost me a bit there, I saved them as new patches with the .1 .2 naming convention, it sounds like you are saying that's what back up and save does and I've accidentally copied it's naming convention with my new saves making them appear as backups ?
-
- KVRist
- Topic Starter
- 208 posts since 8 Aug, 2010 from London, UK
So in other words, don't use an X.1 X.2 naming convention then ?Urs wrote:Ah. ok... sorry...iamyourfather wrote:You've lost me a bit there, I saved them as new patches with the .1 .2 naming convention, it sounds like you are saying that's what back up and save does and I've accidentally copied it's naming convention with my new saves making them appear as backups ?