[RELEASE] Video Pro X13 – SIMPLY HIGH END.

johnebaker wrote on 7/9/2021, 12:42 PM

Hi Ray

. . . . An earlier post seemed to show other hidden parts of the program that could be useful such as the video properties section when right clicking a clip. Why have the addition options suddenly appeared? . . . .

If you are referring to the Object Properties option as shown in Rob's (Bol) image here - they haven't - these options have been there for quite a while - the furthest I can go back is MEP 2015 where the options are there but in a different layout. VPX 6 onwards also had these options.

The only mention they get in the manual AFAICS is in the Keyboard shortcuts list Ctrl + E

. . . . some information on how to set up VPX 13 in the manual should be mandatory . . . .

This could be a problem as there are so many ifs ands or buts with this, projecting the outcome from previous testing we have done with MEP, there is no one combination of settings to fit all types of projects depending on what is on the timeline ie video formats, images, effects, titles, etc.

John EB

dond10 wrote on 7/9/2021, 1:24 PM

Hi Everyone

New patch 19.0.1.105released - see here.

Section, Title and Export range issues are fixed , Display audio channels for Surround Sound now working - still get loss of audio waveform when extracting the channels.

John EB

KF with title is also working.

I had been having trouble playing my video when my Radeon 550 had been selected as Hardware acceleration but this is now working OK so far

CubeAce wrote on 7/9/2021, 2:37 PM

@johnebaker

Hi John.

Ye,I had never noticed that in VPX. Not all of those options are available in MEP where I had looked at it previously. Have now checked with VPX 11. 👍

While I don't disagree that different systems may well need different settings, now that we have more choice it is going to cause an awful lot of people in future to wonder why something isn't working if the settings can't be interchanged at least successfully. It will make diagnosis of future problems here more difficult and may result in less than ideal answers. At least in prior versions most of the settings worked if the equipment was correct even if it didn't give optimal results.

With other manuals for software in the past on other products there was at least a setup guide with explanations of why certain settings may be preferable or why the need for certain levels of equipment.

I'm glad to see Dond10 have success with his AMD graphics. It would be nice to see more conformation of AMD systems working better with VPX or MEP.

Ray.

DonD wrote on 7/9/2021, 3:21 PM

I originally purchased X 12 and was working just fine. The last update uninstalled X12 and installed X13, which is a piece of crap. When I trim a video and click "End of range " ] " (out point) it kills the program without any notice and I have to restart the program. Also it suspended my Hardware Acceleration and at this point I have no idea if I have it anymore. My GPU is very high end and fully updated with all the latest drivers. I haven't used it long enough to discover anymore BUGS. After I send this COMMENT off to ever reads it, and uninstall X13 and reinstall X12 which seems very stable. A not very happy user since 2013.

CubeAce wrote on 7/9/2021, 3:49 PM

@DonD

I spoke too soon 🤔🤔🤐

Sorry to hear that.

Ray.

browj2 wrote on 7/9/2021, 5:55 PM

@DonD

Hi,

When I trim a video and click "End of range " ] " (out point) it kills the program without any notice...

I'm trying to replicate what you did. Could you please explain step by step exactly what you did and how? Does it happen with other video clips?

Also, confirm that you are using the patch that came out today, 19.0.1.105.

John CB

browj2 wrote on 7/9/2021, 6:06 PM

@CubeAce

Hi Ray,

Ye,I had never noticed that in VPX. Not all of those options are available in MEP where I had looked at it previously. Have now checked with VPX 11. 👍

Ray.

I'm not sure what you mean that not all of those options are available in MEP. Do you mean the Object Properties?

In the image, MEP2021 is at the left, VPX13 at the right.

The latest patch seems much more stable and there are some pleasant surprises - more tomorrow.

John CB

CubeAce wrote on 7/9/2021, 6:45 PM

@browj2

Hi John.

Yes I meant the lookup table in VPX which now seems to have more options in 13 if memory serves. Not that I have ever used LUTS much.But also the additional processing box. I don't understand the differences.

Ray.

tpolakov wrote on 7/10/2021, 12:47 PM

Anyone having access to the new build... Are fade in/outs working now on export with HW acceleration enabled?

Thanks

browj2 wrote on 7/10/2021, 1:24 PM

@DonD @johnebaker

Here is the bug that Don mentioned.

When previewing a video clip from the Media Pool in the Source Monitor (not the trim window), if the video is playing back and you press on either of the range start/end buttons ([ or ]), the program shuts down with no warning or error message.

@johnebaker - can you replicate this?

@CubeAce

Hi Ray,

LUTs have been a feature in VPX for several years now, before they could be used in MEP.

John CB

browj2 wrote on 7/10/2021, 1:35 PM

@tpolakov

Hi,

I can confirm that fades don't work in an exported file using my Surface Pro 4, HWA Import, Processing and Export all for Intel HD Graphics 520.

My export is standard NTSC, 1920x1080, 29.97fps.

John CB

johnebaker wrote on 7/10/2021, 3:18 PM

@browj2

Hi John

. . . . previewing a video clip from the Media Pool in the Source Monitor . . . .

Confirmed - I/o points either by the monitor buttons or keyboard shortcuts crash VPX.

. . . . I can confirm that fades don't work in an exported file using my Surface Pro 4, HWA Import, Processing and Export all for Intel HD Graphics 520. . . . .

Same here for the 4K and1920x1080 UHD 630 and PAL 25 fps.

If you compare an export using fades and one using cuts only, there is one frame of black where the fade in/out has been set - in preview it is fine, after exporting it is not obeying the set fade in/out lengths.

John EB

dond10 wrote on 7/11/2021, 7:40 AM

Has anybody been having trouble with HitFilm plugins? Most of my New Blue plugins seem to work except for Titler 6 but any HitFilm crash VPX and on restart I get the crash report to send but on sending get a popup to say the report could not be sent.

Don

CubeAce wrote on 7/11/2021, 4:27 PM

@DonD

Hi Don. Try again.

The servers seem to have been down all day and not long been back on.

NB Titler 6 has always been next to useless on my system with current MEP or earlier version of VPX (11) if I try to go above an HD resolution.

Ray.

dond10 wrote on 7/12/2021, 12:59 AM

@DonD

Hi Don. Try again.

The servers seem to have been down all day and not long been back on.

NB Titler 6 has always been next to useless on my system with current MEP or earlier version of VPX (11) if I try to go above an HD resolution.

Ray.

Hi Ray

Titler 6 worked not to bad in X12 but here it just does not want to know. As for the crash reporting this also does not work.

Don (@dond10)

SevCardy wrote on 7/12/2021, 2:28 AM

@tpolakov

Anyone having access to the new build... Are fade in/outs working now on export with HW acceleration enabled?

No, they're still not working with either NVIDIA or Intel iGPU (tested for UHD and HD 1920x1080 25fps PAL).

I can also confirm the 1 frame of black where a fade-in should start.

Interestingly, if Processing is set to "Compatibility" (ie software only) in the display settings, they do work.

Sev

johnebaker wrote on 7/12/2021, 3:35 AM

@tpolakov, @SevCardy

Hi

. . . . Are fade in/outs working now on export with HW acceleration enabled . . . .

As a workaround, try using the Color fade transition and set it to black - works OK here with acceleration.

John EB

johnebaker wrote on 7/12/2021, 3:52 AM

@DonD, @CubeAce

Hi Don, Ray

No issue with NB Titler 6 here with 4K project/images/video - tested with Device options set as UHD630, UHD630, UHD630 and UHD630, RTX, RTX - exports are also OK.

Added: no issues with Hitfilm Movie Essentials effects with above device options.

John EB

CubeAce wrote on 7/12/2021, 5:08 AM

@johnebaker

Hi John.

No issue with NB Titler 6 here with 4K project/images/video

Try exporting the Title as a video file direct from NB Titler 6 and see if it still works please.

That was when I first had problems on my system with NB Titler 6. Windows 10 can't read the resulting video files on my system although I can see them in MEP 2021. NB Titler 6 has been a very mixed bag for me as you may remember I put a topic thread up some time back. Whether this has been due to a lack of nvidia resources or a mov. problem I can't tell. As long as I stick to projects lower than 4K it seems to work but not above that resolution. NB Titler 6 only seems to be able to export to the mov format.

Why did I do that in the first place?

Originally I needed more instances of NB Titler 6 in the project and found I could only open one instance at a time in the project.

Ray.

johnebaker wrote on 7/12/2021, 6:02 AM

@CubeAce

Hi Ray

. . . . Try exporting the Title as a video file direct from NB Titler 6 and see if it still works please. . . . .

Are you using on of the Main Title presets - I do have issues with these at 4K - mainly in that Alpha is not picked up, if you have Quicktime installed, they do import into MEP 2021 and VPX13, however the Alpha channel is not obeyed and has to be added manually where possible.

At 4K VLC shows the video clip as being blank, MediaInfo reports:

General
Complete name : W:\MAGIX\DVD_BD_Projects\Test Projects\Titling\NB Titler pro\Tug.mov
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 0000.02 (qt )
File size : 3.98 MiB
Duration : 3 s 0 ms
Overall bit rate mode : Variable
Overall bit rate : 11.1 Mb/s
Writing application : Lavf57.71.100

Video
ID : 1
Format : PNG
Format/Info : Portable Network Graphic
Compression : Deflate
Codec ID : png
Duration : 3 s 0 ms
Bit rate mode : Variable
Bit rate : 11.1 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 FPS
Color space : RGBA
Bit depth : 8 bits
Compression mode : Lossless
Bits/(Pixel*Frame) : 0.054
Stream size : 3.98 MiB (100%)
Language : English

The same title added direct to a clip via the plugin also does not keep the Alpha channel for some of the Main Title presets.

HTH

John EB

CubeAce wrote on 7/12/2021, 7:19 AM

@johnebaker

Hi John.

Yes I was using a main title preset in 4K when the trouble started although not since. I fear higher frame rates at 4K may also be contributing to problems. (50fps). I can't get any such clip to play within Windows unless I convert it first. While I can import such a clip into MEP or VPX, such a clip can result in the editor freezing but not always.

I did see a help article that explained why I may not have been able to use more than one instance or NBT6 at a time but the solution to the problem does not seem to be an option within the version that I have. The article is for NBT7.

Thanks for the heads up about the alpha channel. Not sure how to rectify that though.

In all honesty I've more of less given up on NBT6.

Ray.

johnebaker wrote on 7/12/2021, 10:07 AM

@CubeAce

Hi Ray

I too gave up on using NB Titler Pro6 and 7 preferring to use my favourite animation program to create titles such as this

John EB

CubeAce wrote on 7/12/2021, 11:14 AM

@johnebaker

Hi John.

I agree.

I have more than I need at present for my titling needs. Even what is within MEP or VPX.

That, along with the animation one can do within the basics is enough.

Ray.

paulsweigert wrote on 7/17/2021, 10:52 AM

Since updating from VPX 12 to 13 I have been having an issue exporting getting an error message about updating a codec. I have been working with Magix support and they are still trying to resolve the issue. I noticed this, when I had videos in the first track that were H265 and had video in the 2nd track that was H264 it seemed to work ok. But if I switched out the first clip in track one with the clip from the 2nd track I got the issue.

Interesting....