So they've started the unlimited loops subscription and i've been finding a couple of previously purchased soundpools are inaccessible even after i've already purchased them way before the update..... So does that mean I have to subscribe to aceess soundpools that i've already paid for?......
How are you trying to access the loops, and how are they inaccessible? Are the soundpools in question still listed in the "Loops" tab? Do you have problems using them from there, when trying to import single loops from those soundpools into the arranger? Do you get any error message? Or are you strictly talking about the reloading of old projects, which are now listing the loops as only available within the context of the subscription? If it's strictly the latter, we're already working on this. A fix should be available soon. Sorry for the hassle. Other than that, please let me know the details, or contact us directly:
I'm referring to loops already arranged in previous projects, loops already in my loops tab, when uploading projects I'm now prompted that they will no longer play unless I'm subscribed in the unlimited loops program. I'm logged into the store, using a purchased version and have an abundance of soundpools that i've purchased over time.
All soundpools will show up, but you will get an indication opon opening a project that used any samples that fall under the category won't be uploaded into the project unless you subscribe to the unlimited soundpools plan and saving the project without the samples will end up altering the project.. Only way I got around it was to restore my laptop to a couple of days before I performed the update then rescanned all soundpools. I am now able to use them but they all have the unlimited loops icon next to them in my loop list.
. . . . All soundpools will show up, but you will get an indication opon opening a project that used any samples that fall under the category won't be uploaded into the project unless you subscribe to the unlimited soundpools plan . . . .
Can you post a screen shot showing this please showing the message and the Soundpools tab - I am not experiencing this with any old projects.
This one used a loop that was in the format mxcogg. This format was abandoned and the files in the Shop should have been updated to ogg or wav. However, the project still has the mxcogg. It doesn't show up in the Arranger when I force it to open.
It would seem that Magix has put back the mxcogg format for the new Subscription method, which would then interfere with older projects.
Users on the French forum are also complaining about this.
Further to my last reply, I looked at this in a bit more detail.
As best I can figure, when Magix started selling Soundpools through the Store in MM, the loops had the extension .mxcogg. Thus, any projects made with these loops are now deomonstrating the Subscription Problem. Magix then abandoned this format and we were able to download the Soundpools again and this replaced the mxcogg files with ogg or wav files. But, the old projects still had a reference to mxcogg.
If I understand correctly, these projects that used mxcogg files continued to work, even if the mxcogg files disappeared, because MM created files under ...\MusicMaker\AudioTemp with the format name_of loop_mxcogg.wav. The project would read these and keep on working, until now.
With the new Subscription model, Magix reintroduced the mxcogg format. Thus, any project that contains loops with the mxcogg format now has a problem because MM detects the mxc part of the name_of loop_mxcogg.wav file in the AudioTemp folder and considers this to be from the Subscription and one doesn't have it. That is, if I understand correctly how this likely works.
Magix should have used a different prefix rather than mxc for the Subscription.
. . . . If I understand correctly, these projects that used mxcogg files continued to work, even if the mxcogg files disappeared, because MM created files under ...\MusicMaker\AudioTemp with the format name_of loop_mxcogg.wav. The project would read these and keep on working, until now. . . . .
Agreed - do the files still exist in AudioTemp on your PC?
I have found one project, out of 91, that used mxcogg files and it displays the Subscription message.
Checking the AudioTemp folder, on my PC and backup drives, there are no name_of loop_mxcogg.wav files in existence for that project which was created on 15/05/2018 and used the Score - Fantasy Tale soundpool.
All other project files from that period, which was the start of my 'MIDI era', are based on ogg files where soundpools have been used.
Sorry this issue had to spawn such a long thread. Just wanted to confirm again that this is precisely the problem we're already working on, now that the OP has confirmed the problem details. A fix is to be expected early next week, I believe.
The introduction of the soundpool subscription did indeed call for the comeback of the crypted MXCOGG format. Now, there seems to be a little kink in the logic of the mechanism that is checking for the availability of subscription soundpools in loaded projects. If you're not (i.e. no longer) on the subscription, this dialogue is supposed to inform you about the loops that were purchased through the subscription and are now no longer available to the user. The problem is that, after finding references to MXCOGG files in a project, it only checks for subscription status, but doesn't move on to checking whether you possibly purchased that particular soundpool as a permanent item in the olden days of Music Maker 25.x. So, it prevents you from effectively opening those older projects that may still contain references to MXCOGG loops, which wouldn't have been a problem before. (While Music Maker 27.x and 28.x did no longer download crypted MXCOGGs from the server, they were still able to handle/decode them, if they had been instaleld by version 25.x before.)
So, I hope this clears things up. Sorry again for the hassle. Please hang in there until next week. Thanks!
The fix for this will be officially released sometime at the beginning of next week. All practical field tests came back positive so far.
@mckenzie-jones: Please check your private message. I'll send you a direct link to the preliminary patch and some additional instructions. If you don't wish to wait until after the weekend, this will have you up and running again this weekend.
Just FYI: The relevant update to address this issue (version 22.214.171.124) officially want live yesterday. So, this patch is being deployed through the auto-update function in the program to all users now.
Sorry for the hassle to anyone who was experiencing this problem with old legacy projects. Have fun making music again!