Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro PAL and NTSC???

  • John Rofrano

    May 18, 2015 at 10:23 pm

    This won’t affect anything negatively. It’s just bad metadata. As you said, the video is still PAL and will be fine. I wouldn’t worry about it since Vegas Pro has had this bug for many years and everyone who is making PAL videos for the web has been unaffected by it.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Juan Juig

    May 18, 2015 at 10:27 pm

    Alright, thank you so much. I found out everything I needed to know.

    Thank you!

  • John A. mozzer

    May 26, 2015 at 8:51 am

    I have a related issue. I shot footage with my iPad, which is H.264, 1920×1080, Progressive, 30 frames per second. (Seems to me, it is neither NTSC or PAL.) I edited the footage in Final Cut Pro X, with the project’s render properties set to ProRes 422 (HQ), because there seems to be no way to natively edit H.264. I created a ProRes master file using Final Cut Pro X’s Share feature, because I like to use Episode for encoding to H.264. I am not changing the video properties (1920×1080, Progressive, 30 frames per second) anywhere in this workflow. MediaInfo says the resulting Episode encoded H.264 video is the PAL standard, which makes no sense to me.

    It is merely an annoyance, I guess. The video seems fine. But I do wish that I could figure out where the problem is being introduced. (By Episode?)

    P.S. I am using Final Cut Pro X Version 10.0.9 and Episode 6.3.1.23, outdated versions because I am keeping Snow Leopard on the particular iMac that I am using.

  • Jerome Martinez

    May 26, 2015 at 9:50 am

    PAL standard, which makes no sense to me.

    Again, I show only what the encoder says. Nothing else.
    If you want a confirmation, please provide a sample file and I’ll show you the “trace” of the bitstream.

    The video seems fine.

    Most players don’t care of this bitstream field.

  • John Rofrano

    May 26, 2015 at 10:53 am

    [John A. Mozzer] “I have a related issue. I shot footage with my iPad, which is H.264, 1920×1080, Progressive, 30 frames per second. (Seems to me, it is neither NTSC or PAL.)”

    That’s right. NTSC and PAL are “broadcast” standards. Most Internet devices (like tablets and smart phones) ignore broadcast standards and shoot whatever they want. I would say that 30 fps is closer to NTSC than PAL. But some devices use variable frame rates which give you crazy results.

    [John A. Mozzer] “I edited the footage in Final Cut Pro X, with the project’s render properties set to ProRes 422 (HQ), because there seems to be no way to natively edit H.264.”

    You can edit native H.264 if you upgrade to the latest version of FCP X.

    [John A. Mozzer] “It is merely an annoyance, I guess. The video seems fine. But I do wish that I could figure out where the problem is being introduced. (By Episode?)”

    It’s not a problem if the video is fine. As I said, broadcast standards are often ignored for Internet video anyway. I wouldn’t get hung up over them.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • John A. mozzer

    May 26, 2015 at 5:50 pm

    Jerome, I am glad to know that is what MediaInfo is doing, because I didn’t know before reading this thread. Yes, I would like to provide a file and see the trace.

  • John A. mozzer

    May 26, 2015 at 5:51 pm

    John, thanks. Good to know that I’ll be able to edit native H.264 when I upgrade to the latest version of FCP X.

  • Jerome Martinez

    June 3, 2015 at 8:14 pm

    in your file, video_format is set to 1 (so PAL).
    below is the trace of the begining of the avcC atom of your file:

    0000025D AVC decode (55 bytes)
    0000025D Header (8 bytes)
    0000025D Size: 55 (0x00000037)
    00000261 Name: avcC
    00000265 Version: 1 (0x01)
    00000266 Specific (46 bytes)
    00000266 Profile: 100 (0x64)
    00000267 Compatible profile: 0 (0x00)
    00000268 Level: 40 (0x28)
    0000026B Reserved: 63 (0x3F) - (6 bits)
    00000269 Size of NALU length minus 1: 3 (0x03) - (2 bits)
    0000026E Reserved: 7 (0x07) - (3 bits)
    00000269 seq_parameter_set count: 1 (0x01) - (5 bits)
    0000026B seq_parameter_set (33 bytes)
    0000026B Size: 31 (0x001F)
    00000272 nal_ref_idc: 3 (0x03) - (2 bits)
    0000026D nal_unit_type: 7 (0x07) - (5 bits)
    0000026E profile_idc: 100 (0x64)
    0000026F constraints (1 bytes)
    00000276 constraint_set0_flag: No
    00000275 constraint_set1_flag: No
    00000274 constraint_set2_flag: No
    00000273 constraint_set3_flag: No
    00000272 constraint_set4_flag: No
    00000271 constraint_set5_flag: No
    0000026F reserved_zero_2bits: 0 (0x0)
    0000026F level_idc: 40 (0x28) - (8 bits)
    00000276 seq_parameter_set_id: 0 (0x0)
    00000276 high profile specific (18446744073709551612 bytes)
    00000273 chroma_format_idc: 1 (0x1) - 4:2:0
    00000272 bit_depth_luma_minus8: 0 (0x0)
    00000271 bit_depth_chroma_minus8: 0 (0x0)
    00000270 qpprime_y_zero_transform_bypass_flag: No
    0000026F seq_scaling_matrix_present_flag: No
    00000272 log2_max_frame_num_minus4: 4 (0x4)
    00000271 pic_order_cnt_type: 0 (0x0)
    00000274 log2_max_pic_order_cnt_lsb_minus4: 4 (0x4)
    00000271 max_num_ref_frames: 2 (0x2)
    00000270 gaps_in_frame_num_value_allowed_flag: No
    00000273 pic_width_in_mbs_minus1: 119 (0x77)
    00000276 pic_height_in_map_units_minus1: 67 (0x43)
    00000275 frame_mbs_only_flag: Yes
    00000274 direct_8x8_inference_flag: Yes
    00000274 frame_cropping_flag (4 bytes)
    00000273 frame_cropping_flag: Yes
    00000272 frame_crop_left_offset: 0 (0x0)
    00000271 frame_crop_right_offset: 0 (0x0)
    00000270 frame_crop_top_offset: 0 (0x0)
    00000273 frame_crop_bottom_offset: 4 (0x4)
    00000273 vui_parameters_present_flag (22 bytes)
    00000272 vui_parameters_present_flag: Yes
    00000272 aspect_ratio_info_present_flag (7 bytes)
    00000271 aspect_ratio_info_present_flag: Yes
    00000271 aspect_ratio_idc: 1 (0x01) - (8 bits) - 1.000
    00000270 overscan_info_present_flag: No
    00000270 video_signal_type_present_flag (13 bytes)
    0000026F video_signal_type_present_flag: Yes
    00000274 video_format: 1 (0x01) - (3 bits) - PAL
    00000273 video_full_range_flag: 0 (0x00) - (1 bits) - Limited
    00000273 colour_description_present_flag (10 bytes)
    00000272 colour_description_present_flag: Yes
    00000272 colour_primaries: 1 (0x01) - (8 bits) - BT.709
    00000272 transfer_characteristics: 1 (0x01) - (8 bits) - BT.709
    00000272 matrix_coefficients: 1 (0x01) - (8 bits) - BT.709
    00000271 chroma_loc_info_present_flag: No
    00000271 timing_info_present_flag (21 bytes)
    00000270 timing_info_present_flag: Yes
    00000270 num_units_in_tick: 1 (0x1)
    00000270 time_scale: 60 (0x3C)
    0000026F fixed_frame_rate_flag: Yes
    00000276 nal_hrd_parameters_present_flag: No
    00000275 vcl_hrd_parameters_present_flag: No
    00000274 pic_struct_present_flag: Yes
    00000274 bitstream_restriction_flag (21 bytes)
    00000273 bitstream_restriction_flag: Yes
    00000272 motion_vectors_over_pic_boundaries_flagYes
    0000026F max_bytes_per_pic_denom: 2 (0x2)
    00000274 max_bits_per_mb_denom: 1 (0x1)
    00000275 log2_max_mv_length_horizontal: 10 (0xA)
    00000276 log2_max_mv_length_vertical: 10 (0xA)
    00000273 max_num_reorder_frames: 1 (0x1)
    00000270 max_dec_frame_buffering: 2 (0x2)
    0000028C pic_parameter_set count: 1 (0x01)
    0000028D pic_parameter_set (7 bytes)
    (...)

  • John A. mozzer

    June 4, 2015 at 6:09 pm

    Thanks, Jerome. This is good to know. I’ll contact Telestream’s customer support to see whether they can explain why the Episoder encoder is apparently putting a video_format field set to 1 in the bitstream.

Page 2 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy