home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Area 51 - Testing Area
MP1-4777 Additional info for video and audio
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="CyberSimian" data-source="post: 1258193" data-attributes="member: 141969"><p>There was a discussion in another thread concerning the information returned by the existing support for recordings (TV and radio). The problem is that most recordings have one or more minutes of pre-padding at the start of the file. So if MediaInfo determines the file properties from the data at the start of the file, misleading information may result.</p><p></p><p>Specifically, the other thread discussed the question of the number of audio channels. In the UK, most DVB-T/T2 broadcasts have a stereo soundtrack, but major films and prestige drama productions have multichannel soundtracks (where multichannel means "greater than two"). But MP displays the "stereo" logo for these recordings, and not the multichannel logo.</p><p></p><p>The suggestion was made that MediaInfo should allow the invoker to specify a time offset, and relevant properties would be determined by looking at the datastream at that offset in the file. This would apply to the number of audio channels, but might apply to other properties too. MP already allows the end user to specify a time offset for the generation of thumbnails (for the same reason -- you want the thumbnail taken from the programme recorded, and not from the pre-padding), so it would seem sensible to use the same offset for determining the relevant properties.</p><p></p><p>So, now the big question: does the new MediaInfo allow the invoker to specify a time offset from which relevant file properties are determined?</p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1258193, member: 141969"] There was a discussion in another thread concerning the information returned by the existing support for recordings (TV and radio). The problem is that most recordings have one or more minutes of pre-padding at the start of the file. So if MediaInfo determines the file properties from the data at the start of the file, misleading information may result. Specifically, the other thread discussed the question of the number of audio channels. In the UK, most DVB-T/T2 broadcasts have a stereo soundtrack, but major films and prestige drama productions have multichannel soundtracks (where multichannel means "greater than two"). But MP displays the "stereo" logo for these recordings, and not the multichannel logo. The suggestion was made that MediaInfo should allow the invoker to specify a time offset, and relevant properties would be determined by looking at the datastream at that offset in the file. This would apply to the number of audio channels, but might apply to other properties too. MP already allows the end user to specify a time offset for the generation of thumbnails (for the same reason -- you want the thumbnail taken from the programme recorded, and not from the pre-padding), so it would seem sensible to use the same offset for determining the relevant properties. So, now the big question: does the new MediaInfo allow the invoker to specify a time offset from which relevant file properties are determined? -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
MP1-4777 Additional info for video and audio
Contact us
RSS
Top
Bottom