Why do I need to render the timeline ??? PP2

S

S0ftfx

Active member
Ok I just intalled premiere pro 2.0 on a fresh WinXp sp2 installation.

I edit many web videos ( 320x240 ) every week. I get the files ready in virtualdub deinterlacing , resizing and compressing with PICvideo mjpeg codec before I import them to premiere pro.

Everything was working flawlessely in PP 1.5 but now PP 2.0 gives me the rendering red bar over my clips every time.

My project is setup to accept these files . Namely : Video for windows ( desktop in PP2 ) - 320x240 - square pix ( 1.0 ) - no fields progressive scan - 48000hz audio samples - PicVideo mjpeg codec for the rendering preview

In other words there is NO difference between my clips and my timeline yet PP2.0 wants me to render. It is very very annoying because now the scroling is laggy and choppy even if PICvideo gives me a keyframe on everyframe...

I have no clue about the eventual problem - Im I missing something here ?

Please help out If you can ,

Thanks ,

-Sfx
 
I just un-installed pro2! what a piece of crap!!! Bugs galore!!
Adobe was too much in a hurry to release the product!
not moving from 1.5 until aeons ahead
 
I have yet to understand what is going on ! My project settings are exactly set to welcome without any timeline rendering the clips that I import in it ! This is starting to piss me off big time. I worked with 24p advanced 720x480 this week end and there was no rendering needed ( i though i had this problem with that also ) But my 320x240 clips have the red rendering bar still !!!!! And I do almost all my work for the web , thus working at this resolution !

Barrry ? You there ? Anyone ?

-sfx
 
there are bugs... what did you expect for a *.0 release? Perfection? When you find a product that has a prefect *.0 release, let me know.

I think the bugs are outweighed by the advantages.

As for the bug in reference here, how did you get your project in premiere 1.5 to be unrendered for these web videos of such small resolution to begin with?
 
Unrendered ? Well when your project settings are set to receive 320x240 progressive ( deinterlaced ) square pixel ratio clips and the sound has the exact same sample rate.There is no need for premiere to render. But there is something wrong with premiere pro 2.0 i guess... Well I hope it it something wrong and not me being stupid and forgeting something....
 
ChrisLyon said:
there are bugs... what did you expect for a *.0 release? Perfection? When you find a product that has a prefect *.0 release, let me know.
Click to expand...
I don't expect perfection but I expect something much better than this! This doesn't seem to be that big of an upgrade from 1.5.1. I only hope that Encore 2.0 and AE7 make this upgrade worth it, PPro2 is almost a step backwards.

ChrisLyon said:
I think the bugs are outweighed by the advantages.
Click to expand...
What advantages over 1.5.1?

Not only is this a fairly weak release Adobe has totally screwed up the upgrade path so the waitching costs to FCP/G5 aren't so bad. I was really hoping for more.
 
No franckly , this upgrade is really really weak and buggy. They put the emphasis on the new multicam module but before going on that path they should really refine the engine, polish, increase fluidity, responsivnes, loadi time, native HD , debug debug and more debug ...There have the necessary workforce to make premiere the best nle peice of software out there. I say it again , it is weak !
 
Pros: Native HD (good enough for me), multi-cam live style editing, no more conforming audio files (it does what vegas does and creates a peak file) faster render engine (it is noticably faster for me), finally a new title decko, Tighter integration with other Adobe products (ala bridge), better color correction, better rendering of slowed down footage....

i havent had any issues with it being buggy. What are you guys running in premiere that would cause it to be buggy. I have crashed only once since I installed the thing. A much better runrate that 1.5.1... But to each his own. I have no issues with it so far.
 
Have you edited HDV natively?

I'm using AspectHD which provides PPro with a much faster render engine and a lot more realtime functionality. I agree color correction is pretty weak in 1.5.1, I use AE for faster or slower motion. I'd be interested in what some of the upgrades to title decko.

I've also edited a fair amount of DVCProHD with FCP and I'm not impressed with the quality. Of coarse people who love Macs and have never edited uncompressed HD think its just fine, so who am I to argue? I've also tried editing HDV natively on a G5, it can be done but I wouldn't do it.
 
Wow, I never had a NLE work any better than how Premiere Pro 2.0 has been working for me. I never had a single problem with anything yet.
 
yeah I am getting the same problem - everytime I import the clip PPRo 2.0 wants to render it. I have a project setup as "Desktop", and its' identical to the clip footage. But for some stupid reason PPRo 2 wants to render it... Grrrr.....

Importing it into 1.5.1 is fine !

Hope this bug is sorted relatively soon.........
 
Sounds like this may be an issue with projects using resolutions lower than DV. (Ie. A "video for windows" problem)?

I've been using 2.0 extensivly with all kinds of DV and HD resolutions and not had any issues like are being described here.

Infact, I totally agree with skettalee, 2.0 is fantastic for me. Not one bug or issue yet and it's much more stable the 1.5

hope this gets figured out. You guys should head over to the adobe forums and get to the bottom of this
 
>>Sounds like this may be an issue with projects using resolutions lower than DV. (Ie. A "video for windows" problem)?

I disagree... I am editing HD content 1440x1080 uncompressed footage - hence why I choose Desktop as a setting.....

So it's not just the low resolution's that cause the problem..........
 
I suspect Morgan is on to something here. It may have to do with resolution. I have not seen this problem myself but then I've only been doing standard DV since I installed 2.0. Just out of curiosity, how long as it taken to actually render in these cases? Have you looked to see when kind of files have appeared after the render? What's your quality setting on the monitor window? If this is intended behavior or a bug, it would be nice to know what conditions trigger it.

In any case, Morgan's suggestion to go check out the Adobe forum site is a good one. I think you'll have a better chance of getting some answers there.

-Dan
 
You must log in or register to reply here.
Back
Top