> base64 encodes other
>             files to be included (such as midi)
> csb64enc    converts any number of files to Base64 encoded
> CSD tags:
>             

base64 encoded:
What, what for, is that and how do we use it?

Sorry for the ignorance, but I have never used 
or even seen these.

Victor

I have not used the base64 encoding feature either but ...

[Apparently]

The CSD file format is designed not to just encapsulate the orchestra,
score, and csound options into a single file, but also ANY other file that
is required for a particular Csound run.  Thus, you can include Midi files,
input sound files, analysis files, etc. in your CSDs.  But since CSDs are
text files, these binary files must be encoded.  That is what the base64
encoding is for.

Now, this is described in the manual, but how to actually DO IT is another
thing.  The only easy solution I have seen to creating complex CSD files
like this is Istvan's makecsd utility, included in his Csound 4.24 release.

That is why I want to add it to canonical.

Anthony Kozar
anthony.kozar@utoledo.edu
http://akozar.spymac.net/


On 1/18/05 3:58 PM, Victor Lazzarini  etched in
stone:

> 
>> base64 encodes other
>> files to be included (such as midi)
>> csb64enc    converts any number of files to Base64 encoded
>> CSD tags:
>> 
> 
> base64 encoded:
> What, what for, is that and how do we use it?
> 
> Sorry for the ignorance, but I have never used
> or even seen these.
> 
> Victor
>