I don't understand the reason for separating libraries from projects. Instead of having two hundred projects and two hundred libraries scattered everywhere you have only two hundred projects each with their own library exportable in any other project. Softwares with a separate window for each function are relics from the past (does anyone remember the Unity sampler?) :-)
I store my libraries organised by musical type, well sort of. I do have some specialist ones dedicated to individual instruments like drum patterns, guitar rifts..... With the workflow I use, any tune that uses drums will use phrases from the drum library, all trance songs will use some bass and lead phrases from my trance library, and probably chord progressions too. This isnt rigid I might use some phrases from a classical library, but maybe get the timing from a pattern in the trance library or one of the drum patterns. So I probably have about 20 or so libraries and they are used to make up most of my songs. I still make use of the embedded library however as a sort of scratch pad.
agreed wholeheartedly. Different plugins need different styles of phrases, and it makes sense to keep them all together in a library devoted to the plugin. It would be a nightmare to have to go digging through different projects to find what I need.
It is more convenient then to use a single pool shared among all projects (like Apple loops in Logic) and search through a search window, then group items by category, plugins, etc.
The goal should be to work as much as possible in the same window. That doesn't mean I can't export parts of the pool as a single file, if I want to do it (even if I don't see the reason)
I like the idea of having all libraries in a searchable database, showing up in the embedded library space of an arrange window. Reducing the number of split views there is also a great idea. But, in whatever form of organization, libraries are at the core of music prototyping (some users have hundreds of them), so hiding them away in individual projects doesn't make sense.
That's for the "using" part of the workflow. The arrange window is not a good place to edit a library however. So the library editor won't go away. If only as an authoring tool for library creators.
BTW, we are getting off topic. This is an interesting discussion to have in a separate thread.
Could you add a search window and some grouping criterion to the libraries?
If the external libraries remain, I suggest two new features:
1. A search window both in the floating libraries and in the library embedded into the arrangement, so one can create and store a unique and searchable library common to all projects;
2. a new menu voice: File > Save as Template
The enabled MIDI input does not work when starting Synfire. In this case it is a Parnorama P6 keyboard. I have to go to the Audio & MIDI Setup -> Inputs tab and unselect/ then reselect to make it work.
The enabled MIDI input does not work when starting Synfire
This is a Windows issue with non-multi-client capable USB drivers. Another software probably holds onto the MIDI keyboard already (DAW?), so Synfire needs to forcibly re-take it. Not pretty, but nothing we could do much about, unfortunately. You have a similar issue when you put your DAW back into the foreground?
So, what is the trick to getting mps-1.9b31 to install on Windows 8.1?
I fully deinstalled 1.8.5 and 1.9, removed all references to Cognitone from the registry and modified all the install files to be compatible with previous versions. The Setup was modified to be compatible with both Windows 7 and Windows 8 (two different attempts). (Anti-virus is off and everything is run with admin privs, of course.) I still get the hang and eventual fail where it tells me to continue SETUP in the next window. I only have it installing the 64-bit version of the Audio Engine.
Of course, 1.8.5 didn't have this issue and that window comes up.
I managed to get 1.9b70 to run with the following procedure:
Run the installation up to the error message telling you that there was a problem regarding the installer. Don't click it away!
In
C:\ProgramData\Cognitone\Setup\Synfire
there's a newly created SETUP.EXE - set this file to Windows 7 compatibility and run it manually. This should bring up a UAC dialog and then install Synfire in
C:\Program Files\Cognitone\Synfire
After it has run properly, click the error box away. The content of
C:\ProgramData\Cognitone\Setup
gets deleted after that.
Set
C:\Program Files\Cognitone\Synfire\SYNFIRE.EXE
to Windows 7 compatibility
After finishing this procedure, Synfire should run fine. At least for me it works as supposed.
Thanks for the instructions. I wonder why it works on Windows 7 and 10, only not on 8.1. These startup issues are extremely difficult to debug on Windows. Even more so, as there are four programming languages and technologies involved.
By the way, once I applied the above, the install started working not just for b31 but also for the newly downloaded b32. So, I suspect there may have also been a change to the registry or some other file or configuration that "fixes" the issue. That is, I did not need to do anything special to install b32.
That compatibility flags setting gets stored in a database buried somewhere deep inside Windows.
So it's basically persistent and the fix should last now as every new installation will automatically be done in compatibility mode unless you revert the setting.
Synfire (1.9 b71) crashes after switsching to another OSX app
When i switch OSX (10.13.06) focus to another app (no matter what app) and click back on a Synfire window, the app freezes without recovering (coloured OSX ball rotating).
This is the one bug I am desperately trying to reproduce but can't, although I'm on 10.13. too. Does it happen reliably every time? Do you have "Disable Widgets in Background" enabled?
You referring to the osx widgets? should i disable them completely via terminal?
(i don't know a way to disable them, just googled it)
Sorry for asking, didnt had the time to go through this thread completely.
So far it happens every time.
Update:
i deactivated all widgets with this terminal code: defaults write com.apple.dashboard mcx-disabled -boolean YES
But it didnt help. Next time i opened Synfire, same same...
Thanks. It makes me wonder why it doesn't happen here on same OS. Good to know. I'll double the effort to nail this down, as it's currently the only bug holding us back from declaring 1.9 an official release (there are other minor bugs, but this one is not tolerable for a release).
There's a checkbox in Synfire's Preferences to disable widgets in background. It's whether widgets should be grayed out when the window is not at front. It's off by default. You should probably re-enable your macOS widgets.
Today, i tried again. Same Error. I restarted my mac. No error. I can click outside Synfire as many times as i want.... (have my widgets still terminated)
Since i always have trouble getting Logic & Synfire into Rewire mode, i tried to sync the osx video player MTCVideoSlave via MTC.
When i hit play in Synfire the videplayer will jump to the correct position in the video, but it seems it doesnt recieve a "play" command as well, just the position.
Is rewire actually working in 1.9? I'm using Studio One, and loading up the Synfire Transport for rewire doesn't do any sync'ing with Synfire's transport. Is there a dll for 1.9 that I should check for - where would it be located (it's not in my VST folder).
EDIT - resinstalled audio drivers and now working again.
Mon, 2019-02-18 - 21:58 Permalink
please keep the external libraries, I use them all the time.
Tue, 2019-02-19 - 00:07 Permalink
I fully agree with Blacksun. I use phrases from external libraries for almost every project.
Please keep those.
Tue, 2019-02-19 - 00:27 Permalink
I don't understand the reason for separating libraries from projects. Instead of having two hundred projects and two hundred libraries scattered everywhere you have only two hundred projects each with their own library exportable in any other project. Softwares with a separate window for each function are relics from the past (does anyone remember the Unity sampler?) :-)
Tue, 2019-02-19 - 01:34 Permalink
I store my libraries organised by musical type, well sort of. I do have some specialist ones dedicated to individual instruments like drum patterns, guitar rifts..... With the workflow I use, any tune that uses drums will use phrases from the drum library, all trance songs will use some bass and lead phrases from my trance library, and probably chord progressions too. This isnt rigid I might use some phrases from a classical library, but maybe get the timing from a pattern in the trance library or one of the drum patterns. So I probably have about 20 or so libraries and they are used to make up most of my songs. I still make use of the embedded library however as a sort of scratch pad.
Tue, 2019-02-19 - 03:38 Permalink
I don't use "File -> New -> Library," but I use "Book Symbol -> Gear Symbol -> Create New Library . . . ." all the time.
You're only talking about the "File" menu option, right?
Tue, 2019-02-19 - 03:42 Permalink
agreed wholeheartedly. Different plugins need different styles of phrases, and it makes sense to keep them all together in a library devoted to the plugin. It would be a nightmare to have to go digging through different projects to find what I need.
Tue, 2019-02-19 - 09:39 Permalink
It is more convenient then to use a single pool shared among all projects (like Apple loops in Logic) and search through a search window, then group items by category, plugins, etc.
Tue, 2019-02-19 - 09:45 Permalink
The goal should be to work as much as possible in the same window. That doesn't mean I can't export parts of the pool as a single file, if I want to do it (even if I don't see the reason)
Tue, 2019-02-19 - 12:14 Permalink
I like the idea of having all libraries in a searchable database, showing up in the embedded library space of an arrange window. Reducing the number of split views there is also a great idea. But, in whatever form of organization, libraries are at the core of music prototyping (some users have hundreds of them), so hiding them away in individual projects doesn't make sense.
That's for the "using" part of the workflow. The arrange window is not a good place to edit a library however. So the library editor won't go away. If only as an authoring tool for library creators.
BTW, we are getting off topic. This is an interesting discussion to have in a separate thread.
Wed, 2019-02-20 - 13:24 Permalink
This will be my last OT post :-)
Could you add a search window and some grouping criterion to the libraries?
If the external libraries remain, I suggest two new features:
1. A search window both in the floating libraries and in the library embedded into the arrangement, so one can create and store a unique and searchable library common to all projects;
2. a new menu voice: File > Save as Template
Wed, 2019-02-20 - 23:05 Permalink
Question where do i download synfire at im confused
Thu, 2019-02-21 - 16:42 Permalink
Download here: (https://www.cognitone.com/user/downloads/index.stml)
As for the Scaleboard locking up, how can I reproduce? Or does it happen randomly?
Fri, 2019-02-22 - 16:48 Permalink
1.9
When using a 4K monitor VST plugin UIs are tiny. They were much larger in 1.8.5. Please make them larger so can be read more easily.
Fri, 2019-02-22 - 16:54 Permalink
Fresh install of 1.9
The enabled MIDI input does not work when starting Synfire. In this case it is a Parnorama P6 keyboard. I have to go to the Audio & MIDI Setup -> Inputs tab and unselect/ then reselect to make it work.
Fri, 2019-02-22 - 18:18 Permalink
This is a Windows issue with non-multi-client capable USB drivers. Another software probably holds onto the MIDI keyboard already (DAW?), so Synfire needs to forcibly re-take it. Not pretty, but nothing we could do much about, unfortunately. You have a similar issue when you put your DAW back into the foreground?
Thu, 2019-02-28 - 17:57 Permalink
So, what is the trick to getting mps-1.9b31 to install on Windows 8.1?
I fully deinstalled 1.8.5 and 1.9, removed all references to Cognitone from the registry and modified all the install files to be compatible with previous versions. The Setup was modified to be compatible with both Windows 7 and Windows 8 (two different attempts). (Anti-virus is off and everything is run with admin privs, of course.) I still get the hang and eventual fail where it tells me to continue SETUP in the next window. I only have it installing the 64-bit version of the Audio Engine.
Of course, 1.8.5 didn't have this issue and that window comes up.
Thanks! :)
Steve
Fri, 2019-03-01 - 07:59 Permalink
I managed to get 1.9b70 to run with the following procedure:
C:\ProgramData\Cognitone\Setup\Synfire
there's a newly created SETUP.EXE - set this file to Windows 7 compatibility and run it manually. This should bring up a UAC dialog and then install Synfire in
C:\Program Files\Cognitone\SynfireC:\ProgramData\Cognitone\Setup
gets deleted after that.
C:\Program Files\Cognitone\Synfire\SYNFIRE.EXE
to Windows 7 compatibility
After finishing this procedure, Synfire should run fine. At least for me it works as supposed.
Fri, 2019-03-01 - 08:21 Permalink
Thanks for the instructions. I wonder why it works on Windows 7 and 10, only not on 8.1. These startup issues are extremely difficult to debug on Windows. Even more so, as there are four programming languages and technologies involved.
BTW: There are new builds #71 online now.
Fri, 2019-03-01 - 13:09 Permalink
Thank you all so much! Off I go ... :)
Steve
Fri, 2019-03-01 - 14:14 Permalink
By the way, once I applied the above, the install started working not just for b31 but also for the newly downloaded b32. So, I suspect there may have also been a change to the registry or some other file or configuration that "fixes" the issue. That is, I did not need to do anything special to install b32.
Steve
Fri, 2019-03-01 - 16:29 Permalink
That compatibility flags setting gets stored in a database buried somewhere deep inside Windows.
So it's basically persistent and the fix should last now as every new installation will automatically be done in compatibility mode unless you revert the setting.
Fri, 2019-03-01 - 16:44 Permalink
I believe that is correct, buried in the registry.
Tue, 2019-03-05 - 19:56 Permalink
Synfire (1.9 b71) crashes after switsching to another OSX app
When i switch OSX (10.13.06) focus to another app (no matter what app) and click back on a Synfire window, the app freezes without recovering (coloured OSX ball rotating).
Tue, 2019-03-05 - 21:11 Permalink
This is the one bug I am desperately trying to reproduce but can't, although I'm on 10.13. too. Does it happen reliably every time? Do you have "Disable Widgets in Background" enabled?
Tue, 2019-03-05 - 21:58 Permalink
You referring to the osx widgets? should i disable them completely via terminal?
(i don't know a way to disable them, just googled it)
Sorry for asking, didnt had the time to go through this thread completely.
So far it happens every time.
Update:
i deactivated all widgets with this terminal code:
defaults write com.apple.dashboard mcx-disabled -boolean YESBut it didnt help. Next time i opened Synfire, same same...
Wed, 2019-03-06 - 09:37 Permalink
Thanks. It makes me wonder why it doesn't happen here on same OS. Good to know. I'll double the effort to nail this down, as it's currently the only bug holding us back from declaring 1.9 an official release (there are other minor bugs, but this one is not tolerable for a release).
There's a checkbox in Synfire's Preferences to disable widgets in background. It's whether widgets should be grayed out when the window is not at front. It's off by default. You should probably re-enable your macOS widgets.
Thu, 2019-03-07 - 16:17 Permalink
Today, i tried again. Same Error. I restarted my mac. No error. I can click outside Synfire as many times as i want.... (have my widgets still terminated)
Sun, 2019-03-10 - 19:28 Permalink
External sync via MTC
Since i always have trouble getting Logic & Synfire into Rewire mode, i tried to sync the osx video player MTCVideoSlave via MTC.
When i hit play in Synfire the videplayer will jump to the correct position in the video, but it seems it doesnt recieve a "play" command as well, just the position.
Thu, 2019-03-14 - 19:08 Permalink
Where are the staves? ^____^
Sat, 2019-03-16 - 18:25 Permalink
Is rewire actually working in 1.9? I'm using Studio One, and loading up the Synfire Transport for rewire doesn't do any sync'ing with Synfire's transport. Is there a dll for 1.9 that I should check for - where would it be located (it's not in my VST folder).
EDIT - resinstalled audio drivers and now working again.