• 1
  • 3
  • 4
  • 5(current)
  • 6
  • 7
  • 17
[imx6] Deinterlacing feature
#61
Quote:Should we ship that consoleblank=0 by default?

I have it in my uEnv.txt and never tried without. Once the kernel blanks the display for whatever reason the panning will fail. Actually the codec unblanks the framebuffer at stream start but only fb1. Probably we would need to unblank fb0 as well.
Reply
#62
Good - then I will add this, too.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#63
Here is another Testbuild, it includes consoleblank=0 - I am currently running it on HD+ for more than 30 minutes, working fine.
If you get hangs, try the autostart.sh thingy from the previous page.

This patch does not include the kernel fix, I need to rebase that one, to apply it via the buildsystem (it needs more lines ;-))

https://dl.dropboxusercontent.com/u/5572...943.img.gz
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#64
OpenELEC 5.0.1 is out, but sadly without these patches.
Could you please compile a new patched image based upon 5.0.1? The previous build ran quite fine here.
Reply
#65
Use that: https://dl.dropboxusercontent.com/u/5572...fac26c.tar the only thing it's missing is the "release" bump, everything else is in.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#66
Thank you very much, fritsch! Many thanks also wolfgar & smallint for development!

Deinterlacing itself seems to be very fast now, but I still have problems playing various kind of streams whether interlaced or not.
This may or may not be directly related to deinterlacing - but perhaps due to the high frame-rate. And this in return could possibly still be related to field-doubling, or whatever these patches do.
Anyways, every high frame rate whether progressive or double frame-rate interlaced or not, seems to kills a/v syncing or proper video-decoding in some way.

Some experiences on a CuboxTV (=quad-core+1GB RAM):
Ex1:
DVB-streams:
http://www.sendspace.com/filegroup/EC1nu...UTm%2BsMRU
data0001.ts: 1280x720p50 (TV is switching to 50Hz). Many frame skips. Sometimes HDMI disconnects.
data0002.ts: 1920x1080i50 MBAFF (TV is switching to 25Hz). Ok. Double-fr-deinterlacing doesn't look good.
data0003.ts: 1920x1080i50 MBAFF (TV is switching to 25Hz). Plays flawlessly
Another DVB-stream as MKV:
1280x720p50: https://www.sendspace.com/file/yqbkjr
Video decoding seems to be too slow. Again many frame-skips. TV is at 50Hz. Temporary audio-skipping, some HDMI disconnects.

Ex2:
https://www.sendspace.com/file/uorxs5
1920x1080i60, 29.97fps MBAFF
Audio gets async very fast.

Ex3:
https://www.sendspace.com/file/h3znta
1920x1080i60, 29.97fps interlaced
Audio gets async even faster.

Ex2 & Ex3 are from BR, so at least video should be conforming to standards. Audio was trancoded to flac, though.
While playing the videos, CPU usage is quite low and it doesn't matter much if I activate/deacticate deinterlacing.

If I understand correctly deinterlacing is done after hardware decoding. And before these patches it was quite slow, and sometimes CPUs weren't fast enough.
But should't the chipset at least be capable of decoding 1920x1080i60?
Reply
#67
I will check data0001.ts which should work fine. What distribution have you installed and exactly what Kodi branch have you compiled?

Double rate does not make much sense if your TV is running at 25 Hz. The code should detect this (todo) and disable double rate. Double rate (as the name suggests) requires double the rate of the input material: 25*2 = 50Hz.

Quote:But should't the chipset at least be capable of decoding 1920x1080i60?

It actually is. Rendering is more of an issue.

Thank you for your feedback and I will take a look at your samples.
Reply
#68
Tried the 1/29 image last night on my I2 and de-interlacing is working quite well on both live TV and on the 1080i59.94_mpeg2.ts sample!

It could be that I'm paying more attention, but menu navigation did seem slower and the IR response seemed to miss some keypresses periodically. Not sure if the menu navigation is related to the move from 16 back to 32pp in uEnv.txt.

In any case, looks like it's time to buy you guys a round for the excellent work!
Reply
#69
smallint,
I'm using the image of fritsch, which is OpenELEC 5.0.1 with Kodi 14.1. Perhaps fritsch could give any further details.
Regarding 1920x1080i60: I just read that my quad-core should even decode 1920x1080p60 and deinterlacing is done "in HW"
http://www.iwavejapan.co.jp/product/iW%2...uction.pdf
Really odd.
Reply
#70
That images uses the work of smallint and wolfgar rebased on 14.1 integrated into openelec, basically: https://github.com/fritsch/OpenELEC.tv/commits/imx
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#71
Quote:data0001.ts: 1280x720p50 (TV is switching to 50Hz). Many frame skips. Sometimes HDMI disconnects.
data0002.ts: 1920x1080i50 MBAFF (TV is switching to 25Hz). Ok. Double-fr-deinterlacing doesn't look good.
data0003.ts: 1920x1080i50 MBAFF (TV is switching to 25Hz). Plays flawlessly

I tested all three samples and they played without problems on my box. The latter two even with double rate (as long as your display is running at 50Hz). Frame skips for the first sample are normal if you open the stats overlay. Just start the sample and let it run for some seconds, open the overlay 'o' and you should see that skips are almost 0 but start to increase quickly due to the overlay.

Quote:Sometimes HDMI disconnects.

Following wolfgars advice you should increase the IPU priority on AXI bus.

Code:
# devmem 0x020e0018 w 0xffffffff
# devmem 0x020e001c w 0xffffffff

Quote:Ex2:
https://www.sendspace.com/file/uorxs5
1920x1080i60, 29.97fps MBAFF
Audio gets async very fast.

Plays flawlessly for me even with double rate, no audio sync issues.

Note that I am running Kodi master and not the OpenELEC build. Maybe that makes the difference.
Reply
#72
I will do a new version, when the PR is opened with kodi master and exactly your branch.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#73
PR opened: https://github.com/xbmc/xbmc/pull/6351
Reply
#74
Thx much - I try to make a build during the weekend. Though - I am travelling again.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#75
Here are two builds:

image: https://dl.dropboxusercontent.com/u/5572...1bb.img.gz
release: https://dl.dropboxusercontent.com/u/5572...f981bb.tar

This is OpenELEC core with the tree of smallint.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
  • 1
  • 3
  • 4
  • 5(current)
  • 6
  • 7
  • 17

Logout Mark Read Team Forum Stats Members Help
[imx6] Deinterlacing feature3