matteosistisette

open a video file (clicking on the "read" message and browsing for a file on my disk),

and set some starting and ending loop points by using the looppoints parameter.

The movie starts looping between the loop points.

Now I set the "loopreport" to 1, so the movie outputs a "loopnotify" message on its right outlet every time it loops over.

The problem is, it doesn't *always* output the loopnotify message: every once in a while a notify is just lost.

I open the help patch of jit.qt.movie,
open a video file (clicking on the "read" message and browsing for a file on my disk),
I set the loop parameter on 1,
and set some starting and ending loop points by using the looppoints parameter.

Has anyone experienced this?
What may be the problem?

loopnotify-not-alwaya-notifies

I think I've probably understood how it works.

I guess that whenever you send a bang to jit.qt.movie, it outputs the loopnotify message if it is currently in the last (or first) frame. Is that right?

So since the metro is approximately but not perfectly synchronized with the playing of the movie itself, it may happen at times that 2 bangs fall within the same frame or that a frame does not receive a bang at all.

I just thought the notification was driven directly by the internal playing of the movie file (that can be playing even if yoy're not sending it bangs).

I just thought the notification was driven directly by the internal playing of the movie file (that can be playing even if yoy're not sending it bangs).
I wish it were so indeed :)


No, this is not how loopnotify works. It uses QuickTime callbacks to 

inform the object when the movie has hit the end. If you can provide 

more information about how to reproduce the issue, we'll look into 

it. I've attached the trusty bug reporting guidelines.

===================================================

Please report any problems you experience with clear and complete

information, including steps to reproduce, software and system

information, and where possible, an isolated example patch and crash

log. Something like the following would be ideal. This makes it

easier for us to find and fix the problems you experience. Without

such clear and complete information, it is less likely we will be

Provide a descriptive summary of the issue.

In numbered format, detail the exact steps taken to produce the bug.

Describe what you expected to happen when you executed the steps above.

Please explain what actually occurred when steps above are executed.

Describe circumstances where the problem occurs or does not occur,

such as software versions and/or hardware configurations.

Provide additional information, such as references to related

problems, workarounds and relevant attachments.

Am 27.07.2007 um 20:52 schrieb matteo sisti sette:

> I think I've probably understood how it works.

> I guess that whenever you send a bang to jit.qt.movie, it outputs 

> the loopnotify message if it is currently in the last (or first) 

> So since the metro is approximately but not perfectly synchronized 

> with the playing of the movie itself, it may happen at times that 2 

> bangs fall within the same frame or that a frame does not receive a 

> I just thought the notification was driven directly by the internal 

> playing of the movie file (that can be playing even if yoy're not 

No, this is not how loopnotify works. It uses QuickTime callbacks to  
inform the object when the movie has hit the end. If you can provide  
more information about how to reproduce the issue, we'll look into  
it. I've attached the trusty bug reporting guidelines.

Please report any problems you experience with clear and complete
information, including steps to reproduce, software and system
information, and where possible, an isolated example patch and crash
log. Something like the following would be ideal. This makes it
easier for us to find and fix the problems you experience. Without
such clear and complete information, it is less likely we will be
able to.

Summary:
Provide a descriptive summary of the issue.

Steps to Reproduce:
In numbered format, detail the exact steps taken to produce the bug.

Expected Results:
Describe what you expected to happen when you executed the steps above.

Actual Results:
Please explain what actually occurred when steps above are executed.

Regression:
Describe circumstances where the problem occurs or does not occur,
such as software versions and/or hardware configurations.

Notes:
Provide additional information, such as references to related
problems, workarounds and relevant attachments.

>
> Hi,
>
> I think I've probably understood how it works.
>
> I guess that whenever you send a bang to jit.qt.movie, it outputs  
> the loopnotify message if it is currently in the last (or first)  
> frame. Is that right?
>
> So since the metro is approximately but not perfectly synchronized  
> with the playing of the movie itself, it may happen at times that 2  
> bangs fall within the same frame or that a frame does not receive a  
> bang at all.
>
> I just thought the notification was driven directly by the internal  
> playing of the movie file (that can be playing even if yoy're not  
> sending it bangs).
> I wish it were so indeed :)


Is everything current? I had this probably about 6 months ago, (which drove

me nuts) and it was fixed with an update.

On 7/27/07 10:10 AM, "matteo sisti sette" 

> open a video file (clicking on the "read" message and browsing for a file on

> and set some starting and ending loop points by using the looppoints

> The movie starts looping between the loop points.

> Now I set the "loopreport" to 1, so the movie outputs a "loopnotify" message

> on its right outlet every time it loops over.

> The problem is, it doesn't *always* output the loopnotify message: every once

Is everything current?  I had this probably about 6 months ago, (which drove
me nuts) and it was fixed with an update.

On 7/27/07 10:10 AM, "matteo sisti sette" 
wrote:

>
> Hi,
>
> I open the help patch of jit.qt.movie,
> open a video file (clicking on the "read" message and browsing for a file on
> my disk),
> I set the loop parameter on 1,
> and set some starting and ending loop points by using the looppoints
> parameter.
>
> The movie starts looping between the loop points.
>
> Now I set the "loopreport" to 1, so the movie outputs a "loopnotify" message
> on its right outlet every time it loops over.
>
> The problem is, it doesn't *always* output the loopnotify message: every once
> in a while a notify is just lost.
>
> Has anyone experienced this?
> What may be the problem?
>
> Thanks in advance
> Matteo Sisti Sette
>

Quote: Christopher Overstreet wrote on Fri, 27 July 2007 19:39

----------------------------------------------------

> Is everything current? I had this probably about 6 months ago, (which drove

> me nuts) and it was fixed with an update.

It's the trial version I downloaded 4 or 5 days ago from the official site (I don't have it at hand now to check out the version)

Quote: Christopher Overstreet wrote on Fri, 27 July 2007 19:39
----------------------------------------------------
> Is everything current?  I had this probably about 6 months ago, (which drove
> me nuts) and it was fixed with an update.
>

It's the trial version I downloaded 4 or 5 days ago from the official site (I don't have it at hand now to check out the version)


> No, this is not how loopnotify works. It uses QuickTime

> inform the object when the movie has hit the end.

Oh... then it should indeed work the way I expected

> more information about how to reproduce the issue, we'll

> it. I've attached the trusty bug reporting guidelines.

I think I have provided almost all the information mentioned in the guidelines: steps to reproduce, expected behaviour, actual behaviour; the test patch is just the help patch for jit.qt.movie

- current TRIAL version of Max/MSP/Jitter freshly downloaded 4-5 days ago from Cycling74.com

*** UPDATE (of my report, not of the software):

I played around with different values of the looppoints. Sometimes, instead of experiencing lost nitifies, I experience duplicated notifies: i.e., when the loops starts over I get sometimes 2 "loopnotify" messages at once.

There's one think I am confused about, however.

Let's forget for a moment that jit.qt.movie is sometimes giving duplicated or missing loopnotify messages.

When I stop the metro that bangs the jit.qt.movie but DON'T stop the movie itself, it stops outputting the loopnotify messages. That may be even desirable in some cases, but isn't it a bit strange? The movie is supposed to be still playing even if I don't bang it to output the matrix.

Suppose the looppoint is reached just a few milliseconds after the last bang it has received: how does it know whether I will or not bang it again within a few milliseconds more?

And suppose I want to output the video at a reduced framerate (say 1 fps or even less) while still playing it at rate 1... how can I ensure it will still be reporting the loopnitify's? (without wasting cpu time filling matrices that won't be used)

> No, this is not how loopnotify works. It uses QuickTime
> callbacks to 
> inform the object when the movie has hit the end. 

> If you 
> can provide 
> more information about how to reproduce the issue, we'll
> look into 
> it. I've attached the trusty bug reporting guidelines.

The only things I forgot to mention are:
- I am using Windows XP
- quicktime Pro 7 installed
- current TRIAL version of Max/MSP/Jitter freshly downloaded 4-5 days ago from Cycling74.com

*** UPDATE (of my report, not of the software):
I played around with different values of the looppoints. Sometimes, instead of experiencing lost nitifies, I experience duplicated notifies: i.e., when the loops starts over I get sometimes 2 "loopnotify" messages at once.
***

There's one think I am confused about, however.
Let's forget for a moment that jit.qt.movie is sometimes giving duplicated or missing loopnotify messages.
When I stop the metro that bangs the jit.qt.movie but DON'T stop the movie itself, it stops outputting the loopnotify messages. That may be even desirable in some cases, but isn't it a bit strange? The movie is supposed to be still playing even if I don't bang it to output the matrix.
Suppose the looppoint is reached just a few milliseconds after the last bang it has received: how does it know whether I will or not bang it again within a few milliseconds more?
And suppose I want to output the video at a reduced framerate (say 1 fps or even less) while still playing it at rate 1... how can I ensure it will still be reporting the loopnitify's? (without wasting cpu time filling matrices that won't be used)


On 28 juil. 07, at 17:48, matteo sisti sette wrote:

> When I stop the metro that bangs the jit.qt.movie but DON'T stop 

> the movie itself, it stops outputting the loopnotify messages. That 

> may be even desirable in some cases, but isn't it a bit strange? 

> The movie is supposed to be still playing even if I don't bang it 

This is the way it's supposed to work. jit.qt.movie have it's own 

time mechanism in order to make sure that the length the movie will 

be the same no matter how often you redraw it (imagine you have a 

slow computer, the length of your movie won't be different even if 

your computer is not able to redraw every frames). I may suggest your 

reading the tutorials, those kinda things are pretty well explained 

> When I stop the metro that bangs the jit.qt.movie but DON'T stop  
> the movie itself, it stops outputting the loopnotify messages. That  
> may be even desirable in some cases, but isn't it a bit strange?  
> The movie is supposed to be still playing even if I don't bang it  
> to output the matrix.

This is the way it's supposed to work. jit.qt.movie have it's own  
time mechanism in order to make sure that the length the movie will  
be the same no matter how often you redraw it (imagine you have a  
slow computer, the length of your movie won't be different even if  
your computer is not able to redraw every frames). I may suggest your  
reading the tutorials, those kinda things are pretty well explained  
there.

Quote: Emmanuel Jourdan wrote on Sat, 28 July 2007 10:20

> On 28 juil. 07, at 17:48, matteo sisti sette wrote:

> > When I stop the metro that bangs the jit.qt.movie but DON'T stop 

> > the movie itself, it stops outputting the loopnotify messages. That 

> > may be even desirable in some cases, but isn't it a bit strange? 

> > The movie is supposed to be still playing even if I don't bang it 

> This is the way it's supposed to work. jit.qt.movie have it's own 

> time mechanism in order to make sure that the length the movie will 

> be the same no matter how often you redraw it (imagine you have a 

> slow computer, the length of your movie won't be different even if 

> your computer is not able to redraw every frames).

That's exactly why I would expect the loopnotify to be output independently of sending or not sending the bangs to jit.qt.movie.

I will read the tutorial again, but I don't think there was the answer to this question.

Quote: Emmanuel Jourdan wrote on Sat, 28 July 2007 10:20
----------------------------------------------------
> On 28 juil. 07, at 17:48, matteo sisti sette wrote:
>
> > When I stop the metro that bangs the jit.qt.movie but DON'T stop  
> > the movie itself, it stops outputting the loopnotify messages. That  
> > may be even desirable in some cases, but isn't it a bit strange?  
> > The movie is supposed to be still playing even if I don't bang it  
> > to output the matrix.
>
> This is the way it's supposed to work. jit.qt.movie have it's own  
> time mechanism in order to make sure that the length the movie will  
> be the same no matter how often you redraw it (imagine you have a  
> slow computer, the length of your movie won't be different even if  
> your computer is not able to redraw every frames). 

I will read the tutorial again, but I don't think there was the answer to this question.


> reading the tutorials, those kinda things are pretty 

Thank you for the suggestion. I had already read the tutorial, and the help patch and the html reference about jit.qt.movie.

The kinda things regarding jit.qt.movie timing (internal playing rate vs banging it to get the output etc) are indeed pretty well explained in the tutorial, and I had already understood them.

However, the kinda things regarding the loopnotify message are not even mentioned in the tutorial. There's no occurrence of the word "loopnotify" throughout the whole PDF.

The help patch and html reference explain that by setting an appropriate parameter of jit.qt.movie a message (something like a "loopreport 1", I don't have it at hand now), jit.qt.movie will output a "loopnotify" message every time the looppoint is reached; but they don't explain why it does not output loopnotify if you don't periodically bang it (even if the movie IS internally playing), nor whether there is a minimum rate you have to bang it in order to get the notifies.

However I am afraid I should have started a separate thread about this question, instead of writing it in the thread I had started about the missing/duplicate loopnotify.

It is not completely unrelated, though...

Quote: Emmanuel Jourdan wrote on Sat, 28 July 2007 10:20
----------------------------------------------------
> I may suggest your  
> reading the tutorials, those kinda things are pretty 
> well explained  
> there.
----------------------------------------------------

However I am afraid I should have started a separate thread about this question, instead of writing it in the thread I had started about the missing/duplicate loopnotify.
It is not completely unrelated, though...


loopnotify not alwaya notifies?