Love all of your videos! I just added chorus to one of my mx presets but I remember I saw a video of yours on how to stack effects. Ie, add chorus and trem. Is it possible to do a deep dive on how to add various effects? I have both mx and lvx
Hey! So awesome you have both! So on each you can only choose 1 effect from each module. Chorus and Trem are both in the Modulation module on the MX (chorus and ring mod on the LVX). You’re best best is to choose a reverb or delay with mod in the reverb/delay and then add trem. Does that make sense?
I was really hopeful you were going to take them apart in this video to figure out if it's actually identical hardware, with just different firmware 😂Great video as always.
😂 😂 😂 if I had any confidence I could put them back together! I will say, you can’t load LVX presets into the MX so that must mean different hardware right?
@@thepedalcollaborative Not necessarily? The hardware could be interchangeable, the firmware is what governs the presets you can load. Think of it like loading a BitWig project into Reaper. Both runs on the same hardware, but they don't speak each other's project files. I'd say Meris would be smart to have the Mercury X and LVX be essentially identical devices running different software. Much cheaper to develop and produce, and all they would need to change is the enclosure and software running on the device. My money is on exactly this. From what I can tell the devices look identical other than the color? Same ports, same knobs/screen in the same places. I'm sure there is something in place to keep you from loading a Mercury X firmware onto the LVX, but I bet it's purely based in software on the device.
@RandoCalglitchian I was being a little facetious but thanks for humoring me. I agree with you in that the only difference externally is probably enclosure color. Inside is probably a software difference but I’d imagine hardware is the same
Hey, how's it going? If I'm interested in getting the MercuryX presets from your Patreon but I don't don't have MIDI or any other way to hook up the pedal to a computer - is there some way I can still get them? E.g. are all the settings noted down in text maybe?
100% agree! As long as I have the space on the board, I wouldn’t want to be without either! The overlap really frees you to add those effects modules wherever you want within the Meris ecosystem. Example being Chorus. Let’s say I’m playing it “simple” with a drive pedal, the LVX, and the MercuryX and nothing else. I cold essentially add chorus anywhere from right after the drive (in the LVX) to end of signal path after everything (in the MercuryX) and anywhere in between! Having both gives you loads of flexibility!
I've seen one of your videos before Nick where you claimed the Big Sky as your "forever reverb of choice". Still the case even with the flexibility of the MeecuryX? Would be interested in your perspective too pedalcollaborative? Do you see Big Sky as more a standard do-it-all reverb whereas the MercuryX is more of an experimental sound design tool akin to the LVX?
@sengi12 I agree with @nickrresyt for sure! One way I look at it is like this: the BigSky has 12 great algorithms that are easily accessible and you can get a lot of takes on those sounds with a few knobs and a 1 or 2 menu layers. The MX can do the vast majority of what the BigSky can do but requires some more finesse in dialing in as the amount of tweak ability is insane. You can definitely get classic sounds with ease but can also go absolutely crazy with them! If you want a powerful but easy verb, you can’t go wrong with the BigSky. But if you want to test the bounds of your reverb creativity, then MX all the way! 🙌
This was not very useful... of course the identically named software modules inside of two visually identical digital hardware devices are going to sound identical.
![Awesome Reverb Pedals For Guitar [Meris Mercury X, Poly Verbs, Boss RV-200 & EHX Oceans 3-Verb]](http://i.ytimg.com/vi/S1ysRSKg_20/mqdefault.jpg)
Love all of your videos! I just added chorus to one of my mx presets but I remember I saw a video of yours on how to stack effects. Ie, add chorus and trem. Is it possible to do a deep dive on how to add various effects? I have both mx and lvx
Hey! So awesome you have both! So on each you can only choose 1 effect from each module. Chorus and Trem are both in the Modulation module on the MX (chorus and ring mod on the LVX). You’re best best is to choose a reverb or delay with mod in the reverb/delay and then add trem. Does that make sense?
I was really hopeful you were going to take them apart in this video to figure out if it's actually identical hardware, with just different firmware 😂Great video as always.
😂 😂 😂 if I had any confidence I could put them back together!
I will say, you can’t load LVX presets into the MX so that must mean different hardware right?
@@thepedalcollaborative Not necessarily? The hardware could be interchangeable, the firmware is what governs the presets you can load. Think of it like loading a BitWig project into Reaper. Both runs on the same hardware, but they don't speak each other's project files.
I'd say Meris would be smart to have the Mercury X and LVX be essentially identical devices running different software. Much cheaper to develop and produce, and all they would need to change is the enclosure and software running on the device. My money is on exactly this. From what I can tell the devices look identical other than the color? Same ports, same knobs/screen in the same places.
I'm sure there is something in place to keep you from loading a Mercury X firmware onto the LVX, but I bet it's purely based in software on the device.
@RandoCalglitchian I was being a little facetious but thanks for humoring me. I agree with you in that the only difference externally is probably enclosure color. Inside is probably a software difference but I’d imagine hardware is the same
@@thepedalcollaborative 😅
😎
Hey, how's it going? If I'm interested in getting the MercuryX presets from your Patreon but I don't don't have MIDI or any other way to hook up the pedal to a computer - is there some way I can still get them? E.g. are all the settings noted down in text maybe?
Hey there! I don’t have them all written down, but I guess we could work that out out somehow. Email me at thepedalcollaborative @ gmail
Lots of crossover …lots. But imo more than enough individuality to make them ‘worth it’ and absolute powerhouses
100% agree! As long as I have the space on the board, I wouldn’t want to be without either!
The overlap really frees you to add those effects modules wherever you want within the Meris ecosystem. Example being Chorus. Let’s say I’m playing it “simple” with a drive pedal, the LVX, and the MercuryX and nothing else. I cold essentially add chorus anywhere from right after the drive (in the LVX) to end of signal path after everything (in the MercuryX) and anywhere in between!
Having both gives you loads of flexibility!
I've seen one of your videos before Nick where you claimed the Big Sky as your "forever reverb of choice". Still the case even with the flexibility of the MeecuryX? Would be interested in your perspective too pedalcollaborative? Do you see Big Sky as more a standard do-it-all reverb whereas the MercuryX is more of an experimental sound design tool akin to the LVX?
@@sengi12 exactly as you describe it yes. Either way you cut it the bigsky sounds fantastic and covers lots of ground. The Mx just does way more
@sengi12 I agree with @nickrresyt for sure!
One way I look at it is like this: the BigSky has 12 great algorithms that are easily accessible and you can get a lot of takes on those sounds with a few knobs and a 1 or 2 menu layers.
The MX can do the vast majority of what the BigSky can do but requires some more finesse in dialing in as the amount of tweak ability is insane. You can definitely get classic sounds with ease but can also go absolutely crazy with them!
If you want a powerful but easy verb, you can’t go wrong with the BigSky. But if you want to test the bounds of your reverb creativity, then MX all the way! 🙌
@@thepedalcollaborative love the thoughtful responses from both of you! Thanks again and keep up the inspiring work!!
This was not very useful... of course the identically named software modules inside of two visually identical digital hardware devices are going to sound identical.
Now we know! 🙌