V17 full of bugs, crashing, rendering impossible, scrambling data

walter-born wrote on 8/18/2019, 7:11 AM

I spent 4 hours today assembling a small clip of roughly 3 minutes for my wifes Kindergarten summer activity
Input material:
4K DJI Osmo Video, Mavic Pro 2 footage, Iphone XSMax footage and images.
Creatad a sub timeline for getting a small picture show in line with music.
Imported music created with Cubase.
I generally did colourgrading on every track separately.
Only in one track I also modified lights on a dark indoor footage.
What I got after rendering the half way finished thing is a stuttering and faulty clip in the area where I modified colourgrading as above. I got black footage as well and the subclip with the pictures is completely unusable.
Not to mention countless crashes.
That really destroyed my enthusiasm.
Anybody else similar problems?
I uploaded the so far gotten result in 4K here for those who are masochist enough to have a look.

(Will maybe take some minutes until youtube finished upload.)

The project is not overly complex:

Back to post

Comments

Dexcon wrote on 8/20/2019, 6:07 AM

In the german forum I got the info that templates created with V16 opened by V17 lead to memory overflow and crashing

@walter-born … If you're meaning 'projects' (.veg) when referring to 'templates', was there any workaround suggestion on the German forum to create a brand new project in VP17 and then copy/paste the video and audio events from VP16 across to VP17? - even though this would mean re-coding any track level and above FX as well as Media FX and possibly some other FX like Magic Bullet Looks.

The current large project (2.25 hrs long) I'm nearing completion on didn't work all that well in VP17, so I'm finishing it in VP16. The next half-completed large project (which needs to be cut down to 1 hour) has been created in VP16, but I might try the copy/paste approach in a newly created VP17 .veg file to see if that helps. But a VP17 update may well have been released by the time I need to seriously work on the second project.

Former user wrote on 8/20/2019, 6:11 AM

@walter-born It’s not really that difficult, MagicYuv, but the Magix intermediate 422 flavours are built in and ready to go. The 422 HQ is of very high quality.

While trying many different things, its easy to make a mistake, so make certain that in the File I/O tab that you do have it as was posted earlier, i.e. checked and enabled for Nvidia. Also that you have HW Acc. enabled with Nvidia.

walter-born wrote on 8/20/2019, 6:29 AM

In the german forum I got the info that templates created with V16 opened by V17 lead to memory overflow and crashing

@walter-born … If you're meaning 'projects' (.veg) when referring to 'templates', was there any workaround suggestion on the German forum to create a brand new project in

No workaround offered by Magix programmer, but as my template(veg) is not very complicated, I can easily recreate one in V17. In the same time I would say that the same problems might occur when opening a V16 project in V17, as this is practically the same procedure then.

You say then I should simply batch render everything to Magix intermediate 422 HQ and then go ahead editing. Just have to find out now then how to batch render... and all my probs are gone :)

Former user wrote on 8/20/2019, 6:36 AM

@walter-born No, I would only render out the iPhone material. Under tools scripting theres a batch render script, just mark out in regions the multiple different iPhone clips on your timeline.

Former user wrote on 8/20/2019, 6:49 AM

@walter-born You can use this script also, created by another forum user, cannot remember who. I tested it on VP17. "Batch Render, with region name as filename, [14, 15 and 16].cs"

The readme.txt covers other stuff but shows location where to copy the script to, just change the VPnn location.

https://www.dropbox.com/sh/npz07r49ndu6mc3/AADMlMWbgPmvhTzZXgfKBMxva?dl=0

set wrote on 8/20/2019, 7:11 AM

I did not like Proxies in V16 already.
Do you use ultimate s pro to convert footage to Magix Intermediate before putting it on a timeline?

That is what I understand. Same with Vegasaur then I guess?

https://vegasaur.com/transcoder

I never tried Vegasaur, but from what I read, it is very similar to Ultimate S Pro's Render tab:

Render : Render the current project or multiple files or projects in batch mode. Render entire timeline, just a Selection, or Regions or Markers. Create reusable mutli-target render presets to apply to any number of files. Swap Media of any type with any other types effortlessly.

I discovered VASST Ultimate S Pro first time before Vegasaur, and still using it until today - so it's quite difficult currently for me to change or the necessity to invest Vegasaur - although it seems lately Vegasaur is more interesting than Ultimate S Pro.

Wolfgang S. wrote on 8/20/2019, 7:33 AM

In the german forum I got the info that templates created with V16 opened by V17 lead to memory overflow and crashing

@walter-born … If you're meaning 'projects' (.veg) when referring to 'templates', was there any workaround suggestion on the German forum to create a brand new project in

No workaround offered by Magix programmer, but as my template(veg) is not very complicated, I can easily recreate one in V17.

Are we talking about projects or templates?

More, why not show the mediainfo of your different footage types?

walter-born wrote on 8/20/2019, 9:08 AM

We are talking of an empty project, where I setup separate tracks for separate kind of media and purpose with FX setup different for different tracks.
I am already out of home since sevaral hours on the way to vacation and cannot show any mediainfo as I am not on that machine for 2 weeks :)

set wrote on 8/20/2019, 9:30 AM

Have a good vacation :)

fr0sty wrote on 8/20/2019, 9:51 AM

If you want to convert batch files to a format that plays nice with Vegas, you're best off using Happy Otter Scripts' import assist from tools4vegas.com