Re: [Jack-Devel] Installers for Jack 1.9.8 (SVN 4340) for Windows 64 and 32 bits

How Strange ! and what a coincidence !

I just got this Yamaha organ three days ago.
It only works as a VSTi with my Reaper and VSTHost.
As stand alone..... no. I get the message "runtime was requested this .... to terminate in an unusual way ect...". Why is that?

Graham's command -X winmme worked ok.
I saw system_midi on the left (out) and system_midi on the right (in)
Connected them and latency was terrible.... (GrandOrgue v.1)

If not connected I cannot play with my Keyboard anything.
So I deleted this command and returned to my previous status.
All these with my 32bit lap, so far. and Jack 1.9.8 4340.

I tried this, later, without midi from Jack :
Mother88 with Romio II usb/midi
Jack Portaudio opened OK
NI B4MkII : Audio : jackrouter, Midi : Romio II
Piannissimo : Audio : Jackrouter, Midi : Romio II

Mother88 played only B4. with the mouse I got sound from both.
Set Midi out at B4 to MidiYoke 1
Set Midi in at Piannissimo from MidiYoke 1.
No work.

My simple aim is to play from my Mother both piano and organ at desktop as standalones. This is possible (with Asio) only when these two are VSTinstruments in Reaper.

best
Panos

--- Στις Παρ., 22/04/11, ο/η Stéphane Letz <[hidden]> έγραψε:

Από: Stéphane Letz <[hidden]>
Θέμα: Re: [Jack-Devel] Installers for Jack 1.9.8 (SVN 4340) for Windows 64 and 32 bits
Προς: "Panos Ghekas" <[hidden]>
Κοιν.: "Graham Goode" <[hidden]>, "Devin Anderson" <[hidden]>, [hidden]
Ημερομηνία: Παρασκευή, 22 Απρίλιος 2011, 16:22

To be clear, using WinMME JACK MIDI bridge does make sense only when a user wants to inject MIDI messages from WinMME world inside JACK MIDI or the contrary, so basically with *native* JACK clients.

Like for instance Sampo Foo yC20

http://code.google.com/p/foo-yc20/

Stéphane


Le 22 avr. 2011 à 17:11, Panos Ghekas a écrit :

> 
> Thank you Graham and Devin !
> 
> I 'll see what I can do.
> So far I never experienced problems with audio Jack on windows7. 
> Everything after installation and target properties for Asio4all, went ok.
> 
> I never had to use the midi function with Jack Control, as I used Jack (1.9.4 was the first) to get VST reverb for Grand Orgue program, which I controlled from my EL900 organ console. This Yamaha organ sends 3 midi channels merged from its midi output, upper ch1 or 4, lower ch2 or 5, pedal ch3.
> 
> So, when I tried other virtual instruments together, example a Mellotron on ch2, an ARP Odyssey on ch1 and a Moog Taurus on ch3, all played ok from EL900 (audio connections were made with Jack Control, all three to Lexicon PCM Savihosted).
> So, I didn't bother with midi on Jack.
> 
> Later I tried my other keyboards to control these examples, and couldn't. I mean only my first connected 88mother kbd could control anyone but one at at time, Motif ES was in too, but this too could one at a time. Straight as they were inserted in my laptop. 
> Usually I make virtual midi connections with MidiYoke on 32 bit and LoopMidi for both 32 & 64. LoopBe1 is ok but has only one port, so I just left it there stayin'..
> 
> I follow very simple connections, just to be able to play quick.
> Like : Motif ES6 has direct USB out to laptop where Asio4All is installed.
> Open Jack with doubleclick on Jack Portaudio icon. Open stand alone virtual instrument where I preset Midi in from ES - 1 and audio to jackrouter. The same with the stand alone effects.
> 
> For older 88mother and EL900 there's the EST Romio II Midi to USB adapter, which works well.
> 
> Now as I understand Midi on Jack I have to define connections with the patch bay in Jack Control in order to work with Midi, no?
> Like get all 3 synths in my example to be controlled by two or three keyboards ?
> 
> It may look naive as I describe, but keep in mind that I'm a musician and not a programmer and I don't speak native English, so computer terminology has a lot of difficulties from Greek to English. Also my laps here speak 70% Greek and the rest in English.... so you see...
> 
> Devin, thank you for all your efforts and all devs here, I'm extremely happy to help with tests :-)
> 
> Graham, this command has to be added on Jack Portaudio>Properties>Target after the command for ASIO4All v2 ?
> Or on Jack Control> Properties>Target ?
> 
> Best
> Panos
> 
> --- Στις Παρ., 22/04/11, ο/η Graham Goode <[hidden]> έγραψε:
> 
> Από: Graham Goode <[hidden]>
> Θέμα: Re: [Jack-Devel] Installers for Jack 1.9.8 (SVN 4340) for Windows 64 and 32 bits
> Προς: "Devin Anderson" <[hidden]>
> Κοιν.: "Panos Ghekas" <[hidden]>, "Stéphane Letz <[hidden]>Peter L Jones" <[hidden]>, [hidden]
> Ημερομηνία: Παρασκευή, 22 Απρίλιος 2011, 6:27
> 
> Hi Panos,
> 
> To set Jack up to use the new MIDI driver you need to add this to your
> command line (target) property: -X winmme, so the command should start
> like this...
> 
> jackd.exe -R -S -X winmme -d portaudio
> 
> I hope to get time this weekend to do some testing with this too
> 
> Kind regards,
> GrahamG
> 
> On 4/22/11, Devin Anderson <[hidden]> wrote:
> > Hi Panos,
> >
> > On Thu, Apr 21, 2011 at 4:03 PM, Panos Ghekas <[hidden]> wrote:
> >
> >> I'm now about to test the midi functions, hmm here maybe I'll need sone
> >> assistance, I'm afraid...
> >
> > I'm not too familiar with Windows, but I'll tell you what I can:
> >
> > 1.) Start `jackd`.
> >
> > 2.) Connect a MIDI cable from one of the outputs on your MIDI
> > interface to one of the inputs on your MIDI interface.
> >
> > 3.) Start `jack_midi_latency_test` at the command line.  If you know
> > the names of the ports you want to connect, then you can start it
> > using:
> >
> >     jack_midi_latency_test [out-port-name] [in-port-name]
> >
> > (On Windows, this may require an .exe extension.  Or, maybe not.  I'm not
> > sure.)
> >
> > Otherwise, you can start `jack_midi_latency_test` with no arguments
> > and connect the input and output ports you intend to use using a GUI
> > JACK client.
> >
> > 4.) Once you get a valid test, do the following:
> >
> >     jack_midi_latency_test -m 3 -s 8192 -t 5 [out-port-name] [in-port-name]
> >
> > This may take a little while, depending on the settings you use to start
> > JACK.
> >
> > 5.) Once the test is finished, send back the output, along with the
> > name of the device you used.
> >
> > The results I've received so far from Windows users haven't been very
> > good.  Don't be surprised if there's a little more jitter than you'd
> > normally expect.
> >
> > Thank you for your help! :)
> >
> > --
> > Devin Anderson
> > devin (at) charityfinders (dot) com
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

1303493433.19949_0.ltw:2,a <145864.13312.qm at web29104 dot mail dot ird dot yahoo dot com>