Advanced Search

Announcement

Collapse
No announcement yet.

TrialDirector 6 - MPEG-1 and MPEG-2 Compatibility in Windows 8 and Windows 10

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • TrialDirector 6 - MPEG-1 and MPEG-2 Compatibility in Windows 8 and Windows 10

    iProIndLgcy00777-med.png
    MPEG-1 and MPEG-2 Compatibility in Windows 8 and Windows 10


    ​Microsoft dropped out-of-the-box support for DVD Playback including Windows Media Center, MPEG-1 and MPEG-2 playback. This was confirmed per the release of Windows 8 and continued to be an issue for Windows 10. Why did Microsoft do this? See below.

    See here for comments from Microsoft:

    https://blogs.msdn.microsoft.com/b8/...-in-windows-8/


    See here for File Types supported by Windows Media Player:

    https://support.microsoft.com/en-us/...s-media-player


    --- On that same page, scroll down to the section "Detailed information about supported file types".

    Expand the "Moving Pictures Experts Group (.mpg, .mpeg, .m1v, .mp2, .mp3, .mpa, .mpe, .mpv2, .m3u)"

    ***The Moving Picture Experts Group develop the Moving Picture Experts Group (MPEG) standards. These standards are an evolving set of standards for video and audio compression.

    MPEG-1 (.mpeg, .mpg, .m1v)

    This standard permits the coding of progressive video at a transmission rate of about 1.5 million bits per second (bps). This file format was designed specifically for use with Video-CD and CD-i media. The most common implementations of the MPEG-1 standard provides a video resolution of 352x240 at 30 frames per second (fps). When you use this standard, you receive a video that is slightly lower-quality than typical VCR videos.

    Files that use the .m1v extension typically are MPEG-1 elementary streams that contain only video information. Files that use .mpg or .mpeg extensions typically are MPEG-1 system streams that contain MPEG-1-encoded video and MPEG-1 Layer II (MP2)-encoded audio.

    However, MPEG-1 system streams do not exclusively use the .mpg and .mpeg extensions. MPEG-2 program streams also frequently use .mpg and .mpeg file extensions, but they contain MPEG-2-encoded video. Because Microsoft Windows operating systems provide only an MPEG-1 video decoder, Windows Media Player cannot play MPEG-2 program streams without an additional MPEG-2 video decoder (also known as a DVD decoder pack) installed. For more information about purchasing DVD decoder packs, visit the following Microsoft Web site:


    https://support.microsoft.com/en-us/help/10771

    Here is a link to the Windows DVD Player in the Microsoft App store:

    https://www.microsoft.com/en-us/stor...r/9nblggh2j19w


    (DVD files are literally MPEG-2 and MPEG-1 files wrapped in a authoring code such as a VOB container)

    The decision was made by Microsoft because the decoders used for the above formats required royalties to be paid to Intellectual Property Owners. Microsoft was responsible for the payment of all royalties. This was a business decision made per Microsoft and has an impact on users of their OS'es. This also has an impact on any software that uses Windows Media Player for rendering - such as Windows Presentation Foundation (WPF) and Windows Communication Foundation (WCF). Both of these components are used heavily by TrialDirector and TrialDirector Presentation.

    MPEG-4 doesnt use VOB so it's not subject to the above codec demands, however, MPEG-4 isn't natively supported by Microsoft OS'es so it too may require iPro's inData Audio Video Codec Pack to set priority correctly - see the link below:

    http://www2.indatacorp.com/apps/CODEC/CodecPack.exe

    MPEG-4 Parameters listed in the iPro (inData) MPEG-4 Encoding Utility are the recommended parameters for MPEG-4 functionality in TrialDirector 6. This only applies to raw video as the source from the camera it was shot with. If the user is converting a video to those parameters and it's not the root video from the camera, then there's no guarantee that the video will playback or cut correctly. Converting a previously converted file is not best practice.

    Playback and clip cut accuracy in TrialDirector is subject to whatever codecs are set as highest priority in the users system. If any other troubleshooting software was used outside of our Technical Support calls (such as DSFMgr.exe, ClearAMCache.exe, GraphEdit.exe, MediaInfo.exe, or Procexp.exe) then priority may be locked to an unsupported codec. iPro Technical Support has been trained in the use of these programs will not be able to assist users that have taken it upon themselves to use troubleshooting tools they have not been trained with.

    For some problematic videos, Technical Support must test on a barebones install of Windows. These test installs include ONLY the following:

    ----- A supported operating system
    ----- Critical updates for the operating system
    ----- Any needed drivers
    ----- Microsoft.NET versions 2.0 to 4.7 (as of this article)
    ----- iPro (inData) Audio Video Codec Pack
    ----- TrialDirector 6
    ----- Native software needed for documents such as Adobe Acrobat and Microsoft Office.

    No other 3rd software is permitted. This includes DVD Burning software, video edtiting software, codec packs, media editing software and media playback software.

    Beyond the listed options above, we are open to screen capturing the video as a completely different file (MPEG-4) with the correct parameters. The general rule of thumb is - if the TrialDirector 6 Sample Data and client data has the same issues on the same system, it's an environmental issue with the computer(s) in question. If only one video has the issue but others play fine, it's an issue with the problem video.
    Last edited by Chris Friedel; 10-12-2017, 11:35 AM.
    Can't see pictures? You might have to register or login.
Working...
X