What is your sequence size?
Widescreen SD PAL is not the same ratio as HD Widescreen thus you end up with tiny black bars on the edges if you drop a SD widescreen on a HD sequence and scale it up.
720x576 @ 1.4587:1 PAR = 1050.264x576 = 1.823375:1
1280x720 @ 1:1 PAR = 1.7777:1
1920x1080 @ 1:1 PAR = 1,7777:1
The sequence is 720x 576 widescreen.
The footage on digibeta was 16x9
the digital file is 720 x 576 but appears as 4x3 in the 16x9 frame, in after effects interpret footage = wide screen would correct this, but this dosent appear to be the case in premiere the footage remains 'squashed' in 4x3.
at the moment I am Interepting footage in the source window?
Am I missing something? I must be . . . .
That is so odd.
My only assumption is that because it is mov that it uses the QuickTime importer vs the native ones.
I know that QuickTime relies/chooses on the mov information over that of the stream information. So if the mov container says its 4:3 (1.0940:1) and the stream says it is 16:9 then Premiere will interpret it as 4:3 and box it in a 16:9 sequence.
AE on the other hand might not take this code path and thus gets it right.
That's just a guess though
What does MediaInfo (PC) or Media Inspector (Mac) say?
Having said that there really isn't a good way to fix the problem other than stretching it in the clip scaling width/height settings if the interpret is wrong.
Another post about this here http://forums.adobe.com/message/5259586#5259586
I posted there and then like the original poster I too had to totally reinstall for interpret footage to start working again. Now only a month later I'm in the same boat again. Frustrating. The file i'm using is an AVI, not mov.
I guess stretching it to be wide has the same effect as interpret footage, or is there some quality loss in doing this?
Thanks for that Ryan,
As you suggest I have reinstalled the software and thats seems to have fixed things (temporarily as you say).
Strecthing the footage is not the best solution in my opinion, because, as you say, it involves the interpolation of pixels to create the extra data.
does anyone know a way of escalting this issue?