[Csnd] Samples out of range
| Date | 2009-12-06 17:13 |
| From | Siobhán Maher |
| Subject | [Csnd] Samples out of range |
just wondering...
in my comand prompt window i ran a .csd file-it said i had no errors in the performance but there were 117220 samples out of range...could anyone please explain what this means
and how to go about fixing it if it needs to be fixed? Thanks Siobhán |
| Date | 2009-12-06 17:28 |
| From | jpff@cs.bath.ac.uk |
| Subject | [Csnd] Re: Samples out of range |
> just wondering... > > in my comand prompt window i ran a .csd file-it said i had no errors in > the > performance but there were 117220 samples out of range...could anyone > please > explain what this means > and how to go about fixing it if it needs to be fixed? > Samples out of range means that the ampltude is too high for those moments. SO either resule amplitude, or render to floating point and i=use the scale utility. This is not normally considered an error as a few out-of-range samples hardly matter. I woul dbe anoyed if everything stipped after 1 such! Try setting a global irate variable top 1.0 and mumtipole all output signals by it. Then if out of range, reduce the initial setting. ==JOhn ff Send bugs reports to this list. To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |
| Date | 2009-12-06 17:32 |
| From | Victor Lazzarini |
| Subject | [Csnd] Re: Samples out of range |
Very loud amplitudes, going beyond the allowed range. Clipping and distortion can occur. On 6 Dec 2009, at 17:13, Siobhán Maher wrote: > just wondering... > > in my comand prompt window i ran a .csd file-it said i had no errors > in the performance but there were 117220 samples out of > range...could anyone please explain what this means > and how to go about fixing it if it needs to be fixed? > > Thanks > > Siobhán Send bugs reports to this list. To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |
| Date | 2009-12-06 17:36 |
| From | Siobhán Maher |
| Subject | [Csnd] Re: Re: Samples out of range |
so after reading these messages and finding out that it was to do with amplitude i opened the .wav file in audacity and the file had indeed clipped. so the amplitude values must be too high.
thanks! 2009/12/6 Victor Lazzarini <Victor.Lazzarini@nuim.ie> Very loud amplitudes, going beyond the allowed range. Clipping and distortion can occur. |
| Date | 2009-12-06 18:11 |
| From | Richard Dobson |
| Subject | [Csnd] Re: Re: Samples out of range |
You need to read the running output messages as the csd is processed;
these report the peak sample values for each audio block as they are
computed, so you will be able to see just how overrange they are, and
(if the csd is of any complexity) at what time(s) they are being generated.
A quick'n'dirty solution is to find the output statement ("out asig " or
"outs asig1,asig2..." etc, where 'asig" stands for whatever you have
there) and multiply the signal variables at that point by some
sufficiently small value (perhaps start with 0.1 and see what the
difference is). This will create a soundfile that can be played and
displayed, and thus you can see exactly where things are overrange. You
would then go back to your csd file and modify instrument code as
necessary.
Audio can go overrange very easily in Csound, as it is far too general a
system to provide any sort of automatic adjustment. Add ten
full-amplitude signals together, and the result is an output signal
overrange by the same factor of ten.
Also note that (if reasonably short - say about a page) it is OK to post
the csd code to the list, so we can see exactly what is going on. If the
file is larger, post a link to it so people can download it. People here
are very good at investigating such files and reporting back. We have
all been there!
Richard Dobson
Victor Lazzarini wrote:
> Very loud amplitudes, going beyond the allowed range. Clipping and
> distortion can occur.
>
> On 6 Dec 2009, at 17:13, Siobhán Maher wrote:
>
>> just wondering...
>>
>> in my comand prompt window i ran a .csd file-it said i had no errors
>> in the performance but there were 117220 samples out of range...could
>> anyone please explain what this means
>> and how to go about fixing it if it needs to be fixed?
>>
>> Thanks
>>
>> Siobhán
>
>
>
> 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" |
| Date | 2009-12-06 18:16 |
| From | Siobhán Maher |
| Subject | [Csnd] Re: Re: Re: Samples out of range |
thanks for your reply richard...i shall bear it in mind for future reference! i never actually knew what the samples out of range thing meant but now i do it makes it easier to know how to go about fixing it! plus all these tips you guys are giving, samples out of range shall be a problem no longer! *fingers crossed*
i actually figured the problem out-i'd messed the envelope i had made up putting the wrong things in the wrong places and once i'd fixed that the samples out of range problem disappeared! thank you all for the help! i keep making silly mistakes but that's learning for you! :) 2009/12/6 Richard Dobson <richarddobson@blueyonder.co.uk> You need to read the running output messages as the csd is processed; these report the peak sample values for each audio block as they are computed, so you will be able to see just how overrange they are, and (if the csd is of any complexity) at what time(s) they are being generated. |