V15 pan / crop still broken

Mindmatter wrote on 7/25/2018, 8:46 AM

Hi all,

I regularly run into the issue that what I do in the pan crop edit screen is not at all reflected in the preview, resulting in guesswork and black borders etc. This has been around since V12. It's also very frustrating that there is an absolutely absurd limit in reduction to make objects smaller. Why is there a limit at all??

I also feel that working in a larger project with lots of compositing going on, V15 becomes more and more slow and erratic, even on timeline moments where just one simple track is playing. As if it just became overheated by the hour...:)

 

AMD Ryzen 9 5900X, 12x 3.7 GHz
32 GB DDR4-3200 MHz (2x16GB), Dual-Channel
NVIDIA GeForce RTX 3070, 8GB GDDR6, HDMI, DP, studio drivers
ASUS PRIME B550M-K, AMD B550, AM4, mATX
7.1 (8-chanel) Surround-Sound, Digital Audio, onboard
Samsung 970 EVO Plus 250GB, NVMe M.2 PCIe x4 SSD
be quiet! System Power 9 700W CM, 80+ Bronze, modular
2x WD red 6TB
2x Samsung 2TB SSD

Comments

Marco. wrote on 7/27/2018, 4:46 AM

"I regularly run into the issue that what I do in the pan crop edit screen is not at all reflected in the preview"

Could you post a screenshot of what exactly happens?

"It's also very frustrating that there is an absolutely absurd limit in reduction to make objects smaller. Why is there a limit at all??"

This is because the concept behind Pan/Crop works vice versa. It does not reduce the size of the video frame but it does enlarge the size of the workspace in which the video frame is placed in. Thus it multiplies the data calculated.

Pan/Crop just isn't the right tool to reduce the size of video frames. I'd only use it for cropping and panning (like its name says). If Track Motion isn't comfortable to use for reducing frame sizes, the new Picture in Picture FX should serve you well. While the scale slider won't allow to get smaller than a scale of 0.1, you could easily type in any smaller value down to 0.001.

Mindmatter wrote on 7/29/2018, 8:39 AM

hey Marco,

well these kind of things happen.

sometimes the whole pan/crop function goes totally haywire. Butons don't react anymore, the cropped object looks split or half etc. the actual action that you do works when the window is closed, such as the object moving entirely from out of the screen to out of the screen on the other side, but what you see ion the window is something totally different.It would then just stay put in the middle or so, like in the screenshot. A restart usually fixes it, but not always.

Another issue at track level is that the 2D glow suddenly won't react to the color slider anymore.

On a sidenote, could Magix pleaaase change the button color in the track when track motion is active? from blue to slightly different blue isn't really useful.

Thanks!

AMD Ryzen 9 5900X, 12x 3.7 GHz
32 GB DDR4-3200 MHz (2x16GB), Dual-Channel
NVIDIA GeForce RTX 3070, 8GB GDDR6, HDMI, DP, studio drivers
ASUS PRIME B550M-K, AMD B550, AM4, mATX
7.1 (8-chanel) Surround-Sound, Digital Audio, onboard
Samsung 970 EVO Plus 250GB, NVMe M.2 PCIe x4 SSD
be quiet! System Power 9 700W CM, 80+ Bronze, modular
2x WD red 6TB
2x Samsung 2TB SSD

Marco. wrote on 7/29/2018, 9:05 AM

Not sure about the cause of what your screenshot shows, but I see there are two keyframes used to animate Pan/Crop and while in the Pan/Crop workspace you're on the very last keyframe (4 minutes and 18 sec), the video preview shows something from the beginning of the video (about 16 sec).
Your Pan/Crop tool isn't set to be synchronized with the main timeline, so the timeline preview and the Pan/Crop workspace can't match.