Getting the best encoder results...
|
|
does anyone know which setting will give me the best results… |
|
|
Aha, well this is an interesting one. There is a flag which gives most dramatic results is “-n”, which controls the minimum bitrate. The default is 12000, but you can try using “-n 24000” or even “-n 32000”. There is a downside, however. The higher you take the minimum bitrate, the more chance you have of stuttering in the video, when the ARM9 CPU cannot keep up with the video data. What someone could do for us all is test out different minimum bitrate values. Try something like 20000, 24000, 28000, 30000, etc… and see at what level you still get watchable results. Then post back the results to the forums, and I’ll sticky it as a guide to quality levels. Also, you might want to try it on two different types of video. One with lots of motion and camera movement, and one without. The motion affects stuttering, and even at the default levels you will occasionally hear repeated audio when the ARM9 can’t keep up. |
|
|
interesting… ill try a few things and post my finding here in this thread |
|
|
Looking forward to it, Also, would dsvideo work any better with a RAM expansion pack? |
|
|
now that there is a good idea!!! can something be done to get better results with the ram pack? |
|
|
ok i’ve done some testing… and here are the results: |
|
|
No, unfortunately the ram pack won’t make any difference. The decoder is entirely limited by the CPU, and only needs around 500kb to run (most of the ram available on the DS isn’t currently used). |
|
|
is it possible to do this |
|
|
ekolimits: Thanks for the testing, and the information is roughly inline with what we were expecting, based on our own encode tests during development. You can effectively say that “-n 32000” is like a High Quality mode. magenta: Yes, you can use -n and -x together to define lower and upper limits on bit rate.
I’m not sure how good the results will be with such a low maximum bitrate value, but this makes the encoding behave more predictably in terms of resulting file size, like fixed bitrate encoding. In fact, if you made both -n and -x values the same, it would be fixed bitrate. |
|
|
ok i just tested a full length Bourne Ultimatum DVD on DSvideo and got great results at 30000 minimum bit rate ! I do find it interesting that you can set a fixed bit rate and it is probably true that 32000 bits per frame are the best quality without loosing out on sound… The movie moves fast, Its bourne of course the action is there so that tested the video… which passed with flying colors!!!! Im thinking of putting a youtube video of DSvideo in action playing this movie cause it looks and sounds great!!! the only thing is the volume is not loud enough… can you guys implement a volume amplyfier… something like moonshell where it will output sound at at least 400x what the natural sound is… the quality goes down and i know that but that feature is definately useful because of movies like the on i tryed where i couldnt hear much… |
|
|
something interesting i noticed… |
|
|
Hmm I remember a bug in early beta where you couldn’t seek past a certain point in the video, which turned out to be the 65535th frame, and it was due to an overflow bug. This is possibly related. 65535 frames is roughly 90 minutes. |
|
|
nah, the movie is there completely encoded and viewable… its just the time doesnt show on the bottom… |
|
|
65535th frame? So the frame counter is an unsigned int value. I would recommend using unsigned long value which has a limit to 4294967295 :D |
|
|
Well that bug got fixed very early in closed beta testing, but there’s a chance it’s related. |
|
|
if you want more movies just buy like 3 2gb cards thats 2500mb of video that like the whole harry potter line or every game ever made from 1970’s – 1980’s |