Csound Csound-dev Csound-tekno Search About

[Cs-dev] bug in m/n statement

Date2007-11-13 11:17
Fromkroger.lists@gmail.com (Pedro =?utf-8?Q?Kr=C3=B6ger?=)
Subject[Cs-dev] bug in m/n statement
Hi Csounders,

I believe there is a bug in the m/n statement. It can be reproduced by
running the test orc/sco bellow:

----------------------------------------------------------------------
instr 1
  a1        oscil     10000,441,1
            out       a1
endin
----------------------------------------------------------------------
f1  0 1024  10    1  

i1  0  1
s               
m foo          
i1  0  1
s               
n foo
----------------------------------------------------------------------

Csound will print tons of messages like this:

Duplicate 0: foo (repeat.sco,65)
Duplicate 0: foo (repeat.sco,65)

(I suppose it enters in a infinite loop).

Best regards,

Pedro Kroger

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2007-11-13 20:20
FromAnthony Kozar
SubjectRe: [Cs-dev] bug in m/n statement
Hi Pedro,

Yes, I think this bug has been known for quite some time now (2 or 3
years!).  I believe that you can work around it by putting a blank line
after the m-statement.

Hopefully, someone (maybe me?) will find the time to look into fixing it.

Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://anthonykozar.net/

Pedro Kröger wrote on 11/13/07 6:17 AM:

> m foo          
> i1  0  1
> s               
> n foo
> ----------------------------------------------------------------------
> 
> Csound will print tons of messages like this:
> 
> Duplicate 0: foo (repeat.sco,65)
> Duplicate 0: foo (repeat.sco,65)
> 
> (I suppose it enters in a infinite loop).


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2007-11-13 23:54
Fromkroger.lists@gmail.com (Pedro =?utf-8?Q?Kr=C3=B6ger?=)
SubjectRe: [Cs-dev] bug in m/n statement
Anthony Kozar  writes:

> Yes, I think this bug has been known for quite some time now (2 or 3
> years!).  I believe that you can work around it by putting a blank line
> after the m-statement.

thanks for writing. Unfortunately the blank line trick doesn't seem to
work. Shouldn't we document long standing bugs like this somewhere? I
can send a patch to the documentation if you guys think it's relevant.
(I know, a patch to solve the problem is _much_ better, but it will
probably take much more time).

Pedro

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2007-11-18 01:58
FromAndres Cabrera
SubjectRe: [Cs-dev] bug in m/n statement
Hi Pedro,

All suggestions and patches to the docs are very welcome. I'm very slow
implementing changes right now, but take note of things to do them for
the next release.

Cheers,
Andrés

El mar, 13-11-2007 a las 20:54 -0300, Pedro Kröger escribió:
> Anthony Kozar  writes:
> 
> > Yes, I think this bug has been known for quite some time now (2 or 3
> > years!).  I believe that you can work around it by putting a blank line
> > after the m-statement.
> 
> thanks for writing. Unfortunately the blank line trick doesn't seem to
> work. Shouldn't we document long standing bugs like this somewhere? I
> can send a patch to the documentation if you guys think it's relevant.
> (I know, a patch to solve the problem is _much_ better, but it will
> probably take much more time).
> 
> Pedro
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cs