VPX11 Patch 17.0.3.55

browj2 wrote on 11/25/2019, 8:58 AM

An update has been issued - not a bug patch, unfortunately and I presume that the bugs on the list (see below) still exist.

Important changes in version 17.0.2.54

8k real-time playback of HEVC with NVIDIA GeForce 1060 and higher
8k UHD2 project templates and export presets for HEVC HDR preview
Color space handling
Import custom effects lookup tables
New menu for selecting transitions in the arranger
More modern Color picker in the text editor
Templates: Layer masks
Improved performance for the OFX interface
In-App Store: Individual content purchase is now available

Comments

Here is the change to the transition menu available by clicking on the transition icon at the head of an object on the timeline:

Sorry Magix, but this was not really needed and just adds a bug to the list. The previous version had no German text, more on the menu, and there is now a lag between clicking on the icon and when the menu appears.

The new Color Picker in the Text Editor is welcome and can be used to get the RGB (in %) of colours.

Template: Layer masks - is right at the bottom of Image Objects. There are now 94 masks, up from 60. Good addition.

No idea about improved performance of the OFX interface. Anyone?

However, once again, Magix has made things worse. Example: HitFilm Zoom Blur now turns the screen black and I have to change to Compatibility Mode in the Program Settings, and typing numbers into the XY box does not stick. The default is 1920 and 1080 and the only way to change the values is to use the mousewheel. Holding down Ctrl or Alt causes a freeze for several seconds. I tried several HitFilm Effects. However, typing into one of the other boxes seems to unlock the problem and then one can type into the X and Y boxes, press enter, and the value stays. But, keyframing X and Y still causes X to go to infinity.

Link to previous patches:

https://www.magix.info/us/forum/vpx11-patch-17-0-2-47--1232010/

https://www.magix.info/us/forum/vpx11-patch-17-0-2-41-patch-and-bug-list--1230537/

Link to pdf of bug list:

https://www.dropbox.com/s/z951fts2pf64ace/VPX%2011%20BUG%20LIST%20patch%202%C2%AD_41%20r8%20Resolved%20text%20removed.pdf?dl=0

John CB

Back to post

Comments

DugsBugs wrote on 12/11/2019, 1:51 AM

Apologies for not starting a new thread on this.
Since the new 63 update, I can no longer drag the bottom arrow on an object to shorten without the monitor going black.
The only way I can get around it is to open an old project from before the update, remove all objects and save that as a blank template. I can then open that as a new project and work as normal.
I would appreciate if someone can test this before I contact support.
Doug

emmrecs wrote on 12/11/2019, 3:43 AM

@DugsBugs

Hi Doug.

I've just tested this on my installation of VPX with the latest update (left-dragging a video and audio object on the timeline), no problem. No black monitor or anything else apparently "wrong".

@browj2

Yes, the Audio tab and the Store tab problems "seemed" to be fixed on first opening after the update, but again this morning both are "back to their old ways".

Jeff

DugsBugs wrote on 12/11/2019, 3:48 AM

@emmrecs
Thanks Jeff.
Have no idea what could be causing it.
I have created a ticket with support anyway.
Doug.

johnebaker wrote on 12/11/2019, 4:02 AM

@DugsBugs

Hi Doug

. . . . no longer drag the bottom arrow on an object to shorten without the monitor going black . . .

Confirmed for both images and video with one condition - this occurred on my PC only if the Video mode is set to the Intel UHD 630.

If I switch the programs Video mode to my NVidia card then dragging the image or video object does not make the monitor go black.

. . . . get around it is to open an old project from before the update, remove all objects and save that as a blank template . . . .

That suggests there is a setting that has gone awry with the latest patch.

Resetting the program settings partially fixes the the issue for me - ie for images the preview screen does not go black, however for video still has the bug when using the Intel UHD 630.

I have compare the VPX ini file from the previous patch to that of the current patch and cannot see any setting difference that may be causing the issue.

Added: I have created a ticket with this additional information.

HTH

John EB

DugsBugs wrote on 12/11/2019, 4:18 AM

@johnebaker
Thanks John.
I will try these things. It is very annoying.
Doug.

gmlotkow wrote on 12/11/2019, 6:29 AM

@DugsBugs

Sounds like the same issue I was trying to explain. In the settings/program there is a box there stating something about dithering, I found out yesterday that resolved my problem. (I'm away from computer at this time).

DugsBugs wrote on 12/11/2019, 6:38 AM

@gmlotkow
Thanks for that.
Didn't work for me however I unchecked the one saying "True to color conversion for non HDR monitors" and seems to have fixed the issue whatever the hell that means.
Still something that has changed since the latest update.
May be early days but so far so good.
Doug

gmlotkow wrote on 12/11/2019, 6:53 AM

I'm convinced much of my dvd quality issues has to to with bitrate. Some settings must have changed. I created a .m2ts file 1280x720@60p posted to youtube, and it looks great, depending on your internet speed, you may have to let it buffer before the true quality comes together.

Here is an example, I cannot get even close to this making a DVD with this quality. I thought my cameras were set wrong, or I was out of focus, but it was not the case.

Give me your comments on this picture quality, how are you viewing it?

Thanks.

johnebaker wrote on 12/11/2019, 7:28 AM

@DugsBugs

Hi Doug

. . . . True to color conversion for non HDR monitors . . .

AFAIK that means 10 bit/channel (HDR) video is reduced to 8 bit/channel to bring the colours into the correct 'colour space' for non HDR monitors.

@gmlotkow

Hi Greg

. . . . created a .m2ts file 1280x720@60p posted to youtube . . . .

What bitrate did you use? It is showing a few artefacts when the 720p version viewed at full screen 1920 x 1080, viewed at 1280 x 720 looks good - artefacts are rarely visible.

If your source video is 1080i or 1080p then you would be better off exporting and uploading to Youtube as mp4 using these recommended settings - these also include other resolution recommendations

HTH

John EB

gmlotkow wrote on 12/11/2019, 7:45 AM

@DugsBugs

Here is the second half, I rendered it to a 1270 x 720 60p mp4, I do not render the settings. Experimenting at the time with two different formats.

johnebaker wrote on 12/11/2019, 12:06 PM

@gmlotkow

Hi Greg

The MP4 version looks far better at full screen than the m2ts file, no sign of artefacts, may be because of the lower compression compared to that of the m2ts file which I assume was one of the AVCHD presets.

HTH

John EB

gmlotkow wrote on 12/11/2019, 12:18 PM

@johnebaker

@DugsBugs

Thanks for the comments, gives me some confidence, and hope.

Scenestealer wrote on 12/11/2019, 3:37 PM

@gmlotkow @johnebaker

. . . . created a .m2ts file 1280x720@60p posted to youtube . . . .

What bitrate did you use? It is showing a few artefacts when the 720p version viewed at full screen 1920 x 1080, viewed at 1280 x 720 looks good - artefacts are rarely visible.

Looks pretty bad here at 720p and the second clip looks a lot better, but to be fair the second sequence has a lot less detail and action compared to the first so would compress more cleanly with the same bitrate.

It would be good to see a Media info analysis of both segments prior to the YT upload.

Peter

CubeAce wrote on 12/11/2019, 5:13 PM

@gmlotkow

I'm just making an observation but is it possible that on such a nice system as your own that the clips are showing their age? You would be seeing every little defect exaggerated to possibly how you first viewed them. Resolution wise they are bound to suffer viewed such a way.

Ray.

gmlotkow wrote on 12/11/2019, 5:26 PM

@CubeAce

Are you saying I’m too critical of myself?

DugsBugs wrote on 12/11/2019, 5:26 PM

@johnebaker
Thanks John.
Not sure why selecting the HDR would make the screen go black but un ticking it has fixed the problem.
Does anyone know what the default setting was before the update.
I feel it is a new bug that still needs to be addressed but I guess we can add it to the list.
Thanks for all the feedback.
Doug.

marjavideo wrote on 12/11/2019, 10:59 PM

Bonjour
j'ai fait un ticket pour le problème d'affichage in 3D anaglyphe
Différence de qualité entre le moniteur principal et le moniteur source (voir pièce jointe)
cordialement
Jacques
Pour information le même problème se retrouve sur le moniteur principal de la vidéo de luxe Premium après la dernière mise à jour.

CubeAce wrote on 12/12/2019, 5:59 AM

@gmlotkow

Not really. I'm saying that newer gear is going to show up older footage and it will look worse than it used to.

In such cases it's hard to judge whether it's worse or not. Nearly everything I've recorded more than six years ago looks worse to me.

Ray.

gmlotkow wrote on 12/12/2019, 6:18 AM

@CubeAce

I just recorded that last week with some current Panasonic HC-X1's and other Panasonic's, I don't understand your comments regarding older footage.

CubeAce wrote on 12/12/2019, 6:43 AM

Sorry. My mistake.

I thought you were saying that the reason the footage looked odd was because you had revisited it after some time. I didn't realise it was purely due to the program update and the way it was handling your files. Personally I think your footage for the resolution looks good but would look better on a lower resolution screen where I could view it larger and it look sharper but it's only the large shadows areas that are suffering.

Ray.

1 … 2 3 4 5

of 5