My top 5 Bugs (so far)

bitman wrote on 12/3/2016, 4:29 AM

My top 5 Bugs (so far)

1) Newblue ofx watermark does not go away with NewBlue stylizers ultimate package in Magix Pro X (no issues with “magix” vegas 14)

2) Several Newblue ofx plugings of type PIP and alike (picture in picture) do not work properly in Magix Pro X – black mask should not be visible (no issues with “magix” vegas 14)

3) Hardware acceleration (standard modus D3D) reverts to slow compatible modus when using rotation functions with e.g. photos in Magix Pro X.
(no issues in MEP 2016)

4) some collages make you loose hardware acceleration, probably related to issue 3)  

5) 5.1 audio is massacred to a weird mono sound with no resemblance to the original, when imported as a nested sequence in Magix pro X. (It seems that “magix” vegas 14 with the similar project nesting is also not able to nest 5.1, but here at least the 5.1 audio is converted to stereo) 

All these are reported to magix (and some to both newblue and magix), and all I get is after a few weeks of insisting, yes we are aware of the issue, we have passed to the technical staff. And there it ends. I am not happy.

Update 16/12/2016

  • Issue 3 and 4 seem fixed in build 15.0.3.127
  • Issue 5 confirmed by magix, and is not supported yet (5.1 sound in nested sequences) 

Comments

browj2 wrote on 12/7/2016, 10:37 PM

Hi,

For me, doing a mirror knocks out the Hardware acceleration as well.

I think that you are one of the few who has tried out OFX in VPX. Have you tried HitFilm Ignite?

Don't expect quick updates from Magix unless it is really a serious problem. We are still waiting for an upgrade under the 360 day update (upgrade) plan. MEP 2017 came out with new features that VPX does not have, and then even more features were introduced in November. Nothing for VPX

I have also raised a couple of tickets with Magix.

Last changed by browj2 on 12/7/2016, 10:37 PM, changed a total of 1 times.

John C.B.

VideoPro X(16); Movie Studio 2024 Platinum; MM2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

bitman wrote on 12/10/2016, 1:58 AM

I do not have HitFilm Ignite. But OFX (at least with the afordmentionned newblue stuff) does not work properly.

Even if it did not had the issues I mentionned, the way OFX is implemented in Vegas 14 is much more usable

For example OFX PIP with newblue in Vegas has the possibility to drag with your mouse the location of your PIP which is much more convenient than using X and Y sliders.

As I raised some of the OFX bugs on newblue itself, newblue commented that they were surprised their product (newblue elements pack, newblue stylisers pack) was working at all (albeit with issues as mentioned) on a NON suported NLE (which is stange, as OFX is just what it is, O stands for "Open", if the NLE supports OFX or claims it does, it should support it.  

On the plus side Magix pro X feels and works a bit more modern than Vegas, and has a less cluttered UI. 

They both have their pro's and cons.

I do agree that Magix should not let their "Pro X" version in the dark so long without updates for and for their reproducible bugs and features their consumer version MEP 2017 has before "X".  As they are both now under continuous update plan, well update the pro version first, we pay more for this version. I suspect more people purchase the consumer version so even with lower profit margins per unit, the volume make up for it so the consumer version will have priority in resource allocation I assume...

As I am flemisch (=dutch) speaking Belgian I sometimes roam the German forum as German is more or less understandable for me, and I see some rant there as well on lack of updates for bugs and features for the pro version, and slow response to their bug submitting - even in their native German language!      

bitman wrote on 12/13/2016, 1:07 AM

Update yesterday I received a new patch 15.0.3.127 to try out which solves a.o. some of the issues I had:

see 3) and 4)

browj2 wrote on 12/13/2016, 8:23 AM

I started using the Project temp folder more and yesterday had several difficulties. First I import the files into various folders and then import the files onto the timeline from the Project folder, not from the Media pool.

Doing an insert at the playback marker from the Project temp folder placed the object at the end of the timeline. Yesterday. I also tried this on my laptop, no problem. Tried again this am, inserting places object at end of timeline. I was using the shortcut 2. Tried other insert modes, multitrack ripple and overwrite and they also place the object at the end of the track. The only ones that work properly are 1 (normal import to the end of the movie), and 4, exchange.

I tried to import more than one object at a time, and only one showed up on the timeline, but the red lights for all selected objects were on. I tried deleting them from the timeline and the lights stayed on. Even restarting did not get the lights to go off with nothing on the timeline.

Right click on one of these lit objects when it is no longer on the timeline and choosing "Select associated objects in movie" empties the timeline/project window and there is no timescale shown. Click on the bottom scroll bar and the timescale comes back. The movie is now 30 minutes long with nothing on the timeline. And there are a few more anomalies.

I will raise this with Magix, but would appreciate it if someone could confirm some of these problems.

John C.B.

VideoPro X(16); Movie Studio 2024 Platinum; MM2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

bitman wrote on 12/13/2016, 11:29 AM

I started using the Project temp folder more and yesterday had several difficulties. First I import the files into various folders and then import the files onto the timeline from the Project folder, not from the Media pool.

Doing an insert at the playback marker from the Project temp folder placed the object at the end of the timeline. Yesterday. I also tried this on my laptop, no problem. Tried again this am, inserting places object at end of timeline. I was using the shortcut 2. Tried other insert modes, multitrack ripple and overwrite and they also place the object at the end of the track. The only ones that work properly are 1 (normal import to the end of the movie), and 4, exchange.

I tried to import more than one object at a time, and only one showed up on the timeline, but the red lights for all selected objects were on. I tried deleting them from the timeline and the lights stayed on. Even restarting did not get the lights to go off with nothing on the timeline.

Right click on one of these lit objects when it is no longer on the timeline and choosing "Select associated objects in movie" empties the timeline/project window and there is no timescale shown. Click on the bottom scroll bar and the timescale comes back. The movie is now 30 minutes long with nothing on the timeline. And there are a few more anomalies.

I will raise this with Magix, but would appreciate it if someone could confirm some of these problems.


I can confirm some of your observations. I assume when you talk about Project temp folder, you talk about "projectarchive" as it is called in Dutch. I have the Dutch language localisation version of magix pro X (and patched to 15.0.3.127 yesterday - a private download link from magix I got via a mail response to one of my tickets). Inserting does indeed place the objects on the end of the time line when using the projectarchive when using the various insert modes. 

 

browj2 wrote on 12/13/2016, 12:01 PM

Yes, that should be it. Just to confirm, here is the default screen setup with the Project Folder indicated in the red box.

Thanks for confirming the issues.

Have you had any more success with build 15.0.3.127? You are the only one to have it, I presume.

John C.B.

VideoPro X(16); Movie Studio 2024 Platinum; MM2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

bitman wrote on 12/13/2016, 12:48 PM

I was not the only one who had this patch, my norton says the new file was good, fewer than 5 users had this file :)

I am sure this patch is going to be distributed soon, it looked official with a list of solved issues and improvements.

Unfortunatly this list with fixes was only appearing during install of the patch, I cannot find it any more. 

The collages issue and turn and mirror of images which caused the HW acceleration to deactivate seems fixed in build 15.0.3.127

Your issue with the insert from the archive still persits.

As my issues with newblue plugins watermark, newblue PIP which black mask which covers the whole screen (effectively killing the whole purpose of PIP) and the 5.1 audio nested sequence issue.

 

browj2 wrote on 12/13/2016, 1:05 PM

Good to hear that at least some issues will have been fixed.

As I don't have any full-version NB plugins, I can't try them. I only have the ones that came with VPX and previous versions (even some with MEP) and they all work with no watermarks.

I have raised a ticket with Magix about the Project Temp Folder problems. It's not a big deal, but the multiple insert problem is annoying.

John C.B.

VideoPro X(16); Movie Studio 2024 Platinum; MM2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

bitman wrote on 12/13/2016, 2:13 PM

The newblue plugins which came with MEP and VPX always worked fine, without watermark.  They are not OFX but native adapted for Magix. (the same plugins exist in OFX variant). In fact I have some as such in 2 versions: e.g. "glow pro" I have from MEP or VPX and from the standalone package (thus OFX). Some OFX newblue plugins have the watermark issue (especially the NB stylizer package), some do not.

But to be honest I think that the newblue watermark issue for the OFX is a newblue licence APP manager issue which is probably not suporting (yet) Magix for OFX plugins.  I raised tickets also at newblue for it. So maybe magix is (maybe) not to blame alone for this one.  

browj2 wrote on 12/15/2016, 11:07 PM

I received the same patch and it seems to have resolved the HW Accel. problem, but not other problems. One down, more to go.

John C.B.

VideoPro X(16); Movie Studio 2024 Platinum; MM2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos

bitman wrote on 12/16/2016, 3:37 AM

I get the (subjective) feeling mpx seems to crash more often with this new patch. I say subjective, as I cannot quantify it as I am using more often Vegas pro 14 currently (also now from Magix) due to all the issues with MPX which are a deal breaker for me. I am really pleased with Vegas 14, it handles the OFX newblue plugins I have perfectly (and more practically as it has some sort of " feehand mouse pointer x-y placement " control (Not sure how to describe/name it).

Did you get te update via the auto-update or via mail?

Magix has confirmed (finally) that the 5.1 sound in nested sequences is indeed not supported, and they are looking to add this as a new feature in the future. But when, is unknown.    

 

browj2 wrote on 12/16/2016, 10:34 AM

I received the patch by email, and I spoke too soon. Last night when I imported a large image, actually a panorama of a dozen photos made with PanoramaStudio 3 which comes with Xara DesignerPro X, VPX popped out of HW Accel. mode. I'll check the same thing on my Surface Pro 4.

John C.B.

VideoPro X(16); Movie Studio 2024 Platinum; MM2025 Premium Edition; Samplitude Pro X8 Suite; see About me for more.

Desktop System - Windows 10 Pro 22H2; MB ROG STRIX B560-A Gaming WiFi; Graphics Card Zotac Gaming NVIDIA GeForce RTX-3060, PS; Power supply EVGA 750W; Intel Core i7-10700K @ 3.80GHz (UHD Graphics 630); RAM 32 GB; OS on Kingston SSD 1TB; secondary WD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB, 8TB; three monitors - HP 25" main, LG 4K 27" second, HP 27" third; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer.

Notebook - Microsoft Surface Pro 4, i5-6300U, 8 GB RAM, 256 SSD, W10 Pro 20H2.

YouTube Channel: @JCBrownVideos