Posted
I don't get a quick oversight in SFP how a arrangement is build up, when a rootcontainer contains instruments.
Take as example the Orchid Project GPO demo in SFP
For example when i can see that i use a snapshot or a standalone container ( not related with the rootcontainer ) in the structure view?
( this is now not the case in the Orchid Project GPO demo , but it can be possible)
I don't know if SFP shows all instruments in the instrument sheet, used in the arangement when i open the rootcontainer..that means also instruments that are standalone? (not related to the rootcontainer), I did a test and make a new container on top of the rootcontainer and add there a new instrument
It seems that when a make a new instrument in a container what is not related to the rootcontainer and the instrumet sheet of the rootcontainer shows this instrument too from the new container (on top of the rootcontainer)
A snapshot container is related to the rootcontainer, but adding 3 standalone containers as example, than the instrument of these containers are showing up in the rootcontainer and snapshot container instrumentlists too.
Example: In a snapshot of 10 instruments of the rootcontainer i use 5 instruments in the snapshotcontainer and the other 5 instruments stay unused
The used snapshot instrument are in Bold names written ( to chance figure.. ) and the the other 5 are greyed out
When i use a standalone container ( i added a new extra sound) that it shows up in the snapshot container too, also as a greyed out instrument name.
It is confusing that this standalone sound is showing up in the rootcontainer as well in a snapshotcontainer, because this new sound has nothing to do with this these 2 container, because is a stand alone sound.
-------------------------------------------------------------------
1) To avoid this confusion there must be a separation of these container sounds in the instrument list.
2) And in structure view .. also for a standalone container.
For example when i can see that i use a snapshot or a standalone container ( not related with the rootcontainer ) in the container view?
Perhaps a idea to use under the chordtrack in the instrument sheet.... tabbed instrument sheets ?
A tab used for all sounds the whole arrangement ( all containers), rootcontainer, snapshotcontainer, standalone container, what else more?
When i select the container in the structure view ..the tab is selected ..on this way you know what type of container you are dealing with too.
It looks all now the instrumentmanagement in SFP , too simple and complicated ( for me ;) )
Di., 17.07.2012 - 02:18 Permalink
Yes I agree, it is difficult to grasp at first. My understanding is the new added containers will be reflected in the root to show you the structure of the music data. To the right of the instrument should be a line which tells you which container is in which.
To keep things simple in my head. I have each container having one instrument. Even the chord structure is in it's own container. This is helping me to understand where things are.
As I become more adept, if i have a music bed, I might leave a few insruments, and then put in higher containers for a certain instrument when I want to have a variation.
Di., 17.07.2012 - 18:10 Permalink
Keep the root empty and you will always see the structure below. You can put all your music in subcontainers. Andre will beat me to it, but his sample documents are bad examples IMHO. They were all started in root and not developed any further.
Mark, you can use one container per instrument similar to how midi regions work in a sequencer, although their actual purpose is grouping multiple phrases as narrative musical units.
Di., 17.07.2012 - 19:45 Permalink
I thought that there comes a new function in SFP for folding out the imported rootcontainer in subcontainers?
Yes, this function is already there (since version 1.5.10, I think). It's the command "Container >> Pack". Now you can first start a new project at the rootcontainer and later, when your project gets more complex, you can easily move your phrases from the rootcontainer into a new subcontainer with this "Pack" command.