Transcoding MPEG4/DX50 files for a xbox360

I have a number of files in mpeg4 containers using the DX50 codec that will not play through Serviio on my 360, when trying to edit the profiles.xml file, I'm running into issues. I attempted to add the line:

<Matches container="avi" vCodec="DX50" />

which caused Serviio to fail to start. Looking into things, it appears Serviio can only handle "mpeg2video, mpeg1video, wmv2, mpeg4, msmpeg4, h263, h264, vc1, mjpeg, flv, vp6, vp8, theora, dvvideo" in the vCodec="" field. Removing vCodec="DX50" and just leaving:

<Matches container="avi" />

causes ALL avi files to be fully transcoded, and this is not what i want, as there is no need to fully transcode 99% of my avi files.


Output from ffmpeg -i on one of the affected files is as follows:


ffmpeg version git-2012-05-19-d1384c0 Copyright (c) 2000-2012 the FFmpeg developers
built on May 19 2012 19:12:47 with gcc 4.5.2
configuration: --enable-gpl --enable-libfaac --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-nonfree --enable-version3 --enable-x11grab
libavutil 51. 53.100 / 51. 53.100
libavcodec 54. 21.101 / 54. 21.101
libavformat 54. 5.100 / 54. 5.100
libavdevice 53. 4.100 / 53. 4.100
libavfilter 2. 75.100 / 2. 75.100
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
Input #0, avi, from '[S04][E01][Scrubs] My Overkill.avi':
Duration: 00:24:00.23, start: 0.000000, bitrate: 1107 kb/s
Stream #0:0: Video: mpeg4 (DX50 / 0x30355844), yuv420p, 512x384 [SAR 1:1 DAR 4:3], 30 fps, 30 tbr, 30 tbn, 30k tbc
Stream #0:1: Audio: mp3 (U[0][0][0] / 0x0055), 48000 Hz, stereo, s16, 320 kb/s


anyone know what I'm doing wrong, or if this is even possible with Serviio?

[will]

This looks related viewtopic.php?f=7&t=7132

and the reply was "Create a ticket if it's necessary." from 2009? is this STILL not possible even with 1.0.1 released?

[will]

That thread was from last week, the last reply was yesterday, so it was reported after 1.0.1 was released.

whoops, mis-read the information posted. Checked bitbucket and didnt see a ticket in the system. Created a ticket. Thanks!