Is anything wrong with the starting values for the randomi/randomh  
opcodes?
Instead of starting anywhere between the lower and upper limit, they  
always start exactly at the lower limit.
This can be very annoying; for instance if you have a random frequency  
movement or a random panning movement, but it always starts at the  
same point (the lowest one).
An example is below; it shows also that the problem just exists for  
randomi and randomh. The non-interpolating and non-holding random  
opcode is ok.

	joachim




-n


seed 0
instr 1
ktimk timeinstk
kRdm random 400, 800
kRdmi randomi 400, 800, 1
kRdmh randomh 400, 800, 1
if ktimk == 1 then
printk 0, kRdm
printk 0, kRdmi
printk 0, kRdmh
endif
endin


r 5
i 1 0 .01




SECTION 2:
new alloc for instr 1:
i 1 time 0.00023: 517.29187
i 1 time 0.00023: 400.00000
i 1 time 0.00023: 400.00000
B 0.000 .. 0.010 T 0.010 TT 0.010 M: 0.0
end of section 2	 sect peak amps: 0.0
inactive allocs returned to freespace
SECTION 3:
new alloc for instr 1:
i 1 time 0.01020: 564.97852
i 1 time 0.01020: 400.00000
i 1 time 0.01020: 400.00000
B 0.000 .. 0.010 T 0.010 TT 0.020 M: 0.0
end of section 3	 sect peak amps: 0.0
inactive allocs returned to freespace
SECTION 4:
new alloc for instr 1:
i 1 time 0.02018: 453.33304
i 1 time 0.02018: 400.00000
i 1 time 0.02018: 400.00000
B 0.000 .. 0.010 T 0.010 TT 0.030 M: 0.0
end of section 4	 sect peak amps: 0.0
inactive allocs returned to freespace
SECTION 5:
new alloc for instr 1:
i 1 time 0.03016: 664.10803
i 1 time 0.03016: 400.00000
i 1 time 0.03016: 400.00000
B 0.000 .. 0.010 T 0.010 TT 0.040 M: 0.0
end of section 5	 sect peak amps: 0.0
inactive allocs returned to freespace
SECTION 6:
new alloc for instr 1:
i 1 time 0.04014: 631.01086
i 1 time 0.04014: 400.00000
i 1 time 0.04014: 400.00000

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Is it the same if you use the seed opcode?  seed 0 should seed the random
number generators from the clock.


-- 
View this message in context: http://csound.1045644.n5.nabble.com/Problem-with-randomi-randomh-starting-values-tp2644075p2679668.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

yes, i used seed 0 in my examples - that's the problem. here is the  
code and the result again:



-n


seed 0
instr 1
ktimk timeinstk
kRdm random 400, 800
kRdmi randomi 400, 800, 1
kRdmh randomh 400, 800, 1
if ktimk == 1 then
printk 0, kRdm
printk 0, kRdmi
printk 0, kRdmh
endif
endin


r 5
i 1 0 .01




SECTION 2:
new alloc for instr 1:
i 1 time 0.00023: 517.29187
i 1 time 0.00023: 400.00000
i 1 time 0.00023: 400.00000
B 0.000 .. 0.010 T 0.010 TT 0.010 M: 0.0
end of section 2	 sect peak amps: 0.0
inactive allocs returned to freespace
SECTION 3:
new alloc for instr 1:
i 1 time 0.01020: 564.97852
i 1 time 0.01020: 400.00000
i 1 time 0.01020: 400.00000
B 0.000 .. 0.010 T 0.010 TT 0.020 M: 0.0
end of section 3	 sect peak amps: 0.0
inactive allocs returned to freespace
SECTION 4:
new alloc for instr 1:
i 1 time 0.02018: 453.33304
i 1 time 0.02018: 400.00000
i 1 time 0.02018: 400.00000
B 0.000 .. 0.010 T 0.010 TT 0.030 M: 0.0
end of section 4	 sect peak amps: 0.0
inactive allocs returned to freespace
SECTION 5:
new alloc for instr 1:
i 1 time 0.03016: 664.10803
i 1 time 0.03016: 400.00000
i 1 time 0.03016: 400.00000
B 0.000 .. 0.010 T 0.010 TT 0.040 M: 0.0
end of section 5	 sect peak amps: 0.0
inactive allocs returned to freespace
SECTION 6:
new alloc for instr 1:
i 1 time 0.04014: 631.01086
i 1 time 0.04014: 400.00000
i 1 time 0.04014: 400.00000


thanks for the reaction. I'd be very happy if anyone could have a look  
in the code. i think the starting values should be each time different  
for a real random opcode.

	joachim


Am 26.08.2010 um 08:25 schrieb widdly:

>
> Is it the same if you use the seed opcode?  seed 0 should seed the  
> random
> number generators from the clock.
>
>
> -- 
> View this message in context: http://csound.1045644.n5.nabble.com/Problem-with-randomi-randomh-starting-values-tp2644075p2679668.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook  
> users
> worldwide. Take advantage of special opportunities to increase  
> revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net