Cakewalk Rapture Pro Announced :)

[BBFG#]

I'm seeing many of the same problems that have been there with the originals.

In anything concerning having to 'force' Sonar plugins, I've found most of it has to be done in the registry. I have in the past had to rewrite download paths, enter serial numbers and even write strings that Sonar informed me were automatically there, but weren't. Sample Rate settings that had to be forced by a F4 command on start and missing samples searched for and moved from some off folder to where the rest of them installed.
Good synths with many finicky particulars to set up to work properly.

So it looks like a case of "the more they've changed, they more they've stayed the same"...
I get the feeling sometimes that Cakewalk does these things on purpose (although can't fathom a single reason why they should).

Thanks for this thread and all the comments,
it helps me be done with Sonar synths for at least awhile.

edit/add: Something else I've learned along the way with Sonar in general. Make your own change log text file. Because every update returns it to the same state of problems it had before and sometimes worse. Back up every file before an update and rename project files until after the update is complete and functioning as it should.
I've only been a return to Cakewalk in the last 3-4 years, and the time having to deal with snafu updates is seriously getting me ready to go back to Cubase.

[midi sentinel]

There is no explanation on how to "authorize" Rapture Pro, in documentation. They say "If you have not authorized Rupture Pro in the Cakewalk Store (or on Steam), Rupture Pro will function in demo mode." And I can't figure out how the hell do I force this piece of crap to authorize, or prompt me for serial or anything. Nothing about authorization in my Cakewalk account (or "shop", as they say), nothing in CC, nothing in Rupture. They talk about serial number on pages 8 and 10, but seemingly they use voodoo magic since they don't explain what we can actually do with that number.

Anyone knows how to force the authorization?

It just seems to need you to run the Command Centre app and log into your account, if it is already registered there it should also be authorised on your system automatically. The problem is if you can't get the Command Centre to run - took me 5 or so attempts to even get it to load without freezing or crashing, and even then it crashed another time while installing one of the packs, but I managed it in the end.

Thanks for the suggestion.

I've done it many times, RP is properly reported in CC and serial number is there. Anyway, I'll see what supports says, if/when they get back to me. Giving up on it, spent way too much time already.

[jackmazzotti]

i just spoke with technical support and they are working on the file destroyer bug right now

[mholloway]

What a joke!

Cakewalk can suck it. Any number of (better) companies have figured out how to make this all work seamlessly. Garbageware from a garbage company.

[aMUSEd]

I can see what the problem is by comparing what is loaded in Rapture and Rapture Pro. For example for Adrastea pad Rapture is loading the Architecture multisample GSP086 (FM2 08 03 01.00).sfz. In rapture Pro those samples are failing to load and when I try to load them manually they are also refusing to load so I wonder now if they are corrupted, I will try copying over the old Rapture content.

Edit - yes the old sample loads, but the new one doesn't - and yet I just compared the files and they are identical in size.

Right, the problem doesn't seem to be to do with the sfz files themselves, I have determined that they are not corrupted and are identical. However if I attempt to load the same sfz GSP086 (FM2 08 03 01.00).sfz. from the folder Rapture Pro is supposed to be using it fails to load, but if I load the exact same file from the original Rapture content folder, it loads. So I'm not sure what is going on now, they are in folders with identical names, the original Rapture folder structure is actually 1 level deeper than the Rapture Pro folder structure so it's not that, even if I copy the sfz files from the old Rapture content folder to the new one they still fail to load unless I load them from the old folder!

[irvg]

Got a message from Cakewalk tech support that the installer problem (deleting the files) has been resolved and an updated installer is now in place. At least they responded fairly quickly

[AROSSA [Cakewalk]]

We wanted to officially respond to the issues that jackmazzotti and a few other users reported regarding the OS X installer deleting files in custom folders. Unfortunately, this was a serious bug that went undiscovered when we launched. As soon as we found out about the issue, we immediately began working to resolve this and a fix has now been deployed. Moving forward, Rapture Pro will behave as intended when installing by merging files into a custom folder, and existing content will remain untouched. We apologize to users that experienced this issue. We are 100% committed to providing a great experience on OS X. Obviously, this was an error on our part but in no way diminishes our commitment to our customers.

As this was our first release with Command Center OS X, we are aware of some issues with it and are working as quickly as possible to address these. Long term, we believe that Command Center will offer customers a much better installation experience, but as with any launch, there are always a few wrinkles that need to be ironed out.

I hope that users that experienced any of these issues will accept our sincerest apologies.

[Nightpolymath]

Got a message from Cakewalk tech support that the installer problem (deleting the files) has been resolved and an updated installer is now in place. At least they responded fairly quickly

Which is ironic. They still haven't resolved a simple registration problem for CA-2A on Yosemite. Many weeks now. The thing is still up for sale - woe to the OS X user who happens to buy the plugin.

[MarlaPodolski]

I still like and will keep my original Rapture and the many presets (programs) I have gathered/bought in last few years. Got it for $20 and some Soundsets quite cheap. Lovely.... I don't program it a lot, just minor tweaks to sounds already set up usually. It installed so easily, sounds just wonderful and works every time without issue.

I have no interest in having 'more' Rapture than this v.1.22. It's a fine rom-synth for what it is and has enough features and flexibility. I'm keeping it. I use it on a regular basis from the start.

Why this always needing more, more synth, more features, more control, more rubbish, more, more?

[Nightpolymath]

Why this always needing more, more synth, more features, more control, more rubbish, more, more?

Are you OK?

[aMUSEd]

We wanted to officially respond to the issues that jackmazzotti and a few other users reported regarding the OS X installer deleting files in custom folders. Unfortunately, this was a serious bug that went undiscovered when we launched. As soon as we found out about the issue, we immediately began working to resolve this and a fix has now been deployed. Moving forward, Rapture Pro will behave as intended when installing by merging files into a custom folder, and existing content will remain untouched. We apologize to users that experienced this issue. We are 100% committed to providing a great experience on OS X. Obviously, this was an error on our part but in no way diminishes our commitment to our customers.

As this was our first release with Command Center OS X, we are aware of some issues with it and are working as quickly as possible to address these. Long term, we believe that Command Center will offer customers a much better installation experience, but as with any launch, there are always a few wrinkles that need to be ironed out.

I hope that users that experienced any of these issues will accept our sincerest apologies.

Thanks, do we need to update the Command centre, Rapture installers or what?

Also can you figure out what's going wrong with the Piscis presets (see my above posts)? - it's very weird.

[AROSSA [Cakewalk]]

We wanted to officially respond to the issues that jackmazzotti and a few other users reported regarding the OS X installer deleting files in custom folders. Unfortunately, this was a serious bug that went undiscovered when we launched. As soon as we found out about the issue, we immediately began working to resolve this and a fix has now been deployed. Moving forward, Rapture Pro will behave as intended when installing by merging files into a custom folder, and existing content will remain untouched. We apologize to users that experienced this issue. We are 100% committed to providing a great experience on OS X. Obviously, this was an error on our part but in no way diminishes our commitment to our customers.

As this was our first release with Command Center OS X, we are aware of some issues with it and are working as quickly as possible to address these. Long term, we believe that Command Center will offer customers a much better installation experience, but as with any launch, there are always a few wrinkles that need to be ironed out.

I hope that users that experienced any of these issues will accept our sincerest apologies.

Thanks, can you figure out what's going wrong with the Piscis presets (see my above posts)? - it's very weird.

Yes, I will look into that.

[digitalboytn]

Why this always needing more, more synth, more features, more control, more rubbish, more, more?

Unfortunately,that is the mindset that most people are caught up in

And the manufacturers are very happy to create the need and then supply to fulfill the demand...

Personally,I am working towards a simpler situation in all aspects of my life...

A more minimalist approach certainly has it's benefits...

Where less is more...The 80/20 principal...

Less synths, less features, less control, less rubbish, less, less

[jdnz]

the original Rapture folder structure is actually 1 level deeper than the Rapture Pro folder structure so it's not that, even if I copy the sfz files from the old Rapture content folder to the new one they still fail to load unless I load them from the old folder!

check the total path length (directory names+filename) for the 'good' sfz vs the 'bad' - even though it's one level deeper the total path name could be shorter, and the bad one could be going over some internal path length limit in rapture pro (wouldn't be the first plugin where they didn't allow for really long paths)

[BBFG#]

Why this always needing more, more synth, more features, more control, more rubbish, more, more?

Unfortunately,that is the mindset that most people are caught up in
And the manufacturers are very happy to create the need and then supply to fulfill the demand...
Personally,I am working towards a simpler situation in all aspects of my life...
A more minimalist approach certainly has it's benefits...
Where less is more...The 80/20 principal...
Less synths, less features, less control, less rubbish, less, less

Minimalism is the goal here too. The only real thing going for Rapture for me was it came with the DAW and is a NFR product. So I really want to use it since the other option is just to uninstall it as abandonware. And since that means owning it for its lifetime, it is good to keep in the tool box.

But seeing the issues are the ones I've dealt with in the past does beg the question of whether the company has chosen to do things differently or continue with a repackaged program they intend on running under the same philosophy with exactly the same issues.

Under this goal of minimalism though, I can't currently see where it will be able to survive my cut list.