VBEEP on 64-bit

[Joe Caverly]

     _x64: 1
   _admin: 1
_elevated: 1

TCC  26.02.43 x64   Windows 10 [Version 10.0.18363.1198]

In the help for VBEEP, it says;

64-bit versions of Windows do not support the frequency/duration syntax of VBEEP.

It seems to start working, though, at the 38 Hz level. Example;

vbeep 38 15

Also, pre-defined sounds seem to play in the middle of the command. That is;

vbeep 0 120 asterisk

plays the asterisk sound half way through the duration.

If this is valid, adding the info to the help file would be appreciated.

Joe

 

[rconn]

This *was* true on older x64 versions (due to a Windows API change), but a few versions ago BEEP & VBEEP were updated to use DirectSound on x64 builds. The help was updated for BEEP, but I missed VBEEP. I've updated it for the next version.

 

[vefatica]

I think you're getting 2 VBEEPs, a silent one and then the asterisk one. Here, "vbeep 0 120 asterisk" lasts 13 seconds (234 eighteenths of a second).

This one is odd: "vbeep 0 120 asterisk 0 120". I get a 6.5 sec silent visual beep, then a 6.5 sec visual beep that starts with the asterisk sound, then a 6.5 sec visual beep together with 6.5 sec of 120 hertz.

 

[rconn]

Also, pre-defined sounds seem to play in the middle of the command. That is;

vbeep 0 120 asterisk

plays the asterisk sound half way through the duration.

If this is valid, adding the info to the help file would be appreciated.

Joe

As Vince said, you're getting two VBEEP's (which is what you asked for). Since you didn't specify a frequency/duration for the asterisk, VBEEP used the previous duration value (120).