Sending multiple messages sequentially (one by one) to live.object
Hi, I made a device and everything seems to work, but as soon as I close the editor window, the device stops working. But I just go into edit mode and everything works again. I have no errors, everything works fine. I came to the conclusion that I was sending too many messages at once and some of them were receiving values. Any ideas on how to send all these messages one by one, one after the other?
By the way, I also use 2 [live.object] in the patch, but I think this is not a problem.
you don't use pak in first place.
insert thresh -> message or print to see why.
then separate and slow down messages.
why should you set pitch_coarse
or any other parameter twice in same message
using 2 different values ?
Makes no sense.
SOURCE AUDIO, I'm just working on a device that will randomly stretch audio clips on a track, I decided to implement it this way because I didn't quite understand how to work with warp markers using LOM) Thanks, I'll try your advice!
Hey SOURCE AUDIO, nothing seems to work, or I don’t understand exactly how to use pak.?
Problem with pak is that it triggers output
on each inlet input.
in your allready troubled multi message that
multiplies the problem.
you should try to collect your expected list
and output it only once, for example using join
with decided trigger input in case left value arrives before right one whick makes pack
unusable
SOURCE AUDIO, I really don't understand what you mean, here's the patch, maybe you could take a look at it if you have enough time. Thank you! Because I've already broken my head.
Because I've already broken my head.
Maybe take a break, breath, and come back to it later!
Looking at your patch, it seems that you try to assemble differente pieces together without understanding what they do by themselve.
Replacing [pak] by [join] indeed solves the problem of sending the message twice, but I think you wired them the wrong way. Keep in mind cold and hot inlets.
In your example, when a bang arrives to set you pitch values, you:
- first trigger a random value between 0 an 48, scale it, and send it into the [join] hot inlet
- which makes it output a list made of the current new random value, and the previous value coming from its cold inlet (or a 0 when you trigger the [join] output for the first time, as nothing has come into its cold inlet yet).
- then send the value coming from [unjoin 2] into the [join] right, cold inlet (which will be sent only when another value will come into [join] left, hot inlet)
Maybe this example will help you understand:
Maybe simply invert the wires comming into your [join], and also invert $1 and $2 into your subsequent message?
I came to the conclusion that I was sending too many messages at once and some of them were receiving values. Any ideas on how to send all these messages one by one, one after the other?
A message with commas is already like different messages sent one by one:
to fix sending of multiple, unneeded messages is one thing,
but real problem could be if live and it's objects can accept that messages at all.
it is easy to test, send a message filled with some values and check
I am not using Live and can't help you with that part.
TFL, SOURCE AUDIO, No, this still does not solve the problem. The patch works when I'm in the editor, but in device mode (ableton) it still doesn't respond...
Conspicuously missing from that video is the Max console showing possible errors that might explain to you why your code isn't working rather than making us guess.
TYLER MAZAIKA, this is all
You're showing the max console in the Max for Live editor, not the console window in Live context? IIRC they don't share data.
Time to add some [print] to relieve the emptiness and see what's going on.
