V18 brought back some old issues

Mindmatter wrote on 12/18/2020, 4:30 PM

Hi all,

just gave 18 a test run and did a part of a new multicam project on it.

What I noticed is that it runs noticeably slower in multicam mode than 17. 4 exports crashed V18 until I had to do the old trick...set ram to 0 and disable GPU. A few things seem still somewhat annoying, like when opening an FX panel, every submenu has to be opened and expanded again, as opposed to remembereing the view / state of last close opening pan crop windows opens them at the smallest size and have to be resized each time - quite time consuming. Setting the cursor at the end of an event also still makes for a black frame, very annoying for keyframe setting - I thought that had been resolved at some point?

I also ran into a strange issue on multicam track - after synching things and creating the track, as soon as I made the first cam change the track became pink and told me it was now off by a large number of frames. The weirdest thing is that this behaviour stopped when I stopped using the second preview monitor. Just very strange, never saw that before. Also, my render templates weren't what I had saved them to be. Without further looking, I rendered with my typical Magix AVC HD 16mb/s template only to see in the render that V18 had used CBR at the lowest possible bitrate, and that the template now only lets me check the CBR box and a H264 mode. the next render at 14mb/s looked really good though. That's all for now...no crashes so far.

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