Glitches in cross dissolves (5.0.4 vs 5.1.2)

ksteiger

ksteiger

Well-known member
I know this has been covered I just can't find the right posts...been searching for an HOUR!
I have 4 projects created in 5.0.4 (all nature/outdoor related) that started creating duplicate frames in all new cross-dissolves after upgrading to 5.1.2. I know there was an Apple technical bulletin referenced here abvout how to properly re-import from the original P2 files (don't EVER EVER EVER throw them away)

Also I see that there is a newer version 5.1.3 available and I am scared S..TLESS to change again as the upgrade also trashed my BorisGrafitii OEM nstall (Apple was extremely unhelpful with this issue and Boris tech support hung up on me...) Should I upgrade to this newer version before re-importing? Or is it possible that the 5.1.3 upgrade will fix my cross dissolve problem without having to re-import? Any help would be greatly appreciated.
 
Actually, the most recent version is 5.1.4. 5.1.3 is buggy and Apple pulled it within days.

I would upgrade to 5.1.4, trash your prefs and your render files and then try to apply the cross-dissolves again.

Ned Soltz
 
Shooting 720 24PN to P2 4 gig cards.
Using G4 powerbook in the field with PCMCIA slot

I have always made a disc image of the P2 cards on either the laptop desktop or to an external FW800 drive. After that I imported into FCP from that disc image. I had one glitch early on (16 or so small dots neatly spread throughout the image) which was fixed by reimporting from the DVD back up. (I am so paranoid I always burn two DVDs off the disc image before deleting.) Of course I copied the file back to a drive before re-importing. I have never had problems with cross dissolves before. As soon as I switched to 5.1.2 I experienced duplicate frames in the body of the transition.
 
We have been very happy with 5.1.2, but as I recall a simple workaround for the dissolve problem (we ran into it with 5.0.4) was to do something that would force a render, but not alter the image perceptably, like setting the opacity of the two clips to 99, after the render, the disolve displays properly.

-tim
 
Still not working even with the 99% opacity workaround.. It wants to duplicate the frame at the beginning (and/or end) of the transition replacing the following one with the dupe. This was working JUST FINE before 5.1.3!!! And so was my Boris Grafitti plug in.
I don't flame but Apple seems to be pretty cavalier in their attitude towards problems but gung ho in convinvinbg people how vastly superior their products are in their advertising. I edited on a PC for YEARS before I ever touched a Mac and...well let's just say that I used to enjoy wonderful support from Canopus when I was using a humble DV Storm 2 and Premiere Pro. Quite frankly I didn't have to call them nearly as much as I do with Apple...and they never tried to charge me $700 for "Professional Application Support".

Any suggestions?

BTW I am a techy guy who always exhausts all resources before making a tech support call and I am definitely not a whiner. But this one has me smackin' my head on the wall.
:dankk2:
 
Last edited:
Go with 5.1.4, it's safe, fixes it. 5.1.3 was upgraded to 5.1.4 after several days, not the same day. If you don't like FCP, by all means, go back to a PC. But try the 5.1.4 upgrade first. I can assure you the 5.1.3 upgrade was a fluke, Apples updates don't normally break things.
 
960 vs 1280 in 720P

960 vs 1280 in 720P

OK so I reimported all my P2 files to fix the dissolve issue (which it did) Upon doing a "get info" on some of my clips (old and current) I see that some are stamped as 1280 and some as 960 with "little endian" or "big endian" settings in the codec.The 960s appear squashed in the preview but seem to be interchangable when used in a project. Having gone through several of these projects I cannot find where the difference ocurred during P2 import. Can any possibly explain what I am missing?
Thanks.

PS when searching through folders and looking at the filenames of clips all the new ones do not display the .mov extension. Beuhler?:Drogar-Smoke(DBG):
 
You must log in or register to reply here.
Back
Top