Bernd

I usually used the right "train~" outlet thru jit.qball as a stable clock for banging the render context.

In v1.6.1 the framerate drops to around 1 frame behind jit.qball. Is this jit.qball related or should I post this to the max/msp forum?

jit-qball-change-in-v1-6-1

On Aug 27, 2006, at 5:59 AM, Bernd wrote:

> I usually used the right "train~" outlet thru jit.qball as a stable 

> In v1.6.1 the framerate drops to around 1 frame behind jit.qball. 

> Is this jit.qball related or should I post this to the max/msp forum?

To the best of my knowledge, there should have been no functional 

changes to jit.qball in the past several years. However, note that 

there may be a discrepancy between installations due to scheduler 

settings. As always, please provide us a clear example which 

demonstrates the issue so that we can more adequately understand what 

> I usually used the right "train~" outlet thru jit.qball as a stable  
> clock for banging the render context.
>
> In v1.6.1 the framerate drops to around 1 frame behind jit.qball.  
> Is this jit.qball related or should I post this to the max/msp forum?

To the best of my knowledge, there should have been no functional  
changes to jit.qball in the past several years. However, note that  
there may be a discrepancy between installations due to scheduler  
settings. As always, please provide us a clear example which  
demonstrates the issue so that we can more adequately understand what  
it is you're doing.

In the meantime I found the reason (??) for that behaviour.

When saving the patch below as TEXT and loading it the framerate is around 86 fps.

When saving the patch as BINARY and loading it the framerate drops to 1-5 fps.

This is on a OSX 10.4.7, G5, QT 7.1.2, Max/MSP 4.6.1/Jitter 1.6.1

Can anyone confirm this on his/her machine?

I cannot reproduce at all. PowerBook G4. Framerate remains 1-5 the 

> In the meantime I found the reason (??) for that behaviour.

> When saving the patch below as TEXT and loading it the framerate is 

> When saving the patch as BINARY and loading it the framerate drops 

I cannot reproduce at all. PowerBook G4. Framerate remains 1-5 the  
whole time, text or binary.

> In the meantime I found the reason (??) for that behaviour.
>
> When saving the patch below as TEXT and loading it the framerate is  
> around 86 fps.
>
> When saving the patch as BINARY and loading it the framerate drops  
> to 1-5 fps.


here (pb1.67) stays at 86 fps both text/bin

i managed to get i going after playing with the help file

when help file closes the train suddenly runs... (?)

>I cannot reproduce at all. PowerBook G4. Framerate remains 1-5 the 

>>In the meantime I found the reason (??) for that behaviour.

>>When saving the patch below as TEXT and loading it the framerate is 

>>When saving the patch as BINARY and loading it the framerate drops 

here (pb1.67) stays at 86 fps both text/bin
max 4.5.5 jit 1.5.2

how do you start  that train~
i managed to  get i going after playing with the help file
when help file closes the train suddenly runs... (?)

>I cannot reproduce at all. PowerBook G4. Framerate remains 1-5 the 
>whole time, text or binary.
>
>jb
>
>Am 28.08.2006 um 10:56 schrieb Bernd:
>
>>In the meantime I found the reason (??) for that behaviour.
>>
>>When saving the patch below as TEXT and loading it the framerate is 
>>around 86 fps.
>>
>>When saving the patch as BINARY and loading it the framerate drops 
>>to 1-5 fps.
>


I don't think the problem is with [jit.qball], or with text vs. binary.

I think: [train~ 10] is acting suspiciously like [train~ 1000] AKA 

[train~]. A slap upside its left inlet clears it right up for me, but...

MaxMSP 4.6.1/Jitter 1.6.1, OSX 10.4.7, PB G4.

I think: [train~ 10] is acting suspiciously like [train~ 1000] AKA  
[train~]. A slap upside its left inlet clears it right up for me, but...

A loadbang->10 to train~ really does it for me.

Strange enough your example works on all three trains (86fps) identically ??!!

Joshua, should I crosspost this to the Max/MSP list?

thanks for hint!
A loadbang->10 to train~ really does it for me.
Strange enough your example works on all three trains (86fps) identically ??!!

Huh. That's pretty neat. Apparently this patch returns different 

Copying the text and using New -> Paste will cause all the all the 

[train~]s in the patch to behave as [train~ 10], even if they aren't.

Copying the text and using New From Clipboard will return the results 

I was describing earlier, with [train~ 10] ignoring its argument.

Looking a little harder at this, it seems like [train~] has a lot of 

problems in 4.6.1, in addition to what's been described already. I'll 

On Aug 29, 2006, at 7:06 AM, Bernd wrote:

> Strange enough your example works on all three trains (86fps) 

Huh. That's pretty neat. Apparently this patch returns different  
results depending on how it's run.

Copying the text and using New -> Paste will cause all the all the  
[train~]s in the patch to behave as [train~ 10], even if they aren't.
Copying the text and using New From Clipboard will return the results  
I was describing earlier, with [train~ 10] ignoring its argument.

Looking a little harder at this, it seems like [train~] has a lot of  
problems in 4.6.1, in addition to what's been described already. I'll  
work on a bug report.

> Strange enough your example works on all three trains (86fps)  
> identically ??!!


jit.qball change in v1.6.1?