Posted
The law of Murphy is working again here..haha
Windows 7 pro 64 bit is now frozen( it is a chrash ) every when i start Synfire Express
It keeps this state , i start 3 times with SFE with result: a frozen operatingsytem.
I chanced the audiodriver for the 64 bit node , when i hear no sound when i try to fix the keyboard get to work
Than starts this misconfiguration..
------------------------------
How to get out of this ?
- windows safe mode
- reinstall SFE
Mo., 15.10.2012 - 10:58 Permalink
It's the new audio driver that crashes Windows, not Synfire.
Safe mode would probably help to uninstall the driver again.
Mo., 15.10.2012 - 11:29 Permalink
The 64 bit driver. You said you changed the driver for 64 bit engine. That driver is causing the lockup.
Try starting the 64 bit engine standalone (find in program files directory) and switch back to the previous driver.
It is unlikely that you will be able to use both 32 and 64 bit engines at the same time with ASIO. Windows does not like that.
Mo., 15.10.2012 - 12:24 Permalink
I did nothing to fix this.. but SFE works again
See enclosed pic of the soundassigning of the two engines--> they should not be conflicting the 2 asio audiodrivers when i saw this ..and indeed SFE starts normal up
Ok, good to know that the Asio driver works only for one engine and not for both ..if this is 100 % for sure than perhaps a error mesage for the user should be handy
I don't know if there other combinations of audio drivers are possible ?.. 8?
Mo., 15.10.2012 - 12:35 Permalink
Multiple ASIO clients may or may not work, so a general error message would be no good idea. Maybe a warning only. We hope better ASIO drivers will be released some day.
On the Mac, using any number of programs sending to the same audio hardware at the same time is not a problem.
Mo., 15.10.2012 - 18:40 Permalink
Multiple ASIO clients may or may not work, so a general error message would be no good idea. Maybe a warning only. We hope better ASIO drivers will be released some day.
Hmmm ... I thought this was a software issue? I believe Sonar and a few other DAWs specifically permit multiple audio drivers, ASIO or not, whereas Cubase and most others are only able to access one at a time.
I don't know if Jan had another app open, such as his DAW, loaded with a different driver than SFE or not, but this might cause a problem.
I am not saying that the problem lies with SFP/ SFE. If you say "may or may not work," it implies that there are known instances of SFP/ SFE working in a multiple driver setup. Is this what you mean?
I am quite sure that you cannot run any audio driver incompatible with the bits of your OS in Windows. 32 bit OS (Win XP) requires 32 bit drivers and 64 bit OS require 64 bit drivers.
Prado
Mo., 15.10.2012 - 19:08 Permalink
Well, "may or may not work" means that it depends on the driver software that comes with your audio interface hardware, or DAW, or whatever you currently have installed. Unlike Mac OS X, the audio driver layer of Windows is not an integrated part of the operating system, so every vendor is brewing their own soup. At least this is for ASIO stuff. The newer Windows Audio layers may be more flexible, but also come with more latency.
Mo., 15.10.2012 - 21:41 Permalink
I'm not sure this is quite accurate. I had a Sonar install and could use multiple ASIO driversat the same time for different audio hardware that had ASIO drivers, but, with the same OS and things installed, on Cubase I could only use one ASIO driver at a time, whether from the hardware manufacturer, RME and Echo, or software like ASIO4All.
That's why I thiink it is a function of the hosting software.
It is not an issue for me any longer, as I have a 40 channel RME I/0 setup. But it sounds as though you cannot confirm at this time whether SFP/ SFE will work under Windows with a multi-ASIO hosting DAW like Sonar.
Some customers might want to know.
Prado
Mo., 15.10.2012 - 21:52 Permalink
Regarding audio output, the Engine of Synfire works exactly like any other DAW. It does nothing special.
Therefore, if you can run multiple DAW in parallel playing to the same ASIO driver on your Windows 7 installation, then Synfire will also be able to do so.
We can however not test all possible driver combinations in advance. There are too many out there. If users report issues with certain installations, we note that down for future support requests.
Di., 16.10.2012 - 00:34 Permalink
It's all based on the O/S. If you have a 64 bit O/S then you can run a DAW either 32 bit or 64 bit. A 32 bit DAW can only host a 32 bit plug in.
If you are running a 64 bit DAW, with proper bridging is should be able to run a 32 bit VSTi synth, as well as, obviously, a 64 bit VSTi.
If you are able, you should run everything 64 bit. This will increase your processing speed and increase the RAM memory your programs can use. A VSTi sampler, like Halion, will run much better if it mostly runs from RAM. The more RAM, the more instruments you can have loaded and immediately working without glitches.
Prado
Di., 16.10.2012 - 00:38 Permalink
Regarding audio output, the Engine of Synfire works exactly like any other DAW. It does nothing special.
Therefore, if you can run multiple DAW in parallel playing to the same ASIO driver on your Windows 7 installation, then Synfire will also be able to do so.
I see my point is not clear. I am talking about the opposite. One DAW simultaneously addressing multiple audio devices. This is entirely about something 'special' done by the DAW. I know Sonar does this and possibly a few others. Most DAWs do not.
This becomes a concern when people have multiple hardware audio interfaces and would like to use them together, most typically to increase I/O.
Prado
Di., 16.10.2012 - 09:26 Permalink
Cubase does have a Asio Muli Server ( not official ) , you can get this on their site
I am still faces a not working keyboardcontroller with the both audio engines in SFE
Took me the whole day yesterday and it is still not working yet .. how about frustration..haha ..crap windows is responsible for this audio trouble regarding the nanokey2 keyboardcontroller.
How to go further? ..it seems that i got it working with a 64 bit engine and a 32 bit usb korg midid driver ?
Di., 16.10.2012 - 09:49 Permalink
This becomes a concern when people have multiple hardware audio interfaces and would like to use them together, most typically to increase I/O.
Ok I see. That is a nice problem to have, though. You rarely would need that for prototyping and composition, because you are not recording audio. The other way around, addressing a single ASIO hardware from multiple DAWs at the same time (joining audio output), is a show stopper, because it prevents running the Engine together with a synched DAW. This is no problem on the Mac.
it seems that i got it working with a 64 bit engine and a 32 bit usb korg midid driver
Install all drivers you can get for the nanoKEY: 32 and 64 bit, so both engines can see it.
Di., 16.10.2012 - 10:07 Permalink
You only see the output CTRL port of nanoKEY. The KEYBOARD input port is not listed.
Does some other DAW perhaps block it? Although it should not be possible. Multiple programs should be able to listen to the same MIDI input at the same time.
I will get my hands on a WIndows 7 machine this afternoon and test with the nanoKEY.
P.S: Please also check what happens when you shut down both engines (use Host menu) and press RESET button on Audio & MIDI Setup.
Di., 16.10.2012 - 10:08 Permalink
Yes, i nstalled both drivers..
I studied the korg nano2 manual ..see 2 pic
For window Vista/7 Midi OUT = nanoKEY2 ..the same for the input
The port list in SFE shows a nanoKEY2 1CTRL output
------------------------------------------
Assume that both KORG USB 32/64 bit drivers are ok, than has it something to do with the internals of SFE ?
Di., 16.10.2012 - 11:03 Permalink
P.S: Please also check what happens when you shut down both engines (use Host menu) and press RESET button on Audio & MIDI Setup.
Nothing to see
I cannot see if there is a 32 bit or 64 Korg Midi USB driver is involved in the driverlist for ports ?
I noticed for 32 bit engine there is a midi input driver and not for 64 bit engine.
The driverlist for the ports make no difference in 32 or 64 bit --> looks to me handy..if i can see what bit driver is involved ?
Example: when i click on the node 1 engine it shows the 32 bit drivers only and the same for 64 bit -
Well i am waiting for tests : i use a nano2 keyboardcontroller ..the newest one
---------------------------------------------------------------------------
I face another problem here to and that is about saving, because i try to get working the nano2 controller and somehow the setup must be stored
What i do is load the 64 engine assign a shared rack for the Halion4 ( a GM setup) and assign the midi port..than it should working
Question: if i save the arrangement now..all made setupconfiguration will be stored ?
Can not imagine in what case i should use --save & rack&setup and the same for.. all devices if i use save arrangement >
----------------------------------
- saving a arrangement
- save rack$setup
- save all devices
-----------------------------------
For the moment there is nothing else i can do more : my musical future lays in the hands of the Cognitones
Its over ...
Di., 16.10.2012 - 12:31 Permalink
The user manual of nanoKEY states that it can not be used with multiple applications at the same time, unless you install the KORG drivers. If you did so and restarted your computer, it should work.
Example: when i click on the node 1 engine it shows the 32 bit drivers only and the same for 64 bit.
VST plug-ins …. no drivers. Synfire is listing 32 bit MIDI drivers and only the 64 bit Engine uses 64 bit MIDI drivers.
somehow the setup must be stored
Everything is saved automatically when Synfire quits. To be absolutely sure, you can save the rack and the devices you have changed. No need to repeat that everytime you make a change, though.
Di., 16.10.2012 - 12:45 Permalink
When i click on the Hostname ( node1 engine, etc ) when the midi tab is open, than it is not clear what are 32 or 64 bit drivers
Yes the node1 and node2 shows a tree with pluginns.. if i choose one ..i cannot trigger the driverlist?
When i removed the 32 bit midi driver it disappear on the list
Note: i just tested the nano2 keyboard controller on Cubase 6.5 for 32 and 64 bit versions and it works great there.
Di., 16.10.2012 - 13:27 Permalink
Perhaps are the nano2 drivers already occupied by Cubase 6.5?
The user manual of nanoKEY states that it can not be used with multiple applications at the same time, unless you install the KORG drivers. If you did so and restarted your computer, it should work.
Ok ..
- shared rack-> Halion4 . .GM sounds
- Korg midi USB 932 and 64 bit installed )
-Midi@audio setup -> start both engines ( automatically )
- install both versions vst Halion4 in SFE
- put option for midi in driverlist for midi ports.. working ..test ..flickering red by presssing keyboard
- than go to arrangement window.. playing nanokeybord after assigning first a sound to the instrument must now be possible ?
Di., 16.10.2012 - 14:37 Permalink
Hi,
Yes shoud be possible but you might need to turn on midi thru in the playback menu to hear the sound.
If it doesn't work, try drawing some notes in the arrangement and pressing play. Do this on an instrument track with your vst sound setup. Does this make sound?
Try pressing record in synfire and playing the nano keyboard. Does it record the notes into the arrangement?