AVCHD? Premiere pro? Native?

There is no problem, you need to render all of your footage, especially AVCHD since it a b*tch for many computers, even if premiere cs5 is much faster, it stills goes really slow compared to DVCPROHD.

So go to Sequence and then click on either render effects in work area or render entire work area.
 
mercury engine is off in the picture.

Here is my specs: www.igelkottfilm.se/temp/DxDiag.txt

The question is, why does the raw AF100 footage need to rendered in a AVCHD timeline? (without any effect on)

HDV in a HDV timeline do not have red/yellow color over it, nor does DV in a DV timeline.
 
Try this!

Take one of your Footage from the "Project Window" and drag down to the little icon with the shape of a Page next to the Recycle Bin in the bottom border of the "Project Window", this will build a Project timeline with the characteristics of your Footage, your footage will be the Yellow line.

Hope this helps. Cheers
 
Take one of your Footage from the "Project Window" and drag down to the little icon with the shape of a Page next to the Recycle Bin in the bottom border of the "Project Window", this will build a Project timeline with the characteristics of your Footage, your footage will be the Yellow line.

Where have you been all my life!

+1

Thats a great tip!

I also found out a very important thing.
Therse is a bug that makes PPRO read the AF100-files as interlaced and you need to manually make it read them progressive.

Thats is the solution to my problem.

My computer works like an old HD editing machine again :D

Still going to get:

KINGSTON 24GB 1600MHz DDR3 Non-ECC CL9 DIMM
INTEL Core i7 950/ 3.06G/ 8M Tray
ASROCK X58 Extreme6 CFX & SLI USB3 SATA6 AIWI (X58 EXTREME6)
 
Last edited:
Try this!

Take one of your Footage from the "Project Window" and drag down to the little icon with the shape of a Page next to the Recycle Bin in the bottom border of the "Project Window", this will build a Project timeline with the characteristics of your Footage, your footage will be the Yellow line.

Hope this helps. Cheers

+1

Thank you sooo much! I was having the exact same problem.
 
I also found out a very important thing.
Therse is a bug that makes PPRO read the AF100-files as interlaced and you need to manually make it read them progressive


WHO WHAT?!! We use PPRO CS4 and are about ot upgrade to CS5. Can you expand upon your statement because this is news to me and sounds like quite a big deal. I checked the properties and interpret footage settings in CS4 and everything listed seems to state that it sees it as 1:1 progressive files.
 
Last edited:
I was searching around and Adobe PPRO CS4 notes for V4.1.0 do indeed state under known issues that "AVCHD 1080p 30 and 25 progressive clips are interpreted as interlaced files in Adobe Premiere Pro CS4 projects." Does this also apply for 23.976/24fps footage? Or this only an issue with 25 and 30fps?
 
I still have a problem with the video being jittery once it is playing in the timeline…..is that normal ( cs5, mac book pro, yellow line on time line) it doesn't happen with other formats (m2t,movs,mp4)
 
WHO WHAT?!! We use PPRO CS4 and are about ot upgrade to CS5. Can you expand upon your statement because this is news to me and sounds like quite a big deal. I checked the properties and interpret footage settings in CS4 and everything listed seems to state that it sees it as 1:1 progressive files.

Do nor worry...CS5 does not have bug such as this. I suspect O.E
 
Do nor worry...CS5 does not have bug such as this. I suspect O.E
For 25p there is indeed a bug and all footage is mis-interpreted as interlaced footage when importing the footage. One must use Interpret Footage to fix the issue and once done the footage is treated correctly in the project. I have not tested 30p footage, so i dont know how if the same is true for 30p or 24p.

The bug is reported and hopefully it is fixed in the next release.

/Roger
 
For 25p there is indeed a bug and all footage is mis-interpreted as interlaced footage when importing the footage. One must use Interpret Footage to fix the issue and once done the footage is treated correctly in the project. I have not tested 30p footage, so i dont know how if the same is true for 30p or 24p.

The bug is reported and hopefully it is fixed in the next release.

/Roger

Roger. Please advise how it is determined that 25p has been mis-interpreted in CS5 as interlaced and what the "issue" displays as before and after it has been re-interpreted?
 
I have Adobe Premiere Pro CS4 v4.2.1 and will be receiving my AF100 next monday. Do i have use Interpret Footage method to fix the issue with the footage being seen as interlaced ?? or are the fixed by version 4.2.1 ?? i will be shooting in 1080p24. i cant upgrade to CS5 as i am using a 32 bit operating system.
 
Roger. Please advise how it is determined that 25p has been mis-interpreted in CS5 as interlaced and what the "issue" displays as before and after it has been re-interpreted?
1. Import 1080p25 footage from your AF102
2. Right click on the clip in the project panel and choose Modify > Interpret Footage

Result:
The Field Order in the Interpret Footage dialog is set to "Use Field Order from File:" and under that you will see "Upper Field First".

Expected result:
That the "Use Field Order from File:" is set to "No Fields (Progressive Scan)" since the footage is progressive.

If you ignore this and export the footage to progressive you will de-interlace your footage and throw away half the vertical resolution, and thats *not* what you want to do. :)
I have not done so much before and after since i knew about this issue early and thus always use Interpret Footage for 1080p25 AVCHD cams, so i can not give more detailed information about the ins and outs.

africanmarty said:
I have Adobe Premiere Pro CS4 v4.2.1 and will be receiving my AF100 next monday. Do i have use Interpret Footage method to fix the issue with the footage being seen as interlaced ?? or are the fixed by version 4.2.1 ?? i will be shooting in 1080p24. i cant upgrade to CS5 as i am using a 32 bit operating system.
For 1080p24 you should be safe.

/Roger
 
Back
Top