Official BS.Player forums

Official BS.Player forums (http://forum.bsplayer.com/index.php)
-   General Talk And Support (http://forum.bsplayer.com/forumdisplay.php?f=8)
-   -   Real (average) fps is lower than labeled one (http://forum.bsplayer.com/showthread.php?t=11760)

kimiraikkonen 17th October 2010 06:50 PM

Real (average) fps is lower than labeled one
 
Hi,

As i'm used to be curious investigating movie fps by pressing ALT+3 in Bsplayer, found out that though the movie (like WMV) is labeled and "seems" encoded at 30fps (looked with MediaInfo), real average fps doesn't exceed 22 or 20 fps. Though i cannot notice it visually, i believe it's right statistically.

Note: Some of other files encoded at 30fps are running fine, at 30 fps as average.

So, was there some loss of frames during encoding though file header labeled at 30fps?

Any idea about it?

Thanks!

adicoto 18th October 2010 07:33 AM

If your computing power is close to the minimum specifications, displayed framerate may lower beneath real framerate. And that depends on the file resolution (you can play fine 720x576 but can't play 1280x720).

kimiraikkonen 18th October 2010 09:47 AM

I though this but system resources are almost free, CPU load is under %30. So, i highly doubt that the frame loss happened during encoding/capturing the video? Can it be?

adicoto 18th October 2010 09:15 PM

Options -> preferences -> video -> rendering -> try not to skip frames - is it enabled ?

kimiraikkonen 19th October 2010 10:01 AM

Quote:

Originally Posted by adicoto (Beitrag 42954)
Options -> preferences -> video -> rendering -> try not to skip frames - is it enabled ?

I do not have that option. Mine's version is a bit old and it seems that feature is new.

BSPeter 19th October 2010 11:01 AM

The option "Try not to drop frames" was introduced in version 2.21.950 of begin May 2007!!
To avoid misunderstandings and useless conversations (about issues which may possibly already have been covered in newer builds) posters should always mention version and build number! (This is equally valid for longstanding faithful and loyal supporters/users of BS.Player.)
:confuse:

kimiraikkonen 19th October 2010 08:32 PM

Quote:

Originally Posted by BSPeter (Beitrag 42958)
The option "Try not to drop frames" was introduced in version 2.21.950 of begin May 2007!!
To avoid misunderstandings and useless conversations (about issues which may possibly already have been covered in newer builds) posters should always mention version and build number! (This is equally valid for longstanding faithful and loyal supporters/users of BS.Player.)
:confuse:

The problem in the thread which you closed: (Edit BSPeter: for what it's worth: thread reopened again)
http://forum.bsplayer.com/general-ta...cpu-usage.html

...was completely different than the current thread. It was about a problem that results in frame drops, reported in ALT+3 video info page due to "internal renderer overlay(default)".

The current thread is about seeing real-time (average) framerate "lower" than expected, THOUGH no frame drops are reported in ALT+3. I mean, they're not the same. I beleive average frame rate, which is lower than expected, is because of capturing/encoding couldn't have managed to reach expected fps.

I noticed when i capture something from my Conexant TV capture device (AverTV) via Windows Media Encoder(you can try) 9, for some reason, average frame rate doesn't exceed 18~21 fps though expected is 30fps using sufficent bitrate setting with more than %50 of cpu is free.

Just wanted to get ideas about it, as i reproduced it.

adicoto 19th October 2010 11:18 PM

Can you upload a sample of such a file ? You didn't mention that there were files captured by you. I would like to test such a file.
On the other hand, none of the programs we talk about have the posibilty to take 100 % of CPU usage (in BSplayer's options you can set it's afinity but I believe you don't have such a new version). So, the OS doesn't allow to all aplications to have acces to full CPU usage, that's why you will notice that even if it does not use the CPU at 100%, some proceses will run slowly (such a capture device). If I am corect, to do a WMV capture and on-the-fly compresion for a resolution of 576x384@29,97 you will need at least a P4 @ 2GHz CPU (that excludes older Athlons, most of the Semprons and Celerons)


All times are GMT +1. The time now is 11:29 AM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
Search Engine Optimization by vBSEO 3.6.0 PL2
Ad Management plugin by RedTyger


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20