[George Dean]

Hi Francois,

Usually I’m the one pulling up the rear!!!

Best Regards……George

[George Dean]

Hi Robert, have you tried turning your GPU to ‘Off’ in Preferences > Video tab, ‘GPU acceleration of video processing’. It sounds like your GPU is struggling with the combination of effects. You could also, if you haven’t already render with CPU only. If either of these work, could your system updated your GPU driver? Rolling back the GPU driver is another test, if you are not sure.

Best Regards……George

[George Dean]

Hi Joseph,

That seems like a really strange issue. Nothing popup from my pea brain. Obviously something has changed as you point out. The only alternatives I’m aware of is to either reinstall the frameserver routine or perhaps try Happy Otter Scripts depending on the reason you are frame serving.

Best Regards……George

[George Dean]

Hi Linda,

After you have tried Ole’s suggestion……

How much available space do you have on the drive you are rendering to? And have you tried another render to that drive after you received the error about the Mainconcept?

You were able to render to Mainconcept on your old computer, correct? This would appear there is a difference between the two computers that is causing the issue. I doubt the GPU is causing this issue, but stranger things have been caused by GPU’s and if so, then Ole’s suggestion should then produce some results.

What OS system are you running on this new system. It probably is 64 bit, so you did install the 64 bit version of Vegas Pro 11, correct? Actually I started with Vegas Pro 12, so I’m not familiar if version 11 offered 64 bit.

Are you rendering the other formats to the same drive as the Mainconcept? In other words, do you have write permissions for that drive folder?

Best Regards……George

[George Dean]

Hi Bill, I’m sure Stewart will add his wisdom and thoughts, but I thought I would barge in with mine in the meantime.

You will always be able to get support here at the COW although when a new version comes out, if your question is specific to that new version getting answers will depend on how many users here have upgraded to that new version.

Magix is on it’s 3rd upgrade to both Movie Studio and Vegas Pro, so I think they are settled in and making the best of a product that for so long Sony ignored. With that said, there are always some hiccups to a new release and I doubt Magix Vegas Movie Studio 16 will be any different. Hopefully the issues will be few and worked out quickly with follow-up updates (which Magix has been pretty good about).

The good thing is, if you install the just released version 16, your older version can remain for you to fall back on*. I don’t use Movie Studio anymore, rather DaVinci Resolve and I tinker with Vegas Pro. However I do have Movie Studio 15 installed to assist friends who use it and will be upgrading to version 16 later this week just to keep up with the latest.

* Just to be clear in the event you are not familiar, each succeeding version can use the preceding version projects (not withstanding some special FX, Plugin or Extension that was purchased solely for the previous version), but previous versions cannot recognize succeeding version projects. So you could open your version 13 projects in version 16, but version 13 will not recognize version 16 projects.

Best Regards……George

[George Dean]

Good to hear evreything is working out Darren. There is a learning curve, but it will probably pickup and go quickly. But every once in a while we stumble on something that takes a lot of time to work out, so don’t hesitate to rattle our chain in the future if you need us, and as time goes on, you will get to the point you can pass on tricks and methods to us.

Best Regards……George

[George Dean]

Hi Paul,

Thank You for the kinds words, and good catch. Yes, I always ‘disable resample’, and would suggest that Darren also make that change. I have a script that will run through all the timeline events and set them to ‘disable resample’, but cannot remember where I got it. It would probably worth looking at ‘Tools’ > ‘Scripting’ to see if it is listed.

Best Regards……George

[George Dean]

Hi Daren,

Paul has given you some excellent advice. This is what I think may make an improvement on your project, although not all will necessarily cure the 30 minute point blurs, and some of it the same as Paul has pointed out.

In project properties – Definitely go to 8 bit pixel format, there is nothing to gain in 32 bit floating for your project. If you are going to view this video on Youtube/internet or on a flat screen TV from a thumbdrive or home network, I would change the Field Order to ‘None – progressive’.

In Render As – Again as Paul suggest match the frame size to your original project ‘1920 x 1080’. Change the frame per second to also match your project at 25 PAL fps. I assume you are in Europe or a PAL country, however if you are in North America or Japan, change all the FPS setting from 25 PAL to 29.970 (NTSC) both in the Project Settings and in the Render Format Template. Also, I would change Render Format and use either Mainconcept AVC, or even better if you have an option for Sony AVC (I’m not familiar with version 9 but you should have those two options). A note below concerning Paul’s suggestion for sub-render section to MXF follows. Also, as you have it now uncheck ‘Allow source to adjust frame size’ and ‘Allow source to adjust frame rate’.

Mainconcept AVC and Sony AVC render formats will produce a file with a .mp4 extension. These do well for viewing on the internet, your computer, or a flat screen TV that does progressive. The only reason you would need interleave ‘upper field first’ field order is if you were going to put this on a DVD.

NOTE: A good practice is to always set the Project Properties to the source video media. However when doing a slideshow, which of course consist of all stills, the stills do not have video properties such as field order or frame rate, so they will work in just about any properties. In this case we are setting the Project Properties to best fit the delivery format.

There is a possibility that something, mostly likely a still or combination of stills, has caused some corruption in your project and it appears at that 30 minute mark. Breaking down your renders into sub-renders and using an intermediate render format, as Paul suggest, may lead to a complete success, or at least identifying a part of your project that may be causing some corruption. BTW, I would not render with AVCHD to do this rather use MXF as Paul suggest, as that will provide the least amount of quality loss. Then when you put all those prerenderd sections together for the final render I would switch to using Mainconcept AVC or Sony AVC. Both will provide great quality for viewing.

I hope all this helps rather than being confusing or misleading.

Best Regards……George

[George Dean]

Hi Pat,

Unfortunately I’m not familiar enough with Resolve to know if there is a setting. However I can tell you that it works fine for me. Edit, Color and Delivery I use the wheel to zoom in/out, and hold the wheel to move the image around within the window. In Fusion the movement works the same but I need to hold down the ‘Ctrl’ key to zoom in/out.

Windows 10 (1809)
AMD R9 390
Resolve 15.2.2

Best Regards……George

[George Dean]

Hi Darren,

Does the blur occur suddenly, or gradually? If it is suddenly I would suspect you have placed an FX on the track or project level. Although it could also be an FX that has been animated, but I would think you would have remembered doing that.

I would go to Preferences > Video tab and change ‘GPU acceleration of video processing’ to ‘Off’ and try another render, either full or as Paul suggest just a region past the 30 minute point.

Although probably not, it could be a heat issue.

Are your stills jpg, png, or tiff? Just curious it shouldn’t make any difference.

Also can you post here screenshots of your Project Properties and Render Format Template settings.

Best Regards……George