[RELEASE] Video Pro X13 – SIMPLY HIGH END.

browj2 wrote on 6/24/2021, 9:10 PM

I found the rotation handle - it's under Orientation as Rotation is now under Size/Position. Rotating using the handle rotates the dashed box, but not the image. The size and position can also be adjusted - but only for the dashed line, not the image.

Going back to size position after resizing (without working) in Orientation, the new handles box is now smaller, the image is full-screen, but width and height have changed to suit the handles box, not the image.

Bad work!

If it ain't broke, don't fix it applies here.

John CB

johnebaker wrote on 6/25/2021, 5:47 AM

@browj2, @MAGIX_Redaktion

Hi John, Stefan

Rotation handle is definitely misplaced, personally I never used it.

It would be more user friendly, for those who use it, if the new 'rotation centre' handle should have the 'rotation handle' linked to it as part of its function.

The manual is also incorrect in that it shows the old version with the dashed line, however in VPX 13 the box is a solid line when using the rest of the size position and rotation.

The PDF manual needs updating/replacing. The manual and web version appear to be from the same source, however the PDF version has a lot of translations not done eg the majority of the Bookmarks section is in German. The online version is better, bookmarks are in English.

John EB

tpolakov wrote on 6/25/2021, 7:25 AM

Installed the trial yesterday - was looking forward to AMD acceleration on export. Seems to work very fast on simple clips, but...Fade ins/outs are not rendering with AMD hw acceleration. Interestingly enough, they show in the rendering preview, but in the exported video it's just a cut, no fade in or out. CPU rendering is OK, but about 3x slower.
More complicated transitions - like shutter do render. This version clearly needed more QA.

I tested on an intel notebook as well - the fades are not rendering there with GPU acceleration (UHD 620) either, so it's not just an AMD thing. Can you guys confirm this (maybe someone with Nvidia)? This is such a basic thing I can't imagine it was missed in QA.

teroschilo wrote on 6/25/2021, 7:30 AM

this upgrade causes me a lot of problems. continuous crashes and more. I have excellent video card and 32Gb of Ram. New PC and all this did not happen previously. I would like to know how do you get all this enthusiasm. I don't think I will continue to pay for Magix upgrades of this level. I am very disappointed.

cmichael52 wrote on 6/25/2021, 7:55 AM

Downloaded the new version and the title tool is frankly not working. You can't move the title box, the duplication of an existing title for seamless transitions is placing the duplicate in another spot - bugs need fixed.

johnebaker wrote on 6/25/2021, 8:29 AM

@OBVideos, @teroschilo, @cmichael52

Hi

If you were using VPX 12 before the upgrade see this post from Magix.

John EB
Forum Moderator

R-Faber wrote on 6/25/2021, 9:41 AM

R-Faber wrote on 6/25/2021, 10:21 AM

After updating (Yes Windows is updated too) I have several malfunctions. The program won't close anymore even clicking the red X. Using camera luts the screen is increased so I have a FullHD part of a 4K footage. It wraps and replaces all kinds of audiofiles in existing projects and unexpected fatal errors occur.

johnebaker wrote on 6/25/2021, 10:29 AM

@R-Faber

Hi

The LUTS issue is confirmed - and we have seen this before in a previous version of VPX and also Movie Edit Pro.

The issue closing the program appears to occur under specific conditions, which the update, v19.0.1.99 that was released a couple of days ago appears to have fixed for me.

Did you see the post directly above yours?

John EB

johnebaker wrote on 6/25/2021, 10:50 AM

@cmichael52, @MAGIX_Redaktion

Hi

. . . the title tool is frankly not working. You can't move the title box, the duplication of an existing title for seamless transitions is placing the duplicate in another spot . . . .

Confirmed, the Size/Position does not automatically get added as in previous versions, it is now a separate step.

There is also another bug with positioning titles - see clip below

John EB
Forum Moderator

DugsBugs wrote on 6/25/2021, 11:24 PM

@Akademia Best thing to do is contact support and ask them for a link for a direct install for the previous version,
You will need to uninstall what you have now and start again.
Doug

browj2 wrote on 6/26/2021, 7:42 AM

@DugsBugs

Hi Doug,

The instructions and links from Magix to uninstall 13 and reinstall 12 are in the other Important Post from Magix.

@johnebaker

Hi John EB,

About Orientation and Rotation, Size/Position - Zoom, I use the rotation handle mostly on objects like the arrow pointer in my tutorials; the arrow point is adjusted manually using drag and rotation handle. I have a few zoom factors that I use for the arrow and the animated circle as well as zooming in to the screen for consistency. I use the zoom slider and zoom factor a lot.

About what I mentioned, try this.

Select a video object that has no effects.
Go to Orientation and you'll see the dashed line with the handles.
Drag in a corner handle to make the rectangle smaller. This only affects the dashed line, not the image.
Drag the rotation handle and move it to get some rotation. Again the dashed line rotates.
Go to Size/Position/Rotation.
Select Apply Effect.
The new style rectangle with handles will now be smaller than your image, but without rotation. Look at the Width and Height values and you will see that they are not for the full screen but for the handles rectangle, which should still be full-screen.

Another minor bug - on the Startup screen, Load Project - Last opened disc projects, only 2 projects show up (one of which is Unsaved project). I should have 3 projects showing. Do you get the same thing?

John CB

SevCardy wrote on 6/26/2021, 10:25 AM

@tpolakov

I can confirm that fade-ins and fade-outs are converted to jump cuts in exported video when using Intel 630 GPU acceleration or NVIDIA acceleration. This happens whether exporting to MP4 (AVCHD) or HEVC (I haven't tested anything else). It looks like VPX is not passing the correct information to the encoding software.

I've also found that if you try to burn a Blu Ray disk with a menu that has several levels (i.e. a main menu that links to sub-menus), the export fails on the first submenu. This seems to not depend on the GPU used.

It is interesting that if you set the Program Settings to Import=NVIDIA, Processing=NVIDIA, Export= Intel 630, VPX reports in its log that it is using the NVIDIA for export; if you set Import=NVIDIA, Processing=Intel 630, Export=Intel 630, VPX reports it is using the Intel 630 for export. Don't you just love consistency?

Setting Export=NVIDIA always causes a failure on export. But I am using an old NVIDIA 1060 3GB card.

Sev.

dond10 wrote on 6/26/2021, 11:24 AM

Hi All

Just upgraded to VPX13 am also seeing a lot of issues.

1. When first installed I had an auto updated window pop up when starting windows. Googled this and found that it is a know issue from a few years. I had to go to windows settings - apps - auto start to turn this off. This window now pops up when opening VPX.13

2. I have newblue titler pro 6, which worked OK with VPX 12 but NOT with VPX13. On initial start of pro 6 I get a pop up telling me "Titler can't work due to GPU capabilities" at this VPX locks up for a few seconds and then get a message in video window (see screen shot) and in the media pool the titler pro 6 "open titler pro" but is inactive. I have reinstalled Titler pro 6

Dond

johnebaker wrote on 6/26/2021, 12:43 PM

@browj2

Hi John

I get the same when switching from Orientation to Size & Position.

This morning I was working on a new short project and had an couple of issue:

starting with a new project I added 4 images applied fade in/out and crossfade and added a single music track - the preview playback did not work it was 'stuck' on the first image - I added a single video clip and then preview started working removed the video and preview continued to work fine.
On export with the 3 display options set to my NV GPU - I got no HWA on the NV - I changed export setting to the UHD 630 - exported with HWA.

@SevCardy

Hi

. . . . Program Settings to Import=NVIDIA, Processing=NVIDIA, Export= Intel 630, VPX reports in its log that it is using the NVIDIA for export; if you set Import=NVIDIA, Processing=Intel 630, Export=Intel 630, VPX reports it is using the Intel 630 for export. . . . .

This is the same for the earlier version VPX 12.

For h.264/AVC I am finding that:-

if the Intel iGPU is selected for export then for MP4 h.264/AVC, or AVCHD , the Nvidia GPU hardware accelerate effects etc where possible, however the final encoding is done on the iGPU.
if the Intel iGPU is not set for export, then the NV iGPU is still hardware accelerating some effects, however the final encoding is done by the CPU.

HEVC export will use the Nvidia for encoding.

Do note that many of the effects and images titles are not hardware accelerated.

John EB

Scenestealer wrote on 6/26/2021, 6:15 PM

@johnebaker @SevCardy

Hi

. . . . Program Settings to Import=NVIDIA, Processing=NVIDIA, Export= Intel 630, VPX reports in its log that it is using the NVIDIA for export; if you set Import=NVIDIA, Processing=Intel 630, Export=Intel 630, VPX reports it is using the Intel 630 for export. . . . .

This is the same for the earlier version VPX 12.

I am not sure what you mean here John as VPX12 did not have these choices available in the Program Settings. Do you mean if you made similar changes in the Windows Graphics Settings?

And - can you not see any evidence that Nvidia's NVENC is actually being used with H.264 at any stage?

Peter

DugsBugs wrote on 6/26/2021, 6:23 PM

@browj2
Thanks John.
I suggested magix support because they have always been able to provide me with a direct installation file rather than downloading again.
The problem with rolling back is that it won't be the current patch for VPX 12 which is why I like to have the manual installation file stored somewhere.
Unfortunately, it seems Magix have gone the way of most others by only having a FAQ page and no way to email the support desk.
If you have a way around this, I would love to hear it.
It will be a long time before 13 is fixed so I need to know that I can reinstall where I am now in case my computer dies.
Doug

AAProds wrote on 6/26/2021, 10:24 PM

@DugsBugs

It's convoluted, but you can directly message Support using the Support link at the top of this page.

Keep clicking through the appropriate links/pages but when you get to this screen:

type in anything then click "find a solution".

On the next page, down the bottom on the right, is the link to the final page to send a message directly to Support.

DugsBugs wrote on 6/26/2021, 10:37 PM

@AAProds
Thanks for that.
Finally worked it out.
The old days of messaging are long gone.
Doug

SevCardy wrote on 6/27/2021, 11:36 AM

@Scenestealer

OK, screen shots of PerfMon below:

Display settings NV, NV, iGPU

MPEG-4-Export (AVCHD)
Video: H.264; 1920x1080i; 25 frames/s; VBR 19000 kbit/s; HW GPU encoding
Audio: AC-3; Stereo; 48000 Hz; 384 kbit/s
Size estimate: 12230529 kByte

Display settings: NV, NV, iGPU

HEVC-Export (MP4)
Video: HEVC; 1920x1080p; 25 frames/s; VBR 8000 kbit/s; HW GPU encoding
Audio: AAC; Stereo; 48000 Hz; 192 kbit/s
Size estimate: 11478424 kByte

Display settings: NV, iGPU, iGPU

MPEG-4-Export (AVCHD)
Video: H.264; 1920x1080i; 25 frames/s; VBR 19000 kbit/s; HW GPU encoding
Audio: AC-3; Stereo; 48000 Hz; 384 kbit/s
Size estimate: 11478424 kByte

Display settings: NV, iGPU, iGPU

HEVC-Export (MP4)
Video: HEVC; 1920x1080p; 25 frames/s; VBR 8000 kbit/s; HW GPU encoding
Audio: AAC; Stereo; 48000 Hz; 192 kbit/s
Size estimate: 11478424 kByte

And before anyone asks, the size estimates are as reported by VPX when exporting and have been double-checked, although the exact equivalence of case 3 (H.264),to cases 2 and 4 (HEVC) is suspicious! Unfortunately, I didn't let the tests run to completion, so I cannot confirm the actual sizes.

The source files are in the following format (as reported by MediaInfo):

Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 2 frames
Format settings, GOP : M=3, N=12
Codec ID : 27
Bit rate mode    : Variable
Bit rate : 15.0 Mb/s
Maximum bit rate    : 16.8 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
Bits/(Pixel*Frame) : 0.288

Sev.

johnebaker wrote on 6/27/2021, 4:06 PM

@Scenestealer

Hi Peter

. . . . Do you mean if you made similar changes in the Windows Graphics Settings? . . .

Yes, with VPX13 there is no need to set the Windows graphics option - if you do it over-rides whatever you set in the program on the next restart

. . . . And - can you not see any evidence that Nvidia's NVENC is actually being used with H.264 at any stage? . . ..

None - the Video Encode is 0% usage and you can see when the CPU is being used if the iGPU is not being used for the export setting ie using the same project, with export set to the NV the CPU runs at 50 - 60%, set the export setting to the iGPU the CPU usage drops to 30 - 40% and the iGPU shows activity at 20 - 25%.

HTH

John EB

ScreenBytes wrote on 6/27/2021, 5:20 PM

Since I installed the Video Pro X update, so far, I have detected that my acceleration mode no longer works and I am not able to successfully render and save my mp3 audio file from my movie export as I was able to do prior to accepting and installing the Version 13 of Video Pro X. Please help. I have deadlines to meet for several dance projects I am attempting to complete.

Scenestealer wrote on 6/27/2021, 7:05 PM

@SevCardy @johnebaker

Hi Sev

Thanks for you well laid out test results.

Was this just a straight export of an unaltered single clip or were there separate clips and were any effects applied?

Unfortunately you missed out the important setting to answer my query and that was the Export Display setting to use the Nvidia card on export. So, can you confirm what JohnEB is seeing - that there is no activity on the Nvidia with this 3rd option set for H.264 export. You should find that with this setting HEVC export will also show a lot more activity on the Nvidia.

Changing the middle setting 'Processing' should not alter the TM graphs significantly during export because this setting is only for display processing whilst playing the timeline.

Peter

dond10 wrote on 6/28/2021, 12:36 AM

Since I installed the Video Pro X update, so far, I have detected that my acceleration mode no longer works and I am not able to successfully render and save my mp3 audio file from my movie export as I was able to do prior to accepting and installing the Version 13 of Video Pro X. Please help. I have deadlines to meet for several dance projects I am attempting to complete.

Hi ScreenBytes

I think your best bet is to go back to VPX 12 by following this Link to Magix post.

Dond

Scenestealer wrote on 6/28/2021, 1:34 AM

@ScreenBytes @dond10

I am not able to successfully render and save my mp3 audio file from my movie export as I was able to do prior to accepting and installing the Version 13 of Video Pro X.

Interesting that the specification foot note for .mp3 Import states that it can only be achieved as a standalone audio file and not as part of a V/A container:-

"(4) MP3 audio import – can only be imported as an individual .mp3 file, not as part of a video/audio container such as MKV"

It does however state it can be exported but I assume this is again only as an audio file.

Peter