Відео

Are you using the @ symbol before writing "chans"? The "chans" attribute should be a valid attribute for any mc. object. You need the @ symbol to specify that you are talking about an attribute, and not an object argument. You could also change the output channels in the inspector for the object instead of setting it directly on the object itself. Hopefully that helps.

I've done pattrstore interpolation before, but not with this patch specifically. I feel like pattrstorage would be unnecessary for this since it already interpolates and there is only 3 parameters, but in a larger project it could probably be useful. Although I'm not sure what you mean by "dynamic" interpolation factor. If you end up incorporating that somehow I'd love to see what you come up with!

Thank you! and no worries, if you want to connect a sequencer, it really depends on what you want the sequencer to control. It could connect to and modulate any of the parameters of the synth (modulator frequency, ratios, filter, etc). However, I assume you want it to sequence pitched notes, in which case you will want to modulate the carrier frequency. That is the dominant frequency in FM and will determine what pitched is perceived. To do that, you could either plugin directly to carrier inlet of the gen device, or an easier way would be to use the already setup MIDI note allocator function and send MIDI notes into that. Basically, replace the virtual MIDI keyboard with your sequencer, and send notes into the left inlet of the [pack i i], and velocities in the right inlet. However, since this is polyphonic, it might be trickier if you want polyphonic sequencing, but it should work easily as a monophonic sequencer. Also, since you're new, I would highly recommend working through the Max tutorials, there is a lot of good information in there and should be a few topics on sequencing. Hopefully that helps!

@@benjaminward9042 Great, thanks for the prompt reply. All working, thanks for your help (as for the Max tutorials, it's easier for me to follow. video tutorial as I have ADHD and written interactions can be difficult for me to understand)

@@LostandMeandering Ahh I understand, well I'm glad the videos helped and you got it working. Happy patching!

@@benjaminward9042 I have a further question if I may, please. I am making a patch and added two of the myths. The ADSR envelope behaved strangely on the second sytth. The notes were coming through from the sequencer, but the envelope was only putting out the odd truncated note. I tried a few times, but whichever synth I added second had the problemAny ideas? (BTW, I didnt use a send/receive for the. ADSR, I used a cable).

@@LostandMeandering Hmm, not sure. It's hard to tell exactly without seeing your patch. You would need two independent ADSRs for each synth so I would make sure you aren't using a single ADSR for both and they each have independent paths. Otherwise it may have something to do with the timing of the ADSR. Maybe the release time is too long? That could interfere with the next trigger for the ADSR, although I don't know why this would cause it to work with one but not the other. Using a cable instead shouldn't be an issue.

Thank you! Glad to hear you found it helpful.

Oh interesting. I haven't used that before but I'll definitely try it out. Already sounds cleaner than my method. Thanks for the tip!

Thank you! Glad to hear you're finding it useful.

Thanks! Ya, I was unsure if people would like it or not so your feedback is very appreciated. Will remove from future videos. 👍🏻

@@benjaminward9042 great tutorial and agreed about the bg music... would be very curious to see a tutorial for implementing more operators and different fm algorithms/topology. thanks!!

That's because we are not multiplying the signal by any value once we send it into the *~ object. We will only get signal out of the *~ object when we multiplying it by a non--zero value or signal, which will come from the adsr~ and be triggered by our MIDI device. If you want to continuously hear the input signal from that object, you can multiply it by 1, although then this has no effect. Hopefully that helps.

hey, i got the same problem. did you find any solution?

Sounds like it might be an issue with how elektron cycles sends midi data out. I've used other elektron devices like the analog four and for that you have to go in and program how midi data is sent out since there are a few different ways of sending midi with devices like that (live midi, pattern playback). The first thing I would do is make sure you're getting midi to your computer in any way from the elektron cycles at all. I use a free program called Midi Monitor which is really quick to ensure your getting data, but you can test with other softwares. If you are getting data in other programs except for Max, then I would double check the channel settings for both the elektron cycles, and within the Max settings. Hopefully that helps!

Thank you! It's hard to say what exactly the issue is without looking at your patch, but If you're sure that you've made all the right connections, then it could just be a glitch with one of the "mc" objects, specifically mc.adsr~. That's happened to me before and someone else reached out with a similar issue like that so I would try deleting and re-instantiating that object. If that doesn't work try re-instantiating some other mc objects within the chain. Let me know if that works!

No I don't, but that's definitely something I should put on there. I just updated my profile so it should be there now, but here's a link to it anyway github.com/Bohr33

Cool thanks

Np, glad it was helpful!

Hmm, it sounds like it must be an issue with the value sending the setvalue on/off messages. If using mc.adsr, it should be receiving a setvalue message with the channel to trigger, and an on value of “1”. Test sending just a message of “1” to see if the ADSR at least creates output. If it does then it must be an issue with the setvalue messages triggering the ADSR. Double check the last portion of the video which is all about setting mc.adsr. Also, make make sure at the end you send the adsr multichannel signal back into note allocater. That is needed to make sure the release works. Hopefully that helps👍🏻

No worries! That would be because “setvalue” is not an object but a message. It should be placed in a message box (probably with a $1 so incoming values replace that value). Another option would be to use the “prepend” object with argument “setvalue”. That would put the message “setvalue” in front of the incoming values. I don’t remember the exact context I used it in this video, but hopefully that helps.

thank you

Yes you're absolutely right, thanks for catching that!

Oh great! Thanks for the suggestion. I'm always happy to learn of better ways of doing things so I appreciate the tip. I completely forgot about rampsmooth~; that would definitely the simpler option for this.

Thank you! I am going to try and make videos like this regularly,. Let me know if you have any topics you'd like me to explore!

sounds good! at the moment i am very interested in concepts how to transform statsistic datas (=numbers) in (experimental) musical context (what methods are possible, who does it work…) in max/msp.@@benjaminward9042

Oh cool! I haven't done much with statistical data but I'll see if I can find a way to incorporate that somehow. Your channel is sick btw.

@@benjaminward9042 Could you do a video-tutorial on time stretching from incoming audio through the buffer~ object?

Hmm, I can definitely look into. Do you mean incoming audio like live audio from a mic? Or playback from an audio file?