[Csnd] v 5.16/17 issue
Date | 2012-03-24 23:23 |
From | Jason Lim |
Subject | [Csnd] v 5.16/17 issue |
Hello people, Not sure what I have going wrong here. I have a .csd which will run on one machine but not another. I have been polishing off a note list composition which has been my focus for the last fortnight. I have been working out of town on my macbook, which is running Csound v5.13 with CsoundQT version 0.6.1 (I've not wanted to 'fix-what-ain't-broke'. This setup has worked very reliably for a while so have not updated for a while). My main desktop is an iMac OSX 10.7.3 which I have been running 5.16 (and as of this evening 5.17). When I transfered my composition's .csd to my desktop I cannot get it to run. The console greets me with: "Internal error in print_input_backtrace()" Is this significant? The result has been the same before and after installing 5.17 Is there something I'm missing, bringing a file written with .13 to .17? This also appears just before the error in the console: "sread: illegal opcode * section 4: at position 0" It also appears in the console when running the .csd on my macbook, in which case it compiles with no problems. Any suggestions as to the issue here before I do some drastic reinstalls? Thanks for reading best Jason |
Date | 2012-03-26 14:10 |
From | jpff@cs.bath.ac.uk |
Subject | Re: [Csnd] v 5.16/17 issue |
> > I have been polishing off a note list composition which has been my focus > for the last fortnight. I have been working out of town on my macbook, > which is running Csound v5.13 with CsoundQT version 0.6.1 (I've not wanted > to 'fix-what-ain't-broke'. This setup has worked very reliably for a > while so have not updated for a while). > > My main desktop is an iMac OSX 10.7.3 which I have been running 5.16 (and > as of this evening 5.17). > When I transfered my composition's .csd to my desktop I cannot get it to > run. The console greets me with: > > "Internal error in print_input_backtrace()" > That message seems to come from a score error not in a macro but this code has not changed since ~2008 > Is this significant? The result has been the same before and after > installing 5.17 > Is there something I'm missing, bringing a file written with .13 to .17? > > This also appears just before the error in the console: > > "sread: illegal opcode * > section 4: at position 0" > That looks more important. There is a * in your score at the start of a line in the fourth section. So your first call should be to look for that We really do need to take a glance at the score or better .csd Or locate the section that causes the messages ==John ff |
Date | 2012-03-27 16:20 |
From | Jason Lim |
Subject | Re: [Csnd] v 5.16/17 issue |
Thank you both for your prompt replies. Problem is solved. Dr B debugged it in class yesterday. Turned out I had a rogue value after a linenr which, as Victor suggested, was tolerated in the earlier version but not in .16/17. I'm going to tidy up some transitions and then submit it to the podcast to share soon. Thanks again -Jason |