VEGAS Pro 16 Update 3 (build 352) - General Discussion

D7K wrote on 12/21/2018, 1:09 PM

Thanks for the continued development.

Mweb wrote on 12/21/2018, 7:58 PM

I'm soooo happy that this fixes some of the audio sync issues with VFR recordings. Although, with the so4compoundplug.dll, the "building peeks" bug is still there and has been there since at least Vegas 14. I'd love to see this fixed. It happens often with multi-track clips, for example, clips created by Nvidia Shadowplay

NickHope wrote on 12/21/2018, 10:09 PM

I'm soooo happy that this fixes some of the audio sync issues with VFR recordings. Although, with the so4compoundplug.dll, the "building peeks" bug is still there and has been there since at least Vegas 14. I'd love to see this fixed. It happens often with multi-track clips, for example, clips created by Nvidia Shadowplay

@Mweb What exactly happens?

3d87c4 wrote on 12/21/2018, 10:24 PM

Just installed build 352: little planet is the only 360 fx available. When I loaded a 360 project I edited with V13 & V16 307 I got error messages to the effect the reorient isn't installed. I've never seen the 360 stabilization---is this new to build 352?

Windows 7, 64 bit, 32GB ram with an NVIDIA GeForce GTX 660 Ti GPU

I'll be here for a few hours, then will be away from computer 'til Sunday, d'oh! Please comment and I'll follow up then.

NickHope wrote on 12/21/2018, 10:33 PM

@3d87c4 See this comment and the few following it. It's probably because of that new OpenCL-blacklisting feature.

3d87c4 wrote on 12/21/2018, 10:37 PM

Thanks, Nick, I noticed that...but thought (hoped) it was only relevant to the Intel GPU's. Is my only recourse, at this time, to uninstall V16 and re-install build 307?

It's a shame they disabled fx that were actually working...

Still wondering about 360 stabilize...was that in build 307?

NickHope wrote on 12/21/2018, 11:00 PM

Thanks, Nick, I noticed that...but thought (hoped) it was only relevant to the Intel GPU's. Is my only recourse, at this time, to uninstall V16 and re-install build 307?

@3d87c4 Based on that discussion, I fear that it might be. I suppose you could experiment with different GPU drivers. Please put in a Support Request anyway, and let us know what they say.

Were those disabled FX working OK for you before?

I'm starting to wonder if this new OpenCL compatibility test is a bad idea, or too aggressive, if it's disabling plugins that were working OK in previous versions. A strong compatibility warning rather than total disabling of a plugin might have been more prudent.

Still wondering about 360 stabilize...was that in build 307?

It was new in build 307. It's the last item in the "new features" section of the release notes. This comment implies that it must have been in there, since he was missing that FX in build 416 (presumably due to this new OpenCL blacklist).

3d87c4 wrote on 12/21/2018, 11:06 PM

Yes, scene rotation, dual-fisheye stitching, and little planet all seemed to work OK. I never saw 360 Stabilze, and apparently missed it in the new feature list.

I have the Boris VR unit, and just bought Mocha. Is it possible these conflict with the Magix fx?

I have submitted a service request & have a support ticket.

NickHope wrote on 12/21/2018, 11:59 PM

I have the Boris VR unit, and just bought Mocha. Is it possible these conflict with the Magix fx?

I doubt it. More likely a false positive from this new test.

GerY wrote on 12/22/2018, 12:19 AM

I can't save my "VEGAS Dual Fish Eye Stitching" settings. Some one has a solution?😳

Dimitrios wrote on 12/22/2018, 12:43 AM

@3d87c4 See this comment and the few following it. It's probably because of that new OpenCL-blacklisting feature.

It's funny when new features disable old features that people use heavily. So too aggressive like you said, using a hatchet instead of a scalpel. Reminds me when ps3 had a new update that disabled linux. It's a new feature.

fr0sty wrote on 12/22/2018, 2:45 AM

^PS3's Linux was removed because it gave hackers a back door into installing custom firmware that could be used for piracy, so not exactly an apples to apples comparison, but I digress.

I too agree that it should flag a warning instead, and maybe also prompt the user to save their progress before continuing, that way if it does crash, they have a good idea why it did and don't lose any work.

j-v wrote on 12/22/2018, 5:28 AM

I can't save my "VEGAS Dual Fish Eye Stitching" settings. Some one has a solution?😳

@GerY
I am able to save my changes as presets, but if I want to execute this preset somewhere else or on the same event where before the FX was deleted, it always shows the same default original programsetting for all the presets I made.
If you did mean that, I believe this is a bug in the program I saw not before your message because I never use that kind of stuff.

Mweb wrote on 12/22/2018, 6:22 AM

I'm soooo happy that this fixes some of the audio sync issues with VFR recordings. Although, with the so4compoundplug.dll, the "building peeks" bug is still there and has been there since at least Vegas 14. I'd love to see this fixed. It happens often with multi-track clips, for example, clips created by Nvidia Shadowplay

@Mweb What exactly happens?

Well, it doesn't happen with all clips recorded with Shadowplay, but it does on some. I import a clip and it's stuck "Building Peaks". The usual workaround after researching is usually disabling so4compoundplug.dll and compoundplug.dll, but that also introduces its own problems. I have to manually convert the clip twice (one with each audio track) and then import the files to edit it.

Former user wrote on 12/22/2018, 11:39 AM

Getting trouble with 352...

Renders ok but the preview is shot.

Former user wrote on 12/22/2018, 6:58 PM

Don't know if Intel HD Graphics 520 would be same, I think it shares same driver as 530 does.

On my notebook with Intel 520 and driver version (updated to this version a few days before) these FX appear and work fine (in the way they do not crash nor freeze Vegas Pro 16 build 352).
I tested with "Vegas 360° Video Stabilize" and a bunch of the Ignite Pro plug-ins like "Chroma Key", "Skin Retouche", "Cine Style", "Bleach Bypass", "Denoise". Also the Vegas integrated HitFilm FX like "Vibrance", "Witness Protection", "Three Strip Color" work fine.

So it seems like with Intel HD Graphics 520 and driver version there is no problem with all these plug-ins mentioned.

@Marco. FWIW I found that 444 driver slowed down renders, I had to go back to the previous Intel driver, but while it was faster it doesn’t allow Intel HW acc. option. This wasn’t important to me as I use Nvidia for this. Details on page 2 of this thread, I was using Intel graphics 630. That was with vp16 b307.

Update: I just tested VP16 b352 with the latest Intel Graphics driver … 25.20.100.6471 and no improvement, actually got a BSOD. The "faster" previous driver was Intel Graphics driver 6373, I've now reverted back again to this driver.

https://www.vegascreativesoftware.info/us/forum/intel-i9-9900k-processor-review-using-vegas-pro--113429/?page=2

I noticed that the “driver version” info. in your original post is not carried over in the quoted copy?

cyvideo wrote on 12/22/2018, 8:43 PM

Getting trouble with 352...

Renders ok but the preview is shot.

Exactly, destroyed preview. Win 10 8700k OC'd to 5GHz with GTX 1080 Ti. On this box with v15 build 461 I can play an S-LOG 3 1080 50p timeline with 3D LUts and grades at Best/Full at the full 50 FPs.with around 25-27% CPU usage. Perfect in other words. With v16 b 352 the exact same timeline staggers at around 25-30 Fps with CPU usage running at anywhere where between 96-100% CPU. Don't know what has happened but I had to go back to v15 b461.

v16 b 307 has the issue where any legacy text on the timeline shows up in Project Media with random icons such as .AVI. If I change file associations in MPC-HC player then the Project Media Legacy Text icons can change to some other type of icon. This was fixed in b352 but sadly the playback issue is a major one. Have notified the Beta team of this. Hopefully hear something fresh in the New Year.

NickHope wrote on 12/22/2018, 10:40 PM

Getting trouble with 352...

Renders ok but the preview is shot.

@Former user Please provide more information, especially about your media format: https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/ Might be better if you do this in a new post.

Former user wrote on 12/23/2018, 4:11 AM

Getting trouble with 352...

Renders ok but the preview is shot.

@Former user Please provide more information, especially about your media format: https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/ Might be better if you do this in a new post.

Thanks, it’s GoPro 1080 as can be seen in the shot.

NickHope wrote on 12/23/2018, 4:46 AM

@Former user I just tried AVC from the GoPro HERO5 & 6 and the preview is fine. It's probably GPU-related. If you want help troubleshooting that, please start a new post and provide more information as detailed in this post: https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

David-Fairweather wrote on 12/23/2018, 5:34 PM

Import media dont have variant *.mp3 and after import mp3 as all files music is screech

I have the same issue with mp3 files dropped on the timeline. I just get a digital screeching also. I have reverted back to VP15 and no problems at all.

k.miroslav wrote on 12/24/2018, 6:10 AM

Problem with mp3 appeared at build 352 - build 307 is OK

bitman wrote on 12/25/2018, 12:35 AM

Import media dont have variant *.mp3 and after import mp3 as all files music is screech

I have the same issue with mp3 files dropped on the timeline. I just get a digital screeching also. I have reverted back to VP15 and no problems at all.

@k.miroslav and @David-Fairweather

Works fine on my system, no problems here. Tried on stereo project and 5.1 project. Also the import variant *.mp3 is working, you can select it. See my signature for system details.

rkm82 wrote on 12/25/2018, 2:39 PM

I am currently having MAJOR issues with this build. There is a project that I'm working on that I can hardly run with it crashing every few minutes. It's a massive pain in the ass. Very unhappy.

Happy to share more details about system and project if someone from Magix wants to look into that.