@Cloudglow A laggy interface could also be caused by saving your projects into a OneDrive synced directory.

"Exactly which version of MM do you have? The workscreen you show is definitely NOT that for the latest, version 31.0.2.21 (MMM 2023)."

I have the latest version and as I mentioned my drivers are updated.

"it does not appear to me that the GUI is "laggy"!"

Well it is, very. When scrolling I can let go of my mouse and it still keeps scrolling until it completes the commands which came from my mouse wheel.

Here's 8 tracks example:

@daniel-diaz

Your post to this thread has been hidden because it is not relevant to the original question. Please do not hijack another user's thread in this way but rather create a new thread with details of your question.

And please DON'T POST ALL IN CAPITALS! Its' considered to be the forum equivalent of SHOUTING.

Jeff
Forum Moderator

@Cloudglow

I have the latest version

But the Transport Bar you show is NOT the one in version 31.0.2.21 so please check under Help>About and tell us exactly which one you have.

In the video you most recently posted, because we cannot "hear" your mouse clicks etc., it is impossible to "see and hear" what you are seeing and hearing. To me, there is nothing "laggy" about the scrolling; it is rather "jumpy" or "stuttering" but that is purely a graphical issue; on my machine (you can see my system specs in my signature) I don't see that stuttering so it is certainly not a problem inherent to ALL installations of MM.

Jeff

EDIT: my apologies! Having looked again at your video I can see I was wrong about the Transport Bar; that is the layout used in all recent build of the program.

I also got my first "out of memory" warning when using MMM, earlier it was just WinRAR which I used when Music Maker, it complained about not having enough memory for using my compression settings.

It was clear to me then that the MMM has also some memory leak problem and now the latest error which came up and closed MMM completely prooved that. Sad really. just to be sure, I checked Windows memory usage and it was 24% (6GB+2GB RAM disk reserved) used of my memory, MMM was using ~2GB, so there was like ~24GB RAM available.

@Cloudglow

Hi

. . . . When scrolling I can let go of my mouse and it still keeps scrolling until it completes the commands which came from my mouse wheel. . . . .

If the mouse scroll speed is set too high you will get 'overrun' as you are experiencing, the interface rewriting is not keeping up with the number of 'lines' being told to scroll.

In Windows settings what are the Mouse scrolling options set to?

These are mine on Windows 11, if you are on Windows 10 they should be similar.

From you images above the fonts look very heavy, is the monitor resolution lower than 1920 x 1080, or in Windows settings is the Display, Scaling option is set to a value higher than 100%.

. . . . it complained about not having enough memory for using my compression settings . . . .

What is the size of the SSD drive and how much free space does it have?

John EB
Forum Moderator

My scrolling speed is set to 4, 3 is the default I think. It doesn't make any difference.

"If the mouse scroll speed is set too high you will get 'overrun' as you are experiencing, the interface rewriting is not keeping up with the number of 'lines' being told to scroll." - Couldn't have said it better myself, that's exactly what's happening, but like I said it doesn't matter if I change scrolling speed to 1, same behaviour. The interface drags behind and that's what I call lagging.

I'm using 1440p monitor with 1920x1080 and it has 125% scaling. Changing to higher resolution makes it even worse due to more samples on acreen.

My SSD has ~300GB free space. My mechanical drive where the soundpools are has ~800.

@Cloudglow The "out of memory" error message is just a generic error message that is shown if a VST cannot be loaded.

@SP

My project was fully loaded and I wasn't handling any VST.

@Cloudglow

Hi

With respect to the lagging issue see this comment from another user.

The issues you have posted in another topic regarding the MIDI Editor and keyboard shortcuts would suggest that the MIDI Editor does not have focus, click on the MIDI Editor pane and then try the keyboard shortcuts.

From the same post:

. . . . If the function "Rewind" is meant for reversing a sample, I'd suggest "Reverse" as the new name . . . .

'Doing a rewind' is common term in the music industry, DJ'ing in particular, for 'Reverse' and has been around for a very long time.

John EB
Forum Moderator

"'Doing a rewind' is common term in the music industry, DJ'ing in particular, for 'Reverse' and has been around for a very long time."

I see, I hope Magix get it working, until then an external software need to be used to accomplish rewinding a samlpe.

"The issues you have posted in another topic regarding the MIDI Editor and keyboard shortcuts would suggest that the MIDI Editor does not have focus, click on the MIDI Editor pane and then try the keyboard shortcuts."

Nope, doesn't work. Even when the MIDI window is 'active', it chooses the "move" tool in arranger sometimes. Also once you start placing MIDI notes, the MIDI window gets 'deactivated'. Shortcut keys also work sometimes when the MIDI window is 'deactivated'.

@Cloudglow

Hi

For the lagging in the program see this solution it it also applies to Music Maker.

. . . . until then an external software need to be used to accomplish rewinding a samlpe . . . .

Rewind works on audio samples and imported audio files, for me with Music Maker v31.0.2.21, however on some samples the waveform disappears as seen below.

John EB

Yes, apparently it can work on some samples. Not much help though if the majority of the samples are no go.

Great! Now the MMM started putting .HDP files to my D:\Documents\Magix Projects -folder when there's no such path in settings. It probably uses some old path in Windows registry.

Same kind of thing happened when i was istalling MMM, one path was greyed out and I couldn't change it. So I had to go Windows registry and delete the path from there.

This is not how a software should behave, my god!

EDIT: Seems like if I use Rewind on sample, it creates the .HDP in the wrong folder.

@Cloudglow

Hi

Which edition of Music Maker 2023 do you have Plus, Premium or EDM?

From:

• the Folder settings image above, it looks like the computer has a second drive labelled D: is this correct?
  
  Has the Documents folder been redirected to this drive?
   
• your previous posts in the forum I see that you had an earlier version of Music Maker 2019 (EDM edition ?), was this installed on the same computer

. . . . one path was greyed out and I couldn't change it. So I had to go Windows registry and delete the path from there. . . . .

Which one?

The program installer will pickup existing folder paths from prior installations of older versions of the program which in this case would suggest that the previous installation the user file paths were changed, this often necessary for some users when the SSD drive is relatively small.

. . . . it creates the .HDP in the wrong folder . . . .

Which folder are they being created in?

John EB

"Which edition of Music Maker 2023 do you have Plus, Premium or EDM?"

I'm using 2023 Premium. Aren't they all the same? Only difference being soundpools and some features you get when buying. Also different editions wouldn't create different folder structures. Don't really see the relevance here.

"the Folder settings image above, it looks like the computer has a second drive labelled D: is this correct?"
"Has the Documents folder been redirected to this drive?"

Yes & yes.

". . . . one path was greyed out and I couldn't change it. So I had to go Windows registry and delete the path from there. . . . ."

"Which one?"

I think it was the soundpools path*. I had to go to registry and delete the path from there. Only then the greyed part got 'unlocked' and let me change in the new path. Point is that it shouldn't be greyed out, there's no reason.

The program installer will pickup existing folder paths from prior installations of older versions of the program which in this case would suggest that the previous installation the user file paths were changed, this often necessary for some users when the SSD drive is relatively small.

Yes, exactly - that's why it shouldn't be greyed out.

"your previous posts in the forum I see that you had an earlier version of Music Maker 2019 (EDM edition ?), was this installed on the same computer"

Yes, I had Premium 2019 which I upgraded tp 2023 Premium. The path* which was greyed out was from that installation and I needed to change the path, but MM said NO! No you won't.

". . . . it creates the .HDP in the wrong folder . . . ."

"Which folder are they being created in?"

It creates them in D:\Documents\Magic Projects\ -folder - I have subfolders there just for avoiding the mess and so that I know where the files go. In this case all .HDPs should go to D:\Documents\Magic Projects\Exports\ -folder as put in the MMM settings. Other .HDP files which MM creates go there without problems.
I tried some more and yes, it's definitely the "rewind" function which doesn't play by the rules so to speak and
creates those .HDPs in wrong place. Maybe it gets the path from Windows registry, but when the MM has settings especially for defining the folders paths to use, they should be then used, not Windows registry.

Now again it's very hard for me to start searching the registry kay which to change/delete just to get the files go where the main program tells them to.

@Cloudglow

Hi

If you let Music Maker 2023 replace MMM 2019 without fully un-installing MMM 2019, all its Soundpools, and clearing all the remnants of folder and registry fragments left behind before re-installing, then the folder locations will be re-used and in the case of the folders with existing content in them eg Soundpools, locked (greyed out) so they will still be available for MMM 2023 will use.

. . . . Also different editions wouldn't create different folder structures . . .

In theory they should use the same folder structure, however if you did not manually created the EDM subfolder of the projects folder, then the previous EDM edition must have done that.

. . . . In this case all .HDPs should go to D:\Documents\Magic Projects\Exports\ . . . .

No they should not, as I previously commented they should be, by default, in the AudioTemp folder. The .HDP, and H0 files if you have them, are support files for the program, one ot them being the waveform display you see on the associated object on the timeline.

These are my default folder paths:

In your case they should be in the Imports folder as seen in the image of your folder paths.

. . . . it's definitely the "rewind" function which doesn't play by the rules . . . .

See video below:

Note: the 2 support files and the reversed audio WAV file are created in the AudioTemp folder as specified in the Folder paths settings, when rewind is applied.

John EB

"If you let Music Maker 2023 replace MMM 2019 without fully un-installing MMM 2019, all its Soundpools, and clearing all the remnants of folder and registry fragments left behind before re-installing, then the folder locations will be re-used and in the case of the folders with existing content in them eg Soundpools, locked (greyed out) so they will still be available for MMM 2023 will use."

The path still works if it's not greyed out, again, no need to grey it out in case user wants to change the soundpools' location. You said yourself that with SSDs users may need to relocate stuff.

I didn't see that comment where you mentioned anything about AudioTemp folder, however the folder where they should go wasn't the main point, I don't care where they should go, but they certainly don't belong to Magix Projects folder.

"the 2 support files and the reversed audio WAV file are created in the AudioTemp folder as specified in the Folder paths settings, when rewind is applied."

Why isn't that happening in my case?

Also can you tell me, why the MM has collected 9GB of .wav files in my Imports folder? I haven't imported anything, just used MM samples.

@Cloudglow

Hi

. . . .  no need to grey it out in case user wants to change the soundpools' location . . . . The path still works if it's not greyed out . . . .

The majority of users require a consistent installation procedure and maintenance of the existing folder structure to ensure their projects still work from version to version, thus some options may be locked to preserve continuity of use after upgrading to ensure continuance of usability, without the necessity of having to rehash the folder locations every time an upgrade to a newer version is installed - this is by design.

There is nothing to stop you changing these locations after the install and move the Soundpools etc as you require, however you only change those that are accessible via the program settings and nowhere else, changing file folder locations by other means eg, creating mount points, adding or editing program specific parameters in the Registry should not be done.

. . . . why the MM has collected 9GB of .wav files in my Imports folder? . . . .

As the original default folder name 'AudioTemp' suggests this is the location where temporary audio files and the extra support files that the program creates when you import and edit a loop adding effects such as Rewind, are placed. As you have changed this location to a folder called Import that is where they have been placed ie:

They make editing and playback a smoother experience, and are left there after every session of editing so they are available when you go back to work on the same project in the next session of editing.

You can delete these if you wish between sessions, however doing so you may receive error messages that the wav files cannot be found and will have to reload the original loop(s) so the program can recreate these support files.

In summary with the 'issues' you are having and not knowing what 'tweaks' were made to the previous installation of Music Maker, my recommendation would be uninstall all versions of Music Maker currently on your PC, leaving the Soundpools and VST's etc in place. Use Revo Uninstaller free to initiate the uninstalls and clean up files, folders and registry fragments left behind by the uninstaller. If you have added entries to the Registry then you will need to remove these too, CCleaner may be able to detect them.

Do a full Restart - not a shutdown the computer and re-install the Program with a custom install selecting the folder paths as shown in your image above.

Do note that any other changes you make outside of the program settings may lead to unpredictable behaviour of the program.

John EB