Upgrading to Scope v5.1 in a 3 card system

[sergiosimoes]

Hi. Sorry if this question has been answered here many times but I could not find a clear answer and, if there is one in the S|C site, it's in Gree... I mean.... German

I have a machine with 3 cards (Pulsar+Luna+Scope) running Scope v4.5 and WinXP
I'll upgrade it and intend to use Win7/64, keeping the 3 cards. So I'll need to upgrade for Scope v5.1
I think it'll be better to license Scope 5.1 for the bigger card (Scope), and I know that this will allow
me to use the DSP power of all 3 cards in the new system, as ever.
The problem is: I have a device already licensed to the Luna card that is not part of the Scope 5.1 pack: the Prodyssey.

So, my questions are:
- Will I need a new key to run Prodyssey in the upgraded system or will I be able to activate it with the key I already have?
- If a new key is needed and if I choose to associate v5.1 with the Scope card, does this mean that I will
not be able to activate the Prodyssey in the new system? Or will S|C provide me a new key so I'll keep Prodyssey
running, although still associated with the Luna card?

Thanks a lot.

Sergio

[garyb]

yes, just send in your old keyfile attached to an email referencing your order number and the serial number of the card updated to v5.1.

you'll get a keyfile with v5 keys for the other cards' optional devices even though the v5.1 software key will only work with the updated card.

actually, it's cheaper to upgrade the Luna, so you could just upgrade the Luna. i guess it depends on what you want to do.

by the way, there's a little British flag at the top of the webpage on the right. if you click on it, you get the English version.

[sergiosimoes]

Thanks for the help, Gary.

Let me see if I got it straight: a device's license key (e.g. a synth) does not depend only on the serial number of the card for which the device is licensed, but also on the version of the Scope platform that is running on the system? (at least, the keys for version 5 and above must be all be renewed?). Is that correct?

But what if I have 3rd part devices installed? For instance, I have Flexor 1.5 licensed for the Scope card. I'll have to contact Adern and ask for a new Key?

Also I have the Scope SDK (i got it from Creamware after having bought the Scope card). If I have it installed will his key be updated too; will I be able to run it on Scope 5.1? (maybe it's a dumb question; i really never installed it to begin with. But always have this hope of finding some time to play with it, as I have some background on programming and on DSP theory).

And about the S|C site: of course I clicked on the Brit flag; and navigated on all the pages in English. But when accessing the FAQ pages, the links and content are still in German

Again, many thanks

Sergio

[garyb]

you'll only be able to use the v4 SDK, although you are welcome to purchase the v5 SDK. i'd wait until v6 comes out, personally. that has nothing to do with the v5.1 key, however. SDK and Scope are seperate applications.

the Flexor key can be updated by S|C. that's why i told you to send in you old keyfile because yes, keys are tied to cards and the proper version of Scope both.

[sergiosimoes]

Many, many thanks Gary. Things are starting to make some sense again.

One last question (I hope): You said "...you'll only be able to use the v4 SDK..." and that the SDK and SFP are independent applications. Can I develop devices with SDK v4 compatible with Scope 5.1? What the new SDKs offer to justify a purchase?

Well... back to the upgrade plans
BTW, my new machine will be based on an Intel Dh55hc Lga1156 board, as per your recommendations written in another discussion thread.

See ya

Sergio

[garyb]

yes, that board should work, though you may need to disable a few unused devices to get a couple of free irqs, no big deal. the Pulsar1 will degrade performace a bit, but it shouldn't make a lot of difference to you. the extra i/o and dsps are probably worth the pci bus performance hit.

yes, v4 SDK devices should work in v5, the newer SDK offers some improvements and better compatiblity with v5. as i said, things will likely change a bit with v6, so i'd wait to worry about SDK.