[tudstudent]

what was the reason you wanted the xrandr output, because I do not see the link...

Furthermore what happens when e.g. I watch a 720P series?

[fritsch]

Are those questions sane?

In your link, you see:
<mode id="0x1ce" name="1920x1080" w="1920" h="1080" hz="23.97608" current="false" preferred="false"/>

and

<mode id="0x1c8" name="1920x1080" w="1920" h="1080" hz="24.00000" current="false" preferred="false"/>

which is perfect.

You did not have those modes at all before. Now you can easily choose: Adjust refreshrate to match video. It will switch to
23.976 when this matches the fps and to 24.0 when the video is 24.0 fps

720p is switched the same concerning the fps and then will be upscaled by a good quality scaler to 1080.

All fine from that pov.

[tudstudent]

Now I see, I was looking at the one line which said TRUE...
Thanks for the clarification.

Just noticed that my tv is dealing different with the signal.
First I just had a standard PC mode. Now I can select the cal-night and cal-day mode. So a double win.

I need to finish the config for suspend and I will post the log with current settings tomorrow morning.
My GF wants to watch some movies...

[fritsch]

Suspend(!) is highly not suggested at all ...

[tudstudent]

Small update:
Yesterday evening we tried to watch Sherlock (VC1). This now runs smoothly.
I turned "Adjust display refresh rate to match video" on, as you suggested.

What we noticed was that video looked like it was a lot faster (compared to the old settings), furthermore it looked sharper and clearer (coudl this be possible by not skipping frames)?
Besides that there was quite some input lag on the tv versus receiver (if kodi is running correct then I need to adjust this on my receiver).

I will supply all logs later this morning.

Suspend:
I have seen the negative effects of suspend (on a broken ubuntu install), though I have not found what is "highly not suggested", could you explain why not. This is also not included in the kodi suspend howto (that it is not recommended)

[fritsch]

Suspend:

Has nothing to do with kodi at all, but with "weak" drivers. In 9 out of 10 (if you are lucky) suspend won't return and you need to press the power button for a long time. Even worth, it might resume, but put the GPU into a state it does not like to do hw decoding anymore. We have seen your wireless driver spamming on page 1, which also shows that there is something not running that good as it could. Save the planet and shutdown :-)

Concerning the other question, use this as advancedsettings.xml:

Code:

<advancedsettings>
   <loglevel hide="false">0</loglevel>
   <samba>
    <clienttimeout>30</clienttimeout>
  </samba>
  <useddsfanart>true</useddsfanart> <!-- Do not use on Apple TV2/iOS/RPi/many Android systems -->
  <cputempcommand>sensors|sed -ne "s/Core 0: \+[-+]\([0-9]\+\).*/\1 C/p"</cputempcommand>
  <gputempcommand>sensors|sed -ne "s/temp1: \+[-+]\([0-9]\+\).*/\1 C/p"</gputempcommand>
  <gui>    
    <algorithmdirtyregions>3</algorithmdirtyregions>
    <nofliptimeout>0</nofliptimeout>
  </gui>    
<video>
  <latency>
    <delay>0</delay>
    <refresh>
      <min>23</min>
      <max>24</max>
      <delay>175</delay> <!-- set to zero or adjust if audio seems out of sync with 24p movies -->
     </refresh>
  </latency>
</video>
</advancedsettings>

TVs need "more time" to get a nice 23.976 fps displayed, therefore we have a measured delay of 175 ms for this mode. That way you only need to adjust it exactly once in the advancedsettings.xml and don't need to change something for your AVR, cause what works for 24p/23.976 will be different for e.g. 50hz -> see the 50 ms above.

[wsnipex]

Suspend(!) is highly not suggested at all ...

works fine for me on all my intel PCs. Only machine with issues is my AMD kabini system

[fritsch]

That makes it 66% alone for you :-) Which fits in my statistics.
Edit: And think of nvidia's binary blob, it's workaround to hardcoded EDID to not loose audio on resume and so on ... pain, pain, pain.

[wsnipex]

we are talking about intel based systems here, which have been working fine for me on all 4 generations since core i gen 1 to HSW.

[fritsch]

The user is running nvidia binary blobs:

12:35:09 T:139686568454080 NOTICE: GL_RENDERER = ION/PCIe/SSE2
12:35:09 T:139686568454080 NOTICE: GL_VERSION = 3.3.0 NVIDIA 340.76
12:35:09 T:139686568454080 NOTICE: GL_SHADING_LANGUAGE_VERSION = 3.30 NVIDIA via Cg compiler
12:35:09 T:139686568454080 NOTICE: GL_GPU_MEMORY_INFO_TOTAL_AVAILABLE_MEMORY_NVX = 524288

[tudstudent]

Hi Fritsch, correct I am running the Nvidia BLOB

Furthermore here are the latest current logs:
htpc01@htpc01:~$ dmesg|pastebinit
http://paste.ubuntu.com/11739108/
htpc01@htpc01:~$ DISPLAY=:0 /usr/local/lib/kodi/kodi-xrandr | pastebinit
http://paste.ubuntu.com/11739111/
htpc01@htpc01:~$ cat /etc/X11/xorg.conf | pastebinit
http://paste.ubuntu.com/11739112/


And the kodi log:
http://xbmclogs.com/pfdzsob3m

As you can see I added a MKV episode. However I was too fast to start the episode during a copyright message of the BR. Therefore it could not start.
That is why you see multiple start instances of the MKV. The last is the start from the episode. (to avoid confusion about errors and just hurriness of me).

Last: I am running kodi/xbmc for over 3 years, always with suspend and never had "real" problems. Sometimes there had been, but after some commits it is usually solved, so cannot really tell what the reason is for those hiccups. But at this moment running fine. Always waking up correct. I do have to agree that sometimes the audio is gone and only real solution is to restart kodi (sudo service kodi restart). After that it normally works fine again. The fixed edid trick i did not have to apply yet...

I wil apply those expert settings now. Curious how it works. Furthermore curious what you think of the logs.
The total recall BR is the only one which is "jumping" during playback (notably) can it be a bad BR or is it something in kodi?

[fritsch]

Furthermore here are the latest current logs:
htpc01@htpc01:~$ dmesg|pastebinit
http://paste.ubuntu.com/11739108/
htpc01@htpc01:~$ DISPLAY=:0 /usr/local/lib/kodi/kodi-xrandr | pastebinit
http://paste.ubuntu.com/11739111/
htpc01@htpc01:~$ cat /etc/X11/xorg.conf | pastebinit
http://paste.ubuntu.com/11739112/

All fine. Okay, then let's concentrate on bluray now. Try to play it as "iso" (what you normally do) and also mount the iso (mount -o loop) and play the video in that directly. Does that experience differ?

[fritsch]

Perhaps something additional, edit your /etc/security/limits.conf and add in a line before the #End of file

Code:

@audio             -       nice            -1

Make sure the user that is running kodi is in the audio group (id | pastebinit). To be fully sure pastebinit the above limits.conf after your changes. It will be picked up after a reboot.

[tudstudent]

Just a quick search about the why (next time when needed I need to be able to replicate this as well):
http://linuxmusicians.com/viewtopic.php?f=27&t=392
(And for others who are curious)

What do you mean by playing ISO as normally. This is what I did in the kodi.log in my last post.
Total recall is an .ISO

Here are my new files:
htpc01@htpc01:~$ cat /etc/security/limits.conf |pastebinit
http://paste.ubuntu.com/11739199/
htpc01@htpc01:~$ groups htpc01|pastebinit
http://paste.ubuntu.com/11739200/
htpc01@htpc01:~$ cat ~/.kodi/userdata/advancedsettings.xml |pastebinit
http://paste.ubuntu.com/11739206/

What I could do is take the following bluray(s):
- Total Recall ISO -> Play as iso && mount and then play
- The Book Thief ISO -> Play as iso && mount and then play

And create a log?

[fritsch]

Yes, please.

Edit: concerning limits.conf - it does not harm what you have done, but we only increase priority by 1 - and the other things we don't use.