@Former user

Hi.

Are you talking about proxy files or preview rendering?

Proxy file creation is controlled by the setting in the movie settings section.

Preview rendering can be forced by selecting a range with the range markers and using the lightning symbol but is only useful for an unaltered smooth playback and not actual editing.

Ray.

Hi,

Thanks for your reply. The problem is in the proxy files creation. I have like 45 clips in this project and Magix made proxy files only for like the first five clips.

Best,

Sami

@Former user

Unfortunately, a known issue. I don't know if it's been reported as a bug but it is very annoying.

https://www.magix.info/us/forum/proxy-rendering-was-skipped-trial-magix-movie-studio-2023-platinum--1307879/?page=2#ca1833343

@Former user @AAProds

Hi.

There could be more than one reason proxy files are not being created according to the manual but I'm not sure I understand all of them.

Ray.

@CubeAce @Former user

Lost in translation: "memory" should be "storage". Proxys (MXVs) can take up as much space as the originals.

@AAProds

Hi Al.

Whenever I load a project I have to wait while the loading blue bar travels along the start bar of the program window and while objects get occupied with images and wave forms. So does 'Storage' in this instance refer to disk space as temp files are created for the running project and if so would that indicate C: drive space?

Ray.

Thanks guys, I doubt that the problem is free storage space. I have free space for like 10 more projects like this, so I think storage is not the issue.

Could it be that Magix is quite unfamiliar with these "new" type of GoPro videos (with the 8:7 aspect ratio) that the porgram somehow thinks that these are smaller size videos?

Thanks,

-Sami

One quote that I found quite resonating from other post:

"Lets talk about the proxies.
The system on how proxies are generated is absurd.
It triggers the generation on a 1920x1080 16:9 clip, but NOT on a 3840x1646 cinemascope clip.
One simple question. WHY? It suddenly does again on 3840x2160 resolution.
Same codec, same scene, same frame rate. Yet Magix refuses to generate a proxy file."

I am struggling with exact same issues here as this guy. I think Magix confuses different aspect ratios when creating proxy files.

Link to post: https://www.magix.info/us/forum/please-rework-the-proxy-generation--1309659/

-sami

In addition, I have created a service request for Magix. I'll keep you guys up to date on what they reply.

-Sami

@Former user

Hi.

One way to test your theory would be to create a new project and manually type in the resolution of those video files along with the frame rates in the project movie settings. Then only import those types of files and see if proxies are created. If they are then it is a question of mixing aspect ratios of imported clips which traditionally has not been a method of video creation and be causing the problem. Normally such changes to screen ratios have been added in post by cropping.

Ray.

@CubeAce

Thanks, I think I'm going to test this as soon as possible.

My way of creating videos, is that I have the different types of aspect ratio clips in my timeline, and with the section tool, I apply 16:9 to all my clips in the timeline, and then I have this "extra space" vertically to adjust and reframe my footage. For example if a person is cropped out in their head or legs, I can adjust the frame to make the person fit to the 16:9 screen.

So to speak, I may not follow the "traditional" way, but if all would work fine, then my method would not be the issue. I know it would be much much more simpler to just shoot all the clips with 16:9 aspect ratio, but then if my GoPro was sligthly misaligned at one clip, I would not have the option to "save" the clip by re-adjusting.

-Sami

@Former user @CubeAce

I venture to say mixing resolutions have nothing to do with this bug. I quote from my post on the previous topic:

 I have just tried to import, with Proxys activated, two UHD files from my phone, with exactly the same parameters, taken 5 minutes apart.

Proxys were created for the first, but skipped for the second! Needless to say, the first is nice and responsive and the second slow and jerky.

Edit: I tried a new project and dragged in the file that skipped the first time; MMS 2023 created a proxy for it. I then dragged in the first file (the one that had proxies created for it) and this time, it skipped. So it seems that the first file onto the timeline will be proxy-fied, whereas the second won't.

@Former user

So to speak, I may not follow the "traditional" way, but if all would work fine, then my method would not be the issue. 

That is certainly the way I have done, and do, run Magix. That is precisely what Section and Camera Zoomshot are for, and I have used various file resolutions in many projects without issue.

Just for a giggle, I tried a few more Proxy imports of various resolutions and orientations; every time, Magix proxys the first import, but skips the following imports (I used 3 files in am movie).

@AAProds @Former user

It could be because I only ever use one type of file for video (MP4) but I just changed a project I have been working on without proxy files and selected 'Use Proxy files' in the Movie Settings in VPX 14 (I don't have MS2023) and upon closing I got the 'Do you want to create proxy files' option and I pressed yes. The corresponding H0, HDP, and wav files were created for every file already in use and importing more clips produced more proxy files.

Looking at old projects where I did use proxy files in older versions of both programs, the same file types exist.

Ray.

@Former user

@AAProds @CubeAce

Hi.

Are you talking about proxy files or preview rendering?

Proxy file creation is controlled by the setting in the movie settings section.

Preview rendering can be forced by selecting a range with the range markers and using the lightning symbol but is only useful for an unaltered smooth playback and not actual editing.

Ray.

Hi,

So I also tried the prewiev rendering option, did not work too well, I saw a very slight improvement on playback.

I also tried all the options in the ligthning symbol, also the "reduce frame rate" option. None of them worked too well in this project.

I managed to do really well with my previous video project using the proxy files for editining, that went really smoothly and the video quality was pretty much the same. (4:3 60fps 4k video). But now, without the proxy files, these 8:7 60fps 4k clips are just too heavy for my laptop.

I haven't heard back from Magix support yet. Hopefully they reply soon.

I would not like have to solve this problem by getting maybe another video editing software or buying new laptop...

It's sad that because of some proxy- creating- error, I cannot take full advantage of my new GoPro and it's features.

Thanks guys tho, I really appreciate all the help you've provided so far.

-Sami

@AAProds @Former user

Hi.

I've been thinking about why the program may not think it needs to make proxy files and may be related to seek times as well as file sizes. I know a lot of people choose not to copy the files in use to their project folders but are happy to use the original files in their various locations. If those files are on different drives the seek times may well be a lot lower than if they reside on the same drive and the need to make them smaller and faster to read may not be as necessary as if all the files were in the same location. I always have the files copied to the working project folder and have not suffered the inability of having proxy files created. I also always drag the files from within the import section of the program. I don't know whether that would make a difference or not but I then always have to wait for the proxy files to be created. I never start out using proxy files. That I only do if the project starts to slow down to an unusable point. Then I change the movie settings and then have to wait ages for the files already in the project to be rendered.

Ray.

@CubeAce

Ray, it's a bug with 2023. MEP 2021 proxied every file you bring in. MMS 2023 will proxy only the first file, even after swapping the import sequence, from files in that same folder, as I have previously pointed out on this. The file location is irrelevant.

In addition, when I try to drag in multiple files, if Proxy is activated, only half the files come in; the first gets proxied and the second not, as above, but the following two files are not imported at all. Switch proxies off and all files come in correctly.

The whole proxy feature is currently borked in MMS 2023. It's fine in MEP2021.

Could you please put in your signature your program names; makes it easier if we see 'MEP 2022" as opposed to "21.0.2.138".

@AAProds

Hi Al.

I have never bulk imported files into a project so that I wouldn't know. I assume VPX 14 has the same problems as MS2023. At least as far as I can tell they seem to. If MS 2023 is behaving differently is everyone with the program suffering the same problem? It could be, I don't know. I have my own different issues with VPX14 but not creating proxy files for all imported videos is not one of them.

I don't know if you have ever noticed but take the first two digits of the program number and add plus one and you get the year designation . So 20.0.1.80 becomes 21 etc.

Ray.

@CubeAce

I don't know if you have ever noticed but take the first two digits of the program number and add plus one and you get the year designation . So 20.0.1.80 becomes 21 etc.

Ray, I wouldn't expect somebody who is not very familiar the system to know that, and in any case, it doesn't work for VPX. It would just make it easier to understand/see what programs you're using, that's all. If you choose not to put it in, that's your call.

I wouldn't necessarily be comparing the code of VPX 14 with MMS 2023 (which you don't appear to have).

PS: your signature doesn't say you've got VPX 14. 😉

@AAProds

PS: your signature doesn't say you've got VPX 14.

Al, that's because every day I'm still in two minds whether to keep it on my system or revert back 🤣🤣

Ray.

@CubeAce

Hi Ray,

I don't understand why you would remove VPX14. It works fine here. If MS2023 works fine, then VPX14 should work fine. Something else must be going on.

John CB

@browj2

Hi John.

On my system.

VPX 14 is not working with Boris Effects Title studio correctly or even effectively and has caused crashes.

VPX 14 does not remember some settings applied in the audio mixer but not all.

VPX 14 is not as compatible with older VPX projects as VPX12 is due to the changes made with Size Position Rotation as any previous set movement of size position is no longer correct.

VPX 14 has problems with audio from video clips that are repeated relatively close to each other or uses sections of a video clip that are re-organised into a different play order resulting in audio distortions or glitches. Further audio problems are present with butting two different sound tracks resulting in very low but audible click where they are butt joined as opposed to cross faded. Even fading in or out of the sound track does not prevent this.

Selecting a section to repeat play using the project markers often results with the video showing a frozen image after the first play through.

There is no combination of selection within Import, Processing, or Export that I can find to overcome any of the problems with VPX 14 I have posted above.

None of the above problems happen with VPX12 or MEP 2022.

I'm willing to except this may be down to my computer now being at the lower end of the needed specifications to run the program now with the file resolutions I am using and that future upgrades for me will make no sense until I upgrade my computer. I do not have Movie Studio 2023 for that reason.

Ray.