Page 1 of 1 1
Topic Options
#1705924 - 12/29/20 05:50 PM NEW VS2400cd connected to PC w/o RBus?
JoeBwanCanolli Offline
JoeBWanCannoli
Space Cadet


Registered: 01/02/13
Posts: 6
Loc: United States
Hi All, I Hope you and yours are safe and well. I have a hardly used VS2400cd with effect chips. I never bought any additions like R-BUS. Is there any way to connect the VS2400 to a pc without having an RBus to see/transfer audio files.? Thanks. Joe

Edited by JoeBwanCanolli (12/29/20 05:51 PM)

Top
#1705980 - 12/30/20 12:14 AM Re: NEW VS2400cd connected to PC w/o RBus? [Re: JoeBwanCanolli]
dkfackler Offline
Planeteer


Registered: 04/24/06
Posts: 717
Loc: Coventry, OH, planet Thulcandr...
Hey Joe:

First, the disclaimer: I don't own a 2400, but have lengthy experience with the 880, 1680, 2000 and 2480.

With that out of the way, here we go.

AFAIK, as the 2400 has no USB or SCSI(therefore, no SCSI2SD or VirDis), you have limited options for transferring files to computer without some R-BUS device(V-Fire, RPC-1 card or the like) :

1) Record from 2400 to DAW in real time. The number of simultaneous tracks transferred will probably be dependent on the capability of your DAW/interface.

2) Export your tracks as WAV files and drop into DAW. Here, you assign which tracks and v-tracks are to be exported. They are exported to CD en masse.

3) Make a CD backup of the project, then use the excellent VSWE and ripper to import the files. This can be done 'directly' into REAPER via the reaper_vs.dll. VSWE is Windows-only, but works just fine on Mac OS X running Windows in a BootCamp install or virtual machine(I use VirtualBox). IIRC, only the 32-bit version of REAPER will run the reaper_vs.dll. If someone here can verify 64-bit REAPER success, please set me straight.

It's probably possible to pull the HDD, connect to PC, then run VSWE, but that's a lot of work.

None of these is quick. The advantage of options 2 and 3 is the tracks are of the full-length project, so track sync is relatively simple. All of the above leave your original session material intact. The weakness in 2 and 3 is the lifespan of the CDRW drive. It will fail eventually, and these machines are _very_ picky about compatibility of CDRW. There is a list of known compatible drives here on The Planet. If you decide to keep the 2400, get a replacement drive ASAP. It might be worth installing the replacement right away, and keeping the working original as a known-working and compatible spare.

The 2400 can be used as a REAPER control surface via MIDI by assigning the faders, pots and buttons to REAPER actions. It is not difficult, but IS a bit time-consuming to set up, but should be a one-time thing. Once set up, it can be edited as you prefer. I prefer faders and knobs to the mouse, so use an SI-24 as surface.

~dk


Edited by dkfackler (12/30/20 12:16 AM)

Top
#1706317 - 01/01/21 09:24 PM Re: NEW VS2400cd connected to PC w/o RBus? [Re: dkfackler]
JoeBwanCanolli Offline
JoeBWanCannoli
Space Cadet


Registered: 01/02/13
Posts: 6
Loc: United States
Thank you so much for your response and advice. I have an rbus at the tip of my fingers. I will probably go that way.
Happy New Year!
Joe

Top
#1708514 - 01/11/21 09:50 PM Re: NEW VS2400cd connected to PC w/o RBus? [Re: JoeBwanCanolli]
DapperDan99 Offline
Planeteer


Registered: 07/01/09
Posts: 60
You can install an ide to esata adapter and move the hard drive out of the vs2400cd and into an Esata/usb dock. This will let you access the drive via usb on your computer, when not in use by the Vs2400. You can't simultaneously access the drive from both devices (your computer and the vs2400) - but you can access it from either device when the other is powered off.

this will let you import files to your pc and then convert them to .wav files, for futher mixing or archiving.

I've got my v2400CD setup this way and have had no problems so far

i got the idea from Juliens blog
adding esata to roland vs2400

Top
Page 1 of 1 1


Hop to:
Newest Members
raultv, Bgdlive59, AncientJuan, jairo santos, drshum
21372 Registered Users

Generated in 0.016 seconds in which 0.003 seconds were spent on a total of 13 queries. Zlib compression disabled.