Artifacts in Rendered file Vegas Pro 15

Colin-Baxter wrote on 2/21/2019, 4:38 AM

Hi all - newbie here.

I purchased VP15 in August last year on one of Magix "Special Offers". Overall I like the product, but my first real project identified a problem which according to various Google searches has plagued VP for many versions.

I record PAL 1080-50i (1920x1080, 25.000 fps) to pruduce BluRay and DVDs. My project has around 20 clips and no FX.

Using the recomended Mainconcept render option I get odd frames appearing in the wrong places and a little accompanying pixelation. I raised a MAGIX support ticket and followed the advice that I received. I thought it had worked at the time, however 6 month later when I started my next project the same thing happened again. I reopend the case with Magix and eventually thay replied with

"It appears our team has been able to reproduce the issue under specific circumstances. This is a known issue which will be resolved in a future application update. Thank you for reporting this issue."

Now my question is: Will they advise all licenced users of the update to VP15, or will they build the update into VP16 asking me and others to pay for an application update" I have asked them how this will work, but no answer yet. Looking through the Forum it seems that purchases are only supported for 12 months (thereafter requiring payment for updates). I would like to know how other users have fared updates.

Thanks

Comments

j-v wrote on 2/21/2019, 5:04 AM

Which buildnumber of the program do you use?
Not so long ago (28-11-2018) there was a final update buildnr. 416 so maybe it is not needed to upgrade to version 16

Colin-Baxter wrote on 2/21/2019, 5:38 AM

I just found that update to 416 and have installed it. I suspect that the update does not fix this problem as the message from Magix about working on the problem only came to me on Monday. However 416 should be more stable, thanks

Musicvid wrote on 2/21/2019, 10:22 AM

Unfortunately, you will need to upgrade in order to benefit from updates to VP16. I have never known Magix to retrofit a previous version. This is not a widely reported error, so maybe we can help.

Start by providing MediaInfo. Vegas Properties, and a pristine example showing the glitch, as in this FAQ :

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

While you are waiting, try turning Off all GPU in Vegas, and although it may or may not be relevant, this is worth a read.

https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-try-disabling-so4compoundplug-dll--108345/

Colin-Baxter wrote on 2/21/2019, 10:32 AM

Thanks for the response. I will have a go at adding this info tomorrow.

Musicvid wrote on 2/21/2019, 11:01 AM

Yes, I have a third option in my back pocket if neither of those are effective.

But do try the update first, as j-v suggested, as it is the logical first step. I gave up on predicting outcomes long ago.

vkmast wrote on 2/21/2019, 11:03 AM

Re late updates, this was an exception, "updating an older version will not be a regular practice." Don't know why Support chose to use the word "update" in their reply.

j-v wrote on 2/21/2019, 11:11 AM

R Don't know why Support chose to use the word "update" in their reply.

To me it was an update, nothing more or less as other "updates" and also that is an exception, never saw it before since I use Version 8

vkmast wrote on 2/21/2019, 11:17 AM

@j-v please note that I was referring to Support's message, which was given to the OP after the last update. I was not questioning the use of the word "update" in the Patches message regarding v.15 build 416. IOW, that was an update.

j-v wrote on 2/21/2019, 11:29 AM

When I read that message of at least februari as the OP quoted - "It appears our team has been able to reproduce the issue under specific circumstances. This is a known issue which will be resolved in a future application update. Thank you for reporting this issue."-- and they are talking about "a future update" let the users of 15 be happy and wait for it. 😄

vkmast wrote on 2/21/2019, 11:41 AM

The Vegas Pro 15 update 8 (build 416) was released in November 21, 2018. As I understand it, the OP refers to a later message after he "reopend" the case. Maybe he will clarify.

As for the OP's question regarding "supporting purchases", the last updates of the VEGAS product versions can currently be downloaded without time restrictions.

j-v wrote on 2/21/2019, 11:43 AM

But I doubt if the OP gave the right quote of the moment on 22/02/2019 .

Maybe a quote of oct/nov last year????????

Musicvid wrote on 2/21/2019, 3:51 PM

Maybe we should defer until the OP has had a chance to test the options suggested that do not require a full upgrade.

Colin-Baxter wrote on 2/21/2019, 4:20 PM

As the OP I can confirm that the quote was from Monday this week (18 Feb.) Following me reopening the case. Since they have stated that they now can reproduce the error and will provide a maintenance update, I trust they will keep their word. At the end of the day I paid a lot of money out of my pension and am not in a position to pay more for VP16 OR 17. They can of course offer it for free but I doubt that will happen.

Musicvid wrote on 2/21/2019, 4:52 PM

Are you willing to try the non-upgrade options suggested, or not? If not, I shall graciously withdraw from the discussion, but I may already have a clue, contingent on your cooperation and testing.

I have no control over what Magix says, or does, but I know that solutions to reproducible issues "under specific circumstances" such as you have described sometimes occur over a matter of years, not months.

vkmast wrote on 2/21/2019, 4:54 PM

Thanks for the clarification. As @Musicvid said this has no more been widely reported, AFAIK. I came across these artifacts rather regularly with v.10 but I think they mostly went away (only) after upgrading. Hope the dev team is able to fix this issue in those "special circumstances" where it still may occur and offer a solution for users. Note though what Musicvid just wrote about these solutions.

Colin-Baxter wrote on 2/21/2019, 5:30 PM

Naturally I want something that works as intended and I am open to the non-upgrade options as you say @Musicvid. I have disabled Gpu acceleration etc and perhaps your "backpocket option" may be the answer. How do I take this forward? Cheers.

Musicvid wrote on 2/21/2019, 6:23 PM

Please post MediaInfo and Vegas properties along with a sample file per the links above.

Does "etc" include testing the 416 update, disabling GPU, and testing the so4 "fix" in that order?

You see, there is a logical hierarchy (order of doing things), that rarely involves trying the easiest or most most probable suggestions first. It is a bulletproof rule-out protocol that has been around since the early 20th century, and not an arbitrary imposition on one's patience. What you may privately call ridiculous may contain unexpected clues.

Remember to UNDO each unsuccessful change before attempting the next one, lest you forget what you did in the morning, and please, test only one possibility at a time. No free lunch at this diner.

Colin-Baxter wrote on 2/22/2019, 2:31 AM

Hi - I have yet to fully test the 416 build, and have not applied the SO4 fix which I will do later this afternoon. One clue that might help is that even with the 416 build the storyboard timeline shows a pixelated clip on the story board even though it plays cleanly through the join between the two clips. (if that makes sense). I have not tried to render since 416. I will follow your first set of instructions and come back to you with the results and printouts. Thanks

Colin-Baxter wrote on 2/22/2019, 7:09 AM

Hi @Musicvid

Here is the text from File infomation and Mediainfo as requested. Today using build 416 I rendered the original project without making any adjustments and the artifacts did not appear.

Looking at the SO4 fix, I am not sure if this would apply as my files are MXF which are not mentioned in the explanation of the fix.

Just out of interest, I managed to get a successful render before installing Build 416 by copying each edited clip to a new project and rendering them one at a time, then bringing them all together in a new project and rendering them into one file - all worked like a dream.

Thanks for your interest and help.

General  Name: AA006706.MXF  Folder: C:\Cinderella\Sunday Afternoon  Type: Sony MXF  Size: 2.00 GB (2,045,471,164 bytes)  Created: 04 February 2019, 10:12:41  Modified: 02 February 2019, 23:32:44  Accessed: 04 February 2019, 10:14:25  Attributes: Archive Streams  Video: 00:05:15.840, 25.000 fps interlaced, 1920x1080x32, MPEG_HD  Audio: 00:05:15.840, 48,000 Hz, 16 Bit, Stereo, Linear PCM Other metadata  Regions/markers: no  Command markers: no  UMID: 060a2b340101010501010d43-13-000000-0a406d5d1685058000008500022414ad  Source UMID: 060a2b340101010501010d43-13-000000-0a406d5c1685058000008500022414ad Media manager  Media tags: no Plug-In  Name: mxfplug3.dll  Folder: C:\Program Files (x86)\FileIO Plug-Ins\mxfplug3  Format: Sony MXF  Version: Version 15.0 (Build 416)  Company: MAGIX Computer Products Intl. Co.

GeneralComplete name                            : C:\Cinderella\Sunday Afternoon\AA006707.MXFFormat                                   : MXFCommercial name                          : XDCAM HD422Format version                           : 1.2Format profile                           : OP-1aFormat settings                          : Closed / CompleteFile size                                : 1.58 GiBDuration                                 : 4 min 22 sOverall bit rate                         : 51.8 Mb/sEncoded date                             : 2019-02-02 23:32:42.000Writing application                      : CANON XF100 1.00 VideoID                                       : 2Format                                   : MPEG VideoCommercial name                          : XDCAM HD422Format version                           : Version 2Format profile                           : 4:2:2@HighFormat settings                          : CustomMatrix / BVOPFormat settings, BVOP                    : YesFormat settings, Matrix                  : CustomFormat settings, GOP                     : M=3, N=12Format settings, picture structure       : FrameFormat settings, wrapping mode           : FrameCodec ID                                 : 0D01030102046001-0401020201040300Duration                                 : 4 min 22 sBit rate mode                            : ConstantBit rate                                 : 50.0 Mb/sWidth                                    : 1 920 pixelsHeight                                   : 1 080 pixelsDisplay aspect ratio                     : 16:9Frame rate                               : 25.000 FPSStandard                                 : ComponentColor space                              : YUVChroma subsampling                       : 4:2:2Bit depth                                : 8 bitsScan type                                : InterlacedScan order                               : Top Field FirstCompression mode                         : LossyBits/(Pixel*Frame)                       : 0.965Stream size                              : 1.53 GiB (97%)Color range                              : LimitedColor primaries                          : BT.709Transfer characteristics                 : BT.709Matrix coefficients                      : BT.709 Audio #1ID                                       : 3Format                                   : PCMFormat settings                          : LittleFormat settings, wrapping mode           : Frame (AES)Codec ID                                 : 0D01030102060300Duration                                 : 4 min 22 sBit rate mode                            : ConstantBit rate                                 : 768 kb/sChannel(s)                               : 1 channelSampling rate                            : 48.0 kHzFrame rate                               : 25.000 FPS (1920 SPF)Bit depth                                : 16 bitsStream size                              : 24.0 MiB (1%)Locked                                   : Yes Audio #2ID                                       : 4Format                                   : PCMFormat settings                          : LittleFormat settings, wrapping mode           : Frame (AES)Codec ID                                 : 0D01030102060300Duration                                 : 4 min 22 sBit rate mode                            : ConstantBit rate                                 : 768 kb/sChannel(s)                               : 1 channelSampling rate                            : 48.0 kHzFrame rate                               : 25.000 FPS (1920 SPF)Bit depth                                : 16 bitsStream size                              : 24.0 MiB (1%)Locked                                   : Yes Other #1ID                                       : 1-MaterialType                                     : Time codeFormat                                   : MXF TCTime code of first frame                 : 16:41:59:01Time code settings                       : Material PackageTime code, striped                       : Yes Other #2ID                                       : 1-SourceType                                     : Time codeFormat                                   : MXF TCTime code of first frame                 : 16:41:59:01Time code settings                       : Source PackageTime code, striped                       : Yes Other #3Type                                     : Time codeFormat                                   : SMPTE TCMuxing mode                              : SDTITime code of first frame                 : 16:41:59:01

Musicvid wrote on 2/22/2019, 7:52 AM

Here 'ya go, Colin.

https://www.vegascreativesoftware.info/us/forum-search/?query=Canon%20mxf%20422%20xdcam

I named that tune on the first note.

Here's exactly what I did:

At the top right of the forum page is a Search Bar. What I did was type in Canon XDCAM 422 MXF. And the results are in the link above. Now you know where we stand at the forum level.. You are encouraged to join in one of the discussions, and just may become part of the solution.

Colin, we all have to shout at the wind at times. Now, when that's all done, what comes next? Well, you have passively refused to provide a source example. We understand that completely (This isn't our first rodeo). But it also effectively rules out doing any further testing here, even if someone was inclined to do so.

Have you tried Happy Otter Import Assist yet? How about VideoRedo trial? There, my back pocket is now empty, and I am so outta here.

Hoping that providing this for you the first time will empower you to plough forward through the Vegas learning curve, which may seem daunting at times, yet ultimately rewarding, and educational.

Now who said following logical troubleshooting protocol is a waste of time? We helps those who helps themselves. As far as Magix retrofitting a previous version, that would be extraordinary, but not unheard of, as Vkmast brought to our attention. Welcome to the discussions 😌

Colin-Baxter wrote on 2/22/2019, 8:30 AM

Cheers @Musicvid I will indeed read through the posts