Newbie questions and (potential) issues

4 posts / 0 new
Last post
aerial7's picture
aerial7
Online
Last seen 9 min 32 sec ago

Newbie questions and (potential) issues

MIDNAM import:   I have a utility I wrote that extracts patch names from MIDI devices;  I used that to generate MIDNAM files for my hardware synths.   However, none of them would import successfully.    So I tried manually defining a few patches in SynFire and exporting that so I could make sure my MIDNAMs were in the format expected by SynFire.    However, even if I make my MIDNAMs have the same structure and identical content (plus the remaining patch definitions), they still won't import.    In fact, I found that exporting a MIDNAM from SynFire and then re-importing that same unmodified file, also doesn't work.   In looking at different MIDNAMs from different sources, I found some variations that might explain this.....but all I know is I've not gotten import to work.


Sonar drones:   Admittedly, I'm a total newbie at this part....but I didn't make much progress in getting drones to work with Sonar.   In fact, I found out that I couldn't seem to adjust the tempo from SynFire and this made me nervous about the integration of the two.    (I've searched the forum and gotten a mixed impression of whether Sonar and SynFire work well together -- it's not very clear.)     I then decided to try Reaper -- I've always wanted to give that another look anyway.        Normally, I'd say this is a potential deal-breaker for me, however, I'm quite willing to use Reaper in my workflow, especially if it works well with SynFire.


Workflow for guitarists:   Sometimes my songs start out on guitar, so my dream for Synfire is that it will allow me to develop my riffs into well-composed songs.    I tried just sketching in a simple song with a well-worn progression and a few tracks....that I eventually managed to get working on drones in Reaper.   So then I thought I'd just do what guitarists do:   Hit record and solo over the progression.    Is this possible?   The transport controls seem to be one-way, with SynFire controlling the playback and no way to trigger recording in Reaper.    

andre's picture
andre
Offline
Last seen 1 day 4 hours ago

Thanks for reporting the MIDNAM issue. Can you please attach a ZIP with a few MIDNAM files that don't work for you? I will have a look and provide a patch, if possible. Thanks.

I remember others having problems with Sonar too. Transport commands and tempo are sent over a ReWire connection to the DAW. Sonar's implementation of ReWire may be incomplete here, but I can't test right now. Please check if there's a switch in Sonar to enable something like "Allow slave to set tempo" or similar.

The only way to record audio with Synfire is to link it with a DAW and do it there. Once you save the project in Synfire, all MIDI datra is transferred to the drones and is kept there, so you can switch over to the DAW and work there, as if all MIDI was on its tracks.

aerial7's picture
aerial7
Online
Last seen 9 min 32 sec ago

Andre, sure, I'll attach some MIDNAMs, but first, about your response to my workflow question.....

 

Broadly speaking, I think I'll need two workflows.  Some songs start out as audio-based, meaning that I'll want to record audio and/or vocals in my DAW and then use that as the foundation for composing in Synfire.  I still need to try this as part of my evaluation of Synfire, but from what I've seen, I think this is pretty straightforward -- it's just a matter of enabling transport sync and then concentrating on composing in Synfire.....

 

The other worfklow, the one I mentioned briefly in my original post, is a song that's initially composed in Synfire....and where audio is recorded over that using the DAW.   If I understand you correctly, this workflow is something I can't try with the demo version of Synfire because it requires the ability to save in Synfire.   So I'd have to take it on faith that I could start composing in Synfire, sync it up with a DAW, and everytime I hit save in Synfire the MIDI tracks in my DAW would be updated so that using my DAW's transport for Recording as well as Playback would allow me to hear my Synfire-composed tracks.     Is this documented in the manual?  I couldn't find it......

 

I guess as an amateur songwriter, my use cases are a bit different:  My songs are always composed as a mix of audio and MIDI tracks....in fact, some songs are a mix of the two where maybe an intro is initially composed as MIDI but then I add guitar;  sometimes a verse might be composed initially as audio (with vocals or guitar) but then I want to harmonize that in Synfire.   So I need some assurance that Synfire is proven to handle both of these workflows well.   Thanks!

aerial7

andre's picture
andre
Offline
Last seen 1 day 4 hours ago

If I understand you correctly, this workflow is something I can't try with the demo version of Synfire because it requires the ability to save in Synfire.

Instead of saving the arrangement, you can also do File >> Export >> Export MIDI To DAW. Saving is a bit more convenient, because there's a keyboard shortcut for it, but otherwise the effect on the drone's MIDI buffers is the same.

everytime I hit save in Synfire the MIDI tracks in my DAW would be updated so that using my DAW's transport for Recording as well as Playback would allow me to hear my Synfire-composed tracks

Yes. Once Synfire pushed generated MIDI data to the drones, the DAW is in control until you switch to Synfire again. Normal playback in Synfire pushes only a small portion of MIDI data, always a bit ahead of time. The Export command ensures that all data is pushed in one go.

You can even load and play the DAW project without Synfire later on. Albeit the MIDI will not be visible or editable.

Regarding an audio-first workflow, this video shows an example where the vocals are recorded in the DAW and transcribed and harmonized in Synfire:

 

Log in or register to post comments

Scholarly Lite is a free theme, contributed to the Drupal Community by More than Themes.