PlanetZ forums - scopeusers.com

I finally got my new PC setup with Scope 5 and cards. Basically I run it through a Mac via midi as a sound device. It autoloads and works fine. My problem is that no other applications, and I mean no sequencers, standalone, nothing else works with the cards. Configurations show the midi i/o being via Scope, but there is no midi response in the program. This happens whether the Scope programs are running or if I turn them off. That is using Windows 7 in 32 bit mode and/or Windows XP. Does anyone have an idea what's going on here?

what is in the routing window? the midi modules are in the routing window BEFORE the other program is opened, correct?

Yes; there is no problem with Scope synths, but nothing else is receiving midi.

Post a screen shot of your Scope project window.

I have the screen shot but don't know how to post it here.

When you press the 'Post Reply' button, and the window comes up where you type, below it is a browse button.

Click the Browse Button, select your file, type in the name of the file or comment in the 'file comment' box, then press 'add the file' button.
Then after it upload, put your cursor back in your message test box, and press 'place inline'

I've tried that, but I keep getting a message "The extension .(doc,rtf, etc.) is not allowed. It is in a Word file. What kind of file is acceptable? It is in a Word file because I copied screen on my PC then sent from my Mac.

Common image file types are jpg or png - please do not insert the screenshot in an MS document

Here is a .jpg. It is a simple startup.

Ok thanks cybermooks. Its a bit small and blurred, could you possibly make it a bit bigger so I can read the writing on the devices ? Up to 200K should be OK.

This is 184k

Ok that better. Well I can't see anything wrong in the project itself, I suppose it all depends on what you have connected to 'Sequencer Midi Source' ( Cubase midi track output ? ) and Scope MIDI A Source ( midi cable from Mac ? ).

Basically, this setup will send your sequencer track to an external synth (connected to Scope MIDI A Dest ) and your Scope MIDI A Source to the MINIMAX and STM 1632 - which is OK if this is what you intend.

Otherwise, if you want to control the MINIMAX from a sequencer on the same box as your scope card, you would have to connect Sequencer MIDI Source 1 to the MINIMAX.

Next thing I would try is connecting a MIDI MONITOR component to these 2 MIDI sources ( you can leave the current connections in place ) to see if there's any MIDI data coming in.

Yes Scope Midi Source A is a cable from the Mac and works fine. I haven't connected anything to Sequencer Midi Source (i.e. Cubase, Sonar) which may be the problem. I'm not sure how to do that. Again there is no problem playing any Scope instruments, it is just that I can't get midi input recognized in Sonar or any other standalone instrument even though it is set for Scope.

the Scope midi A source needs to connect to the sequencer dest. think of the sequencer dest as the mini input jacks of the sequencer. the Scope midi A source is the other end of the cable that comes into the computer from the controller....

the sequencer midi source is the midi output jack of the sequencer.

why do you have midi going through the mixer? is it being automated?

cybermooks wrote:I haven't connected anything to Sequencer Midi Source (i.e. Cubase, Sonar) which may be the problem. I'm not sure how to do that.

Well once you have Scope running with a Sequencer Midi Source, it should then appear as a MIDI output in Cubase or Sonar, if you look in the respective setup of the sequencer and make sure it is enabled to appear in the main program.

Cubase allows you to turn on or off the various MIDI I/Os so you only have to deal with the set of those you actually want to use.

So yeah, Sequencer Midi Source is no use to you if you're not using it as a MIDI I/O port in a sequencer on the same box.

yes, that's true. if the sequencer is in another box, the other box will need an interface and a cable connected to it, if through Scope, then from the card's midi output. in the routing window, the Scope midi A dest would be the thing to connect to to send midi to the other box. this behavior is exactly the same as any hardware...

I have no problem with audio connections. My problem is midi. I simply want whatever program is on the screen to respond to midi input, and that's not happening. For example, I can use the virtual keyboard in Cubase to play VIs and i get sound. It just isn't responding to midi.

Unfortunately it has been years since I've used this so I've forgotten everything. Could someone perhaps post a simple setup picture that has external programs receiving midi?

have you gone into the vst setup and made sure that the Scope midi drivers are selected and active in Cubase?

other than that and my last post, there is NO WAY that it doesn't work as long as the modules are in the routing window BEFORE Cubase is open. it MUST work.

Well if you connect a midi keyboard to a scope midi input, then in scope project you can connect Scope MIDI Source to Sequencer MIDI Dest then run cubase, the midi should transmit to a cubase track where you select scope midi as it's input. In your diagram these 2 connectors have the STM in the middle - I dont think STM will re-transmit out what its receiving in ( like a 'thru' ) - coz if it did, my BCR setup would surely infinite loop

You can see how GregH did this for samplitude - select 'Scope Project Overview' menu at

http://www.hitfoundry.com/issue_02/samptude.htm
...yet another scoperise article needed ....

Yes thank you all. I finally resolved my problem, actually when I found some old files I had set up. That takes care of sequencers, VSTis, DXis, etc. but what about a standalone version not running through a sequencer. How would you map that?