I write this tool for my video conversion works. I hope that is helpful.
NET Framework 3.5 required.
Beta 1.6: BitRater_1_2_Beta_6.zip
* Add Video Type List
* Add new Quality Factor members.
* Add "DTS" in "Audio Bitrate" list.
* Fix some bugs.
+ Reply to Thread
Results 1 to 30 of 74
Last edited by Hikmet; 4th Jun 2013 at 03:47.
When releasing new software always use www.virustotal.com to scan it just to be sure,
Your zip and exe are clean.
I'm adding a mirror to this post also if it's okey. I might add it to our tools/software list later also.
Maybe I am mistaken but it comes over buggy to me.
Change the quality factor and then follow that with the framerate amd bitrate/file size goes off the scale.
If not enter video time, file size can not calculate...
Last edited by Hikmet; 18th May 2013 at 16:08.
Here is a short vid to show what I mean
I follow your steps, but not happen. Try again and again, but not happen. But in your video, bitrate value invalid calculated...
This is maybe .NET Framework issue. Uninstall .NET Framework and install again.
You bet it's invalid
My .Net Framework was 'repaired' a few weeks ago when an update corrupted it. It should be ok since the programs, other than this one, that rely on it appear to be working fine.
I will do as you ask but not tonight. But I would also ask what your final result from the shown steps is.
This is .NET Framework issue...
I check my code. I think, Framework data type conversion problem occur. Force conversion and recompile. Please download and try again.
[Attachment 17935 - Click to enlarge]
Last edited by Hikmet; 18th May 2013 at 17:52.
"a lot of people are better dead" - prisoner KSC2-303
Ran the new version. Same result.
Uninstalled .Net 4 and 3.5. Reinstalled 3.5. Same result on both versions
Reinstalled .Net 4. No change.
Everything* appears normal until the very last step which should return as it appears in step 2. *I do note however that the total file size - video and audio - is also wrong.
I have to install .Net 4 since one program I use depends on it. Just tested that and it works fine.
Now this could be my setup but I would like to hear from others if they also have problems.
I can live without your calculator.
Confucus would say "You can test your software on 00's of PC's but you will still find one lemmy for which it does not work as intended"
The challenge is to find out why.
But surely you are trying to 'have the cake and eat it'
With one sentence you say my system is at fault and then you say the fault lies with .NET . If both were equal I would get the same results as you but even replicating your initial screen my total video and audio is 100 times larger than yours.
Like I said, I do not really care but I appear to be the only person coming forward on here to have tested this. If .NET is conflicting with something in my system then it would be nice to know all the same.
BTW The 'default' button also does not appear to work. Well it worked once and gave me the crazy paving answer but that is the only time it worked.
I have the same problem,the final size is estimated as 185330.00 MB when 1 hour and 30 minutes are input.I think,therefore i am a hamster.
(1280 * 720 * 23.976 * 0.160) / 1000 = 3535,405056
And convert unsigned integer, result must be "3535", not "3535405". But some computers .NET framework cannot convert unsigned integer properly. It is MS fault.
Next version I will try convert another way or compile NET Framework 4.0.
I change convert method and release new version (1.1):
Last edited by Hikmet; 20th May 2013 at 03:44.
You simply can not blame 'some computers'. A program should work on all.
It works at step 2 of my sample so it 'works'. That is to say it is converting. So by the same token it should work at the final step.
public static uint CalcVideoBitrate()
float fRate = ( (float)stValues.uiWidth *
stValues.fFactor ) / 1000.0f;
Why some computer not bug, but another in bug? And what is your OS and CPU?
And I don't trust .NET Framework Library anymore. I will write own library next time...
I do not know c#.
I only know what I cee. Run that video again again look closely at step 2 where the QF changes to h264.high. The result IS 3535 which means that the result has been rounded (I understand that much)
Then in the final step the QF comes back to h264.high. So logic dictates that if it works first time then it should work the second time.
You can check my OS and cpu by looking at my profile (mouse-over the centre icon) but do not blame that or just restrict your sw to Win7 etc.
And lots of software aren't perfectly cleaned as some antivirus thinks that everything is malware or suspicous.
But back to topic now.
Well done. The true art of debugging is to eliminate the suspect libraries.
Shame that the fault does not appear to be with .NET as this phenomen - the bad last step - is still present.
And, to repeat, what is the issue with the total video+audio size ?. That is also still wrong by a factor of 100.
I apologise for breaking your software but when it works as I expect it to then my 'beta-testing' will be done.
Problem is .NET Framework, because I cannot write convert operations. I need to use .NET Framework convert operations.
This is small program and I don't use trace log mechanism. But, I will add log mechanism next time...
And, I add very very simple log mechanism. Please Copy/Paste Log text and send to me...
Last edited by Hikmet; 20th May 2013 at 08:05.
From the last two steps...
So you see it is actually the fps, going from a whole number to 23.976 but calculated at 23976, which throws the calculation.
Last edited by Hikmet; 20th May 2013 at 09:29.
The last 3 steps:-
Bitrate - shown correctly
File-size - shown correctly
Total filesize - shown correctly
Default button - responds correctly
I think we have a winner.
I think you should leave that log screen as it can be of assistance.