Lee,
What I mean by "safe zones" is the borders that show where Action Safe and
Title Safe are. The original video specs are listed below, both for "not
resized" and "resized". The resized one was adjusted to be within the safe
zones in Premiere, and works perfectly when brought into Encore. I just don't
see any parameter difference in the resized and not resized files. They were
both rendered with exactly the same settings. It wouldn't matter to me if it
were only a few files, but I have to resize and render in Premiere for fifty or
more files! Any further ideas? I also tried to see if there was a difference
between Mpeg 2 and Mpeg 2-DVD, but there was no difference in physical
dimensions when importing to Encore. It is hard to explain this, screen shots
would work much better.
NOT RESIZED:
*** General Parameters ***
- Name: Sequence 01_1 from premeier, not resized, ntsc high quality 4, mpg
2.mpg
- Container: Mpeg Program Stream
- Creation Date: 2013-01-01 5:41:30 PM
- Size: 28.52 MB
- Duration: 1mn 4s
- Bitrate: 3 537 Kbps
- Encoding Library: Undefined
- Encoding Application: Undefined
*** Video Track Parameters ***
- Format: MPEG-2 Video
- Size: 26.11 MB (91%)
- FourCC: 0x10000002
- Track number(s): 0
- Bitrate: Max.: Undefined
Average: 3 243 Kbps
Min.: Undefined
- Frame rate (fps): Max.: Undefined
Average: 29.970
Min.: Undefined
- Bitrate mode: Variable
- Encoding profile: Main@Main
- Resolution: Undefined
- Width (Pixel number): 720
- Height (Pixel number): 480
- Pixel Aspect Ratio: 8:9
- Display Aspect Ratio: 4:3
- Chroma subsampling format: YUV420p
- Standard: NTSC
- Interlacing: Interlaced - Bottom Field First
- Encoding library: Undefined
- Additional Parameters: BVOP: Yes
Matrix: Default
GOP: M=3
Bits/(Pixel*Frame) ratio: 0.313
RESIZED:
** General Parameters ***
- Name: Sequence 01, from premiere mpg 2, resized, high quality ntsc 4.mpg
- Container: Mpeg Program Stream
- Size: 29.26 MB
- Duration: 1mn 4s
- Bitrate: 3 621 Kbps
*** Video Track Parameters ***
- Format: MPEG-2 Video
- Bitrate: Max.: Undefined / Average: 3 325 Kbps / Min.: Undefined
- Frame rate (fps): Max.: Undefined / Average: 29.970 / Min.: Undefined
- Encoding profile: Main@Main
- Width (Pixel number): 720*480
- Pixel Aspect Ratio: 8:9
- Display Aspect Ratio: 4:3
- Interlacing: Interlaced - Bottom Field First
*** First Audio Track Parameters ***
- Format: Mpeg-1 layer 2 (mp2)
- Bitrate: 224 Kbps
- Resolution: Undefined
- Profile: Layer 2
- Channel(s): 2 (stereo)
- Position: Undefined
--- In [email protected], Lee Menningen <l_menningen@...> wrote:
>
> Rick
>
> Just to make a clarification - the mpeg format defines something - such as
> frame rate - and specifies where in the file that information can reside,
> what the numerical limitations are, the number format, scaling, etc. The
> camera software has to write its information into the video file according
> to those limitations but the value of its frame rate can be whatever the
> camera deems it ought to be. Same thing for other parameters, such as
> compression. There are many ways to do compression even within the mpeg
> standard. Cameras don't always use the best compression but whatever it does
> use, it has to fully annotate all the necessary parameters so that the
> decompression software can correctly process the file. The GOP and B and I
> frames all have to be identified in a way the decompress software can
> decipher, etc.
>
> The point is that saying a video is "Mpeg II" doesn't by itself say much
> about the file; the software has to look inside of each specific Mpeg file
> to see what is really there. Every camera mfg. makes their video a little
> different (sometimes for capacity or quality reasons, sometimes for royalty
> payment reasons). Most of the formats you see in Premiere under other names
> such as AVCHD are Mpeg or mpeg derivatives even if they've given them
> proprietary file extension names. Premiere goes to great effort (Adobe works
> directly with the manufacturer, they don't do "reverse engineering") to
> write its input software to be able to recognize various camera files, and
> to be able to re-write those files according to defined common denominators.
>
> Again, hoping this helps.
>
> Lee
>
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Rick
> Sent: Tuesday, January 01, 2013 9:56 AM
> To: [email protected]
> Subject: [AP] Premiere to Encore Question
>
>
> Hi everyone,
> I am flummoxed by a circumstance when bringing a video into Encore from
> Premiere. For instance, the original video is an Mpeg II, 720 * 480.
> When I bring it into Encore it exceeds the safe margins and cuts the sides
> off when presented on TV. But, if I bring it into Premiere first, adjust its
> size to within the constraints of safe margins, render, and then import to
> Encore, it fits perfectly. Both videos are the same format, at 720 * 480. I
> can't figure out what is different about the two videos, considering all
> parameters appear to be the same, even after rendering. Anyone have the
> answer?
>
> Also, how can I do a batch process to convert the videos to safe zone
> compliance? Thanks for your time and knowledge.
>
>
>
> [Non-text portions of this message have been removed]
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/Adobe-Premiere/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/Adobe-Premiere/join
(Yahoo! ID required)
<*> To change settings via email:
[email protected]
[email protected]
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
