PlanetZ forums - scopeusers.com

Hi!

Tried to use the Pulsar I MIDI remote by connecting it to the Sequencer MIDI In. In Cubase I don't see any MIDI signals being received when clicking the remote buttons. Anybody had any luck using this thing?

/freddan

Hey this is not a real reply since i have the same problem.
pulsar 2.04 and cubase 5r6. with cubase 3.7 it did worked, with cub5 it doesn't!?!.
I did what I'm supposed to do but no response. Maybe there is something else i can't understand.
Is there anybody out there willing to help?

The Midi remote sends certain midi messages (which are configurable, I believe, check the device drawer).

In Cubase, you probably have shortcut keys to the remote as well, which you can assign both a key from your computer keyboard, and a midi message (at least, you can do this in Logic for nearly every command).

Just make sure the midi messages match in both places, it should work. I got the remote working in Logic this way even though it is supposed to be for Cubase...

Let me know if it's changed in V3 and you can't do this, I haven't tested V3 extensively yet.

OK, I'll dig some more. I think it's strange though that the MIDI indicator in Cubase doesn't show any in-signal at all when using the remote.

BTW, I'm using Pulsar 3.0 and Cubase 5r6.

<font size=-1>[ This Message was edited by: freddan on 2001-10-25 09:28 ]</font>

Since v5.xx of Cubase, midi remote is configured on the:
Edit/Key Command Preferences/Transport and Locaters page.
Make sure "Remote Active" is checked, and set all the command-event preferences you require.
Sub - maybe this one should go in the faq.
/dave

And every CC# that might being used by Cubase Remote, will not be thru-put :/ This leaves me enabling/disabling Remote Control in Cubase. Not the Transport section, but the VST remote.

Using a PC1600x, I use an .xml file for cubase to know it's assignments, and I have to manually reload that one after each reactivation.

I'm working on my midi routings now, since I want Rebirth and Reason to follow CC# (knobs/tweaks) and notes (Pattern Select/Step Program) too.
Under Win2k, it seems that nor AMT8 nor Pulsar midi ports are multi client.

Wish I was a born architect. Maybe I am.

Ok so here's my Midi Remote Tip.

In this explicatory Project, I'm gonna use:
-Sequencer Remote
-Hardware Midi Source
-Sequencer Midi Source and Dest
-ASIO source and dest
-2 midi mergers
-2 midi Filters, to filter irrelevant info.
-Midimonitors as you like

Connect Sequencer Remote to Midi Merger in1, Hardware Midi Source to midi Filter to Midi Merger in2. Send this to Sequencer Midi Dest.
Merge Hardware Midi Source and Sequencer Midi Source thru Filter to Pulsar devices and modules.

Connect your remote control device (keyboard/pc1600/... to Pulsar midi in.

As you now move faders or play keys via hardware, this signal goes to both Sequencer as Project. Plus, your Seq sends to the project.
But Seq cannot send to itself. Still, disable 'midi thru' in your Seq for the used Remote Midi Channel. Or Pulsar Project would get double signals.

This is a very basic setup, I might come back for more.

<font size=-1>[ This Message was edited by: atomic on 2002-01-21 00:16 ]</font>