[BUG] MVC s3D files not opened correctly in Vegas Pro 17

NickHope wrote on 12/23/2019, 11:42 PM

Quoting from @Wolfgang S.:

"Beginning with VP17 b353 and now also with b387 the support for s3D MVC files from cameras like the Sony TD10 but also the Panasonic Z10000 is broken. Even after Setting the Project properties to s3D, files from those cameras are not read any more as s3D files and paired automatically, but are shown as 2D files only.

Reported in the German Videotreffpunkt https://www.videotreffpunkt.com/index.php?thread/22488-vegas-pro-suite-17-build-387-ist-online/&postID=393033#post393033 and verified by me."

I downloaded the test file provided in the thread linked above. MediaInfo:

General
ID                                       : 0 (0x0)
Complete name                            : E:\0-test-media\Sony-TD10e-stereoscopic-3D-20150523145309.m2ts
Format                                   : BDAV
Format/Info                              : Blu-ray Video
File size                                : 1.88 MiB
Duration                                 : 540 ms
Overall bit rate mode                    : Constant
Overall bit rate                         : 28.6 Mb/s
Maximum Overall bit rate                 : 28.0 Mb/s
Recorded date                            : 2015-05-23 14:53:08-10:00
Writing application                      : Sony HDR-TD10E

Video #1
ID                                       : 4113 (0x1011)
Menu ID                                  : 1 (0x1)
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4.1
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 2 frames
Codec ID                                 : 27
Duration                                 : 440 ms
Bit rate mode                            : Variable
Maximum bit rate                         : 22.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 25.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Interlaced
Scan type, store method                  : Separated fields
Scan order                               : Top Field First
IrisFNumber                              : 4.000000

Video #2
ID                                       : 4114 (0x1012)
Menu ID                                  : 1 (0x1)
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Stereo High@L4.1
MultiView_Count                          : 2
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 2 frames
Codec ID                                 : 32
Duration                                 : 440 ms
Bit rate mode                            : Variable
Maximum bit rate                         : 22.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 25.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Interlaced
Scan type, store method                  : Separated fields
Scan order                               : Bottom Field First

Audio
ID                                       : 4352 (0x1100)
Menu ID                                  : 1 (0x1)
Format                                   : AC-3
Format/Info                              : Audio Coding 3
Commercial name                          : Dolby Digital
Codec ID                                 : 129
Duration                                 : 544 ms
Bit rate mode                            : Constant
Bit rate                                 : 448 kb/s
Channel(s)                               : 6 channels
Channel layout                           : L R C LFE Ls Rs
Sampling rate                            : 48.0 kHz
Frame rate                               : 31.250 FPS (1536 SPF)
Compression mode                         : Lossy
Delay relative to video                  : -80 ms
Stream size                              : 29.8 KiB (2%)
Service kind                             : Complete Main

Text
ID                                       : 4608 (0x1200)
Menu ID                                  : 1 (0x1)
Format                                   : PGS
Codec ID                                 : 144
Delay relative to video                  : -80 ms

In VP17 build 387 it opens as a single track of video and a stereo audio track. The plug-in used is compoundplug.dll:

In VP16 build 424 it shows what seems to be 5.1 audio, but no video. It also opens at around 15 mins on the timeline, even if I drop it at 0 mins. The plug-in used is mvcplug.dll:

Can anyone open that sample file correctly in any version?

Does anyone have another stereoscopic 3D sample file that opens correctly in a version prior to VP17 build 353?

Comments

vkmast wrote on 12/24/2019, 1:25 AM

@NickHope VMS Platinum 16 build 175

and Season's Greetings to all ! (off for a day or two)

 

Wolfgang S. wrote on 12/24/2019, 2:15 AM

email sent to the development team written yesterday (23.12):


„A user in my German spoken forum has reported, that - beginning with VP17 b353 and now also with b387 the support for s3D MVC files from cameras like the Sony TD10 is broken. Those MVC files have been imported in the past in Vegas and have been recognized as s3D and the both streams have been paired automatically, if one enables a s3D project in the project settings before you try the file import.

Well, I can confirm that for s3D files shoot with my Panasonic Z10000, has the same MVC format that has been used by the TD10.

As far as I have been able to track down the error there sees to be a bug in the mvcplug.dll and/or sonyjvt.dell in the Vegas Pro 17, since the decoder used to decode the file seems to be now the compundplug.dll but not any more the mvcplug.dll as it had been in Vegas Pro 16. (That is why we see after the decoding step a 2D file only, since we need the mvc decoder for this type of mvc files.)

An easy workaround seems to be to copy the two older files mvcplug.dll and sonyjvt.dll from the Vegas Pro 16 folder to the Vegas Pro 17 folder. If you do that, then the MVC files are recognized again by Vegas Pro 17b387 as s3d files. So I assume that it is a bug in the mvcplug.dll decoder.“

 

The team has answered yesterday that they will have a look to that.

matthias-krutz wrote on 12/24/2019, 2:48 AM

For me, this short sample file is opened incorrectly in all versions. It seems to be a file shortened with ffmpeg.
You can find a sample file on this page.

https://forum.cyberlink.com/forum/posts/list/0/18211.page#93673

http://forum.cyberlink.com/forum/posts/downloadAttach/5768.page

So I can confirm the problem.

Wolfgang S. wrote on 12/24/2019, 2:59 AM

Dont panic. I never used this file linked above since I have a lot of own TD10 and Z10000 files from my own cameras. A short original sample MVC Z10000 file shoot by me was forwarded to the development team from my side too, together with the report and other documents showing what goes wrong here.

So we have a clear repro, have pinned down that the wrong decoder is used by Vegas Pro 17. The team is aware of that and will have a look into it.

Joelson_Forte wrote on 12/24/2019, 12:11 PM

If Vegas users who need this feature are lucky, maybe someday MAGIX will fix it. In the meantime, try the workarounds below.

In the video I used the version of Vegas Pro 14. Maybe it works on versions 15-17.

Alternative solution - Drag the video track to right

 

Wolfgang S. wrote on 12/24/2019, 3:36 PM

If Vegas users who need this feature are lucky, maybe someday MAGIX will fix it. In the meantime, try the workarounds below.

In the video I used the version of Vegas Pro 14. Maybe it works on versions 15-17.

Alternative solution 1

Alternative solution 2


I really do not sure if I understand what you are talking about. The bug discussed here is a very specific bug - s3D files encoded to the MVC Format (cameras like the TD10 or Z10000) cannot be read any more correctly in the latest two builds of Vegas Pro 17. In former builds like Vegas Pro 14 there is no issue with MVC files. So if you use Vegas Pro 14, I do not see any need for a workaround for MVC files.

NickHope wrote on 12/24/2019, 9:30 PM

There are 2 separate bugs here:

#1. The bug that Wolfgang raised, whereby s3D MVC files are opening with the wrong decoder in VP17 b353+, and so show only single video track + stereo audio.

#2. The bug that Joelson refers to, whereby the video streams of some 3D MVC files open "bunched up" on the left, but can be dragged out with the mouse so that they display (as shown in Joelson's demo video).

While testing for bug #1 with the sample from Videotreffpunkt, I confusingly suffered bug #2. Thank you @matthias-krutz for the link to the sample, which exhibits bug #1 and does not suffer bug #2.

I'll add bug #1 to the known issues post.

@Joelson_Forte, do you (or anyone else) know what conditions cause bug #2?

NickHope wrote on 12/24/2019, 10:46 PM

@Joelson_Forte Yes, it could just be that the file is so short. I got the impression from your previous comments that you have had to use your workaround often, so I thought you might have noticed a pattern.

Regarding the workaround in your 2nd video (disabling mvcplug so that compoundplug is used), I get the feeling that the video will still only be 2D, because it's showing only 1 stream on 1 track. When a stereo 3D video stream opens correctly, the streams are on 2 tracks. When you switch to "Side by Side (full)", I think it's just showing the same stream side by side.

Wolfgang S. wrote on 12/25/2019, 7:14 AM

 

Sorry, but you are totally wrong. The same BUG is also present in VP14. Just watch the video to see.

The alternative solution 2 worked very well here on vp14 and also on the latest VP17 Build 321, 353 and 387.

The purpose of the video is just to provide a possible temporary solution for users who are in need and cannot wait forever for a MAGIX fix. If this is not serve for you, I am sorry, it may serve other users just as it has been serve to me.

This thread is about a very specific bug that has been raised, tested, verified and communicated to the development team. It is something that has happened in the latest 2 builds of Vegas Pro 17 only. To mix that up with another bug is confusing.

I do not say that you are wrong with your bug - but even then it makes no sence to mix that together.

 

Wolfgang S. wrote on 12/25/2019, 7:37 AM

When a stereo 3D video stream opens correctly, the streams are on 2 tracks. When you switch to "Side by Side (full)", I think it's just showing the same stream side by side.

That is not always true. If one enable s3D settings in the Project Settings an Imports an MVC file, then this file is paired as s3D stream in 1 track.

MVC opens on two tracks only if s3D has not enabled in the Project settings. But even then it is possible to pair the two tracks of an MVC file - and end up with a correct s3D file.

The sbsf or sbsh does not help really to know if we have a s3D view now. A better way is to swith to the anaglyphic view to see if there are disparities or not.

Regarding the workaround in your 2nd video (disabling mvcplug so that compoundplug is used), I get the feeling that the video will still only be 2D,

The file "20110131223148[1].MTS" from the second link of Matthias is an MVC file. It required an MVC decoder to show both L and R of the footage. I one disables the mvcplug.dll he disables the MVC decoder. The compoundplug.dll can show a 2D stream only. And yes, this file can be opened in Vegas Pro 16 as s3D file but not in Vegas Pro 17.

NickHope wrote on 12/26/2019, 12:06 AM
This thread is about a very specific bug that has been raised, tested, verified and communicated to the development team. It is something that has happened in the latest 2 builds of Vegas Pro 17 only. To mix that up with another bug is confusing.

I do not say that you are wrong with your bug - but even then it makes no sence to mix that together.

@Wolfgang S. I doubt this was intentional. I expect J.F misunderstood which bug was being discussed, which is understandable, since the sample discussed in the original post exhibits both bugs.

When a stereo 3D video stream opens correctly, the streams are on 2 tracks. When you switch to "Side by Side (full)", I think it's just showing the same stream side by side.

That is not always true. If one enable s3D settings in the Project Settings an Imports an MVC file, then this file is paired as s3D stream in 1 track...

You're correct. My error. Apologies for the misinformation. But the 2nd workaround J.F posted (disable mvcplug so that compoundplug is used) does only give 2D video.

matthias-krutz wrote on 2/27/2020, 6:03 AM

@Wolfgang S., @NickHope The problem appears to be fixed in b421. For me MVC s3D is opened correctly again with mvcplug.dll.

NickHope wrote on 3/3/2020, 5:35 AM

The sample that @matthias-krutz linked to above seems to open correctly for me in VP17 build 421. There was nothing in the release notes about this being fixed. @Wolfgang S. Are you satisfied that this is now fixed?

andreas-georgiou wrote on 3/3/2020, 7:38 AM

I have the same issue, this although seemed to be fixed by b421 but the sound is now silent as there doesn't seem to be support for AC-3 5.1 dolby surround?

Also I find the preview (GPU-off) on VP16 is around 23fps, on VP17 b421 starts fast then drops to 1fps.

Footage from Sony TDR20, *.M2TS imported via Sony Playmemories home.

Have not tested burning ability from timeline to BD s3D MVC and 5.1 surround sound, neither exporting to Architect and burning s3D to MVC BD same settings.

Really sad that instead of adding support to more codecs and improving performance of existing ones, the seem to predicate support for a number of codecs and adding hundreds of unnecessary plugins for transitions etc. how many of these does anyone see on the big screen?