Posts: 266
Joined: Nov 2003
Reputation:
0
ktd
Senior Member
Posts: 266
2004-05-11, 00:03
so now xbmc sometimes hang or shows a scrambled picture when i try to watch a 4:3 movie and xbmc auto switches from 16:9... me and frodo was working on that one for like a week before we found this solution to the problem...
please, uncomment the two sleep (1000); in xbox_video.cpp!!!
Posts: 266
Joined: Nov 2003
Reputation:
0
ktd
Senior Member
Posts: 266
thanks dday!
yes, its just the two // that needed to be removed.
Posts: 10,520
Joined: Sep 2003
Reputation:
10
Gamester17
Team-XBMC Forum Moderator
Posts: 10,520
2004-05-11, 17:48
are you sure jmarshall or butcher commeted this out on purpose in the cvs? (maybe it was causing other problem?, i don't know)
Posts: 266
Joined: Nov 2003
Reputation:
0
ktd
Senior Member
Posts: 266
maybe, but none that i herad of. i think they might thought it wasent needed because it only mess up 16:9 -> 4:3 for some of us and the sleep (1000); dosent have a coment why is in there...
Posts: 26,215
Joined: Oct 2003
Reputation:
187
not sure if it was me that commented this out in cvs or if it was someone else. it isn't needed on my system, obviously different tvs need more time to switch or something.
obviously some systems need the sleep there to switch correctly. i'm not exactly sure why this would be so. it seems to me that it would be primarily an xbox issue, as the sleep is performed before we reset the graphics system to the new resolution.
perhaps it has something to do with the fact that mplayer is in a separate thread so may call render() when we are in fact not ready to render. this doesn't really make much sense though.
i'd really like to figure out exactly why it is needed on some setups.
Posts: 761
Joined: Dec 2003
Reputation:
0
Butcher
Retired Developer
Posts: 761
actually it was me that uncommented it jmarshall. i didn't see any valid reason for it being there, so i removed it as people were complaining about slow starting of videos.
Posts: 26,215
Joined: Oct 2003
Reputation:
187
i too don't see any reason for it being there, except of course that it appears to stop bad things happening with ktd's setup.
seems very strange to me.
ktd: does it happen when switching from 16:9 -> 4:3 and 4:3 -> 16:9 and does it do it everytime, or only sometimes?
Posts: 761
Joined: Dec 2003
Reputation:
0
Butcher
Retired Developer
Posts: 761
i suspect it's a multi-threading issue, i've seen similar issues with multiple threads before.