Thomas

I have encountered a really strange bug (I think) today.

I am working on a fairly large patch. For me it is at least, I think there's 100-200 objects at least.

As part of the patch I have implemented some AM on some oscillators and everything seem to be in order, but some of the objects are acting very strange.

Specifically, the AM won't work unless I create a MSP object in the patch. That's it.. I don't have to connect it to anything, but the AM does not influence the carrier signal, unless I create a MSP object somewhere inside the patch, It doesn't work if I create a Max object, but simply creating a [number~] or [saw~] suddenly makes it work.

This is really twisting me, as I would like this patch to work of course!

Do any of you have any idea why this is happening and how to fix it?

I have included a video recording, as I felt this was easier than uploading the whole patch as it is right now. There's some very significant time delay in the video. This is just some error with the screen capture software - it has nothing to do with Max.

https://www.youtube.com/watch?v=bm2_E7peh80&feature=youtu.be

I have encountered a  really strange bug (I think) today.
I am working on a fairly large patch. For me it is at least, I think there's 100-200 objects at least.

As part of the patch I have implemented some AM on some oscillators and everything seem to be in order, but some of the objects are acting very strange.
Specifically, the AM won't work unless I create a MSP object in the patch. That's it.. I don't have to connect it to anything, but the AM does not influence the carrier signal, unless I create a MSP object somewhere inside the patch, It doesn't work if I create a Max object, but simply creating a [number~] or [saw~] suddenly makes it work.

This is really twisting me, as I would like this patch to work of course!
Do any of you have any idea why this is happening and how to fix it?

I have included a video recording, as I felt this was easier than uploading the whole patch as it is right now. There's some very significant time delay in the video. This is just some error with the screen capture software - it has nothing to do with Max.
LINK FOR VIDEO: https://www.youtube.com/watch?v=bm2_E7peh80&feature=youtu.be

really-strange-bug-with-msp-objects-video-included-help-me-not-lose-my-mind

Putting the dummy MSP object in causes the signal chain to compile. Which leads me to believe that their's something strange about how your signal chain initially compiles.

Why are you using send with signals, rather than send~? Is there anything dynamic going on there that could be confusing Max's signal diagram?

maybe it is too late now, but usually if somehting like that appears, it will be ok again if you re-open the patcher or eventually restart max.

Really strange bug with MSP objects (Video included). Help me not lose my mind.