VRC-S, eh.. whats the idea of this?

Stige · Post by **Stige** » Thu Apr 08, 2004 6:39 am

I've been trying to get vrc-s remote control device working, but no luck. The manual describes clearly, how to set up it for controlling cubase via ASIO2 protocol. But.. this device simply does nothing. Play, stop, rewind, forward buttons doesn't react at all, even if I'd hit them with hammer. Does anyone know, how to blow some life to this device? What I understand vrc-s should start sending timecode when I press 'play', but nothing happens. Just nice graphics in an empty shell. I'm quite sure the problem is vrc-s itself. The transport buttons aren't functional.
I know i can use 'sequencer remote' device for controlling cubase, but I'd like to have more visual control about playback position, markers, etc..

Thanks for your help

<font size=-1>[ This Message was edited by: Stige on 2004-04-08 07:42 ]</font>

virtualstudio · Post by **virtualstudio** » Thu Apr 08, 2004 7:00 am

did you set the sync button in the transportbar from cubase on? dbl click for settings, set sync source to asio. and in project clock out to asio dest.

this should work

Post by **hubird** » Thu Apr 08, 2004 8:12 am

and don't forget to choose the right midi track in Cubase...
That's why I stopped using it, you always get confronted with the fact that you changed to another track before going back to SFP...
There should be a way to make the interaction independent from having active a track, but I never got that figured out.
I tried IAC bus, and all other thinkable tricks, but without any result.
good luck, keep us informed about your progress

Stige · Post by **Stige** » Thu Apr 08, 2004 10:21 am

Thanks for the replies. I've tried everything possible, I can think.
I've been isolating the problem to the vrc-s unit. It simply doesn't send timecode or anything. It's fully dumb. What I understand, vrc should generate the timecode, which other units have to follow. Sadly it's just silent. I have to give up with this, vrc-s is not a functional plugin (in my system). So i'll stick with 'sequencer remote'

PS: have you actually got it working?

PPs: correction: Have you actually got it doing anything?

<font size=-1>[ This Message was edited by: Stige on 2004-04-08 11:26 ]</font>

marcuspocus · Post by **marcuspocus** » Thu Apr 08, 2004 10:31 am

VRC-S is made to control a DAT or VDAT...

The clk output is only working when receiving timecode info FROM the device it control, aka VDAT.

When VDAT is connected to VRC-S, it send timecode info for the sequencer to follow.

It is NOT a remote control for a sequencer, it is a remote control for a DAT machine or a VDAT....

Same goes to VRC-128

alfonso · Post by **alfonso** » Thu Apr 08, 2004 10:32 am

I think it needs to be connected to a VDAT or an ADAT to work. Just a thought.

alfonso · Post by **alfonso** » Thu Apr 08, 2004 10:33 am

haha marcus, we posted almost together

Stige · Post by **Stige** » Thu Apr 08, 2004 11:10 am

Thanks a lot, I understand it perfectly now

. If creamware gives us a new plugin for half price, as the newest rumour goes now, VDAT might be mine then.

marcuspocus · Post by **marcuspocus** » Thu Apr 08, 2004 2:02 pm

And i'd say, that's a very good choice

It's the most abused plugin i own...

virtualstudio · Post by **virtualstudio** » Thu Apr 08, 2004 2:03 pm

excuse me, I so used to working with VDAT,
that I automaticly presumed it would work without.

VDAT is for sure very good choise!!, still one of my favorite plug-ins!