Abnormal playback performance
Posted: Wed Jun 23, 2010 2:44 pmHello,
I tried on searching about this problem, but did not find anything. Please forgive me if I had overlooked something and now this gets posted again.
I don't really know if this is the right place to ask about this and/or if I ask this in a correct way. Please bear with the annoyance I [probably] am.
Here goes:
I am using, as SMPlayer's about>info says, SMPlayer 0.6.9 (SVN r3447) and MPlayer SVN r31042 - (both from rvm's PPAs on launchpad); Ubuntu 10.04 with 2.6.32-22 kernel;
Noticed this behaviour today. it was OK a week ago.
When playing a specific video file (info about the file is all there in the MPlayer logs I've attached), at the beginning of the video everything runs smoothly, but as the video goes further, no matter if it goes forward with a normal playback, or by jumping/seeking forward, it starts playing gradually worse and worse. Going past the first 10% of the video, or so, it is almost unwatchable.
Playback of this video, using MPlayer alone, goes flawlessly.
This might be related to the fact that I had updated my nvidia driver to ver. 256.25 a couple of days ago. (Updated to 256.35 a couple of minutes ago, while writing this line)
This video file should normally be easily playable with my hardware, not to mention that when testing, I (think I) turned off everything what could require additional processing power.
Noticed that changing the ceche for local files affects how badly it plays. I have my cache for local files set to 4096 kb; that portion of the video (last ~90%) plays very choppy with that. if the cache is set to 2048kb or lower, that portion turns practically unplayable - can be described like: "similarly as if someone would be pausing the video for one second every half a second". If the ceche is set to at least 20480kb (20mb !), then that portion is somewhat watchable - the sound chokes rarely, and the video undergoes pretty intensive framedrop.
Two MPlayer logs are attached: first one - playing the beginning of the file; and the second one - playing somewhere in the middle. Also, thought of attaching another log - playing around the middle with 20480kb of cache, but it does not show anything more than the 2nd one. Also, the only [real] difference between the 1st one and the 2nd one, is that 2nd one says my hardware is too slow. No such message when playing on MPlayer alone (except when I trigger a strange, but totally harmless [bug, maybe?] in MPlayer itself.); Scrap that, attached another, third log - SMPlayer, playing past median point, using 20480kb of cache.
So: is this some sort of SMPlayer bug; my system is just messed itself up in some sort of a strange way; or [insert reason here; i.e. something else]? And, maybe some pointers on fixing this?
~Thank You for Your time.
~Vinis
P.S. Sorry for my cruddy english, and for the fact that I keep using british and american english in the same text.
P.P.S. VLC also plays it flawlessly.
P.P.P.S I have deleted the stored settings entry of this file in the smplayer_files.ini before starting the test, and also deleted it when trying to fix problem somehow.
I tried on searching about this problem, but did not find anything. Please forgive me if I had overlooked something and now this gets posted again.
I don't really know if this is the right place to ask about this and/or if I ask this in a correct way. Please bear with the annoyance I [probably] am.
Here goes:
I am using, as SMPlayer's about>info says, SMPlayer 0.6.9 (SVN r3447) and MPlayer SVN r31042 - (both from rvm's PPAs on launchpad); Ubuntu 10.04 with 2.6.32-22 kernel;
Noticed this behaviour today. it was OK a week ago.
When playing a specific video file (info about the file is all there in the MPlayer logs I've attached), at the beginning of the video everything runs smoothly, but as the video goes further, no matter if it goes forward with a normal playback, or by jumping/seeking forward, it starts playing gradually worse and worse. Going past the first 10% of the video, or so, it is almost unwatchable.
Playback of this video, using MPlayer alone, goes flawlessly.
This might be related to the fact that I had updated my nvidia driver to ver. 256.25 a couple of days ago. (Updated to 256.35 a couple of minutes ago, while writing this line)
This video file should normally be easily playable with my hardware, not to mention that when testing, I (think I) turned off everything what could require additional processing power.
Noticed that changing the ceche for local files affects how badly it plays. I have my cache for local files set to 4096 kb; that portion of the video (last ~90%) plays very choppy with that. if the cache is set to 2048kb or lower, that portion turns practically unplayable - can be described like: "similarly as if someone would be pausing the video for one second every half a second". If the ceche is set to at least 20480kb (20mb !), then that portion is somewhat watchable - the sound chokes rarely, and the video undergoes pretty intensive framedrop.
Two MPlayer logs are attached: first one - playing the beginning of the file; and the second one - playing somewhere in the middle. Also, thought of attaching another log - playing around the middle with 20480kb of cache, but it does not show anything more than the 2nd one. Also, the only [real] difference between the 1st one and the 2nd one, is that 2nd one says my hardware is too slow. No such message when playing on MPlayer alone (except when I trigger a strange, but totally harmless [bug, maybe?] in MPlayer itself.); Scrap that, attached another, third log - SMPlayer, playing past median point, using 20480kb of cache.
So: is this some sort of SMPlayer bug; my system is just messed itself up in some sort of a strange way; or [insert reason here; i.e. something else]? And, maybe some pointers on fixing this?
~Thank You for Your time.
~Vinis
P.S. Sorry for my cruddy english, and for the fact that I keep using british and american english in the same text.
P.P.S. VLC also plays it flawlessly.
P.P.P.S I have deleted the stored settings entry of this file in the smplayer_files.ini before starting the test, and also deleted it when trying to fix problem somehow.