akapuma
1st August 2004, 01:13
Hello,
normally, I use BeSweet in a DOS-BOX under WIN98SE. Now, I tested some different alternatives of prompting:
My normally method, the DOS-Box, is the slowest! For a test-transcoding, I needed 4:53min. If I use a minimized DOS-Box, I need 4:37min. Not much faster.
It is much faster, when using a DOS-Fullscreen: Start via Windows: 3:00min, Start from a DOS-Fullscreen via "Command": 2:59min. But a minimized fullscreen is approx the same as a minimized DOS-Box: 4:36min.
The fastes one is appending ">NUL" in the BeSweet commandline, e.g.:
c:\programme\BeSweet\BeSweet.exe ....parameters.... >NUL
Duration for a transcoding in a DOS-Box: 2:48min
Duration for a transcoding in a DOS-Fullscreen: 2:46min
Disadvantage: No visual output while transcoding.
My recommendation at DSPGuru:
Can you refresh the output while transcoding only every 1 second? I think, you can make your great BeSweet much faster (up to 40-50%?)
Best regards
akapuma
normally, I use BeSweet in a DOS-BOX under WIN98SE. Now, I tested some different alternatives of prompting:
My normally method, the DOS-Box, is the slowest! For a test-transcoding, I needed 4:53min. If I use a minimized DOS-Box, I need 4:37min. Not much faster.
It is much faster, when using a DOS-Fullscreen: Start via Windows: 3:00min, Start from a DOS-Fullscreen via "Command": 2:59min. But a minimized fullscreen is approx the same as a minimized DOS-Box: 4:36min.
The fastes one is appending ">NUL" in the BeSweet commandline, e.g.:
c:\programme\BeSweet\BeSweet.exe ....parameters.... >NUL
Duration for a transcoding in a DOS-Box: 2:48min
Duration for a transcoding in a DOS-Fullscreen: 2:46min
Disadvantage: No visual output while transcoding.
My recommendation at DSPGuru:
Can you refresh the output while transcoding only every 1 second? I think, you can make your great BeSweet much faster (up to 40-50%?)
Best regards
akapuma