Status of VC1 on Intel NUC hardware?
#31
And please don't double post ... I replied in the other thread where you posted that issue.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#32
(2015-02-05, 17:31)fritsch Wrote: Did somebody even try the build I linked? Or posted the relevant logfiles?

I tried the build you posted (Feb 3 special VC1 build you posted) and posted log files... (in that other thread though.)

Honestly my reason to post here would be to get feedback from a slightly different Vaapi build. If I could swap out my Chromebox for a NUC and lose this issue then that works for me.
Reply
#33
For VC-1 Interlaced, here is work Fernet did a year ago: https://github.com/fritsch/FFmpeg/commits/vc1 which was stopped as intel did not contribute a single thing. Might work with the libva-driver-intel VC1 patch I posted longer ago.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#34
I'd like to revive this topic because I have the same question/issue as mentioned earlier this thread. I own the DE3815TYKHE (Atom E3815) running OpenElec and I did enable hardware acceleration VAAPI for VC-1. However, when I play remuxed VC-1 encoded mkv's of 1080p blu-rays, I get blocking artifacts. While it was my understanding this Intel NUC is capable of playing 1080p VC-1 smoothly. Was I mistaken? Is the Atom E3815 simply not capable? Or is there something I can try to fix it?
Reply
#35
I still am having issues VC-1's on my nuc running openelec. (DN2820 Celeron). I'm going to try the VAAPI again but I don't recall it working before. All else seems fine...except of course my Marantz 7702's inability to down mix the multi channel LPCM output to two channel for zone 2!!!

Still don't know what that issue is about when the 7702 d-mixes my DTV box DD to 2 channel no problem. Oh well.

James
Reply
#36
No status. Intel refuses to implement it for VAAPI on linux. They only support VC-1 progressive - not interlaced.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#37
(2015-02-05, 14:59)fritsch Wrote: https://ffmpeg.org/pipermail/ffmpeg-deve...67384.html <- painful read up:-)
FFmpeg can now finally use Libyami via VAAPI for hardware offload of video transcode on the Intel GPU:

https://github.com/01org/ffmpeg_libyami

Libyami now also supports:
* MPEG2, VC1, H.264, H.265, VP8, VP9, JPEG ad-hoc decoder for video decoding
* H.264, H.265, VP8, JPEG ad-hoc encoder for video encoding
* CSC and scaling

https://github.com/01org/libyami
Reply
#38
No, that's not ffmpeg. This is a special fork of the libyami people and nowhere in ffmpeg.

VC1 <- progressive only. As the interlaced limitation is _in_ the driver.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply

Logout Mark Read Team Forum Stats Members Help
Status of VC1 on Intel NUC hardware?0