![]() It's even - more or less - the case with "AviDemux", but: for the VIDEO stream only, not the audio. And THEN drop your file to its face it won't complain, neither malfunction. In fact and against the most obvious logic, with "VirtualDub", you can even pick an output codec without opening (or having dropped) any video in the 1st place. to finally drop ANOTHER one on "VD", settings are maintained. ![]() If you open a video to "VD", then set all kinds of stuff: codec choice, compression level, and even certain filters - and then close that video. It's - somehow - the case with " VirtualDub" (among other tools): may be due to the fact that some programs do (precisely) let the user set certain parameters BEFORE loading (dropping) a video to their interface. (.) Why should you have even thought that AviDemux would be different ? One thing that strikes me from the above is the notion of editing something BEFORE you have loaded that something. Not the case with old 2.5.x versions and 64-bit versions, neither until 2.6.1 or 2.6.3 32-bit versions. Unaware of that bug, you first believe that your AviDemux version is not able to append, anymore. If you want to append more videos by drag'n'drop, or even if you closed that 1st one without quitting AviDemux, any next video must be dropped ON THE TITLE header or ribbon (top of window), NOT anywhere on the interface. With the 32-bit versions of AviDemux, starting from 2.6.3 or 2.6.7 (I forgot), up to 2.6.8, on AviDemux general window / interface, you can only drop: your FIRST video. If I prepare a script with any audio CODEC preset, then, same problem: the user HAS to RE-select the (same) audio codec, eventhough it LOOKS perfectly active.Īnd that one is typically a bug. AS LONG AS, in my "project script", the audio is set to: "Copy"! Next, they (simply) have to close my dummy clip, and drop THEIR video to AviDemux. And it HAS to be mine, since I don't know the file name of the video they'll want to proceed. So: opening a "project script" necessarily opens a video. Therefore, to provide friends with some scripts, I add "dummy" (very short) videos, to the same folder as of the scripts. It means that to record, and later, to launch one of those (".py") scripts, you NEED the video that was used to build it. They are not independent: they rely on a video * Another reason why the programmers should rework this, is. At least, users would SEE something happening, changing. When the user drops a video to the interface, whatever audio codec was (already) selected, AviDemux should highlight the audio field in red + empty it. Plus, I usually set all output parameters AFTER * opening a video anyway.īut: knowing that many users just don't configure their audio, AviDemux programmers should really modify that - or at least warn somehow. So, the fact that nothing happens on clicking "Configure" is a warning, of course. I doesn't happen to me often, since I (almost) always need to modify or at least check the audio config. Now, if you forget that, altough the interface displays the audio codec you chose, AviDemux direct streams (simply copies) the audio, instead of converting. Or not even, if you don't care to set them. Once that done, you CAN finally configure the audio parameters (sampling rate etc.). until you (realize you HAVE to) select - AGAIN - the audio format (codec) you want.īecause, since the interface displays the codec you chose in the first place, you naturally believe that it's active / going to work. When you set the output parameters FIRST, and THEN drop a video on AviDemux, if you try to click the "Configure" button under "Audio output", no config. and you just pointed one more (out of quite a few!), of the strange or unexpected behaviors of AviDemux! One that I'm used to, but still tend to forget.Īnd that turns out to be a nasty little trap: many users, newbies above all, might wonder for hours - or days. Net Development Test version here), but that's just my own favorite with a good balance of control if needed and good presets. I prefer Handbrake for that (there is an actively maintained. There are a some tools for that with different level of complexity or control. ![]() If you need a special video-/audio-format, you may have to do a complete recompression (slow). A good and simple tool for that could be AVIDemux, because it can simply copy tracks from MKV to AVI or MP4 without a new encoding (very fast). In such a case you need to switch the container from MKV to MP4 but don't need to recompress. MP4-files containing the same tracks should be no problem. Apple iTunes does not accept MKV-files anymore regardless of the encoding. ![]() Just an example: MKV-files often use H.264 (or H265 lately) encoded video-tracks and mp3, acc or ac3 audio. ![]() What can be played depends on the capabilities of your desired device. Both MKV- and AVI-files are just containers that can contain many different video and audio formats. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |