Linux VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52) +---- Thread: Linux VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 (/showthread.php?tid=165707) Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - lelouch - 2015-03-22 I followed the guide and the memory leak issue went away. On comparing the two systems I found out that on streaming iptv channels using 'udpxy' there is an issue of memory leak in kodi. If we dont use udpxy then there is no memory leak. Just sharing this information. If we try to play a iptv stream which does not exist or is temporarily down then the player waits for 30 Seconds until timeout is reached. Is there a way to reduce the 30 Seconds timeout in case when there is no stream ? Thank you. RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - Jorgensen - 2015-03-24 Is there anyway to delay the start of XBMC/KODI to after this event? Code: INFO: LIRC Connect: successfully started I am using the startup script from post 1. RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2015-03-24 Sadly lirc uses init.d to start and not upstart - see here: https://bugs.launchpad.net/mythbuntu/+bug/563139 for a lengthy workaround. Edit: You need to remove the init.d way of starting lirc and using the upstart script instead. RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - Jorgensen - 2015-03-25 (2015-03-24, 22:17)fritsch Wrote: Sadly lirc uses init.d to start and not upstart - see here: https://bugs.launchpad.net/mythbuntu/+bug/563139 for a lengthy workaround. Thanks for the link. I tried to follow the suggestions but something went wrong. The two startup scripts I am using: Code: xbmc@xbmc:~$ cat /etc/init/lirc.conf My xbmc upstart script: Code: xbmc@xbmc:~$ cat /etc/init/xbmc.conf If I remove lirc from /etc/init.d/ then Kodi never finds the /dev/lircd Code: 01:53:32 T:139824437864192 INFO: LIRC Process: using: /dev/lircd but if I leave lirc in /etc/init.d/ then Kodi boots up before LIRC is ready and I have to restart Kodi. So what is the correct way to "disable LIRC the init.d way"? PS: If this is off-topic, let me know and I'll use another tread. RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2015-03-25 http://manpages.ubuntu.com/manpages/hardy/man8/update-rc.d.8.html <- RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2015-03-25 And yeah you are fully off topic -> ubuntuforums.org is the correct place to ask as its their init foobar. RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2015-03-26 https://bugs.freedesktop.org/show_bug.cgi?id=82349#c8 <- this fixes the EDID issue - you need to patch some recent kernel and all will be fine :-) RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2015-03-26 Here is a kernel, that includes the byt fix and the EDID fix: https://dl.dropboxusercontent.com/u/55728161/linux-image-3.19.2-legacy%2Bedid%2B_3.19.2-legacy%2Bedid%2B-10.00.Custom_amd64.deb https://dl.dropboxusercontent.com/u/55728161/linux-headers-3.19.2-legacy%2Bedid%2B_3.19.2-legacy%2Bedid%2B-10.00.Custom_amd64.deb Much fun with testing. Source is at the usual location ... RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - AndyFurniss - 2015-03-26 (2015-03-19, 20:58)Ney Wrote:(2015-03-19, 20:22)fritsch Wrote: Good news. Been testing on my Baytrail ASrock Q1900DC-ITX with 40 mbit/s h264 1080i30 made from SVT test sequences. ftp://vqeg.its.bldrdoc.gov/HDTV/ Edit : above link seems to get mungled and broken this (hopefully) is the correct one - Code: ftp://vqeg.its.bldrdoc.gov/HDTV/ For madi/mcdi it just works without any overlay, with I get skips gputop looks like - Code: render busy: 91%: ██████████████████▎ render space: 165/131072 Code: render busy: 50%: ██████████ render space: 30/131072 The SVT I have are pretty much all panning - so visually you don't really get a chance to see the difference between bob - madi/mcdi do display 1 pix static weave correctly, on something like - http://www.w6rz.net/vertrez1080.zip (FWIW IIRC from years ago some w6rz streams have the wrong flag for field order - doesn't matter on this one though) Currently madi/mcdi doesn't quite work properly in the it's not field rate. This patch on top of https://github.com/fritsch/libva-intel-driver.git ppa-new-1.5.0 branch http://xbmclogs.com/paqmnxn6y/fefnv4/raw "works for me" field rate mcdi on burosch letters has a few artifacts that madi doesn't. On only one, out of eight SVT samples I have, can I see a very slight artifact with mcdi. Other HDTV I tried so far looks the same with both to me. RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2015-03-26 Most of the speed is sadly eaten by the full rgb conversion in vaPutSurface :-( We really hope that with EGL, we can avoid that and then have more performance available for VPP lanczo3 or that MCDI RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2015-03-26 Ah and btw. can you send the above patch on the bugtracker? So that gwenole and haihao can have a look? RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2015-03-26 Feedback for your patch: With that the flickering is gone. Burosch does not look that "pulsing" anymore. RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - AndyFurniss - 2015-03-26 Thanks for the feedback, I sent the patch to FDO. I notice Gwenole has a new commit on FDO intel-driver which looks to make some things more efficient including vaapi-bob, but I guess not m*di. I haven't tried that yet - from memory gpu top with vaapi-bob currently is 80% for 1080i30. So will egl let you read back yuv surfaces post decode/processing? RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - fritsch - 2015-03-26 yes, there is an API for that. RE: VAAPI: Nuc, Chromebox, HSW, IVB, Baytrail with Ubuntu 14.04 - devilstrike - 2015-03-30 Nice Work the dev have made, now i can watch 1080i(14mbit mpeg4 mbaff) with hardware deinterlacing(vaapi-bob) on my j1800 baytrail soc, so cpu from 60% on both cores to 10% usage on both cores. |