Stone Design Forums

The specific problem is with image overlays occurs when you select an area in the center of a clip and overlay an image. If you attempt to click on the image and move it around, the clip suddenly jumps back to the start of the entire clip outside of the area you have selected. With the other bug I just posted, this potentially renders images overlayed on the middle parts of clips uneditable.

My work around has been to define an overlay effect at the start of the clip. I then apply that effect to the clip and sub the image. A bit of a complex process.

I am on a MacBook Pro with OSX 10.4.7 and QT 7.1.

I have other bug reports but the hour grows late.

Be sure to STOP the video (space bar is short cut) before you drag image - the playhead should be inbetween the fade-in and fade-out marker if you are trying to set the middle parameters. Note that the playhead moves when you move the fade-in or fade-out markers in the effects area.

I just reproduced the problem after stopping the video (which I had always been doing). I click on the item I want to move. It does move slightly. Then the video jumps back to the start of the entire clip.

Are you testing on Intel machines? I'm on a 15" macbook pro. I have experienced the problem consistently using both OSX 10.4.6 and 10.4.7 with QT 7.1.

The fact that I get slight movement suggests something is starting to work and then blows up.

Does the image have fade in and fade outs?
I'll bet all this stuff is connected, so I'll see what I can fix today.
I'm on a macbook pro 17

No fade in or fade out. I just tried this on a virgin project where I attempted to overlay an image and then adjust. What I noticed is that the playback marker jumps back to about 1 second into the clip when I click on the image. If I set the start of effect at that exact point, then I am able to move the image around although the cursor still jumps around.

Further experimentation shows that although the cursor jumps back to around the 1 second mark, the overlay image seems to move in accord with my mouse. In other words, I am moving the image without being able to see it.

My solution has been to create effects at the start of clips, save them as myFX and then apply those where I want to in the clip.

Yeah - I totally see the problem now...

Bud & Blond -

Definitely was a bug, which caused all sorts of nastiness - but that's all fixed now! Moreover, you can drag iTunes, Audio clips, Midi, or even Movies with Soundtracks onto the Audio Tracks panel to quickly insert the audio into your composition.

ftp://ftp.swcp.com/pub/tmp/a/Videator.dmg.gz

or our regular .Mac site - which I'm happy to say has broken 250 GIGS of downloads for the last two months running!

I'm afraid this one did not work for me. I still get the same bug on my test project.

1. Select a portion of the clip that does not contain either the beginning or end of the clip.

2. lay an image over it.

3. Attempt to move the image with your mouse (not having set any fades or anything).

4. The movie play head will jump back to about 1 second into the movie and the image will disappear.

If you scroll back to the selection over which you placed the image, you will see that it moved.

Unless you mousedown RIGHT on the center, the image will move so that the new center is your mousedown point - that's the whole point of the cross-hair (especially when they are lots of effects showing!).

I cannot duplicate your "jump back to about 1 second" bug though - the playhead stays put when I mouse around on the newly added image.

The bug is reproduceable. Plus, I get your behavior also. If I record off of the isight camera or take a pre-recorded MOV with a data rate in the range of say, 1 megabits/second, then graphical editing works as you describe. In fact, it's fantastic.

If I load a mov recorded directly by my camera, where the data rate is 11.16 mbits/second, I get the breakage I describe. I suspect I'm blasting past the memory allocated to the effect and just breaking it.

I have read that the memory model in quicktime is caught between two models, one with garbage collection and one where you specify the memory allocated to the plugin.

This may be too much of an edge case for you. If you'd like, I'll send an example movie or make it available on a server for download.

Sure throw it on a Server - it could be a QT bug in which case Apple would want to know.

I sent the URL by email from my fpgibson AT gmail account to andrew AT stone. Here's some more diagnosis.

On the file I sent, modal editing of image overlay effects applied to part of the clip works just fine. I can edit fades, etc., and all shows up on screeen as I put new numbers in the boxes. So, that is a fall back and substantially better than before.

However, graphical editing continues to display the bug I described. I wonder if that does not have something to do with issues in the QT memory model. Here's an article that describes one issue an imovie plugin developer is facing in a conflict between carbon and cocoa memory models:

http://www.imovieplugins.com/B151616523 ... index.html

I suspect you are not using the carbon memory model. At any rate, I would appreciate your perspectives

I opened the Movie in Safari, chose Save As... but it only made an 8 k file (a link to the movie) - what's the trick of actually saving the movie from Safari, do you know?

If you click on the downward pointing triangle in the lower right corner, you will see an option to save as quicktime movie once the movie stops loading. That works (I assume you have QT Pro). Saving as source does not.

Alternatively, if you received the email in a web based mail app, you can right click (control click) on the link and save as source.

OK - that's a great tip - it's 62.8 megs, right?

Now, remind me of what steps I need to take to duplicate the bug!