@truegent

Hi

Check the following:

The graphics drivers, from the GPU manufacturers, not Windows, are up to date.

In the Windows settings, System, Display the Scaling and layout option is set to 100%

HTH
John EB
Forum Moderator

@truegent

I am not sure whether this is the reason for the problem you are seeing but MM version 31 is actually MM 2023, not MM 2022 so you have actually updated to the latest release version.

In doing so you may have accidentally encountered the problem of Update versus Upgrade! To make the full transition from MM Premium 2022 to MM Premium 2023 you have to buy the Upgrade; merely updating your version should have left you with ALL the features you had in MM 2022 but without the additions that MM 2023 has brought. I don't think this should affect the display of those waveforms etc., but I would begin to suspect this might be the reason.

One thing you might like to try: go to View>Default layout (shortcut F4). Does that make any difference?

Jeff
Forum Moderator

If the upgrade, as you are labeling it in this case, is not intended for the version I was using then why was it offered as an automatic update within the UI of the program? I check for updates periodically and upon doing so yesterday I was presented with this nearly 1GB download and update to version 31. Is this a ploy on the part of development to force users to update to the new version?

I have also attempted the Default Layout to no avail.

@truegent I believe it is 1GB because of the Song Maker AI update. The idea is that you use always the newest version. This is also a good idea, because Music Maker gets bugfixes over time. Your old version will not get any bugfixes in the future. But it is also possible, that new bugs get introduced. So you should finish all your projects before updating. All your features will be transferred to the new version.

@truegent I believe it is 1GB because of the Song Maker AI update. The idea is that you use always the newest version. This is also a good idea, because Music Maker gets bugfixes over time. Your old version will not get any bugfixes in the future. But it is also possible, that new bugs get introduced. So you should finish all your projects before updating. All your features will be transferred to the new version.

Working in the software industry I am completely onboard with that logic, but if I'm being told that the update to the UI is the cause of the issue and that I did it accidentally, I take exception to the mere idea that I did something that was not intended by the program developers. It's not like I'm downloading this program through torrent, I've been a bought and paid user of Magix software since 1999.

@truegent The problem is that Magix always stores the Mxupdate.exe in a temp folder, then waits until you install it and deletes it automatically. I think the path is C:\Users\YourUserName\AppData\Local\Temp\MXUpdate.exe. If you didn't back it up you cannot go back because you always dowload the newest update with the bug that you don't want. I can send you my backup of the previous update 31.0.0.10 if you want. Or you can ask customer support at infoservice@magix.net for update 31.0.0.10

I also would suggest you drag and drop the Loops tab from the right side of the screen to somewhere else, because the right pane is very narrow. I always place the Loops tab at the bottom.You can also place it on a second screen if you want. Then you will have enough space to see everything.

@truegent The problem is that Magix always stores the Mxupdate.exe in a temp folder, then waits until you install it and deletes it automatically. I think the path is C:\Users\YourUserName\AppData\Local\Temp\MXUpdate.exe. If you didn't back it up you cannot go back because you always dowload the newest update with the bug that you don't want. I can send you my backup of the previous update 31.0.0.10 if you want. Or you can ask customer support at infoservice@magix.net for update 31.0.0.10

I'm going to wait until after work to tinker with this some more, I'm starting to think it's possibly resolution driven but it may be a bug yet. Thanks for the offer, I may still have to consider it.

Hi,

There is something definitely wrong with the Loops windows MMM2023 - 31.0.1.13.

I dragged the window to the bottom and went through various problems, first with the formatting of the windows, then with adding optional rows. The Instruments and Soundpools columns are far too wide by default. Just the Soundpools column cannot be resized on its own, you have to resize (reduce) the width of the instruments which will reduce the Soundpools column.

This makes the Loops column wider. Add optional rows, all of them. You have to scroll to the right to see the last column. The heart column is far too wide. Trying to reduce only does a little bit. Trying it again and I lost the bottom scroll bar. Reducing the Instruments column a bit more brings back the last Loops column, but the heart column can no longer be resized.

Move the Loops window back to the right window then back to the bottom and the width of the columns is changed to the default.

Resize the columns, exit and restart MMM. The formatting of the Loops window goes back to the default widths.

Oops, this time I managed to reduce the Heart column. Seems to be an intermittent problem.

Optional rows - what does Preview do? With Preview turned off, the waveform is shown with the Loop Name. Turn on Preview and the waveform is shown in a separate column called Preview that can be resized. Strange but fine.

Here is a sample project with Loops at the bottom, column widths modified.

Project saved, exit, restarted, project opened, column widths back to default.

There are a couple more anomalies that I will try to capture.

@truegent

Hi,

I notice that there is no header for the columns in your image, so something is wrong.

Try closing/opening the Loops window. Try adding optional rows.

Try dragging the Loops window to the bottom like in my image.

Do you get the column headings?

John CB

Hi,

There is something definitely wrong with the Loops windows MMM2023 - 31.0.1.13.

I dragged the window to the bottom and went through various problems, first with the formatting of the windows, then with adding optional rows. The Instruments and Soundpools columns are far too wide by default. Just the Soundpools column cannot be resized on its own, you have to resize (reduce) the width of the instruments which will reduce the Soundpools column.

This makes the Loops column wider. Add optional rows, all of them. You have to scroll to the right to see the last column. The heart column is far too wide. Trying to reduce only does a little bit. Trying it again and I lost the bottom scroll bar. Reducing the Instruments column a bit more brings back the last Loops column, but the heart column can no longer be resized.

Move the Loops window back to the right window then back to the bottom and the width of the columns is changed to the default.

Resize the columns, exit and restart MMM. The formatting of the Loops window goes back to the default widths.

Oops, this time I managed to reduce the Heart column. Seems to be an intermittent problem.

Optional rows - what does Preview do? With Preview turned off, the waveform is shown with the Loop Name. Turn on Preview and the waveform is shown in a separate column called Preview that can be resized. Strange but fine.

Here is a sample project with Loops at the bottom, column widths modified.

Project saved, exit, restarted, project opened, column widths back to default.

There are a couple more anomalies that I will try to capture.

@truegent

Hi,

I notice that there is no header for the columns in your image, so something is wrong.

Try closing/opening the Loops window. Try adding optional rows.

Try dragging the Loops window to the bottom like in my image.

Do you get the column headings?

John CB

John CB,

Thank you for your analysis and recommendation. By right clicking on the non-existent column headers or via the cog I was able to add "Optional Rows" which did provide more detail relating to the loops, but the Loopname column is still problematic. This is at least a start and your information is greatly appreciated. I apologize for the delayed response as I just got home from work but rushed to check this for you as soon as I did.

Hello, i had the same problem, but...

SOLUTION
--------

Edit this file
C:\Users\*YourName*\AppData\Roaming\MAGIX\mm31\MusicMaker.ini

Find
[LoopsViewColumns]

and change this
WidthNameSouthdock=352
WidthFavouriteSouthdock=68

I took it from the previous version and it works :D

Hello, i had the same problem, but...

SOLUTION
--------

Edit this file
C:\Users\*YourName*\AppData\Roaming\MAGIX\mm31\MusicMaker.ini

Find
[LoopsViewColumns]

and change this
WidthNameSouthdock=352
WidthFavouriteSouthdock=68

I took it from the previous version and it works :D

That is an amazing bit of information, but I will tinker with the east dock numbers as that is my preferred location, but this is exactly what I'm looking for. You're a Rockstar

THIS!! Why was this changed??
THANK YOU so much!

Hello, i had the same problem, but...

SOLUTION
--------

Edit this file
C:\Users\*YourName*\AppData\Roaming\MAGIX\mm31\MusicMaker.ini

Find
[LoopsViewColumns]

and change this
WidthNameSouthdock=352
WidthFavouriteSouthdock=68

I took it from the previous version and it works :D

So I did this.... and nothing changed.... the original values were like 1371 for both attributes.... but after changing them, nothing has changed in the loop name and file viewer field

@cheatcode Be sure to close the program and edit the file only if Music Maker is closed. Also check if your Loops tab is positioned at the bottom of the screen or at the side. You need to edit the values accordingly (South, East etc.)