[un1versal]

There is no reason that file wont play 100% smooth like butter on ION, look at your interlacing settings in XBMC like suggested above and consider adding xorg.conf for tweaking the 23.976p and 24p playback and stick to 304.XX drivers.

[nickr]

Is this a VDPAU Features "Note 1" GPU? If so there is every reason why it wouldn't play properly - hardware doesn't accerate on that size video frame:

VDPAU FEATURES NOTE 1

GPUs with this note may not support H.264 streams with the following widths:
49, 54, 59, 64, 113, 118, 123, 128 macroblocks (769-784, 849-864, 929-944,
1009-1024, 1793-1808, 1873-1888, 1953-1968, 2033-2048 pixels).

Your video is 1808 wide.

To find out, what is the output of lspci -n ?

[un1versal]

mmm I missed that, though if a sample was made available I would like to test that on mine.

Its interesting wording, the ION is B1, yet that note says may not, its not a "definitive" cannot note (I suppose some ppl may interpret "may not" differently), just one reason why I would like to test that, just to see. Though my ION is not a zotac base, and each manufacturer did their own implementation with some variations which dont make all the gpus alike.

Idle definetly like to test a sample.

[fbacher]

It appears to be caused by the 1808. I checked and I have 8 movies recorded thus and they all exhibit this problem. Curiously, I have known that a number (most, if not all) of the recordings from the cablecard were in 1808, but I thought that HandBrake cleaned that up. Perhaps it sometimes can not. At least it is only 8 movies.

I modified my xorg file and XBMC settings for 24p, from above and reverted my drivers to 304.88. Same result.

If you would like an 1808 sample, I can supply one if you can tell me how to extract a segment from an .mkv file.

[fritsch]

Cable card is 1920 x 1088

[nickr]

WHAT IS THE OUTPUT OF lspci -n

[un1versal]

If you would like an 1808 sample, I can supply one if you can tell me how to extract a segment from an .mkv file.

Well you can segment a mkv with mkvtoolnix I believe, maybe even handbrake..

Did you teak the interlacing settings too?

Anyway give nickr the output of lspci -n before he blows up.

Ill await for sample (dropbox or google drive) and then well see, Ill post my lspci as well so as to get comparison going.

[nickr]

Anyway give nickr the output of lspci -n before he blows up.

LOL.
I know on my ION1 machine that 576p movies (which at 16:9 are 1024 pixels wide) don't get the vdpau treatment, but they work fine on the ION2 machines. To be sure we need the product id - lspci -n shows vendor:product id's numerically (hence -n) so we can search through the nvidia readme for the product number and see what is supoprted.

[un1versal]

Its Feature set B1 on all fields except one and that one field is B2, either way ION 1 is what were talking about and depending who makes it some will be better than others, by simple nature each manufacturer implemeted the ION design in they're own way. Specially the earlier ION single core, but Ive seen same ION machines from Asus and Zotac and asrock and all varied in bits added/removed.

Rain the sample.

[fbacher]

fbacher@tinkie:~$ lspci -n
00:00.0 0600: 10de:0a82 (rev b1)
00:00.1 0500: 10de:0a88 (rev b1)
00:03.0 0601: 10de:0aad (rev b2)
00:03.1 0500: 10de:0aa4 (rev b1)
00:03.2 0c05: 10de:0aa2 (rev b1)
00:03.3 0500: 10de:0a89 (rev b1)
00:03.5 0b40: 10de:0aa3 (rev b1)
00:04.0 0c03: 10de:0aa5 (rev b1)
00:04.1 0c03: 10de:0aa6 (rev b1)
00:06.0 0c03: 10de:0aa7 (rev b1)
00:06.1 0c03: 10de:0aa9 (rev b1)
00:08.0 0403: 10de:0ac0 (rev b1)
00:09.0 0604: 10de:0aab (rev b1)
00:0a.0 0200: 10de:0ab0 (rev b1)
00:0b.0 0101: 10de:0ab4 (rev b1)
00:0c.0 0604: 10de:0ac4 (rev b1)
00:10.0 0604: 10de:0aa0 (rev b1)
00:15.0 0604: 10de:0ac6 (rev b1)
00:16.0 0604: 10de:0ac7 (rev b1)
00:17.0 0604: 10de:0ac7 (rev b1)
00:18.0 0604: 10de:0ac7 (rev b1)
02:00.0 0480: 1131:7164 (rev 81)
03:00.0 0300: 10de:087d (rev b1)
04:00.0 0280: 168c:002a (rev 01)

[nickr]

OK the video device is 10de:087d, which definitely has the limitation referred to in Post 17

Try to encode your video at an allowed width. If you want 1080p then the correct width is 1920, which does work.

[un1versal]

If you would like an 1808 sample, I can supply one if you can tell me how to extract a segment from an .mkv file.

@fbacher
I had a look into this with mkvtoolnix

(mkvtoolnix) - global tab, enable splitting and fine tune sizes etc

I even found a nice how to with that thing called google http://www.techfleece.com/2011/06/18/how...kvtoolnix/

@nickr

Im sure that just because a file isnt vdpau accelerated the ION still has enough teeth, I recall several 1080p files mpeg4 which the ION doesnt accelerate and they play just fine, a test will tell how different ION1 handles that specific frame size.

[nickr]

Yeah good luck with that. Its an atom after all. What specific mpeg4 codec are you referring to?

[fbacher]

I created a 28M file that demonstrates the problem. If this is too big I can create a shorter clip. I used mkvmerge --split size:20m to create it.

http://feuerbacher.us/data/1808.mkv

[fbacher]

In case anyone is curious as to how I got these 1808 files:

I have mythtv with an InfiniTV card (on Ubuntu). I record mostly Turner Classic Movies. Sometimes the mpeg.ts files are not perfect and apparently come as 1808. I use Avidemux to trim the files and then feed to Handbrake, which is running as a background script using settings that I came up with after painful experimentation.

I did look at tools for fixing problems, such as projectX, mpeg2repair, Ts4Np, VideoRedo, etc. but none were completely satisfactory since a) they could not fix all problems b) frequently created as many problems as fixed c) many ran only on windows d) significant problems did not occur very often.

After each encode is complete I use XBMC (ubuntu i5-HD4000 box) to sniff test it to make sure that it is okay. All of these problematic movies work just fine there. Now I find that I have 8 which the ION hates.

I considered hard coding the width that HandBrake uses, but thought that it might a) slow the encoding down even more b) introduce unnecessary error (blur/artifacts) c) complicate life

The specific Handbrake options that I use are:

${NICE} HandBrakeCLI\
${titleOption} \
--encoder x264 \
--quality 19.0 \
--rate 23.976 \
--keep-display-aspect \
--decomb \
--detelecine \
--aencoder copy \
--audio-fallback ac3 \
--audio ${audioTracks} \
--aname English-Surround \
--ab auto \
--mixdown auto \
--markers \
--encopts "b-adapt=2:rc-lookahead=50:ref=5:me=umh:bframes=5ubme=8:partitions=all:deblock=-1,-1:psy-rd=1|0.15" \
--input "${filePath}" \
--output "${ENCODING_DIR}"/"${movieName}.mkv"