I always choose FFMPEG and then Matroska Lossless. Then I compress using Handbrake before uploading to youtube.
I don't know what quality settings are used when using the Matroska preset, so I generally avoid that. But maybe someone knows. I haven't tested it.
I see no point in using AVI. It's very old and supports only specific formats. MKV supports pretty much everything.
Sooo... I know I should have asked this sooner, but...
How is the emulation of Genesis on Bizhawk now? Because if it's good enough, then I'll use it over Gens.
Is it as reliable/accurate/stable as the one from Gens?
Sorry for double posting, but I wanna ask something again.
This might sound pretty dumb, but is there a way to make a .gmv file work on BizHawk? That's because I made a couple movies with Gens, so I was wondering if BizHawk could make the .gmv work without desync.
It's saying above that they added .gmv movie importer on one of the earlier versions. Does that mean it's possible to do what I want?
Joined: 3/31/2010
Posts: 1466
Location: Not playing Puyo Tetris
Due to accuracy (?) differences between Gens and Bizhawk, Desyncs are VERY likely. Sure you can import, but don't expect it to run correctly with out doing work to make it resync.
When TAS does Quake 1, SDA will declare war.
The Prince doth arrive he doth please.
First time using Bizhawk (love it) and I have a few questions about the N64 plugin support. Sorry if these have been asked and answered before.
I know Bizhawk depends on Mupen64, but is there any way to use other video plugins aside from the 3 offered? I'm looking for the video plugin that makes games look as close to the original as possible (zero enhancements). I've read a lot as to why that's very difficult to achieve.
So from the ones offered with Bizhawk: Glide64 makes games look awful, Glide64mk2 doesn't work at all for me, and Rice looks very good from what I have tested. Text and sprites look really good while still maintaining the polygons as close to the original console. The latter one is my preferred plugin, however, I recently heard about a plugin called "Softgraphic" and I would love to try it to see if it's better than Rice's, but Mupen64-rr, which lets you select that plugin doesn't load for me (I get a missing SDL.dll and glew32.dll error).
So, any way of using bizhawk with that Softgraphic plugin?
Some advocate for the plugin who has got it running will have to advocate for it. There's no way to use an n64 plugin in bizhawk without it being coded in, and theres no way to use an n64 plugin in a rerecording emulator with it being scrutinized by programmers, as most of them require some measure of repair.
Are you so sure that the already-provided plugins are stacked with enhancements?
Oh no no, the Rice plugin works just fine. Glide64 looks awful, and Glide64mk2 doesn't work for me, so I can't comment on that one.
But that Softgraphics plugin looks the most faithful to the real thing. It's missing the trademark fog of N64 games, but at least bitmaps and sprites look great with no cut borders.
I understand the sole purpose of bizhawk is to make TAS(es), so faithful graphics or plugins is not really a priority. I got Mupen64-rr working now, so I can always use that one, even if it's missing all the great options Bizhawk has.
OK, your choice of terminology is confusing. What you're looking for is the least horrible graphics plugin. Unfortunately with N64 they're all horrible, so you just have to pick which particular horribleness you prefer. "Faithful graphics" is a gross simplification and a matter of opinion.
Heh, yes I know they are all horrible. Sorry for being confusing. But the least horrible is the softgraphics plugin (which actually requires a lot more CPU power to run at a decent speed) and I was wondering if that might be supported. But I supposed it will not be, at least not anytime soon since it's not optimal for TASing.
I would just like to emphatically state that making TASes is NOT the sole purpose of Bizhawk. I am one of the core developers for Bizhawk and I am definitely more of game-player than a TASer. Although adelikat, natt and zeromus all have a long history with TASvideos so, you know, I'm outnumbered.
Bizhawk is about more than TASing, BUT, sync-stable emulator cores are kind of a requirement. A lot of emulator cores that have never been targeted for movies aren't sync stable because it's easy to make subtle mistakes or omissions that break sync if you aren't explicitly targeting it and testing for it.
Sync stability and determinism is key for just having robust savestates and rewind, so the sync-stable requirement doesn't only benefit TASing.
Emulator Coder, Site Developer, Site Owner, Expert player
(3573)
Joined: 11/3/2004
Posts: 4754
Location: Tennessee
For the record, I agree with Vecna. TASability is one of the requirements I consider for releasing new stuff, but that is just one aspect of Bizhawk among many. Personally, Bizhawk is my preferred casual gaming emulator because I get nice rewind, hassle free fullscreen, and all my preferred hotkeys. Also, we put a lot of work into making a nice UI for all the various features that each core needs.
Got it.
I've been messing with this SoftGraphics plugin in Mupen64-rr and it look great. No bitmaps cutting off, HUD text looks N64 blurry and not the usual plugin blurriness.
It's a shame that Mupen64-rr doesn't have all the Bizhawk options, and all the options all the other rerecording emus have (FCEUX, SNES9X, etc).
Is the hook-up function for Pier Solar finished?
ps: One suggestion: Is it possible to put control settings in a separate .ini file from other configurations?
I thought it's better to clear the settings after a major update, but resetting controller settings every time doesn't seem necessary. It might be nice if it's possible to keep the controller settings while clearing other configurations.
Emulator Coder, Site Developer, Site Owner, Expert player
(3573)
Joined: 11/3/2004
Posts: 4754
Location: Tennessee
all releases come with default.json, that's the input settings that are put into the config when you reset your input (or fresh start). So if you want, just edit that and reuse it.
However, keep in mind that even input config is subject to changes (new cores, new peripherals)