Since they already exist, they should not be changed. For the sake of backward compatibility.

You can always write a user-defined opcode (like mkvedelay for vdelay) to convert the unit you do not like (say milliseconds) to the one you do like (say seconds).

Regards,
Mike

-----Original Message-----
>From: mark jamerson 
>Sent: Jan 28, 2008 11:49 AM
>To: Csound 
>Subject: [Csnd] Vdelay opcode family delay rates
>
>
> Hey, 
>
>     I just noticed that the vdelay and vdelay3 opcodes have delay times measured in milliseconds, while the rest of the vdelay opcodes have them measured in seconds. Unless there is a reason for the difference, I feel like those should all be standardized to one or the other.  
>
>                                                       Mark 
>
>
>
>
>      ____________________________________________________________________________________
>Be a better friend, newshound, and 
>know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 
>
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"