cheers



unbelieverble indeed!okantah wrote:This SCOPE product !!! one can not believed it's a product from 1990's yet it's so functional & so powerful.unbelieverble
cheers![]()
![]()
Yeah, that would be really nice. We've mentioned that suggestion a few times now. OSC would be cool, but not as important as the USB midi device handling imo.ChampionSound wrote:Wouldn't it be handy if USB midi devices can be recognized in the project and selected from the I/O menu? Automation data can then be routed to any device in your project.
for USB MIDI, just use MIDIyoke to route the USB port into Scope MIDI modules.Shroomz~> wrote:Yeah, that would be really nice. We've mentioned that suggestion a few times now. OSC would be cool, but not as important as the USB midi device handling imo.ChampionSound wrote:Wouldn't it be handy if USB midi devices can be recognized in the project and selected from the I/O menu? Automation data can then be routed to any device in your project.
i agree, but it takes a bit of software(midi yoke) to communicate with the hardware(scope midi driver and usb midi driver).there's no way for Scope to be software inside the os when it's one of the hardware pieces, as i understand it.Shroomz~> wrote:I can already do it in midi/audio sequencers & can use something else like MIDIyoke as you suggest if I need to, but that slightly detracts from the beauty of Scope's midi routing capabilities. If I could boot my computer with Scope as I do & route a usb midi channel to anywhere I want without using an app other than Scope for that purpose, then I'd surely be better off. Scope doesn't need a separate software midi patchbay as it already performs this task. It just needs to support all of the installed midi devices on a system. Please don't take these comments as moaning or whining though because I'm a very happy Scoper & think we have something that's practically unbeatable.
That's not really correct Gary since Scope is hardware & software. In a sense neither would exist as we know it without the other. I can think of a few examples which suggest this is the case, but I won't go into them all. Basically, I don't think Scope would need to communicate directly with midi devices, but rather through the OS & that communication channel already seems to be open (Scope midi driver).garyb wrote:i agree, but it takes a bit of software(midi yoke) to communicate with the hardware(scope midi driver and usb midi driver).there's no way for Scope to be software inside the os when it's one of the hardware pieces, as i understand it.
Hence why people jumped all over me for requesting a USB driver module so many years ago.garyb wrote:i agree, but it takes a bit of software(midi yoke) to communicate with the hardware(scope midi driver and usb midi driver).there's no way for Scope to be software inside the os when it's one of the hardware pieces, as i understand it.Shroomz~> wrote:I can already do it in midi/audio sequencers & can use something else like MIDIyoke as you suggest if I need to, but that slightly detracts from the beauty of Scope's midi routing capabilities. If I could boot my computer with Scope as I do & route a usb midi channel to anywhere I want without using an app other than Scope for that purpose, then I'd surely be better off. Scope doesn't need a separate software midi patchbay as it already performs this task. It just needs to support all of the installed midi devices on a system. Please don't take these comments as moaning or whining though because I'm a very happy Scoper & think we have something that's practically unbeatable.
You're probably about 95% correct there.garyb wrote:no processing in Scope is done in the cpu's world,