1 Vandal SE does not open.

2 Same behaviour as you.

3 MIDI editor works - can you explain how you were using the editor?

I am using Midi editor as I have often done. I am using DRAW in mouse mode. When I click the Piano keys on the left of the midi editor page it should sound the note, but it doesn't. Also when I click on the note I have drawn in the midi editor it should play, but it doesn't.

If I open an older composition in music maker premium 2017, midi editor plays correctly when I click the notes. I then open the same composition in 2020 version, but it doesn't play note when i click it

When I create a new composition in 2020 version, the midi editor also doesn't play the notes when I click the note or side piano.

The midi editor does plays the notes when I press PLAY, but wont play the individual notes when i click on them in the midi editor..

@daveabove

Hi

. . . . open an older composition in music maker premium 2017 . . . .

Is 2017 installed on the same computer as 2020?

When you installed 2020 were you asked or told that 2017 would be replaced? I had issues when I updated to 2018 and told the installer to use a different location for 2018 in order to keep 2017 - in the end the issues were fixed when I allowed 2018 to replace 2017.

Also after the 2020 installation did you download and install all the instruments etc again?

John EB

I've been getting constant crashes, and often I see this MagixOfa module on the Task Manager. (I was also getting them all the time on the 2019 version, with the same mystery module.) Usually happens when I'm using the midi editor, either recording or playing.

I'm also having a problem in which the tracks turn huge no matter how many times I shrink them back to default size. Whether I change them from the context menu or by dragging from the bottom, they always go back to big-size as soon as I take any action involving scrolling the timeline. It's really annoying, and means I can only look at 3 tracks at a time. Makes it hard to compare and correct notes in different instruments...

Is 2017 installed on the same computer as 2020? I have 3 versions of Muisc Maker Premium currently installed on the same computer. They are 2014, 2017 and 2020.  . I originally downloaded the free 2019 Magix version because it was advised to me that the 2014 and 2017 versions were no longer supported by Magix with updates. So as I had a couple minor bugs in them I downloaded the free version of 2019. This would allow me to use the instruments I already owned that were compatible with 2019 version........ but some older instruments didnt work on 2019 version. I had purchased 2019 premium only a few weeks ago

When you installed 2020 were you asked or told that 2017 would be replaced? The 2020 version only replaced the 2019 version. If I recall correctly, during installation it asked me if I wanted to replace an older version. I believe it meant 2019 version. After 2020 version was installed, 2019 version disappeared . I now still have 2014 and 2017 versions with 2020 version on the computer.

Also after the 2020 installation did you download and install all the instruments etc again? As you know a number of older instruments I own didn't activate in the free 2019 version (even though they should have) and even though they are currently working with 2014 and 2017 versions on my computer. Magix maintained there is no record of these instruments being purchased and only when the purchase is proven can these instrument be activated. After much back and forth with Magix support I finally decided to buy the 2019 version when it was on sale as it came with 8 instruments. This now means I can once again replace the instruments and Magix will now have a new record of purchase for these instruments going into the future. The 2020 version supports the old instruments from 2014 and 2017  and of course the new ones I purchased in the 2019 version. So you could say in the end I basically paid for the old instruments again for the price of the 2019 premium version as that really was the only reason I bought it

Confirmed, however works correctly in Track and Master effects Sorry for my ignorance but how did you open vandal in the track and master effects. I cant work that out.

I've been getting constant crashes, and often I see this MagixOfa module on the Task ManagerI have gotten some crashing in 2017 and 2019 version but dont get MagixOfa notice. I just get a grey box pop up telling me "Music Maker Premium v.24 doesnt work anymore". It gives me some options in that box and I always chose "Close Program"

Im also having a problem in which the tracks turn huge no matter how many times I shrink them back to default size I dont get this problem. If you right click on a track then click "Track height", then click "All tracks", then select "Default". This will make all the tracks small. If this doesnt help Im not sure what will .

Cheers

@daveabove

MM 28.0.0.12 - I have pretty much everything, most instruments, presets and features from previous versions and Premium versions, going back years.

I, too, have the track height problem. Default is big; I get 4 tracks on the screen. Reducing a track height then right-clicking on it and selecting "Track height - All tracks - Adjust to this track" makes then all big again.

Dragging loops to the Arranger works fine until I have to scroll down to see tracks 5 and beyond. Then dragging a loop is hit and miss. Usually the screen automatically scrolls back up to tracks 1 to 4.

Downloads - keeps giving me Soundpools that have already been installed, show up under Soundpools and work. Download All. Restart the program and some of the same and more show up for download...over and over. I will clean up the Store.

I still have some Soundpools in the Store that are mxcogg format and won't play. I uninstalled one of them and then tried to get it again. The Store says that I already have it. I will clean up the Store, but this should still not be happening. I cleaned up the Store in the previous version, unsuccessfully, it seems.

In the past, Century Keys was a problem and the instrument would not work except in one or two versions. I finally gave up and used a coupon.

Two instruments that I bought directly from Magix prior to the invention of the "Store" would not work. Again, I finally gave up and used my coupons. Seeing that there are some new instruments, I think I'll go back and hit up Magix for these.

I haven't gone very far with my testing. The one thing that I think has finally been fixed is "Normalize after recording (audio)." Someone should confirm that this now works.

John CB

@daveabove, @browj2

Hi

. . . . have the track height problem . . . .

Likewise here.

. . . . Dragging loops to the Arranger works fine until I have to scroll down to see tracks 5 and beyond. Then dragging a loop is hit and miss. Usually the screen automatically scrolls back up to tracks 1 to 4 . . . .

No problem here - yet!

. . . . Normalize after recording (audio) . . . .

Is working correctly.

John EB

Ive updated MMM Premium to 2020 version a day ago. The following bugs occure. Does anyone else have the same problem

1 - Vandal SE wont open up when I right click on an audio file and select it from audio effects menu.

Replicated & reported to development!

BTW: Vandal SE will still activate as an object effect via the "Inspector" tab, by adding it via the plus sign from the "MAGIX Plugins" section there. So, it's just the entry in the context menu that seems to be broken.

2 - I cant reverse an audio file. When I right click on audio file and select "Rewind" from the audio effects menu, it seems to wipe the audio file so there is no sound from file. Is this the way to reverse the audio from an audio file.

Haven't managed to replicate this yet, neither with a small loop from the MAGIX soundpools, nor with a bigger audio file. There must be some additional problem parameters. Will keep my eyes on the situation. What kind of files are you processing, and what location are you importing them from? I believe this effect still works as an offline effect, and maybe this is a problem writing the processed file after applying the effect or something. Just a wild guess, though.

3 - Midi editor wont play back the notes I click on even though I have selected "Play clicked notes" from the options drop down menu.

Make sure to use ASIO or WASAPI drivers. What you're describing would occur with Wave or DirectSound drivers. Starting in generation 2018 (25.x), with the introduction of the Samplitude audio engine in Music Maker, it's no longer possible to play the software instruments in "stop mode" when using the latter driver types. This applies to using the on-screen MIDI keyboard, and even an external MIDI master keyboard, but also includes the click on the notes in the piano roll of the MIDI Editor. Just make sure to use ASIO, which you should be doing for the lower recording latency times anyway, and you should be fine.

Cheers!

Hi John,

I, too, have the track height problem. Default is big; I get 4 tracks on the screen. Reducing a track height then right-clicking on it and selecting "Track height - All tracks - Adjust to this track" makes then all big again.

Yeah, that doesn't sound right. Will report. BTW, I recommend the Tab key for the quick switching between the two track heights of all tracks.

Dragging loops to the Arranger works fine until I have to scroll down to see tracks 5 and beyond. Then dragging a loop is hit and miss. Usually the screen automatically scrolls back up to tracks 1 to 4.

Understood. This seems to be the awkward drag & drop behaviour I'm seeing here on my end as well, as per this thread. Reported.

Downloads - keeps giving me Soundpools that have already been installed, show up under Soundpools and work. Download All. Restart the program and some of the same and more show up for download...over and over. I will clean up the Store.

I believe you had this very same problem before. Still not really sure how people end up in this situation, but it seems to be due to data in the soundpool database getting corrupted, rather than someething that cleaning up the store will rectify. Delete the soundpool database file ("SoundPoolDB.dat") instead. You'll find it in the following location on your hard drive:

C:\ProgramData\MAGIX\Common\Database

Delete the file (while Music Maker is not running), and then restart Music Maker. The "Loops" section will automatically be populated with available soundpools again. Should any soundpools that are installed in the defaut location not be listed, please open the program settings ("P" key) and trigger the rescanning of the soundpools via the "Rescan Soundpools" button in the "General options" tab. If you need to add MAGIX soundpools that are installed on your hard drive outside of the default location, use the "Add new soundpools" function (available from the cog wheel drop-down menu in the "Loops" tab), and manually point the program to the location of those soundpools.

I still have some Soundpools in the Store that are mxcogg format and won't play. I uninstalled one of them and then tried to get it again. The Store says that I already have it. I will clean up the Store, but this should still not be happening. I cleaned up the Store in the previous version, unsuccessfully, it seems.

What problem are you having accessing those MXCOGGs? Even if the in-app store system is no longer using the crypted OGG version at this stage, Music Maker is still equipped to deal with this format, if any of the locally installed soundpools are still crypted. However, this does require that you're logged into the in-app store system under the account under which the soundpool was purchased, so Music Maker can check whether it's owned under that account. (For soundpools that were downloaded more recently and are not crypted, your log-in status into the store technically doesn't even matter any longer.) If it comes down to it, you could force the re-download and re-installation of the problematic soundpool(s) as follows: Navigate to the following location on your hard drive while Music Maker is not running.

C:\Users\Public\Documents\MAGIX\Common\Soundpools\Shop

This folder will contain a sub folder for each soundpool installed through the Music Maker in-app store. Simply delete the folder(s) for the soundpool(s) you were having problems with. Then start up Music Maker again. The deleted soundpools will have been cleared from the list in the "Loops" section. Switch over to the "More soundpools" section of the in-app store and find the entries for the deleted soundpools again. There will be a re-download option (arrow pointing down) in the upper left-hand corner of the tile for the soundpool(s) in question. Use this to trigger the re-download and installation. This way you will reliably get a regular OGG or WAV copy of the soundpool, depending on what you have chosen to use in the Music Maker program settings.

In the past, Century Keys was a problem and the instrument would not work except in one or two versions. I finally gave up and used a coupon.

Two instruments that I bought directly from Magix prior to the invention of the "Store" would not work. Again, I finally gave up and used my coupons. Seeing that there are some new instruments, I think I'll go back and hit up Magix for these.

Is this about technical problems using particular instruments and Music Maker, or is this all about the DRM/authentication? Depending on what source you purchased a specific instrument through, the copy-protection can't work with the in-app store system in the more current version. Then, there's the workaround solution of redeeming older Music Maker serial numbers in the in-app store, resulting in the unlocking of the bundled instruments via the store system. However, this won't work if you purchased through yet some other source, e.g. the instruments that were previously available separately on magix.com, or even on Catooh.com years ago. As long as you can still proof the purchase of those, we will usually find some way to sort you out, e.g. via a replacement coupon.

I haven't gone very far with my testing. The one thing that I think has finally been fixed is "Normalize after recording (audio)." Someone should confirm that this now works.

It has. You should hopefully find that this is not the only problem that has been fixed, especially when it comes to MIDI and VSTi workflows, also thanks to your excellent reports. Work on this version will continue over the next few months, and further updates are already scheduled. I encourage users to get in touch with our support and file detailed reports on problems they may be experiencing, rather than just posting about it here. It's the only way we can guarantee that they will be looked at. I'll try to stay on top of what's happening here, though.

Cheers!

Great advices ralftaro! Just to add to the (very annoying topic) of Tabs being too big, I was very annoyed but accidentally figured it out.

There is a settings in View -> Arranger -> Zoom Track Header that is now checked by default. Uncheck it and close the Music Maker. This will now save it to MusicMaker.ini located in C:\Users\yourusername\AppData\Roaming\MAGIX\mm28

Same applies to your Audio Setings. It appears the MM is crashing when you close it. Open MM and don't load any projects. Change your audio settings and close MM entirely.

Now The file above will have correct settings so even if it crashes it will go back and load those settings.

The SoundPool problem I can confirm still exists, had brand new PC and clean install and it is behaving the same, always showing in "Download" :-( It MIGHT be because I am choosing to download WAV instead of ogg. This is the only dfference I can see.

Hope this helps!

@ralftaro

Hi Ralf,

Thanks for replying.

Track height: Pressing on Tab seemed to fix something and the tracks now got smaller. Prior to that, even the +/- on the vertical scroll bar would not even work. It now works, even after restarting MM.

Additional rows BPM and Downloads: After cleaning up the Store, when rebooting today, I saw a bunch more Soundpools to be downloaded that are already installed. I looked at the first 2, House - Big Room Mastercuts and House - Soulful House and the BPM was showing as "-1" under Loops. I downloaded these again, and the BPM now shows as 123 and 125, respectively.

mxcogg files: Annoyingly, the mxcogg files work today. I was sure that I was logged in to the Store yesterday, but probably not. Today, the startup screen went straight to the log in part. Today, I added back Garden of Joy and the mxcogg files worked.

I had at least one Soundpool under Shop, Swing - Swing Time, that refused to show up in MM, even after adding it specifically again. I deleted the folder from Shop, restarted MM, went to the Store, to Swing Time and it showed as acquired. I clicked on the "i" and then Go to Loops. This took quite a while before going to the Soundpools tab. Of course, Swing Time was still not there. Thus, just deleting the Soundpool from the Shop does not help get it back. So, I deleted the Soundpool.db as you recommended and restarted MM. The Loops tab was empty; no automatic population of the Soundpools. Under Downloads, I had a list of all 32 Soundpools that were under Shop. I did the Download all and the Soundpools that had mxcogg files now had both mxcogg and ogg, and the deleted Swing Time came back under Shop. I'll delete the duplicate mxcogg files that have ogg files. All 32 Soundpools from the Shop showed up. I then went back and rescanned the entire Soundpools folder.

The key is to delete the database.

Instruments: As I mentioned, I purchased 2 instruments directly from Magix (not Catooh) prior to the invention of the in-app Store. Magix replied that they could not find a way to make these purchased instruments work in the newer versions. I will take this up with Magix. The other one, Century Keys, came with one version of Samplitude Music Studio - it worked in one version, but not the next and not with MM with one exception where Magix gave us a workaround. History.

Independence: I started it up in MM and tried to load an instrument from the Basic instruments. This causes MM to crash and stay open in the Background Processes, unable to remove it; had to reboot. The default piano works, but nothing else.

I presume that the Basic instruments that we got with an old version of Samplitude Music Studio will not load in Independence started in MM. Is this correct?

Bugs: I prefer to first raise potential bugs here to make sure that it is not just me and that others can replicate the problem, before reporting it to Magix. We have many reports of bugs on the forum that are actually user problems.

John CB

@ralftaro

Thanks for your help

"Make sure to use ASIO or WASAPI drivers. What you're describing would occur with Wave or DirectSound drivers. Starting in generation 2018 (25.x), with the introduction of the Samplitude audio engine in Music Maker, it's no longer possible to play the software instruments in "stop mode" when using the latter driver types. This applies to using the on-screen MIDI keyboard, and even an external MIDI master keyboard, but also includes the click on the notes in the piano roll of the MIDI Editor. Just make sure to use ASIO, which you should be doing for the lower recording latency times anyway, and you should be fine."

I went to 2020 Music Maker Program Settings, then  Audio Midi Page, then selected  all the ASIO options. One by one I tested the 3 x ASIO options but all sound in the playback is cut by this option. The program works but has no sound at all. However the WASAPI option does work when I press play and when I click the notes in Midi Editor. But a new problem has arisen. When I use WASAPI G276HL driver and press play, there is a delay of 5 to 6 seconds before the program starts to play, sometimes longer. Its very annoying. It seems to be struggling.The Wave Driver option and Direct Sound options allow the program to play instantly with sound, but I have the issue of no sound when the notes in the Midi Editor are clicked.

In my 2017 Music Maker  ASIO options also cuts sound, but like the 2020 version,  WASAPI option works in play back and clicked midi notes but also has the delay problem . When I use the Wave Driver option and Direct Sound options in Music Maker 2017 the playback sound and clicked midi editor notes work fine with no delay.

QUESTION - Why dont my ASIO driver options work at all when it should, and why does the WASAPI G276HL option struggle with a delay?

Cheers

@daveabove

I'm not sure that Ralf, who is a Magix staff member will necessarily see you post so I will edit it slightly to ensure he receives notification of it.

In the meantime, you mention "3 ASIO options" as being shown on your computer. Can you tell us/show us (by screenshot) what these are?

Jeff

Thanks Emmrecs

These are the driver options I have in my 2020 Music Maker Audio Midi page

Cheers

@daveabove

Thanks for the screenshots.

From the options you show I would select Magix Low Latency 2016 ASIO and then press the "Advanced" button directly below where the driver is shown at the top of that screen. I would be very interested to see its settings, because I suspect something there may be "wrong", e.g. the sampling frequency, which should be 44.1 or 48 kHz.

Just to add: I would not consider using the Realtek ASIO driver! Unfortunately, Realtek do not have the brightest reputation in the audio world!

HTH

Jeff

Emmrecs

Ive shown you screen shot of all 3 options. What should it be set to.....never dealt with this box before.

......because I suspect something there may be "wrong", e.g. the sampling frequency, which should be 44.1 or 48 kHz.

what option should I chose and how do i set it to 44.1 or 48 kHz.

Cheers

Emmrecs

Ive shown you screen shot of all 3 options. What should it be set to.....never dealt with this box before.

......because I suspect something there may be "wrong", e.g. the sampling frequency, which should be 44.1 or 48 kHz.

what option should I chose and how do i set it to 44.1 or 48 kHz.

Hi there,

The real question at this stage is: What sound hardware have you actually connected your headphones or speakers to? Is it actually the Realtek on-board solution that is highlighted in your advanced ASIO driver settings? The most typical problem we're getting when people are reporting that they are simply not getting any audio out of Music Maker is that the output option for the generic ASIO driver has defaulted to a device other than the one they're actually intending to use and expecting the signal to come out from (e.g. some USB or BT headset/audio codec). For ASIO, which is now the default driver typer in the program, you'll always need to make sure to go via the "Advanced" view, whereas for the DirectSound and Wave drivers you'd need to choose the physical output device via the drop-down list at the top of that dialogue.

Cheers!

@browj2: Will have to get to your post and follow up on it tomorrow!

@ralftaro

Thank you for your answer. But my limited technical knowledge of these things mean I only have a vague understanding of what you've said, and an even more vague understanding of how to perform the tasks you've asked me to do. Im not that savvy when it comes to computers and music software.

Can you give me more basic actions that I should be doing and looking for in laymen speak . Im a bit lost.

Cheers

@daveabove

We need to know how your computer produces audible audio! IOW, what do you use to listen to any audio on your computer, built-in speakers, external speakers, headphones or other?

Jeff

Thanks for reply Emmrecs

I use an external Logitech speaker system comprising of 2 x speakers and 1 x Bass box. My computer is a Dell desk top and doesn't have built in speakers.

My operating system is Windows 10 Home; Processor  is  Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4008 Mhz, 4 Core(s); 8 Logical Processor(s); Installed Physical Memory (RAM)    32.0 GB

Cheers
 

@daveabove

Thanks for this further information.

I will assume your speakers are directly connected to output sockets on your computer? In which case you are using the Realtek drivers. So, on the Advanced screen you posted earlier you need to ensure that the first option is selected.

Then you need to access the Realtek Control Panel (I can't advise how you actually do this because I don't have the same set-up on my computer) but once there, you need to check all of the following: sample rate, should be 44.1kHz or 48kHz; bit depth, should be 16 or possibly higher; any "enhancements" should be turned OFF.

Since I don't have access to the Realtek panel, if you still experience problems it would be very helpful if you could post a screenshot of it so that we can see if there is anything "obvious" that needs to be changed.

Jeff

Hi Emmrecs

Left on the image above shows what Realtek file Im opening, and the right box is what opens when I click the Realtek icon . It opens a Dell Audio box. It doesnt look like Realtek device opens. Have I done something wrong?