Hi,
I can't see the scope midi hardware i/o in protools tdm.
I have a mix 24 card and a scope card in a pc.
In protools I can't see the hardware midi i/o.
Anyone know why?
regards,
James
hardware midi i/o
-
nightscope
- Posts: 686
- Joined: Tue Aug 21, 2007 4:24 pm
- Location: UK
Re: hardware midi i/o
Scope MIDI[hardware] Source & Destination do not show up in any host as I/O's but are available in the Scope project; if you put them in one.tripstation wrote:I can't see the scope midi hardware i/o in protools tdm.
Sequencer MIDI source and destination modules transfer MIDI between Scope project and host. They do show up in a host. The number that are available will depend on how many Scope MIDI drivers have been activated.
ns
“Women and rhythm-section first!”
-
nightscope
- Posts: 686
- Joined: Tue Aug 21, 2007 4:24 pm
- Location: UK
Re: hardware midi i/o
PS Don't know about XTC.nightscope wrote:Scope MIDI[hardware] Source & Destination do not show up in any host as I/O's but are available in the Scope project; if you put them in one.tripstation wrote:I can't see the scope midi hardware i/o in protools tdm.
Sequencer MIDI source and destination modules transfer MIDI between Scope project and host. They do show up in a host. The number that are available will depend on how many Scope MIDI drivers have been activated.
ns
“Women and rhythm-section first!”
-
tripstation
- Posts: 176
- Joined: Tue Oct 12, 2004 4:00 pm
Re: hardware midi i/o
Hi,
I used to have this sussed.
Havn't done it for a while, can't remember how it works.
So If I connect to a sequencer o/op from say protools, do I also have to connect this to a hardware i/p in scope and physically connect the cables, or can I do this with software routing.
I used to have this sussed.
Havn't done it for a while, can't remember how it works.
So If I connect to a sequencer o/op from say protools, do I also have to connect this to a hardware i/p in scope and physically connect the cables, or can I do this with software routing.
Re: hardware midi i/o
hi,
And there is a setting in scope driver for how many sequencer midi port the scope declare to the OS.
cheers
And there is a setting in scope driver for how many sequencer midi port the scope declare to the OS.
cheers
-
tripstation
- Posts: 176
- Joined: Tue Oct 12, 2004 4:00 pm
Re: hardware midi i/o
What about the Scope MIDI A Source in the sfp project.
Isn't this a hardware midi port.
If so, Should I not see this in protools?
Isn't this a hardware midi port.
If so, Should I not see this in protools?
Re: hardware midi i/o
Hi,
No, You need to add a sequencer midi dest (from the Software IO ) and connect it to your midi A source.
cheers
No, You need to add a sequencer midi dest (from the Software IO ) and connect it to your midi A source.
cheers
-
tripstation
- Posts: 176
- Joined: Tue Oct 12, 2004 4:00 pm
Re: hardware midi i/o
Do I have to have sfp running to use the hardware midi i/o, say just as a midi interface?
How does this work?
How does this work?
Re: hardware midi i/o
Hi,
Yes, if you don't use XTC
2 cases:
- You use XTC, and you do your wiring in xtcproject.pro
- you use SFP, and you do your wiring in your project. You launch SFP with this project when you use your sequencer.
Basically it seems there is something you do not have grasped yet:
What you see in the SFP project window is "Inside" your DSP boards and is unknown to your PC. Your interface with the PC are:
- ASIO In/Out devices for audio
- sequencer midi in / outs devies for midi
Your Physical interfaces (plugs on your cable ) are adressed with the Physical IO devices (scop midi in out, adats, spdif,..
that need to be loaded in your projet in order for the DSP, to know what it need to use.
The project window describe the connections (routing) between what is available to the PC and which physical connectors are used.
You should read the manual to clarify this.
cheers
Yes, if you don't use XTC
2 cases:
- You use XTC, and you do your wiring in xtcproject.pro
- you use SFP, and you do your wiring in your project. You launch SFP with this project when you use your sequencer.
Basically it seems there is something you do not have grasped yet:
What you see in the SFP project window is "Inside" your DSP boards and is unknown to your PC. Your interface with the PC are:
- ASIO In/Out devices for audio
- sequencer midi in / outs devies for midi
Your Physical interfaces (plugs on your cable ) are adressed with the Physical IO devices (scop midi in out, adats, spdif,..
that need to be loaded in your projet in order for the DSP, to know what it need to use.
The project window describe the connections (routing) between what is available to the PC and which physical connectors are used.
You should read the manual to clarify this.
cheers
-
tripstation
- Posts: 176
- Joined: Tue Oct 12, 2004 4:00 pm
Re: hardware midi i/o
Ok.
I seem to have this working with ProTools now.
This is a fantastic setup.
I have a totally silent PC running all the audio with DSP's.
Pro Tools mix card, scope 15dDSP and a powercore.
I'm running this on a 2gig p4 (this doesn't need much cooling and has a fanless psu) this thing is so quiet ( can't even hear over my ADAT bridges) great for doing vocals.
The traffic is quite a pain though.
Thing is, when I select a second midi in/out 2 in pro tools, and add a second midi sequencer source in sfp, I get no midi into sfp on the second i/o.
I seem to have this working with ProTools now.
This is a fantastic setup.
I have a totally silent PC running all the audio with DSP's.
Pro Tools mix card, scope 15dDSP and a powercore.
I'm running this on a 2gig p4 (this doesn't need much cooling and has a fanless psu) this thing is so quiet ( can't even hear over my ADAT bridges) great for doing vocals.
The traffic is quite a pain though.
Thing is, when I select a second midi in/out 2 in pro tools, and add a second midi sequencer source in sfp, I get no midi into sfp on the second i/o.
Re: hardware midi i/o
There's an i/o configuration tool for Scope that can help with these settings, or you can do it manually:
In your control panel, "Sounds and Audio Devices", go to the "Hardware" tab, under devices select your primary Scope/Pulsar card and choose properties at the bottom of the panel.
In the properties panel that opens, go to the "Settings" tab and specify the number of Wav & Midi devices you want (wav inputs & outputs are specified separately, a single setting for midi controls the number of both in & out). Ignore the 'preferred bit depth' part under wav, that's a legacy setting which is now controlled by the wav module you load into Scope.
----------
Also note the "Powermanagement" Section at bottom for later, don't mess with it now. Users who experience lockups when the machine is idle for a while (especially under non-ACPI systems where power management isn't functioning 100%) might need to uncheck "Reset board if idle" but I only mention this for others reading, I do NOT suggest changing this for your midi driver issues only if you find you're having problems when Scope is left open overnight on a system where the ACPI kernel has been replaced by "Standard PC" or "MPS Multiprocessor PC" and APM drivers weren't installed correctly.
In your control panel, "Sounds and Audio Devices", go to the "Hardware" tab, under devices select your primary Scope/Pulsar card and choose properties at the bottom of the panel.
In the properties panel that opens, go to the "Settings" tab and specify the number of Wav & Midi devices you want (wav inputs & outputs are specified separately, a single setting for midi controls the number of both in & out). Ignore the 'preferred bit depth' part under wav, that's a legacy setting which is now controlled by the wav module you load into Scope.
----------
Also note the "Powermanagement" Section at bottom for later, don't mess with it now. Users who experience lockups when the machine is idle for a while (especially under non-ACPI systems where power management isn't functioning 100%) might need to uncheck "Reset board if idle" but I only mention this for others reading, I do NOT suggest changing this for your midi driver issues only if you find you're having problems when Scope is left open overnight on a system where the ACPI kernel has been replaced by "Standard PC" or "MPS Multiprocessor PC" and APM drivers weren't installed correctly.