OK, so I'm working on a patch that keeps things perfectly in phase just to tinker with fundamentals/overtone combinations/amplitudes and such. I realized there was an issue with the results after I adjusted the boxes then set them back, so I hook up a scope~ to both of them and its actually oscillating the one cycle~ object at 1/2 of what it should be. So I resend the values 1000 times, it's still doing it. I delete and copy+paste the second half of the patch 1000 times, it's still doing it. Eventually I just decide ill close the patch and reopen it and see what happens. So I close the patch and reopen it and it works perfectly fine.

Seriously, are you fucking kidding me? Every time I try to do anything precise in Max it seems like some garbage nonsense bullshit like this always happens where it turns out to be not some fault of mine, but just some fault of Max not performing properly. It reminds me why I grew to hate it a few years ago. Can anyone explain why it seems to love to randomly not function properly for absolutely no reason sometimes?

OK, so I'm working on a patch that keeps things perfectly in phase just to tinker with fundamentals/overtone combinations/amplitudes and such. I realized there was an issue  with the results after I adjusted the boxes then set them back, so I hook up a scope~ to both of them and its actually oscillating the one cycle~ object at 1/2 of what it should be. So I resend the values 1000 times, it's still doing it. I delete and copy+paste the second half of the patch 1000 times, it's still doing it. Eventually I just decide ill close the patch and reopen it and see what happens. So I close the patch and reopen it and it works perfectly fine. 

Seriously, are you fucking kidding me? Every time I try to do anything precise in Max it seems like some garbage nonsense bullshit like this always happens where it turns out to be not some fault of mine, but just some fault of Max not performing properly. It reminds me why I grew to hate it a few years ago. Can anyone explain why it seems to love to randomly not function properly for absolutely no reason sometimes?


broken-objects-until-restart

Actually, it really seems like whenever I try to do something precise, I pay enough attention and discover another one of Max's inconsistencies in what should be a proper data output. (It's not just a timely inconvenience, It's a consistent inconsistency that I only discover only when I pay that much attention).

broken objects until restart