THE way to install Arturia (non-iLok) plugs

[looneytunes]

Hi Everyone,

I have finally figured this out. I have a good way to install the Arturia plugins on Receptor that have the disk based registration. The method I am describing involves actually running the Arturia installers and DOES NOT involve messing around with the registry. This will also make sure that there are no path problems in the install. I have been able to install ARP2600V, Minimoog V, CS80V, and Moog Modular V all from this method using the original install disks.


This method involves working with both hardware and Linux, so you need to be courageous enough to do this (eg you will probably void the warranty). You need to also be adept at following Oggs instructions to be able to gain "ssh" access to your receptor (from a remote host, like "putty" on a PC, or "ssh" from an Xterm window on MacOSX.

Before I go further and detail what needs to be done, I wanted to pass on Great Kudos to BryanJ and
Ogg (Olle Gustafson) who have given significant hints (I mostly pulled things together).

Also before going any further, I want to extend the same disclaimers that Ogg posts:

Code: Select all

I take no responsibility for what you do with the information on this page. Don't complain to Muse Research (or me) if you accigently remove everything with a missplaced 'rm -rf'. Make sure you have backups! Don't blindly follow the things you read. Make sure to think things through before you actually do anything. Lookup Linux commands on Google and Wiki to get an understanding of what they are before you execute them.

Enough of the Legalese!

The basic steps are:
1.) [SW] Get Root Access (setup a root password) on your receptor
2.) [SW] Setup Remote Access (via 'ssh') to your receptor
3.) [HW] Install a CD-ROM drive
4.) [SW] Make the drive available in Linux
5.) [SW] Run the Arturia installer

I will illustrate this method using Arturia CS80V in these posts.

Steps [1-2] are already well documented in [1] and [2].

I will cover steps 3-5 in the next 3 posts.

Kevin L

[looneytunes]

Step 3: [HW] Install a CD-ROM drive

This is the Hardware step that will involve opening up your Receptor. You will require additional Hardware too.

What you will need

0.) small and smaller phillips screwdrivers to remove the top of Receptors case.

1.) a standard ATAPI/IDE CDROM drive
(I'm using a SONY CDU5232 CDROM)

2.) a '4 pin Power Y Cable'

The Y cable is a MALE 4 pin power connector on one side, and two FEMALE 4 pin connectors on the other side. The two FEMALE sides will connect to the power connections on both your Receptor HD and the CDROM. The MALE connector will connect to the power cable that is currently directly connected to your Receptor HD.

0.) Choose a good place to work

You should have a place to work where you can still keep all your current connections to receptor.

For this part, you will need to unplug Receptors power cord.

Be careful to work in an area where you will not generate a static charge

Be careful to keep the screws in a place where they won't be scattered or lost.

1.) Remove the Receptor case top

You need to first remove the Rack ears.

Then you will need to remove 9 screws:

3 on the left side,
3 on the right side,
and 3 on the back.

The metal panel should simply lift off the top.


2.) Configure the CDROM to be the IDE SLAVE

Instructions for this are typically printed in the drive's instructions and/or on the back of the CDROM drive itself.

There is typically a small jumper on the backplane of the CDROM drive. By default, this is usually set to be the IDE MASTER. You should move the jumper to the position where the CDROM will be the IDE SLAVE.

3.) Disconnect the power connector from Receptors Power Supply to the HD

This is a translucent white plug on the far right side of the Hard Drive. Pull this out, from the Hard Drive.

4.) Connect the power connector to the MALE connector of the Power Y Cable

5.) Connect the FEMALE connector of the Power Y Cable back to the Receptor HD

6.) Connect the other FEMALE connector of the Power Y Cable to the CDROM

7.) Connect the IDE bus cable to the CDROM drive

The IDE cable going to Receptor's Hard Drive should have a spare connector in the middle of the bus cable. Plug this connector to the back of your CDROM drive.


8.) Plug in Receptors Power cord

9.) Power up Receptor

10.) Verify the status indicator on the CDROM lights up

You should also be able to open the tray of the drive by hitting the eject button.


Now you have the CDROM installed with Receptors Hardware. You will next make the OS aware of this drive.

[looneytunes]

Step 4: [SW] Make the drive available in Linux

This is the Software step that you need to do to make Receptor's OS aware of the drive.


1.) Get to Receptors display

You can either do this via Receptor Remote (on a PC or Mac), or via a keyboard and display directly hooked up to your Receptor.


2.) Remote SSH into receptor

In addition to the Receptor interface, you now remote login into Receptor (via ssh) as root.

We will refer to this as the terminal window.


3.) Check to see that Receptor has identified the CDROM as an IDE device

You can do this via the Linux command 'dmesg'

Code: Select all

 # dmesg | more
...
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: ATA-66/100 forced bit set (WARNING)!!
    ide0: BM-DMA at 0xe200-0xe207, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xe208-0xe20f, BIOS settings: hdc:pio, hdd:pio
hda: ST3400633A, ATA DISK drive
hdb: SONY CD-ROM CDU5232, ATAPI CD/DVD-ROM drive
....

 

The important thing to note is that last line, that identifies the CDROM.

If you do not see a CDROM mounted on 'hdb' or 'hdc', you probably have a device conflict with Receptors HD - you should go back and make sure that your CDROM is configured as a slave.


4.) Mount the device

Code: Select all

 # mkdir /mnt/cdrom
# mount /dev/hdb /mnt/cdrom

This will make the OS see the drive. To verify, you can do a 'df'

Code: Select all

 # df
 df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hda2                2893660        748528       1998140     28% /
/dev/hda1                   101089             5801          90069      7% /boot
/dev/hda4            379652144 255814364 104552552     71% /c
none                         1026500                   0   1026500         0% /dev/shm
/dev/hdb                     764980        764980         0          100%     /mnt/cdrom

(sorry if the formatting on this table is bad. The important thing to note is that /dev/hdb shows in the mount table.


5.) Identify the mount to WINE

This step makes the WINE translation layer aware of the drive as a windows drive.

Code: Select all

 # cd ~/.wine/dosdevices
# ln -s /mnt/cdrom h:

Now you are ready to run the Arturia installer from the CDROM.

[looneytunes]

Step 5: [SW] Run the Arturia installer

This is the cool part. You actually can run a windows .exe file (like an installer) on Receptor. The important thing to remember is that you need to redirect Windows to a different display.


1.) change directory to the CS80V CDROM

Code: Select all

 # cd ~/.wine/dosdevices
# cd h:

2.) display the directory contents of the CS80V CD

Code: Select all

 # ls
cs80v_en_quickstart.pdf  cs80v_jp_quickstart.pdf  cs-80v setup.exe
cs80v_fr_quickstart.pdf  cs-80v mac install       wav.dat

3.) set the display to be the Receptor Interface

When you do this, the installer will bring up its windows either in your Receptor Remote interface or display that is connected to Receptor

Code: Select all

 # export DISPLAY=:1

4.) Run the Arturia installer

You do this by invoking 'wine' with the installer.exe

Code: Select all

 # wine 'cs-80v setup.exe'
c:\ : This is not a CDROM !
found volume
fopen succeeded
Read byte : B4
fixme:ole:CoCreateInstance no classfactory created for CLSID {00021401-0000-0000-c000-000000000046}, hres is 0x80040154

NOTE: I had to single quote the name since it has spaces.

This will launch Arturia's installer dialogs on your desktop.

There are some important things you should specify for paths to the installer:



4A.) When the installer asks for the 'destination directory', do not use the default

It will default to "C:\PROGRAM FILES\Arturia\CS80V"

Instead, use the browse button, and navigate to:
"C:\program files\vst plugins\unsupported plugins\Arturia\CS80V"


4B.) When the installer asks for the 'VST plugins directory', do not use the default


Instead, use the browse button, and navigate to the same directory specified above:
"C:\program files\vst plugins\unsupported plugins\Arturia\CS80V"


4C.) When the installer completes, Go to the 'SETUP' tab on your Receptors Display, and install unsupported plugins (via usual button push)

That's it. They are up and running

I have been able to install ARP2600V, Minimoog V, CS80V, and Moog Modular V all from this method using the original install disks.

[looneytunes]

Some folluwup notes:

How to get your CD back from the CDROM drive

Code: Select all

#cd /
#umount /dev/hdb

Now you should be able to eject the CD from the drive. The next time you wish to put another CD into the drive, the only thing you really need to do is to mount the drive again, eg.

Code: Select all

#mount /dev/hdb /mnt/cdrom

(you do not need to redo the symbolic link to the wine dirs).


Carefully, undo the Hardware steps that you did, to put everything back.



As Arturia does not use FXBx/FXPs to store their patches, you will need to manually Receptorize these.

I'll send some more notes later, regarding updating existing Arturia plugs.

Regards,
Kevin L

[Hybernation]

Kevin, this is absolutely fabulous stuff here. I cannot thank you enough for putting this together. I'll be trying it as soon as I get my receptor back from Muse!

One question: have you also run all the updaters for the various plugs, or are you just using the (older) version on your CDRoms?

[looneytunes]

Hi Hyber,

I'm in the middle of testing this out. Not going as smooth as I would like.

Some things I am trying:

1.) copying the updater.exe's to Receptor, and then running them from Wine
(this doesn't seem to work well, don't know why).

2.) overwriting the existing installs, manually changing registry keys for authorizations.
(works for some, I haven't found this very stable yet (eg. I do the installation, it runs and looks OK, and then the VSTi later disappears from the instrument list)

I also think there is something flaky going on here, like the latest updates were compiled against VST 2.4, and Muse hasn't adopted this yet - some errors in the syslog indicate this.

CS80V update seems relatively stable so far.

More info later when I get a better handle on it ...

Regards,
KTL

PS. John, I was at JavaOne too. I work for Sun, and was up in SF last Monday. Next time around let me know when you're in town.

[Bryan J]

Hi Kevin,

This is a beautiful thing. Good work on pulling it all together. Hopefully soon, Muse will provide automounting of external USB CD-ROMs, making this even easier in the future.

Also, which versions were you using? While I had GUI problems with earlier versions of the Arturia plugins, it seems that the latest ones work quite well with the Receptor. I'm currently using...

Minimoog 1.6
CS-80V 1.6
Arp2600V 1.2
Modular V (whatever the latest is)

The other thing I love about your new method is that it allows you to run the installer straight from the Receptor itself... something I hadn't even tried before. (I was only using the CDROM drive for authorizations).

If the updaters are failing however, maybe it might make sense for others to install from their original install CD using your method, but then just copy the Arturia VSTi folders and Arturia Program Files from a working (but updated) Windows install. That way, all the registry entries and any additional DLL files are handled first, so that only a few files need to be copied over afterwards.

Bryan J

[looneytunes]

Hi Bryan,

I am at the same levels as you, except for Moog Modular (I'm still looking for my 2.0 installer).

I ended up doing the same thing as you did for the updates.

The Receptor is a different beast than windows, and I believe Muse has chosen to 'throttle down' task priorities on GUI tasks (then audio tasks). This seems to result in audio artifacts when the GUI editor is present and you are clicking around. I even notice this a bit on the latest versions. However, when the editor is not up, the audio performance and CPU usage is very good.

I'd still like to figure out how to make the updaters work natively.

Regards,
Kevin L

[Kermit Jagger]

Great explanation, but I'd like to know if anyone has successfully run an external USB CD-ROM.

[looneytunes]

Hi Kermit,

I haven't tried it myself, but Ogg alluded to the possibility of this here.

Seems like if you can get the Receptor OS to recognize this, you could simply create the symbolic link in wine like I did above, and then install from wine as above.

Again, I can't confirm this - and it would be cool if someone with a spare USB ROM drive could confirm.

Regards,
Kevin L

[Bryan J]

I couldn't ever get a USB drive to work... which is what ultimately led me to just connect a CDROM drive to the IDE bus... I might have been missing something though, as I'm still a bit new to Linux.

[looneytunes]

Hi everyone,
Here's some footnotes, hopefully to avoid some downstream 'Gotchas' :

1.) For the first few (two, I think) times that you instantiate (and open the editors) for these Arturia plugs, the plugs try to authorize by looking for the disk. It is probably a good idea to install/authorize as above, restart your receptor (with the Disk still attached), instantiate the plug on a receptor channel, and bring up the editor. It would be a shame to bundle everything back up, and find the "insert original CD" dialog appearing the next time you open the VSTi editor for the Arturia plug.

2.) You also might wish to plan ahead for installing the preset banks from Arturia's support site (such that you import these files into the Arturia VSTi editors while you still have the CDROM hooked up). As well as for updating the VSTi, the Arturia plugs also look for the CDROM when you import banks.

Regards,
KTL

[Hybernation]

looney,
Got them ALL working. Was able to take MiniMoogV and CS80V to 1.5 but NOT 1.6 just running the exe's from ssh. Fabulous stuff, thanks again for all the legwork on this one.

That whole "running the exe via ssh" thing is just totally fabulous. I just got back my Beta OS 1.6/K4 receptor a couple of weeks ago, and it was a virgin unit, so I've had to reinstall pretty much everything that I had working before (that I felt was needed). Many of them I did before using the "hunt down the registry entries" method, and this was SO Much easier. Plus I got a few running this way that I NEVER got to run before, such as Ravity!

Cheers and thanks again,
John

[looneytunes]

Hey John,

Great! Congratulations!

To me, this is the single most important (unsupported) install method. And for me, those legacy Arturia synths are about as important as Kontakt and Ivory on Receptor (though the OP-X is right up there too).

As Kermit mentioned before, once the USB CDROM support is there, this becomes more of a user operation.

BTW, I got this up and working after upgrading my 2 receptors. Muse had copied most of my data files when I did my upgrade, but I still had to uninstall/deauthorize and re-install/authorize. Still, this was much easier than starting from ground zero. Many Kudos to Muse for going the extra mile for me by doing this (I think I kept Dave in the shop after midnight one evening copying ~200g on a HD). This is what makes them a great company.

Regards,
Kevin Looney