Posted
A "disable" (mute?) flag for each container, that when set, causes Synfire to completely ignore it when rendering. Could be useful while still deciding whether or not you want to commit to what it contains but don't quite want to remove it yet.
Currently there seems to be no way to turn a temporarily turn a container off other than deleting it.
Fri, 2009-01-30 - 10:56 Permalink
Good idea. You could "pause" the phrases inside the container, but that also has side-effects on inheritance.
We have a general feature category named "Workflow & Convenience" which evolves over time. We will collect features and changes for a while and then decide if and how to implement them. They need to follow a clear design scheme.
Fri, 2009-01-30 - 15:58 Permalink
My concern isn't so much about disabling phrases, it is more about disabling the whole container itself, making Synfire completely ignore its existence.
For example, I might have a couple of alternate chord progressions I want to experiment with and might place them in containers in parallel locations. Since there can only be one value for harmony at a time, I can disable the containers I don't want to use, but not have to delete them if I want to re-enable them later.
Kind of like temporarily "commenting out" containers.
Fri, 2009-01-30 - 18:11 Permalink
Yes, I have done it in similar way to that... for many of my projects I've ended up creating a dedicated companion library for holding things I've created but am not sure about yet.
And this works well, except that it is somewhat of a hassle to have to maintain two separate files (loading two files, saving two files). Maybe each arrangement could have its own embedded library?
Overall I've found the concept of general purpose libraries great in theory, but in practice they seem to amass a large memory footprint quite quickly, so it turns out I am using many small libraries rather than a couple of large ones.
Tue, 2009-02-03 - 02:58 Permalink
Dear Cerators of this Magic software!
I have been experimenting for some time now and I would like to add some considerations to the discussion.
I apreciate very much all what is possible! It is realy a lot.
So, some words about what I find a bit unconvinient.
Measure insert should be free in any place and in chord progresions too.
Container relocation is an issue, I think. I understand compilcations of the vertical context interpretation, however the behaviour of the program at the moment does not feel intuitive. Someone here was asking for container "switch off". This request goes in the same direction. You re-locate or "switch off" a container and then meke new rendering or re-interpretation and the new verticval interpretation is presented.
It feels to me at the moment that priority of vertical interpretation is supressing linear freedom. Prioritising (leyering) containers in relation to the moment of their addition is annoing to me, but probably I do not make proper use of copying and aliasing.
I intend much more experimenting
Best Regards
Andy