Corrupt theme/kenBurn preview and final result

Question

Level 1

13 points

Corrupt theme/kenBurn preview and final result

Hello,

since last update of OS (10.4.9) and QuickTime 7.1.5 I have big problem with themes and kenBurn effects: the preview looks corrupt and also the final rendering.

Please help. I have to finish my movie soon.

mac Mini 1.25 GHz Mac OS X (10.4.9)

mac Mini 1.25 GHz, Mac OS X (10.4.3), iMovie HD 6.0.3

Posted on Mar 22, 2007 3:20 PM

Reply

Answer 1

SDIllini

Level 6

16,675 points

Mar 22, 2007 3:45 PM in response to Denis Smolin

Unfortunately, if you started your movie prior to updating your mac, you may just be stuck with what you have.

It might actually be easier to start over.

But, try repairing permissions first using the disk Utility.

Sue

Reply

Answer 2

Denis Smolin Author

Level 1

13 points

Mar 26, 2007 12:04 PM in response to Denis Smolin

Hello,

thx for answer.

I tried to repair the permissions.
If this wouldn't help: can I transfer the clips from current to the new project?

Reply

Answer 3

Denis Smolin Author

Level 1

13 points

Mar 26, 2007 12:20 PM in response to Denis Smolin

Hello again,

I run the permissions reparation task: problem is still there.
I creates a new project without any clips: problem is still there - the theme preview (the drop zones are empty) is still corrupt.

Reply

Answer 4

SDIllini

Level 6

16,675 points

Mar 26, 2007 12:21 PM in response to Denis Smolin

Did you update Tiger and iMovie 6 as well?

Reply

Answer 5

Denis Smolin Author

Level 1

13 points

Mar 26, 2007 3:21 PM in response to Denis Smolin

Hello,

I've apply the last OS (10.4.9) and QuickTime 1.7.5 updates. The iMovie wasn't updated (still 6.0.3).

PS: not every theme-transition has corrupt preview but some (is reproduceble).

Reply

Answer 6

Mar 26, 2007 4:23 PM in response to Denis Smolin

What do you mean by "the preview looks corrupt and also the final rendering"? What exactly happens? Is the image changed in some way?

How is it corrupt? Does the image not play?

If you can post a example we can look at, that would be great.

Karl

Reply

Answer 7

Denis Smolin Author

Level 1

13 points

Mar 27, 2007 9:48 AM in response to Denis Smolin

http://denissmolin.gmxhome.de/iMovieError.jpg
http://denissmolin.gmxhome.de/iMovieError2.jpg

Reply

Answer 8

Mar 27, 2007 12:26 PM in response to Denis Smolin

Wow! Those are really awful.

When I see images like that, containing multiple chunks of images, my first thought is some kind of memory problem, where data gets corrupted in RAM — or while swapping data in RAM and virtual memory.

How much RAM does your Mac have?

Have you added any third-party RAM to your Mac or are you running Apple-only RAM?

Have you run any RAM diagnostics to find out if your RAM is flawed? I'd suggest memtest, available at versiontracker.com.

http://www.versiontracker.com/dyn/moreinfo/macosx/17156

But I'd first run Disk Utility to make sure the hard drive is functioning properly. You can Verify the drive in Disk Utility, but to Repair it — if problems are found — requires booting up your Mac from the Mac OS X Installer DVD.

There should also be a Hardware Test on one of the disks that came with your Mac.

Hopefully someone has seen a similar image and can pinpoint the cause.

Oh, be sure to rule out third-party QuickTime and iMovie add-ons that might be causing trouble for iMovie. More here:
http://discussions.apple.com/message.jspa?messageID=4030731#4030731

Karl

Reply

Answer 9

Akickr

Level 1

5 points

Mar 27, 2007 1:16 PM in response to Denis Smolin

I am getting the exact same images after I import a photo into timeline, it looks ok until it renders the ken burns effect. After reading through some other posts...tonight I am going to try to create a new movie on my local hard drive, (right now I am saving imove to an external). Someone said try to export the photo's from iphoto save as a jpeg and drag into imovie from desktop. Remove my music I have in my project. Repair permissions etc. I am wondering if it is a RAM thing. I have a 512 and a 256 in my emac. I am ok according to the spec's.

I like the old imovie...this is very frustrating. If I find any solution I will post here.

Reply

Answer 10

SDIllini

Level 6

16,675 points

Mar 27, 2007 2:17 PM in response to Karl Petersen

Karl:

Both the OP and the other poster do not seem to have updated Tiger yet. Do you think that could be a factor?

Also, I have seen several posts where folks have updated QT, Tiger and iTunes and since that they have had problems. is that a possible factor?

Just thought I'd ask the Guru!

:)Sue

Reply

Answer 11

Denis Smolin Author

Level 1

13 points

Mar 27, 2007 3:22 PM in response to Karl Petersen

Hi,

my macMini have 1GB RAM (is replacement for the 512 MB before).
The MacOS X is installed on external FW drive miniPartner (is formatted as HFS+ with journaling on).

I've removed all non-apple QT and iMovie plugins.

I don't think that macMini memory is defect.
The harddrive is already checked by the harddisk utility.

Reply

Answer 12

Mar 27, 2007 8:01 PM in response to Denis Smolin

I don't think that macMini memory is defect.

Are you sure the RAM is okay? Has it been tested? Remember, RAM defects can remain hidden until a software upgrade or new application. The problems were there before, of course, but not revealed.

Karl

Reply

Answer 13

Mar 27, 2007 8:08 PM in response to SDIllini

Karl:

Both the OP and the other poster do not seem to have
updated Tiger yet. Do you think that could be a
factor?

Also, I have seen several posts where folks have
updated QT, Tiger and iTunes and since that they have
had problems. is that a possible factor?

I don't know, Sue. There are so many factors it's hard to say. Lots of times a problem occurs after an upgrade but isn't necessarily caused by the upgrade. And for every person who thinks an upgrade caused a problem there are thousands for whom the upgrade worked fine.

If there's an underlying problem, of course, an upgrade my exacerbate it.

Karl

Reply

Answer 14

SDIllini

Level 6

16,675 points

Mar 28, 2007 4:46 AM in response to Karl Petersen

Thank you, Karl.

Reply

Answer 15

Denis Smolin Author

Level 1

13 points

Mar 28, 2007 1:05 PM in response to Karl Petersen

Memtest version 4.2 (32-bit)
Copyright (C) 2004 Charles Cazabon
Copyright (C) 2004, 2005, 2006 Tony Scaminaci (Macintosh port)
Licensed under the GNU General Public License version 2 only

Mac OS X 10.4.9 (8P135) running in single user mode
Memory Page Size: 4096
System has 1 PPC processor(s) with Altivec
Requested memory: 982MB (1029939200 bytes)
Available memory: 982MB (1029939200 bytes)
NOTE: Memory request is too large, reducing to acceptable value...
Allocated memory: 954MB (1001100864 bytes) at local address 0x02008000
Attempting memory lock... locked successfully
Splitting allocated memory into 2 comparison buffers...
Buffer A: 477MB (500550432 bytes) starts at local address 0x02008000
Buffer B: 477MB (500550432 bytes) starts at local address 0x1fd64b20

Running 1 test sequence... (CTRL-C to quit)

Test sequence 1 of 1:

Running tests on entire 954MB region...
Stuck Address : ok
Linear PRN : ok
Running comparison tests using 477MB buffers...
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok

All tests passed! Execution time: 4637 seconds.

Reply