I have made additional changes in Cabel CVS at xxx.

Csound instrument definitions generated by Cabel now use
"basename_number" instead of a plain number, where "basename" is the
base name of the Cabel patch file. This allows multiple .ins
(instrument patch) files saved from Cabel to be #included in a single
Csound orchestra without conflicts.

All Cabel modules that incorporate function tables have been changed.
The function tables are no longer defined in the orchestra header.
They are now defined in the body of the Csound instrument or opcode
definitions using the ftgenonce opcode. Again, this enables #including
multiple Cabel instruments in a single Csound orchestra without Csound
compilation errors.

The goal here is to be able to create and edit quite complex Csound
orchestras, whether for live performance or for off-line rendering,
using Cabel and without needing to cut and paste. The user would edit
a master orchestra that would include .ins files saved from Cabel
patches containing individual instruments. Any or all of the #included
instruments could be edited, and the piece could be tested again and
again in a tight loop with instrument edits.

This is already possible now with some limitations. My next steps will be:

Include the signal flow graph opcodes and the Jacko opcodes as Cabel modules.

Update the archive file for download on SourceForge.

Regards,
Mike


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

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Hi,

I was surprised that Cabel run without a hitch on Ubuntu a few weeks
ago, I couldn't make it run some years ago when I first tried.... It's
a nice simple system.

How hard do you think it would be for score events passed via the API
to support named instruments?

Cheers,
Andrés

On Thu, Apr 8, 2010 at 1:46 AM, Michael Gogins  wrote:
> I have made additional changes in Cabel CVS at xxx.
>
> Csound instrument definitions generated by Cabel now use
> "basename_number" instead of a plain number, where "basename" is the
> base name of the Cabel patch file. This allows multiple .ins
> (instrument patch) files saved from Cabel to be #included in a single
> Csound orchestra without conflicts.
>
> All Cabel modules that incorporate function tables have been changed.
> The function tables are no longer defined in the orchestra header.
> They are now defined in the body of the Csound instrument or opcode
> definitions using the ftgenonce opcode. Again, this enables #including
> multiple Cabel instruments in a single Csound orchestra without Csound
> compilation errors.
>
> The goal here is to be able to create and edit quite complex Csound
> orchestras, whether for live performance or for off-line rendering,
> using Cabel and without needing to cut and paste. The user would edit
> a master orchestra that would include .ins files saved from Cabel
> patches containing individual instruments. Any or all of the #included
> instruments could be edited, and the piece could be tested again and
> again in a tight loop with instrument edits.
>
> This is already possible now with some limitations. My next steps will be:
>
> Include the signal flow graph opcodes and the Jacko opcodes as Cabel modules.
>
> Update the archive file for download on SourceForge.
>
> Regards,
> Mike
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
>
> 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"
>
>



-- 


Andrés


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"

Score events to named instruments is easy because Csound assigns an
instrument number to each named instrument. They are numbered in order
of definition. Also, I think an inputMessage call which takes just a
string would work fine with an instrument name explicitly in the i
statement.

Regards,
Mike

On Thu, Apr 8, 2010 at 12:29 PM, Andres Cabrera  wrote:
> Hi,
>
> I was surprised that Cabel run without a hitch on Ubuntu a few weeks
> ago, I couldn't make it run some years ago when I first tried.... It's
> a nice simple system.
>
> How hard do you think it would be for score events passed via the API
> to support named instruments?
>
> Cheers,
> Andrés
>
> On Thu, Apr 8, 2010 at 1:46 AM, Michael Gogins  wrote:
>> I have made additional changes in Cabel CVS at xxx.
>>
>> Csound instrument definitions generated by Cabel now use
>> "basename_number" instead of a plain number, where "basename" is the
>> base name of the Cabel patch file. This allows multiple .ins
>> (instrument patch) files saved from Cabel to be #included in a single
>> Csound orchestra without conflicts.
>>
>> All Cabel modules that incorporate function tables have been changed.
>> The function tables are no longer defined in the orchestra header.
>> They are now defined in the body of the Csound instrument or opcode
>> definitions using the ftgenonce opcode. Again, this enables #including
>> multiple Cabel instruments in a single Csound orchestra without Csound
>> compilation errors.
>>
>> The goal here is to be able to create and edit quite complex Csound
>> orchestras, whether for live performance or for off-line rendering,
>> using Cabel and without needing to cut and paste. The user would edit
>> a master orchestra that would include .ins files saved from Cabel
>> patches containing individual instruments. Any or all of the #included
>> instruments could be edited, and the piece could be tested again and
>> again in a tight loop with instrument edits.
>>
>> This is already possible now with some limitations. My next steps will be:
>>
>> Include the signal flow graph opcodes and the Jacko opcodes as Cabel modules.
>>
>> Update the archive file for download on SourceForge.
>>
>> Regards,
>> Mike
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> 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"
>>
>>
>
>
>
> --
>
>
> Andrés
>
>
> 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


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"

On windows I'm having problems running Csound with Cabel. I keep
getting the following problems:

BEGAN CppSound::compile()...
BEGAN CppSound::compile(15, 026C7238)...
PortMIDI real time MIDI plugin for Csound
PortAudio real-time audio module for Csound
0dBFS level = 32768.0
Csound version 5.11 (float samples) Nov  1 2009
libsndfile-1.0.20
Reading options from $CSOUNDRC: C:\MyDocuments\SourceCode\Csound5\csoundInstall\
Csound\.csoundrc
orchname:  Files\Csound\csound.exe
scorename: tmp.csd
RAWWAVE_PATH: C:\MyDocuments\SourceCode\Csound5\csoundInstall\Csound\samples/
rtaudio: WinMM module enabled
rtmidi: WinMM module enabled
orch compiler:
cannot open orch file Files\Csound\csound.exe
ENDED CppSound::compile.
ENDED CppSound::compile.

Is there a quick fix? The interface looks great now. I thought work on
Cabel had come to an end?


On 8 April 2010 18:11, Anthony Palomba  wrote:
> Hey Michael,
>
> I am not familiar with Cabel, I was wondering if you could give me
> and others a brief summary of what it does and how it interfaces
> with csound.
>
>
> Thanks,
> Anthony
>
>
>
>
> On Thu, Apr 8, 2010 at 11:40 AM, Michael Gogins 
> wrote:
>>
>> Score events to named instruments is easy because Csound assigns an
>> instrument number to each named instrument. They are numbered in order
>> of definition. Also, I think an inputMessage call which takes just a
>> string would work fine with an instrument name explicitly in the i
>> statement.
>>
>> Regards,
>> Mike
>>
>> On Thu, Apr 8, 2010 at 12:29 PM, Andres Cabrera 
>> wrote:
>> > Hi,
>> >
>> > I was surprised that Cabel run without a hitch on Ubuntu a few weeks
>> > ago, I couldn't make it run some years ago when I first tried.... It's
>> > a nice simple system.
>> >
>> > How hard do you think it would be for score events passed via the API
>> > to support named instruments?
>> >
>> > Cheers,
>> > Andrés
>> >
>> > On Thu, Apr 8, 2010 at 1:46 AM, Michael Gogins
>> >  wrote:
>> >> I have made additional changes in Cabel CVS at xxx.
>> >>
>> >> Csound instrument definitions generated by Cabel now use
>> >> "basename_number" instead of a plain number, where "basename" is the
>> >> base name of the Cabel patch file. This allows multiple .ins
>> >> (instrument patch) files saved from Cabel to be #included in a single
>> >> Csound orchestra without conflicts.
>> >>
>> >> All Cabel modules that incorporate function tables have been changed.
>> >> The function tables are no longer defined in the orchestra header.
>> >> They are now defined in the body of the Csound instrument or opcode
>> >> definitions using the ftgenonce opcode. Again, this enables #including
>> >> multiple Cabel instruments in a single Csound orchestra without Csound
>> >> compilation errors.
>> >>
>> >> The goal here is to be able to create and edit quite complex Csound
>> >> orchestras, whether for live performance or for off-line rendering,
>> >> using Cabel and without needing to cut and paste. The user would edit
>> >> a master orchestra that would include .ins files saved from Cabel
>> >> patches containing individual instruments. Any or all of the #included
>> >> instruments could be edited, and the piece could be tested again and
>> >> again in a tight loop with instrument edits.
>> >>
>> >> This is already possible now with some limitations. My next steps will
>> >> be:
>> >>
>> >> Include the signal flow graph opcodes and the Jacko opcodes as Cabel
>> >> modules.
>> >>
>> >> Update the archive file for download on SourceForge.
>> >>
>> >> Regards,
>> >> Mike
>> >>
>> >>
>> >> --
>> >> Michael Gogins
>> >> Irreducible Productions
>> >> http://www.michael-gogins.com
>> >> Michael dot Gogins at gmail dot com
>> >>
>> >>
>> >> 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"
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> >
>> >
>> > Andrés
>> >
>> >
>> > 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
>>
>>
>> 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"

I will make an entry on my blog about that when I have a good example,
which I am working on. Should be in a few days or weeks.

I should add, I am very interested in the possibility, but I do not
know how well this will really pan out in practice. I do feel that
lack of a graphical patcher has limited me in Csound instrument
design, though.

Regards,
Mike

On Thu, Apr 8, 2010 at 1:11 PM, Anthony Palomba  wrote:
> Hey Michael,
>
> I am not familiar with Cabel, I was wondering if you could give me
> and others a brief summary of what it does and how it interfaces
> with csound.
>
>
> Thanks,
> Anthony
>
>
>
>
> On Thu, Apr 8, 2010 at 11:40 AM, Michael Gogins 
> wrote:
>>
>> Score events to named instruments is easy because Csound assigns an
>> instrument number to each named instrument. They are numbered in order
>> of definition. Also, I think an inputMessage call which takes just a
>> string would work fine with an instrument name explicitly in the i
>> statement.
>>
>> Regards,
>> Mike
>>
>> On Thu, Apr 8, 2010 at 12:29 PM, Andres Cabrera 
>> wrote:
>> > Hi,
>> >
>> > I was surprised that Cabel run without a hitch on Ubuntu a few weeks
>> > ago, I couldn't make it run some years ago when I first tried.... It's
>> > a nice simple system.
>> >
>> > How hard do you think it would be for score events passed via the API
>> > to support named instruments?
>> >
>> > Cheers,
>> > Andrés
>> >
>> > On Thu, Apr 8, 2010 at 1:46 AM, Michael Gogins
>> >  wrote:
>> >> I have made additional changes in Cabel CVS at xxx.
>> >>
>> >> Csound instrument definitions generated by Cabel now use
>> >> "basename_number" instead of a plain number, where "basename" is the
>> >> base name of the Cabel patch file. This allows multiple .ins
>> >> (instrument patch) files saved from Cabel to be #included in a single
>> >> Csound orchestra without conflicts.
>> >>
>> >> All Cabel modules that incorporate function tables have been changed.
>> >> The function tables are no longer defined in the orchestra header.
>> >> They are now defined in the body of the Csound instrument or opcode
>> >> definitions using the ftgenonce opcode. Again, this enables #including
>> >> multiple Cabel instruments in a single Csound orchestra without Csound
>> >> compilation errors.
>> >>
>> >> The goal here is to be able to create and edit quite complex Csound
>> >> orchestras, whether for live performance or for off-line rendering,
>> >> using Cabel and without needing to cut and paste. The user would edit
>> >> a master orchestra that would include .ins files saved from Cabel
>> >> patches containing individual instruments. Any or all of the #included
>> >> instruments could be edited, and the piece could be tested again and
>> >> again in a tight loop with instrument edits.
>> >>
>> >> This is already possible now with some limitations. My next steps will
>> >> be:
>> >>
>> >> Include the signal flow graph opcodes and the Jacko opcodes as Cabel
>> >> modules.
>> >>
>> >> Update the archive file for download on SourceForge.
>> >>
>> >> Regards,
>> >> Mike
>> >>
>> >>
>> >> --
>> >> Michael Gogins
>> >> Irreducible Productions
>> >> http://www.michael-gogins.com
>> >> Michael dot Gogins at gmail dot com
>> >>
>> >>
>> >> 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"
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> >
>> >
>> > Andrés
>> >
>> >
>> > 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
>>
>>
>> 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


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"

Hi,

Seems the problem is here:
> cannot open orch file Files\Csound\csound.exe

The space is apparently messing up things...

Cheers,
Andrés

On Thu, Apr 8, 2010 at 6:25 PM, Rory Walsh  wrote:
> On windows I'm having problems running Csound with Cabel. I keep
> getting the following problems:
>
> BEGAN CppSound::compile()...
> BEGAN CppSound::compile(15, 026C7238)...
> PortMIDI real time MIDI plugin for Csound
> PortAudio real-time audio module for Csound
> 0dBFS level = 32768.0
> Csound version 5.11 (float samples) Nov  1 2009
> libsndfile-1.0.20
> Reading options from $CSOUNDRC: C:\MyDocuments\SourceCode\Csound5\csoundInstall\
> Csound\.csoundrc
> orchname:  Files\Csound\csound.exe
> scorename: tmp.csd
> RAWWAVE_PATH: C:\MyDocuments\SourceCode\Csound5\csoundInstall\Csound\samples/
> rtaudio: WinMM module enabled
> rtmidi: WinMM module enabled
> orch compiler:
> cannot open orch file Files\Csound\csound.exe
> ENDED CppSound::compile.
> ENDED CppSound::compile.
>
> Is there a quick fix? The interface looks great now. I thought work on
> Cabel had come to an end?
>
>
> On 8 April 2010 18:11, Anthony Palomba  wrote:
>> Hey Michael,
>>
>> I am not familiar with Cabel, I was wondering if you could give me
>> and others a brief summary of what it does and how it interfaces
>> with csound.
>>
>>
>> Thanks,
>> Anthony
>>
>>
>>
>>
>> On Thu, Apr 8, 2010 at 11:40 AM, Michael Gogins 
>> wrote:
>>>
>>> Score events to named instruments is easy because Csound assigns an
>>> instrument number to each named instrument. They are numbered in order
>>> of definition. Also, I think an inputMessage call which takes just a
>>> string would work fine with an instrument name explicitly in the i
>>> statement.
>>>
>>> Regards,
>>> Mike
>>>
>>> On Thu, Apr 8, 2010 at 12:29 PM, Andres Cabrera 
>>> wrote:
>>> > Hi,
>>> >
>>> > I was surprised that Cabel run without a hitch on Ubuntu a few weeks
>>> > ago, I couldn't make it run some years ago when I first tried.... It's
>>> > a nice simple system.
>>> >
>>> > How hard do you think it would be for score events passed via the API
>>> > to support named instruments?
>>> >
>>> > Cheers,
>>> > Andrés
>>> >
>>> > On Thu, Apr 8, 2010 at 1:46 AM, Michael Gogins
>>> >  wrote:
>>> >> I have made additional changes in Cabel CVS at xxx.
>>> >>
>>> >> Csound instrument definitions generated by Cabel now use
>>> >> "basename_number" instead of a plain number, where "basename" is the
>>> >> base name of the Cabel patch file. This allows multiple .ins
>>> >> (instrument patch) files saved from Cabel to be #included in a single
>>> >> Csound orchestra without conflicts.
>>> >>
>>> >> All Cabel modules that incorporate function tables have been changed.
>>> >> The function tables are no longer defined in the orchestra header.
>>> >> They are now defined in the body of the Csound instrument or opcode
>>> >> definitions using the ftgenonce opcode. Again, this enables #including
>>> >> multiple Cabel instruments in a single Csound orchestra without Csound
>>> >> compilation errors.
>>> >>
>>> >> The goal here is to be able to create and edit quite complex Csound
>>> >> orchestras, whether for live performance or for off-line rendering,
>>> >> using Cabel and without needing to cut and paste. The user would edit
>>> >> a master orchestra that would include .ins files saved from Cabel
>>> >> patches containing individual instruments. Any or all of the #included
>>> >> instruments could be edited, and the piece could be tested again and
>>> >> again in a tight loop with instrument edits.
>>> >>
>>> >> This is already possible now with some limitations. My next steps will
>>> >> be:
>>> >>
>>> >> Include the signal flow graph opcodes and the Jacko opcodes as Cabel
>>> >> modules.
>>> >>
>>> >> Update the archive file for download on SourceForge.
>>> >>
>>> >> Regards,
>>> >> Mike
>>> >>
>>> >>
>>> >> --
>>> >> Michael Gogins
>>> >> Irreducible Productions
>>> >> http://www.michael-gogins.com
>>> >> Michael dot Gogins at gmail dot com
>>> >>
>>> >>
>>> >> 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"
>>> >>
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> >
>>> > Andrés
>>> >
>>> >
>>> > 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
>>>
>>>
>>> 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"
>
>



-- 


Andrés


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"

Pull down the configuration dialog to reveal hidden fields (I will fix
this if I can) and set up the right paths etc.

Development of Cabel by its authors has evidently stopped.

I am continuing to work on it IF AND ONLY IF I see clear benefit to my
own work. It's not clear that what I am doing will in fact end up
being useful, but since I do feel the lack of a GUI patcher for Csound
and Cabel does already sort of work, that is the path I am pursuing
right now.

I looked at Surmulot but it seemed like a lot of stuff that might be
complex and fragile, and I couldn't get it to work right off the bat
the way I did with Cabel.

If I had the sources for Russell Pinkston's original GUI patcher for
Csound I would probably try fixing that up to be more useful. It was a
lot faster and easier to use than Cabel. It's not just adding opcodes
(which it already allows) but other assumptions (#includes,
input/output, MIDI/score, etc, etc.).

One day, there will be a magnificent score writer, with MIDI
sequencing, that is scriptable and that embeds Csound, other
programmable software synthesizers, and has GUI patchers for them,
etc. The file format will be tagged text and you will be able to
switch back and forth between GUI patches/code patches/note
lists/notation and so on and so on. This will not be stuck with 12 TET
or MIDI and it will become a standard, sort of like the piano or the
grand staff. Then we will be able to get down and make some computer
music.

There just isn't enough time in the day.

At some point, I may buy Sibelius and try running CsoundVST in it, and
try running Cabel from CsoundVST via Python opcodes or some other sort
of hack...

BTW, thanks for adding Python support to Csound5Gui.

Regards,
Mike



On Thu, Apr 8, 2010 at 1:46 PM, Andres Cabrera  wrote:
> Hi,
>
> Seems the problem is here:
>> cannot open orch file Files\Csound\csound.exe
>
> The space is apparently messing up things...
>
> Cheers,
> Andrés
>
> On Thu, Apr 8, 2010 at 6:25 PM, Rory Walsh  wrote:
>> On windows I'm having problems running Csound with Cabel. I keep
>> getting the following problems:
>>
>> BEGAN CppSound::compile()...
>> BEGAN CppSound::compile(15, 026C7238)...
>> PortMIDI real time MIDI plugin for Csound
>> PortAudio real-time audio module for Csound
>> 0dBFS level = 32768.0
>> Csound version 5.11 (float samples) Nov  1 2009
>> libsndfile-1.0.20
>> Reading options from $CSOUNDRC: C:\MyDocuments\SourceCode\Csound5\csoundInstall\
>> Csound\.csoundrc
>> orchname:  Files\Csound\csound.exe
>> scorename: tmp.csd
>> RAWWAVE_PATH: C:\MyDocuments\SourceCode\Csound5\csoundInstall\Csound\samples/
>> rtaudio: WinMM module enabled
>> rtmidi: WinMM module enabled
>> orch compiler:
>> cannot open orch file Files\Csound\csound.exe
>> ENDED CppSound::compile.
>> ENDED CppSound::compile.
>>
>> Is there a quick fix? The interface looks great now. I thought work on
>> Cabel had come to an end?
>>
>>
>> On 8 April 2010 18:11, Anthony Palomba  wrote:
>>> Hey Michael,
>>>
>>> I am not familiar with Cabel, I was wondering if you could give me
>>> and others a brief summary of what it does and how it interfaces
>>> with csound.
>>>
>>>
>>> Thanks,
>>> Anthony
>>>
>>>
>>>
>>>
>>> On Thu, Apr 8, 2010 at 11:40 AM, Michael Gogins 
>>> wrote:
>>>>
>>>> Score events to named instruments is easy because Csound assigns an
>>>> instrument number to each named instrument. They are numbered in order
>>>> of definition. Also, I think an inputMessage call which takes just a
>>>> string would work fine with an instrument name explicitly in the i
>>>> statement.
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>> On Thu, Apr 8, 2010 at 12:29 PM, Andres Cabrera 
>>>> wrote:
>>>> > Hi,
>>>> >
>>>> > I was surprised that Cabel run without a hitch on Ubuntu a few weeks
>>>> > ago, I couldn't make it run some years ago when I first tried.... It's
>>>> > a nice simple system.
>>>> >
>>>> > How hard do you think it would be for score events passed via the API
>>>> > to support named instruments?
>>>> >
>>>> > Cheers,
>>>> > Andrés
>>>> >
>>>> > On Thu, Apr 8, 2010 at 1:46 AM, Michael Gogins
>>>> >  wrote:
>>>> >> I have made additional changes in Cabel CVS at xxx.
>>>> >>
>>>> >> Csound instrument definitions generated by Cabel now use
>>>> >> "basename_number" instead of a plain number, where "basename" is the
>>>> >> base name of the Cabel patch file. This allows multiple .ins
>>>> >> (instrument patch) files saved from Cabel to be #included in a single
>>>> >> Csound orchestra without conflicts.
>>>> >>
>>>> >> All Cabel modules that incorporate function tables have been changed.
>>>> >> The function tables are no longer defined in the orchestra header.
>>>> >> They are now defined in the body of the Csound instrument or opcode
>>>> >> definitions using the ftgenonce opcode. Again, this enables #including
>>>> >> multiple Cabel instruments in a single Csound orchestra without Csound
>>>> >> compilation errors.
>>>> >>
>>>> >> The goal here is to be able to create and edit quite complex Csound
>>>> >> orchestras, whether for live performance or for off-line rendering,
>>>> >> using Cabel and without needing to cut and paste. The user would edit
>>>> >> a master orchestra that would include .ins files saved from Cabel
>>>> >> patches containing individual instruments. Any or all of the #included
>>>> >> instruments could be edited, and the piece could be tested again and
>>>> >> again in a tight loop with instrument edits.
>>>> >>
>>>> >> This is already possible now with some limitations. My next steps will
>>>> >> be:
>>>> >>
>>>> >> Include the signal flow graph opcodes and the Jacko opcodes as Cabel
>>>> >> modules.
>>>> >>
>>>> >> Update the archive file for download on SourceForge.
>>>> >>
>>>> >> Regards,
>>>> >> Mike
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Michael Gogins
>>>> >> Irreducible Productions
>>>> >> http://www.michael-gogins.com
>>>> >> Michael dot Gogins at gmail dot com
>>>> >>
>>>> >>
>>>> >> 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"
>>>> >>
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> >
>>>> >
>>>> > Andrés
>>>> >
>>>> >
>>>> > 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
>>>>
>>>>
>>>> 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"
>>
>>
>
>
>
> --
>
>
> Andrés
>
>
> 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


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"