jit.qball change in v1.6.1?

Aug 27, 2006 at 12:59pm

jit.qball change in v1.6.1?

Hi,

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?

Or did I miss some changes?

Bernd

OSX 10.4.7, G5, QT 7.1.2

#27321
Aug 27, 2006 at 10:33pm

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

> 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.

-Joshua

#82567
Aug 28, 2006 at 8:56am

Ok, here is the example.

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

That?s strange…

Can anyone confirm this on his/her machine?

Bernd
———————

max v2;
#N vpatcher 10 59 610 459;
#P window setfont “Sans Serif” 9.;
#P user jit.fpsgui 251 239 60 196617 0;
#P window linecount 1;
#P newex 246 184 45 196617 jit.qball;
#P newex 194 115 53 196617 train~ 10;
#P connect 0 1 1 0;
#P connect 1 0 2 0;
#P pop;

#82568
Aug 28, 2006 at 2:17pm

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.

#82569
Aug 28, 2006 at 2:58pm

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… (?)

-mj

>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.
>

#82570
Aug 28, 2006 at 4:38pm

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.

-Dave

max v2;
#N vpatcher 10 59 441 365;
#P button 217 24 15 0;
#P user ezdac~ 165 190 209 223 0;
#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P newex 235 43 27 196617 10.;
#P newex 235 23 54 196617 loadbang;
#P user jit.fpsgui 265 105 60 196617 0;
#P newex 265 84 45 196617 jit.qball;
#P newex 235 63 40 196617 train~;
#P user jit.fpsgui 159 107 60 196617 0;
#P newex 159 86 45 196617 jit.qball;
#P newex 129 65 40 196617 train~;
#P user jit.fpsgui 64 106 60 196617 0;
#P newex 64 85 45 196617 jit.qball;
#P newex 21 64 53 196617 train~ 10;
#P window linecount 2;
#P comment 44 24 100 196617 It’s tired of listening to your arguments.;
#P user panel 37 14 124 44;
#X brgb 236 110 110;
#X frgb 0 0 0;
#X border 1;
#X rounded 0;
#X shadow 0;
#X done;
#P connect 2 1 3 0;
#P connect 3 0 4 0;
#P connect 5 1 6 0;
#P connect 6 0 7 0;
#P connect 14 0 12 0;
#P connect 11 0 12 0;
#P connect 12 0 8 0;
#P connect 8 1 9 0;
#P connect 9 0 10 0;
#P pop;

#82571
Aug 29, 2006 at 11:06am

Hi David,

thanks for hint!
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?

Bernd

#82572
Aug 29, 2006 at 2:13pm

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.

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

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

#82573

You must be logged in to reply to this topic.