Login at Kodi Home

jjslegacy · 2015-12-22, 23:24

I certainly don't think I have any "crappy" hardware but I get your point.

You are incorrect though the projector can display 59.94 just fine. I am quite sure it can't display 1920x1200 though which is where the problem is. I still don't understand why Kodi is picking that as the resolution to try instead of the actual 1920x1080 59.94 that works fine.

I think that is:

1920x1200 (0xdf) 154.000MHz +HSync -VSync
h: width 1920 start 1968 end 2000 total 2080 skew 0 clock 74.04KHz
v: height 1200 start 1203 end 1209 total 1235 clock 59.95Hz

vs

1920x1080 (0xe1) 148.352MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.43KHz
v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz

I can change he KODI GUI just fine to 59.94 with no issues.

jjslegacy · 2015-12-22, 23:27

(2015-12-22, 23:17)fritsch Wrote:
(2015-12-22, 23:00)jjslegacy Wrote: I did test that briefly and it seemed to work but the video was choppy as I leave my kodi refresh rate at 23.97 because of the random issues I have switching resolution rates. I suppose this needs to be played at 60hz.

Seems like it's picking the first one that tmatces the refresh rate vs matching the resolution or maybe I am completely wrong

What I don't understand is why would that video choose 1920x1200 - any way for me to cleanup what the projector is supplying? Do I need to lock in an xorg or some other option?

Yes - you cannot play 29.97i at 23hz. Sorry - I cannot support all the crappy hardware out there ... ask the vendor of the projector, why they announce 59.94 hz when they cannot do it.

Quote:14:15:47 T:139884185327552 INFO: Output 'HDMI1' has 42 modes
14:15:47 T:139884185327552 INFO: ID:0x48 Name:1920x1080 Refresh:60.000000 Width:1920 Height:1080
14:15:47 T:139884185327552 INFO: Pixel Ratio: 0.994500
14:15:47 T:139884185327552 INFO: ID:0xe0 Name:1920x1080 Refresh:50.000000 Width:1920 Height:1080
14:15:47 T:139884185327552 INFO: Pixel Ratio: 0.994500
14:15:47 T:139884185327552 INFO: ID:0xe1 Name:1920x1080 Refresh:59.940201 Width:1920 Height:1080
14:15:47 T:139884185327552 INFO: Pixel Ratio: 0.994500
14:15:47 T:139884185327552 INFO: ID:0xe4 Name:1920x1080 Refresh:24.000000 Width:1920 Height:1080
14:15:47 T:139884185327552 INFO: Pixel Ratio: 0.994500
14:15:47 T:139884185327552 INFO: ID:0xe6 Name:1920x1080 Refresh:23.976080 Width:1920 Height:1080
14:15:47 T:139884185327552 INFO: Pixel Ratio: 0.994500
14:15:47 T:139884185327552 INFO: ID:0xdf Name:1920x1200 Refresh:59.950169 Width:1920 Height:1200

See the 59.95 mode ...

Yes I see that - 59.94 vs 59.95 can't we just round down Smile

If xrandr would just let me delete a mode all would be easy but apparently that doesn't work.

Does seem very strange that the projector (a rather expensive JVC) would be outputting that. I will have to connect directly to the projector and remove the AVR just to make sure something funny isn't going on.

**fritsch** · 2015-12-22, 23:39

Resolution only takes the width (!) into account, so for your 1920x1080 and your 1920x1200 the one that is evaluated last wins ...

jjslegacy · 2015-12-22, 23:43

gotcha - well thanks for the help/info. It's only a few videos so I will just handle those differently Hope the debug for the audio issue helps.

**fritsch** · 2015-12-23, 00:01

Can't you get rid of the of that 4:3 resolution? I did not see the audio issue cause of the noise ... I will upload a build that will consider the aspect ratio and keep the ratio the TV originally had.

You find it (after it's fully up 45 minutes) at the usual location, it has jjslegacy in its name.

jjslegacy · (This post was last modified: 2015-12-23, 00:17 by jjslegacy.)

get rid of that resolution how?

The video with the audio issues shouldn't have had any resolution issues. What extra noise was in the log?

this log right?: http://sprunge.us/cWPX

Thanks for the new build - amazing service around here

**fritsch** · (This post was last modified: 2015-12-23, 01:04 by fritsch.)

Build is up ... this can btw. be run by everyone - it does not hurt ...

For jjslegacy's Audio: Disable passthrough - it is inferior and proper sync is not possible.

jjslegacy · 2015-12-23, 01:15

Thanks for the quick turnaround. I got a quick test in before the family came home.

For the Frozen planet video that went straight to a blank screen it works perfectly!

The Life video still locks up at the kodi screen and audio starts to play so there must be somthing more there. I will generate a new debug file as soon a I get back down there later.

I have been disabling passthrough but have been testing back and forth to see if newer builds have it working.

What I haven't been able to figure out is - am I missing anything by not using it? Any limitations or situations that aren't handled properly?

Thanks again!

jjslegacy · (This post was last modified: 2015-12-23, 05:10 by jjslegacy.)

Interesting the Life movie in VLC reports resolution 1920x1088 and is VC1
Frozen planet reports: 1920x1090 mpeg-4 avc

Debug log for Life video: http://sprunge.us/PXLe

Video plays with hardware acceleration turned off for VC1 but it's choppy at times as a single core hits 100% repeatedly so not quite watchable although close.

ilovethakush · 2015-12-23, 06:33

On my chromebox, when I update from 6.0.98 to the latest test build, I lose a lot of my database. Even tried updating to the earliest available test build after restoring backup and still I lose a lot of my database.

**fritsch** · (This post was last modified: 2015-12-23, 09:52 by fritsch.)

(2015-12-23, 04:58)jjslegacy Wrote: Interesting the Life movie in VLC reports resolution 1920x1088 and is VC1
Frozen planet reports: 1920x1090 mpeg-4 avc

Debug log for Life video: http://sprunge.us/PXLe

Video plays with hardware acceleration turned off for VC1 but it's choppy at times as a single core hits 100% repeatedly so not quite watchable although close.

VAAPI still cannot decode VC-1 Interlaced content. This is a driver bug intel won't fix. We cannot do anything about it.

I suggest: Convert this 1080i VC1 files to progressive using ffmpeg and yadif deinterlacer and done ...

**fritsch** · 2015-12-23, 09:50

(2015-12-23, 06:33)ilovethakush Wrote: On my chromebox, when I update from 6.0.98 to the latest test build, I lose a lot of my database. Even tried updating to the earliest available test build after restoring backup and still I lose a lot of my database.

Database version is bumped - rescan your content. If you use mysql, make sure that your server supports creating a new DB. Besides that - not a single idea without your logfiles ...

sat4all · (This post was last modified: 2015-12-23, 12:12 by sat4all.)

here is the debug log about a/v sync problem.
true-hd suffers more from this problem, audio is away ahead with an a/v:-10.12x while it's arround -4.600...-7.000 for dts-hd.

thanks much

**fritsch** · 2015-12-23, 12:53

We currently don't have a nicely working sync method for Passthrough - it works as it works - you are welcome to implement the IEC burst pause packages. I cannot suggest anyone using passthrough currently and in general at all.

ilovethakush · 2015-12-23, 18:09

(2015-12-23, 09:50)fritsch Wrote:
(2015-12-23, 06:33)ilovethakush Wrote: On my chromebox, when I update from 6.0.98 to the latest test build, I lose a lot of my database. Even tried updating to the earliest available test build after restoring backup and still I lose a lot of my database.

Database version is bumped - rescan your content. If you use mysql, make sure that your server supports creating a new DB. Besides that - not a single idea without your logfiles ...

That's definitely the reason why, no need for logfiles here. I could always just rescan my content, but I'd rather not cause it's not just a loss of scanned content, I changed all of the artwork and some sorting for my movies/tv as well, and I lose all of that too.

Isn't there a version I can update to that won't lose the database, and then another, and then another until I get to the latest build. Or am I mistaking about that?