@Former user

Hi Gid.

I was experimenting with export formats to see if there were any advantages to any of them.

The export to mxv for my 41 minutes of files only took just over an hour so not actually a lot longer than for some other formats on my machine. The export used the Intel GPU more than the nvidia so may explain the difference in export times from my machine over yours.

I had also added alterations to each clip so that the overall look of the project looked the same from scene to scene and using a lossless codec I thought would preserve detail for further editing. It produces files equal in quality to exporting to the lossless avi format at a much reduced file size which my machine can't play back smoothly at all, either from within MEP, VPX or even VLC.

Indeed, from within MEP the mxv file is flawless in playback and immediate even when adding additional effects it hardly impacts performance, but trying to export mxv to a more expected every day codec has been unobtainable, with or without adding additional effects.

So what is the point of having mxv? If it can only be played back in either MEP or VPX but then not able to be then re-rendered into another format for use? Or can it be my system specs are not up to the task for some reason? Is the file simply too large? I will try other options to try and see.

What I did notice when trying to export the mxv file was an exponential increased spike from the project drive exceeding 440MB/s read for a brief half second before the program crashed on each attempt.

Why even bother?

Sometimes my projects get so complex my machine falters and editing becomes impossible to accurately time position some clips so I export some clips with effects just to re-import them and then remove the original clip with the effects added to lessen the load within the project. That can mean generational loss, so using a lossless format makes more sense if I could get it to work.

Just out of interest, the best export format I've found so far for quality is using wmv which will be my next experiment and see if that file format an be re-imported and then exported again. Also if the playback performance of wmv files are as good as the mxv files.

@CubeAce Ok i understand the want for lossless exports, 👍 I did export that short mxv i made into an mp4, but that was very short with fx's so not a good example,

Yeah the difference with intel & AMD is always interesting, I do sometimes wonder if i made the right choice, but it's too late now,

I just set that 25mins 4k exporting as mvx, i added several random colour changes & some other fx's, 35mins to go n it looks like this, I'll get back to after i've tried importing it & exporting as a different format 👍

@CubeAce 25mins 4k 3840x2160 exporting as MXV

MXV file 50GB, imports in Magix no problem, but won't export as MPEG-4 or HEVC,

WMV export estimated 2hrs, (pressed cancel), AVI gave a little warning msg & no render, 😒🤷‍♂️🤦‍♂️

I tried the MXV to MPEG-4 export again after closing & re-opening MEP, same crash/fail msg as before,

@CubeAce, @Former user

Hi Ray

. . . . 41 minutes in length using MP4 files at 25fps at 1920 x 1080 . . . export as an MXV file of approximately 42.4GB . . . . . . . .

25mins 4k 3840x2160 exporting as MXV . . . .

I use MXV files quite extensively, however not to that length, mainly shorter < 2 mins and have not had a problem with them.

Ray - are you just testing or actually going to use the 41 min MXV file as a basis for projects?

John EB

@johnebaker @Former user

Hi John.

I think you have both answered my question. That exporting to another format using mxv files is possible but maybe not at that size or possibly also not edited further. IE, not cut up and re-ordered. I will do further testing using shorter clips but some of the original files are 4GB to start with and 16 minutes long. They are only HD and not 4K in this instance. I'm still not sure whether the access violation is due to a lack of enough memory or the speed the project drive is being asked to work at and topping out. Gid has three times more motherboard memory than my system and five times more Vram.

I was hoping to use xmv files but I do have other workarounds.

Hi Gid.

I suspect in this instance, the difference in export times comes down to you trying to convert 4K files and not HD files, rather than the difference between a Ryzen and Intel processor based system. My export times for the files on inspection was just over half the total length of a given file. So a 4 minute clip is taking around 2 minutes 14 secs. Maybe you should try some HD files instead.

Thanks for both your input. It has given me things to think about.

Ray.

@CubeAce yeah i used 4k, that's what i normally use but i thought because like you say i have a bit more memory i'd give it a bit more to work on & i wasn't really thinking, .. my pc memory that is 👴😂

2.49mins of assorted HD 1920x1080 clips, exported as MXV,

MXV 1.12GB file imported back in MEP, export attempt at MPEG-4, crash/fail

@CubeAce, @Former user

Hi

I should have checked the patch level for the date of my last project on VPX 13 😳😟. I was running 19.0.1.123

Looks like a bug may have been introduced since then, with VPX v19.0.141 with the same MXV files I get the crash irrespective of the GPU settings and resolution.

Added:

Tested MEP 2022 on my laptop and could replicate the issue, however on adding a MP4, ~ 12 secs long, before the MXV files I could export the project with no issue.

After this, with repeated closing and starting MEP 2022 and adding just the mxv files I could export with no issues - tested 7 times to make sure ????

John EB

@johnebaker @Former user

Hi John.

I opened my project using VPX 11 and exported the whole project with no issues. EI using the one mxv file edited and re-ordered the chopped up file. Export took two minutes longer than the length of the edited project length with maximum quality settings for the H265 export.

Will recheck your findings with MEP tomorrow and add a short mp4 file to the beginning sometime tomorrow.

Would this still be considered a bug with MEP 2022?

Ray.

@CubeAce @johnebaker

I would have thought that if Magix can't even use it's own proprietary video format, that is definitely a bug.

I can confirm that this is indeed a bug: I tried to export an old 18.2gb MXV I had lying around (waiting to be edited 😉) and MEP 2022 immediately crashed, Exception.

MEP 2021 exported with no issues.

I put a short MP4 at the start of my timeline but it still crashes on export.

@AAProds @johnebaker @Former user

Thank you for joining in Al.

I can confirm your findings. Adding a short mp4 file to the beginning made no difference in MEP 2022.

Now I am using the studio drivers. I will try the game ready drivers later.

Can't wait for MEP 2024 😏

@CubeAce

Can't wait for MEP 2024

What is that song, "things can only get better!" 😂

@CubeAce, @AAProds

Hi Ray, Alwyn

. . . . What is that song, "things can only get better!"  . . . .

Do you mean this one:-

Some things in life are bad
They can really make you mad
Other things just make you swear and curse
When you're chewing on life's gristle
Don't grumble, give a whistle
And this'll help things turn out for the best

or Kylies?

Back to the topic:

Definitely a bug and as far as my testing goes VPX13 is not behaving the same as MEP 2022 did with the mp4 added and Photostory 2022 v 20.0.1.105 does not crash at all.

None of the above crash when previewing the MXV files - the issue is in the export.

Added: Bug report filed with crash log and link to this topic.

John EB

I was thinking of Howard Jones.

Hard to "give a whistle" when you're staring at a Exception box! 😃

@AAProds @Former user @johnebaker

Thank you all for testing this for yourselves.

The game ready driver does not seen to alleviate this problem and I'm sure Magix will be delighted with yet another new 'bug report' this late in the development of the program.

I am beginning to wonder if some of these 'problems' are not down to Magix trying to get the programs ready for official Windows 11 support and the ability to make use of the new Intel CPU architecture of big and little cores or "chiplets" of their new Alder Lake processors and intel® iris® xe graphics chips which would find performance benefits with Windows 11 if or when the program gets tuned to run with it.

VPX has it still listed as coming soon.

Which as far as I'm aware has been there since VPX 13's introduction.

Still.

Reported as bug.

Ray.

@johnebaker @Former user @AAProds

I have had a reply from the Magix team. It has been forwarded to the development team along with my crash report.

Ray.

Greetings,

I appear to have come late to this party, for which I can only sincerely and profoundly apologise. I can confirm the crash bug with MEP. However that's not really the reason for my writing.

You may already know this little nugget and I'm not if sure it's really useful but it may be to someone, somewhere at sometime.

MXV files can be opened in Magix Photo Manager Deluxe and can be exported as WMV, MXV, AVI, RM and MOV. Please note the AVI export includes Lagarith (if installed) up to 4K but the final AVI crashes Photo Manager.

Now it does mean spending several pennies on Magix Photo Manager and so I leave the usefulness of this information to the reader.

AndyW

If you already know this then ......

And of course it's only really useful until Magix development team deem to squash the bug

@CubeAce, @me_again

Hi

. . . . I have had a reply from the Magix team. It has been forwarded to the development team . . . .

Same here.

. . . . Which as far as I'm aware has been there since VPX 13's introduction . . . .

I am not so sure on this as I have been working with MXV files throughout January with no issues, it was only when I updated, as I previously commented, that the issue arose.

Hi Andy

. . . . MXV files can be opened in Magix Photo Manager Deluxe and can be exported . . . .

A useful nugget of information, I got PM in a Humble Bumble bundle - try saying that fast .

John EB

@johnebaker

Hi John.

. . . Which as far as I'm aware has been there since VPX 13's introduction . . . .

Was referring to the image above that quote and the support for the newer Intel IGPUs has not been officially added.

Ray.