![]() ![]() only.Īnd about 64-bit hardware: no, I was mentioning 32-bit capable machines ONLY - of course, and as I've tested 64-bit ones: successfully (always). may be the 1st thing I should have tested: x264 command line version - which I did, LONG ago, with no problem, on even older PCs (!), but on short vids. That's why I tested x264: VfW version, thru "VirtualDub" => AVI avc files, that ADM easily "re-contains" to. I haven't forgotten that ADM uses its own codecs exclusively I wonder if anyone has encountered the same problem and, of course, may be found some solution.Īnd in short before further testing *, well. It doesn't happen on few seconds test vids., but as soon as they exceed that short a duration, such as long footage, & also beyond one of a few minutes only. While it's not too difficult to to, it requires to watch the WHOLE video VERY carefully, which is no less than tedious. In order to achieve a perfectly clean result, those few frames need to be replaced – therefore the whole (AVC) GOP. ![]() a 25th or 29.976th of a second, once in a while, comes out badly garbled! ![]() On XP ONLY, whatever ADM version is used, and I noticed this in 3 different PCs - + using FFmpeg alone just the same -: SOME images, i.e. 10 PC stays free for editing & other stuff. For instance, long AVC encodings often go to the XP machine – that will "grind" for hours if needed, so that the Win.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |