Hello,

i'm trying out this example from the manual but it outputs only zero volume.
Can someone please try out this example?
In the original example there is talk about "clarinet.sdif" but i did not
find that anywhere, so i took "clarinet.ctest.sdif" from Loris itself. This
SDIF file is checked in SPEAR and works. 
This is  "clarinet.ctest.sdif": 
http://old.nabble.com/file/p28866735/clarinet.ctest.sdif clarinet.ctest.sdif 
I could not run Lorisplay in Windows because it is not included. So I tried
in Linux.


; tryit.csd - a Csound structured data file 
; for testing the Loris unit generators
-odac           -iadc     -d     ;;;RT audio I/O
; To try this out, copy flute and clarinet
; SDIF files from the test directory into
; this directory, naming them flute.sdif
; and clarinet.sdif.
;




; originally tryit.orc
sr = 44100
kr = 4410
ksmps = 10
nchnls = 1

; 
; Play the partials in clarinet.sdif 
; from 0 to 3 sec with 1 ms fadetime 
; and no frequency , amplitude, or 
; bandwidth modification.
;
instr 1
    ktime    linseg      0, p3, 3.0    ; linear time function from 0 to 3
seconds
             lorisread   ktime, "clarinet.ctest.sdif", 1, 1, 1, 1, .001
    asig     lorisplay   1, 1, 1, 1
             out         asig
endin


; 
; Play the partials in clarinet.sdif 
; from 0 to 3 sec with 1 ms fadetime 
; adding tuning and vibrato, increasing the 
; "breathiness" (noisiness) and overall
; amplitude, and adding a highpass filter.
;
instr 2
    ktime    linseg      0, p3, 3.0    ; linear time function from 0 to 3
seconds
    
    ; compute frequency scale for tuning
    ; (original pitch was G#4)
    ifscale  =           cpspch(p4)/cpspch(8.08)

    ; make a vibrato envelope
    kvenv    linseg      0, p3/6, 0, p3/6, .02, p3/3, .02, p3/6, 0, p3/6, 0
    kvib     oscil       kvenv, 4, 1   ; table 1, sinusoid

    kbwenv   linseg      1, p3/6, 1, p3/6, 2, 2*p3/3, 2
             lorisread   ktime, "clarinet.ctest.sdif", 1, 1, 1, 1, .001
    a1       lorisplay   1, ifscale+kvib, 2, kbwenv  
    a2       atone       a1, 1000      ; highpass filter, cutoff 1000 Hz
             out         a2
endin


instr 3
	idur = p3		; duration of instrument play
	ipitch = cpspch(p4) ; pitch to play
	
	ifscale = ipitch/415	; the original fundamental was about 415 Hz
	ifadetime = 0.001 	; a fadetime of 1 ms (same as Loris) will be used
	
	; make a time index signal
	ktime linseg	0.15, idur/4, 1.8, idur/4, .8, idur/2, 2.3
	
	; make a vibrato envelope
	kvenv linseg	0, idur/6, 0, idur/2, .02, idur/3, 0
	kvib oscil		kvenv, 4, 1		; table 1, sinusoid

             lorisread   ktime, "clarinet.ctest.sdif", 1, 1, 1, 1, ifadetime
	a1 lorisplay 1, ifscale+kvib, 2, 1  

	a2 atone a1, 1000  
	out a2
endin



; originally tryit.sco
; make sinusoid in table 1
f 1 0 4096 10 1

; play instr 1
;     strt   dur
i 1    0      3
i 1    +      1
i 1    +      6
s

; play instr 2
;     strt   dur   ptch
i 2     1     3    8.08
i 2     3.5   1    8.04
i 2     4     6    8.00
i 2     4     6    8.07

e




This example has run on Ubuntu10.04 64bit, Csound 2.12 double precision
greetings,
Menno

Just a guess - maybe try setting 0dbfs to 1.

P

On 12 Jun 2010, at 19:54, menno wrote:

>
> Hello,
>
> i'm trying out this example from the manual but it outputs only zero  
> volume.
> Can someone please try out this example?
> In the original example there is talk about "clarinet.sdif" but i  
> did not
> find that anywhere, so i took "clarinet.ctest.sdif" from Loris  
> itself. This
> SDIF file is checked in SPEAR and works.
> This is  "clarinet.ctest.sdif":
> http://old.nabble.com/file/p28866735/clarinet.ctest.sdif  
> clarinet.ctest.sdif
> I could not run Lorisplay in Windows because it is not included. So  
> I tried
> in Linux.
>
> 
> ; tryit.csd - a Csound structured data file
> ; for testing the Loris unit generators
> -odac           -iadc     -d     ;;;RT audio I/O
> ; To try this out, copy flute and clarinet
> ; SDIF files from the test directory into
> ; this directory, naming them flute.sdif
> ; and clarinet.sdif.
> ;
> 
>
> 
> 
> ; originally tryit.orc
> sr = 44100
> kr = 4410
> ksmps = 10
> nchnls = 1
>
> ;
> ; Play the partials in clarinet.sdif
> ; from 0 to 3 sec with 1 ms fadetime
> ; and no frequency , amplitude, or
> ; bandwidth modification.
> ;
> instr 1
>    ktime    linseg      0, p3, 3.0    ; linear time function from 0  
> to 3
> seconds
>             lorisread   ktime, "clarinet.ctest.sdif", 1, 1, 1, 1, .001
>    asig     lorisplay   1, 1, 1, 1
>             out         asig
> endin
>
>
> ;
> ; Play the partials in clarinet.sdif
> ; from 0 to 3 sec with 1 ms fadetime
> ; adding tuning and vibrato, increasing the
> ; "breathiness" (noisiness) and overall
> ; amplitude, and adding a highpass filter.
> ;
> instr 2
>    ktime    linseg      0, p3, 3.0    ; linear time function from 0  
> to 3
> seconds
>
>    ; compute frequency scale for tuning
>    ; (original pitch was G#4)
>    ifscale  =           cpspch(p4)/cpspch(8.08)
>
>    ; make a vibrato envelope
>    kvenv    linseg      0, p3/6, 0, p3/6, .02, p3/3, .02, p3/6, 0,  
> p3/6, 0
>    kvib     oscil       kvenv, 4, 1   ; table 1, sinusoid
>
>    kbwenv   linseg      1, p3/6, 1, p3/6, 2, 2*p3/3, 2
>             lorisread   ktime, "clarinet.ctest.sdif", 1, 1, 1, 1, .001
>    a1       lorisplay   1, ifscale+kvib, 2, kbwenv
>    a2       atone       a1, 1000      ; highpass filter, cutoff 1000  
> Hz
>             out         a2
> endin
>
>
> instr 3
> 	idur = p3		; duration of instrument play
> 	ipitch = cpspch(p4) ; pitch to play
> 	
> 	ifscale = ipitch/415	; the original fundamental was about 415 Hz
> 	ifadetime = 0.001 	; a fadetime of 1 ms (same as Loris) will be used
> 	
> 	; make a time index signal
> 	ktime linseg	0.15, idur/4, 1.8, idur/4, .8, idur/2, 2.3
> 	
> 	; make a vibrato envelope
> 	kvenv linseg	0, idur/6, 0, idur/2, .02, idur/3, 0
> 	kvib oscil		kvenv, 4, 1		; table 1, sinusoid
>
>             lorisread   ktime, "clarinet.ctest.sdif", 1, 1, 1, 1,  
> ifadetime
> 	a1 lorisplay 1, ifscale+kvib, 2, 1
>
> 	a2 atone a1, 1000
> 	out a2
> endin
>
> 
> 
> ; originally tryit.sco
> ; make sinusoid in table 1
> f 1 0 4096 10 1
>
> ; play instr 1
> ;     strt   dur
> i 1    0      3
> i 1    +      1
> i 1    +      6
> s
>
> ; play instr 2
> ;     strt   dur   ptch
> i 2     1     3    8.08
> i 2     3.5   1    8.04
> i 2     4     6    8.00
> i 2     4     6    8.07
>
> e
> 
>
> 
>
> This example has run on Ubuntu10.04 64bit, Csound 2.12 double  
> precision
> greetings,
> Menno
>
> -- 
> View this message in context: http://old.nabble.com/lorisplay-tp28866735p28866735.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

nope - sorry :)

B  0.000 ..  3.000 T  3.000 TT  3.000 M:  0.00000
B  3.000 ..  4.000 T  4.000 TT  4.000 M:  0.00000
B  4.000 .. 10.000 T 10.000 TT 10.000 M:  0.00000
end of section 1	 sect peak amps:  0.00000
inactive allocs returned to freespace
SECTION 2:
B  0.000 ..  1.000 T  1.000 TT 11.000 M:  0.00000
new alloc for instr 2:
B  1.000 ..  3.500 T  3.500 TT 13.500 M:  0.00000
new alloc for instr 2:
B  3.500 ..  4.000 T  4.000 TT 14.000 M:  0.00000
new alloc for instr 2:
B  4.000 ..  4.500 T  4.500 TT 14.500 M:  0.00000
B  4.500 .. 10.000 T 10.000 TT 20.000 M:  0.00000
end of section 2	 sect peak amps:  0.00000

Maybe there is a float/double incompatibility between the SDIF file  
and your csound build?


On 12 Jun 2010, at 20:19, menno wrote:

>
> nope - sorry :)
>
> B  0.000 ..  3.000 T  3.000 TT  3.000 M:  0.00000
> B  3.000 ..  4.000 T  4.000 TT  4.000 M:  0.00000
> B  4.000 .. 10.000 T 10.000 TT 10.000 M:  0.00000
> end of section 1	 sect peak amps:  0.00000
> inactive allocs returned to freespace
> SECTION 2:
> B  0.000 ..  1.000 T  1.000 TT 11.000 M:  0.00000
> new alloc for instr 2:
> B  1.000 ..  3.500 T  3.500 TT 13.500 M:  0.00000
> new alloc for instr 2:
> B  3.500 ..  4.000 T  4.000 TT 14.000 M:  0.00000
> new alloc for instr 2:
> B  4.000 ..  4.500 T  4.500 TT 14.500 M:  0.00000
> B  4.500 .. 10.000 T 10.000 TT 20.000 M:  0.00000
> end of section 2	 sect peak amps:  0.00000
>
>
>
> -- 
> View this message in context: http://old.nabble.com/lorisplay-tp28866735p28866842.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Djack wrote:
> 
> I understand, thanks for your answer.
> but in that case why not to write this information in the csound manual.
> It is written that Loris opcodes are an optional component of Csound5,
> just adding " not maintained opcodes, use at your own risk..:)
> 
> Just to prevent users to invest to much time on it.
> 

i think it has to do with the fact that Csound and it contributions are so
"open" for everyone in the way that there is no real leader and a policy as
one can see with closed source and commercial software. In csound people
that feel that new opcodes are needed just create them and give them to the
Csound community. And that is great! The diversity of ideas created this way
is a nice thing about Csound but it may happen that the creator of these
particular new opcodes does not feel that he has to maintain these opcodes
for the rest of his life. So at some point the opcodes  might not work
anymore because the world around them has changed and the opcode didn't
change with it.
I realize this is becoming Off Topic so i return to the CSound Loris
opcodes:
if the function of the Loris opcodes has become obsolete and the same
results can be achieved with the PVS opcodes than Loris can be removed from
Csound to avoid any further noise?? Can they replaced by PVS?

Menno

Well, yes and no. The functionality may be replaced, but it's not the  
same process and the algorithms are different, so Loris will be an  
alternative to pvs, as the ATS opcodes are. But the difference between  
Loris and ATS is that while the former is in csound and has been  
maintained as part of it, Loris is not. Maybe we should look into  
moving the last working Loris sources into Csound so that we can  
maintain it? The Loris opcodes, as far as I know, were written by the  
Loris developers a long time ago and they are not maintaining the  
Loris lib anymore (or are they?).

Victor

On 13 Jun 2010, at 08:55, menno wrote:

> if the function of the Loris opcodes has become obsolete and the same
> results can be achieved with the PVS opcodes than Loris can be  
> removed from
> Csound to avoid any further noise?? Can they replaced by PVS?
>
> Menno



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

On sourceforge th eloris files were last  changed a coupl eof months ago. 
So still some life
==John ff

 Well, yes and no. The functionality may be replaced, but it's not the
> same process and the algorithms are different, so Loris will be an
> alternative to pvs, as the ATS opcodes are. But the difference between
> Loris and ATS is that while the former is in csound and has been
> maintained as part of it, Loris is not. Maybe we should look into
> moving the last working Loris sources into Csound so that we can
> maintain it? The Loris opcodes, as far as I know, were written by the
> Loris developers a long time ago and they are not maintaining the
> Loris lib anymore (or are they?).
>
> Victor
>
> On 13 Jun 2010, at 08:55, menno wrote:
>
>> if the function of the Loris opcodes has become obsolete and the same
>> results can be achieved with the PVS opcodes than Loris can be
>> removed from
>> Csound to avoid any further noise?? Can they replaced by PVS?
>>
>> Menno
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>
>




Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I'm wrong here. Their sourceforge site seems to be active alright. We  
can't add the sources to Csound because they are GPL.
I should stop talking about stuff I don't know about...

Victor

On 13 Jun 2010, at 09:09, Victor Lazzarini wrote:

> Well, yes and no. The functionality may be replaced, but it's not  
> the same process and the algorithms are different, so Loris will be  
> an alternative to pvs, as the ATS opcodes are. But the difference  
> between Loris and ATS is that while the former is in csound and has  
> been maintained as part of it, Loris is not. Maybe we should look  
> into moving the last working Loris sources into Csound so that we  
> can maintain it? The Loris opcodes, as far as I know, were written  
> by the Loris developers a long time ago and they are not maintaining  
> the Loris lib anymore (or are they?).
>
> Victor
>
> On 13 Jun 2010, at 08:55, menno wrote:
>
>> if the function of the Loris opcodes has become obsolete and the same
>> results can be achieved with the PVS opcodes than Loris can be  
>> removed from
>> Csound to avoid any further noise?? Can they replaced by PVS?
>>
>> Menno
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"