Skip to main content

Midi export from SFP/E to DAW only for Cognitone Drone

Posted

Because  HALion 4 is not accepted by the Cognitone Drone( to many outputs) ..i  am forced to use a Midi Drone.
But with a Midi Drone it seems to be not possible to export Midi from  Synfire P/E with the export button anymore.

Is there a another way to export midi from SFP/E  ..to Cubase  when i use a Midi Drone ? ( not save and load , because that must be over )



 


Sun, 2012-11-18 - 20:28 Permalink

Thanks Juergen

This is not working for the HALion 4 your video gif, it has too many outputs 

Note that there is no Drone window, if there is a MIDI Drone used .. so i cannot export Midi ( due to HALion 4, probably Halion Sonic is working normal in the Cognitone Drone, because your video shows this setup with the expressionmap )

There is no expressionmap connection possible if it is MIDI drone, because exporting midi seems to be also not working anymore  

Maybe it can fixed by Cognitone that there is no easy midi export ( export midi to DAW or dragging ) possible for a Midi Drone ?

Sun, 2012-11-18 - 20:32 Permalink

A MIDI Drone can export the rendered output, as juergen showed correctly. No need to load a plug-in.

Sun, 2012-11-18 - 20:45 Permalink

The "export button" is not a button. It's merely an indicator showing that there is data available for the export. To export the MIDI data you must grab the label of the drone. See enclosed gif. This works also with MIDI drones.

 

Attachments

Sun, 2012-11-18 - 21:41 Permalink

@Juergen uses here a Cognitone Drone and not a MIDi drone ( as setup in Cubase )and not as in SFP/E) as i see it right here.   

In Cubase there is a indirect connection methode with a Cognitone Drone and a separated midi channel for the instrument.

( the Conitone Drone is not installed complete with F11 in Cubase than: Cubase asked to install the Cognitone as Midi track and i choose for no ..this is the "cubase midi drone")

You can use different definitions for a Midi Drone

- the one used by Cognitone

_ the one used in Cubase 

Because i cannot use a Cognitone Drone for HALion 4  in Cubase, than a MIDI drone (SFP/E definition) will also not work

Therefore i am forced to use a Cubase Midi Drone ..and this is not working with the export midi function...that is my point.

------------------------------------------------

HAlion 4 flagship of Vsti soundgeneratingsystem ( 350 Euro) is not to use normal with SFP/E , because the Cognitone drone is not accepting this Vsti ( to many outputs)
In this case  the midi export is also not working anymore

There is no workaround for i am afraid .. i can install HALion4 as Cubase Midi Drone, but that the midi export is not working

So it is a crippled  piece of software  the HAlion 4 in SFP/E ..stupid.

Sun, 2012-11-18 - 22:05 Permalink

@Juergen uses here a Cognitone Drone and not a MIDi drone ( as setup in Cubase )and not as in SFP/E) as i see it right here.

 

No, I have used a MIDI drone in the gif (BTW: MIDI drones are also Cognitone drones  ;) ). A drone becomes a MIDI drone when you tick the checkbox "MIDI Drone" at SFE.  The only difference between these two types of drones is that you cannot load a VSTi into a MIDI drone. Therefore you have to route the MIDI output from the drone to the VSTi manually. There is a tutorial at the Wiki which shows the routing from a MIDI drone to a VSTi: 

https://users.cognitone.com/content/midi-drones-cubase

 

The export of MIDI data from a MIDI drone to a MIDI track at Cubase with drag and drop works the same way as with a regular drone. 

 

Sun, 2012-11-18 - 22:45 Permalink

I read the WIKI ... thanks for this.

 

I was not sure if the setup you describe is monophonic or polyphonic? Does each drone contain one port and 16 channels, or just one port with one channel?

 

Prado

Mon, 2012-11-19 - 02:32 Permalink

Pretty sure it's 1 port 16 channels, just use the same drone instance but change the midi channel on the different instrument inspectors.