2009-06-08, 16:36
Thanks for a prompt reply
ekim232 Wrote:I am so happy this has finally been completed. Thanks for all your hard work on it. I am not over familiar with all the audio and video codecs, so I was thinking it would be useful to have a legend or key that details what the codecs are and represent. Primarly I am concerned with audio, since I am not entirely sure what codecs are dolby digital, dts, dts true hd, ect. If someone could throw something together I think it would be a big help so that all skin work being done is the same in terms of proper flagging.
Also, is it possible to determine between i and p....720p or 720i?
EDIT: Just been informed this is not possible
If anyone could help with this is would be GREATlY appreciated because I am looking to get started right away.
Video: mpeg4 1027
msmpeg4 348
h264 75
msmpeg4v2 1
mpeg1video 9
flv 1
Audio: ac3 321
mp3 1090
aac 22
dca 28
mp2 10
pcm_s16le 1
vorbis 5
wmav2 9
ekim232 Wrote:I have been playing around with this and just want to confirm some of my audio code with everyone to make sure it is reprenting everything correctly.
I am using the following to start...
<visible>substring(listitem.audiochannels,6) + substring(listitem.audiocodec,ac3)</visible>....this show dolby digital 5.1
<visible>substring(listitem.audiochannels,8) + substring(listitem.audiocodec,ac3)</visible>....this show dolby digital 7.1
<visible>substring(listitem.audiochannels,6) + substring(listitem.audiocodec,dca)</visible>....this show dts 5.1
<visible>substring(listitem.audiochannels,8) + substring(listitem.audiocodec,dca)</visible>....this show dolby digital 7.1
It seems as though all my mp3 audio codecs are 2 channel. Can this be considered dolby digital 2.0?
I would appreciate help on this. Thanks again!
C-Quel Wrote:if it is i see no reason why it couldnt be appended to the current resolution which is obtained thus allowing 720p/i image files to be used.It isn't. The thing is that frames are interlaced, not content, so there is nothing in the header to indicate an interlaced disposition. Really the only way to tell is to scan through the file looking for frames with interlaced flags. However some content doesn't flag the frames as interlaced fields, they just encode the content as if it were progressive. Others might interlaced encode but not set the frame header to indicate it, relying on the macroblock processor to be smart enough. So in short it can be a mess. That's not saying it isn't possible, just I'm not going to do it as it is impractical.
ekim232 Wrote:<visible>substring(listitem.audiochannels,6) + substring(listitem.audiocodec,ac3)</visible>....this show dolby digital 5.1Not to be pissing in your cornflakes but isn't that kind of retarded? Why not just make a dolby digital icon, dts icon, and then a 5.1 icon and a 7.1 icon and have them butt up to each other? The performance overhead of having 4 items with scripted conditional visibility is an order of magnitude higher than having 2 items based on single conditions. In addition, the "miss ratio" where a texture has to be replaced with another is higher.
<visible>substring(listitem.audiochannels,8) + substring(listitem.audiocodec,ac3)</visible>....this show dolby digital 7.1
<visible>substring(listitem.audiochannels,6) + substring(listitem.audiocodec,dca)</visible>....this show dts 5.1
<visible>substring(listitem.audiochannels,8) + substring(listitem.audiocodec,dca)</visible>....this show dolby digital 7.1
It seems as though all my mp3 audio codecs are 2 channel. Can this be considered dolby digital 2.0?
ccMatrix Wrote:Would it be possible to separate divx, xvid and maybe other mpeg4 based codecs in VideoCodec?Sorry, can't do that either. What gets recorded is what decoder will be used to decode the video, not the encoder used to create it.
CapnBry Wrote:Not to be pissing in your cornflakes but isn't that kind of retarded? Why not just make a dolby digital icon, dts icon, and then a 5.1 icon and a 7.1 icon and have them butt up to each other? The performance overhead of having 4 items with scripted conditional visibility is an order of magnitude higher than having 2 items based on single conditions. In addition, the "miss ratio" where a texture has to be replaced with another is higher.
CapnBry Wrote:Here is version 8 which will probably be the one I submit.
xbmc@eva:~$ wget http://capnbry.net/~bmayland/fi/code/hdflagging_total_8.diff
--2009-06-09 09:21:46-- http://capnbry.net/~bmayland/fi/code/hdflagging_total_8.diff
Resolving capnbry.net... failed: Name or service not known.
wget: unable to resolve host address `capnbry.net'
xbmc@eva:~$
ekim232 Wrote:I use icons that are like this. It works 100% perfect on my library of 980 videos. I even set a labels for channels and codec on the screen to test it out.
<control type="image">
<texture>$INFO[ListItem.AudioCodec,prefix,.png]</texture>
</control type="image">
<control type="image">
<texture>$INFO[ListItem.AudioChannels,prefix,.png]</texture>
</control type="image">
watzen Wrote:I think that he means that it is easier and faster to do it this way:Yup that's exactly what I mean. Just load the texture from a variable rather than having one texture for each with conditional visibility.
Code:<control type="image">
<texture>$INFO[ListItem.AudioCodec,prefix,.png]</texture>
</control type="image">
<control type="image">
<texture>$INFO[ListItem.AudioChannels,prefix,.png]</texture>
</control type="image">