Trying to understand DivX
#1
So not all DivX are the same?

In my quest to understand why 720p divx from icefilms won't play nice on atv2, I tried several files. Among them one played smooth and nice with the Videotoolbox. So I need to understand what was different on this file than others.

Here is the media info:
Walking dead
INFO: ffmpeg[8AF9000]: Metadata:
00:20:13 T:145723392 INFO: ffmpeg[8AF9000]: encoder : Lavf52.104.0
00:20:13 T:145723392 INFO: ffmpeg[8AF9000]: Duration: 00:21:00.01, start: 0.000000, bitrate: 4752 kb/s
00:20:13 T:145723392 INFO: ffmpeg[8AF9000]: Stream #0.0: Video: mpeg4, yuv420p, 1280x720 [PAR 1:1 DAR 16:9], 23.98 tbr, 23.98 tbn, 23.98 tbc
00:20:13 T:145723392 INFO: ffmpeg[8AF9000]: Stream #0.1: Audio: mp3, 44100 Hz, 2 channels, s16, 320 kb/s
00:20:13 T:145723392 NOTICE: Opening video stream: 0 source: 256
00:20:13 T:145723392 NOTICE: Creating video codec with codec id: 13

To my untrained eyes, except for encoder and video height, all the files look the same. So why was this one accepted by Videotoolbox.

P.S: I have recompiled XBMC to force mpeg4 and the other one to Videotoolbox for testing (just in case someone tells me they're not being handled by videotoolbox).
Reply
#2
Use mediainfo to determine the difference. The ffmpeg Metadata dump does not contain enough info.
Reply
#3
newatv2user Wrote:So not all DivX are the same?

In my quest to understand why 720p divx from icefilms won't play nice on atv2, I tried several files. Among them one played smooth and nice with the Videotoolbox. So I need to understand what was different on this file than others.

Here is the media info:
Walking dead
INFO: ffmpeg[8AF9000]: Metadata:
00:20:13 T:145723392 INFO: ffmpeg[8AF9000]: encoder : Lavf52.104.0
00:20:13 T:145723392 INFO: ffmpeg[8AF9000]: Duration: 00:21:00.01, start: 0.000000, bitrate: 4752 kb/s
00:20:13 T:145723392 INFO: ffmpeg[8AF9000]: Stream #0.0: Video: mpeg4, yuv420p, 1280x720 [PAR 1:1 DAR 16:9], 23.98 tbr, 23.98 tbn, 23.98 tbc
00:20:13 T:145723392 INFO: ffmpeg[8AF9000]: Stream #0.1: Audio: mp3, 44100 Hz, 2 channels, s16, 320 kb/s
00:20:13 T:145723392 NOTICE: Opening video stream: 0 source: 256
00:20:13 T:145723392 NOTICE: Creating video codec with codec id: 13

To my untrained eyes, except for encoder and video height, all the files look the same. So why was this one accepted by Videotoolbox.

P.S: I have recompiled XBMC to force mpeg4 and the other one to Videotoolbox for testing (just in case someone tells me they're not being handled by videotoolbox).

I think icefilms offers some of its HD content in XviD, and some in h/x264. Are you absolutely certain that the file that you claim is a 720p XviD/DivX isn't in fact a 720p h/x264?
Reply
#4
Well, the filename does say x264. Here is the pastebin for mediainfo.

http://pastebin.com/8wsKWMes

What do you think? So x264 is not xvid? And is that supported for hardware decoding?

Also if it is supported, how would you detect the format since there is no mention of it other than in the filename?
Reply
#5
newatv2user Wrote:Well, the filename does say x264. Here is the pastebin for mediainfo.

http://pastebin.com/8wsKWMes

What do you think? So x264 is not xvid? And is that supported for hardware decoding?

Also if it is supported, how would you detect the format since there is no mention of it other than in the filename?

h.264 == x.264 == mpeg4 part 10 - videotoolbox hw decoder can handle it
xvid == divx == mpeg4 part2 - videotoolbox hw decoder can't handle it (at least nobody knows how ...)

Detecting is happening by reading the binary header of the file which encodes 1001 bits of what this file contains ...
AppleTV4/iPhone/iPod/iPad: HowTo find debug logs and everything else which the devs like so much: click here
HowTo setup NFS for Kodi: NFS (wiki)
HowTo configure avahi (zeroconf): Avahi_Zeroconf (wiki)
READ THE IOS FAQ!: iOS FAQ (wiki)
Reply
#6
Question not directly related to this thread: When I use my compiled version, the default skin seems to be messed up. All transparent, no highlights, no black portions of the skin. Did I missed a step while compiling?
Reply
#7
newatv2user Wrote:Question not directly related to this thread: When I use my compiled version, the default skin seems to be messed up. All transparent, no highlights, no black portions of the skin. Did I missed a step while compiling?

Start a new thread with the steps you used and we'll try to give you a hand. Just to keep this thread clean.

If I have helped you in any way, please forgive me, it was entirely accidental.
Reply
#8
So back to my original question, based on the pastebin above, is this file supported for hw decoding or not?

Right now with the unmodified xbmc, it goes through software decoding.

22:21:20 T:128344064 INFO: ffmpeg[7A66000]: Input #0, avi, from 'http://www1250.megaupload.com/files/bb0c2122adc4674e2af7c7d54bcdb874/the.walking.dead.s02e06.720p.hdtv.x264-orenji.part1.avi':
22:21:20 T:128344064 INFO: ffmpeg[7A66000]: Metadata:
22:21:20 T:128344064 INFO: ffmpeg[7A66000]: encoder : Lavf52.104.0
22:21:20 T:128344064 INFO: ffmpeg[7A66000]: Duration: 00:21:00.01, start: 0.000000, bitrate: 4752 kb/s
22:21:20 T:128344064 INFO: ffmpeg[7A66000]: Stream #0.0: Video: mpeg4, yuv420p, 1280x720 [PAR 1:1 DAR 16:9], 23.98 tbr, 23.98 tbn, 23.98 tbc
22:21:20 T:128344064 INFO: ffmpeg[7A66000]: Stream #0.1: Audio: mp3, 44100 Hz, 2 channels, s16, 320 kb/s
22:21:20 T:128344064 DEBUG: CDVDInputStreamFile::SetReadRate - set cache throttle rate to 725151 bytes per second
22:21:20 T:128344064 NOTICE: Opening video stream: 0 source: 256
22:21:20 T:128344064 NOTICE: Creating video codec with codec id: 13
22:21:20 T:128344064 DEBUG: CDVDFactoryCodec: compiled in hardware support: VDADecoder:no VideoToolBoxDecoder:yes CrystalHD:no OpenMax:no
22:21:20 T:128344064 DEBUG: FactoryCodec - Video: - Opening
22:21:20 T:128344064 DEBUG: SECTION:LoadDLL(special://xbmcbin/system/players/dvdplayer/avfilter-1-arm-osx.so)
22:21:20 T:128344064 DEBUG: Loading: /private/var/stash/Applications/XBMC.frappliance/XBMCData/XBMCHome/system/players/dvdplayer/avfilter-1-arm-osx.so
22:21:20 T:128344064 NOTICE: CDVDVideoCodecFFmpeg::Open() Using codec: MPEG-4 part 2
22:21:20 T:128344064 DEBUG: FactoryCodec - Video: ff-mpeg4 - Opened
22:21:20 T:128344064 NOTICE: Creating video thread
22:21:20 T:134152192 DEBUG: Thread CDVDPlayerVideo start, auto delete: 0

When I had modified XBMC before, it played real nice with hw decoding.
Reply
#9
mpeg4 part 2 - XviD
Probably a dodgy filename. Run it through mediainfo to be sure.
Reply
#10
newatv2user Wrote:So back to my original question, based on the pastebin above, is this file supported for hw decoding or not?

...snip

When I had modified XBMC before, it played real nice with hw decoding.

MPEG-4 part 2, not a chance with hw decoding. Not sure what you think you did but it did not use VideoToolBox for hw decoding. Why am I so sure... I wrote that particular code and MPEG-4 part 2 is excluded because of certain unsolved issues.
Reply
#11
I know you wrote it to exclude mpeg4 part2 and the other one. I modified to throw everything to vtb to see what happens. Most divx were garbled. This particular one plays perfect. The filename does say x264, but it is being detected as would any other divx on icefilms site. So I'm just wondering if whoever made this file messed the media info so it's being detected as xvid and hence being sent to software decode.

If you still don't believe me, please try the video with vtb yourself. On icefilms, walking dead, season 2, the second last one right now (i think 6), among the hd sources, it's the one with two parts. Not implying that mpeg-4 part 2 would run on hw decoder, just that maybe wrong detection.
Reply

Logout Mark Read Team Forum Stats Members Help
Trying to understand DivX0