![]() in fact, I'm afraid it's already too long. Again, I don't think it would be a good idea to duplicate this in the Quickstart introduction, which should be really short and simple, otherwise nobody would bother reading it. Also, which container formats can be readily swapped with another/others?The section links to the Output formats article with its table of supported audio/video formats in different containers. Quote- Finally, maybe a chart showing which container formats can hold which video & audio types (and ones they canââ,¬â,¢t), & maybe ones typically found too. QuoteShould the ââ,¬Å"container formatââ,¬Â be the 1st term explained before the rest?OK, done. On the other hand, I'm afraid of losing the readers' interest when the Quickstart guide for Avidemux begins with some boring general terminology instead of saying something about Avidemux. I was thinking about it, too, and I agree it should be the first thing the users should learn before using Avidemux. QuoteWould the basic terms be better at the beginning?Perhaps. QuoteAn interface image would be a touch too, perhaps with red numbers on it that people can reference too from your text?Maybe, but we already have the User interface/Main window article, and it may not be the best idea to duplicate too many things. This has been the most requested feature for Avidemux in the last couple of years.) ![]() (Still, I think it would be better if users would not have to add these extensions manually. QuotePerhaps you could also mention that when saving your file you have to manually add the file extension yourself?OK, added. In this case, retiming this run shows the run to be faster by that margin than it actually took.Quote from: djboshh on March 16, 2012, 11:14:45 PM- Thereââ,¬â,¢s a spelling mistake in the basic terms section: "automagically"Actually, that's not a mistake. ![]() This can be seen in this run of the game Burnstar, where about 3/4 of a second got dropped from the recording, and the video skips ahead. If the recording dropped enough to lose both video and audio data, it's possible for this method to be inaccurate. Media Player Classic, for example, does not have accurate frame timing, and could give different results on different retimings. This should match the Selection length given by AviDemux.Įditing software is the best method for making sure the retime is accurate. If you subtract the times, you get your final time for the run - in this example, 00:44:54.953. Write down this frame's timestamp as well - in this example, 00:45:11.025 - or in AviDemux press "Set Marker B". The frame where Samus is facing forward is the last frame of the run. Next, scroll near the end of the run, and find the last frame before Samus faces forward on the ship, and then the first frame she does. Write down the timestamp of this frame - in this case, 00:00:16.072 - or in AviDemux press "Set Marker A". The second frame (where the missile disappears) is the first frame of the run. You should find two frames - the last frame where the missile icon appears, and then the first frame where it disappears. When you get close, you can use Left and Right to move one frame at a time. You can drag the slider, or you can use Up and Down to move one keyframe at a time. Open up your file, and skip ahead until you're near the start of your run. I've heard of people using VirtualDub, but I use Avidemux, and that is what these instructions will use. Using video editing software, you can get an accurate time for your run. Let's say you finish a run, and you end up with a time of 1:00:00.05, and you're wondering if you actually hit sub-hour, but were just slightly off on hitting your timer button.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |