EXE FILESIZE THE SAME! If you change the file size, the checksum will not match, and the program won't run anymore. You should use a hex editor and be certain to KEEP THE ORIGINAL. exe file remains the same, even including spaces. It's vitally important that the Window name's original position & length in the. exe file & hack the window name by getting rid of the space before "Level" and adding a null character at the end of "Meter". You can use A_Space as part of the name, but there may be problems with consistent window recognition among the different AHK window-related commands. One caveat, if you are using the meter mentioned above and are using window detection, the author uses a space as the first character of the window name. I've spent considerable time looking for VU meters, and this one fits the bill pretty well. This meter will allow you to monitor via peak or steady-state with selectable mode/delay. After a while, you will be writing loop functions that will check to see if the sound level is > or, Level Meter with Digital Readout, for steady state measurements. You will be glad you invested the time, especially if you are young and will be using AHK on a regular basis. When using RegEx function, do yourself a huge one and create a software tool (I use MS Excel with concatenated formulas) to derive your regexes. One nice thing about having the VU GUI is that you can actually see the levels, which may initially help you set trip points in your software when checking for sound levels to steer events. You can always regex out the sign, but that makes coordinating the number with the GUI reading a little difficult. The VU meter recommended below uses dB, so when you do your level checking, it will be done in negative dB, which is not a problem for AHK. Keep in mind that the raw numbers from the soundcard may represent different scales such as dB or absolute digital values. In the future, I may poke around with some VU meters and extract some code that derives just the numbers without the VU GUI. I offer the following less-than-optimal solution that worked very well for me. Personally, I do not have time to learn windows API. It's plainly obvious that if VU meter software exists, programmers have a way of getting the numbers. The ability to monitor sound levels is an indispensable & powerful feature. I suspect that someone out there already has a good solution to this involving solely numerical extraction.
0 kommentar(er)
