Skip to main content

Experimental Audio Engine

Posted

Since some plug-ins with more than 32 audio outputs and/or 2 inputs are currently not supported, I built an experimental Audio Engine that supports up to

  • 70 outputs (32 stereo + 5.1 surround)
  • 4 inputs

In order to test if this works for your specific plug-ins, please try out the experimental Audio Engine and give some feedback.  You will find it in your Cognitone user account, listed with the Synfire files.

You do not need this engine, unless you own one or more plug-ins that exceed 2 inputs and/or 32 outputs and want to use these with the DAW drones.

However, everyone is invited to test this engine with their setup. I would be very much interested if you experience any performance hits due to the increased numer of audio channels being handled.


Tue, 2012-11-27 - 23:03 Permalink

With my limited knowledge .. i cannot relocate the HALion4 Vsti in Synfire

But i installed the new audio engines on the same locations as the old ones.. i think i must make a new fresh reinstall ?

I did a reinstall ..

YES..now i can relocate HALion4 from Synfire E into Cubase 6.5 ..it shows up in Cubase

Was it in the past that i must assign a DAW cubase port first..than relocate.. ..somehow i looks strange it is now a node1 engine 02 ( Halion 4 Vst..) port what makes that the relocate function work ..and the DAW 2 Cubase ..port cannot used for relocating?

Or did a wrong order ?  

Also confusing is when you start with type -> Plug-in ..than the Vsti is not to be seen anymore  --> how do i assign the sound  when i choose the DAW2 Cubase01(..) port  ..Load plugin? .... no Vsti to be seen anymore.
Perhaps i must first assign the sounds to a Node..port and than chance to DAW node? 

 

The bottom line is : i don't know how  i did relocate HAlion 4 with the DAW port ?, but in Cubase 6.5 i dragged the midi from Synfire and it plays in Cubase with HAlion 4 good and also the drone panel is integrated in HALion 4.

Synfire Express has 16 midi channels so there is no chance of overloading i think. The problems comes witth Synfire Pro ?

Ideal should be when i can relocate HAlion  as a multimbral synth with 16 midi channels in one operation

Now i must load for every midi track in Cubase a Vsti HAlion 4.. or do i miss something?  
Only what is the the right workflow for the drone assigning?
Awesome to have HALion 4 now as 2-way  Drone.

Wed, 2012-11-28 - 11:13 Permalink

That's good news. Halion 4 now also works in a drone. Thanks for reporting.

Now i must load for every midi track in Cubase a Vsti HAlion 4

Certainly not. In Cubase it should be possible to create multiple MIDI tracks playing to a single plug-in. Almost every DAW can do that. Please check the Cubase user manual.

Ideal should be when i can relocate HAlion  as a multimbral synth with 16 midi channels in one operation

Synfire does so already. It relocates the entire device including all instruments that use it.

I must admit that I am having difficulties understanding your other questions. If you could restate them, perhaps using other words in a new topic, one by one, that would be very helpful.

Wed, 2012-11-28 - 13:49 Permalink

Certainly not. In Cubase it should be possible to create multiple MIDI tracks playing to a single plug-in. Almost every DAW can do that. Please check the Cubase user manual.

Yes, that is basic handling in Cubase 6.5.

Relocating works for one Vsti assigned to one instrument track..when exported to Cubase i end up with the same Vsti in Cubase.
So for say  6 instrument tracks i must use 6 HAIlion Vsti plugins ?..or do i miss something.

The other questions of mine..  has to do that i am unsure what is the right assigning order in SFP/E to get the relocate function working ( for this i must study the video again )..it is now trial and error.

Wed, 2012-11-28 - 14:11 Permalink

You only need a single plug-in.

In Synfire, you assign multiple instruments to different MIDI channels of the same plug-in (port).

In Cubase, you add an extra MIDI track that plays to the same plug-in.

Wed, 2012-11-28 - 15:08 Permalink

Thanks!

This setup i must practice again and is logical me to use a mult-timbral synth instead of instances of it. 

Fri, 2012-11-30 - 11:24 Permalink

I tried to setup the HALion 4 in SFE and loaded in 2 instrument tracks a Vsti Plugin

Keeping the same port for both ( DAW2....) , but with the first instrument track it was possible to relocate the VSti to Cubase6.5, but the second instrument track there was no relocate function anymore?
I must set up IN SFE a multitimbral VSti (HALion4) and get the same HAILion Multitimbral setup in Cubase

Must i use a shared device setup?..but with this there is no relocate function ?

 

Fri, 2012-11-30 - 12:28 Permalink

When you set the instruments up when using te engine, did you specify a different channel for the second instrument and name it, etc?
Did you look at the vst in the drone, it may ate already loaded all parts?

Fri, 2012-11-30 - 12:56 Permalink

Thanks

When you set the instruments up when using te engine, did you specify a different channel for the second instrument and name it, etc?

 Yes i did

But in Cubase i first assign the Cognitone drone to midi track 1 and than add the second midi track by hand in Cubase

It seems to me logical that i must use relocate only once for instrument track 1 and that's all.
Perhaps i must only install the Cognitone drone in Cubase 6.5  ?
Is there something to find about this issue, also in video /manual information ? 

Fri, 2012-11-30 - 13:12 Permalink

Unfortunately I don't have cubase, im an ableton live user, so my experience will be of limited help.
Basically once I've relocated the instruments to a drone in live I can export the midi from the drone. The drag and drop of the export button gives me a bunch of midi track data that I can then drop onto ableton live tracks. These live tracks should have the midi routed to the track with the drone and vst.
There is one 'track' included in the drag and drop data for each instrument that was setup to use the drone/vst.

In the video section of the website, under synfire and setup, there are a number of vids about using synfire with different daw. If you watch them all it might help you work out what you need to do to adapt the process to work with cubase.
You might also need to set the drone in cubase as omni so t can receive all midi channels fed it.

Fri, 2012-11-30 - 13:46 Permalink

  Thanks

Again puzzling how this getting working :-)

But the manual states that i must add as many Cognitone drones as needed, so ..that is probably the solution

Fri, 2012-11-30 - 17:13 Permalink

You only need a drone to hold a vst, so if that is a 16 part multi-timberal device you only need 1 drone.

Fri, 2012-11-30 - 19:17 Permalink

Thanks!

Than i must setup Cubase 6.5 with a multitimbral setup as usual (it is a basic handling, but it is not every day's work ) and consider the cognitone drone with the Vsti as a startingpoint and extend this with midi channels ( compare the standard multiitimbral Vst i installation with that new one with the Cognitone Drone )