I'm in the process of programmatically dealing with this situation by
writing a Python script that will allow users to easily import
existing instruments from either a composition or an instrument
library file. Instrument names / numbers are assigned after
importation, and I'm also trying to work out a system of auto-managing
table numbers, UDOs, and chn busses. Reusing instruments in new pieces
should be a walk in the park, if I manage to streamline the process
instead of add an extra layer of complexity.


On Sun, Apr 22, 2012 at 8:50 AM, Ralph Bluecoat  wrote:
> Hello,
>
> I realize that many people on this mailing list must have at least a decades
> worth of Csound instruments on their computer somewhere. How does one keep
> track and organize of all of those instruments? I'm trying to create a
> systematic way of organizing my own personal library of sounds, and I could
> use some inspiration.
>
> Thanks,
>
> -Ralph



-- 
codehop.com | #code #art #music

I use my program blue, which has an library feature for organizing
instruments into folders.  When I start a new piece, I usually go
through my library and find instruments I want to use and
drag-and-drop them into my project.  blue's instrument system has
instruments completely encapsulated, so all dependencies (ftables,
UDO's, etc.) are packaged with the instrument, so it is easy to
drag-and-drop and just start working.

In the library I have things organized into different folders, some by
synthesis type, others just by name of the instrument with different
versions within that folder.  I had been meaning to add tags to blue's
library (as well as the blueShare instruments) so that one can
sort/search by tags, amongst other things.  This will probably happen
in late summer after some other work.

On Sun, Apr 22, 2012 at 5:31 PM, Jacob Joaquin  wrote:
> I'm in the process of programmatically dealing with this situation by
> writing a Python script that will allow users to easily import
> existing instruments from either a composition or an instrument
> library file. Instrument names / numbers are assigned after
> importation, and I'm also trying to work out a system of auto-managing
> table numbers, UDOs, and chn busses. Reusing instruments in new pieces
> should be a walk in the park, if I manage to streamline the process
> instead of add an extra layer of complexity.
>
>
> On Sun, Apr 22, 2012 at 8:50 AM, Ralph Bluecoat  wrote:
>> Hello,
>>
>> I realize that many people on this mailing list must have at least a decades
>> worth of Csound instruments on their computer somewhere. How does one keep
>> track and organize of all of those instruments? I'm trying to create a
>> systematic way of organizing my own personal library of sounds, and I could
>> use some inspiration.
>>
>> Thanks,
>>
>> -Ralph
>
>
>
> --
> codehop.com | #code #art #music
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

I download other people's pieces and instruments into my orc
directory, with one subdirectory per composer.

Then I edit the orc files to use a consistent sample rate/ksmps and
render the pieces.

If I hear something I like, I copy the instr definitions into my
master orc file. An earlier version of this file exists in the Csound
examples/CsoundAC.orc file.

I change the instr definitions to use a standard set of pfields, move
the ftables out of the  score and into the instr using ftgenonce, add
a damping envelope, use higher-quality opcodes where possible, use the
signal flow graph opcodes, try to normalize the amplitude, and so on.

When I do an actual piece, I copy the instr from the master orc file
and paste it into the actual piece. Because of the consistent set of
pfelds and the use of the signal flow graph opcodes, it is easy to
simply paste instruments into the orchestra. In the orchestra header,
I use the connect opcode for routing signals from instruments to
master effects modules.

Regards,
Mike

On Sun, Apr 22, 2012 at 12:39 PM, Steven Yi  wrote:
> I use my program blue, which has an library feature for organizing
> instruments into folders.  When I start a new piece, I usually go
> through my library and find instruments I want to use and
> drag-and-drop them into my project.  blue's instrument system has
> instruments completely encapsulated, so all dependencies (ftables,
> UDO's, etc.) are packaged with the instrument, so it is easy to
> drag-and-drop and just start working.
>
> In the library I have things organized into different folders, some by
> synthesis type, others just by name of the instrument with different
> versions within that folder.  I had been meaning to add tags to blue's
> library (as well as the blueShare instruments) so that one can
> sort/search by tags, amongst other things.  This will probably happen
> in late summer after some other work.
>
> On Sun, Apr 22, 2012 at 5:31 PM, Jacob Joaquin  wrote:
>> I'm in the process of programmatically dealing with this situation by
>> writing a Python script that will allow users to easily import
>> existing instruments from either a composition or an instrument
>> library file. Instrument names / numbers are assigned after
>> importation, and I'm also trying to work out a system of auto-managing
>> table numbers, UDOs, and chn busses. Reusing instruments in new pieces
>> should be a walk in the park, if I manage to streamline the process
>> instead of add an extra layer of complexity.
>>
>>
>> On Sun, Apr 22, 2012 at 8:50 AM, Ralph Bluecoat  wrote:
>>> Hello,
>>>
>>> I realize that many people on this mailing list must have at least a decades
>>> worth of Csound instruments on their computer somewhere. How does one keep
>>> track and organize of all of those instruments? I'm trying to create a
>>> systematic way of organizing my own personal library of sounds, and I could
>>> use some inspiration.
>>>
>>> Thanks,
>>>
>>> -Ralph
>>
>>
>>
>> --
>> codehop.com | #code #art #music
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

For the (Python) program I am developing I have made a structure of folders
like this:
csds - contains .csd files
scores - contains .sco file
orcs - contains orchestra files (.orc)
instruments -  contains .ins files, basically from instr .. .. endin
samples - contains samples and soundfonts
udos - contains udos
midis - contains midi files

The program has a very simple structure:
input ( can be midi in, a midi file, an orc file, etc)
  |
  V
process ( can be a csd file, an ins file, a python program)
  |
  V
output ...

This way I can make many combinations :
e.g. play a instrument  file with input form a .sco file or .mid file


etc.

Richard






--
View this message in context: http://csound.1045644.n5.nabble.com/Organizing-csound-instruments-tp5657565p5657784.html
Sent from the Csound - General mailing list archive at Nabble.com.