The CM-202 "Save" Issue - Revisited

Official support for: muon-software.com
Locked New Topic
RELATED
PRODUCTS

Post

Sorry to bring this up after so long. I know this was addressed when the 202 was released, but it's still bothering me.

Whenever I have the 202 open, and I hit "Save" in Cubase, everything works fine. But if I close Cubase with the 202 active, I am unable to EVER open that file ever again. If I remember correctly, this was described as a problem with the way Cubase stores and handles the save data.

But why is this only a problem for the CM software? Absynth, Dynamo, Attack, Crystal, Model E, Ganymed, Crazy Diamonds, the list goes on...none of these VSTi's display this behavior, and the first two I listed have some pretty whacked VSTi implementation.

So I guess I don't understand how this can be a Cubase issue.

For what it's worth, the reason this came up for me was because last night I had the 202 open for the first time in months. I haven't been using it because of the issues described in the other current CM-202 thread here in this forum. Sure enough, I happened to try to pan one of the sounds away from center and the whole thing froze up on me. Unfortunately the last time I had hit "Save" I must have had the 202 open, so now I am totally unable to open that song file anymore. I'm glad to see that you're "working on this." I'm hoping this save issue can be addressed as well. These are nice VSTi's you guys are cranking out...it sure would be nice to actually be able to use them!

(G4/800, btw)

Paul
Top

Post

Do you mean the SR-202, the drum machine, or the CM-101, the synth? There is already a separate thread about the SR202 going on...
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
Top

Post

SR202 is different from all the plugins mentioned because it saves the SAMPLES you loaded into the song file. This requires a certain amount of space in the song file.

if you are using Cubase or Logic version older than v5 the file format doesn't always allow sufficient space for SR202 to save its samples. Same goes for Cubasis versions older than v3.

What sequencer are you using, and we'll take it from there?

Dave
Top

Post

Cubase 4.1

I was using the 808 kit, only has about 8 samples or so, I think.

Paul
Top

Post

SR202 can only give you its full functionality with Cubase v5 or higher. There's nothing we can do to update the plugin to get around the limitations of your host software except to fundamentally change the way it works.

I can only recommend that you upgrade to a more recent version - surely there are precious few advantages to staying with an ancient version like 4.1? Modern plugins need a modern sequencer IMHO.

Regards
Dave
Top

Post

Well crap.

Sure is a fickle industry, isn't it? Funny how my copy of 4.1 is "ancient" while the Fender Jazz bass that I purchased in 1998 is merely in its infancy. :^)

I've stayed with 4.1 because I've yet to have a need to upgrade to 5.x. From what I've read, there seem to still be many bugs to work out in the Mac version of 5 and up until this 202 issue, I've had no problems with 4.1. Why fix what isn't broken, eh? Besides, all my other "modern" plugins run just fine. My choice now is to shell out a couple hundred on 5.x or SX just to run the 202...(which STILL crashes when one tries to turn any of the filter/pan knobs!)...or just keep using Attack and/or Reason 2.0.

Thanks for your help.

Paul
Top

Post

We're working on the crashing issues. It's a tough one to crack when most Mac's we've got access to work perfectly with no problems *at all*. On the G4/450 down to my left, SR202 works flawlessly for hours. It's a hardware conflict issue probably at interrupt level and we're having to rewrite the plug's engine practically from scratch to get around it.

However, even when the bugs are fixed, SR202 still won't work for you if you don't upgrade your sequencer for the reasons stated.

Dave
Top

Post

Well like I said, right now it's just the 202 that won't work on 4.1, so I won't be upgrading my sequencer until more of the plugs that I desire won't run on it.

FWIW, the freeze issue occured regularly on my G3/300 and on my new G4/800. If I could get around THAT issue, I'd be okay with my original concern regarding the saving. (Then I could at least disable the 202 prior to save/quit and re-enable it when I reopen...kind of a PIA, but workable when it's not crashing!) I wonder what the difference between your G4/450 is and my two Macs. (Hey, for a small fee I'll ship you my G3 for a few weeks if you want. :) )

Paul
Top

Post

If only you were in London rather than Ohio though....!

Regards
Dave
Top

Post

I learned on the internet that all software companies are rich, money grubbing and greedy, so you SHOULD have enough money to fly me an my Mac over there! Right? Right? :lol:

Good luck with the revisions, and thanks again for your quick response. Even when it's not the answer we're looking for, we're still fortunate to have you guys available to us end-users like this.

Paul
Top

Post

If a few more CM plugin users bought an Electron and Tau Pro each we'd be able to afford to fly a crack team of Mac experts to you to fix the problem in your own studio :wink:

Seriously though, this is the benefit of supporting smaller developers - we'll always try to give the best one-on-one service that we can.

Cheers
Dave
Top
Locked

Return to “Muon Software”