The 1st bug:

No sound for *.M2TS files.

The last correct MVC-FileIO was version 17 build 284.

That means they didn't squint even one eye for such "small" things and these small things shall be carried...?

What do you mean by "no sound"?

Working fine here...

 

No sound for *.M2TS files.

That's Sony AVCHD?

I have no trouble editing this format...

I was looking forward to this. I thought final no more "levels" global video output FX that I keep forgetting to turn off before rendering. For me this is absolutely annoying and one reason I walked away from Vegas Pro.

Unfortunately 8 bit full level simply clips shadows/highlights and makes them unrecoverable.

All I want is

1. a preview window that shows the same levels as the exported video (without workarounds)
2. no unnecessary clipped shadows/highlights

I can't believe it's so hard to implement this. Complains about this has been ignored again and again by the Vegas team because it's a "pro" feature. The irony is that software most pros are using doesn't have that issue.

You sure you didn't set this wrong:

I didn't export because even in the preview window the shadows/highlights details are gone. It's not possible to recover them (by reducing gain for example). They are just clipped.

My complaint about 1 was that I need to set a global video level filter (preset: Studio RGB to Computer RGB) while editing to have the preview window show what the footage will actually look like.

The problem is when I forget to disable the levels filter before exporting, the final result will have wrong levels again. I've wasted hours of rendering time because of this.

It's absolutely frustrating that the preview window and final result don't look the same and we have to use these weird workarounds.

It's this kind m2ts files:

It's this kind m2ts files:

@Yelandkeil Using xmedia recode to copy your video stream and recode your Audio stream to AVC.

I was looking forward to this. I thought final no more "levels" global video output FX that I keep forgetting to turn off before rendering. For me this is absolutely annoying and one reason I walked away from Vegas Pro.

Unfortunately 8 bit full level simply clips shadows/highlights and makes them unrecoverable.

All I want is

1. a preview window that shows the same levels as the exported video (without workarounds)
2. no unnecessary clipped shadows/highlights

I can't believe it's so hard to implement this. Complains about this has been ignored again and again by the Vegas team because it's a "pro" feature. The irony is that software most pros are using doesn't have that issue.

You sure you didn't set this wrong:

I didn't export because even in the preview window the shadows/highlights details are gone. It's not possible to recover them (by reducing gain for example). They are just clipped.

My complaint about 1 was that I need to set a global video level filter (preset: Studio RGB to Computer RGB) while editing to have the preview window show what the footage will actually look like.

The problem is when I forget to disable the levels filter before exporting, the final result will have wrong levels again. I've wasted hours of rendering time because of this.

It's absolutely frustrating that the preview window and final result don't look the same and we have to use these weird workarounds.

 

Is your video in a .mov wraper?

It's this kind m2ts files:

And this is mine:

Working without problems.

Is your video in a .mov wraper?

It's this kind m2ts files:

And this is mine:

Working without problems.

It's an mts file from a Sony A7. I've had similar issues with action cam footage. This is a short sample directly from the cam:

https://mega.nz/file/SkskWCpD#pQ0bMf1eTAxS6rAwij0dudPl_Z_uYrQrVdvZfUtoW3A

Format                         : AVC
Format/Info                    : Advanced Video Codec
Format profile                 : High@L4
Format settings, CABAC         : Yes
Format settings, RefFrames     : 2 frames
Format settings, GOP           : M=1, N=6
Codec ID                       : 27
Bit rate mode                  : Variable
Color space                    : YUV

Really looking forward to the 8 bit full level project mode, which seems like the simplest thing. Can't tell you have many times I've forgot to change levels before rendering... and then having to rerender. Video noise reduction and audio noise reduction inside the program sound really nice too. I love the new color grading panel in 17, but it will be really nice to be able to move it. Can anyone comment on what/how logarithmic exposure works?

Is your video in a .mov wraper?

It's this kind m2ts files:

And this is mine:

Working without problems.

 

 

It's an mts file from a Sony A7. I've had similar issues with action cam footage. This is a short sample directly from the cam:

https://mega.nz/file/SkskWCpD#pQ0bMf1eTAxS6rAwij0dudPl_Z_uYrQrVdvZfUtoW3A

Format                         : AVC
Format/Info                    : Advanced Video Codec
Format profile                 : High@L4
Format settings, CABAC         : Yes
Format settings, RefFrames     : 2 frames
Format settings, GOP           : M=1, N=6
Codec ID                       : 27
Bit rate mode                  : Variable
Color space                    : YUV

Downloaded the clip. Imported. Sound is there...

Clip gets decoded using the compoundplug.dll.

So we finally get:

A comprehensive media management solution. Now when I'm editing... let's say a wedding... I can go through all my shots and tag them with "bride", "wedding party", "cake", etc. and easily pull those shots up as needed when editing with a quick search of those tags.

It great to see that vp pro 18 will come with Vegas prepare something similar to avid Media management that would be great for a lot or film/production companies and very soon vp will over take avid and and Adobe so there a lot of   competition

Great job Magix!

Thank you for the constant releases of Vegas and your devotion to keep improving it.

I remember a time during the last days of Sony Vegas where releases were non-existent, communication was so poor that I was even thinking of bailing out of Vegas...and the releases were very buggy. You have come a long way and see that you're giving it your best. Thank you!

I'm also happy that this isn't a subscription model. I'll keep supporting you!

😟 I was looking forward to the new Vegas Pro 18. I thought the bug that didn't allow me to work with the last 3 builds of Vegas Pro 17 was fixed. But no! I installed Vegas Pro 18-trial and when opening a project containing .mts files or importing a .mts media file it gave instant error. - it gave instant error. 😔

I installed vegas18 without removing vegas 17 and what? When starting vegas 18, the program crashes immediately and wants to send a bug report.

It's this kind m2ts files:

@Yelandkeil What version of Windows 10 are you using?

Trial zawiesza się przy starcie ... (kupiłem V18, ale ponieważ jest to wersja EDU, chciałem ją wypróbować czekając na autoryzację) .. Miałem ten sam problem z wersją próbną Video Studio 17 kilka dni temu. Mój V16 działa dobrze.

Edycja: znaleziono problem. to „znowu” moje wtyczki hitfilm, które bezpieczeństwa awarię vegas. działało dobrze w Vegas 16 po kilku tygodniach awarie, a teraz problem powróć w Vegas 18 :( ... Czekam na nadejście w przyszłości i myślę, że znowu będzie na długa wymiana poczty z obsługą., jest całkiem fajny, bo pominąłem V17. nie żałuj :-) aktualizacji (spodziewaj się całego mojego pakietu hitfilm :( Ignite itp.).

You solved the problem because I have the same

Is it possible that vegas 18 does not want to run through add-ons such as newblue fx etc. On another computer it started without any problems

Yes, another user has reported similar issues. I'm sure the team is aware and looking into it.

Yes, another user has reported similar issues. I'm sure the team is aware and looking into it.

Tomorrow I will check to uninstall all add-ons and install vegas pro 18 first, run as it goes to install add-ons and see what then

Yes, another user has reported similar issues. I'm sure the team is aware and looking into it.

Tomorrow I will check to uninstall all add-ons and install vegas pro 18 first, run as it goes to install add-ons and see what then

You can 'limit' the OFXs to run in specific version in case these FXs cause error, by moving from 'C:\Program Files\Common Files\OFX' to "C:\Program Files\VEGAS\VEGAS Pro 17.0\OFX Video Plug-Ins" (in this case, limit only to run in VP17).

Hope helps.

This new version sounds decent. I’m still not expecting I’ll be able to use it though. When I bought my Z-Cam E2 early last year I had to switch to Resolve, as Vegas would crash when loading a bunch of .h265 footage from the E2. Which was tough, having been a Vegas user since before the program even did video way back in the late 90s. Even after building a new PC (Ryzen 3950 with RTX 2070), loading a bunch of E2 clips still caused it to crash, even in a demo of Vegas 17.

Anyway, I’ll try the demo of 18 and see how it goes. Although the upgrades are so expensive now! The $249 upgrade is $349 here in Australia. In comparison, Resolve Studio only cost me $420 Australian for the whole program. They don’t charge for upgrades, they don’t put Spyware on my computer asking me to upgrade all the time, and unlike Vegas, the program rarely ever crashes.

I think Magix should cut the price of their upgrades by not bundling all the [mostly useless] 3rd party software.

I totally agree with you that Magix should cut their upgrade prices as it's not competitive anymore considering competitors such as Resolve Studio offers free upgrades! However, I am not asking for free upgrades, instead wishing for reasonable prices just like what Sony Vegas Pro used to cost! I believe $149 for the Pro and $229 for the Suite is reasonable for the upgrades!

Yet another $250 for an update of Pro? ... no.

Same price it's always been...

Used to be much lower prices when Sony used to own the software!

Not seeing 100% usage doesn't mean that there is power going unused... that isn't how it works. Any number of bottlenecks in your system could be preventing that from hitting 100% usage. As for flicker removal, did you run the motion tracking and then enable the motion compensation option?

All looks interesting BUT, having just paid the same on 28th April it feels like a bit of a con (at this rate Adobe looks like good value - and it was their "value" gap that had me abandoning Adobe to return to Vegas)

The fact that you waited until near the end of 17's life cycle to buy it doesn't mean adobe charging $600 per year is any more attractive... 17 has been on the market a full year.

@fr0sty In case you don't know, you are spreading misinformation my friend! As much as I hate Adobe with their stupidly crazy prices, we still need to tell the truth nonetheless! Adobe Premiere Pro costs $239.88/year! So it is in par with Vegas Pro 365 also at $239.88/year. The $600/year you are referring to is for a huge suite which includes over 20 applications (like Photoshop, Illustrator, InDesign, Lightroom, Acrobat Pro, Premiere Pro, After Effects, Dimension, Audition, etc.) + 100GB of cloud storage, Adobe Portfolio, Adobe Fonts, and Adobe Spark!