Hello all,

So I am trying to figure out a patch idea and running into some snags. I am wanting to run a couple CVs into My Herzlich Labs MMI and then out into a sample and hold to modulate and trigger my Braids. Am I able to run the cv out from Ornament and Crime into the MMI and then back into O_c for the S&H to trigger Braids and input to the V/O? I'm sure I can also use Zoia for this too so either option is fine, I'd just like to use O_c if possible. Thanks!
Heres my rack!
ModularGrid Rack


i was mentioning that i thought the admins should implement ai chat assistance at a fair and democratized price for the site's benefit, so, i plugged this question into Claude 3.7 Sonnet to show off a demo of why i thought this would be a good idea, in general, ... ... ...

Claude:

I'd be happy to help you with your eurorack patching question!

Yes, you can definitely run CV outputs from your Ornament & Crime (O_C) into the Herzlich Labs MMI and then back into the O_C for sample and hold functions to trigger and modulate your Braids. This kind of feedback patching is absolutely possible in a eurorack system.

Here's how you could set this up:

  1. Use one of your O_C outputs to send CV to the MMI inputs
  2. Take the CV output from your MMI (which will now be influenced by your gestural control)
  3. Route that back into an input on your O_C
  4. Configure one of your O_C apps (likely Hemispheres) to use its S&H functionality
  5. Use the resulting modulated output to control parameters on your Braids

Your setup is perfectly capable of this kind of patching. The MMI is designed specifically for these kinds of performance-oriented signal manipulations. Since you have two uO_C modules, you could even use one for generating the initial CV and the other for the S&H processing.

The buffered multiples in your rack will also come in handy here, as you might want to split some of these signals to multiple destinations.

As you mentioned, the ZOIA could accomplish this as well - it's extremely flexible for this kind of signal routing and processing. But using the O_C as you described would work great and give you a more hands-on, hardware-focused approach to the patch.

Is there anything specific about this patch flow you're having trouble with?

...

(and if this model was further fine tuned and continuously retrained on more new and annotated data, pretty soon it would know more than anyone on this forum.)

((peace ))


I do have the Hemisphere app in both O_c so what would be the best apps? I have been trying to use Vector LFO for the CV source and Dual Quantizer for S&H, but its not really working the way I think it should.


Claude says:

I understand your challenge with the Hemisphere apps. Since you're using Vector LFO and Dual Quantizer, there are some specific considerations for making this patch work properly.

For your application, Vector LFO isn't ideal for feeding into the MMI then into a sample and hold setup. Here's a better approach using your two O_C modules:

For the first O_C:
- Instead of Vector LFO, try using "LOFI" or "Quadraturia" for generating more interesting CV sources
- These will give you more complex modulation to feed into your MMI

For the second O_C:
- Rather than Dual Quantizer, use "ASR" (Analog Shift Register) or the dedicated "Sample and Hold" app in Hemispheres
- Make sure to set up a clock source for the S&H function - you could use the internal clock or patch in an external trigger

The critical issue might be that Dual Quantizer isn't really a true sample and hold - it's designed to quantize incoming CV to musical scales. For proper S&H functionality to trigger Braids, you specifically want one of the sampling apps.

For patching, try:
1. First O_C: LOFI/Quadraturia output → MMI input
2. MMI CV output → Second O_C input
3. Second O_C: ASR/S&H app output → Braids V/Oct and trigger inputs

If you're still having trouble, consider trying the full O_C firmware rather than Hemispheres on one of your modules - the "Piqued" app is excellent for this kind of sample and hold application with extensive trigger options.

Does that help clarify what might be going wrong with your current patch approach?