Max 5: problems with seq~
Max 5.0.4 on Windows XP SP3
Using a metro-locked phasor does not seem to enable recording into seq~ like a 'regular' phasor. Also, the message 'eraseall' does not seem to work like 'clear'.
Also, a question: What's the best way to maintain the tightness of signal domain sequencing after the seq~ object?
Here's the patch:
Hi,
Yes, I was using the Global Transport to test this patch. Are you able to get the seq~ to record bangs at all when using the Global Transport with the locked phasor?
Thanks.
Hmm, it's still not working. If I switch to the regular phasor after having recorded using the locked phasor, it'll play the events back but not if I'm using the locked phasor to play back.
Yeah - I'm seeing the same thing. We'll investigate - thanks for the patch.
Cheers
-A
Strange! Still nothing... Definitely outputting a ramp but the seq~ is not playing back the bangs...
Quote: RabidRaja wrote on Wed, 20 August 2008 11:26
----------------------------------------------------
> That's weird, it's working perfectly for me no matter which phasor~ i choose... try this one, this time, click on "tempo 60" to make sure your locked phasor is running at the same tempo as your regular one. And, just to make sure you're not recording over previous runs with silence/inaction, do me a favor and click on record, overdub, and play and leave them all on at the same time, while you record bangs into it.
> I've also included a scope~ which should read a ramp from 0 to 1 no matter which phasor~ you choose. Let me know your results:
>
>
>
>
----------------------------------------------------
Thanks for your help. I'll see if I encounter the problem on my OS X machine tonight.
Just to clarify, if someone from Cycling '74 responds to a bug report saying, "Thanks for the report. We'll look into it," this means the bug has been logged in our bug-tracking system and sent on to the developers, and you don't need to do anything else unless someone contacts you for further info. Sending an email about this issue to support will just mean more redundant work for someone else.
Thanks to all for the assistance.
Andrew B.
in taking a closer look at this, if you turn on 'scheduler in overdrive' and 'in audio interrupt' in your dsp settings, this patch works as expected.
I can see if this is just the way it is or if this is a bug, but regardless, I highly recommend that you have both of these options activated whenever you are doing anything with ITM.
Another thing, 'eraseall' is not a valid message to seq~, not sure where that came from. You want 'erase', which is the same as 'clear'.
All the best,
-Ben
Quote: ben@cycling74.com wrote on Wed, 20 August 2008 15:55
----------------------------------------------------
> in taking a closer look at this, if you turn on 'scheduler in overdrive' and 'in audio interrupt' in your dsp settings, this patch works as expected.
>
> I can see if this is just the way it is or if this is a bug, but regardless, I highly recommend that you have both of these options activated whenever you are doing anything with ITM.
>
> Another thing, 'eraseall' is not a valid message to seq~, not sure where that came from. You want 'erase', which is the same as 'clear'.
>
> All the best,
> -Ben
>
>
----------------------------------------------------
Hi,
Sorry, it's in the seq~ help subpatch [editing] and it's 'erase all' not 'eraseall', you're right.
Also, 'add' and 'delete' entries in the seq~ Reference are transposed.
By the way, excuse my ignorance, but what is ITM? This is the second time in as many days that I've seen the acronym.
Matt
the seq~ documentation error has been fixed for the next incremental.
-Ben
and the 'I' stands for "Integrated" ;)
-b
hey guys,
i was suffering this same problem.
using 'scheduler in audio interrupt' fixed it instantly.
should this be necessary though?
t
On 7 sept. 08, at 13:44, trent.gill wrote:
> hey guys,
> i was suffering this same problem.
> using 'scheduler in audio interrupt' fixed it instantly.
> should this be necessary though?
For any precise timing scheduler in audio interrupt is required.
ej