The only Adobe people who might see this are in Product Support, and not on the development teams. These are provided as user-to-user forums ... again, with some monitoring from Product Support.
As to how something works on different software ... part of that depends on the total "load" ... and the type of load ... that different programs put on the system. PrPro puts a ton more load in several places than say Elements does. Folks are always saying that as something plays on VLC without stuttering, it should play back on PrPro without stuttering. Except they totally miscalculate things ... VLC is just playing one file.
In PrPro they've got 38 files put together in bits & pieces, so the program has to hunt them down, grab the appropriate frames from all the different files ... then add some graphics work ... time-ramp this section, re-size here, there, and there ... throw in some complicated color corrections ... different on each clip, of course ... and the complaint is that PrPro can't playback a file as well as VLC. Well, it's apples to planets. Duh! Even if it's only one file, PrPro has the system setup for a much bigger workload.
I've used PrPro since CS6 ... and imported quite a number of long mp4 files, up to an hour or more, without issue. Win7, now Win10. And if it were very widespread through the user-base, there'd be a lot more posts here about it. Which leads me to conclude it happens on a few systems, but not most.
Which could be either a typical "bug" ... or something about specific user setups/practices/media. And of course, I've no way of knowing personally. So ... I lean toward a "bug", if not a wide-spread one. And being as you've tested this with files encoded into H.264/mp4 via AME, that rules out say a camera doing intriguing things to the compression settings (as the GH5 is doing). Again, seems to support this being a bug.
So ... having your OS/CPU/RAM/GPU/vRAM, and the number/type/connection of discs you're using to work your projects would be very useful data. Long-GOP media is always harder on the system than the intraframes such as Cineform, DNxHD/R, and ProRes.
And as you mentioned proxies (the new system in general works quite well) one caveat there ... it isn't file-size you want smaller, it's the compression type you want to choose to make the proxies work best. H.264 and mp4 are NOT the better choices ... as they always require more work of the CPU and RAM ... cores/threads ... than the intraframes. Intraframes take more space on disc, but edit vastly better. So pick one in say 1/2 or 1/4 the frame-size of the original media for best results.
Let's puzzle out your system, and maybe if another user or two comes on with this problem, and see if a workaround or different approach can ameliorate or banish the problem. And of course, filing bug reports is always good. They don't respond, but all the reports filed get distributed to the upper management who determine engineering time budgets in some tabulated form.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Neil
10
Replies
AdChoices