Vegas urgently needs to improve encoder and decoder

Former user wrote on 12/6/2018, 12:49 PM

Vegas has many problems with encoder and with the Decoder of many important video and audio formats. If this were solved in the following versions it would already be a big step and this would solve many problems that we users face.

In my point of view this is one of the main problems of Vegas and what causes more limitations for users at the time of editing. Thank you for your attention if anyone on the Vegas team is reading this.

Comments

j-v wrote on 12/6/2018, 12:56 PM

Vegas has many problems with encoder and with the Decoder of many important video and audio formats.

Such as?
Which encoder problems?
Which decoder problems?
I like to know and try it out at laptop and desktop from signature.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Musicvid wrote on 12/6/2018, 1:55 PM

That was a pretty broad brush stroke. Anything specific, or just morning indigestion?

Former user wrote on 12/6/2018, 2:11 PM

This is just the beginning. Or do not you too know how to read?

https://www.vegascreativesoftware.info/us/forum/known-issues-in-the-latest-version-of-vegas-pro--108942/

fr0sty wrote on 12/6/2018, 2:19 PM

You're posting a link to a page called known issues of the latest version of Vegas. Known being the key word... the team is well aware that they have work to do on the Vegas decoders/encoders, they've been making improvements for some time and they continue to. It's obviously no easy task, or they would have fixed it long ago and saved themselves the negativity.

Former user wrote on 12/6/2018, 2:24 PM

@fr0sty

I posted this link because the problems with encoder and decoder are also listed in this link.

j-v wrote on 12/6/2018, 2:41 PM

This is just the beginning. Or do not you too know how to read?

https://www.vegascreativesoftware.info/us/forum/known-issues-in-the-latest-version-of-vegas-pro--108942/

I think you are not willing to answer my question I made in order to give maybe some help. That's your discision, but another question then:
What is the intension of your post other than to attend the team, because that list they know already and for a long time.
It is your responsibillity and free will to use this program or not.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

fr0sty wrote on 12/6/2018, 2:45 PM

@fr0sty

I posted this link because the problems with encoder and decoder are also listed in this link.

I know, it is on that list because we (and the development team) are all well aware of the issue, and the dev team has been saying for a long time that they are working on the various bugs that have come with the new decoders and encoding systems.

Former user wrote on 12/6/2018, 4:42 PM

@j-v

Here are some examples of encoder and decoder problems in Vegas. These files open and render without error in other video editors.

I know it's my choice to use Vegas or not. So I also use Premiere, DaVince Resolve and Avid Media Composer simply to not be hostage to any software. The reason I'm still using Vegas is by dynamism during the editing process, which without a doubt is the best there is and because I believe in its potential and I want it to improve every day.

https://www.vegascreativesoftware.info/us/forum/pro-res-mov-files-are-pixelized-on-import-on-both-vegas-pro-15-16--113282/#ca700120

https://www.vegascreativesoftware.info/us/forum/bug-vegas-pro-16-open-hevc-aac-file--113096/#ca698776

https://www.vegascreativesoftware.info/us/forum/alpha-channel-not-working--113478/

https://www.vegascreativesoftware.info/us/forum/vegas-pro-16-rendern-in-4k-und-surround-5-1--113771/#ca703206

 

@fr0sty

I've been using Vegas since version 6. I have special affection for him. My criticism is for it to improve.

Previously Vegas was always ahead of the other video editors. Today the scenery is reversed and this makes me sad and angry even though it will not solve anything.

 

 

 

 

fr0sty wrote on 12/6/2018, 5:02 PM

Our point is, you're preaching to the choir. We all know, they know, it's being worked on.

j-v wrote on 12/6/2018, 5:20 PM

@j-v

Here are some examples of encoder and decoder problems in Vegas. These files open and render without error in other video editors.

Thanks for the examples, sadly I could only downloaded the ones from the mov files, the other had no proper download opportunity.

I could add them and played them at full preview on my VPro 16 build 307 and exported them to all kind of files I wanted.
My question now it : what are the problems you are encountering with VPro 16 and using those files?
 See here my tests

BTW 1
I tested on my laptop with the default install and settings of Vegas Pro, nothing hidden or changed other than allowed the old Mainconcept render option.

 

BTW 2
And here are the file properties as my Vegas is seeing them where @NickHope was asking for.

 

Last changed by j-v on 12/7/2018, 1:28 AM, changed a total of 2 times.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Musicvid wrote on 12/6/2018, 8:04 PM

This is just the beginning. Or do not you too know how to read?

https://www.vegascreativesoftware.info/us/forum/known-issues-in-the-latest-version-of-vegas-pro--108942/

Since this is a direct dig, I will respond in kind, without further comment on this thread.

When it comes to spinning known issues as some sort of personal entitlement, one had better come off as being part of the solution, rather than part of the problem.

Got time to do some coding, joelson?

NickHope wrote on 12/6/2018, 10:07 PM

@j-v

Here are some examples of encoder and decoder problems in Vegas. These files open and render without error in other video editors.

Thanks for the examples, sadly I could only downloaded the ones from the mov files, the other had no proper download opportunity.

I could add them and played them at full preview on my VPro 16 build 307 and exported them to all kind of files I wanted.
My question now it : what are the problems you are encountering with VPro 16 and using those files?
 See here my tests

BTW. I tested on my laptop with the default install and settings of Vegas Pro, nothing hidden or changed other than allowed the old Mainconcept render option.

@j-v If you are saying that the native mxhevcplug.dll decoder decodes that file without pixellation (it's difficult to see from your video), please post that finding to the thread about it so we can try and investigate why your system behaves differently from the other posters' systems.

Former user wrote on 12/6/2018, 10:46 PM

@j-v

For you to see the problem in the first clip you will need to put in full screen mode. You will notice that the video is pixelated (with huge pixels). In the Premiere is OK.

The problem in the second video is that Vegas does not recognize the alpha channel of the ProRes video file and does not remove the black background from it. In the Premiere is OK.

I'm also sending you a third video for you to test on your machine. It's a HEVEC video file with AAC audio that gets the distorted sound in Vegas. In the Premiere is OK.

download link for original video files here https://drive.google.com/file/d/1aZXK7p2kvHMgj6ulEgQsjIuzNs1zBdR1/view?usp=sharing

Watch the video below to understand better.

Former user wrote on 12/6/2018, 10:49 PM

@NickHope thanks

His comments are always sensible and of an admirable technical knowledge.

Former user wrote on 12/6/2018, 10:57 PM

Our point is, you're preaching to the choir. We all know, they know, it's being worked on.

The problem is that they have known this for over two years and Vegas still has issues with version 16  that are issues of the version 13. And we all know that.

I'm one of those who prefers a stable Vegas fix and no bugs than a new vegas full of new features that does not work right. But that is my way of thinking and and my thinking is not an absolute rule nor does it reflect the interests of the market.

j-v wrote on 12/7/2018, 1:41 AM

@j-v If you are saying that the native mxhevcplug.dll decoder decodes that file without pixellation (it's difficult to see from your video), please post that finding to the thread about it so we can try and investigate why your system behaves differently from the other posters' systems.

I posted the Vegas properties a my former comment.

@j-v

For you to see the problem in the first clip you will need to put in full screen mode. You will notice that the video is pixelated (with huge pixels). In the Premiere is OK.

I'm sorry not to do that because AFAIK that was not the question and I normally never use that kind of stuff and for sure never used and will use mov files. Why should I do that?

And for the coming days I think I have no time to test things for this forum because I 'm going out for a while to celebrate my 50 year wedding anniversary. 🍺🍹 😎

Last changed by j-v on 12/7/2018, 1:56 AM, changed a total of 1 times.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

NickHope wrote on 12/7/2018, 2:56 AM

@j-v If you are saying that the native mxhevcplug.dll decoder decodes that file without pixellation (it's difficult to see from your video), please post that finding to the thread about it so we can try and investigate why your system behaves differently from the other posters' systems.

I posted the Vegas properties a my former comment.

@j-v

For you to see the problem in the first clip you will need to put in full screen mode. You will notice that the video is pixelated (with huge pixels). In the Premiere is OK.

I'm sorry not to do that because AFAIK that was not the question and I normally never use that kind of stuff and for sure never used and will use mov files. Why should I do that?

@j-v Because your post implies that you're not seeing the issue that I and others are seeing, which is the video decoding in blocks of 8 pixels:

If you really are not seeing that behaviour, then I believe you would be the only one so far, and your feedback would be useful in analyzing and fixing the problem.

Anyway, enjoy your wedding anniversary.

karma17 wrote on 12/8/2018, 3:05 AM

I do agree with fixing known issues before adding more features, and Godspeed to the Magix team.