Synfire 2.0.3

Excellent bug hunting Andre. Can't wait to try this out tomorrow!

Hi Andre,

Did I jump the gun? My download file is empty!

> Audio Engine 4.1.1: Support plug-ins with 16 input + 70 output channels

VCV Rack can now be loaded directly, nice!

Thanks a lot for all your hard work!

There are now additional quintuplet options for quantisation and MusicXML output, something not even listed above. Thanks!

Unfortuantely, I still fail to export the previously shared file with 1/20 quintuplets, though. 

Probably not related, but notation software still report an input error like the one below (or a close variant):

Fatal error: line 56 column 34 Content of attribute port does not match its type definition: Engine1:08 is not valid according to xs:positiveInteger..

(I am saying that this is likely not related, because this error is also shown for successful exports without tuplets.)

Will do a few more tests.

I now did a few more tests. Sometimes I now could export to MusicXML music that includes quintuplets (sometimes it works, good!), but not always. I am trying to find a pattern. Sometimes, it is possible to output in principle, but the resulting notation is too complicated.

I will continue doing a few more such tests, but for creating a piece for music notation and tuplets with Synfire, it might be a good idea to keep the figures of each track simple, and then merge multiple tracks (e.g., for piano) later manually in the notation software.

Again, thanks for your work on this!

A bit more details: keeping tracks simple with only a single figure at a time and a single tuplet type per track seems to help Synfire, and it exports more accurate results.

However, even then the results are still not necessarily accurate. It might be that Synfire MusicXML tuplet export can get confused if a tuplet does not start with notes on the beginning of a beat, but instead with some rests. That can confuse Synfire so much that it can even export a longer or shorter rhythm than fits into the time signature.

To give you some idea, I am sharing here a screen shot of some Synfire figures, where the rhythm is reasonably easy to read, and the resulting notation. Note that the chord in the 2nd track and 2nd bar is completely missing in the notation export -- even without any tupletes being involved. As mentioned elsewhere before, chord factories can result in chord notes positioned slightly before their beat, which seems to be the case here too and might confuse the notation export. In the first track, the rhythm of the notated tuplets does not match the rhythm of the tuplets in the Synfire project. The notated rhythm is not even fitting into the time signature.

Maybe this is just happening to me, but it seems like after I updated to 2.0.3 Build 1 the green "Link" button in the Factory tab is no longer working properly. Prior to updating, it would follow whatever chord progression was in the main arrangement tab. And when I changed the progression, it would follow the new progression accordingly. Now, it will only follow the first progression. The weird thing is, the chord names will change in the Factory tab to the new progression, but it will still follow the original one soundwise.

For example, let's say I drag Am,C,Em,D into the Harmony outlet on the Arrangment tab. When I go to the Factory tab and generate a phrase, it will follow Am,C,Em,D. So far so good. After awhile, I want to hear how that phrase sounds with a different progression. So now I'll drag different progression, let's say Gm,A,B,Em. The markers above the generated phrase will indicate that I've changed progressions (now it shows Gm,A,B,Em) but I can hear that it's still following the original progression (Am,C,Em,D). This is even after I've clicked the green "Link" button.

I'm not sure whether or not this has something to do with version 2.0.3. This function was working fine before I updated. If I want to hear the updated progression now I have to go back to the Arrangement tab everytime I generate a new phrase and drag it onto the timeline.

FYI, since yesterday my Synfire installation tells me to download the following update online, but currently there is no download available there.

Synfire Pro 2.0.3 Build #2 (Windows)

I assume that you are aware of this, and that this message within Synfire is just some leftover from an update that was later pulled. No worries, just wanted to let you know in case...

Andre,

I've had a crash when previewing chords in the Palette view. I was switching between root notes and just clicking on sequences of chords and after about 40 or so previews the main programme crashed out. Unfortunately no crash file produced when I look under Help/Updates. Also I now cannot load the project I created to test 2.0.3 (the one that I was working with when the Palette view crash happened). The load process is stuck trying to load Omnisphere VST plugin.

Thanks, Tim

FYI, the green "Link" button in the Factory tab is currently gone. I assume this is on purpose for the quick fix shared today until a proper fix is implemented.

Update: If a library is embedded in a project, then the link button is there and working, but separate libraries do not feature this button. Probably some misunderstanding on my part...

I've come what looks like another small bug. When I open the window to import MIDI files, there is a play button (and what looks like a stop button) for auditioning the MIDI files in my folder. When I press the play button to audition the MIDI file I hear a sample, but when I press the stop button it continues to play. The only way to stop it from playing is to press the play button again. And when I press the play button again to audition the same file, it will not play again. I have to select another file then come back to the file I was just listening to to hear it again.

I'll give an example just to clarify: Let's say I have two MIDI files in my folder, Song A and Song B. I follow the path File>Import>Standard MIDI File and I get the window that contains my MIDI files. I select Song A and hit the play button. I hear a few bars and want to stop it. When I press the stop button, nothing happens and the Song A file continues to play. So now I hit the play button a second time and now the Song A file stops playing. But lets say that just after I stopped it from playing (by pressing the play button) I forgot what it sounded like and I want to hear it one more time. Song A is still selected from that first play through. So I hit play again and nothing happens. Now I have to select Song B (playing it is not necessary) and then select Song A once again just to audition it a second time. I have to follow this process whenever I want to listen to a MIDI file consecutive times after stopping it. So it looks like neither the stop nor play buttons are functioning as intended.

V2.0.3 introduced bug: instruments don't remember their assigned sound if global. Saving and reopening the arrangement shows the red keyboard icons.
Resetting the audio/MIDI system does work, but you have to do this every time you re-open your arrangement.

New example library that lists all factories

Cool.

"instruments don't remember their assigned sound if global. Saving and reopening the arrangement shows the red keyboard icons."

I have found something similar for a while - changing a global device description caused the instrument to be "not found" when re-opening the arrangement.  Saving the global rack seemed to sort it out.

For me, saving the global rack doesn't solve the issue. This didn't happen with 2.0.2.
To be more specific:

1. Assign a sound to a track by choosing Global -> Piano.
2. Make sure such global instrument has a valid sound, e.g. play the demo music or click some keys.
3. Two cases depending on Synfire's mood:

• The arrangement track may play back and no more red icon, but if you save the arrangement and reload, you get it again.
• The arrangement track doesn't get the sound assigned correctly (this alone is another bug), and the icon stays red. Fix: assign it manually from the panel on the right, with the wrench button. However, saving and reopening the arrangement gives you a red icon again.

Unit testing would be much needed for this kind of things lol

I can't possibly know the reason of the bug, but it feels like the global rack is not immediately "recognized" until its window is opened, something like that.

I keep losing work because SFP is locking up. Can we please get a autosave feature?

Synfire 2 is currently unusable. You shouldn't lose "work" because you shouldn't do "work" with it in the first place, only testing. You can't even select stuff from the menus because the popup menus go partly off-screen. And honestly, I'm not surprised: it's not like V1 was much better in terms of usability and bugs.

Anyway, the autosave feature already exists since V1: Preferences -> Files -> check "Automatic Backup". But it's every 10 minutes, and that is not customizable.

got it. thanks. I am also having to reset the audio/midi constantly when using drones. This occurs anytime I change something in Ableton. Also locking up when resampling to a new note value. 

Hi, I only see this version "Synfire Pro 1.10.12 Build #3 (Mac)" in my account.

How do I get this new version Synfire pro 2.0.3?

Ok, I now see that this is a paid upgrade.

A network exception occurred with embedding an URL

How do I get this new version Synfire pro 2.0.3?

By upgrading your license first, in your account at cognitone.com. There are more details in the pre-release thread IIRC, you can start e.g. from here:

https://users.cognitone.com/comment/19051#comment-19051

Ok, I now see that this is a paid upgrade.

It depends on when you bought Synfire. If you bought it recently, the upgrade is free.

I am also having to reset the audio/midi constantly when using drones.

May or may not being related to what I've reported here: https://users.cognitone.com/comment/19661#comment-19661

I'm also having to reset the audio/MIDI system very frequently when using the Palette tab to write a progression, and switching the "immediate audio feedback" button on/off.

@duderanch By the way, if you're not already doing it, please send crash reports via the "Online updates" window.

Hi Andre,

Not sure if it's a bug (or 2.0.3 exclusive) but I've set up 3 drones in Reaper, and was synchronizing both softwares. But at some point something happened and now I can not open my synfire file for the song because it does not find the drone (which is still in Reaper and apparently online).

So I lost my arrangement, apparently. Is there a way to open the file?

Kr,

Carlos

I am getting crashes when trying to import this simple 8 bar midi. I have submitted crash reports. Can someone try to import this?

Can someone try to import this?

I can confirm. It hangs for a while, when searching for interpretations ("X possibilities in Y clusters" etc.) and then it crashes. I've sent a crash report myself too, maybe it can be of help.

Looking at the file in Cubase (where it plays fine) I did notice a couple of very short notes - eg A1 at the start of bar 7 is only one "tick" long.  There were three notes like that and I lengthened them to give this file which imported into Synfire ok for me. Does this file import ok for others?

Is there settings how I can have a pentatonic scale of a chords when I use the free and line draw tools?