Csound Csound-dev Csound-tekno Search About

dssiinit.csd - parsing error in manpage example

Date2015-08-22 13:07
From"Dr. Richard Boulanger"
Subjectdssiinit.csd - parsing error in manpage example
AttachmentsNone  None  

STARTING FILE

Creating options

Creating orchestra

Creating score

rtaudio: PortAudio module enabled ...

using blocking interface

error: syntax error, unexpected T_IDENT (token "dssiinit") from file /Library/Frameworks/CsoundLib64.framework/Resources/Manual/examples/dssiinit.csd (1)

line 15:

>>>gihandle dssiinit <<<

Unexpected untyped word gihandle when expecting a variable

Parsing failed due to invalid input!

Stopping on parser failure

cannot compile orchestra



Date2015-08-22 13:11
From"Dr. Richard Boulanger"
SubjectRe: dssiinit.csd - parsing error in manpage example
AttachmentsNone  None  
NOTE:  similar problem with ALL dssi opcode examples in the manual.

Creating score

rtaudio: PortAudio module enabled ...

using blocking interface

error: syntax error, unexpected T_IDENT (token "dssiinit") from file /Library/Frameworks/CsoundLib64.framework/Resources/Manual/examples/dssiinit.csd (1)

line 15:

>>>gihandle dssiinit <<<

Unexpected untyped word gihandle when expecting a variable

Parsing failed due to invalid input!

Stopping on parser failure

cannot compile orchestra




Date2015-08-22 13:57
Fromjpff
SubjectRe: dssiinit.csd - parsing error in manpage example
Usual questions: platform? version?

I suspect you are using OSx but dssi is a linux plugin format so probably 
not built for OSX.  At least that would be my first guess

==John ff

On Sat, 22 Aug 2015, Dr. Richard Boulanger wrote:

> 
> STARTING FILE
> 
> Creating options
> 
> Creating orchestra
> 
> Creating score
> 
> rtaudio: PortAudio module enabled ...
> 
> using blocking interface
> 
> error: syntax error, unexpected T_IDENT (token "dssiinit") from file/Library/Frameworks/CsoundLib64.framework/Resources/Manual/examples/dssiinit.
> csd (1)
> 
> line 15:
> 
> >>>gihandle dssiinit <<<
> 
> Unexpected untyped word gihandle when expecting a variable
> 
> Parsing failed due to invalid input!
> 
> Stopping on parser failure
> 
> cannot compile orchestra
> 
> 
> 
>

------------------------------------------------------------------------------
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-08-22 14:55
FromVictor Lazzarini
SubjectRe: dssiinit.csd - parsing error in manpage example
yes, these are for Linux.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 22 Aug 2015, at 13:57, jpff  wrote:
> 
> Usual questions: platform? version?
> 
> I suspect you are using OSx but dssi is a linux plugin format so probably 
> not built for OSX.  At least that would be my first guess
> 
> ==John ff
> 
>> On Sat, 22 Aug 2015, Dr. Richard Boulanger wrote:
>> 
>> 
>> STARTING FILE
>> 
>> Creating options
>> 
>> Creating orchestra
>> 
>> Creating score
>> 
>> rtaudio: PortAudio module enabled ...
>> 
>> using blocking interface
>> 
>> error: syntax error, unexpected T_IDENT (token "dssiinit") from file/Library/Frameworks/CsoundLib64.framework/Resources/Manual/examples/dssiinit.
>> csd (1)
>> 
>> line 15:
>> 
>>>>> gihandle dssiinit <<<
>> 
>> Unexpected untyped word gihandle when expecting a variable
>> 
>> Parsing failed due to invalid input!
>> 
>> Stopping on parser failure
>> 
>> cannot compile orchestra
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Csound-users mailing list
> Csound-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-users
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

------------------------------------------------------------------------------
_______________________________________________
Csound-users mailing list
Csound-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-users
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-08-22 15:09
Fromjpff
SubjectRe: [Cs-dev] dssiinit.csd - parsing error in manpage example
Moved to devel list......

I have started to mark in the manual the opcodes that need a plugin.  But 
if I do not build a particular plugin I do not know its name.  i would 
like a list of all plugin-opcodes but I do not read cmake well enoh

On Sat, 22 Aug 2015, Victor Lazzarini wrote:

> yes, these are for Linux.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
>> On 22 Aug 2015, at 13:57, jpff  wrote:
>>
>> Usual questions: platform? version?
>>
>> I suspect you are using OSx but dssi is a linux plugin format so probably
>> not built for OSX.  At least that would be my first guess
>>
>> ==John ff
>>
>>> On Sat, 22 Aug 2015, Dr. Richard Boulanger wrote:
>>>
>>>
>>> STARTING FILE
>>>
>>> Creating options
>>>
>>> Creating orchestra
>>>
>>> Creating score
>>>
>>> rtaudio: PortAudio module enabled ...
>>>
>>> using blocking interface
>>>
>>> error: syntax error, unexpected T_IDENT (token "dssiinit") from file/Library/Frameworks/CsoundLib64.framework/Resources/Manual/examples/dssiinit.
>>> csd (1)
>>>
>>> line 15:
>>>
>>>>>> gihandle dssiinit <<<
>>>
>>> Unexpected untyped word gihandle when expecting a variable
>>>
>>> Parsing failed due to invalid input!
>>>
>>> Stopping on parser failure
>>>
>>> cannot compile orchestra
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Csound-users mailing list
>> Csound-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-users
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Csound-users mailing list
> Csound-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-users
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2015-08-22 15:24
Fromjpff
SubjectRe: [Cs-dev] dssiinit.csd - parsing error in manpage example
nother way is to create dummy libraries for all plugins so the think will 
parse but just produce an error.  Or both approaches  Any views?
==John ff



------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2015-08-22 16:23
FromSteven Yi
SubjectRe: [Cs-dev] dssiinit.csd - parsing error in manpage example
AttachmentsNone  None  

Not on my computer at there moment, but I think you can grep for make_plugin to get the plugin library names. I'd prefer not having dummy libraries myself,as it won't address platforms where we don't have plugins (I.e. web, ios)


On Sat, Aug 22, 2015, 10:24 AM jpff <jpff@codemist.co.uk> wrote:
nother way is to create dummy libraries for all plugins so the think will
parse but just produce an error.  Or both approaches  Any views?
==John ff



------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

Date2015-08-22 16:49
FromMichael Gogins
SubjectRe: [Cs-dev] dssiinit.csd - parsing error in manpage example
I agree with Steven.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sat, Aug 22, 2015 at 11:23 AM, Steven Yi  wrote:
> Not on my computer at there moment, but I think you can grep for make_plugin
> to get the plugin library names. I'd prefer not having dummy libraries
> myself,as it won't address platforms where we don't have plugins (I.e. web,
> ios)
>
>
> On Sat, Aug 22, 2015, 10:24 AM jpff  wrote:
>>
>> nother way is to create dummy libraries for all plugins so the think will
>> parse but just produce an error.  Or both approaches  Any views?
>> ==John ff
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2015-08-23 08:53
FromOeyvind Brandtsegg
SubjectRe: [Cs-dev] dssiinit.csd - parsing error in manpage example
AttachmentsNone  None  

Would it be possible to have a dummy function, which is overridden upon succesful loading of a plugin? Should work also on platforms without plugins.

22. aug. 2015 17.24 skrev "Steven Yi" <stevenyi@gmail.com>:

Not on my computer at there moment, but I think you can grep for make_plugin to get the plugin library names. I'd prefer not having dummy libraries myself,as it won't address platforms where we don't have plugins (I.e. web, ios)


On Sat, Aug 22, 2015, 10:24 AM jpff <jpff@codemist.co.uk> wrote:
nother way is to create dummy libraries for all plugins so the think will
parse but just produce an error.  Or both approaches  Any views?
==John ff



------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------

_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel