How do I reduced the speed percentage for the games of the Dolphin emulator?
Basically, instead of playing at 100% how would I play consistently at 50%?
I've tried loading Final Fantasy I & II: Dawn of Souls with it. I get an error stating that I don't have the correct BIOS, or words to that effect.
BizHawk has been compatible with GBA games since version 1.8.0 I think, so what needs to be changed in terms of settings?
So I downloaded BizHawk 1.8.3.
Proceeded to load an SNES game, and then attempted to configure the controls to my wired XBOX 360 Controller. It is not recognizing any of its inputs.
Could someone please assist with this?
I've been experiencing a slight problem with the latest version of BizHawk (latest as of the time and date of this post).
With respect to N64 ROMs, some work with BizHawk 1.6.0, and others don't. Some examples:
a) Super Mario 64 worked just fine.
b) With Perfect Dark 64, the load screen came up (it's the first thing you see when you start the game), then it froze.
c) BattleTanx did not load at all.
Any help with this would be appreciated. I'm using the Rice plugin in all instances.
Thank you for the replies.
Also, I just downloaded BizHawk 1.6.0 and immediately after unzipping the files, my anti - virus software (Norton 360) deleted a bunch of them.
Do these files pose a threat to my computer's safety? If not, why does my anti - virus software identify and delete them? Finally, are these files integral to BizHawk's ordinary operation?
Good day to you all.
So I've had some issues with VirtualDub that I've previously discussed here. I have for the most part solved them.
I'm now trying to resolve an issue relating to the .avi files rendered by VirtualDub. I use x264vfw (but not with the command line).
The problem is that the .avi file produces an error when I try to add it to Movie Studio Platinum 13 (MSP13). Something about codecs.
What do I do? I'm looking to add audio to these .avi videos, and it's the only way I know how that doesn't involve the use of complicated muxers that never work for me anyway.
EDIT: Furthermore, when I try to use a N64 game with BizHawk, I get an error. Is BizHawk not compatible with N64 games, or must I download something else first?
Hello, good day to you all.
I've made this topic to bring to the attention of those who may be concerned that the standard command line for x264 encoding:
--keyint 600 --ref 16 --no-fast-pskip --bframes 16 --b-adapt 2 --direct auto --me umh --merange 64 --subme 10 --trellis 2 --partitions all --input-range pc --range pc --rc-lookahead 250 --no-dct-decimate --tcfile-in times.txt
I tried using that, but when I drag and drop the file into the command prompt window, nothing happens.
Drag'n'drop it onto the file encode.bat.
This did not work, either.
Error message?
Yes.
I've also downloaded xVid and ffdshow codecs to use with VirtualDub, but I have no idea how to go about using those to achieve the same outcomes x264vfw did.
I just wish there was another straightforward method of doing what VDub did.
I tried using that, but when I drag and drop the file into the command prompt window, nothing happens.
Drag'n'drop it onto the file encode.bat.
This did not work, either.
I think I will continue looking for a solution to this new problem. I just can't grasp how a program which was working just fine a week ago is completely non - functional now.
Seems like x264vfw is too old (?) so it doesn't know about the --input-range option. You could try updating it, but it probably won't help...
Just use the following: encode.rar
Extract (WinRAR/7-Zip/...) and use the batch file. Edit it to change the parameters.
I tried using that, but when I drag and drop the file into the command prompt window, nothing happens.
I am more concerned about the fact that something I used with great success before (from the date on which your screenshot was posted to yesterday) no longer works at all. How can that be? x264 wasnt too old up until then.
[...]
I think I read sometime ago that it's a well - kept secret. If that's the case, then could someone explain why?
Where did you read that? The script producing this kind of layout is public (be it not too well documented).
Well, a long time ago I saw a LP video with that layout, someone commented asking how to achieve it, and the uploader responded by saying that, as stated above, it was a well - kept secret. I don't remember the particular Let's Player or video.
I think I've started to get the hang of the encoding process for FCEUX when using VirtualDub. Of course I want to move onto other consoles as well.
So, given the command line I was so generously given (seriously, thanks for that), I'm looking to achieve similar results with snes9x and the VisualBoyAdvance.
I've read that the appropriate dimensions are:
SNES - 256x240 OR 256x224;
VBA - 240x160.
And for the sample aspect ratio:
SNES - 5:4
VBA - ??? (The page I'm looking at doesn't specify).
So, if I keep everything else the same (including the dimensions of 2048x1796), will the video's quality be similar to what the NES looks like?
I have here another topic with another question.
Every TAS for the Nintendo DS I have seen lately has had the following layout:
http://www.youtube.com/watch?v=vrTvCqPtxao
How is this layout achieved?
I think I read sometime ago that it's a well - kept secret. If that's the case, then could someone explain why?
Thank you all for helping me with the encoding processes. I have experimented with VirtualDub and YouTube, and achieved the results I wanted, visual quality - wise.
Now I'm faced with a new problem.
I'm using VirtualDubMod in an attempt to add commentary to the video. I'm using the "Stream" feature. I add the audio commentary which was recording using Audacity.
I set both audio tracks to "Full processing mode".
Then, I render.
However, after the rendering, I only hear the system audio. If I highlight the volume audio for the commentary track, I only hear that track after rendering. It would appear that VirtualDubMod only allows you to render one at a time.
Is there any way around this, that won't compromise the visual quality? I'm looking to add the commentary audio to the remainder of the video, and to have both clearly audible.
Replace <keyint> with a number; it's described on that page.
The command line is actually the most flexible option; you can write batch files if you don't always want to type it out.
encode.bat:
@echo off
x264 --sar 7:6 --crf 20 --keyint 600 --ref 16 --no-fast-pskip --bframes 16 --b-adapt 2 --direct auto --me umh --merange 64 --subme 10 --trellis 2 --partitions all --input-range pc --range pc --rc-lookahead 250 --no-dct-decimate --tcfile-in times.txt -o video.mp4 %1
Now you can execute it with "encode dump.avi" from the command line or drag'n'drop dump.avi onto the batch file in Explorer.
So, what you're saying is, is that I should copypaste what you put into VirtualDub's command line? In that case it didn't work (I excluded "-o video.mp4 %1" as suggested).
I apologize for all these questions, and also if I'm being annoying by asking them. Once again I only started learning about encoding yesterday.
It should also be noted that I am using VirtualDub for this purpose (it is my understanding that this is all I will need; please correct me if I am wrong). [...]
- I am looking to encode this video to 1080p HD, if possible (720p, if not). [...]
- I am using x264 (64-bit) with VirtualDub (64-bit).
Note that for advanced video effects Avisynth is a popular tool; for that it'd probably best to use a 32-bit toolchain. VirtualDub can handle the resizing though; you just set "Video -> Full Processing Mode" and add a resize filter.
inavojo wrote:
At the bottom where it says "Use command line", I copypaste:
x264 --sar <PAR> --crf 20 --keyint <keyint> --ref 16 --no-fast-pskip --bframes 16 --b-adapt 2 --direct auto --me umh --merange 64 --subme 10 --trellis 2 --partitions all --input-range pc --range pc --rc-lookahead 250 --no-dct-decimate --tcfile-in times.txt -o video.mp4 in.avi
... as shown in the "Encoding" portion of the Encoding guide. I enter it exactly like that, without changing anything (which I'm fairly certain is the root of my problem).
That pasted text is a command-line to be used in a console window (like that of cmd.exe), and you need to use actual parameters for "<PAR>" etc. (open cmd.exe, navigate to where x264 is and use "x264 --fullhelp |more" to see all options).
If you're using VirtualDub then you can select the CRF and SAR values through that; also remove the "-o video.mp4 in.avi" part because files are handled by VirtualDub. You probably don't need the "x264" at the beginning either.
Ah, I should say that I used 7:6 as the value for the parameters (since I'm dealing with the NES).
Do I need to change the "--keyint <keyint>" part to anything?
Also is it possible to get the same results without having to go through all of this with the command line stuff?
Alright. I guess my question here would be, how would I convert a 256x224 video to 2048x1796 using VirtualDub?
Again, I am a complete newbie at this. In fact, I do not understand much of the terminology you have used (such as "point scaling".
Thank you.
Regarding my use of the command line feature and the part I quoted, do I use it, and if so how would I have to change it to ensure that I do not get an error?
For NES, which is 256x224, the smallest factor that works is 6 (1536x1344). However, due to how x264 works, using 8 (2048x1796) results in smaller filesize.
Also, lowering the CRF value produces better quality at expense of larger file size.
Regarding audio. Use Vorbis at high quality settings (at least 7) or uncompressed PCM. Beware that Youtube has had bugs in handling FLAC (specifically, parts of audio would go missing).
And if you want good quality, stay away from normal video editors. Those do who knows what to the video (and resaving the video after editing can lose a lot of quality).
... Of course "quality" here is relative. You can't get very good quality on Youtube. And also perennial problem is that youtube supports maximum of 30fps, and many games have effects that have frequencies above 15Hz and thus are not representable without higher framerate (by Nyquist sampling theorem).
Alright. I guess my question here would be, how would I convert a 256x224 video to 2048x1796 using VirtualDub?
Again, I am a complete newbie at this. In fact, I do not understand much of the terminology you have used (such as "point scaling".
At least I know that truly good quality isn't possible on YouTube. What I am aiming for, however, is akin to this:
http://www.youtube.com/watch?v=R0EoQ23CR7k
... when set to the "1080p" HD resolution.
In fact, I see that you encoded that TAS yourself.
Good day to you all.
First and foremost, let it be noted that I am completely new to the process of encoding. I only started to learn it yesterday (29th August 2013).
Essentially, I have no idea what I am doing and require some assistance.
So as to demonstrate that I have not attempted to help myself, here are some key passages of the Encoder Guidelines that I have read:
... our runs are intended to appear as though they could be played on the original hardware ... Thus, one core guideline for our encodes is to appear, as closely as possible, as though the run was played on the original hardware.
Quality: The video should look and sound as close to the pre-encoding input (i.e. raw emulator output) as possible.
This is what I am attempting to do. Please note that I am not looking to start my own tool - assisted speedruns. I am looking to replicate the aforementioned effect for my Let's Plays. They will be uploaded onto YouTube.
It should also be noted that I am using VirtualDub for this purpose (it is my understanding that this is all I will need; please correct me if I am wrong).
With reference to the Encoding Guide: http://tasvideos.org/EncodingGuide.html
I have followed steps 1 and 3 without trouble. Again, since I am not creating TASs, I have skipped steps 2 and 4. My difficulties lie with step 5: http://tasvideos.org/EncodingGuide/Encoding.html
From this point, please take into consideration the following:
- I am attempting to encode an .avi recording from FCEUX (version 2.2.1).
- I am looking to encode this video to 1080p HD, if possible (720p, if not).
- I am using the built - in .avi recording feature of the FCEUX emulator.
- I have modified FCEUX as specifically recommended by the Encoding Guide (this includes using the Lagarith Lossless Codec, and its own appropriate configurations).
- I am using x264 (64 - bit) with VirtualDub (64 - bit).
The few tutorials which on YouTube which deal with encoding on VirtualDub with x264 are made on the assumption that you're working with a video which has been rendered already. So I took a small gameplay from Mega Man 4 and rendered that.
I used Movie Studio Platinum 12.0, with the default "Video for Windows" (.avi) ---> HD 720p - 60p YUV template.
Afterwards, I put the rendered video into VirtualDub. Then I go to Video ---> Compression. I select the "x264vfw - H.264/MPEG-4 AVC Codec".
Then I click "Configure".
At the bottom where it says "Use command line", I copypaste:
x264 --sar <PAR> --crf 20 --keyint <keyint> --ref 16 --no-fast-pskip --bframes 16 --b-adapt 2 --direct auto --me umh --merange 64 --subme 10 --trellis 2 --partitions all --input-range pc --range pc --rc-lookahead 250 --no-dct-decimate --tcfile-in times.txt -o video.mp4 in.avi
... as shown in the "Encoding" portion of the Encoding guide. I enter it exactly like that, without changing anything (which I'm fairly certain is the root of my problem).
I then set the ratefactor to 20 (again, as recommended), enable the "Normal recompress" setting and then attempt to save as .avi.
It is here that I get an error (-100) regarding corrupt data.
My questions are these:
1. What am I doing wrong throughout this entire process?
2. Should I not use VirtualDub?
3. Is there an easier method to obtain the results I desire?
Any help would be greatly appreciated. Assume that my computer is sufficiently powerful to handle all but the most intense encoding processes.