Thanks for your answer.

As I said though, I already checked the thread you linked, and it didn't help me solve my problem.

Here's a video I just recorded, where I try the solution you mentioned in this thread :

Sorry if I missed something, but nothing changed when resizing the keyboard.

Hi

Thanks for the video clip that helps.

The problem looks like there is insufficient space on your screen area to accommodate the full width keyboard - this could be due to the monitor resolution being set low or is physically lower than that need for MMM. I am using 1920 x 1080 resolution monitors from which my videos were recorded.

An option if your screen resolution is lower, is to minimise the right pane using the button directly below the close program X, top right of the screen.

HTH

John EB

Thanks again for your answer.

My monitor's resolution is 1920 x 1080.

Minimising the right pane unfortunately didn't solve it ; I guess it lessened the gap a little bit, but it's still here.

Actually, I wasn't having this problem until a few days ago, when it suddenly became like that when I started the software, and I can't recall anything that could have caused it 😕

Hi

Assuming other programs are displaying normally when full screen, I suspect that you have accidentally hit the Tab key which is the Zoom Soundpool and Keyboard shortcut - press the Tab key once should return to normal.

The timeline track heights look too big as well - did you zoom these? If not try reducing their height using the + and - zoom keys just below the vertical slider at the right side of the timeline pane.

HTH

John EB

Hi, thanks again for taking time to help me.

Pressing the Tab key fixed the height of the timeline track (thanks for that !).

The keyboard is still the same though 😕 (the first time I pressed tab actually zoomed it even more)

Hi

This looks like there have been multiple 'issues' - try pressing F4 to reset the window layout of MMM.

HTH

John EB

Hi

Pressing F4 didn't change anything 😕 (it "refreshed" the layout but the interface remains the same)

The fixer solved it !

Thanks a lot to both of you for your help ! 😃

Hi

@Telroshan

Pleased to know you are now sorted.

@ralftaro

Thank you for letting us know there is an issue with some hardware combinations and/or possible Windows 10 updates.

Windows 10 updates have indeed caused many issues, and not just with Magix products, but others as well.

Best wishes

John EB

@ralftaro

Many thanks for the fix - that had me worried :)

Hi Telroshan,

This is most likely another problem that falls into the category of compatibility issues between the graphics engine currently used in Music Maker and certain graphics chipsets/drivers. This also only started popping up in the past few weeks, possibly triggered by a recent Windows (10) update (or graphics driver update). Your easiest way out is probably the operation of Music Maker in a more compatible graphics rendering mode. You can accomplish this configuration by downloading and running the following fix:

https://support2.magix.com/customer/en/download_do/294659

 

I hope this helps!

 

Windows is detecting this as a threat and wont let me apply it. Is there an easier (registry/config) method to make this change?

Yeah when I downloaded that link and scanned it windows defender said there was a trogan attached to the download. Any other solutions?

@tylor

. . . .windows defender said there was a trogan attached to the download . . . .

Windows Defender has a reputation for giving false positives for Trojans, particularly when using the Heuristics engine, my AV and Malwarebytes report the file as being clean.

What was the specific 'trojan' that was identified by Defender?

John EB

@tylor

. . . .windows defender said there was a trogan attached to the download . . . .

Windows Defender has a reputation for giving false positives for Trojans, particularly when using the Heuristics engine, my AV and Malwarebytes report the file as being clean.

What was the specific 'trojan' that was identified by Defender?

John EB

False positive or not, it won't let Windows user using Windows Defender (which I'd guess is probably 95% of users) run the application - there is no option to exclude or bypass.

That said, you've had a different experience than I have. I haven't had a false positive with Windows Defender yet and had plenty with Malwarebytes.

Either way, is there a solution that doesn't involve running this executable? Is it changing a setting, swapping a DLL? It was posted by the team so nonchalantly I'm hoping it is a trivial modification.

Hi

. . . . run the application - there is no option to exclude or bypass . . . . is there a solution that doesn't involve running this executable

You have a Catch 22 situation - turn off Windows Defender while you run the fix, if you do not want to do that then you cannot run the fix.

John EB

When executing the exe and the Windows Defender popup appears, you can simply click "more information" and a button to execute it anyways should appear.

At least that's how I always do it(W10)

Hi Telroshan,

This is most likely another problem that falls into the category of compatibility issues between the graphics engine currently used in Music Maker and certain graphics chipsets/drivers. This also only started popping up in the past few weeks, possibly triggered by a recent Windows (10) update (or graphics driver update). Your easiest way out is probably the operation of Music Maker in a more compatible graphics rendering mode. You can accomplish this configuration by downloading and running the following fix:

https://support2.magix.com/customer/en/download_do/294659

 

I hope this helps!

 

When executing the exe and the Windows Defender popup appears, you can simply click "more information" and a button to execute it anyways should appear.

At least that's how I always do it(W10)

Worked for me, thanks!

You have a Catch 22 situation - turn off Windows Defender while you run the fix, if you do not want to do that then you cannot run the fix.

John EB

 

I am aware of that - that is why I chose option #2 and am asking for an alternative fix from the developer of the application :)

Well, I went ahead and installed the "patch" and now Music Maker is all messed up. When I launch it, half the interface jumps to 2x the height and goes off screen, while the other half stays usable. F4 seems to fix the issue temporarily ... too bad this was an executable patch, because now the only way to undo this is a reinstall.

I'm also worried because this EXE patched my "Samplitude" which I had no issues with, and I'm wondering what it broke there as well now.

Hi, I have been having this exact same issue, but when i open the patcher it says it is expired (see image): http://puu.sh/ySTXK/d99b829421.png

What now?
 

Hi, I have been having this exact same issue, but when i open the patcher it says it is expired (see image): http://puu.sh/ySTXK/d99b829421.png

What now?
 

I have the same Problem... I think the patch is just for 2017 Version not for 2018...

Hi, I have been having this exact same issue, but when i open the patcher it says it is expired (see image): http://puu.sh/ySTXK/d99b829421.png

What now?
 

I have the same Problem... I think the patch is just for 2017 Version not for 2018...

Please try again now, from the same link posted above. The fix has been updated. If you still get the old version (with the expiration message) this might be due to a caching mechanism in your web browser, since neither the URL nor the file name for the fix has changed. It might help if you explicitly save the patch to a different location, rather than opening it directly from the URL, or if you clear out the cache of your browser first.

I hope this helps!