Missing Midi INs in Standalone

[Sabatini]

Hi @ll,

directly to the problem
Jupiter8 version 1.1.1
installed on i7, OSX 10.6.2 snow leopard

Midi Setup is
5 x Moto MidiExpress 128
this gives me alltogether  40 Midi I/Os !!

The Midi Input Menu of the Jupiter8 gives me
only a choice for
- all, or
- having the option of 8 ports (I/Os from 1 Interface only)

and.....
Exactly this interface has no Keys connected -
hmm poor.

Ok, when I set the input to "ALL", midi comes in and it works - we can say.
But - in a setup of this size - when you merge all 40! Midi ports to 1 input, - this brings often unexpected
results   
F.e. touching a rack or keyboard or desk, might make any devices to send "non grata" controller data from buttons, keys or front knobs. With so many devices, the risk is very high, if I can not filter the Input data.

I have observed the missing inputs in several Arturia Instruments.
The system itself is properly working.
All Native Instruments Synths, finding all my ports correctly in Standalone.

The other is, I tried to "update" to version 2.0. But the eLicenser gives me no chance.
whats new and better in V2 and why can I not update?  Extra fee? where? how much?

Who can help?

Kind regards
Toni

[tommym]

I'm not 100% sure, but I think your v.1.x license works for v.2, just download the app itself.
Is that right, Antoine?

PS. In my standalone MIDI setup (Macbook Pro SantaRosa OSX 10.6.2) I have to first uncheck all midi inputs, then close the window, then open it again and check them, then close the window and then I receive MIDI fine.

[Sabatini]

tommym wrote
I'm not 100% sure, but I think your v.1.x license works for v.2, just download the app itself.
Exactly what I did - no success
                                               
                                     eLicenser refused!!!!!

tommym wrote
In my standalone MIDI setup (Macbook Pro SantaRosa OSX 10.6.2) I have to first uncheck all midi inputs, then close the window, then open it again and check them, then close the window and then I receive MIDI fine.

I did not check this out - but such a workaround its not applicable for 40 Midi Ports !!!!!!!
oh hell
but many thanks for trying to help

[Sabatini]

and I forgot to say,
that I can not SEE this missing Midi ports, because the software does not offer all the physical existing Midi ports.
In the OSX audio and Midi devices - everything is fine, all ports there - Arturia software does not shoe me - but  - as I told, when I tag "all"
so the midi works - but all grap data from any of my serveral devices in the studio, coming from from 40 physical Midi ports
(be aware, that means 640 Midi Channels !!!!!)
are merged to the input of ONE Synthesizer! 

kind regards

Toni

[tommym]

Wow, that sucks, Toni. . . I hope the next update solves it.
640 Midi Channels - wow - with controller info,
that could be as much data as Audio or Video makes.
And imagine having to uncheck, and then re-check 640 boxes in a dialog, lol:
It would be simpler to go out and find a real Jupiter8 !
So compared to those, my problems with it are small.
Good luck!