Thanks to everybody

and thanks Tobiah for the help. I finally openned the sound sample as
you said with a text editor, and looked for the copyright chunk. It
wasn't there. I found other chunks such as FORM, which is in most of my
samples and i don't think it's the cause of them clicks! But most
probably the problem is the sample itself!
    And as J.M Darremont suggested i tried out diskin.  The problem
disappeared!!!
  So i suppose, transposing with loscil in stereo produces sometimes
clicks depending on the sample??? The sample was transposed about 1
octave lower! and the clicks were always on the right channel and about
1 to 3 samples out of range!
Anyhow as i'm concerned i will use  diskin instead, but hope that the
problem with loscil will be elucidated.
    As Matt Ingals said, it might be a problem of Ram/File size/ Os.
Well, here i'm working with Macos, with plenty of Ram, and the sample
size is but 1 mega big. I say this because i have used other samples
bigger than that, and without problems.

    Maybe this clipping is a problem of phase while transposing certain
sounds???
I'm no SIgnal Processing Guru(SPG! :-), i might be saying nonsense???

    Anyhow thanks to everybody who helped me out, and showed me new
things!

    karim

>   So i suppose, transposing with loscil in stereo produces sometimes
> clicks depending on the sample??? The sample was transposed about 1
> octave lower! and the clicks were always on the right channel and about
> 1 to 3 samples out of range!

sounds like a legit bug to me.  i would guess loscil does this always and
only certain samples are more noticeable.

>     As Matt Ingals said, it might be a problem of Ram/File size/ Os.
> Well, here i'm working with Macos, with plenty of Ram, and the sample

i wasnt saying there was a problem with ram, just that with large files
you cant use loscil (at least on MacOs - and i would guess stressing
virtual memory on other OSs like this might not be the greatest thing
either)- on the other hand with short samples things may be faster loading
entire sample into ram.

soundin/diskin/etc of course have its own internal buffer in memory
anyway, so i was thinking ideally it would be cool to have just one ugen
that handles lookup-kind-of-things and does all the memory/file management
for you - so you dont have to worry where the contents came from (a file,
gen statement, etc) nor how big or sample rate or nchnls or  power of 2s
or whatever...


-matt