I found another way to handle the volume spike. Have the pedal always on, and create a patch that has the filter wide open in dry mode, all other sounds off. That way regardless of the sounds you make, they are loud! So far its working well for me.
Enjoy the benefits of a premium membership!
Upgrade Account
-
TalkBass has been independent since 1998. Add your voice.
Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
Join free Log in
Want zero display ads or expanded classifieds tools? Compare plans.
Meris Enzo Synth Pedal
- Thread starter Phagor
- Start date
-
- Tags
- synth pedal
I found another way to handle the volume spike. Have the pedal always on, and create a patch that has the filter wide open in dry mode, all other sounds off. That way regardless of the sounds you make, they are loud! So far its working well for me.
Has anyone seen this thread? It hasn't had any replies... any thoughts?
Editor and Librarian for Meris Enzo
Editor and Librarian for Meris Enzo
I’m happy to answer any questions.
I’m going to shoot some short videos soon, to demonstrate the software.
Here is a brief overview of the editor librarian:
Available for free:
ElliotGarbus/Enzo-Editor-and-Librarian
Available for free:
ElliotGarbus/Enzo-Editor-and-Librarian
Kind of after the honeymoon, but I'm giving up on my Enzo. I got it on the hype because it promised to be just what I'd been looking for. But after six months on the board, it's not making it.
Pros: It's a fine, sensitive, compact assemblage of electronics. People who enjoy tweaking parameters just-so can have a field day with it.
Cons: It's sort of nerdy, and certainly impractical for the live player who would rather have some usable sounds available outright, or at least editable/recallable without having to invest in and learn complex extra gear.
I can see myself using the Enzo on home recordings, where you have tweaking time. Not saying I've yet explored the very depths of it, but it's a little thin-sounding, and seems better suited to guitar.
It looks like Meris is not listening either, and the Enzo continues to be out of stock.
Pros: It's a fine, sensitive, compact assemblage of electronics. People who enjoy tweaking parameters just-so can have a field day with it.
Cons: It's sort of nerdy, and certainly impractical for the live player who would rather have some usable sounds available outright, or at least editable/recallable without having to invest in and learn complex extra gear.
I can see myself using the Enzo on home recordings, where you have tweaking time. Not saying I've yet explored the very depths of it, but it's a little thin-sounding, and seems better suited to guitar.
It looks like Meris is not listening either, and the Enzo continues to be out of stock.
- May 16, 2007
- 3,395
- 4,869
- Disclosures
- Volunteer developer/beta tester with Source Audio, Morningstar Engineering & MORTRIX
Yes, I'm concluding as much. For a live setup it would be the sensible option.
Quick! Sell it so some nerd can buy it and use it to its full potential!
+1^^ Exactly where I landed too i.e. the FI is, for me, easily the better option as a gigging bassist, for all the reasons you set out.
So I, for one, am appreciative of your candid earlier review, particularly as you had the Enzo for more than just 5 minutes before making your mind up.
I'd have to respectfully disagree about its live usefulness, with a caveat. If a few hours are spent getting the right presets into the pedal, it can be great for live work. It simply does some complex things that nothing else can do. That said, I spend 3 or 4 hours a night in front of my synths, so it's not a big deal to me. I do think the need for external gear for this is a drawback, but I think that's a drawback for all of the Meris pedals. That said, I have three Meris, now, and with the addition of the DAD qConnect, these three pedals are a force to be reckoned with. Unfortunately, you're looking at about 900 bucks, there.
This speaks to needing a community to share .syx files for presets. I barely have time to set up my Enzo, so setting up a community location will be hard, but I'm happy to contribute when there is one!
Perhaps @ElliotDG has plans for this?
I think that would be awesome, especially if @ElliotDG also does some progs for the other Meris pedals.
- May 16, 2007
- 3,395
- 4,869
- Disclosures
- Volunteer developer/beta tester with Source Audio, Morningstar Engineering & MORTRIX
I’ll happily do it if someone provides me with an Enzo on which to create patches.
I dunno I think it sounds like the EHX or the keeley might be it. Future Impact is also nerdy and requires HOURS of tweaking to get what you want. EHX and keeley are regular pedals w a few knobs that take expression for live sweeping.
Yeah, good suggestion, the EHX Monosynth is the least nerdy.
Enzo is such a cool tool. We have it laced throughout a song we are writing, and I'm finding so many ways to use it. At this point I don't care about presets because its so easy to navigate after those few hours with it.
If you aren't a synth nerd (meaning you don't understand how one of the most popular instruments in current music is used at a basic level) the learning curve is steep. It helps to know what an oscillator is, how filters work, and what poly, arp, mono and dry modes can do. Anyone can learn this pedal though, it just takes some patience.
Now that I'm messing around with the Enzo some more, I'm seeing how the volume spike can be an issue. I've read some people are putting a compressor after it. I don't normally use compression, but wouldn't mind getting one for this, as I use the Enzo a lot. Can anyone make a good recommendation for what kind of compressor would be good for this specific problem? Looking for the simplest kind, preferably in a mini format.
@lordradish I suggest turning down the resonance, or what Meris calls filter bandwidth, on the patches with the volume issues. This is the alt function on the filter env knob. This will really help address the problem.
I don't have any plans to create a community for Meris patches. Seems like the natural choices would be to do it here, or VGuitar Forums - Index or perhaps Meris could host a site.
My plans right now are to get a Mac port done of the Enzo editor, I have a friend helping with that, but it is going slow. I may just break down and buy a mac to get it done.
In parallel, I'm working on new features to automatically create patches. My current idea, the synth mode and mix mode are set manually, all other parameters are set by the patch generator.
There will be a number of different patch generator modes. A random mode, that just sets the parameters randomly, and a morph mode. In the morph mode the user selects any 2 patches from the library and the patch generator will create variations of patches between these 2 patch settings.
The UI will allow the user to select an interval in seconds, and at every interval, a new patch would be generated. This would allow hands free evaluation of dynamically generated patches. If you like a patch hit stop and save it into the library.
I'm currently experimenting with the morph algorithms, looking to get the most useful variations and eliminate patches that don't make a sounds (Low pass filter with cutoff at zero), and thinking about how to keep the ui simple.
I'd appreciate any feedback on the patch generator concept.
I don't have any plans to create a community for Meris patches. Seems like the natural choices would be to do it here, or VGuitar Forums - Index or perhaps Meris could host a site.
My plans right now are to get a Mac port done of the Enzo editor, I have a friend helping with that, but it is going slow. I may just break down and buy a mac to get it done.
In parallel, I'm working on new features to automatically create patches. My current idea, the synth mode and mix mode are set manually, all other parameters are set by the patch generator.
There will be a number of different patch generator modes. A random mode, that just sets the parameters randomly, and a morph mode. In the morph mode the user selects any 2 patches from the library and the patch generator will create variations of patches between these 2 patch settings.
The UI will allow the user to select an interval in seconds, and at every interval, a new patch would be generated. This would allow hands free evaluation of dynamically generated patches. If you like a patch hit stop and save it into the library.
I'm currently experimenting with the morph algorithms, looking to get the most useful variations and eliminate patches that don't make a sounds (Low pass filter with cutoff at zero), and thinking about how to keep the ui simple.
I'd appreciate any feedback on the patch generator concept.
Being able to take two patches, and make them the heel and toe settings for the expression control would be a really cool feature!
While porting to Mac, if possible, please consider the older versions of OS. 10.9, even snow leopard is used. These old Macs are built well and keep working!
Edit: Being able to bundle a patch with some global options would be useful as well - essentially making the global options that can be changed on the fly incorporated in a way that makes them per patch...
@Alien8 I like your idea of merging patches to create the toe-up and toe-down settings. Very nice!
For storing global data with the patch, this could only work when setting the patch from the editor. The Enzo does not have this capability. Additionally, I could NOT do it for Trails or split. Unfortunately these can not be set from MIDI - and I think Trails and split are the setting that would be the most useful.
For storing global data with the patch, this could only work when setting the patch from the editor. The Enzo does not have this capability. Additionally, I could NOT do it for Trails or split. Unfortunately these can not be set from MIDI - and I think Trails and split are the setting that would be the most useful.
Regarding trails & split: Bah! Meris logic strikes again! That would be the one I would love to flip around.
