I Swear I Could Just Fucking KILL Premiere Pro!

[Wheee_It's_Me!]

I all decided to go and try out Premiere Pro, thinkin, well, this should make things easier...OH...MY...FUCKING...GAWD...

I was all doin a lil chop and paste lip synch job, took about 3 and a half hours to make and WOW, it looked PERFECT, so I saved it, checked it over a few more times just to be sure, yeah, AWESOME! So then I thought, "Hrmmm...I wonder what it looks like BIGGER." So I resized the monitor window...yeah, BIG mistake. All a sudden, all the lil cut up clips, altered themselves! Just, out of the fucking blue they decided to go all screwy and just couldn't seem to unfuck themselves. So basically all the lil snipped up portions that had like 3 frames of the mouth closed, suddenly had 2 frames closed and the end frame suddenly became an open mouth. And then other frame segments with like 3 frames of wide open mouth suddenly because 1 frame of wide and 2 frames of closed...AAAAAAAAAHHHHHHH FFFFFFFUUUUCCCCKKKK!!!!

I was so gawd damn pissed off I took a blank CDR and crushed it to pieces in my bare hand...and now there's shiny lil bits of foil all over the place...*sigh*...that's it, I'm never gonna use Premiere Pro again.

And in case you're wondering, the clips were all 23.98 and the frame rate of the project was set the same and the res on both the project and source clips was exactly the same as well, so that can't be it. I also tried doing about 20 steps of undo, still the same problem. Tried to export hoping the problem was just in the monitor window, no. Tried to exit the program and go back in and reopen, no, same thing. And it's not a problem with my system, I've got over 2 GB of Infineon ECC registered memory and at the time I wasn't running any other programs.

[Scintilla]

And in case you're wondering, the clips were all 23.98 and the frame rate of the project was set the same and the res on both the project and source clips was exactly the same as well, so that can't be it.

... 23.98? I thought Premiere didn't handle 23.98 very well, and 23.976 almost not at all.

[Wheee_It's_Me!]

And in case you're wondering, the clips were all 23.98 and the frame rate of the project was set the same and the res on both the project and source clips was exactly the same as well, so that can't be it.

... 23.98? I thought Premiere didn't handle 23.98 very well, and 23.976 almost not at all.

Well it seems to be fucking up even worse now. I managed to fix most of the lil damaged portions (although it doesn't look nearly as good as it did originally) and I managed to export a good sequence...only now check this out:

http://www.backwater-productions.net/_video/baka.avi
(1.97mb)
(the text still needs to be edited out and the black flashes will be replaced with a better effect, probably some kind of screen blur effect and the lip synch doesn't look perfect yet)

o_O

Can anyone tell me how exactly it's managing to screw up the picture size? I mean, IT'S THE SAME CLIP! How on earth is it managing to do that? I checked the clips in Premiere, they're both using the same file, with the same speed, with the same settings and yet...what's it doin...*sigh*...I think once I get this one portion semi acceptable I'm just gonna go back to using teh old premiere, I don't care if the new one handles better speed wise on my system or not cause it's just not worth it if it's gonna try and think behind my back and fuck everything up.

[Wheee_It's_Me!]

Okay I fixed it...sorta, although I still don't understand what the hell it's doing.

For some reason you can like "speed up" or "slow down" a clip but then you can like not constrain it to the timeline...which doesn't make any fucking sense AT ALL to me (cause if you slowed it down or sped it up, how could it NOT have an effect on the clip length). But apparently it has something to do with the picture size. I dunno, maybe the control also doubles as a kind of clip zoom in/out feature or something. o_O

I'm also wondering if the original problem was a sole product of premiere or a combination of Premiere and DivX encoded footage. I'm going to try and do some stuff with Huffyuv encoded clips and see if that works any better. Huffyuv used to be great for editing because it was fast, but the file sizes were always huge. I was hoping with the speed of my new system I'd be able to edit using MPEG-4 encoded footage, but if it's gonna cause Premiere to fuck up, well, I may just be shit out of luck.

I'll also try using a different frame rate, see if that makes any difference.

[7sigma]

Dude, I'm sorry for your trouble, but you were working with DivX encoded footage at 23.98fps in Premiere. You ASKED for trouble . Good thing everything fell into place.

[bum]

this thread is entertaining

[Brolly345]

... 23.98? I thought Premiere didn't handle 23.98 very well, and 23.976 almost not at all.

I thought it was that premiere can handle 23.98, but not 23.976, and the importance of that was because if you try to use 23.976 footage in compression it fucks up your times.

[Scintilla]

... 23.98? I thought Premiere didn't handle 23.98 very well, and 23.976 almost not at all.

I thought it was that premiere can handle 23.98, but not 23.976, and the importance of that was because if you try to use 23.976 footage in compression it fucks up your times.

Well, it's been mentioned before multiple times that using any kind of MPEG-4 codec for your source files isn't good for timing accuracy... but yeah, I personally would suggest just converting everything to 24 for to edit and then back to 23.976 when you're done. That's what I do.