MIDI loopback devices in Scope?

[auricle]

Hail, fellow citizens of the Earth.

Do the inputs and outputs of MIDI loopback devices show up in Scope? I'm thinking LoopBe and Hubi's loopback device.

Thankyou!

[Tau]

No, all you get in Scope are its own MIDI ports: Hardware MIDI and Software (virtual) MIDI ports (Seq source and dest MIDI modules).

Cheers,

T

[garyb]

the other way 'round.

midi loopback programs can see the sequencer midi source and destination module(s) and use them.

[auricle]

Ah, I see. Thanks!

I wonder if anyone has used Max to control elements of Scope?!?

[auricle]

exactly like gary said.

loopback devices are needed in windows since windows does not have an OS native midi routing.

Scope and there in the routing window there are 2 types of midi source and dest:
The HW midi I/Os of scope: Midi source and dest
The SW midi I/Os of scoep: sequencer source and dest

The latter appear in any midi applications and also in the loop back devices as cremware midi in and out.

Thanks Stardust - and I suppose if I create new sequencer source and destination ports in Scope - they will all appear in the loopback device.

[auricle]

yes they do

Rawk!

[mike.kennedy]

It would be quite handy if you could "see" other MIDI devices that are installed in the same computer from within the SFP Routing Window - e.g. PC or USB MIDI Interfaces....

[mike.kennedy]

thats what the loopback devices in the OS are needed for. They can route any other midi to the creamware midi I/Os

I appreciate that - but it would be kind of handy to use the nice graphical SFP interface to enable MIDI routing directly to external interfaces & ports rather than via the Scope MIDI Sequencer Interfaces + loopback software. It would certainly make my life easier...

[astroman]

or... to be honest... it's a piece of crap (not sure if Scope or XP is to blame)
there must be some kind of leak or so that will completely crash the machine - time may vary but it will strike
Seems to depend on the degree of user interaction somewhat

the Sequencer Midi Modules have been mentioned a couple of times in this context.
Since I'm annoyed by it on a fairly 'reliable' base, I'll replace those with the Scope hardware ports fed by another interface and see if it makes any difference... hopefully it will...

cheers, Tom

[dawman]

I have great MIDI control inside and outside of the Project Window.
When I first got Scope I was using Gigastudio and just ditched the EgoSysWamiRack that had 8 ports, and the Oberheim MC3000 had 8 x ports also. I was nervous about using Loopback and USB. It just seems like the more convenience we recieve the more trouble we see.
The all USB mobo's that Intel pushed on us were plagued with a lack of power and bandwidth.
I don't care what white paper specs they throw at us say, Firewire and USB aren't even acceptable for a home studio IMHO. And PCI MIDI is the best, but computer MIDI and USB need a jolt of extra electricity or something to work smoothly. I had to get a powered USB Hub and it removed all troubles w/ dongles, USB sticks and 88 note controllers. I also have to have hardware patchbays because of my external gear, but I have zero issues because of the extra juice.
Below is the ancient Digital Music Corporation MX8. It is the cure for any MIDI blues. I have another example of how software just don't replace certain hardware protocols. Wolf's MIDI Tool Box is great but the Panic Button is a crapshoot.
It still holds stuck notes for a second or so as it unclogs it's pipes, and this is unacceptable for live work,or studio IMHO. I use a footswitch panic button because hardware wins again. Losing a great take because a need for an all in one box solution for convenience is just not good enough IMHO.
I even disable the USB on the controllers for the hardware MIDI port. USB is only good for lighting up a few LED's.

Anyone having trouble should just break down and buy some cheap hardware that's free of the OS and lasts much longer than the next M$ upgrade.
JLCooper has great old patch bay/filtrers for 50 bucks, and the MX8's are about the same.
Just shoot some juice into the DAW and it fixes all of this crap.

[auricle]

Wow Jim, aren't you worried that one day all your gear might become self aware and try and take over the world?

I agree with what you say though, but it seems that Windows handles USB more poorly than OSX. I used to run Windows XP on my old box and I had no end of USB troubles - certain midi controllers didn't like sharing the same bus, for example. Also, it's really annoying that Windows always needs to install the drivers every time you plug your device into another port! When I changed over to a Hackintosh, all my USB problems ceased even though it was the same hardware.

I used to own a MOTU MIDI interface that was rock solid - the problem was it was an ISA board that connected from the computer to the 1U unit. ISA is now state of the ark and isn't supported anywhere. I then moved to an Emagic MIDI interface that was USB. USB is supported but the drivers are no longer compatible with any modern operating system.

If it connects to a computer, one day it will be obsolete.

[Gatam]

I then moved to an Emagic MIDI interface that was USB. USB is supported but the drivers are no longer compatible with any modern operating system.

If it connects to a computer, one day it will be obsolete.

?
I have an Unitor 8 MkII (usb) pluged in my Macpro ealry 2009, rock solid !!
Drivers are class compliant in Mac os X since apple bought Emagic
And Unitor 8 control is still working

[auricle]

I then moved to an Emagic MIDI interface that was USB. USB is supported but the drivers are no longer compatible with any modern operating system.

If it connects to a computer, one day it will be obsolete.

?
I have an Unitor 8 MkII (usb) pluged in my Macpro ealry 2009, rock solid !!
Drivers are class compliant in Mac os X since apple bought Emagic
And Unitor 8 control is still working

I was talking about Windows, sorry