default settings for zebra modules
-
- KVRer
- 12 posts since 31 Jan, 2010
to enhance my workflow with zebra I would like to ask if it's possible to save new default settings for modules such as reverb, shaper, chorus, comb 1, comb 2, so each time i load it it's ready to go with my favorite settings.
I've tried right clicking in a module, and choosing "make default" from the pop up menu. But it doesn't work. But maybe that function is only for the gui.
thanks if you have any ideas or suggestions.
I've tried right clicking in a module, and choosing "make default" from the pop up menu. But it doesn't work. But maybe that function is only for the gui.
thanks if you have any ideas or suggestions.
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
- open a fresh instance
- edit your settings as you like
- click save button
- put in "default" as name
After this you have a preset called "default.h2p" which should reside in the root preset directory. Each time you open a new Zebra it'll start out with just that preset.
Cheers,
Urs
- edit your settings as you like
- click save button
- put in "default" as name
After this you have a preset called "default.h2p" which should reside in the root preset directory. Each time you open a new Zebra it'll start out with just that preset.
Cheers,
-
- KVRer
- Topic Starter
- 12 posts since 31 Jan, 2010
thanks for that Urs, however i think that's not entirely what i mean.
Let's say i want "mod fx_1 chorus" to have my favorite setting. By saving them into the default( like you said)it helps when building sounds from scratch, but in case i want to add that specific modfx_1 chorus to already existing presets it loads a different chorus modfx_1 than the one saved in the default.
i hope that makes sense...
any ideas?
Let's say i want "mod fx_1 chorus" to have my favorite setting. By saving them into the default( like you said)it helps when building sounds from scratch, but in case i want to add that specific modfx_1 chorus to already existing presets it loads a different chorus modfx_1 than the one saved in the default.
i hope that makes sense...
any ideas?
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Ah, okay.
It is possible though.
1. Save a patch with your favourite ModFX1 setting and open it in a text editor (WordPad or TextEdit will do)
2. delete everything from the line that starts with #nm=32 up to the line that says #cm=ModFX1 (but you don't delete #cm=ModFX1!)
3. delete everything from #cm=ModFX2 to the end (including the ugly binary stuff, the ModFx don't need it)
Now you have isolated the ModFX settings within the presets. But a little cosmetical problem is left:
Somewhere at the beginning of the preset file, preferredly on a new line right after the meta information enclosed by /* and */ you need to add two lines:
#defaults=no
#patchname=no
Then, save as .h2p under a distinct new name (don't just overwrite the preset you just openend)
So what you get should look like this:
Now you can load it like a normal patch. It will only overwrite the ModFX1 settings and leave the rest untouched.
If you're using only like 3-5 settings, it's a bit of work but it's quickly done.
(if you want to load it on top of old presets from pre-2.5 era, delete "#Vers=20500" too)
Urs
It is possible though.
1. Save a patch with your favourite ModFX1 setting and open it in a text editor (WordPad or TextEdit will do)
2. delete everything from the line that starts with #nm=32 up to the line that says #cm=ModFX1 (but you don't delete #cm=ModFX1!)
3. delete everything from #cm=ModFX2 to the end (including the ugly binary stuff, the ModFx don't need it)
Now you have isolated the ModFX settings within the presets. But a little cosmetical problem is left:
Somewhere at the beginning of the preset file, preferredly on a new line right after the meta information enclosed by /* and */ you need to add two lines:
#defaults=no
#patchname=no
Then, save as .h2p under a distinct new name (don't just overwrite the preset you just openend)
So what you get should look like this:
Code: Select all
/*@meta
Author:
'somebody'
*/
#defaults=no
#patchname=no
#AM=Zebra2
#Vers=20500
#Endian=little
#cm=ModFX1
Mode=0
Cent=20.00
Sped=50.00
PhOff=50.00
Dpth=50.00
FeeB=0.00
Mix=0.00
LCut=0.00
HCut=100.00
Quad=0.00
Qphs=25.00
Leq=0.00
Heq=0.00
Q1=0.00
Q2=0.00
EQon=1If you're using only like 3-5 settings, it's a bit of work but it's quickly done.
(if you want to load it on top of old presets from pre-2.5 era, delete "#Vers=20500" too)
-
- KVRist
- 183 posts since 28 Jun, 2010
Hi Urs,
Wow, if you have all of this set up, it seems that a right click on a module could allow someone to save these out. Maybe it could make the long list
Best regards,
Gino
Wow, if you have all of this set up, it seems that a right click on a module could allow someone to save these out. Maybe it could make the long list
Best regards,
Gino
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Yep, that's entirely possible.Gino Cortesi wrote:Maybe it could make the long list
The main reason it's not there is that for stuff like Arpeggiator presets I need to do subsets of a module, but not the whole module. At the same time there needs to be a solution for a choice of subsets, such as "oscillator preset with waveform and all but without any tuning or modulation settings"
I've been mangling ideas in the back of my mind for years now. Not an easy task.
The best way I guess would be "whole module presets" and some educational material to customise these (as in my above post about extracting ModFX settings)
- Banned
- 6129 posts since 9 Oct, 2007 from an inharmonious society
