A while ago I skimmed a document from either c74 or Ableton which outlined the steps to take before releasing a M4L device. I remember it was relatively long. Does anyone know what I am talking about/where to find it? I can’t seem to find it on my own.

Do you mean:


?
3 Likes

yes thank you so much! my searches of “how to release max for live devices” and similar phrases were fruitless haha

I’m trying to update a device I made years ago and I can’t for the life of me remember how to open bpatcher when it is set to ‘embed patcher in parent’. I want to edit a few parameters, and I don’t have the original patcher files, only the consolidated .amxd

Anyone know what I can do?

From memory, I think you’d have to right click, open a new view and then save as. Then de-check embed on the bpatcher and point it to the new saved version.

1 Like

That did the trick thank you!

1 Like

Hey people!

First-time poster here. Have been lurking around the forum for around a year now, and already learned so many new things, it’s a really cool place you have going! I thought if I’d join the conversation it would be nicer and maybe eventually I could even give back something!

I’ve been trying to transition my modular workflow more into Ableton throughout this past year, and every now and then I end up banging my head against the wall for some seemingly simple thing that I just can’t figure out by myself. One major thing that I often find myself lacking is some triggerable sample and hold-thingy, that would let me hold a modulation value (say, from a M4L LFO) whenever “something” happens (say, MIDI note is triggered). I thought I had a breakthrough a couple of days ago when I found this Modulation Tools Set M4L pack that seemingly does what I need, but unfortunately it also had it’s problems…

The Sample and Hold module in that pack would be ABSOLUTELY PERFECT, if it wouldn’t break the undo history of Ableton whenever it’s triggered. I tried to look into the problem and found there’s lot’s of conversation about it online, but since I have no experience with programming anything with M4L, I’m not quite sure if this is something that could be fixed or not. I tried this one proposed solution (https://help.ableton.com/hc/en-us/articles/209066909-Unable-to-undo-due-to-certain-Max-for-Live-devices) of settings the “Parameter Visibility” to “Hidden” in the device properties, but as a consequence the trigger input wasn’t mappable anymore…

Does any of you use some sort of sample and hold M4L tricks in your Live sessions? Am I missing something obvious? What’s your solution?

Cheers and thank you for any input!

3 Likes

I suppose it what the something is, and how you can measure it and send it to your device. In the case you’re describing, it may be easier to hack the Midi LFO to run continually and output on midi notes. Or you could create a device with a UI slider or similar, then have other things map to it and build your sample and hold after it. I guess then you’d have to map that onwards, and I don’t know how M4L would deal with that.

Hey @_mark, thanks for joining in!

“I suppose it what the something is, and how you can measure it and send it to your device.”

Yeah for sure! I think I have that “something” / “source”-part figured out. Be it Midi notes, some modulation or some audio event, I can usually turn it into this mappable “modulation” thingy in Ableton that you can route around and process using various M4L devices. It’s more the “triggering”-part that I’m struggling with. Until just couple of days ago I didn’t have any way of simulating the S&H-functionality where I could map my various “sources” and hold their value whenever something triggers/crosses a threshold. Now the problem, like I said in the earlier post, is that, at least with this spesific S&H device, whenever the triggering happens, the Undo History is also messed up which is also not ideal. I also don’t know that if I’d patch together my own sample and hold of sorts whether that could be avoided. This is where I thought someone with more knowledge or some alternative workaround that I haven’t thought of could jump in!

( Happy Holidays everyone! )

I am looking at building a simple router to route the inputs from my Apollo interface to OBS for streaming. Loopback worked, but I don’t really want to buy $100 software to do a couple streams. I’m trying to use soundflower with Max, but I’m stuck. I see inputs from my Apollo using ADC but I’m unsure how to route that to Soundflower. I thought use DAC, but I don’t see anything in OBS doing that and I’m not sure why I would need to converter from digital to analog if I’m routing to a virtual channel. What am I missing?

I use the jack audio router for this, you set OBS to jack and then set your Apollo monitor outs (mine were like 27/28 or something, look at the io matrix in console) or a cue out or whatever you want in the jack app’s matrix. It is not the fanciest software but once you have the routing set it does stay solid, unless you unplug then you have to restart jack router and set OBS to it again.

The problem is my Apollo is firewire, not thunderbolt, so Console doesn’t give IO matrix options.

O hmm, I’m not sure then, sorry about that

It seems like it should be way easier than it is proving to be. Maybe I should just route all these into my analog mixer and do it the old fashion way instead.

1 Like

i feel like this is my experience with livestreaming in general hah

1 Like

Blackhole is the new sound flower and is super solid in my experience

3 Likes

Nice, looks like that works!

I am trying to figure out this schematic and how to translate it into gen~objects. I have prior experience with building a biquad filter, compressor and a reverb so I know most of the symbols.

Do any of you know what the blocks containing the [integral-symbols] is in gen~? and also I am a bit confused about what the [d/dt] represents.

The schematic is from a research paper on making a digital model of the buchla lowpass-gate if any of you are interested.

http://dafx13.nuim.ie/papers/44.dafx2013_submission_56.pdf

The \frac{d}{dt} should be taking the derivative of the input signal. Something like delta object would work for this, I think? As for the integrals, you’re probably looking to use something like history in combination with some other objects to accumulate values over time.

2 Likes

this figure (figure 3 in the paper) illustrates the analog topology. it is not a direct description of a DSP structure.

section 2 of the paper precisely concerns the classic problem of discretizing the integrator and differentiator blocks.

  • first, approximation by trapezoidal rule using a delay element. the corresponding DFT2 blocks are illustrated in figure 4.

  • you can stop there (the “classic” solution), or continue reading on how to solve the resulting system to eliminate the delay loop (the “new and improved” method, which is more efficient and stable under modulation.)

also important to look at section 2.3. this discusses the nonlinearities introduced by optocoupling, which are really important to the sound of the vactrol LPG. these elements are not shown in the basic block diagram, cannot really be captured by the DFT2 model, and they complicate the delay-free model considerably.


if you just want to plug something into gen~ right away, proceed to equations (25) and (26), and at least skim the control path section if you want it to “feel” like a vactrol as well as sound like one.

3 Likes