View Full Version : [MOVED] Problems starting XBMC fullscreen
AllanMar
2009-03-09, 05:06
So i'm using driver 180.37 with SVN 18345 (has the same problem with all previous versions also)
When i start XBMC with 1080p Fullscreen, all my video plays choppy and out of sync with lots of dropped frames. When I start with resolution set to auto (it dosnt open fullscreen), then change it to 1080p it works perfectly until the next restart.
Here is my xbmc.log:
http://pastebin.com/m4b326adb
Any ideas whats going on here?
So i'm using driver 180.37 with SVN 18345 (has the same problem with all previous versions also)
When i start XBMC with 1080p Fullscreen, all my video plays choppy and out of sync with lots of dropped frames. When I start with resolution set to auto (it dosnt open fullscreen), then change it to 1080p it works perfectly until the next restart.
Here is my xbmc.log:
http://pastebin.com/m4b326adb
Any ideas whats going on here?
I get the same thing and had to go back to the build of XBMC I was running without hardware acceleration of video decoding.
The cause of the choppyness is 9/10 times pulseaudio. killall -9 pulseaudio before launching xbmc perhaps.
Yes, the thumbnail generation is a known issue - i'll keep it in mind for my next batch of fixes but its a fairly low priority.
AllanMar
2009-03-09, 22:37
The cause of the choppyness is 9/10 times pulseaudio. killall -9 pulseaudio before launching xbmc perhaps.
Yes, the thumbnail generation is a known issue - i'll keep it in mind for my next batch of fixes but its a fairly low priority.
Ive tryed killall -9 pulseaudio and i compiled with --disable-pulse. The thing is, this ONLY occurs when XBMC is started in 1080p(dosnt work when i hit \ to take it out of fullscreen either). If i start it in auto, and then choose 1080p/60 (or 1920x1080 @ 50hz) and hit test resolution 1080p plays flawlessly (until i restart xbmc). So I guess the big question would be, how does XBMC handle it differently between starting in a resolution and changing it afterwards? something to do with XRanR modes perhaps? Im hoping mayb you can shed some light on this.
Ive tryed killall -9 pulseaudio and i compiled with --disable-pulse. The thing is, this ONLY occurs when XBMC is started in 1080p(dosnt work when i hit \ to take it out of fullscreen either). If i start it in auto, and then choose 1080p/60 (or 1920x1080 @ 50hz) and hit test resolution 1080p plays flawlessly (until i restart xbmc). So I guess the big question would be, how does XBMC handle it differently between starting in a resolution and changing it afterwards? something to do with XRanR modes perhaps? Im hoping mayb you can shed some light on this.
I am getting the EXACT same behavior! I don't have pulseaudio installed. MythTV and mplayer (both with VDPAU) play fine. XBMC also plays fine if I follow the steps above, until I restart it of course.
I'm using r18361, with nvidia driver 180.37.
I tried:
make reallyclean
./configure --disable-pulse
make
./xbmc.bin
If you need more info, or some log files, or need me to test something, I'm glad to help.
-- Kevin
AllanMar
2009-03-09, 23:27
I am getting the EXACT same behavior! I don't have pulseaudio installed. MythTV and mplayer (both with VDPAU) play fine. XBMC also plays fine if I follow the steps above, until I restart it of course.
I'm using r18361, with nvidia driver 180.37.
I tried:
make reallyclean
./configure --disable-pulse
make
./xbmc.bin
If you need more info, or some log files, or need me to test something, I'm glad to help.
-- Kevin
Glad to hear I'm not the only one, hopefully motd2k has some ideas. Out of curiosity though, what hardware do you have? M3N78-EM(8300GS) & 4850e X2 with 2x2gb ram here
Glad to hear I'm not the only one, hopefully motd2k has some ideas. Out of curiosity though, what hardware do you have? M3N78-EM(8300GS) & 4850e X2 with 2x2gb ram here
Jetway JNC62K (Geforce 8200 IGP), AMD 5050e, 1x2gb RAM (only one slot on board)
And yes, I know about the AMD and IGP bus speed bottleneck. I have my CPU set to not go below 1.8 GHz with cpufreq.
-- Kevin
Jetway JNC62K (Geforce 8200 IGP), AMD 5050e, 1x2gb RAM (only one slot on board)
And yes, I know about the AMD and IGP bus speed bottleneck. I have my CPU set to not go below 1.8 GHz with cpufreq.
-- Kevin
I am having onbord Geforce 8100. 1080p play fine in full screen, resolution was set at default native resolution 1680x1050. The only thing that I am worried about switching to full screen native resolution is when "sync to v blank" is enabled, the gui will be sluggish, while disabled, the CPU usage will be 100% on one core. But none of them are affecting video playback.
I am using XBMC-vdpau r18331, nvidia 182.37, ubuntu 8.10. CPU runs at 1.8G constantly.
Maybe you need to tweak your xorg.conf a bit.
Option "TwinView" "0"
Option "UseEvents" "true"
Option "NvAGP" "1"
Option "Coolbits" "1"
Option "NoLogo" "True"
Option "PixmapCacheSize" "1000000"
Option "AllowSHMPixmaps" "0"
Option "TripleBuffer" "True"
Option "RenderAccel" "True"
they are in the screen section.
Have you tried to force the CPU run at the max frequency possible and see what will happen, since the memory bandwidth of your system is bit limited (only single channel)?
@Allanmar, @kross
I have an Asus M3n78-VM -- geforce 8200 based mobo and experience the same thing. It should be noted, however, that this is not specific to the VDPAU branch so this discussion should be taken to an appropriate thread as this is a general bug in XBMC. I tested the latest intrepid SVN PPA (r18324) and r18359 vdpau branch and both have the same behavior.
--Nick
I am having onbord Geforce 8100. 1080p play fine in full screen, resolution was set at default native resolution 1680x1050. The only thing that I am worried about switching to full screen native resolution is when "sync to v blank" is enabled, the gui will be sluggish, while disabled, the CPU usage will be 100% on one core. But none of them are affecting video playback.
I am using XBMC-vdpau r18331, nvidia 182.37, ubuntu 8.10. CPU runs at 1.8G constantly.
Maybe you need to tweak your xorg.conf a bit.
Option "TwinView" "0"
Option "UseEvents" "true"
Option "NvAGP" "1"
Option "Coolbits" "1"
Option "NoLogo" "True"
Option "PixmapCacheSize" "1000000"
Option "AllowSHMPixmaps" "0"
Option "TripleBuffer" "True"
Option "RenderAccel" "True"
they are in the screen section.
Have you tried to force the CPU run at the max frequency possible and see what will happen, since the memory bandwidth of your system is bit limited (only single channel)?
I added your options to my xorg.conf. It didn't help. I also set the cpu freq to max, as seen:
htpc:~# cpufreq-set -g performance
htpc:~# cpufreq-info
cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@lists.linux.org.uk, please.
analyzing CPU 0:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 2.60 GHz
available frequency steps: 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1000 MHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance
current policy: frequency should be within 1.80 GHz and 2.60 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 2.60 GHz (asserted by call to hardware).
cpufreq stats: 2.60 GHz:6.27%, 2.40 GHz:0.17%, 2.20 GHz:0.14%, 2.00 GHz:0.17%, 1.80 GHz:93.25%, 1000 MHz:0.00% (2508)
analyzing CPU 1:
driver: powernow-k8
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 2.60 GHz
available frequency steps: 2.60 GHz, 2.40 GHz, 2.20 GHz, 2.00 GHz, 1.80 GHz, 1000 MHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance
current policy: frequency should be within 1.80 GHz and 2.60 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 2.60 GHz (asserted by call to hardware).
cpufreq stats: 2.60 GHz:6.27%, 2.40 GHz:0.17%, 2.20 GHz:0.14%, 2.00 GHz:0.17%, 1.80 GHz:93.25%, 1000 MHz:0.00% (2508)
@Allanmar, @kross
I have an Asus M3n78-VM -- geforce 8200 based mobo and experience the same thing. It should be noted, however, that this is not specific to the VDPAU branch so this discussion should be taken to an appropriate thread as this is a general bug in XBMC. I tested the latest intrepid SVN PPA (r18324) and r18359 vdpau branch and both have the same behavior.
--Nick
Ah, interesting! motd2k is off the hook then! :D
Thanks,
-- Kevin
AllanMar
2009-03-10, 03:32
@Allanmar, @kross
I have an Asus M3n78-VM -- geforce 8200 based mobo and experience the same thing. It should be noted, however, that this is not specific to the VDPAU branch so this discussion should be taken to an appropriate thread as this is a general bug in XBMC. I tested the latest intrepid SVN PPA (r18324) and r18359 vdpau branch and both have the same behavior.
--Nick
Well I'm not really sure if that is good or bad news. lol. I was wondering that but my processor struggles with 1080p without vdpau so I wasnt sure.
EDIT: Found this: http://xbmc.org/trac/ticket/4884 sounds similar, unfortunately its 6 months old. The workaround there also dosnt help.
EDIT2: Actually I remember a few posts back motd2k said he had basically the same hardware running and wasn't having any problems. So I wonder whats different with our setup(s)?
Allan/Kross/Mr.B
What video are you using to test 1080p? Killa?
xnappo
AllanMar
2009-03-10, 04:32
Allan/Kross/Mr.B
What video are you using to test 1080p? Killa?
xnappo
I have several x264 movies, some VC1, and I've tried killa too. All have the same result, also killa performs worst when im having the problems (no surprise). All will play fine as long as xbmc is not started in 1080p
Im thinking mayb this has something to do with XRandR and setting modes? In my xbmc.log i have:
When starting in auto
22:15:25 T:3880572896 M:109060096 INFO: XRANDR: /home/allan/xbmc-vdpau/XBMC/xbmc-xrandr --output default --mode 0x10d
22:15:26 T:3880572896 M:105652224 DEBUG: Constructing surface 1280x720, shared=(nil), fullscreen=0
And theres no more mention of that again when i change to 1080p manually (will still play fine)
When i start with 1080 i get this though:
22:17:42 T:2299250656 M: 87248896 WARNING: CXRandR::SetMode: found alternative mode (same hz): default mode: 0x138.
22:17:42 T:2299250656 M: 87248896 INFO: XRANDR: /home/allan/xbmc-vdpau/XBMC/xbmc-xrandr --output default --mode 0x138
22:17:42 T:2299250656 M: 71061504 DEBUG: Constructing surface 1920x1080, shared=(nil), fullscreen=0
AllanMar
2009-03-10, 14:38
Just out of curiosity, have you tried what I been mentioning earlier as a problem? Try starting XBMC in Auto resolution, then goto settings, change to 1080 and hit test resolution, then try playing your video
Just out of curiosity, have you tried what I been mentioning earlier as a problem? Try starting XBMC in Auto resolution, then goto settings, change to 1080 and hit test resolution, then try playing your video
Wow - well I thought my system just couldn't handle killa even with VDPAU, but I finally followed your instructions the right way, and indeed it plays completely smoothly following that sequence! I have only had this setup a few days... Thanks though - gives me hope...
My hardware:
AMD 5050e
MSI K9N2GM (8200)
1GBx2 800Mhz RAM
xnappo
All - regarding the 1080p dropped frames issue - not at home to try - but from the WARNING message - perhaps it would be a good idea to try commenting out all the supported resolutions other than 1920x1080 and see what happens if set to 'Auto'?
xnappo
AllanMar
2009-03-10, 19:06
@Allanmar, @kross
I have an Asus M3n78-VM -- geforce 8200 based mobo and experience the same thing. It should be noted, however, that this is not specific to the VDPAU branch so this discussion should be taken to an appropriate thread as this is a general bug in XBMC. I tested the latest intrepid SVN PPA (r18324) and r18359 vdpau branch and both have the same behavior.
--Nick
I just tried and the non-vdpau branch plays much better than the vdpau brand (when started in 1080p). It dosnt play great, but its sorta watchable whereas when i start vdpau xbmc in 1080p its compleatly out of sync and unwatchable.
Can anyone with a better cpu (that can handle 1080p without vdpau) and has the problem i've been describing (works fine when started in auto and changed to 1080p, but not when started in 1080p) try the normal xbmc branch? I'm still not convinced if this is a vdpau branch problem or not.
AllanMar
2009-03-10, 21:38
motd2k:
You might not be the right person to answer this, mayb we should start a new thread. I wondering if theres some difference between whats done when the resolution is set at startup as opposed to when it is done through the GUI.
I'm also wondering what could be different with your setup vs my very similar hardware. What distro? I heard some distros still use the older XRandR 1.1 (I have XRandR 1.2).
EDIT: Also, killa is not primarily what im using for testing, although I have tried it.
motd2k:
You might not be the right person to answer this, mayb we should start a new thread. I wondering if theres some difference between whats done when the resolution is set at startup as opposed to when it is done through the GUI.
I'm also wondering what could be different with your setup vs my very similar hardware. What distro? I heard some distros still use the older XRandR 1.1 (I have XRandR 1.2).
Allan - did you try motd2k's latest SVN and not doing 'make install'? I also have pretty much identical hardware, and the only difference I can tell is that I used the 'min install' wiki, which includes running 'make install'.
xnappo
AllanMar
2009-03-10, 22:28
Allan - did you try motd2k's latest SVN and not doing 'make install'? I also have pretty much identical hardware, and the only difference I can tell is that I used the 'min install' wiki, which includes running 'make install'.
xnappo
Im compiling the latest one now, i was using one from a day or two ago. Ive never been using make install. Are you saying yours is working fine now? (I thought you said a few posts ago you had the same issues I had)
Im compiling the latest one now, i was using one from a day or two ago. Ive never been using make install. Are you saying yours is working fine now? (I thought you said a few posts ago you had the same issues I had)
No! Sorry didn't mean to give you that idea - I am just living vicariously through you as I am at work and can't play myself :P . I am hoping the scaling change makes a difference. It is good to know 'make install' is not the difference. Still - there must be something else different.
mod2k - you are using Ubuntu 8.10 with no pulse? Are you using SPDIF/HDMI/Analog?
Thanks,
xnappo
AllanMar
2009-03-10, 22:43
I wonder if this could be related to the actual display. Unfortunatly I only have the one 1080p capable tv (Sony Bravia). Perhaps the different display modes are where the differences are.Ive also just noticed this in my Xorg.log
(WW) NVIDIA(0): The EDID for SONY TV (DFP-0) contradicts itself: mode
(WW) NVIDIA(0): "1920x1080" is specified in the EDID; however, the EDID's
(WW) NVIDIA(0): valid VertRefresh range (58.000-62.000 Hz) would exclude
(WW) NVIDIA(0): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
(WW) NVIDIA(0): check for mode "1920x1080".
(WW) NVIDIA(0): The EDID for SONY TV (DFP-0) contradicts itself: mode
(WW) NVIDIA(0): "1920x1080" is specified in the EDID; however, the EDID's
(WW) NVIDIA(0): valid VertRefresh range (58.000-62.000 Hz) would exclude
(WW) NVIDIA(0): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
(WW) NVIDIA(0): check for mode "1920x1080".
(II) NVIDIA(0): Assigned Display Device: DFP-0
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0): will be used as the requested mode.
(==) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
(--) NVIDIA(0): DPI set to (30, 30); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Disabling 32-bit ARGB GLX visuals.
I wonder if this could be related to the actual display. Unfortunatly I only have the one 1080p capable tv (Sony Bravia). Perhaps the different display modes are where the differences are.Ive also just noticed this in my Xorg.log
Interesting. ONE time, I set the resolution to 1980x1024 30hz (something my TV does not support) and then 1080p played smoothly. After I exited XBMC however my TV was very sad (has weird lines across it on all inputs). I had to turn my TV off and back on to get it to work right again. I have not been able to recreate this though.
I have a Philips PFL7432D.
xnappo
AllanMar
2009-03-10, 22:50
Interesting. ONE time, I set the resolution to 1980x1024 30hz (something my TV does not support) and then 1080p played smoothly. After I exited XBMC however my TV was very sad (has weird lines across it on all inputs). I had to turn my TV off and back on to get it to work right again. I have not been able to recreate this though.
I have a Philips PFL7432D.
xnappo
I'd have to guess this meant that XBMC did not actually goto that resolution when changed on the fly like that (otherwise i would think you wouldnt be able to see it). So mayb when were setting to 1080 on the fly, its going to something slightly different also and working..... (im grasping at straws mostly)
EDIT: Tried SVN:18401, mayb a slight improvement hard to say. Still pretty significant a problem. Still fine when started in Auto then changed to 1080p in the GUI though.
I see that it is possible to delete modes from xrandr using the 'delmode' option. Not sure how easy it is to undo though...
xnappo
[EDIT]
This guy's Boxee blog is interesting:
http://www.deviceguru.com/the-boxeebox-cookbook/
He is running something like this:
xrandr –output HDMI-2 –mode 720p1 –pos 0×0
sleep 1
/opt/boxee/run-boxee-desktop
xrandr –output HDMI-2 –mode 640×480 –pos 0×0
[EDIT2] motd2k - if you want us to take this to another thread, just say the word!
i hooked up my box to my 720p Tv (was testing on my 1080p capable monitor prior).. I don't see the same behavior on my TV that I did on my monitor. So, yes, I think it has something to do with the display.
AllanMar
2009-03-11, 12:19
I dont see this problem on 720p, period. Only 1080p, so I'm not sure thats convincing evidence this is display related....
rodercot
2009-03-11, 14:18
I wonder if this could be related to the actual display. Unfortunatly I only have the one 1080p capable tv (Sony Bravia). Perhaps the different display modes are where the differences are.Ive also just noticed this in my Xorg.log
(WW) NVIDIA(0): The EDID for SONY TV (DFP-0) contradicts itself: mode
(WW) NVIDIA(0): "1920x1080" is specified in the EDID; however, the EDID's
(WW) NVIDIA(0): valid VertRefresh range (58.000-62.000 Hz) would exclude
(WW) NVIDIA(0): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
(WW) NVIDIA(0): check for mode "1920x1080".
(WW) NVIDIA(0): The EDID for SONY TV (DFP-0) contradicts itself: mode
(WW) NVIDIA(0): "1920x1080" is specified in the EDID; however, the EDID's
(WW) NVIDIA(0): valid VertRefresh range (58.000-62.000 Hz) would exclude
(WW) NVIDIA(0): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
(WW) NVIDIA(0): check for mode "1920x1080".
(II) NVIDIA(0): Assigned Display Device: DFP-0
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0): will be used as the requested mode.
(==) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
(--) NVIDIA(0): DPI set to (30, 30); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Disabling 32-bit ARGB GLX visuals.
That is not uncommon on new TV's. If you follow this link and do what it says to do you will come up with all the modes and refesh rates that your tv model will support. I find I have had to do this with all my Tv's as the native resolution option is nice but not always the answer and it defaults to nvidia auto-select for modes.
http://ubuntuforums.org/showthread.php?t=1003099&page=2
Regards,
Dave
i hooked up my box to my 720p Tv (was testing on my 1080p capable monitor prior).. I don't see the same behavior on my TV that I did on my monitor. So, yes, I think it has something to do with the display.
I don't think that is conclusive - if I set XBMC to 720p on my 1080p TV, Killa plays smoothly no matter what.
xnappo
for all of us talking about the weirdness that we experience with auto setting on resolution on 8X00 motherboards, we're starting to confuse people coming to this thread looking for info about VDPAU. I'll try and right a summary post to start a new thread when I have some time later if someone else doesn't do it first. Our threadjack has got to stop because it's having a negative impact on peoples perception of how well VDPAU can play 1080P material.
That is not uncommon on new TV's. If you follow this link and do what it says to do you will come up with all the modes and refesh rates that your tv model will support. I find I have had to do this with all my Tv's as the native resolution option is nice but not always the answer and it defaults to nvidia auto-select for modes.
http://ubuntuforums.org/showthread.php?t=1003099&page=2
Regards,
Dave
I am not sure, but I think the solution in this thread may accomplish the same thing with slightly less pain:
http://xbmc.org/forum/showthread.php?p=242273
xnappo
Almoust everything I've tested so far runs good (including killa sample) except some framedrops in when the video starts.
I'm having the frequence to 24Hz otherwise i get "jitter". I also sometimes get audio out of sync. But this happens to xvids aswell.
I havn't updated in a few days now, so don't know if these issues still exists with the latest svn.
Great! Thanks.
Only problem is I can't find that or any other compatible PCI card in norway. Guess i'll just have to import one.
for all of us talking about the weirdness that we experience with auto setting on resolution on 8X00 motherboards, we're starting to confuse people coming to this thread looking for info about VDPAU. I'll try and right a summary post to start a new thread when I have some time later if someone else doesn't do it first. Our threadjack has got to stop because it's having a negative impact on peoples perception of how well VDPAU can play 1080P material.
I'd appreciate that. I'm following the VDPAU-thread since a while now - and it's amazing what progress has been made. Thanks again to all the people spending their time for xbmc! I'm really considering now to upgrade from my xbox-based htpc set. Some summarized infos would therefore be really helpful. :)
I am not sure, but I think the solution in this thread may accomplish the same thing with slightly less pain:
http://xbmc.org/forum/showthread.php?p=242273
xnappo
I played with this briefly, but it didn't help so far.
Allan - you are definitely right about the mode being set wrong.
Check this out:
- In the non-working case, go to the shutdown menu then over to info and take a look - you will see that the resolution is set to 1920x1080 60hz, BUT the real frequency is fluctuating around 38hz.
- In the working case, take a look and you will see the frequency is locked correctly at 60hz.
Please confirm you see the same thing(all).
xnappo
AllanMar
2009-03-12, 18:27
Interesting... Yea, I see the same thing. But im not sure what this means really.... This could simply be because of ____ problem it cant keep up with 60hz (it cant maintain the framerate either, hence all the dropped frames). But I'm not really sure. I cant try right now, but what if you did something like knock the CPU down to 1ghz (we know this causes problems) and run it where it would normally work and see if it stays locked at 60hz or not.
Interesting... Yea, I see the same thing. But im not sure what this means really.... This could simply be because of ____ problem it cant keep up with 60hz (it cant maintain the framerate either, hence all the dropped frames). But I'm not really sure. I cant try right now, but what if you did something like knock the CPU down to 1ghz (we know this causes problems) and run it where it would normally work and see if it stays locked at 60hz or not.
Interesting idea. I am also going to try using a modeline instead of using EDID when I get a chance.
xnappo
AllanMar
2009-03-12, 18:59
Yea, ive been meaning to do that too. The one issue with moving this to a separate thread, is i was hoping some of the people with similar hardware that have it working (such as motd2k) could describe their setups. Could this be a distro issue?
I don't think it is a distro issue since i'm experiencing the same behaviour on Arch Linux x86_64, though i did not test this as fully as you guys. I'm running on ASUS M3N78-EM w/GeForce 8300 and a AMD X2 4850e CPU running at least @1800 Mhz due to bandwidth limitation if i go lower. Memory is 2 x 2GB DDR2-800 running in DualChannel mode. However i did see a direct link of core speed and reached fps in xbmc but this might be another issue.
I am actually glad so many people have the problem. I am also glad there is a way to work around it.
I think with a little experimentation and cooperation we will get this licked - but it would be nice to have someone with more experience reading the thread...
xnappo
AllanMar
2009-03-12, 19:19
I don't think it is a distro issue since i'm experiencing the same behaviour on Arch Linux x86_64, though i did not test this as fully as you guys. I'm running on ASUS M3N78-EM w/GeForce 8300 and a AMD X2 4850e CPU running at least @1800 Mhz due to bandwidth limitation if i go lower. Memory is 2 x 2GB DDR2-800 running in DualChannel mode. However i did see a direct link of core speed and reached fps in xbmc but this might be another issue.
I have the EXACT same hardware on ubuntu 8.10, Im running at 2.5ghz though. It is somehow related to CPU, because when i overclock to 2.9ghz its plays moderatly well (not perfect like it does when not opened full screen, but ok)
@xnappo: And I agree, I was glad so many people had it. The part that is discouraging is not everybody with similar setups is having this problem.
@xnappo: And I agree, I was glad so many people had it. The part that is discouraging is not everybody with similar setups is having this problem.
I think most 8X00 users are though - it would be really nice to know if motd2k or others NOT having the issue are running with EDID on a TV...
xnappo
To clear it up: i do not have modelines in my xorg.conf. nvidia driver is also complaining about incompatible edid mode information coming from the tv (also Sony Bravia, 40E4000 if that matters). Seems like it gets intialized @24Hz although the tv set does not recognize it as 1080/24p as it does eg. on bluray.
AllanMar
2009-03-12, 22:03
What would be great is if I could figure out how to make my TV (Sony Bravia 52V4100) show me whats the input actually is, IE refresh rate. Anyone know of anything? Figured out how to get into the service menu, but not how to actually use it.
Well i did not exactly find out what refresh rate my TV is using, but i do see two different OSD hints. One is 1080p for anything 1920x1080 at any refresh rate EXCEPT 'real' 24Hz for which the TV responds with "1080/24p". I can force this mode by setting it in nvidia-settings or using '1920x1080@24Hz' in XBMC.
Well, I played with the modeline thing. It doesn't really work if you run XBMC in standalone mode - I think in that case it uses EDID/XRANDR regardless of xorg.conf? So then I tried running something like:
X
sleep 2
xbmc.bin
Still didn't work though.
In the process of all of this, I found that if I set XBMC to 1080i, it DOES work and video plays smoothly. The info screen now reads "1920x1080 1080i 16:9 100Hz" That 100Hz is the real-time number. My TV reports the mode is 1080p though... Huh??
xnappo
mythmaster
2009-03-13, 06:31
Hey, guys --
I'm starting to think that this might be an issue with some code somewhere and AMD.
I'm not experiencing the problem to the extent that you are (9300GS + phenom x4)...it only happens to me on hdpvr-encoded files (see the other thread, I don't have the sample link handy), and motd2k is unable to reproduce the problem; because, I believe, that he's running an Intel CPU.
Could this be possible?
Add me to the list now...experiencing same issue with similar hardware.
AMD 4850e + 8200 motherboard w/3gb RAM in dual channel mode. 180.35 drivers and vdpau-xbmc svn from march 13.
Starting in my TV's native resolution (1920x1080 60hz) gives me slow playback...starting in auto and then switching to it gives smooth playback.
Somehow your proposed workaround doesn't seem to work here. If i start in auto mode, my tv switches to 720p, then, if i set xbmc to 1920x1080 @60Hz does switch to 1080p, but fps in xbmc info screen hovers around 25-30?!
I also found my system to report an incorrect refresh rate. If I start with the 1920x1080 60hz option set in xbmc, but go to info screen, the refresh rate says it is only at 30hz (which my TV does not support, so it must be inaccurate).
Well that is the original problem in this thread, but somehow, if you start in auto mode and then switch to 1920x1080@..Hz and go to 'Test resolution' all is working fine. At least that is what some here are experiencing. Unfortunately it does also not work for me :-(
I know, that is why I said I "also found". Setting the resolution to the correct one after starting in auto mode should allow the videos to play properly, not set the refresh rate of the OSD to 60fps, if that is what you are thinking.
Oh i see, well that may be working, i did not test this as i simply had a look at system info which did not seem to get better. I will try this tonight - at least we have a trail :-)
shassino
2009-03-13, 13:06
I have the same issue. tested now on vdpau and linuxport both at svn 18470. Both have the same issue.
debian 5.0 kernel 2.6.28
athlon 64 X2 5200+
asus m3n78-em
igp nv8300 512MB shared
AllanMar
2009-03-13, 14:16
I've noticed (through my TV's Info) that changing the resolution of XBMC does not actually change the output resolution to the TV (not sure if it should) ONLY changing the X resolution does this. Anyone know if thats how its supposed to work?
Well, switching to 720p at least switches the TV to 720p - i can see this in the tv set's info screen. Switching to anything 1080p does switch to 1080p on the tv set. i did not try anything else.
So did anyone else try setting it to 16:9 1080i? Mine works all the time with that setting, even though it runs at 100hz for some reason. It also is not 1080i - my TV says it is 1080p...
Also - does anyone know for sure if XBMC even looks at xorg.conf when it is run with --standalone? Or does it always use XRandR/EDID regardless?
xnappo
So did anyone else try setting it to 16:9 1080i?
I tried this once - but not on my recent svn build (18448). Though i can't remember that it was anything better. My TV also displays 1080p for that mode. Will test tonight and report back.
For any brave souls out there - my xorg.conf follows.
I have several machines, none exhibit this problem...
1) Intel QX6800, 680i motherboard, 2x1GB 800Mhz DDR2, 512MB PCI-e NVIDIA 9500GT connected via HDMI to a Crystalio2 scaler, and thereafter via component to a Panasonic panel. Works fine, but the panel is only 720p - crystalio is actually downscaling!
2) AMD 5050e, ASUS P2-M3A3200, 2x2GB 800Mhz DDR2, with 512 MB PCI-e NVIDIA 9500GT... my VDPAU development machine, connected via DVI to a Sony SDM-P234 @ 1920x1200.
3) AMD 4800+, ABIT cheapass mobo, 2x1GB 800Mhz DDR2, NVIDIA 8200 (with 512MB allocated) onboard, connected to a generic 42" 1080p LCD.
All work fine, smooth, start in full-screen mode etc.
Anyway - he is what i use.
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder62) Thu Feb 5 00:08:50 PST 2009
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
ModeLine "1920x1200@48" 151.48 1920 2032 2240 2560 1200 1201 1204 1234 -hsync +vsync
ModeLine "1920x1080@48" 138.500 1920 1968 2000 2080 1080 1083 1088 1111 +hsync +vsync
ModeLine "1920x1080@50" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
ModeLine "1920x1080@60" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "ExactModeTimingsDVI" "True"
Option "AddARGBGLXVisuals" "True"
Option "UseDisplayDevice" "DFP-0"
Option "DynamicTwinView" "false"
Option "FlatPanelProperties" "Scaling = Native"
Option "ModeValidation" "DFP-0: NoMaxSizeCheck, NoHorizSyncCheck, NoVertRefreshCheck, AllowNon60HzDFPModes, NoMaxPClkCheck, NoVesaModes, NoXServerModes, NoPredefinedModes"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Disable"
EndSection
Hey, thanks a lot. This clears things up a bit, since you are using custom modelines - and apparently the 'brave souls' in here use EDID/xrandr information. How did you generate those modelines? Will try this ASAP since this is a promising difference.
The options are important too. The modelines, well tbh i cheated and just downloaded some - they likely do not produce pixel-perfect images but i dont care.
My scaler can give me the information needed to write the modelines, by adjusting suitable test-images until everything is perfect, a process known as calibration, for which people pay alot of money.
The xorg.conf options look mostely the same as mine - except for the modeline stuff. I'll have a look after this. Meanwhile some lines from Xorg.0.log:
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoFlip" "True"
(**) NVIDIA(0): Option "NoLogo" "True"
(**) NVIDIA(0): Option "NvAGP" "1"
(**) NVIDIA(0): Option "RenderAccel" "True"
(**) NVIDIA(0): Option "TwinView" "False"
(**) NVIDIA(0): Option "ExactModeTimingsDVI" "True"
(**) NVIDIA(0): Option "Coolbits" "1"
(**) NVIDIA(0): Option "TripleBuffer" "True"
(**) NVIDIA(0): Option "UseEvents" "True"
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
(**) NVIDIA(0): Option "DamageEvents" "True"
(**) NVIDIA(0): Option "FlatPanelProperties" "Scaling = Native"
(**) NVIDIA(0): Option "DynamicTwinView" "False"
(**) NVIDIA(0): Option "PixmapCacheSize" "1000000"
(**) NVIDIA(0): Option "AllowSHMPixmaps" "0"
(**) NVIDIA(0): OpenGL flipping disabled
(**) NVIDIA(0): Enabling RENDER acceleration
(**) NVIDIA(0): Use of NVIDIA internal AGP requested
(II) NVIDIA(0): NVIDIA GPU GeForce 8300 (C77) at PCI:2:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 524288 kBytes
(--) NVIDIA(0): VideoBIOS: 62.77.2f.00.00
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 8300 at PCI:2:0:0:
(--) NVIDIA(0): SONY TV XV (DFP-0)
(--) NVIDIA(0): SONY TV XV (DFP-0): 165.0 MHz maximum pixel clock
(--) NVIDIA(0): SONY TV XV (DFP-0): Internal Single Link TMDS
(WW) NVIDIA(0): The EDID for SONY TV XV (DFP-0) contradicts itself: mode
(WW) NVIDIA(0): "1920x1080" is specified in the EDID; however, the EDID's
(WW) NVIDIA(0): valid VertRefresh range (48.000-62.000 Hz) would exclude
(WW) NVIDIA(0): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
(WW) NVIDIA(0): check for mode "1920x1080".
(WW) NVIDIA(0): The EDID for SONY TV XV (DFP-0) contradicts itself: mode
(WW) NVIDIA(0): "1920x1080" is specified in the EDID; however, the EDID's
(WW) NVIDIA(0): valid VertRefresh range (48.000-62.000 Hz) would exclude
(WW) NVIDIA(0): this mode's VertRefresh (24.0 Hz); ignoring VertRefresh
(WW) NVIDIA(0): check for mode "1920x1080".
(II) NVIDIA(0): Assigned Display Device: DFP-0
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0): will be used as the requested mode.
(==) NVIDIA(0):
As you can see, the driver even complains about incompatible edid information on the tv set. i think this perfectly fits the issue everybody's seeing.
Hehe - seems like it is as easy as this:
haggy@aereogramme /var/tmp $ gtf 1920 1080 50
# 1920x1080 @ 50.00 Hz (GTF) hsync: 55.60 kHz; pclk: 141.45 MHz
Modeline "1920x1080_50.00" 141.45 1920 2032 2232 2544 1080 1081 1084 1112 -HSync +Vsync
or to try this at home:
gtf <horizontal_res> <vertical_res> <refresh_rate>
For posterity, here's mine...
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "ExactModeTimingsDVI" "True"
(**) NVIDIA(0): Option "UseDisplayDevice" "DFP-0"
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
(**) NVIDIA(0): Option "ModeValidation" "DFP-0: NoMaxSizeCheck, NoHorizSyncCheck, NoVertRefreshCheck, AllowNon60HzDFPModes, NoMaxPClkCheck, NoVesaModes, NoXServerModes, NoPredefinedModes"
(**) NVIDIA(0): Option "FlatPanelProperties" "Scaling = Native"
(**) NVIDIA(0): Option "DynamicTwinView" "false"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): NVIDIA GPU GeForce 9400 GT (G96) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 524288 kBytes
(--) NVIDIA(0): VideoBIOS: 62.94.4b.00.77
(II) NVIDIA(0): Detected PCI Express Link width: 16X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 9400 GT at PCI:1:0:0:
(--) NVIDIA(0): Sony SDM-P234 (DFP-0)
(--) NVIDIA(0): Sony SDM-P234 (DFP-0): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): Sony SDM-P234 (DFP-0): Internal Dual Link TMDS
(II) NVIDIA(0): Mode Validation Overrides for Sony SDM-P234 (DFP-0):
(II) NVIDIA(0): AllowNon60HzDFPModes
(II) NVIDIA(0): NoMaxPClkCheck
(II) NVIDIA(0): NoMaxSizeCheck
(II) NVIDIA(0): NoHorizSyncCheck
(II) NVIDIA(0): NoVertRefreshCheck
(II) NVIDIA(0): NoVesaModes
(II) NVIDIA(0): NoXServerModes
(II) NVIDIA(0): NoPredefinedModes
(II) NVIDIA(0): Assigned Display Device: DFP-0
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0): will be used as the requested mode.
(==) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1200
(--) NVIDIA(0): DPI set to (97, 98); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(WW) NVIDIA(0): 32-bit ARGB GLX visuals require the Composite extension.
(WW) NVIDIA(0): Disabling 32-bit ARGB GLX visuals.
Hehe - seems like it is as easy as this:
haggy@aereogramme /var/tmp $ gtf 1920 1080 50
# 1920x1080 @ 50.00 Hz (GTF) hsync: 55.60 kHz; pclk: 141.45 MHz
Modeline "1920x1080_50.00" 141.45 1920 2032 2232 2544 1080 1081 1084 1112 -HSync +Vsync
or to try this at home:
gtf <horizontal_res> <vertical_res> <refresh_rate>
Learn something everyday! Thanks :)
In nearly ten years of linux i NEVER stumbled upon this handy tool...
Would you mind posting some Xorg.log lines from your nvidia 8200 machine as this also seems to make a difference. Most of the issues seem to come from 8200/8300 GPUs.
Learn something everyday! Thanks :)
Thanks for the tips - how do you launch XBMC? I am currently using my .xsession to do it AND am running --standalone. I think that this is not appropriate for using modelines right? How do you autostart XBMC at boot time?
Thanks,
xnappo
xnappo,
i'm unsure whether it will work in the way you describe or not. I simply add an entry to System/Prefs/Sessions
Up to now i start via inittab and xinitrc:
/etc/inittab:
x:5:once:/bin/su haggy -l -c "/bin/bash --login -c startx >/dev/null 2>&1"
and .xinitrc:
exec nvidia-settings --load-config-only &
exec ck-launch-session xbmc -fs --standalone
but i think i have to change this using modelines - at least --standalone has to go i think.
Unfortunately i dont think gtf is reliable - its given me the exact same modeline for both my Sony monitor and 42" TV.
Better than nothing though, but I suspect it wont give proper 1:1 pixel mapping and whatnot.
This is from my 8200...
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "ExactModeTimingsDVI" "True"
(**) NVIDIA(0): Option "UseDisplayDevice" "DFP-0"
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
(**) NVIDIA(0): Option "ModeValidation" "DFP-0: NoMaxSizeCheck, NoHorizSyncCheck, NoVertRefreshCheck, AllowNon60HzDFPModes, NoMaxPClkCheck, NoVesaModes, NoXServerModes, NoPredefinedModes"
(**) NVIDIA(0): Option "FlatPanelProperties" "Scaling = Native"
(**) NVIDIA(0): Option "DynamicTwinView" "false"
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): NVIDIA GPU GeForce 8200 (C77) at PCI:2:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 524288 kBytes
(--) NVIDIA(0): VideoBIOS: 62.77.24.00.08
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 8200 at PCI:2:0:0:
(--) NVIDIA(0): OEM 37'' TFT-TV (DFP-0)
(--) NVIDIA(0): OEM 37'' TFT-TV (DFP-0): 165.0 MHz maximum pixel clock
(--) NVIDIA(0): OEM 37'' TFT-TV (DFP-0): Internal Single Link TMDS
(II) NVIDIA(0): Mode Validation Overrides for OEM 37'' TFT-TV (DFP-0):
(II) NVIDIA(0): AllowNon60HzDFPModes
(II) NVIDIA(0): NoMaxPClkCheck
(II) NVIDIA(0): NoMaxSizeCheck
(II) NVIDIA(0): NoHorizSyncCheck
(II) NVIDIA(0): NoVertRefreshCheck
(II) NVIDIA(0): NoVesaModes
(II) NVIDIA(0): NoXServerModes
(II) NVIDIA(0): NoPredefinedModes
(II) NVIDIA(0): Assigned Display Device: DFP-0
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0): will be used as the requested mode.
(==) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
(--) NVIDIA(0): DPI set to (304, 304); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(WW) NVIDIA(0): 32-bit ARGB GLX visuals require the Composite extension.
(WW) NVIDIA(0): Disabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
xnappo,
i'm unsure whether it will work in the way you describe or not. I simply add an entry to System/Prefs/Sessions
So your xbmc command is simply 'xbmc.bin'. I am using '/usr/share/xbmc/xbmc.bin -q --standalone' . I don't have Gnome or anything installed - just using the minimum install - so I think in that case to match your setup I need to change my .xsession to start X, and then launch xbmc without --standalone..?
Thanks,
xnappo
what does '-q' mean?
I have no idea, I just followed this guide:
http://xbmc.org/wiki/?title=HOW-TO:_Install_XBMC_for_Linux_on_Ubuntu_8.10_(Intrepi d)_step-by-step
I also noticed this line in motd2k's .xorg:
Option "ModeValidation" "DFP-0: NoMaxSizeCheck, NoHorizSyncCheck, NoVertRefreshCheck, AllowNon60HzDFPModes, NoMaxPClkCheck, NoVesaModes, NoXServerModes, NoPredefinedModes"
I think that might be important.
xnappo
Unfortunately i dont think gtf is reliable - its given me the exact same modeline for both my Sony monitor and 42" TV.
I don't think gtf takes the actual screen into count as it is simply a nicer interface to a calculator :-)
every screen should handle those computed modelines well or am i wrong?
I also noticed this line in motd2k's .xorg:
Option "ModeValidation" "DFP-0: NoMaxSizeCheck, NoHorizSyncCheck, NoVertRefreshCheck, AllowNon60HzDFPModes, NoMaxPClkCheck, NoVesaModes, NoXServerModes, NoPredefinedModes"
I think that might be important.
xnappo
Those lines force the driver to NOT use any edid/xrandr/crystalball modes and to use specified modelines.
carseneau
2009-03-13, 19:29
If anyone's interested here is my xorg that I've gotten working 1080p24 playback perfectly smooth.
The only options I change in xbmc are the screen resolution to "default: 1920x1080 @ 60Hz" because it starts in 24hz and the menus are choppy. Also I turn on auto refresh rate change.
AMD 5000
Asus M3N78-VM (8200 IGP)
2gb ram dual channel
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder63) Tue Nov 4 14:07:17 PS T 2008
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
# VendorName "Unknown"
# ModelName "Unknown"
Option "DPMS"
Modeline "1920x1080@24" 74.160 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
Modeline "1920x1080@50" 148.500 1920 2448 2492 2640 1080 1084 1089 112 5 +hsync +vsync
Modeline "1920x1080@60" 148.350 1920 2008 2052 2200 1080 1084 1089 112 5 +hsync +vsync
HorizSync 15.0 - 68.0
VertRefresh 23.0 - 61.0
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "UseEdidFreqs" "false"
Option "NoLogo"
Option "TwinView" "0"
Option "UseEvents" "true"
Option "NvAGP" "1"
Option "Coolbits" "1"
Option "NoLogo" "True"
Option "PixmapCacheSize" "1000000"
Option "AllowSHMPixmaps" "0"
Option "TripleBuffer" "True"
Option "RenderAccel" "True"
Option "DynamicTwinView" "false"
Option "AddARGBGLXVisuals" "True"
Option "ExactModeTimingsDVI" "True"
SubSection "Display"
Depth 24
Modes "1920x1080@24" "1920x1080@60" "1920x1080@50"
EndSubSection
EndSection
Aaaaaaah! Another one with modelines :-)
shassino
2009-03-13, 20:38
Uhm my tv has 24,50,60Hz i'll try your xorg.conf and i'll report u what i've got.
I don't think gtf takes the actual screen into count as it is simply a nicer interface to a calculator :-)
every screen should handle those computed modelines well or am i wrong?
Probably - but here is the real way to get the modelines:
http://ubuntuforums.org/showthread.php?t=1003099&page=2
xnappo
I created some test images to use to check for pixel clock issues. The image (the one relevant for your resolution) should appear smooth, with no horizontal or vertical banding visible within the sections.
AllanMar
2009-03-13, 22:38
So I tried motd2k's xorg.conf and the problem is still there. However it did seem slightly better, getting more like 21fps (24fps content) now where i was only getting around 18fps before. When i get a chance im going to mess around with my own mode lines and some different refresh rates and see if that makes any difference.
EDIT: My tv now shows 720p/etc when xbmc changes resolution to 720p and such, and it did not before. Altho 24hz still does not show on the tv.
So did anyone else try setting it to 16:9 1080i?
I did, and it works for me. I have xbmc set to start 1080i 16:9 and it plays the apple demo perfectly and my other test 1080p movie which was skipping badly. The content is playing in 1080p as well. I'm going to generate some custom modelines using the link posted a few posts back and experiment some more...as it seems mot2dk has AMD+8200 and isn't having trouble...so it must be our configuration that is causing the issue.
Wooho guys this is another weird moment in my xbmc experience. I just came home, switched on TV and HTPC and xbmc showed me this in system info:
http://dump.haggy.org/htpc/xbmc_running_smooth_at_1080p.png
xbmc is set to 1080i 16:9, but i SWEAR i tested this mode earlier without success. One thing though: i removed both -fs and --standalone from my xbmc startup call in .xinitrc.
Could this be a hint at least for 1080i ?
OK - after some more tests i can fully confirm xnappo's and philter's experience. Starting up in 1080i is fine, system info is as shown above - hovering around 55fps. I can test every other 1080p mode (24, 50, 60) and it will also do fine and lock fps on selected refresh rate, BUT, after leaving xbmc and restarting fps drop down to 20-24 Hz on every selected mode. If i afterwards select 1080i again and restart xbmc, all modes can again be set to desired refresh rate, so i think we can narrow it down to:
1) Starting in anything other than 1080i will lock refresh at about 20-24 fps
2) Starting in 1080i and testing/selecting any other 1080p mode will do fine.
It seems the removal of those two flags at startup did not have any direct affect on this, but my video calibration was messed up afterwards.
shassino
2009-03-14, 03:16
same result for me with both xorg.conf. 1080i in my htpc is choppy as 1080p.
I must use the windowed mode and then change to 1080p to get all running smooth.
tomorrow i'll try 1080i with old xorg.conf.
AllanMar
2009-03-14, 03:19
OK - after some more tests i can fully confirm xnappo's and philter's experience. Starting up in 1080i is fine, system info is as shown above - hovering around 55fps. I can test every other 1080p mode (24, 50, 60) and it will also do fine and lock fps on selected refresh rate, BUT, after leaving xbmc and restarting fps drop down to 20-24 Hz on every selected mode. If i afterwards select 1080i again and restart xbmc, all modes can again be set to desired refresh rate, so i think we can narrow it down to:
1) Starting in anything other than 1080i will lock refresh at about 20-24 fps
2) Starting in 1080i and testing/selecting any other 1080p mode will do fine.
It seems the removal of those two flags at startup did not have any direct affect on this, but my video calibration was messed up afterwards.
starting in 1080i for me has SLIGHT issues when playing 1080p content. Little bits of stutter, during fast motion and such (not present when starting in auto then going to 1080p).
Actually, for me only starting in 1080p will lock refresh to 18-20hz
Just for some info, I also tried compiling with --disable-xrandr, seemed to provide some improvement, not as much image stuttering and such, but audio is way out of sync
same result for me with both xorg.conf. 1080i in my htpc is choppy as 1080p.
I must use the windowed mode and then change to 1080p to get all running smooth.
tomorrow i'll try 1080i with old xorg.conf.
Shassino,
I know you started out running NON-VDPAU. Are these result from VDPAU or standard?
Thanks,
xnappo
shassino
2009-03-14, 03:29
vdpau svn 18470.
I'll try tomorrow on standard svn 18470. But i think is not necessary all my previous result r identical for linuxport and vdpau.
I start with exec xbmc --standalone in my xsession, it starts fullscreen in the 1080i mode and plays 1080p content perfectly. If I start with 1080p @60hz, the choppyness and slow fps returns. If I start with 1080i (or any other resolution) and switch to 1080p, it plays perfectly.
vdpau svn 18470.
I'll try tomorrow on standard svn 18470. But i think is not necessary all my previous result r identical for linuxport and vdpau.
No need to try standard, just making sure we were all using VDPAU.
Thanks,
xnappo
Does anyone have the problem at 1080i?
shassino
2009-03-14, 12:32
In my htpc 1080p and 1080i if started in fs give me the same problem.
@motd2k: Do u want my logs? maybe u can see something we can't :P
You'll be pleased to know I now suffer from this too... after having done nothing except reboot it seems!
I'm on it.
There's aliens, lottery, the weather - and there's xbmc :-)
You'll be pleased to know I now suffer from this too... after having done nothing except reboot it seems!
I'm on it.
Yea! Oh.. I mean... Sorry to hear that :laugh:
xnappo
shassino
2009-03-14, 20:16
I'm trying rev 185 of nvidia driver. Let see if this gonna change :nerd:
shassino
2009-03-14, 20:40
180.35 18 fps with vdpau and without
LOL 185.15 12 fps with vdpau and 8fps without.
This let me thinking that is a driver issue, i'm trying now with 180.29 driver
AllanMar
2009-03-14, 20:43
Altho I havnt tryed 185 yet, mplayer with vdpau plays perfectly. So I assumed this wasnt a driver issue.
shassino
2009-03-14, 21:00
180.29 8 fps with vdpau
180.35 16 fps with vdpau
180.37 10 fps with vdpau
185.15 12 fps with vdpau and 8fps without.
All tested at min 38 of Iron man 1080p
Shassino, these values are while playing as shown in system info?
If true, you are suffering something similar to my issues - that is not being able to play videos smoothly with vdpau. My fps look similar, though i can play the files without vdpau enabled.
AllanMar
2009-03-14, 21:27
i normally get around 18fps with this. Do you have your CPU speed lowered? Even though there shouldnt be much cpu relation when using vdpau, when experincing the issue were talking about here, the faster i set my cpu the better it performs.
Lowered yes, but i configured cpupowerd to not go below 1800 MHz due to bandwidth issues at lower speed. I even tested using fixed 2500 MHz (max of my cpu) and it didn't help - still video is too slow and full of judder. mplayer does the same file fine...
AllanMar
2009-03-14, 21:51
Yea, I know it still dosnt work. I was just saying when Im having these problems its at like 18fps, wondering why the other guy was only getting like 12fps. Likely due to the lower cpu speed?
Do you have the same CPU/setup? As for me, fps move from 10 to 20 depending on the actual screen content, and are not fixed at these values. However, performance gain and degration throughout several driver releases are quite interesting
AllanMar
2009-03-14, 23:05
Im fairly sure I have the same (or close). 4850e & M3N78-EM.
Yea, it does vary a bit, but i rarely see it go that low. Overclocking to 2.9ghz I can pretty much achieve 24fps, but there are still some issues every now and then.
Just curious, as you have exactly the same hardware as me: Can you play the Artbeats and/or Killa-Sample using Advanced shaders (GLSL) without issues?
AllanMar
2009-03-14, 23:55
No (only tried killa), havn't tried overclocked tho.
Which revision are you running? nvidia driver? xorg.conf? is xbmc the only client running on X or do you have gnome/compiz/whatever running in the background?
AllanMar
2009-03-15, 02:02
180.37, using motd2k's xorg.conf still i think. I've has this problem since late feb though, as far as I know I was the first one to report it. Its happened on all drivers/SVN's since then. Im running a basic Intrepid 8.10 install, so yes gnome/etc
shassino
2009-03-15, 02:24
Checked now CPU was at minimum speed , if I force freq to 2.5GHz i get 18-20fps
AllanMar
2009-03-15, 05:25
Checked now CPU was at minimum speed , if I force freq to 2.5GHz i get 18-20fps
Ahh, thats what I thought....Unfortunately it hardly helps us though...lol
At least theres a workaround for now.. Hopefully motd2k will be able to find something now that he also has this issue.
shassino
2009-03-16, 20:01
Someone have opened a trac ticket? Only to know if is possible to follow this strange issue :)
Please try xbmc-vpdau SVN revision 18669.
You should find an additional option under Settings->Appearance->Screen called 'Safe fullscreen mode'. Select this mode, and restart XBMC.
Scratch that, changes have been reverted for unrelated reason.
Scratch that, changes have been reverted for unrelated reason.
Ok - so don't bother with 18670? Also we need the latest NVidia driver right? Probably good I didn't install - now I can make sure the new video driver doesn't break first.
xnappo
Ok - so don't bother with 18670? Also we need the latest NVidia driver right? Probably good I didn't install - now I can make sure the new video driver doesn't break first.
xnappo
So after reading in the main thread that 18670 still had the fix, I gave it a shot.
- Installing the 185.13 video driver worked fine.
- New menu option for safe fullscreen was there, selected it
- Restarted in 'Full Screen' mode.
- All videos play fine (they played fine for me before in 1080i too)
- All test patterns look perfect
- The INFO screen still shows 1080i as the selected resolution, however my TV says 1080p. This is the same as before when I manually selected 1080i. Double checked the settings screen has 1920x1080 (full screen) selected. Also tried default: 1920x1080 with the same result.
Is this as expected? It is working perfectly, just the weird 'info' saying it is running 1080i. Thanks for your hard work!
xnappo
AllanMar
2009-03-20, 00:01
I also tried 18670, and it appears to be a vast improvement. Only slight issues when playing 1080p. Little jutter once and awhile. I suspect this is because my im now seeing 25% cpu0 and 90-100% cpu1. On screen display shows vdpau accelerated, however it no longer says DVDPlayer(VDPAU)...Im guessing this is just a change though.
Any thoughts?
EDIT: Scratch that, when i upgraded to 185.13, the CPU usage dropped to vdpau levels (5% or so) and playback is perfect! Ive noticed when i start xbmc with -fs it goes full screen then goes windowed. When i start without it, it starts fullscreen and stays there. Hopefully this finds its way back into the svn.
EDIT: Scratch that, when i upgraded to 185.13, the CPU usage dropped to vdpau levels (5% or so) and playback is perfect! Ive noticed when i start xbmc with -fs it goes full screen then goes windowed. When i start without it, it starts fullscreen and stays there. Hopefully this finds its way back into the svn.
Ah - makes sense. Can you check the 'i' info thing in the shutdown menu to see what resolution it is reporting?
I did use the 'program launcher' to run 'nvidia-settings' and it does not indicate interlaced from what I can tell..
xnappo
AllanMar
2009-03-20, 02:23
Yes, it does show 1080i, but as far as i can tell 1080i in xbmc is 1920x1080@30hz, where even though it says 1080i, its at 60Hz which is the 1080p setting.
Yes, it does show 1080i, but as far as i can tell 1080i in xbmc is 1920x1080@30hz, where even though it says 1080i, its at 60Hz which is the 1080p setting.
Yeah, I really don't think it is 1080i. I don't understand why it reports that.
xnappo
Yeah, I really don't think it is 1080i. I don't understand why it reports that.
xnappo
What does xrandr report? Willing to try out 18670 just for motd2k's patch acceptance sake.
What does xrandr report? Willing to try out 18670 just for motd2k's patch acceptance sake.
Running an xterm using launcher, then running 'xrandr -q' I get a '*' next to '1920x1080 60hz'. I assume this means that is the current mode. 1080i is also on the list at 30hz with no '*'.
xnappo
[EDIT] running with --verbose, I can confirm the mode is 1920x1080 60Hz non-interlaced.
shassino
2009-03-24, 21:57
Sry for upping thread, i only wanted to know if the safe fullscreen patch is present in Linuxport (VDPAU and Linuxport r merged now right?) rev 18900.
@motd2k: If not, plz can u attach a patch file? And ty for ur work on vdpau.
Nope, not merged into linuxport. If you checkout -r18670 for example you can find the patch though it might be easier if motd2k supplies a diff of the necessary files.
I've been following this thread and the vdpau thread, but must have missed the "patch" discussion. Has the issue in the first post of this thread been fixed with a patch? Which thread can I find the patch in?
shassino
2009-03-27, 13:46
U can find the patch in vdpau since rev 18670, i'm trying rigth now to build linuxport svn (don't rember revs :P 18900~) with the patch.
I'll post the diff file if i got success :P
U can find the patch in vdpau since rev 18670, i'm trying rigth now to build linuxport svn (don't rember revs :P 18900~) with the patch.
I'll post the diff file if i got success :P
Thanks - would really appreciate that. I really want the MKV aspect ratio fix.
xnappo
shassino
2009-04-02, 13:53
I got success, i have now linuxport svn 19150 with safe fullscreen patch, i'm making now the diff file. I'll post soon.
shassino
2009-04-02, 15:19
This is the diff file :)
diff -r -u xbmc/XBMC/guilib/GUIWindowManager.cpp xbmc_sf/XBMC/guilib/GUIWindowManager.cpp
--- xbmc/XBMC/guilib/GUIWindowManager.cpp 2009-04-02 12:41:37.000000000 +0200
+++ xbmc_sf/XBMC/guilib/GUIWindowManager.cpp 2009-04-02 11:39:59.000000000 +0200
@@ -220,6 +220,9 @@
void CGUIWindowManager::PreviousWindow()
{
+ BOOL safeFull = false;
+ if (g_guiSettings.GetBool("videoscreen.safefull"))
+ safeFull = true;
// deactivate any window
CLog::Log(LOGDEBUG,"CGUIWindowManager::PreviousWindow: Deactivate");
DWORD currentWindow = GetActiveWindow();
@@ -270,7 +273,7 @@
HideOverlay(pNewWindow->GetOverlayState());
// deinitialize our window
- g_audioManager.PlayWindowSound(pCurrentWindow->GetID(), SOUND_DEINIT);
+ if (!safeFull) g_audioManager.PlayWindowSound(pCurrentWindow->GetID(), SOUND_DEINIT);
CGUIMessage msg(GUI_MSG_WINDOW_DEINIT, 0, 0);
pCurrentWindow->OnMessage(msg);
@@ -282,10 +285,10 @@
// ok, initialize the new window
CLog::Log(LOGDEBUG,"CGUIWindowManager::PreviousWindow: Activate new");
- g_audioManager.PlayWindowSound(pNewWindow->GetID(), SOUND_INIT);
+ if (!safeFull) g_audioManager.PlayWindowSound(pNewWindow->GetID(), SOUND_INIT);
CGUIMessage msg2(GUI_MSG_WINDOW_INIT, 0, 0, WINDOW_INVALID, GetActiveWindow());
pNewWindow->OnMessage(msg2);
-
+ if (safeFull) g_graphicsContext.SetFullScreenRoot(true);
g_infoManager.SetPreviousWindow(WINDOW_INVALID);
return;
}
diff -r -u xbmc/XBMC/language/English/strings.xml xbmc_sf/XBMC/language/English/strings.xml
--- xbmc/XBMC/language/English/strings.xml 2009-04-02 12:34:29.000000000 +0200
+++ xbmc_sf/XBMC/language/English/strings.xml 2009-04-02 11:16:14.000000000 +0200
@@ -993,6 +993,8 @@
<string id="13119">Sinc</string>
<string id="13120">Strict Pixmap-Texture Binding (requires restart)</string>
+
+ <string id="13121">Safe fullscreen mode</string>
<string id="13130">Display blanking</string>
<string id="13131">Disabled</string>
diff -r -u xbmc/XBMC/xbmc/Application.cpp xbmc_sf/XBMC/xbmc/Application.cpp
--- xbmc/XBMC/xbmc/Application.cpp 2009-04-02 12:40:34.000000000 +0200
+++ xbmc_sf/XBMC/xbmc/Application.cpp 2009-04-02 11:20:12.000000000 +0200
@@ -834,6 +834,7 @@
#endif
// set GUI res and force the clear of the screen
+ if (g_guiSettings.GetBool("videoscreen.safefull"))
g_guiSettings.m_LookAndFeelResolution = AUTORES;
g_graphicsContext.SetVideoResolution(g_guiSettings .m_LookAndFeelResolution, TRUE, true);
// initialize our charset converter
@@ -906,6 +907,8 @@
time(&seconds);
srand((unsigned int)seconds);
+ if (g_guiSettings.GetBool("videoscreen.safefull"))
+ g_graphicsContext.ToggleFullScreenRoot();
return CXBApplicationEx::Create(hWnd);
}
diff -r -u xbmc/XBMC/xbmc/GUISettings.cpp xbmc_sf/XBMC/xbmc/GUISettings.cpp
--- xbmc/XBMC/xbmc/GUISettings.cpp 2009-04-02 12:40:34.000000000 +0200
+++ xbmc_sf/XBMC/xbmc/GUISettings.cpp 2009-04-02 11:22:37.000000000 +0200
@@ -633,6 +633,7 @@
AddString(3, "videoscreen.guicalibration",214,"", BUTTON_CONTROL_STANDARD);
AddString(4, "videoscreen.testpattern",226,"", BUTTON_CONTROL_STANDARD);
AddInt(6, "videoscreen.vsync", 13105, DEFAULT_VSYNC, VSYNC_DISABLED, 1, VSYNC_DRIVER, SPIN_CONTROL_TEXT);
+ AddBool(7, "videoscreen.safefull", 13121, false);
AddCategory(7, "filelists", 14018);
AddBool(1, "filelists.hideparentdiritems", 13306, false);
This is the diff file :)
Thanks a lot. My patch-fu is weak though - mind sharing the command line to patch?
Thanks
xnappo
fasteddy
2009-04-02, 16:44
[Edit: Removed instructions. Given that I'm no expert on patch and diff, I don't want to send you down the wrong path.]
shassino
2009-04-02, 19:08
open a terminal
move just outside xbmc src folder
patch -p0 < diff_file
u should get:
shm@shm-desktop:/media/htpc$ patch -p0 < diff
patching file xbmc/XBMC/guilib/GUIWindowManager.cpp
patching file xbmc/XBMC/language/English/strings.xml
patching file xbmc/XBMC/xbmc/Application.cpp
patching file xbmc/XBMC/xbmc/GUISettings.cpp
AllanMar
2009-04-07, 02:01
So how is everyone making out with this now? Ive just been using the old svn before the patch was removed and its been working quite well. With the exception of the dark knight, for whatever reason.
There is some probs with regards to the library and such in this old version though, so I want to upgrade to the latest linux port. Is this working for anyone? If not I guess ill try the patch posted above.
I have been reading the the VDPAU thread and there seems like there may have been some progress with regards to this prob, any info?
Asswipe44
2009-04-10, 04:54
just out of curiosity, have you tried what i been mentioning earlier as a problem? Try starting xbmc in auto resolution, then goto settings, change to 1080 and hit test resolution, then try playing your video
thank you!!!!!!!!!!!!!
So how is everyone making out with this now? Ive just been using the old svn before the patch was removed and its been working quite well. With the exception of the dark knight, for whatever reason.
There is some probs with regards to the library and such in this old version though, so I want to upgrade to the latest linux port. Is this working for anyone? If not I guess ill try the patch posted above.
I have been reading the the VDPAU thread and there seems like there may have been some progress with regards to this prob, any info?
I applied the above patch to the latest linuxport as of a few days ago, and it works great for me. Solves my 8200 IGP problems.
AllanMar
2009-04-15, 23:42
So just a little update. I applied the patch to the SVN with a bit of effort. For the most part is was working well, however some movies still didnt quite play right. But only one or two odd 1080p ones.
After reporting this problem when i first built my HTPC i was getting kind of tired of screwing around with it and just wanted to enjoy some movies. I noticed a MSI 9400 silent card go on sale for $60 (cdn), so i decided id grab it, if nothing else itd be good for my desktop (which cant currently handle 1080p). I slapped that into my HTPC and instantly every problem ive been experiencing with the 8400 has been fixed. Ive also noticed that even movies i thought were working fine before, now run with much higher bitrate. Before the framerate would vary a bit between 23.7 and 24 and now it stays locked at 23.8fps.
VDPAU now works flawlessly without the safe fullscreen patch. I know this info isnt really a surprise since we established awhile ago this was an 8200 series problem. But I just thought id share my experience.
I too have noticed a couple videos that don't play right. Not frame drops, but some weird artifacts on the screen, particularly in high-motion scenes. I wouldn't mind writing this off as an 8200-specific problem, if not for the fact that every video I have plays perfectly, and almost always has, in mplayer (with vdpau). But it's hard to go back to MythVideo after I've seen XBMC with Media Stream skin. :(
-- Kevin
I believe I have found the issue, try rebuilding with this patch
http://xbmc.org/trac/ticket/6761