Developers, do you need more info on the resolutions not being detected correctly?
#1
Recent builds apparently started having problems once more with resolutions/refreshes available detection. We talked about this here: http://forum.xbmc.org/showthread.php?tid=57427&page=3

Is there need for logs, guisettings.xml, stuff like that or you have this covered already? I'm asking because with the current "not ready for primetime state" it's tough to understand whether bug reports are good or bad for you (the homepage says "we ask that you hold off on bug reports" but Spiff mentioned here that it's ok to test, with the understanding that these are not "stable moments").
Reply
#2
Regarding refresh rate detection of the movie, it seems that the problem belongs to ffmpeg.

In the log when I play a H264 movie in a MKV container (fps = 23,976 for this file), I get this:

Quote:13:31:50 T:3720 M:977072128 DEBUG: CDVDDemuxFFmpeg::Open - av_find_stream_info starting
13:31:50 T:3720 M:974307328 DEBUG: CDVDDemuxFFmpeg::Open - av_find_stream_info finished
13:31:50 T:3720 M:974303232 INFO: ffmpeg[E88]: Input #0, matroska, from 'D:\WALL-E.mkv':
13:31:50 T:3720 M:974303232 INFO: ffmpeg[E88]: Duration: 01:38:41.98, start: 0.000000, bitrate: N/A
13:31:50 T:3720 M:974270464 INFO: ffmpeg[E88]: Stream #0.0: Video: h264, yuv420p, 1920x1080, PAR 1:1 DAR 16:9, 24 tbr, 1k tbn, 47.95 tbc
13:31:50 T:3720 M:974270464 INFO: ffmpeg[E88]: Stream #0.1: Audio: dca, 48000 Hz, 6 channels, s16

You can see that ffmpeg report "24 tbr". This is not correct, it should be 23.98. It reports also "47.95 tbc" that is exactly the double value of 23.98. Something is wrong here I think.
Of course with this file auto refrest rate doesn't work and set the refresh rate at 24hz instead of 23.98.

In the log when I play a VC1 movie in a MKV container (fps = 23,976 for this file), I get this:

Quote:13:38:53 T:3388 M:951459840 DEBUG: CDVDDemuxFFmpeg::Open - av_find_stream_info starting
13:38:53 T:3388 M:950919168 DEBUG: CDVDDemuxFFmpeg::Open - av_find_stream_info finished
13:38:53 T:3388 M:950919168 INFO: ffmpeg[D3C]: Input #0, matroska, from 'D:\LES CHORISTES.mkv':
13:38:53 T:3388 M:950919168 INFO: ffmpeg[D3C]: Duration: 01:36:17.83, start: 0.000000, bitrate: N/A
13:38:53 T:3388 M:950956032 INFO: ffmpeg[D3C]: Stream #0.0: Video: vc1, yuv420p, 1920x1080 [PAR 1:1 DAR 16:9], 23.98 tbr, 1k tbn, 23.98 tbc
13:38:53 T:3388 M:950956032 INFO: ffmpeg[D3C]: Stream #0.1: Audio: dca, 48000 Hz, 6 channels, s16

Here "tbr" and "tbc" values are correct and auto refresh rate works as it should.

This behavior happens only with mkv files. With m2ts files, everything works whatever the codec is.

Hope this help...
Reply
#3
I think it will be better (or more accurate) to get the fps value from the container instead of the video stream itself.
Reply
#4
Bear in mind that, while the points you raised are extremely valid and contribute the overall quality of vision experience, I was referring to the fact that on certain configurations (all?), XBMC doesn't seem able to identify the proper "resolution/refresh rates" available from the graphic card.

In my case, this means that instead of having [email protected], 1080p@24, 1080p@25, [email protected], 1080p@50, [email protected] and 1080p@60 I end up with only 1080p@60...
Reply
#5
Oups sorry !
I will post in more appropriate thread.
My above two posts can be deleted if necessary Wink
Reply
#6
Sorry for bumping the thread, I'd just like to understand whether it makes sense for me to try and test all forthcoming builds or if this is something you have your hands on already. Smile
Reply
#7
I would also like to know if this is a known problem or not. I've seen in the changelog that many things concerning frame rate problems been fixed. But it's impossible to test that out as XBMC can "find" available refresh rates now. Just one refresh rate is available.
Reply
#8
i think "we know it's broken right now, we will announce when we think things are in shape again" is a perfect statement for the current situation already.

my understanding here is the devs do not want to answer those questions right now, but will do again once they think all is running fine again and we still encounter issues.
cheers,azido :;):
Reply
#9
Well, spiff had this to say "as long as it's made perfectly clear that this is WIP code and that anyone grabbing it have to expect a bumpy ride, we're certainly not against it (rather the opposite). we're past the initial this-crap-won't-even-compile-stage and are at the why-doesnt-that-crap-render stage".

Considering this, I am only inquiring to see whether help is needed for troubleshooting this problem or not. Simple, ain't it? Smile
Reply
#10
Hello,

I am using the SVN 22943 and saw that in the setting --> Resolution, only the Desktop resolution can be set anymore ?, is that a feature or a Bug ?

I was a great feature of xmbc to change the resolution inside the Application, and when exiting to have the normal desktop resolution back...

Now i have to use scripts to set the resolution prior of starting xbmc and reverting it on xbmc exit.....

Is there a way to reenable the full list of resolutions in the Screen Settings ?

Thankyou in Advance,
Konstantin
XBMC, Intel P4 3.0GHz with HT, 2GB RAM, ATI 3450 HDMI GPU
Reply
#11
currently no.
Reply
#12
Hello spiff, thankyou for the fast reply!

Is this a wanted change or a problem due to the merge ?

Cheers,
Konstantin
XBMC, Intel P4 3.0GHz with HT, 2GB RAM, ATI 3450 HDMI GPU
Reply
#13
It's a wanted change.

99.9% of users do not ever want to change resolutions, and there is zero reason for them to do so.

I suspect if it's added back then it'll be some advanced setting.

An indication as to why you'd use such a thing would be useful.

Cheers,
Jonathan
Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.


Image
Reply
#14
Ok, I've seen Elupus claiming that the refresh rate switching wasn't working and that he fixed it.

But I still get (GL version SVN 23069) only my desktop resolution and refresh rate as selectable (plus the windowed option). As of 21930, which I'm still using, there are the full complement of 24, 25, 50 and 60Hz option for my TV native resolution (1080p).

Happening to everyone?
Reply
#15
Missed this and posted back in my old thread.

I might be missing something, will check and come back but...

1) This is what I need to check, maybe even if the different resolutions/refresh rates combos are not shown automatic refresh rate switching will happen. If it doesn't, I'll surely want my movies to play at 24fps, but the UI is far smoother at 60.
Edit: unfortunately I was right. If I start with the desktop at 60Hz, XBMC will start at 60Hz and 24fps content will play at 60Hz, even if 24Hz is available.
I'm not sure if you are missing this but we went over the need for autoswitching a long time ago. Maybe I'm not getting what you are trying to say, though.

2) Some people might like to keep their regular desktop at 720p but want to play back movies at 1080p. The lower resolution equals bigger characters, easier to read.
Reply

Logout Mark Read Team Forum Stats Members Help
Developers, do you need more info on the resolutions not being detected correctly?0