Posted
'Save to Global Rack' is an option available if you right-click on a DD in the Arrangement DD (private) rack.
From the description, I thought it would move it from the private rack to the Global Rack. However, it doesn't do that. What it does is save another copy of the DD for use in another rack.
I think this is misleading and adds further confusion to an already complicated area. Perhaps it should be called 'Save copy of Device Description' or something similar?
I also don't understand the benefit of saving presets in a private rack, because this doesn't update the DD (because it's not global). So you end up with a preset that doesn't match the DD. It's all very confusing!
Tue, 2014-12-09 - 20:16 Permalink
Yes, little changes in a wording can make a big difference. Thanks.
If you save a preset (or should it be 'Template' ?) of a module on a private rack, a copy of the device is included with the file. If the preset is later loaded into a global rack, a copy of the device will be saved to disk where the global devices are, unless a device with the same unique ID already exists.
I never really liked the idea that once a DD is copied, it will no longer be updated when the user edits the original. On the other hand, it would have unpredictable side effects on many arrangements. The former means a little more work, the latter means chaos. After a while I came to the conclusion that chaos is worst ;-)
Tue, 2014-12-09 - 23:12 Permalink
One problem is that anything 'global' should never be changed because, as you say, it would affect many arrangements.
My problem is that I very rarely want to use the same setup on different projects. The only true global items I have are a GM one, and one for the global instruments.
So I started saving global racks to the project folder instead of the normal place. The problem with that is that if I want to quickly fire-up Synfire for a quick idea, I have to wait ages for the last global rack to load, when all I want is a few basic instruments.
So now I've just been using private racks, but I've got in a complete mess with lots of different DDs and presets. Also, I can't then re-use a private DD without saving yet another copy of it as global.
The auto-renaming of DDs maybe doen't help either. Perhaps if one already exists, we could have the option of re-naming it to our own liking? At least that would give some sense of control. That way, you could easily save a private DD with a preset as something meaningful, and have it available for use elsewhere.
Wed, 2014-12-10 - 00:11 Permalink
My problem is that I very rarely want to use the same setup on different projects.
But why you don't use a fixed sound rack or a mixed sound rack ? ( both are global )
Make a template for both with 16 sounds and assign the sounds you need and give it a project name
Bypassing racks good be helpful !... only the latest rack to construct is loading..saves a lot of loading time..this is a new feature in Synfire to implent seems to me ?
Wed, 2014-12-10 - 09:10 Permalink
Also, I can't then re-use a private DD without saving yet another copy of it as global.
You can: Either make a preset, or wait for the next update: You will be able to copy & paste a preset via the clipboard without saving it to disk.
So I started saving global racks to the project folder instead of the normal place.
That's a good idea only if you share the same rack with multiple arrangements, e.g. a film score with many short snippets composed to fit a theme. Otherwise a private arrangement rack is better.
The auto-renaming of DDs maybe doen't help either.
You can edit a DD's unique id before saving (open the lock). Change its generic name to something meaningful that associates the plug-in or sound. The filename is created from this id.
Wed, 2014-12-10 - 12:18 Permalink
I think what happened was that I loaded a preset into a private rack, then I changed it and saved it back as the original name. When I later re-loaded it into another project there was a mis-match because the plugin loaded as I had changed it, but the DD was still the same as before.
I've also somehow ended up with multiple presets of the same name but that are physically different. It's very easy to get in a mess unless you're completely aware of what's going on behind the scenes.
The auto-renaming I'm referring to is when you 'Save to Gobal Rack'. This is how I've ended up with many DDs, and I've lost control of what's what.
The update sounds interesting. ETA?
Mon, 2014-12-15 - 21:39 Permalink
How about, if prior to startup, Synfire gave the user choices:
1. Load a Default Global Rack
2. Choose a Global Rack to load
3. Load a project with it's associated Private Rack
4. Startup with a Null Rack
+1
It also bothers me that Synfire necessarily always wants to start the last loaded global rack. To have the above options would be great. The option "Load the last used Global Rack" should be added in that list of course. And in the program settings it could be selectable if you do want to have those options available on startup or not.
Mon, 2014-12-15 - 22:40 Permalink
How about, if prior to startup, Synfire gave the user choices:
1. Load a Default Global Rack
2. Choose a Global Rack to load
3. Load a project with it's associated Private Rack
4. Startup with a Null Rack
5. Load the Last Rack used.
How about 3 Tabs - Start Synfire - Load Project - Load Rack
This would enable the user to set up different Global Racks for different categories. Classical - Jazz - Rock - Pop - whatever. It's important to be able to Name these Global Racks and to be able to choose one as the "Default Global Rack".
Mon, 2014-12-15 - 22:46 Permalink
This has been on the list for a long time now I thought.
A year ago:
(https://users.cognitone.com/content/default-global-rack)
9 months ago:
(https://users.cognitone.com/content/global-rack-options)
Obviously this is not as simple as it sounds, but how long will it be before we see it please?
Tue, 2014-12-16 - 00:33 Permalink
Harrison Mixbus, my favorite DAW, gives you a pop-up window and a choice of
- New Session - Open Session - Audio Setup
It may be complicated, or maybe just a Pop-up to choose which ini file to use.
For now, I'm creating blank projects pre-loaded with private racks and a spreadsheet to show:
Project Name - Project Racks - Device Descriptions - Patches
I tested this by creating some blank projects pre-loaded with private racks.
I then saved them under a new name, added some data and re-saved them.
Next I re-loaded my blank project. My empty tracks and racks were still there.
Then I re-loaded the new project, and again everything was fine.
I think to make this work, the Racks and Device Description's have to be carefully named and documented, otherwise you just wind up with even more confusion. Once I have a satisfactory setup going, I'll be happy to share.
Tue, 2014-12-16 - 08:55 Permalink
Obviously this is not as simple as it sounds, but how long will it be before we see it please?
When a thing gets implemented is not so much about how easy it is to do. It's more about when the topic gets on the table. There are many items on the list related to 'Files & Document Handling' that need to be working well together (e.g. how a global rack is tied to individual arrangements). Developers wrapping their heads around a specific topic often takes a whole day alone, only to get ready for coding. Hasty isolated hacks pile up to over time, add side effects, make a software impossible to maintain. That's why 'The List' is processed by topic, rather than by sequence.
Well. that's just for a little insight into the procedure. Not an excuse.
If this was an urgent problem ... it'd be different. I'll check if the Documents & Files Handling topic deserves a little more priority.