It is correct that Synfire has to be the synch master (i.e. tells a connected DAW where to start and stop). Propellerheads ReWire protocol however uses a different terminology that works the other way round: Here the slave (Synfire) controls the master's transport (DAW). Very much like a remote control.
This works with Logic 8 and, if I don't miss anything important, should still work with its successor.
I make a phrase (melody line) in Logic and then i want this to be sent (through iac bus) to Synfire.
I then want Synfire to come up with chord ideas for this phrae (or even alterations of the phrase) which it sent back (through iac) to Logic , so i can record this midi data in logic.
I read about Synfire but i am not sure if this is possible with it..
Theoretically this should work. Set the respective Logic track to solo and press the record button in Synfire. This will start playback in Logic and capture the output in Synfire.
However, you will likely see all notes recorded a little off their actual timing. Adjusting the appropriate latency in Synfire can be tricky (trial and error). As far as I know Logic's internal timestamps do not go through the IAC driver.
Concerning the other direction, routing midi input to individual tracks through Logic's environment is something of a pain. I don't know whether this was improved with Logic 9 (we only have Logic 8 at this time). Simple recording to the armed track however should be no problem.
Unfortunately Logic can't copy and paste midi data from the clipboard. That would be ideal for data exchange.
HN does not support external synch except simple MIDI clock signals for tempo synchronization with sound generators. The standard way to get MIDI into HN is importing midi files or manual recording.
Our long term goal is to provide copy and paste data exchange support for all sequencers and DAWs that support this. To my knowledge, Logic does not.
Unless you only want to render a simple synth pad, it makes little sense to move a naked chord progression back to Logic. What is it supposed to do with the chord information?
You will enjoy a lot more creative freedom if you stay within Synfire and arrange all instrument's parts there. Once your song has settled to a certain degree, you will want to reimport the final midi file into Logic to begin the actual production phase.
To answer your question: Both HN and Synfire are best for layout-oriented composition tasks. Although there are features that feel real-time, harmonic analysis can not go beyond recognizing one chord at a time in this mode and the resulting progression would probably not make much sense as a whole. Good results require a scan of the entire melody at once (that is: midi import and interactive harmonization).
All our software is cross-platform and uses a very clean and lean foundation (no dependencies on specific OS features), so it should run on all OS versions from Tiger on upwards without problems. If any issues arise, they can be fixed in no time.
If you want to 100% sure about the products, try out the demos. There will be a version 2.0 of HN soon, which might also be interesting.
Here are a few notes on how I followed the Cognitone video to set up Logic 9 as a sound source for Synfire. There may be better ways on the Logic side to do this but this worked for me.
As a first task, I wanted to replace the General Midi instruments in demo Synfire composition: "Chanel No. 5" with Logic 9 instruments.
This worked: Open Logic first. By default Logic is in a good Rewire mode.
In Logic 9 create five software instrument tracks: flute, piano, violins, cello, oboe. Load up your instruments into those tracks however you normally do it. Make sure they work via your midi keyboard. You can hear sound.
You follow the video up to and including the creation of the Logic channel splitter, including the midi routing to the Logic instruments via midi channels 1 thru 5 (or whatever). Don't close the Logic Environment window, you are going to use it again soon.
Know the one IAC Bus you are going to use. I think the video uses bus 8. I used IAC Bus 1. In OSX Audio/Midi setup, I always put IAC in the name of the IAC bus so later on I don't get confused about what buses are what in OSX Logic and other programs.
Hook up the channel splitter input to your IAC bus output. This will bring the midi from Synfire to the splitter. You can unhook, delete the cable, between your keyboard and the Sum of the physical input.
Now in Logic 9, how do we hook the individual midi channels from the IAC bus via the splitter to the instruments?
Go to Mixer view inside Logic Environment window. (My Logic superstition: make sure to use the exact same Environment window, not another copy, otherwise occasional Logic bugs) Copy the five channel strips associated with your five software instrument tracks. Go back to the Clicks & Ports view. Paste the copies of the channel strips. Five times, create a cable between splitter output and a pasted channel strip.
Save Logic 9 project.
Start up Synfire.
Open Chanel No 5 composition.
Save As Chanel No 6 so as not to modify original file.
Play it (in General Midi) to see that it produces sound as delivered.
Ok, two more Synfire chores: (1) make new instruments (2) use them.
Open up Synfire's "Audio & Midi Setup"
Don't play with what's under the routing table as I did. I wrongly thought that's where I would specify some routing.
Rather, work under Device Descriptions. Follow video (with a few interface changes)
Follow the video carefully to make five new instruments under flute, piano, cello, violin and oboe. First you have to be working in a sound bank that you create inside a Device that you create. I call my device L9 Bridge. This takes a few steps in the video.
Set Device Port A (lower left corner of window) to same IAC Bus you use in Logic. Save as you go along. Name your instrument after browsing down the Instrument tree to find its place. Name it something recognizably different. I called my Logic flute: L9 Flute. Later on you'll know
you have found the right flute via the "L9" part of the name.
As of right now, today, don't freak out like me if new edits don't quite show up instantaneously everywhere as they probably should. I've written a lot of software myself and I get that there are some interface improvements that will be made when there is time to do it. The interface is marginally different from what you see in the video - don't sweat it.
Make four more new instruments in Synfire Audio Midi Setup. Test that all five instrument connect to Logic and make sound. Save the whole device. By the way, now you can look back at the Routing table and see that your Logic bridge points to a IAC bus.
Ok, how do you use the new instruments? There may be a better way to do this but I went to the Arrange window with "Chanel No. 6" in it. Click on Flute Motif in the top overview window. In the window below click on the words Solo Flute. Look to the right. Click on Instr. Click on Sound, Click on Browse. Now browse for the flute instrument you made: L9 Flute.
Click OK.
Hit play button at bottom of arrange window. Out comes your beautiful Logic 9 Flute! Pick your Logic sounds for the other four parts.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You can attach files in this forum You can download files in this forum
It is correct that Synfire has to be the synch master (i.e. tells a connected DAW where to start and stop). Propellerheads ReWire protocol however uses a different terminology that works the other way round: Here the slave (Synfire) controls the master's transport (DAW). Very much like a remote control.
