I currently have 3x Pulsar II on a Windows XP system with Scope 5.1 (soon to upgrade to Windows 7) but I am considering a Luna II purchase with an unbalanced I/O box.
I haven't actually used my 3x Pulsar setup in a meaningul way, but what is the difference between Luna I and II?
Will Scope 5.1 work with Windows 8.1 and Cubase 7.0.7, and is anyone here using this configuration?
Also, is there a difference in the software in terms of Synthesizers and Mixing plugins, e.g. for sharing projects between setups?
Any information is greatly appreciated.
Thank you all in the forum.
Luna II, Luna I differences
Re: Luna II, Luna I differences
Scope 5.1 (PCI + XITE1-D) / Windows 8.1 and Cubase 7.5 working here - all 64 bit.
Re: Luna II, Luna I differences
Good to know, thanks.
Another question, if I buy a system that already has 5.1 included, e.g. a Luna II and it (luna card) breaks, is the license transferrable to another card, say one of my Pulsar II cards?
Thanks again
Another question, if I buy a system that already has 5.1 included, e.g. a Luna II and it (luna card) breaks, is the license transferrable to another card, say one of my Pulsar II cards?
Thanks again
Re: Luna II, Luna I differences
if you return the broken card it is.
write to support if that happens.
write to support if that happens.
Re: Luna II, Luna I differences
Yes !emotive wrote: Will Scope 5.1 work with Windows 8.1 and Cubase 7.0.7, and is anyone here using this configuration?
Windows 8.1 64bit, Scope 5.1 and Cubase Artist 7.5.
For installing card driver under Windows 8.1, you'll also need to know this :
Windows 8 requires the driver to be signed by microsoft. the Scope driver isn't signed so you must turn off the "feature" that requires this. here are two easy methods to install the driver. i prefer the second one in the link.
You can permanently enable Test Mode by opening an Elevated Command Prompt (Run as Administrator) and typing the following commands, then rebooting:
To turn it on :
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
To turn it off :
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
Best,
Matej