NEKTAR configuration

[jacekk]

How should be configure SCOPE to use Nektar Impact LX61? I have Scope 5.1 Win7 32bit. Nektar have only USB but in Win lacking drivers to Nektar. Scope don't receive any MIDI message on Pulsar MIDI source device.

When I use Presonus Studio One 2 Nektar communicate with Studio One by External Dev > Impact LX61 Control ["receive from MIDIIN2 (IMPACT LX61)"] but keyboard not work.

[sunmachine]

SCOPE doesn't see the external MIDI ports, so you have to route the MIDI data somehow to a SCOPE Sequencer MIDI Source device. This can either be done with a DAW like Studio One or any other software that has MIDI routing capabilities (like CopperLan for example).

I don't have a Nectar Impact but basically it works like this:
1. SCOPE: Add at least one Sequencer MIDI Source Device to your SCOPE project. You might have to restart Studio One after that, so that it can see the new virtual SCOPE MIDI port.
Connect a synth to the MIDI source device.
2. Studio One: Add a New Instrument and select the SCOPE MIDI port as output (send to).
3. Studio One: Add a New Keyboard and select the appropriate MIDI port from your Nectar Impact as Input (receive from).
4. Studio One: Add an Instrument Track and select the Keyboard device (3.) as Input and the Instrument device (2.) as Output in the track header. Turn on the monitoring (also in the track header).
Now you should be able to play the SCOPE synth with the Nectar keyboard.

Hope this helps! Maybe the ScopeRise Studio One article is also helpful (http://www.hitfoundry.com/issue_23/one_mast.htm)
Let us know if you got it working.

[jhulk]

you can use midi-ox or bidule todo this you set the incoming midi to go to the scope internal midi

[jacekk]

Thank You very much! I tested both methods. Connecting Nektar by Studio One (Presonus) is ok but to playing on keybords is needed a lot actions and complicated configurations of these programs.
Midi-ox have a big latency ca 0,8 sec with MidiMapper. I don't make connecting Nektar with Sample Player (Scope) but this solution seems strange, I havn't trust (drops, mapping, routing midi in WIN and next program).

It is very strange situation - SCOPE DSP Audio Platform without basic drivers USB-MIDI devices - without possibility working with a new technology as USB MIDI. It is really so hard to implementation to SCOPE (as device USB to MIDI)?

[garyb]

the usb device connects to windows via a DRIVER.
Scope connects via a DRIVER.

a driver connects the hardware to software.
a driver will NOT connect hardware to hardware.
software is required to bridge the gap between two pieces of hardware. this is how computers work.

if you need 0 latency midi, connect directly to the Scope card's midi i/o.
midi from any hardware to a sequencer(for playing vstis or the like) will always have at least the ASIO latency.

[jacekk]

Now I understand - Scope DSP Platform supports only own hardware sockets (audio, midi, digital). USB socket is supported by Windows (PC machine). Now we must connect MIDI USB to MIDI Source (Scope) use DAW for example Studio One. It is possible with latency ASIO but I can't configure it. Nektar send control message but not note (keyboard don't send messages). Unfortunately I dont use daily Studio One (my knowledge is poor, I am older user of Cubase) and I have trouble with configuration Studio One to use Scope.

I resolve problem simply by changng masterkeyboard to other with true MIDI OUT socket, then I will use Sample players Scope without neccesity use of external programs and others difficult actions.

If I understand correctly, Scope can't (and will not) support USB MIDI and this solution is unpossible.

[garyb]

yes, impossible unless you use software(a sequencer, midi-ox, copperlan)to connect the two pieces of hardware.

[jacekk]

Friends - thank You very much!

[jksuperstar]

Also possible if you use an iConnect midi hardware router. It is a MIDI router that operates with a computer, or stand alone, and supports USB MIDI devices also! (no need for computer to go USB->MIDI)

[sunmachine]

According to the Nektar web site, the Impact XL is class compliant. So it should work with the iConnectMIDI4+ even if it's not connected to a computer (the standalone mode mentioned by jksuperstar). That is, you'd connect the Impact to the iConnectMIDI4+ via USB and SCOPE via MIDI to it and could then play SCOPE devices with the Impact keyboard. This should actually work right out of the box because the default routing is set up that way, that the USB inputs are routed to the MIDI DIN outputs.

This simple direct routing won't work with the smaller iConnectMIDI2, though, since it doesn't have a USB Hub. So a setup with the iConnectMIDI2 would be similar to a software routing solution like CopperLan or the like (both the Nektar and the iConnectMIDI2 would be connected to the computer).

[dante]

if you need 0 latency midi, connect directly to the Scope card's midi i/o. midi from any hardware to a sequencer(for playing vstis or the like) will always have at least the ASIO latency.

If fact this is what I now do. After years of using MIDEX over USB, I now have master keyboard plugged into XITE-1D MIDI IN. I then connect that to MIDI Sequencer Dest to redirect to Cubase / Reason etc. Or a Scope XITE or PCI synth.

[HUROLURA]

I do the same actually, but as I want to be able to have several MIDI gears available as an input for the Scope hardware MIDI IN there is an old good magic AMT8 in between to route the MIDI signal.

Actually, I want to be able to use not only the keyboards, but also different controllers (woodwind, guitar, drum pads) and a bunch of hardware control element (encoders, potis and switches).
And with such a setup I can provide all this MIDI flow to several Scope systems and hardware synths ...

[Bud Weiser]

If fact this is what I now do. After years of using MIDEX over USB, I now have master keyboard plugged into XITE-1D MIDI IN. I then connect that to MIDI Sequencer Dest to redirect to Cubase / Reason etc. Or a Scope XITE or PCI synth.

It´s an advantage to have a masterkeyboard offering physical MIDI and USB.

I go w/ physical MIDI directly into XITE-1 and w/ USB into the Hi-Speed USB hub connected to the computer mobo.
Works w/ Kurzweil PC3 as well as Edirol PCR300 or both when using the PCR300 MIDI merge function.
In addition I have a 8x8 MIDI interface connected to the parallel port which I fortunately still have on my machines.
That´s a 32Bit solution though.
With 64Bit I´d have to use my MIDEX-8 too or going Copperlan.

Bud

[dawman]

You don't mean like the awesome Physis K4 do ya'...?

http://www.viscountinstruments.it/physis-piano-k4.html

[dante]

I think most controller keys now have USB midi as well as old skool MIDI - at least the ones in Buds article
http://www.hitfoundry.com/issue_24/key_mast.htm

Physis, KAWAI MP7 & VPC-1, Kurzweil Forte, CASIO PX-5S, Studiologic NUMA Concert.....not sure which of these merge IN to OUT though

[Bud Weiser]

I think most controller keys now have USB midi as well as old skool MIDI - at least the ones in Buds article
http://www.hitfoundry.com/issue_24/key_mast.htm

Physis, KAWAI MP7 & VPC-1, Kurzweil Forte, CASIO PX-5S, Studiologic NUMA Concert.....not sure which of these merge IN to OUT though

Well,- yes, but they aren´t the same ...

Each one being interested should investigate himself before buying something.
Some USB MIDI only carries the same MIDI channels as the physical MIDI does, others work independent in the way the physical MIDI is MIDI Channel 1-16 and the USB is 4 virtual ports = 4x 16 MIDI channels!

MIDI Merge is also a matter of definition.
P.ex., when Edirol added a "merge" switch to the physical MIDI I/O and USB configuration and "In" is been routed to the "Out",- in old MIDI language that means "MIDI Echo" in reality.
Normally, "MIDI Merge" is 2 MIDI Inputs being merged together to one MIDI Out stream.
The merge functionality might come alive when using USB and physical MIDI together though, depending on MIDI driver functionality.

So, the Physis Piano K4 DAWMAN mentioned above, is a real "merging" (as also re-channelizing) keyboard, offering 2 independent MIDI Ins and several (8) MIDI Outs as well as 4 independent USB MIDI busses.
You cannot expect this from the piano controllers and digital pianos per sé, but some might offer a fraction of these features while others are I/O & thru and USB MIDI I/O w/ 16 MIDI channels only, like my Kurzweil is.

Bud

[dawman]

Worth mentioning is that MIDI Channel 2 handles all internal sounds, but if you choose to avoid their Sounds, this channel can then become what ever the performer wants.
In my case the PianoTeq Pro 5 D4 for Chopin/Debussy covers, the U4 for realistic Uprights, the 200A for Wurlitzer sounds, then Kontakt for my FS1R and Neo Soul Rhodes stuff.

My search was over the day I read the manual.
No more MIDI Solutions Filters, Pedal controllers, Merge boxes, Routers, no more BCF 2000, no QuNexus and farewell to the Casio PX-3S.

Actually glad that Casio made the PX-5 so unattractive with the Orca The Whale paint job, or I would have bought one of those.
This was worth the wait.

[dante]

Have you got it already then - the Physis ?

[Bud Weiser]

Worth mentioning is that MIDI Channel 2 handles all internal sounds, but if you choose to avoid their Sounds, this channel can then become what ever the performer wants.

Which is only valid when buying the EX version,- did you ?

Actually glad that Casio made the PX-5 so unattractive with the Orca The Whale paint job, or I would have bought one of those.

Hmmm,- the blue of the K4 isn´t any better I fear,- it´s much lighter blue than I expected,- more the PPG WAVE 2 front panel blue ...

This was worth the wait.

I hope so, you´re the guinea pig here,- let´s read your reports soon please.

Otherwise,- winter NAMM is near ...
Maybe CASIO learned and come up w/ a PX5SmkII offering expression pedal inputs and black finish,- who knows ?

Bud

[dante]

Maybe JB should make a Solaris in a rack module version ( w/ external ribbon cont thrown in ) with brushed metal black finish. Might be easier than adding triple sensor weighted keys, inbuilt 8x8 MIDI Hub, independent USB, sliders and stubby holder to the keyboard version ...