michelez

I have a problem with seq~. I have a large patch with many poly~s in parallel mode. It does not go beyond 50-55% of CPU usage. I run max 7.2 on a 2.5 GHz mac intel core i7. I have 48 seq~ running simultaneously. The seq~ work fine in a normal setting. I have attached a patch that shows what I am doing for every seq~. But if the patch is running all of things at once the seq~s start acting up: they send out messages when they are not supposed to, repeat messages etc. I have tested this over and over, tried to work with the vector size. I would welcome any comments. I am sure somebody else had this problem?

To test the matter I have tried to download the dspstress~ object that comes with the idk but it's not there anymore...

I have a problem with seq~. I have a large patch with many poly~s in parallel mode. It does not go beyond 50-55%  of CPU usage. I run max 7.2 on a 2.5 GHz mac intel core i7.  I have 48 seq~ running simultaneously. The seq~ work fine in a normal setting. I have attached a patch that shows what I am doing for every seq~. But if the patch is running all of things at once the seq~s start acting up: they send out messages when they are not supposed to, repeat messages etc. I have tested this over and over, tried to work with the vector size. I would welcome any comments. I am sure somebody else had this problem?
To test the matter I have tried to download the dspstress~ object that comes with the idk but it's not there anymore...
See patch attached.

seq-behaves-strangely

Actually I think the problem is unrelated to seq. I would erase this post but not sure how

48 seq~ objects is a lot. Just to make sure - you do know you can use one seq to sequence many channels of data? Do you need that many individual objects?

Unfortunately I do. I am using ten different seq # for each seq~. It's an interactive patch with polyrhythm and patterns that go "out of sync". All of them use the same phasor~ though, with a few rate~ that determines the polyrhythm rate.

seq~ behaves strangely