Hi,

This also occurs with the 21.0.1.205 (UDC2 /version of video pro x15 )
like this "test version" that I downloaded, logically I didn't test it for export, just like I did with the movie studio version. Steps to test: create a simple project in VMS 2023, make 2 videos of 15 minutes each, containing (more or less) in each video 4 clips (mp4), 4 png images, 3 wma audios. In this same project, generate another video joining these 2 videos (which will total 30 minutes). Export to mp4. Then go back and try to watch it inside the VMS player. In my case, there was the error reported above.
Continuing, I closed the VMS, loaded the video to x15, opened the VMS project, and saved it in another folder as a separate project. Right after this, when I went to play it, it displayed the out of memory message. See that at this moment there was only VPX open!
It's a parenting bug!

I closed the program, entered the project again and then it worked (but I can't test it for export because the limit is 3 minutes)

Thanks!

@Roberto-Goncalves

Hi Roberto.

Although this warning is coming up as a memory problem it could be that the program is running out of C: drive free space. While rendering, the program produces temp swap files which can get very large. If they can't be written to disk then the data may get stuck in memory, unable to do more. Personally I have never allowed my C: drive to have less than 10GBs of free space so that doesn't happen.

I have no idea if this is what is happening in your case but it is a possibility.

Another possibility is your graphics driver is not up to date. It needs to be at least version 27.20.100.9466

Ray.

my free c:\

@Roberto-Goncalves

Are you using any of the effects in the projects?

If so which ones please?

How many tracks are you running? I see there is at least one more.

How many different file types? I count at least four on the tracks I can see.

What happens if you set the program settings to Import, Processing, and Export settings all to use the CPU rather than GPU?

Ray.

Hi,

(1) No effect!
(2) nothing extra, just videos and images distributed in 6 tracks only totaling 32 minutes (in another test 30 minutes, but it doesn't make any difference).
(3) configured everything (import,process,export) for CPU

" The big problem with Magix is that the problem is always someone else's! "

@Roberto-Goncalves

Hi

. . . . " The big problem with Magix is that the problem is always someone else's! " . . . .

😂

Sometimes it is, if the problem can be replicated then it is not. Unfortunately I cannot replicate the issue adpoting the same track layout as shown in your images.

However the one thing does seem odd, and whether it affects the issue or not, I do not know as my attempts to replicate the issue failed to do so, is that the layout of tracks in MMS 2023 is mimicking that of Vegas MS.

In MMS the tracks are upside down compared to Vegas MS tracks.

Track 1 is the background track and is the one which normally has the background video/images on it. VMS is the opposite.

I would post an image of my test project test track layout to see if I could replicate the issue using both layout styles, however the forum upload is refusing it.

To eliminate whether this is the cause or not, put the images, and video if any, on tracks 1 - 4 and the audio files onto higher track numbers eg tracks 6 -10 or more.

HTH

John EB

@Roberto-Goncalves

Well the only thing I can do is go through every step one bit at a time. We can now see you have enough disc space on the C: drive.

I have just noticed on one of your images that the warning also has '26 days remaining' on it.

Are you running the demo?

If so it is limited to a three minute export.

Ray.

Yes! trial version of VPX as per 4 comments above.
As I'm going into a long project and I'll have to incorporate effects and quality. I'm evaluating whether to return to Vegas (now Pro) or move up to VPX. I consulted Magix sales and I can upgrade to Vegas or VPX where my expectations are.
(this is because I left VegasMovie Studio 17 and have already adapted well to Magix Movie Studio)
3 days ago I increased my notebook's memory to the minimum prerequisite (16GB) that was missing! A positive point on the Magix forum is that you are very active, always with good will and this is very good! Thanks!

@johnebaker

Hi John.

I have found that when the site refuses to upload an image, if I shut my computer down (reboot) then I can upload images again.

@Roberto-Goncalves

Hi Roberto.

For what it is worth, I find the VPX / MMS are more stable on my system than Vegas. I prefer the VPX monitor setup and track layout. I run both programs. Both have their own strengths and weaknesses. I also find Vegas exports slower on my machine but different people with different systems may find the opposite. What I like about Vegas is it's effects flexibility but it is more complex and with complexity comes the ability to make more mistakes. I find VPX / MMS more intuitive personally. With Vegas I spend more time reading the manual.

Ray.

@CubeAce read the manual?? NEVER!!!!!

@Roberto-Goncalves

Hi,

Looking at your early images, the out of memory error indicates that it is for the Logitech headset. That is strange.

Try going to Program Settings (shortcut Y), Playback tab. I presume that the Wave driver is selected. Try changing the Output device to something. What are the Audio buffer settings (show us screen shot?

Under Device Options tab, what options do you have under the dropdown for Processing and Export? Maybe try a different setting if possible.

John CB

@Reyfox

Hi.

Some manuals are not worth reading such as the one for my motherboard if I am interested in setting up the bios. That I can read and still not understand what a particular setting will do or it's consequences of altering. For that I think I would need to do a degree course first. 😅

Never often means missing bits that could have saved me time or miss an alteration made to a new version of a product. Assuming the alterations are actually in the new manual.

I miss having paper manuals but in a world where the consumer becomes the ultimate beta tester to a new program rather than companies having rigorous in house testing regimes I suspect a paper manual would need countless revisions to it to be relevant.

Then if you dare to use more than one companies product there is the language barrier. Either introduced because one company has tried to copyright the terminology of an action or cultural differences. Meanings may seem similar but the actions taken may be different.

Instances I have seen.

Cut / split / splice

Render / export

EQ / RSQ / Tone control.

Combine / Link

Copy / duplicate

Making a cut in one program may make a break of one object into two while in another program may remove it from the timeline.

So in short I do personally find manuals useful. 👍

Ray.

Hi,

It's not a hardware problem.
In my understanding, there was no thread management involved to relieve unused memory, from the moment "two videos" were preliminarily imported and then their objects were pasted to a new video, within the same project. Exactly here (as I reported to Magix support) a "free memory" should have been performed, which I assume did not happen! And if there was, there may have been what we call a memory leak!
Less bad is that exactly when the program prevents either playing the video or exporting it, it allows the user to save the project/videos involved. You will avoid losses! Logically I did this! I had to close the program. I reloaded the project again and from then on it worked as expected. Logical conclusion: memory management with the threads involved! This is the responsibility of the programmer and is not difficult to resolve. Just the knowledge you must have! and also good will!

Thanks!

@browj2 @johnebaker @Reyfox @browj2

Hi John.

Good catch!

Haven't we seen in the past problems with other Logitech products such as their webcams on the forums?

Ray.

@Roberto-Goncalves

Hi

. . . . no thread management involved to relieve unused memory .... a "free memory" should have been performed, which I assume did not happen! And if there was, there may have been what we call a memory leak! . . . .

Are you using the default setting, 10, for the Undo / Redo option in the program settings, System tab.

. . . . when the program prevents either playing the video or exporting it . . . .

Have you tried using the Empty undo and cache memory option under the Edit menu before playing/exporting the project?

John EB