There is a HUGE mistake disabeling the Mainconcept AVC codec. I can't figure out why MAGIX did that.... cannot find any reason for it. It is still the fastest one based on GPU rendering. and this is important! Not all CPU's support intel QSV.

Thankfully you can enable it again in the internal menu.

 

... a LUT OFX plugin that has been available and free for some time now, and Crop/PIP options that we kind of already had.

Is the Vegas 15 LUT plugin the same as the Vision Colour one that was mysteriously withdrawn a few months ago?

Also, I keep thinking I have missed something with the PIP and Crop plugin features. I was sure we had that and more from the normal track composition and transform tools. It sounds more like something for the Vegas cut down version (whatever it is called...)

There is a HUGE mistake disabeling the Mainconcept AVC codec. I can't figure out why MAGIX did that.... cannot find any reason for it. It is still the fastest one based on GPU rendering. and this is important! Not all CPU's support intel QSV.

Thankfully you can enable it again in the internal menu.

This is another 'new feature' that had confused me. I was sure that GPU acceleration was already a thing in Vegas. Perhaps they are letting the licence on that wind down as well, thus are phasing it out? 99% of my renders are done in the Mainconcept AVC Codec with GPU enabled.

There is a HUGE mistake disabeling the Mainconcept AVC codec. I can't figure out why MAGIX did that.... cannot find any reason for it. It is still the fastest one based on GPU rendering. and this is important! Not all CPU's support intel QSV.

Thankfully you can enable it again in the internal menu.

The MAGIX AVC encoder (the non-QSV and non-NVENC options) uses a newer version of the MainConcept AVC codec.

Old MainConcept AVC codec can be used in scripts (eg. standard Batch Render)

Old MainConcept AVC codec can be used in scripts (eg. standard Batch Render)

That is true. We've basically hidden the older codec in the render dialog as we consider it redundant.

There is a HUGE mistake disabeling the Mainconcept AVC codec. I can't figure out why MAGIX did that.... cannot find any reason for it. It is still the fastest one based on GPU rendering. and this is important! Not all CPU's support intel QSV.

Thankfully you can enable it again in the internal menu.

The MAGIX AVC encoder (the non-QSV and non-NVENC options) uses a newer version of the MainConcept AVC codec.

The older codec Mainconcep is very fast, MUCH faster that the Magix newer one. I don't have Intel QSV and i render about 5 times faster with the older codec. This is CRITICAL!

it shoud be activated as default because a LOT of us are using it all the time because on some non-QSV buids it works best.

Old MainConcept AVC codec can be used in scripts (eg. standard Batch Render)

That is true. We've basically hidden the older codec in the render dialog as we consider it redundant.

Are the improvements mainly in the render times with GPU and QSV support etc., or can we see any visual quality improvements in the encoding? Does QSV have much impact on visual quality? My experience with QSV in other applications is that it is mainly useful for live streaming/broadcasting applications where speed is critical. The quality is a bit ropey for DVD/Blu Rays.

Also, why doesen't the newer Mainconcept MAGIX AVC codec allow GPU rendering?

Also, why doesen't the newer Mainconcept MAGIX AVC codec allow GPU rendering?

I wonder if at present it just does not support your GPU. I guess the chances of it supporting the GPU in the future are slim given that it was already supported in the earlier version. I might be wrong, but are all of these problems with GPU compatibility down to the application still being VfW based? Would it be easy to take advantage of all graphics cards if it used Direct X?

Magix welcomes you to 2005.

I haven't installed VP15 yet, but there's nothing in the press release about adding support Panasonic's new UltraAVC codecs (well, new - it's been a while). So I'm guessing that's still not working?

It's working.

No, it's not. Just installed VP15 and none of the Panasonic Varicam files could be imported. It seems the scope of importable video files still hasn't changed...

AVCintra files from professional Panasonic products are not some kind of obscure format - and every other NLE out there supports this : http://pro-av.panasonic.net/en/avc-ultra/intra2k4k.html .

I do love working with Vegas Pro, but I (and many others) have been asking this for such a long time. Converting up front is an enormous hassle. If Vegas Pro still wants to be considered as one of the possible pro editing options, it should at least make this list. This is a letdown. Is support for Panasonic pro even planned?

I haven't installed VP15 yet, but there's nothing in the press release about adding support Panasonic's new UltraAVC codecs (well, new - it's been a while). So I'm guessing that's still not working?

It's working.

No, it's not. Just installed VP15 and none of the Panasonic Varicam files could be imported. It seems the scope of importable video files still hasn't changed...

AVCintra files from professional Panasonic products are not some kind of obscure format - and every other NLE out there supports this : http://pro-av.panasonic.net/en/avc-ultra/intra2k4k.html .

I do love working with Vegas Pro, but I (and many others) have been asking this for such a long time. Converting up front is an enormous hassle. If Vegas Pro still wants to be considered as one of the possible pro editing options, it should at least make this list. This is a letdown. Is support for Panasonic pro even planned?

 

Any downloadable sample media available on the internet ?

If you can share the AVCIntra small sample, hopefully that can help the developers.

I own a couple of GH5s. Vegas 15 supports 10bit 422, no problem.

What version of the Mercalli v4 plug in are you running?

You definitely need to have the OFX-files at the new Vp15 location. Best practice is to reinstall Mercalli after loading the actual version from your proDAD account.

Hi Peter_P .. The Mercalli that came with VP14 ... 4.4.0.471.1.

As I already mentioned I have re-installed it and it doesn't accept the serial number, it may be tied/limited to VP14. If anyone else has the same setup maybe they can confirm, thanks.

Maybe that is the difference: I have here the Mercalli Vegas plugin Version 4, that did not came with Vegas but that was purchased in addtion.

When I installed Vegas Pro 15, the plugin was recognized automatically - and I see it in Vegas Pro 15 too. The Version in 4.0.471.1 - so I assume identical. The plugin states that it is the latest one. BUT it was not necessary to re-install it again and it was not necessary to activate it.

The Installation file - if you start it what I did for test purposes only - offered also to install the plugin in Vegas 13/14/15 on my System.

I haven't installed VP15 yet, but there's nothing in the press release about adding support Panasonic's new UltraAVC codecs (well, new - it's been a while). So I'm guessing that's still not working?

It's working.

No, it's not. Just installed VP15 and none of the Panasonic Varicam files could be imported. It seems the scope of importable video files still hasn't changed...

AVCintra files from professional Panasonic products are not some kind of obscure format - and every other NLE out there supports this : http://pro-av.panasonic.net/en/avc-ultra/intra2k4k.html .

I do love working with Vegas Pro, but I (and many others) have been asking this for such a long time. Converting up front is an enormous hassle. If Vegas Pro still wants to be considered as one of the possible pro editing options, it should at least make this list. This is a letdown. Is support for Panasonic pro even planned?

 

Any downloadable sample media available on the internet ?

If you can share the AVCIntra small sample, hopefully that can help the developers.

Probably not on the internet, but I have offered before to supply sample clips in all formats if necessary. Anyhow, I can't see it as a problem to get the 'white pages' from Panasonic for Magix...

I own a couple of GH5s. Vegas 15 supports 10bit 422, no problem.

Yes, but that is 'normal' H264, out of the Panasonic AVCCAM range. Unfortunately the codecs from the pro & cinema products of Panasonic are not supported. I suspect the new EVA1 files will be working too for that reason.

I really love the new GUI design (prefer the middle grey setting which is just slightly darker than the old one) including the hamburger menus. To me this is more than just cosmetic - it is workflow improvement. It allows to let me have my individual set of buttons for trimmer, preview, tracks and events. And the new way the events are designed now finally allows for direct access to things like Pan/Crop or FX even if the tracks are minimized (a restriction which sometimes drove me nuts in the versions before).
 

After a couple of hiccups regarding Send2Handbrake not working initially (my fault) and the SeMW plugin crashing VP15 on start up (which has been resolved with today's announcement of a new version which works perfectly now) I'm finding the interface, layout tweaks, etc suits my needs perfectly. Others complaining about this and that and they're leaving to edit with another NLE indicates an unwillingness to see that this is the first version, which usually has issues initially. As the updates begin rolling out, we'll see improvements, and other under the hood tweaks that will make it the best version yet. For my multimedia storytelling projects (Both audio slide shows and video) and Small Business Profile videos I shoot, Vegas can't be beat for speed and quality.

There is a HUGE mistake disabeling the Mainconcept AVC codec. I can't figure out why MAGIX did that.... cannot find any reason for it. It is still the fastest one based on GPU rendering. and this is important! Not all CPU's support intel QSV.

Thankfully you can enable it again in the internal menu.

The MAGIX AVC encoder (the non-QSV and non-NVENC options) uses a newer version of the MainConcept AVC codec.

The older codec Mainconcep is very fast, MUCH faster that the Magix newer one. I don't have Intel QSV and i render about 5 times faster with the older codec. This is CRITICAL!

it shoud be activated as default because a LOT of us are using it all the time because on some non-QSV buids it works best.

@ iron-marin,

well, I did some render Tests with both Vegas Pro 14 and Vegas Pro 15. The source file was a UHD 50p XAVC-I Clip from my FS7 with a length of 7,2 seconds - and the PC is a 8 core machine. Has installed a Quadro K4200 but also a AMD R9 390X.

Following results:

a) Vegas Pro 14

Rendering with the Mainconcept AVC encoder

- CPU only: 0:47 minutes

- Open Cl: 0:46

- CUDA: 0:46 (Cuda is shown as available)

Fazit: no difference at all!

b) Vegas Pro 15

Rendering with the new Magix AVC/AAC MP4 encoder

- NV Encoder - Default: 0:29 minutes

- NV Encoder - high Performance: 0:21

- NV Encoder - high Quality: 0:32

- Mainconcept Settings: 1:04 minutes

Fazit:

- true, the new Encoder is slower (1:04 versus 0:46 minutes, so +40%) if you use the MC Settings. But here not for 5 times.

- but using NVENC even with my weak Quadro K4000, that is much much faster (-55% if one uses the high Performance mode - so that is much faster).

What GPU do you use?

Can anyone confirm the GH5 10-bit files are working? That would be awesome...

Also does the LUT plugin allow adjustment of strength/level? (Other than copying a layer and decreasing opacity of the above level)

If both of those are in place I may move back to Vegas. Thanks,

Can anyone confirm the GH5 10-bit files are working? That would be awesome...

Also does the LUT plugin allow adjustment of strength/level? (Other than copying a layer and decreasing opacity of the above level)

If both of those are in place I may move back to Vegas. Thanks,

Yes, GH5 10-bit files are working....

and the LUT have a strength slider.