Posted
I try to connect again the nano2 keyboard controller
I tested in Halion4 standalone ..it is working
I used console ( don't know yet what it is ) to get this error ...
How to solve this?
Window>> Console???
Mon, 2012-10-15 - 02:55 Permalink
It's very easy to create a midi loop especially if you are using a daw as well as synfire. Make sure the midi from the controller only routes to one place (eg sf) and make sure if it then routes to the other software( daw) via midi thru ( sf menu option) that doesn't route it back to synfire.
If you really are sending midi to your controller make sure it doesn't echo it back in thus creating a loop.
This used to happen a lot to me when synfire used virtual midi cables, and I'm used to routing midi via real cables to real synths!
Mon, 2012-10-15 - 08:25 Permalink
This console message is nothing to worry about. You can not send a direct midi-through signal back to an input port. It makes no sense anyway.
Janamdo, the tone of you posting is really not appropriate.
Mon, 2012-10-15 - 09:46 Permalink
Thanks!
On the MIDI tab on the Audio& MIdi Setup page there are 2 midi ports for the nanokey2 keyboard ..the "output only" has a option for Midi input what is ticked for "on" --> so this is the cause of the problem to get a Midi loop?
Thanks for the tip: SFE + DAW to get the right keyboard setup with MIDI thru.. now i can play the keyboard at hesame time SFE and Cubase..who knows how handy this will be? ( problem is now probably the sound.. i do need a multiclient driver..but Steinerg has a experimental asio multiclientdriver )
Mon, 2012-10-15 - 09:52 Permalink
The message is not an error message. It just says you can not send midi-through to the nanoKEY keyboard, because it is used for input.
Mon, 2012-10-15 - 15:01 Permalink
Still dealing with the nano2 key ..in Cubase it works ok , but in SFE?
I get it working( still without no sound ) when i go to the keyboard it shows the pressed keys ( no sounds )
When i go than to the arrangement view and than back to the keyboard in the progression window ..there is no input anymore
I installed the korg midi driver and the Korg control software ( it can that the keyboard internalsoftware must be updated too?)
I am starting to sing here: why oohh why ..during this search i stumbled on a open question and found a answer not related with the keyboard..that's good
--------------------------------------------------------------------
I cannot solve this this issue with the nano2 keyboardcontroller.. on HN2 it was working
mm .. i must make a reinstall with SE ..ofcourse i can do a test with another bigger keyboardcontroller..when this in normal working it has something to do with the nanokeyboard.
Mon, 2012-10-15 - 15:31 Permalink
You dont need to reinstall Synfire.
Do you have both engines on? Try working with a single engine only at a time. Or disable "User Engine for MIDI Input" switch in Audio & MIDI Setup.
KORG nanoKEY works fine here on Windows 7 x64.
Mon, 2012-10-15 - 18:13 Permalink
Thanks,
I do use KORG nanokey 2 ....i will try this
I am now focussed on the 64 bit engine...
(sidequesion : i am using i think a 32 bit Halion4 Vst i plugin in the 64 bit audioengine ..is this possible ?..it seems to be working)
-------------------------------------------------------------------
Now in the 64 bit configuration..there is only a Midi output..there is no Midi input anymore !
The KORG USB mididriver configuaration : shows that i use the korg usb-midi driver for windows[x64 Edition]
Midi in: 64 bit only
Ok let me go to the KORG kontrol editor --> preferences ..MIDI in = nanOKEY2 KEYBOARD (not connected)
This must be connected.. not possible with manually ..so the kontrol editor cannot set the midi in for the nano2 keyboard..what causes this?
THERE IS NO MIDI PORT FOR INPUT ON THE PORT LIST : can SFE handle 64 bit midi drivers ?
------------------------------------------------------------------------
Ok, i able the 32 bit driver for Korg and 32 bit engine and there is now a midi port again back.
Let me now disble the32 bit engine ...what happens than?
Ok now i use a 64 bit engine and a 32 bit midi port driver from Korg (whil ethere is a 64 bit version, but using thi s driver alone with th e64 bit engine gives no midi in port.
It seems that the 64 bit engine uses a 32 bit VSti Halion4( this i am not sure of) and a 32 bit korg Midi driver ( this is for sure)
----------------------------------------------------------
I can play on the nanokeyboard , and playing on the keys in FE..but no sound ( mouseclicking gives a sound )
So how to solve this ??
Stay in the 32 bit mode ?
=================================
SOLVED!!!! it seems..stupid crap of a cable : i use a usb hub with a long cable ( it must enforce the signal ) and use now the default cable for the hub aqnd now is the signal seems to be strong enough..that i can play on the nano2 keyboard
I use now a 32 bit driver and a 32 bit vsti probably on a 64 bit engine
Woow, i went again thrue the internals of SFE...haha
-------------------
No !.. i changed the long usb cable back and than removed it and get a default cable back for the usb hub
I remember me know that the usb hub is powered ..so it must be probably working even with the long ( signal enforced cable), but now it works again not even with the default usb hub cable ?
So again the nano2 keyboard is playing the keyboard in SFE, but no sound
SFE becomes chaotic as it seems :) ..right now i don't know it anymore
Wait , i make a restart with the short default hub cable and SFE..let see what happens than ?
--------------------------------------------------------------------------
The long USB cable i snow working again with SFE .. ( "get now a breast" as we say here )
Mon, 2012-10-15 - 18:25 Permalink
Hey janamdo if you are still having trouble with getting sound out of your vst when playing your midi keyboard.. Check
You get the midi input light flashing when you press keys
If not something is failing with the midi port or driver
Assuming the light flashes when you press keys, can you get sound when you play the virtual keyboard with the mouse and a sound setup ( you said yes to this )
Make sure midi through is enabled in the synfire menus
If you still can't get any sound, maybe look at channel assignments, maybe the midi keyboard is sending on a different midi channel and although synfire is seeing midi traffic, maybe your vst in synfire is set to a different channel?
Hope you get this all sorted soon, with this level of frustration, you are going to compose some pretty aggressive tunes and I can't wait to hear them ;)
Mon, 2012-10-15 - 19:14 Permalink
Can you please make your setup with 32 bit first and only after that worked, try running 64 bit?
Mon, 2012-10-15 - 20:18 Permalink
You are right, the tone of my posting is really not appropriate..i removed this post
I must try to be reasonable..in the past i hammer with my fist on my computer sometimes, when i working for a long time on a issues and it doesn't work at the end ..not handy :-)
But better is to go to the gym or other things for relaxation: music !
Let's go back to this issue..of getting the keyboard working
Mon, 2012-10-15 - 20:26 Permalink
It is now working for 64 bit the nano2 keyboard
Yes the 64 bit engine is now only there and there is a Halion4 Vsti
Can you please make your setup with 32 bit first and only after that worked, try running 64 bit?
Problem is Halion4 i cannot determine if there are two version of it exists a 32 and 64
Mon, 2012-10-15 - 20:34 Permalink
Thanks!,
Hope you get this all sorted soon,
Yeah, there can be lot of setup conditions going wrong, but the nano2keyboard is now working for a 64 bit engine
and it uses 32 bit Vsti and a 32 bit midi driver ?
The Halion 4 manual is not clear about the versions for the Vsti ( 32 or 64 bit ?)