I've recently added Flexor 3 to the system and naturally the serial number shows up in my settings dialogue box.
However, I can't seem to find where the allkeys.sfk file is stored or whether it is possible to generate one - I like to keep a safe copy of this as a backup.
Is there a way of generating it or do I have to request an update from Ralf please?
allkeys file
you should be able to download allkeys files from your user on the cw site... if that works atm?
otherwise for flexor3 you get a seperate key directly from adern
afaik
otherwise for flexor3 you get a seperate key directly from adern
afaik
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
1) the cw user site is down since ages. I doubt since that it will reappear in the near future.
2) although I kinda believe that the generated key you receive from adern is in fact generated by ralf on behalf of adern, I don't know if you are able to bother ralf directly with that
3) you should have a scope.rgy file somewhere in your scope folder or one of it's subfolders. make a copy of that and rename it allkeys.skf when you need it. you can compare your current allkeys and the scope.rgy with a file viewer, and they should differ from each other by that certain Flexor III line.
-greetings, markus-
2) although I kinda believe that the generated key you receive from adern is in fact generated by ralf on behalf of adern, I don't know if you are able to bother ralf directly with that
3) you should have a scope.rgy file somewhere in your scope folder or one of it's subfolders. make a copy of that and rename it allkeys.skf when you need it. you can compare your current allkeys and the scope.rgy with a file viewer, and they should differ from each other by that certain Flexor III line.
-greetings, markus-
--
I'm sorry, but my karma just ran over your dogma.
I'm sorry, but my karma just ran over your dogma.
-
Neil B
Thanks both for the reply.
Actually there was a bit of a misunderstanding - Flexor 3 is working fine - I simply typed the code in when I received it.
It's just that I checked the registry, saw it was there and thought "I'd better take a fresh backup of my allkeys file".
Anyway Kylie - thanks for the tip
Are you then saying that the scope.rgy file, when copied is exactly like the allkeys file? Would I be able to import it in case of problems?
Faxinadu - Creamware site suggests emailing them for an allkeys file, so there is a way of getting one, but if Kylie's method works, then that's fine (or I just type the codes in again should I ever have to!)
Again, thanks to you both.
Actually there was a bit of a misunderstanding - Flexor 3 is working fine - I simply typed the code in when I received it.
It's just that I checked the registry, saw it was there and thought "I'd better take a fresh backup of my allkeys file".
Anyway Kylie - thanks for the tip
Are you then saying that the scope.rgy file, when copied is exactly like the allkeys file? Would I be able to import it in case of problems?
Faxinadu - Creamware site suggests emailing them for an allkeys file, so there is a way of getting one, but if Kylie's method works, then that's fine (or I just type the codes in again should I ever have to!)
Again, thanks to you both.
yes, the content of both files is identical - and I've imported several times from scope.rgyNeil B wrote:...Are you then saying that the scope.rgy file, when copied is exactly like the allkeys file? Would I be able to import it in case of problems?
if you do a fresh install from scratch, then there will be an empty scope.rgy be created in the application directory.
All imported keys will go into that file which will grow - just make a copy of it and you have your current keys.
you might want to rename your backup of scope.rgy to avoid messing it with the empty file of a fresh install - replacing the keys by nothing isn't that funny...
cheers, Tom
FleXor v3I (full or upgrade) is an independant license available only from Adern's database so Ralf will not have it. Save him some email time. Older Flexor 1.x keyswould be only available from SC/Ralf as Adern will not market past versions (needed for users who already own it and only bought the upgrade key from Adern) . 
Older Flexor 1.x keyswould be only available from SC/Ralf as Adern will not market past versions (needed for users who already own it and only bought the upgrade key from Adern) . that's how I understood it. it's always a good idea to make a backup of those files, especially when it contains license information you won't get from ralf by requesting the allkeys file again (concerning F3, I was obviously wrong here. thanks valis for enlightening meNeil B wrote: Actually there was a bit of a misunderstanding - Flexor 3 is working fine - I simply typed the code in when I received it.
It's just that I checked the registry, saw it was there and thought "I'd better take a fresh backup of my allkeys file".
).I bought a scope card some months ago, and got the scope.rgy from the seller (it contained an additional key for the stw ambience). since I had no allkeys file, I imported the information from the supplied file (I don't remember if I had to rename the original file to allkeys.skf, but iirc the import dialogue also accepts the scope.rgy). since I am able to use this card and all its plugins, I can assure you that it worked at least for meAre you then saying that the scope.rgy file, when copied is exactly like the allkeys file? Would I be able to import it in case of problems?
you can, btw, re-enter the activation code when prompted to, should your .rgy ever got lost, and grab the other licenses from the allkeys file from ralf. I even expect a screenshot of the registry window could do, if anything else goes wrong. the string for the device is imho identical with the activation key. you could then manually start every device you have a license for and enter the key for it, even with no backup (execpt the printed sheet).
I didn't have to try that, but I'm kinda conviced it would work
-greetings, markus-
--
I'm sorry, but my karma just ran over your dogma.
I'm sorry, but my karma just ran over your dogma.
-
Neil B
noob with Luna II
I just picked up a Luna II used, and I'm trying to get the Allkeys file. Should I go ahead and write Ralf as so many threads here say? Got it last night, very antsy about getting it running. I have nefarious plans for this card in my studio!!
Thanks in advance for any help you can offer!
Thanks in advance for any help you can offer!
That makes some sense. I was wondering if I hit a holiday season, but it's a bit late in the year for the full holidays where everyone is gone for a month.
It seems strange that I have to wait for the manufacturer to respond to an email in order to get a key file to install the basic software to use the hardware. It would be quite nice if I could just use the card as additional processing for VST plugins without all the installation madness.
Oh well - from what I understand, it's worth the hassle.
It seems strange that I have to wait for the manufacturer to respond to an email in order to get a key file to install the basic software to use the hardware. It would be quite nice if I could just use the card as additional processing for VST plugins without all the installation madness.
Oh well - from what I understand, it's worth the hassle.
-
Mr Arkadin
- Posts: 3283
- Joined: Thu May 24, 2001 4:00 pm
Well in the old days you could generate the key yourself from the Creamware page, but due to the mature world of hackers that had to be disabled and now it has to be done manually. Once you have it it's no hassle to import it and yes it's well worth the wait - although you may be wanting some more DSPs soon. Oh and don't be confused into thinking you can use VSTis on it - you use proprietory Scope synths and effects.tormenter wrote:That makes some sense. I was wondering if I hit a holiday season, but it's a bit late in the year for the full holidays where everyone is gone for a month.
It seems strange that I have to wait for the manufacturer to respond to an email in order to get a key file to install the basic software to use the hardware. It would be quite nice if I could just use the card as additional processing for VST plugins without all the installation madness.
Oh well - from what I understand, it's worth the hassle.
Unfortunately, my seller got it from another seller who didn't hook him up, and he never got it going because there wasn't OS X support for it. The blame lies two sellers back, but it's still a bit lame.
I'm about at wits end with this card though. My entire intent was to install it to add a couple of compressors and/or a reverb that weren't taxing my computer's processor.
I finally got to the point where the software is installed, the new plugs show up in my VST plugins directory, I add one, change the settings, hit play, and...the computer shuts down and restarts. No warning, just off, then back on.
I'm using a Focusrite Saffire Pro 26 i/o as my audio interface, and the card as purely a plugin runner, no external i/o through the card at all. The card and the interface are both set to 48Khz, but I wonder if I need to bring a clock in from the SPDIF out of the Focusrite in order to get them synced together.
Any experience with this?
Also, what's up with Luna software? I open it, it asks for some registration key and shows me something to copy that looks like a serial number followed by a registry key with the option to copy this, but no clue as to where to past it to generate an activation key for whatever the hell it's asking for activation of. As long as I don't screw with that, Luna shows up in the start menu at startup, but the moment I try to do anything with the software (3.1c) I get this registration thing and I don't know how to get past it, Luna shuts down, and I get an error message saying the drivers aren't properly installed. What?
All in all, I would say this has been a most frustrating, confusing, and bizarre trip down early software development memory lane. I remember when every program had its own interface and its own set of rules of how to get from installation to actual use. I'm now pretty much ready to sell (or return) this card that has taken more of my time with fewer results than any other piece of hardware I've ever installed on any computer for any purpose.
I'm about at wits end with this card though. My entire intent was to install it to add a couple of compressors and/or a reverb that weren't taxing my computer's processor.
I finally got to the point where the software is installed, the new plugs show up in my VST plugins directory, I add one, change the settings, hit play, and...the computer shuts down and restarts. No warning, just off, then back on.
I'm using a Focusrite Saffire Pro 26 i/o as my audio interface, and the card as purely a plugin runner, no external i/o through the card at all. The card and the interface are both set to 48Khz, but I wonder if I need to bring a clock in from the SPDIF out of the Focusrite in order to get them synced together.
Any experience with this?
Also, what's up with Luna software? I open it, it asks for some registration key and shows me something to copy that looks like a serial number followed by a registry key with the option to copy this, but no clue as to where to past it to generate an activation key for whatever the hell it's asking for activation of. As long as I don't screw with that, Luna shows up in the start menu at startup, but the moment I try to do anything with the software (3.1c) I get this registration thing and I don't know how to get past it, Luna shuts down, and I get an error message saying the drivers aren't properly installed. What?
All in all, I would say this has been a most frustrating, confusing, and bizarre trip down early software development memory lane. I remember when every program had its own interface and its own set of rules of how to get from installation to actual use. I'm now pretty much ready to sell (or return) this card that has taken more of my time with fewer results than any other piece of hardware I've ever installed on any computer for any purpose.
i assure you that the problems you are having are not the card's fault, unless it's actually broken. THEY DO WORK PROPERLY.
you want to use the scope software. the Luna software is ancient.
the registration window is because you need KEYS to drive the car. you can obtain the keys by writing to soniccore. if you write during the week, you'll likely have keys the next day. if you write on the weekend, you will usually get the keys by monday. the fact that you don't have the keyfile IS the fault of dthe last seller. it is he who has messed you up, but it's not fatal. just a bit of patience will sort out all your troubles. if you need help, PM me, i'd be glad to help.
you want to use the scope software. the Luna software is ancient.
the registration window is because you need KEYS to drive the car. you can obtain the keys by writing to soniccore. if you write during the week, you'll likely have keys the next day. if you write on the weekend, you will usually get the keys by monday. the fact that you don't have the keyfile IS the fault of dthe last seller. it is he who has messed you up, but it's not fatal. just a bit of patience will sort out all your troubles. if you need help, PM me, i'd be glad to help.
Perhaps I wasn't clear.
I have the allkeys file. I installed Scope 4.0. It blows my machine up.
What would help a total newbie with this hardware/software configuration is a list of the software I actually need to get started and what the latest versions are - drivers, core software, what's new and works, what's old and doesn't work.
Something like:
1. Install card
2. Install X.X version drivers, downloaded from (url)
3. Install software/plugins platform, downloaded from (other url)
4. Sync your card to the external audio interface (do I need to do this, or will it pick up the sync when I start Cubase?)
5. Open Cubase (Nuendo, Logic, Sonar, whatever) and use the new plugins with happy faces all around!
Instead, I've downloaded two versions of scope (325Mb each), two versions of Luna, two versions of the drivers for the card - one an 2.5 beta version, the other an incomplete install of the 3.0 drivers, which I had to roll back to the 2.5 beta because it half installed then asked for pieces of the installation that don't exist on the FTP server.
Topping that off, now that I actually have the plugins installed, I'm getting BAD graphic artifacts - the plugins will occasionally lose the interface for no reason. Shut them down, open them again, most of the time the interface comes back. But, if I actually try to hit play, boom - instant computer shut down.
I'm really not a new guy to computer recording - I was multi-tracking audio in '91 with the first versions of Logic Audio, and was the lead Mac tech for a major Chicago firm back then. I've kept my tech skills current, but this card has given me a serious beating.
So, to make it basic, I need the latest driver for the card, and the latest version of the software, which is Scope, not Luna. I should uninstall Luna? Is having Luna installed as well as Scope possibly blowing things up? I was under the impression that Luna was for card control (like Cuemix for Motu control) and Scope was for platform control. Apparently the name Luna on the card and the name Luna on the software are no longer related.
I have the allkeys file. I installed Scope 4.0. It blows my machine up.
What would help a total newbie with this hardware/software configuration is a list of the software I actually need to get started and what the latest versions are - drivers, core software, what's new and works, what's old and doesn't work.
Something like:
1. Install card
2. Install X.X version drivers, downloaded from (url)
3. Install software/plugins platform, downloaded from (other url)
4. Sync your card to the external audio interface (do I need to do this, or will it pick up the sync when I start Cubase?)
5. Open Cubase (Nuendo, Logic, Sonar, whatever) and use the new plugins with happy faces all around!
Instead, I've downloaded two versions of scope (325Mb each), two versions of Luna, two versions of the drivers for the card - one an 2.5 beta version, the other an incomplete install of the 3.0 drivers, which I had to roll back to the 2.5 beta because it half installed then asked for pieces of the installation that don't exist on the FTP server.
Topping that off, now that I actually have the plugins installed, I'm getting BAD graphic artifacts - the plugins will occasionally lose the interface for no reason. Shut them down, open them again, most of the time the interface comes back. But, if I actually try to hit play, boom - instant computer shut down.
I'm really not a new guy to computer recording - I was multi-tracking audio in '91 with the first versions of Logic Audio, and was the lead Mac tech for a major Chicago firm back then. I've kept my tech skills current, but this card has given me a serious beating.
So, to make it basic, I need the latest driver for the card, and the latest version of the software, which is Scope, not Luna. I should uninstall Luna? Is having Luna installed as well as Scope possibly blowing things up? I was under the impression that Luna was for card control (like Cuemix for Motu control) and Scope was for platform control. Apparently the name Luna on the card and the name Luna on the software are no longer related.