Hello-
Is there an upper limit on score size?  It seems when my scores exceed
somewhere around 200,000 lines Csound gets stuck during "sorting score...".  
Thanks.
Kurt.

There is no internal limit;  however the score sorting method is not the
fastest and so a large score may lead to inordinate times -- and memory
use.
==John ff

PS If you want to send me the score privately I will take a deatiled look
to see is this is in reality a bug

>
> Hello-
> Is there an upper limit on score size?  It seems when my scores exceed
> somewhere around 200,000 lines Csound gets stuck during "sorting
> score...".
> Thanks.
> Kurt.
> --
> View this message in context:
> http://www.nabble.com/score-size-limit--tp25204238p25204238.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>




Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hey-
So it seems I simply didn't wait long enough.  Thanks anyways for the help
and quick response. I guess this leads me to another question... When
dealing with large scores, would the sorting go faster if created my .sco
files with the events already in chronological (I tend to create score
events instrument by instrument) order or does the sort time only depend on
the size of the .sco?  Also, might something like the Bash 'sort' command be
faster?
Thanks again.
Kurt

Normally, Csound preprocesses a .sco file to produce a temporary .srt
file, which is what actually drives the Csound performance. It's in
the same format as the .sco file, but in addition to being sorted and
having all "carry" fields filled in and macros expanded, the time and
duration fields each are duplicated. One each of the time and duration
fields is the original, and the other is "warped" by tempo changes. If
you run Csound with --keep-sorted-score, Csound will save the
preprocessed score as "score.srt."

I THINK -- but I'm not sure, the manual isn't completely unambiguous
-- that if you use a program to create a sorted .srt file in that
format, then the Csound command-line option -t N will cause Csound to
skip the .sco file and just use your .srt file instead, something like
this:

csound -o outfile.wav -t 60 my.orc my.srt

Hope this helps,
Mike



On 8/29/09, kCk  wrote:
>
> Hey-
> So it seems I simply didn't wait long enough.  Thanks anyways for the help
> and quick response. I guess this leads me to another question... When
> dealing with large scores, would the sorting go faster if created my .sco
> files with the events already in chronological (I tend to create score
> events instrument by instrument) order or does the sort time only depend on
> the size of the .sco?  Also, might something like the Bash 'sort' command be
> faster?
> Thanks again.
> Kurt
> --
> View this message in context:
> http://www.nabble.com/score-size-limit--tp25204238p25206170.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>