Yeah, they stopped letting you choose your own codec. I'm not sure which codec it is they use, but it is high quality and opens with the editing programs I use. (VirtualDub and Adobe Premiere)
Ah s**t...
Thanks for your answer!
Usually I use lagarith lossless.
The codec they chose takes a lot of space during file writing, this is not really the best.
Is the choice of codec still possible on older versions?
Ah s**t...
Thanks for your answer!
Usually I use lagarith lossless.
The codec they chose takes a lot of space during file writing, this is not really the best.
Is the choice of codec still possible on older versions?
Older versions still allow codec change.
There are two codecs available at the moment, FMP4 (with the FourCC changed to XVID), and FFV1. FFV1 is your lossless codec, while FMP4 is your lossy codec.
By default, FMP4 is the codec it uses, and can be changed to FFV1 by going into Graphics > Advanced and ticking off the "Use FFV1 for Frame Dumps" options.
Ah s**t...
Thanks for your answer!
Usually I use lagarith lossless.
The codec they chose takes a lot of space during file writing, this is not really the best.
Is the choice of codec still possible on older versions?
Older versions still allow codec change.
There are two codecs available at the moment, FMP4 (with the FourCC changed to XVID), and FFV1. FFV1 is your lossless codec, while FMP4 is your lossy codec.
By default, FMP4 is the codec it uses, and can be changed to FFV1 by going into Graphics > Advanced and ticking off the "Use FFV1 for Frame Dumps" options.
I use Sony Vegas Pro 13, and some video converters which can change the audio in the encode. Now, as for 4.0 9283, they all just refuse to identify the format!
For 4.0 8715, converters can identify the encode, but SVP13 shows smashed video.
How to fix it?
TASing is like making a film: only the best takes are shown in the final movie.
I'm using Vegas Pro 13 as well; just make sure the xvid codec is installed.
For some reason, if you don't use RealXFB and end up in a non-60 FPS game, the encode gets buggy.
I've tried asking someone to fix this, but, no one has really looked into it and I'm not sure what's wrong. Apparently a lot of things don't react well to the blank frames.
What was the purpose of no longer allowing the user to select the codec?
FFmpeg doesn't allow the user to supply their own codecs the way VFW does. We switched to FFmpeg for various reasons, like avoiding the audio desync that could happen for instance during certain loading screens, having one cross-platform way to dump instead of maintaining a separate one for Windows, and avoiding the various limitations of the ancient VFW.
It seems virtualdub (with and without avisynth's avisource()) refuse to open FFV1 avi dumps. So I'm stuck using the supposedly lossy alternative.
On the other hand, it doesn't look that lossy to me. Looks good enough for youtube.
It seems virtualdub (with and without avisynth's avisource()) refuse to open FFV1 avi dumps. So I'm stuck using the supposedly lossy alternative.
On the other hand, it doesn't look that lossy to me. Looks good enough for youtube.
You'll need to use ffms2 avisynth plugin to load FFV1 video files.
The default codec is more than good enough quality to be used on YouTube.
To be precise, I keep getting explorer.exe and com suggorate crashes when moving/attempting to open that ffv1 avi dump.
It could be because I edited registry today to remove malware..
Edit: or - as this page says - the cause is a flaky video codec
Since this change of codec, for me, the sound is out of sync with the video (Wii and Game Cube).
Whereas before it was not.
Do others have this problem again?
Edit: Cut the extra part of the sound file at the beginning of it seems to work
Since this change of codec, for me, the sound is out of sync with the video (Wii and Game Cube).
Whereas before it was not.
Do others have this problem again?
Edit: Cut the extra part of the sound file at the beginning of it seems to work
Some games sync, some don't. Sometimes I need to cut audio.
TASing is like making a film: only the best takes are shown in the final movie.
Since this change of codec, for me, the sound is out of sync with the video (Wii and Game Cube).
Whereas before it was not.
Do others have this problem again?
Edit: Cut the extra part of the sound file at the beginning of it seems to work
The first Mario Party 5 WIP video I made was fine.
The second one had audio desync and I fixed it by delaying audio by -0.3 seconds.
Both videos used the lossy codec.
Joined: 9/21/2009
Posts: 1047
Location: California
Fog wrote:
sonicpacker wrote:
So is this new method the standard or are there plans to revert back to the "normal" way? I really prefer Lagarith personally.
Standard.
Can you explain the reasoning behind the change if you know why it happened? Like efficiency or any other sort of justified superiority that would out-favor customization and control? I want to make an encode and would like to know why this method is better, first. I assume it's better anyway, given the circumstances.
We switched to FFmpeg for various reasons, like avoiding the audio desync that could happen for instance during certain loading screens, having one cross-platform way to dump instead of maintaining a separate one for Windows, and avoiding the various limitations of the ancient VFW.
I really wish we had a better description of the change than that one I wrote up here... Unfortunately the change never made it into a Dolphin progress report. Fog, do you have anything to add to what I said?
Joined: 9/21/2009
Posts: 1047
Location: California
Yeah, I saw the above notes and was hoping for more answers since this method that users are now stuck with is extremely inconvenient for multiple reasons that I would argue outweigh what was written. Is there some way for devs to make Lagarith an option within the menu, similar to the current lossless codec? Not really wanting to write a script every time I would like a good looking video, or download the stuff required for it. That's regardless of the absurd file size it outputs. And the lossy codec is not nearly up to par with my channels' standards, so I can't use it for my TAS. If you guys can't program said suggestion for whatever reason, can someone direct me to the last version of Dolphin where the codec is able to be chosen? Hopefully my 5.0 movie syncs, if need be.
Yeah, I saw the above notes and was hoping for more answers since this method that users are now stuck with is extremely inconvenient for multiple reasons that I would argue outweigh what was written.
That's understandable. Unfortunately I'm not that familiar with the details.
sonicpacker wrote:
Is there some way for devs to make Lagarith an option within the menu, similar to the current lossless codec?.
FFmpeg doesn't support encoding Lagarith, so I don't think it's especially simple.
sonicpacker wrote:
If you guys can't program said suggestion for whatever reason, can someone direct me to the last version of Dolphin where the codec is able to be chosen? Hopefully my 5.0 movie syncs, if need be.
I really wish we had a better description of the change than that one I wrote up here... Unfortunately the change never made it into a Dolphin progress report. Fog, do you have anything to add to what I said?
Not really, that seems to have summed up everything.
Porting the VFW stuff into 5.0 would not work straight on, as there are some additional changes which need to be accounted for.
Perhaps I can revisit VFW to see what can be done. My most recent encode of 007 Agent Under Fire originally used VFW, and I found that adjusting the framerate to 59.94 FPS made it sync up. Perhaps there is something missing in the original implementation?
5.0-97 - Split Video Dumps on Resolution Change (PR #3930)
5.0-99 - Split Audio Dumps on Sample Rate Changes (PR #3891)
Thank you, but no thank you.
There is there a possibility that Dolphin has an option to choose whether we want it or not split?
I have tested the r-5.0-213 today.
As shown in the screens below, video of 9m01s over 200 parts, some of which are useless, I tried with several editing software.
If it is not possible to have an option for that, so I come back to a previous version until this is the case.
