![]() This also happens when I completely disable "autodetect BPM" in the settings. For example, from 90 BPM to 160 or 60.It does not seem to affect the speed of audio tracks, but it turns out by the end of the project with 90 BPM, my BPM project jumps to 200! The added WAV "loops" do not have any media data. Everything seems to work, but in many cases, adding third-party "loops" changes the BPM of the entire project. ![]() Does anyone have a problem with the BPM of the project? I set the settings to automatically change the BPM of the added file. I had to do it before when an update would "break" a feature just to find out it did nothing but cause me a day to reload everything. I have waaaayy to many soundpools and packages that I would need to reinstall. My real problem is I need to wait for the release and recommending a "reload" is out of the question. This waveform issue has happened before in earlier updates but was quickly fixed with the next update released. I'm gonna need to keep a log on what breaks when the magix team pushes an update. The weird thing is if I load a project I made from an older version the waveforms shows in the project, but since the update no matter what loop I add to an existing project, or a new project, the waveforms do not show. I know if I copy and paste the loops from the original to a "new" project the issues are still occuring.Īnd I also know if I add the loops manually to a new project to recreate the problem project from the pool library, the problem disappears.Īll goes to normal except for the new problem of the waveform in all loops not showing when adding to a project. (In more current product generations, this will take you to the start dialogue to trigger the actual patch download.) Please keep in mind that, under the current Music Maker product concept, you'll be able to patch your way up to the current product generation and revision from any version starting in generation 25.x of the you "recreate" a faulty project and its content as a "new" Problems with scanning VST instruments fixedĪs always, the patch will be deployed via the program's automatic update function, which you can also trigger via the "Update program online" option in the "Help" menu.Dropdown menu in MIDI Editor visible again.Problems with restoring the window layout fixed.Fixed problems with the use of the starter pack (Note: If you still have problems, please rescan the sound pools in the program settings > General).Here are the official patch notes:Ĭhanges in patch 32.0.2.11 compared to 32.0.1.8 For us, it's right back to work on Music Maker, and you can expect further improvements and bug fixes in yet another update in the near future. ![]() This time we wanted to respond quickly to your feedback on the last update, so we fast-tracked this smaller patch. Another update for Music Maker has just gone live. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |