![]() ![]() Not much difference in the images (all 1.4-1.6 MB each). However, today- I tried to render a similar video with different content- totaling about 2:15 in run time- but now it's taking 18-20 minutes to render. This was within a very acceptable time frame for me. ![]() ![]() Yesterday, I rendered the video- which ran about 3 minutes- and the render was done in about 3 minutes. Some days, there may be 25 images, other days as many as 60- so the video will run up to about 3 minutes long. Essentially, the video is nothing more than a series of still images at 3 seconds each. I have a video which I update every day for our business to run on our lobby displays. I'm confused by what's happening with ME and PR. This needs to be fixed (or any solution) fast. So currently exporting with Adobe PP/AE/AME is impossible for me. Doing that with direct export would block me heavily. Looks like a bug for me - sadly exporting direct export from PP is not an option as I have multiple files and multiple targets to render, which I normally queue up over the day and then let run overnight. For me that means 100MB/s no matter if I export 1 or the usual 3 targets for my projects in parallel - except that the 3 parallels are coming to a near stand still after around 90seconds, with 1 target after around 10-15min. Thank god it's only reading, not writing at that speed. It feels a little that AME starts reading the source-file for every frame from the beginning, that way it starts ok and then quite fast slows down to nearly stand and finally crashes. I observed that the AME since last update excessively is reading the source-file (I mean excessively, infinite reading at full speed, whatever the HD is giving, without any sense - even when AME is paused). yeah you guess never ending, counting app and finally crashing AME. I have the same problem, went from a 3hr rendering to. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |