Csound Csound-dev Csound-tekno Search About

error messages...? Did something change?

Date2015-12-05 09:33
FromRory Walsh
Subjecterror messages...? Did something change?
Is it just me, or has something changed in the way Csound reports errors? I find myself constantly having to scroll up in the terminal window to see errors in the latest version. Or am I dreaming? Here's an example. Could the errors be printed last so that they can easily be seen?

virtual_keyboard real time MIDI plugin for Csound
0dBFS level = 32768.0
Csound version 6.07 (double samples) Nov 16 2015
libsndfile-1.0.25
UnifiedCSD:  ../Linux/build/test.csd
STARTING FILE
Creating options
Creating orchestra
Creating score
rtmidi: ALSA Raw MIDI module enabled
rtaudio: JACK module enabled
LINE: 46

error: syntax error, unexpected NEWLINE, expecting ',' or ')'  (token "
") from file ../Linux/build/test.csd (1)
 line 46:
>>>kShuffle init metro 0.11  <<<
Parsing failed due to invalid input!
Stopping on parser failure
cannot compile orchestra
sorting score ...
    ... done
--Csound version 6.07 (double samples) Nov 16 2015
displays suppressed
0dBFS level = 32768.0
orch now loaded
audio buffered in 256 sample-frame blocks
system sr: 44100.000000
 0: dac:system:playback_ (system:playback_)
writing 256 sample blks of 64-bit floats to dac
SECTION 1:
      B  1.000 - note deleted. instr 1(200) undefined
Score finished in csoundPerform().
inactive allocs returned to freespace
end of score.           overall amps:      0.0
       overall samples out of range:        0
2 errors in performance
173 256 sample blks of 64-bit floats written to dac
rory@rory-linux-pc:~/sourcecode/cabbageaudio/cabbage/Builds/Android$

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-12-05 10:54
FromVictor Lazzarini
SubjectRe: error messages...? Did something change?
I have not noticed this here. With the latest code:

ligeti:debug victor$ ./csound ~/csound/matest.csd 
time resolution is 1000.000 ns
virtual_keyboard real time MIDI plugin for Csound
WARNING: STK opcodes not available: define environment variable RAWWAVE_PATH
(points to rawwaves directory) to use STK opcodes.
0dBFS level = 32768.0
Csound version 6.07 beta (double samples) Dec  5 2015
libsndfile-1.0.25
UnifiedCSD:  /Users/victor/csound/matest.csd
Calling unified file system4
STARTING FILE
Creating options
Creating orchestra
Creating score
WARNING: STK opcodes not available: define environment variable RAWWAVE_PATH
(points to rawwaves directory) to use STK opcodes.
rtaudio: PortAudio module enabled ... 
using callback interface
rtmidi: PortMIDI module enabled
LINE: 10

error: syntax error, unexpected T_IDENT  (token "s") from file /Users/victor/csound/matest.csd (1)
 line 10:
>>>i2 = 0s <<<
Parsing failed due to invalid input!
Stopping on parser failure
cannot compile orchestra
end of score.		   overall amps:      0.0
	   overall samples out of range:        0
1 errors in performance
Elapsed time at end of performance: real: 0.002s, CPU: 0.002s



========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 5 Dec 2015, at 09:33, Rory Walsh  wrote:
> 
> Is it just me, or has something changed in the way Csound reports errors? I find myself constantly having to scroll up in the terminal window to see errors in the latest version. Or am I dreaming? Here's an example. Could the errors be printed last so that they can easily be seen? 
> 
> virtual_keyboard real time MIDI plugin for Csound
> 0dBFS level = 32768.0
> Csound version 6.07 (double samples) Nov 16 2015
> libsndfile-1.0.25
> UnifiedCSD:  ../Linux/build/test.csd
> STARTING FILE
> Creating options
> Creating orchestra
> Creating score
> rtmidi: ALSA Raw MIDI module enabled
> rtaudio: JACK module enabled
> LINE: 46
> 
> error: syntax error, unexpected NEWLINE, expecting ',' or ')'  (token "
> ") from file ../Linux/build/test.csd (1)
>  line 46:
> >>>kShuffle init metro 0.11  <<<
> Parsing failed due to invalid input!
> Stopping on parser failure
> cannot compile orchestra
> sorting score ...
>     ... done
> --Csound version 6.07 (double samples) Nov 16 2015
> displays suppressed
> 0dBFS level = 32768.0
> orch now loaded
> audio buffered in 256 sample-frame blocks
> system sr: 44100.000000
>  0: dac:system:playback_ (system:playback_)
> writing 256 sample blks of 64-bit floats to dac 
> SECTION 1:
>       B  1.000 - note deleted. instr 1(200) undefined
> Score finished in csoundPerform().
> inactive allocs returned to freespace
> end of score.           overall amps:      0.0
>        overall samples out of range:        0
> 2 errors in performance
> 173 256 sample blks of 64-bit floats written to dac
> rory@rory-linux-pc:~/sourcecode/cabbageaudio/cabbage/Builds/Android$ 
> 
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2015-12-05 11:35
FromRory Walsh
SubjectRe: error messages...? Did something change?
A fresh pull and rebuild did the trick. It's strange, I noticed it on Windows too. Perhaps I should stick with the master branch from now on. I must have got caught in a commit-warp! 

On 5 December 2015 at 10:54, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:
I have not noticed this here. With the latest code:

ligeti:debug victor$ ./csound ~/csound/matest.csd
time resolution is 1000.000 ns
virtual_keyboard real time MIDI plugin for Csound
WARNING: STK opcodes not available: define environment variable RAWWAVE_PATH
(points to rawwaves directory) to use STK opcodes.
0dBFS level = 32768.0
Csound version 6.07 beta (double samples) Dec  5 2015
libsndfile-1.0.25
UnifiedCSD:  /Users/victor/csound/matest.csd
Calling unified file system4
STARTING FILE
Creating options
Creating orchestra
Creating score
WARNING: STK opcodes not available: define environment variable RAWWAVE_PATH
(points to rawwaves directory) to use STK opcodes.
rtaudio: PortAudio module enabled ...
using callback interface
rtmidi: PortMIDI module enabled
LINE: 10

error: syntax error, unexpected T_IDENT  (token "s") from file /Users/victor/csound/matest.csd (1)
 line 10:
>>>i2 = 0s <<<
Parsing failed due to invalid input!
Stopping on parser failure
cannot compile orchestra
end of score.              overall amps:      0.0
           overall samples out of range:        0
1 errors in performance
Elapsed time at end of performance: real: 0.002s, CPU: 0.002s



========================
Dr Victor Lazzarini
Dean of Arts, Celtic Studies and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

> On 5 Dec 2015, at 09:33, Rory Walsh <rorywalsh@ear.ie> wrote:
>
> Is it just me, or has something changed in the way Csound reports errors? I find myself constantly having to scroll up in the terminal window to see errors in the latest version. Or am I dreaming? Here's an example. Could the errors be printed last so that they can easily be seen?
>
> virtual_keyboard real time MIDI plugin for Csound
> 0dBFS level = 32768.0
> Csound version 6.07 (double samples) Nov 16 2015
> libsndfile-1.0.25
> UnifiedCSD:  ../Linux/build/test.csd
> STARTING FILE
> Creating options
> Creating orchestra
> Creating score
> rtmidi: ALSA Raw MIDI module enabled
> rtaudio: JACK module enabled
> LINE: 46
>
> error: syntax error, unexpected NEWLINE, expecting ',' or ')'  (token "
> ") from file ../Linux/build/test.csd (1)
>  line 46:
> >>>kShuffle init metro 0.11  <<<
> Parsing failed due to invalid input!
> Stopping on parser failure
> cannot compile orchestra
> sorting score ...
>     ... done
> --Csound version 6.07 (double samples) Nov 16 2015
> displays suppressed
> 0dBFS level = 32768.0
> orch now loaded
> audio buffered in 256 sample-frame blocks
> system sr: 44100.000000
>  0: dac:system:playback_ (system:playback_)
> writing 256 sample blks of 64-bit floats to dac
> SECTION 1:
>       B  1.000 - note deleted. instr 1(200) undefined
> Score finished in csoundPerform().
> inactive allocs returned to freespace
> end of score.           overall amps:      0.0
>        overall samples out of range:        0
> 2 errors in performance
> 173 256 sample blks of 64-bit floats written to dac
> rory@rory-linux-pc:~/sourcecode/cabbageaudio/cabbage/Builds/Android$
>
> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2015-12-06 18:39
FromTarmo Johannes
SubjectRe: error messages...? Did something change?

Thanks for the hint!

 

I had complained about the problem, too. Indeed,

 

git pull

sudo make unistall

make clean

make

sudo make install

 

solved the problem.

 

I am mostly too lazy to do the clean step, but now it really helped.

I definitely stick to the develop branch - it always has worked for me and has the most recent fixes.

 

Best!

tarmo

 

On Saturday 05 December 2015 11:35:18 you wrote:

> A fresh pull and rebuild did the trick. It's strange, I noticed it on

> Windows too. Perhaps I should stick with the master branch from now on. I

> must have got caught in a commit-warp!

>

> On 5 December 2015 at 10:54, Victor Lazzarini <Victor.Lazzarini@nuim.ie>

>

> wrote:

> > I have not noticed this here. With the latest code:

> >

> > ligeti:debug victor$ ./csound ~/csound/matest.csd

> > time resolution is 1000.000 ns

> > virtual_keyboard real time MIDI plugin for Csound

> > WARNING: STK opcodes not available: define environment variable

> > RAWWAVE_PATH

> > (points to rawwaves directory) to use STK opcodes.

> > 0dBFS level = 32768.0

> > Csound version 6.07 beta (double samples) Dec 5 2015

> > libsndfile-1.0.25

> > UnifiedCSD: /Users/victor/csound/matest.csd

> > Calling unified file system4

> > STARTING FILE

> > Creating options

> > Creating orchestra

> > Creating score

> > WARNING: STK opcodes not available: define environment variable

> > RAWWAVE_PATH

> > (points to rawwaves directory) to use STK opcodes.

> > rtaudio: PortAudio module enabled ...

> > using callback interface

> > rtmidi: PortMIDI module enabled

> > LINE: 10

> >

> > error: syntax error, unexpected T_IDENT (token "s") from file

> > /Users/victor/csound/matest.csd (1)

> >

> > line 10:

> > >>>i2 = 0s <<<

> >

> > Parsing failed due to invalid input!

> > Stopping on parser failure

> > cannot compile orchestra

> > end of score. overall amps: 0.0

> >

> > overall samples out of range: 0

> >

> > 1 errors in performance

> > Elapsed time at end of performance: real: 0.002s, CPU: 0.002s

> >

> >

> >

> > ========================

> > Dr Victor Lazzarini

> > Dean of Arts, Celtic Studies and Philosophy,

> > Maynooth University,

> > Maynooth, Co Kildare, Ireland

> > Tel: 00 353 7086936

> > Fax: 00 353 1 7086952

> >

> > > On 5 Dec 2015, at 09:33, Rory Walsh <rorywalsh@ear.ie> wrote:

> > >

> > > Is it just me, or has something changed in the way Csound reports

> >

> > errors? I find myself constantly having to scroll up in the terminal

> > window

> > to see errors in the latest version. Or am I dreaming? Here's an example.

> > Could the errors be printed last so that they can easily be seen?

> >

> > > virtual_keyboard real time MIDI plugin for Csound

> > > 0dBFS level = 32768.0

> > > Csound version 6.07 (double samples) Nov 16 2015

> > > libsndfile-1.0.25

> > > UnifiedCSD: ../Linux/build/test.csd

> > > STARTING FILE

> > > Creating options

> > > Creating orchestra

> > > Creating score

> > > rtmidi: ALSA Raw MIDI module enabled

> > > rtaudio: JACK module enabled

> > > LINE: 46

> > >

> > > error: syntax error, unexpected NEWLINE, expecting ',' or ')' (token "

> > > ") from file ../Linux/build/test.csd (1)

> > >

> > > line 46:

> > > >>>kShuffle init metro 0.11 <<<

> > >

> > > Parsing failed due to invalid input!

> > > Stopping on parser failure

> > > cannot compile orchestra

> > > sorting score ...

> > >

> > > ... done

> > >

> > > --Csound version 6.07 (double samples) Nov 16 2015

> > > displays suppressed

> > > 0dBFS level = 32768.0

> > > orch now loaded

> > > audio buffered in 256 sample-frame blocks

> > > system sr: 44100.000000

> > >

> > > 0: dac:system:playback_ (system:playback_)

> > >

> > > writing 256 sample blks of 64-bit floats to dac

> > >

> > > SECTION 1:

> > > B 1.000 - note deleted. instr 1(200) undefined

> > >

> > > Score finished in csoundPerform().

> > > inactive allocs returned to freespace

> > > end of score. overall amps: 0.0

> > >

> > > overall samples out of range: 0

> > >

> > > 2 errors in performance

> > > 173 256 sample blks of 64-bit floats written to dac

> > > rory@rory-linux-pc:~/sourcecode/cabbageaudio/cabbage/Builds/Android$

> > >

> > > Csound mailing list Csound@listserv.heanet.ie

> >

> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to

> > https://github.com/csound/csound/issues Discussions of bugs and features

> > can be posted here

> >

> > Csound mailing list

> > Csound@listserv.heanet.ie

> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> > Send bugs reports to

> >

> > https://github.com/csound/csound/issues

> >

> > Discussions of bugs and features can be posted here

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here