(2015-05-08, 10:12)gurabli Wrote:

(2015-05-08, 09:34)fritsch Wrote: Concerning Vivid I answered all those questions two pages back.

No idea - did not see any BRW news yet, sadly.

Here: http://forum.kodi.tv/showthread.php?tid=165707&pid=1990573#pid1990573 (it needs special care for suspend / shutdown options, though) - minimal update instructions is three pages back.

Vivid: sorry, my mistake, I'm doing ten things at a time and missed this. Excellent, will look into this.

BRW: I hope there will be some news really soon. Do you plan to get a BRW board once it is released and test who it will perform?

(2015-05-11, 22:17)noggin Wrote: No - running MCDI VAAPI on a 2955u Chromebox with Freeview SD 576i and HD 1080i content, and Freesat HD 1080i stuff. No odd artefacts.

(2015-05-11, 22:17)noggin Wrote: No - running MCDI VAAPI on a 2955u Chromebox with Freeview SD 576i and HD 1080i content, and Freesat HD 1080i stuff. No odd artefacts, even with the Freeview HD hybrid 25p/50i dynamic encoder switching.

(2015-05-11, 22:32)mattlach Wrote:

(2015-05-11, 22:17)noggin Wrote: No - running MCDI VAAPI on a 2955u Chromebox with Freeview SD 576i and HD 1080i content, and Freesat HD 1080i stuff. No odd artefacts.

Good to know. Thank you. it might just be the terrible video quality of Globo Internacional that is doing it then...

If I may ask, which scaler do you use?

I've been playing around with the ones fritsch mentioned in the first page, and can't seem to decide which one I like best for the chromebox. Lanczos3 of course looks great, but the differences are minor to my eyes.

One downside with Lanczos 3 I have found is that on the Chromebox it can load the unit enough to kick the fan into an audible rpm, which is a little annoying. Though, this hasn't happened in a little bit, so I wonder if the fan settings were updated the last time I updated SeaBIOS.

I wish SeaBIOS were more configurable, and I could make my own fan profile. It's often blowing audibly at ~65C, which is silly considering the Intel Tmax is 100C.

I tried installing fancontrol in linux, but the setup unfortunately doesn't detect any PWM fans, so the Chromebox must use some non-standard application compared to Desktops there.

--Matt

(2015-05-12, 09:23)wsnipex Wrote:

(2015-05-11, 22:32)mattlach Wrote: One downside with Lanczos 3 I have found is that on the Chromebox it can load the unit enough to kick the fan into an audible rpm, which is a little annoying. Though, this hasn't happened in a little bit, so I wonder if the fan settings were updated the last time I updated SeaBIOS.

I wish SeaBIOS were more configurable, and I could make my own fan profile. It's often blowing audibly at ~65C, which is silly considering the Intel Tmax is 100C.

I tried installing fancontrol in linux, but the setup unfortunately doesn't detect any PWM fans, so the Chromebox must use some non-standard application compared to Desktops there.

--Matt

did you install lm-sensors?

(2015-05-12, 08:21)fritsch Wrote: Provide a Debug Log and the very best would be a sample of this stream that shows the issue.

If you can replace the backend to VDR and use VNSI and retest.

(2015-05-12, 08:21)fritsch Wrote: Provide a Debug Log and the very best would be a sample of this stream that shows the issue.

If you can replace the backend to VDR and use VNSI and retest.

Quote:[ 0.425926] vesafb: mode is 1920x1080x32, linelength=7680, pages=0
[ 0.425927] vesafb: scrolling: redraw
[ 0.425928] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.425942] vesafb: framebuffer at 0xe0000000, mapped to 0xffffc90004e80000, using 8128k, total 8128k
[ 0.528365] Console: switching to colour frame buffer device 240x67

Quote:11:59:32 T:140103409121024 ERROR: OutputPicture - failed to configure renderer
11:59:32 T:140103409121024 NOTICE: fps: 23.976024, pwidth: 1280, pheight: 720, dwidth: 1280, dheight: 720
11:59:32 T:140103392335616 WARNING: CDVDMessageQueue(audio)::Get - asked for new data packet, with nothing available
11:59:37 T:140103409121024 WARNING: CRenderManager::Configure - timeout waiting for state
11:59:37 T:140103409121024 ERROR: OutputPicture - failed to configure renderer
11:59:37 T:140103409121024 NOTICE: fps: 23.976024, pwidth: 1280, pheight: 720, dwidth: 1280, dheight: 720

(2015-05-14, 02:24)mattlach Wrote:

(2015-05-12, 08:21)fritsch Wrote: Provide a Debug Log and the very best would be a sample of this stream that shows the issue.

If you can replace the backend to VDR and use VNSI and retest.

fritsch,

Here is the kodi.log file and sample video stream requested.

Some details:

Hardware:
Asus Chromebox
Haswell Celeron 2955u dual core 1.4ghz, no HT
2GB ram, single channel

OS:
Ubuntu Linux 15.04 (Vivid) Server Edition (couldn't find a mini install iso for Vivid)

Software:
Latest Kodi from stable repo, installed per 15.04 instructions earlier in this thread. No window manager running. Kodi is a session.

Problem:
Visual artifacting during playback only with deinterlace set to "Auto", exhibited as skips or jumps. Artifacting goes away when played with deinterlace "on" or "off"

The stream was originally played using Janbar's MythTV plugin, but for the purpose of this test I manually extracted the mpeg file from the backend and dumped it into a library folder and played it from there, to minimize any plugin variables.

In this particular clip the worst instances are during ads (great opportunity for you to experience some stupid american car ads :p ), but this happens across many channels during normal playback, not just ads.

The log file consists of me booting the system, playing the file, followed by turning off debug logging.

Worth noting: During playback I noticed that the fps readout on the top of the screen (the one that appears when you enable debug logging) was fluctuating. Sometimes it was 59fps, sometimes 24fps. The video file claims to me 30fps, but I don't recall seeing this number at the top of the screen at all.

Appreciate the help!

--Matt