loopreport broken?

Apr 10, 2007 at 5:37am

loopreport broken?

I believe ive seen this posted on the list – but could not find any
reference, but @loopreport 1 seems to be broken with jit.qt.movie?

this patch does not report uh, anything other than the file being
read in.

#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P message 192 108 56 196617 asyncread;
#P newex 349 190 32 196617 print;
#P message 149 108 33 196617 start;
#P newex 315 164 32 196617 print;
#P toggle 60 60 15 0;
#P newex 60 79 51 196617 qmetro 2;
#P newex 349 161 82 196617 route loopnotify;
#P user jit.pwindow 128 176 82 62 0 1 0 0 1 0;
#P newex 129 137 230 196617 jit.qt.movie @autostart 0 @loopreport 1
@loop 1;
#P connect 3 0 0 0;
#P connect 2 0 7 0;
#P connect 4 0 3 0;
#P connect 6 0 0 0;
#P connect 0 0 1 0;
#P connect 8 0 0 0;
#P connect 0 1 2 0;
#P connect 0 1 5 0;
#P window clipboard copycount 9;

v a d e //

http://www.vade.info
abstrakt.vade.info

#31278
Apr 10, 2007 at 5:45am

oops! Sorry!

Mac OS X 10.4.9, QT 7.1.5, Max 4.6.2, Jitter 1.6.3b2

On Apr 10, 2007, at 1:37 AM, vade wrote:

>
> I believe ive seen this posted on the list – but could not find any
> reference, but @loopreport 1 seems to be broken with jit.qt.movie?
>
> this patch does not report uh, anything other than the file being
> read in.
>
> #P window setfont “Sans Serif” 9.;
> #P window linecount 1;
> #P message 192 108 56 196617 asyncread;
> #P newex 349 190 32 196617 print;
> #P message 149 108 33 196617 start;
> #P newex 315 164 32 196617 print;
> #P toggle 60 60 15 0;
> #P newex 60 79 51 196617 qmetro 2;
> #P newex 349 161 82 196617 route loopnotify;
> #P user jit.pwindow 128 176 82 62 0 1 0 0 1 0;
> #P newex 129 137 230 196617 jit.qt.movie @autostart 0 @loopreport 1
> @loop 1;
> #P connect 3 0 0 0;
> #P connect 2 0 7 0;
> #P connect 4 0 3 0;
> #P connect 6 0 0 0;
> #P connect 0 0 1 0;
> #P connect 8 0 0 0;
> #P connect 0 1 2 0;
> #P connect 0 1 5 0;
> #P window clipboard copycount 9;
>
>
> v a d e //
>
> http://www.vade.info
> abstrakt.vade.info
>
>
>

v a d e //

http://www.vade.info
abstrakt.vade.info

#101412
Apr 10, 2007 at 6:30am

Mac OS X 10.4.9 PPC, QT 7.1.5, Max 4.6.2, Jitter 1.6.2 here

Couldn’t seem to replicate your problem here… tried all sorts of
different ways to make it not happen… I remember this problem in
1.5, but I think it’s fixed. Only difference I see is the 1.6.3b2…
sorry…

Keith

On 4/10/07, vade wrote:
> oops! Sorry!
>
> Mac OS X 10.4.9, QT 7.1.5, Max 4.6.2, Jitter 1.6.3b2
>
>
>
> On Apr 10, 2007, at 1:37 AM, vade wrote:
>
>
> I believe ive seen this posted on the list – but could not find any
> reference, but @loopreport 1 seems to be broken with jit.qt.movie?
>
> this patch does not report uh, anything other than the file being read in.
>
> #P window setfont “Sans Serif” 9.;
> #P window linecount 1;
> #P message 192 108 56 196617 asyncread;
> #P newex 349 190 32 196617 print;
> #P message 149 108 33 196617 start;
> #P newex 315 164 32 196617 print;
> #P toggle 60 60 15 0;
> #P newex 60 79 51 196617 qmetro 2;
> #P newex 349 161 82 196617 route loopnotify;
> #P user jit.pwindow 128 176 82 62 0 1 0 0 1 0;
> #P newex 129 137 230 196617 jit.qt.movie @autostart 0 @loopreport 1 @loop 1;
> #P connect 3 0 0 0;
> #P connect 2 0 7 0;
> #P connect 4 0 3 0;
> #P connect 6 0 0 0;
> #P connect 0 0 1 0;
> #P connect 8 0 0 0;
> #P connect 0 1 2 0;
> #P connect 0 1 5 0;
> #P window clipboard copycount 9;
>
>
>
> v a d e //
>
> http://www.vade.info
> abstrakt.vade.info
>
>
>
>
> v a d e //
>
> http://www.vade.info
> abstrakt.vade.info
>
>
>
>
>
>

#101413
Apr 10, 2007 at 6:44am

“poop”

Thank you sir for testing. What happens with @loop 0 ?

On Apr 10, 2007, at 2:30 AM, keith manlove wrote:

> Mac OS X 10.4.9 PPC, QT 7.1.5, Max 4.6.2, Jitter 1.6.2 here
>
> Couldn’t seem to replicate your problem here… tried all sorts of
> different ways to make it not happen… I remember this problem in
> 1.5, but I think it’s fixed. Only difference I see is the 1.6.3b2…
> sorry…
>
> Keith
>
>
> On 4/10/07, vade wrote:
>> oops! Sorry!
>>
>> Mac OS X 10.4.9, QT 7.1.5, Max 4.6.2, Jitter 1.6.3b2
>>
>>
>>
>> On Apr 10, 2007, at 1:37 AM, vade wrote:
>>
>>
>> I believe ive seen this posted on the list – but could not find any
>> reference, but @loopreport 1 seems to be broken with jit.qt.movie?
>>
>> this patch does not report uh, anything other than the file being
>> read in.
>>
>> #P window setfont “Sans Serif” 9.;
>> #P window linecount 1;
>> #P message 192 108 56 196617 asyncread;
>> #P newex 349 190 32 196617 print;
>> #P message 149 108 33 196617 start;
>> #P newex 315 164 32 196617 print;
>> #P toggle 60 60 15 0;
>> #P newex 60 79 51 196617 qmetro 2;
>> #P newex 349 161 82 196617 route loopnotify;
>> #P user jit.pwindow 128 176 82 62 0 1 0 0 1 0;
>> #P newex 129 137 230 196617 jit.qt.movie @autostart 0 @loopreport
>> 1 @loop 1;
>> #P connect 3 0 0 0;
>> #P connect 2 0 7 0;
>> #P connect 4 0 3 0;
>> #P connect 6 0 0 0;
>> #P connect 0 0 1 0;
>> #P connect 8 0 0 0;
>> #P connect 0 1 2 0;
>> #P connect 0 1 5 0;
>> #P window clipboard copycount 9;
>>
>>
>>
>> v a d e //
>>
>> http://www.vade.info
>> abstrakt.vade.info
>>
>>
>>
>>
>> v a d e //
>>
>> http://www.vade.info
>> abstrakt.vade.info
>>
>>
>>
>>
>>
>>

v a d e //

http://www.vade.info
abstrakt.vade.info

#101414
Apr 10, 2007 at 6:59am

it notifies, but does not loop

On 4/10/07, vade wrote:
> “poop”
>
> Thank you sir for testing. What happens with @loop 0 ?
>
>
>
> On Apr 10, 2007, at 2:30 AM, keith manlove wrote:
>
> Mac OS X 10.4.9 PPC, QT 7.1.5, Max 4.6.2, Jitter 1.6.2 here
>
> Couldn’t seem to replicate your problem here… tried all sorts of
> different ways to make it not happen… I remember this problem in
> 1.5, but I think it’s fixed. Only difference I see is the 1.6.3b2…
> sorry…
>
> Keith
>
>
> On 4/10/07, vade
wrote:
> oops! Sorry!
>
> Mac OS X 10.4.9, QT 7.1.5, Max 4.6.2, Jitter 1.6.3b2
>
>
>
> On Apr 10, 2007, at 1:37 AM, vade wrote:
>
>
> I believe ive seen this posted on the list – but could not find any
> reference, but @loopreport 1 seems to be broken with jit.qt.movie?
>
> this patch does not report uh, anything other than the file being read in.
>
> #P window setfont “Sans Serif” 9.;
> #P window linecount 1;
> #P message 192 108 56 196617 asyncread;
> #P newex 349 190 32 196617 print;
> #P message 149 108 33 196617 start;
> #P newex 315 164 32 196617 print;
> #P toggle 60 60 15 0;
> #P newex 60 79 51 196617 qmetro 2;
> #P newex 349 161 82 196617 route loopnotify;
> #P user jit.pwindow 128 176 82 62 0 1 0 0 1 0;
> #P newex 129 137 230 196617 jit.qt.movie @autostart 0 @loopreport 1 @loop 1;
> #P connect 3 0 0 0;
> #P connect 2 0 7 0;
> #P connect 4 0 3 0;
> #P connect 6 0 0 0;
> #P connect 0 0 1 0;
> #P connect 8 0 0 0;
> #P connect 0 1 2 0;
> #P connect 0 1 5 0;
> #P window clipboard copycount 9;
>
>
>
> v a d e //
>
> http://www.vade.info
> abstrakt.vade.info
>
>
>
>
> v a d e //
>
> http://www.vade.info
> abstrakt.vade.info
>
>
>
>
>
>
>
>
> v a d e //
>
> http://www.vade.info
> abstrakt.vade.info
>
>
>
>
>
>

#101415
Apr 10, 2007 at 8:22am

I had the same problem. If you manually set loop to 0 and then back
to 1 it starts working same versions.

#101416
Apr 10, 2007 at 12:37pm

except you no longer get loopnotified when loop is 0, which you did
prior. Shoot.

has this been reported as a but yet?

On Apr 10, 2007, at 4:22 AM, Christopher Overstreet wrote:

> I had the same problem. If you manually set loop to 0 and then back
> to 1 it starts working same versions.

v a d e //

http://www.vade.info
abstrakt.vade.info

#101417
Apr 10, 2007 at 12:47pm

Thanks for the reports, gentlemen. It appears to only affect
“asyncread”, not “read” (which is the present workaround). And it’s
been fixed for the next release.

jb

Am 10.04.2007 um 14:37 schrieb vade:

> except you no longer get loopnotified when loop is 0, which you did
> prior. Shoot.
>
> has this been reported as a but yet?

#101418
Apr 10, 2007 at 1:15pm

ah! I should have tried with read! Thanks Jeremy – look forward to
the next beta.

*bug not but below, obviously :)

On Apr 10, 2007, at 8:58 AM, Jeremy Bernstein wrote:

> Thanks for the reports, gentlemen. It appears to only affect
> “asyncread”, not “read” (which is the present workaround). And it’s
> been fixed for the next release.
>
> jb
>
> Am 10.04.2007 um 14:37 schrieb vade:
>
>> except you no longer get loopnotified when loop is 0, which you
>> did prior. Shoot.
>>
>> has this been reported as a but yet?
>

v a d e //

http://www.vade.info
abstrakt.vade.info

#101419

You must be logged in to reply to this topic.