@Zkuggi

Hi.

I take the 'faster interaction' or any 'improvements' with a pinch of salt now as often those improvements rely on the computer having the latest CPU / GPU combinations. Intel Arc is a new design as is the CPU it is embedded to. That means high and low efficiency cores my processor does not have.

I will also wait and see what has been recently broken in the latest release.

[Edit]

I noticed this in the small print.

"* During testing with a 2-minute 4K video, the export time on an ASUS Vivobook decreased from 98 seconds to 47 seconds".

The top of the range Vivobook has the following processing capability here and here

I noticed the specs page has changed quite a bit as well.

At least they have been more specific with the requirements this time around and for that I applaud them.

One more hidden bit of information.

Intel® Hyper Encode Both graphics cards are simultaneously enabled on Intel desktop and laptop systems equipped with an onboard GPU and an additional Intel GPU, such as the new Intel® Arc™. Hyper Encode accelerates rendering, so you can export your finished movie twice as fast* as with just one GPU.

Read more: https://www.magix.com/us/video-editor/video-pro-x/update-history/
 

Ray.

Have they fixed the Section effect (where's the screaming button)?

Read my lips game-ready driver. 😉

I have installed VPX14.

Of course, all settings have been lost, including my linked folders and VST locations.

Folders are set up by default for:

drive:\Documents\MAGIX\Video Pro X14

Before, by default everything went under:

B:\Documents\MAGIX\Video Pro X

without mention of the version. I don't know if this is good or bad.

HitFilm effects - X or Y goes to infinity if keyframed, as before. Magix has bundled the paid upgrade with more Hitfilm effects. I wonder if they are suffering from the same problem.

Export to MP4, 1920x1080, some masking and blurring, but nothing much abnormal - so far, it looks to be much slower than VPX13 as I exported this yesterday much faster. After 3 minutes, movie time is 1 minute 1 second. I've got the Device set to NVidia. I had tried with Intel and it was looking to be the same, so I switched.

EDIT: F1 doesn't work on my Desktop, but does on my Laptop. Gives an error on Desktop.

General impression - it works far better than the initial release of VPX13, but still has most of the same bugs where 13 left off. Exporting looks to be worse.

@AAProds

Hi,

The Section effect has not been corrected, still wiped out if you return to change the crop. It uses the old Size/Position effect so you end up with Size/Position and Size/Position/Rotation effects, not playing nicely with each other.

Camera/Zoom shot has the same problem as the one that I showed recently. It too, uses the old Size/Position effect so you end up with Size/Position and Size/Position/Rotation effects, not playing nicely with each other.

On the plus side, they have added some controls to the Size/Position/Rotation effect.

I would still like to have the Zoom slider back.

@CubeAce

Hi Ray,

Scrolling along the timeline looks to be buttery smooth now.

Under devices, I have Intel UHD Graphics 630 for all 3. Suggestions for what to do with NVidia GeForce RTX 360?

John CB

More export testing - Demo project. Note that the video clips are very low resolution. I changed project to FullHD, once with 25 fps and another adjusted to 29.97fps.

For a 1:44 project, export times were 1:36 for the 25fps project, 1:56 for the 29.97fps project.

I have what I consider to be a high-powered setup. What is wrong with this? I am not getting anywhere close to the speeds that Magix boasts of.

Basically, I have not seen any increase in export speed between my 10 year old computer and this new one or from one version to another, except for slower export speeds on one or two of the versions.

I am not using 4K, just FullHD.

John CB

@browj2

Hi John.

Are you on Studio drivers? I'm surprised the UHD 620 graphics is doing so well on its own.

Your Nvidia card is 55% more powerful than my own and has the latest internal layout. I'm at a loss as to why it is not performing. If you are still using the Power Saving option in Windows I suggest turning it off.

What CPU options are showing? anything new there?

This is what I always bang on about. The increases in performance Magix always quotes goes along with having the newest hardware. It is not due to software efficiency.

Ray.

@browj2

Hi John.

I have not tried out the demo but I did download the game ready drivers for use in VPX 11 and MEP 2022.

In VPX I can now edit 4K without having to use proxy files or pre-render sections. Playback is smoother and the nvidia card is using less vram as well as less motherboard ram is in use at any one time. Export times are not a lot different but again vram and ram usage is lower but 3D rendering and video decoding has increased on both GPUs. Disk read and write speeds have increased during playback and exporting.

As for the missing slider. There is no need for one. Just left click the numbers in either the horizontal or vertical boxes and drag the mouse left or right to increase / decrease the size. Both will alter at the same time.That has been available for some versions now. but not mentioned in the manuals. It is the normal way of working with some third party effects as well.

Ray.

Just left click the numbers in either the horizontal or vertical boxes and drag the mouse left or right to increase / decrease the size.

This is typical of the nerds taking over. For the sake of cleaning up the interface by getting rid of that ghastly and so old-fashioned slider, we are now stuck with something that is not intuitive if you don't know it's there and is harder to use anyway. And now there is no display of the actual zoom value, which was handy to type in. Just like Magix taking away the up-down arrow play functions. The program is getting harder and harder to use as time goes on.

@AAProds

Hi Al.

It is not just Magix doing this. Music DAWS have been slimming down graphical interfaces for years now.

Controls eat up processing power that could be used elsewhere where it is needed more. While I agree with you and prefer sliders, as the programs progress and get more processor hungry, the only way programmers can make real software performance gains is to have less code intensive controls.

This option has been around since the first infusion engine version as far as I remember.

This is from VPX 11

It didn't work as well at first as it does now

Current version of MEP

and is not limited to just that effect.

Any effect that has numerical boxes can be grabbed by a mouse click.

I think since Magix enabled OFX plugins it must have been possible as that is the way to adjust some of those plugins within their interfaces.

How far Magix will take this I have no idea but there will eventually be limits. Graphics cards are getting more powerful generation by generation but also more power hungry. For some countries using lower voltage mains it won't be long before you would need two power leads into one PC to cope with the power draw.

Ray.

Just upgraded to VXP 14 yesterday. As happened for @browj2 all settings went back to default. Inconvenient for me as I have spent much time on creating different window layouts and different export profiles. Should be simple for Magix to keep settings from earlier versions.

Then to the good part. I can honestly say that all actions on busy timeline is much much faster. Render speed seems to have increased aswell. At least for HEVC.

Lucky timing I guess, but the day before the new version came out I finished my 1 hour project. It contained 23 tracks, 4K with Filmconvert plugin applied to all clips. In VXP13 the timeline had become quite slow and "sluggish" once the project became quite large. I exported it to HEVC and total render time was 6,5 hours.

And of course VXP14 came out the day after :) ... I upgraded, opened the project and could immediately tell that the interface was much faster. Night and day difference. Then I exported the video again using same HEVC settings as earlier, except now I told it to use multiple GPU's and the total render time was 2,5 hours.

That is more than 2x faster in exporting!

I am using Intel based Desktop with Nvidia 2080ti. Same drivers in both tests.

So far so good. Looking forward to do my next project to get real sense of how its working.

@browj2 @Zkuggi

I concur fully with the fact that personalised settings do NOT transfer to the new version! Thanks to both of you for the heads-up on this - I only installed the new version today - so was able to take screenshots of the most "important" (to me) of those personalised settings so restoring them was not especially taxing!

For me, this new version has one extremely positive improvement (and something which Magix Support will doubtless be very pleased to hear, because I have sent several emails to the Support Manager regarding this and he acknowledged there was a specific problem on my machine - I included some screen recordings - but they could not explain or reproduce the problem)! Specifically, right-clicking on the Transition icon (when two video objects are butted together) would open the list of transitions but, attempting to make any change to any transition would immediately freeze the program completely. The only solution was to then force-close the program, so losing any changes made to the video. I soon learned to Save and Resave and Save again, very often!

In VPX 14 that problem seems to be no more. I can easily access that right-click Transitions menu and make changes and see the preview and NOT experience the freeze.

However, there is now another problem, with that same menu! I have a number of third-party transition apps installed, specifically from Pixelan and ProDAD (Vitascene). I can easily select a transition from either manufacturer, but accessing the "Settings" option (to make changes to that transition - type, length, etc.,) - although it opens the "edit" screen for the specific app, that screen now does NOT show the original video footage to which one is trying to add the "new" transition. The transition is clearly "active" (the edit screen shows its "effect" on a blank background) but this is not very useful when trying to decide whether to use a specific transition in a specific location in the video. One has to guess what the final version might look like. The actual transition chosen can be "applied" and will affect the video on playback in the VPX timeline but losing the facility to preview the effect is very annoying!

Can anyone else reproduce this, e.g. @browj2 who I know uses quite a lot of Pixelan effects etc?

Another "negative" for me, which may be something unique to my computer: I make a lot of use of my computer keyboard to Start/Stop playback (the Spacebar) and to go to Home or End of the timeline, etc., etc.. I also have a Contour Shuttle Express for use when editing. In VPX 14, suddenly and without any warning, the app will completely stop responding to ANY key press or Shuttle command. The on-screen controls all seem to be still active, but I, for one, do not like having to move the mouse to a specific icon and then click on it to, e.g., simply start Playback. The only method I have discovered, so far, to restore use of my keyboard is to close and reopen the app! Again, not a happy situation, so does anyone else encounter this? If others can reproduce this, I will raise yet another support ticket with Magix (as an apparently reproducible bug).

Jeff

@emmrecs

Hi Jeff,

Well, they've messed up the third party transitions. I get what you get with Pixelan and Adorage and some even more strange ones, like switching from a Pixelan transition to Adorage then trying to open the settings opens Pixelan instead of Adorage, and things like that. In Pixelan SpiceMaster 3, the video doesn't even move.

In the last go-round, the screen in Pixelan SpiceMaster was black. Try putting a SpiceMaster transition between the second last and last objects on the timeline. Black screen in SpiceMaster. This then happened between third last and second last.

I managed to crash VPX twice by clicking on Adorage.

What a mess!

Please raise a ticket with Magix. They will try to blame proDAD and Pixelan.

BTW, you can use the left or right mouse button to click on the transition icon to open the menu.

You may want to check keyframing X or Y for any HitFilm effects, like Zoom Blur. Y usually goes to inifinity upon moving the playback marker back and forth. This has been on my bug list for a few years.

So far, no problem here with my ShuttlePro. You may want to try attaching the link to the location of the new VPX14 executable.

John CB

@AAProds

Hi Alwyn

. . . . Just like Magix taking away the up-down arrow play functions. . . .

I can't think of any other video editor I have used, that used these for forward/reverse playback, the 'industry standard shortcuts' for playback are space bar, J, K and L keys.

@emmrecs

Hi Jeff

This may actually be a Windows issue - I occassionally get the same non responsiveness with web browser, image editing (PSP 2021 Ultimate) and File explorer.

John EB

@johnebaker

. . . . Just like Magix taking away the up-down arrow play functions. . . .

I can't think of any other video editor I have used, that used these for forward/reverse playback, the 'industry standard shortcuts' for playback are space bar, J, K and L keys.

John, that shouldn't be a reason to remove a feature that is quite handy and easier to use than JKL.

If we're going industry standard, we should redo the timeline so we have dedicated video, audio and title tracks. A program stands out when it has nifty features that make life easy for the user. Magix is removing the things that make it easy and simple to use.

@browj2

Hi John.

Guess what??? I just created a support ticket about the problem with third-party transitions not displaying in the edit screen. Having received the acknowledgement from Magix I thought a couple of screenshots might help so I created an extremely short project (two clips), selected to use a Vitascene transition between them, went to Settings (Vitascene opened), I selected a transition at random and the edit screen played back the first clip but not the second!!! So, "half" of the problem seems to have disappeared.

Interestingly, when I wanted to test whether Pixelan did the same I discovered I had to first change the transition to a Cut (no fade) before I could select Pixelan and access its settings, which also showed the first clip but not the second!!!

Oh the wonders of computers and Magix software. I wonder whether the second clip might decide to be visible if I repeat the exercise tomorrow?

Jeff