That must be why this has never worked for me. I am using 60 FPS in my projects - obviously I'll never have less than at least several hundred images in my sequences. Image size, resolution, number and total amount of data is typical for my use case - but it seems to be a lot more than in your own test scenarios! The images for this particular test are 4000x3000 pixel JPGs from a GoPro Hero 7, about 2-3MB each, the whole set would consist of ~1730 images and taking up close to 4 GB of disk space total - still nowhere near the available RAM on my machine (32GB). I now tested a little bit more, still on Windows 10, 64bit and I actually managed to get this working for 2 images, for around 30 images, and once even for a few hundred images - but never for much more than that (I tried about 10 times). The circumstances really weren't suggesting that this would be hard to reproduce at all - at least not with Windows 10, 64bit as I mentioned in my original report. Image sequences have actually NEVER worked for me in the last 18 months or so - and yes, I did the same thing on various machines, with images from different sources and so on. Plesase accept my apologies for wasting your time. I understand your frustration, and I'm well aware that you do all this for free and hardly ever get anythng in return. I will test on Windows 10 and macOS next. Otherwise, I have to keep trying many different ways and relay them only to receive feedback about yet another way I never even thought about. See all these combinations I tested? That is why steps are helpful. Make your 4K and HDR photos and videos look even better. I tested changing Properties of image in both Source and Timeline. Every video and photo can have new motion trails 3D LUTs & filters for quick color editing. For empty project, I tested Automatic Video Mode and 4K24. I tested both existing project and empty project. Not reproduced on Linux using one image sequence of 1716 4K JPEGs and another 26331 1280x720 PNGs.
0 Comments
Leave a Reply. |