Spectrum analyzer possible in DSP?

stylus02 · Feb 10, 2009, 01:47 PM

ok, we have to deal with this behavior of a bandpass- gear. anyway it's very useful for my mixing purposes.

Max M. · Feb 10, 2009, 01:59 PM

...
sure - it does the trick anyway...

Russ · Feb 10, 2009, 02:01 PM

You have to think of the display more like you what you would see on a (40 band) graphic EQ, where the center of each bar would be where the center frequency for each band is located, rather than the grid lines (or labels). Picture in your head each band labeled with it's center frequency, and anything in between does not exist (i.e. you only see the level of each band, not the level of stuff in between).

Maddogg6 · Feb 10, 2009, 02:17 PM

Quote:

Originally Posted by Max M.

well, just to avoid confisuion (sure no complaining at all

- we just share the info) - there's no rolloff (you get your "-2..3dB" results just because you set the WaveGen to the frequencies that are natural to human eye (like 100Hz or 5Hz or 10Khz) but they're just fall out of the SA band points (its freq points are 1/4 octave points with anchor at 1kHz)
Try this test to see the rolloff

- better to test with increased peak hold time.

yes, it is just about perfectly flat across the spectrum...
Before I was trying freqs that seemed to have a bar for it.

Quote:

anyway it's very useful for my mixing purposes.

Agreed in deed.

Quote:

i.e. you only see the level of each band, not the level of stuff in between

I see what you are saying, but... it doesnt quite behave this way - the graphic EQ I had was probably FFT based, a single freq test tone *only* registered on its band - say it was a 100 Hz tone - only the 100 Hz bargraph responded - with SA.Minus - the neighboring bands also react. Its just different from expected.

Still quite useful of course.

And I worked around the F5 key thing, by temporarily deleting all but 2 color schemes and just had to 'scroll' through the 2 color schemes to see my changes in the registry - then I reloaded the 'factory' color schemes by re-registering the included .reg file - no problem... while the F5 would have been handy.... except for knowing which color scheme was currently selected - that was really why I did the deleting - to get a grasp on which scheme I was editing before I renamed it.
At first I was editing what I thought was the white on black scheme - turns out I was editing the black on white scheme :s

Its all good - thanks again Max.

Max M. · Feb 10, 2009, 02:44 PM

yeah, that could be painful. Backup, backup, backup

personally, i was setting up the peakBarColor of the scheme i'm going to edit to the bloody red first - to easily find it through shift-c without mistake.

Maddogg6 · Feb 10, 2009, 03:44 PM

Quote:

Originally Posted by Max M.

yeah, that could be painful. Backup, backup, backup

personally, i was setting up the peakBarColor of the scheme i'm going to edit to the bloody red first - to easily find it through shift-c without mistake.

Doh! - Wish I thought of that... oh yeah.. the another thing I needed to understand was the first byte (of some colors) - turns out it is an 'alpha' (opacity/transparency) value - so between the multiple things I was still ignorant about.. well now I know.

I mean, I had figured there was an alpha - but was it the first or last byte?? was I editing the right scheme??? - *deletes registry keys* ....

So, for the 4 byte colors (in case others dont know ..??)
color = 0xAARRGGBB
0x = A hexidecimal prefix. (No need to type that in)
AA = Alpha 0= 100% transparent | FF = 100% Opaque
RR = Red Amount
GG = Green Amount
BB = Blue Amount

Leave it to me to state the obvious (to everyone but me

)

And ohhhh - 'bloody'....
Here's Bloody Graphite...

Code:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\kX\Plugins\SA.minus\Colours\Bloody Graphite]
"peakBarColor"=dword:99cc0000
"holdBarColor"=dword:cccc0000
"bkgLightColor"=dword:ff333333
"bkgDarkColor"=dword:ff000000
"gridBorderColor"=dword:ff000000
"gridLineColor"=dword:ff606060
"labelColor"=dword:ff999999

Russ · Feb 11, 2009, 06:02 AM

Here is another color scheme...

Code:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\kX\Plugins\SA.minus\Colours\Serenity]
"peakBarColor"=dword:a0c8c8c8
"holdBarColor"=dword:a0ff0000
"bkgLightColor"=dword:ff576997
"bkgDarkColor"=dword:ff091231
"gridBorderColor"=dword:ff8a8a8a
"gridLineColor"=dword:a08a8a8a
"labelColor"=dword:c0ffffff

stylus02 · Feb 12, 2009, 12:55 PM

making a color scheme for the sa.minus could be a new hype. very nice russ & maddogg.

http://freenet-homepage.de/stylish-s...al_schemes.jpg
http://freenet-homepage.de/stylish-s...al_schemes.zip

sorry guys, can't stop doing that.

http://freenet-homepage.de/stylish-s...ls_schemes.jpg
http://freenet-homepage.de/stylish-s...ls_schemes.zip

imperia · Feb 18, 2009, 08:43 AM

Is there a chance for 'light'. This one is not very SB Live friendly.
Maybe with less bargraphs.

Max M. · Feb 18, 2009, 02:38 PM

well, not me - sorry.

Max M. · Feb 22, 2009, 08:49 AM

source code
kxl binary

Changes:
* added settings status window (F2)
* added different "band curve" modes (Ctrl+B, see details below)
* fixed missing "infinite hold" (Crtl+I) command
* added "always on top" toggle (Ctrl+A)
* fixed other minor bugs
* some source code clean-up

I also included the colour schemes posted here in the kxl package (i hope it's OK i did it without asking first, kick me if it's not)

Note this version is incompatible with the settings saved within kxmixer by previous SA.minus versions - so if you value your current settings make sure to save them as default (or [0...9]) preset before installing this update.

"Band curve" mode details:
The "band curve" mode (more correctly to be named as "band separation" but that sounds awful to me) is a combination of the two SA settings - the "band intersection" (which is simply a filter band width defined as the level at neighbour bands crossover frequency) and the "band leak compensation" (which is a sort of "magic" peak data postprocessing used to reduce the effects of the interband crosstalk

). Well, basically speaking, these modes determine the accuracy and (as a secondary effect) the smoothness/sharpness of the peak display. See this table for a quick "band curve" mode comparison.
For a compatibility with the previous versions, the default mode is "I" (band intersection -6dB, band leak compensation off), though the most precise one (and hence recommended) is the "Mode IV" (band intersection -3dB, band leak compensation on). Note that the "band leak compensation" significally affects perceived peak display dynamics so (with the option turned on) you will likely need to increase visible level range by 15...25dB (and probably decrease peak decay speed a little).

babinosman · Feb 22, 2009, 10:54 AM

thanksssssssssss

TheKezReturns · Feb 23, 2009, 10:49 PM

I'd like to have a play with the source code but I'm a little clueless about the last two things

* Link to kxapi.lib and gdiplus.lib
* Compile as non-MFC and non-unicode dll

I downloaded the SP2 SDK and added the folders to inculdes and libs directories.
But I don't know how to 'Compile as non-MFC and non-unicode dll'
I get this at the moment.

Quote:

C:\Documents and Settings\Kez\Desktop\src\kali/dbgutils.h(7) : error C2010: '.' : unexpected in macro formal parameter list
C:\Documents and Settings\Kez\Desktop\src\kali/dbgutils.h(7) : error C2010: '.' : unexpected in macro formal parameter list
C:\Documents and Settings\Kez\Desktop\src\kali/dbgutils.h(7) : error C2010: '.' : unexpected in macro formal parameter list
C:\Documents and Settings\Kez\Desktop\src\helpers.h(137) : warning C4002: too many actual parameters for macro 'trace'
C:\Documents and Settings\Kez\Desktop\src\os.window.h(39) : warning C4002: too many actual parameters for macro 'trace'
C:\Documents and Settings\Kez\Desktop\src\os.window.h(51) : warning C4002: too many actual parameters for macro 'trace

'

Max M. · Feb 24, 2009, 03:49 AM

it looks like you're trying to compile it with something earlier than vc2005 (vc6, vc2003, DDK?) - please use something newer (any version of vc2005 or higher (including "express") or WDK will do the trick).
Although for vc2003 or DDK you would fool it with:

Code:

inline void trace(...) {}

instead of

Code:

#define trace(...) __noop

but i'm not sure if they have other incompabilities (i suspect they have, particulary vs. kX SDK itself).

* Link to kxapi.lib and gdiplus.lib
* Compile as non-MFC and non-unicode dll
- this depends on the building sytem you use (IDE? Driver Kit?)

TheKezReturns · Feb 24, 2009, 06:42 PM

Ok thanks Max, will dload vs express and try that.

And regarding the filter coefficients, would it be easy enought o calculate some new ones for a different frequency range. I'd like to have an option to 'zoom in' on the lower part of the spectrum, maybe 20-300, as this is generally where it's extra helpful to have visual feedback.

When you say

Quote:

we have only 40 points of exact level matches

is that because of the current set of coefficients or is there some sort of limitation to what frequencies we can measure accurately with this method?

Sorry if any of these questions sound naive, but I'm a 'lean as you go' kind of guy and generally learn as much as I need to know to get the job done and stop there.

I'd also like to implement the following features-

- An option to have the exact frequency of the band the mouse is hovering over displayed somewhere on the graph in a large font. could have peak hold level too.

- Hotkey to enlarge / shrink the graph label font - saved with the preset.

- Shift clicking on a band would enable / disable it's frequency label on the graph. -saved with preset.

- Maybe a turbo mode for when you don't care about the cpu hit and want impress your friends

I take it it's throttled at the moment?

- And for something really adventurous.... big part imagination this one but I'm just gonna put it out there...

Hold down a key and the analyzer starts taking an long term average of the bands and stores those values when the key is released, similar to the learn function of the many eq matching plugins out there.
Hold another key down and another average is taken, this time compared with the stored values and overlayed on (or replacing) the graph with bars stretching between the two average readings. A positive or negative difference could be indicated somehow, perhaps different colours or arrow heads.
I think this would be very helpful in determining quickly... 'is my mix too bright overall.. is there enough / too much sub... did I scoop the midrange toomuch' - relative to your favorite productions. Ofcourse all the rules of an eq matching plugin would apply here. ie. music of the same genre with much the same elements and sampling the eq over say 4 bars of chorus when all instruments are 'in'.

Although I have the intention of having a go at making these additions myself, I'll most likely do so very slowly. I generally only boot xp when I really have to these days and even then I still havent managed to successfully compile the source!
So if anyone want to beat me too it, I certainly won't be offended.

What a great community. Just weeks ago I was jealous of this guys rme analyzer, now we have better one

stylus02 · Feb 25, 2009, 07:28 AM

very nice band curve modes, max. your baby becomes a professional audio tool.

stylus

TravelRec. · Feb 26, 2009, 02:03 PM

Hi MaxM.

thank you very much for upgrading the tool - it´s fantastic! As a suggestion: it would be very fine if the analyzer would have a drop-down menu or similar (right click with the mouse thingie) for faster access and a better overview to the active/not active settings.

TheKezReturns · Feb 28, 2009, 02:45 AM

Sorry to be such a newb and all but trying to complie in vc++ express gives me this.

I have added kx SDK includes and libs and SP2 SDK libs and includes for gdiplus.

Code:

1>------ Build started: Project: Sa+, Configuration: Debug Win32 ------
1>Compiling...
1>cl : Command line warning D9035 : option 'Wp64' has been deprecated and will be removed in a future release
1>kxl.cpp
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(334) : warning C4005: '__reserved' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1956) : see previous definition of '__reserved'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(341) : warning C4005: '__checkReturn' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1957) : see previous definition of '__checkReturn'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(344) : warning C4005: '__typefix' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1958) : see previous definition of '__typefix'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(349) : warning C4005: '__override' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1959) : see previous definition of '__override'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(350) : warning C4005: '__fallthrough' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1968) : see previous definition of '__fallthrough'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(351) : warning C4005: '__callback' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1960) : see previous definition of '__callback'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(352) : warning C4005: '__in' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1753) : see previous definition of '__in'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(353) : warning C4005: '__out' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1762) : see previous definition of '__out'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(354) : warning C4005: '__inout' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1781) : see previous definition of '__inout'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(356) : warning C4005: '__out_ecount' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1763) : see previous definition of '__out_ecount'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(357) : warning C4005: '__in_ecount' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1754) : see previous definition of '__in_ecount'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(358) : warning C4005: '__inout_ecount' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1782) : see previous definition of '__inout_ecount'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(359) : warning C4005: '__out_bcount' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1764) : see previous definition of '__out_bcount'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(360) : warning C4005: '__in_bcount' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1755) : see previous definition of '__in_bcount'
1>c:\program files\microsoft platform sdk for windows xp sp2\include\specstrings.h(361) : warning C4005: '__inout_bcount' : macro redefinition
1>        g:\visual studio c++ express\vc\include\sal.h(1783) : see previous definition of '__inout_bcount'
1>c:\documents and settings\kez\desktop\src\sa.options.h(224) : warning C4996: '_snprintf': This function or variable may be unsafe. Consider using _snprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>        g:\visual studio c++ express\vc\include\stdio.h(358) : see declaration of '_snprintf'
1>c:\documents and settings\kez\desktop\src\sa.options.h(231) : warning C4996: '_snprintf': This function or variable may be unsafe. Consider using _snprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>        g:\visual studio c++ express\vc\include\stdio.h(358) : see declaration of '_snprintf'
1>c:\documents and settings\kez\desktop\src\sa.options.h(239) : warning C4996: '_snprintf': This function or variable may be unsafe. Consider using _snprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>        g:\visual studio c++ express\vc\include\stdio.h(358) : see declaration of '_snprintf'
1>c:\documents and settings\kez\desktop\src\sa.h(331) : warning C4996: 'swprintf': swprintf has been changed to conform with the ISO C standard, adding an extra character count parameter. To use traditional Microsoft swprintf, set _CRT_NON_CONFORMING_SWPRINTFS.
1>        g:\visual studio c++ express\vc\include\swprintf.inl(85) : see declaration of 'swprintf'
1>c:\documents and settings\kez\desktop\src\sa.h(347) : warning C4996: 'swprintf': swprintf has been changed to conform with the ISO C standard, adding an extra character count parameter. To use traditional Microsoft swprintf, set _CRT_NON_CONFORMING_SWPRINTFS.
1>        g:\visual studio c++ express\vc\include\swprintf.inl(85) : see declaration of 'swprintf'
1>c:\documents and settings\kez\desktop\src\sa.h(352) : warning C4996: 'swprintf': swprintf has been changed to conform with the ISO C standard, adding an extra character count parameter. To use traditional Microsoft swprintf, set _CRT_NON_CONFORMING_SWPRINTFS.
1>        g:\visual studio c++ express\vc\include\swprintf.inl(85) : see declaration of 'swprintf'
1>c:\documents and settings\kez\desktop\src\kxl.cpp(230) : warning C4996: 'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>        g:\visual studio c++ express\vc\include\string.h(157) : see declaration of 'strncpy'
1>c:\documents and settings\kez\desktop\src\kxl.cpp(233) : warning C4996: 'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>        g:\visual studio c++ express\vc\include\string.h(157) : see declaration of 'strncpy'
1>c:\documents and settings\kez\desktop\src\kxl.cpp(256) : warning C4996: 'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>        g:\visual studio c++ express\vc\include\string.h(157) : see declaration of 'strncpy'
1>c:\documents and settings\kez\desktop\src\sa.h(676) : warning C4996: '_snprintf': This function or variable may be unsafe. Consider using _snprintf_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>        g:\visual studio c++ express\vc\include\stdio.h(358) : see declaration of '_snprintf'
1>        c:\documents and settings\kez\desktop\src\sa.h(666) : while compiling class template member function 'void sa::View<Plugin,InfoTool>::updateInfo(void)'
1>        with
1>        [
1>            Plugin=Plugin,
1>            InfoTool=InfoTool
1>        ]
1>        c:\documents and settings\kez\desktop\src\kxl.cpp(130) : see reference to class template instantiation 'sa::View<Plugin,InfoTool>' being compiled
1>        with
1>        [
1>            Plugin=Plugin,
1>            InfoTool=InfoTool
1>        ]
1>        c:\documents and settings\kez\desktop\src\kxl.cpp(120) : while compiling class template member function 'PluginWindow<Plugin>::PluginWindow(Plugin *,int *)'
1>        with
1>        [
1>            Plugin=Plugin
1>        ]
1>        c:\documents and settings\kez\desktop\src\kxl.cpp(322) : see reference to class template instantiation 'PluginWindow<Plugin>' being compiled
1>        with
1>        [
1>            Plugin=Plugin
1>        ]
1>c:\documents and settings\kez\desktop\src\sa.h(678) : error C2065: 'colorsKey' : undeclared identifier
1>c:\documents and settings\kez\desktop\src\sa.h(678) : error C2228: left of '.subKey' must have class/struct/union
1>Build log was saved at "file://c:\Documents and Settings\Kez\Desktop\src\Debug\BuildLog.htm"
1>Sa+ - 2 error(s), 26 warning(s)

Max M. · Feb 28, 2009, 07:42 AM

hehe, well, MS likes problems like this. It's just the vc2008 incompatible with the XP Platform SDK.
see Microsoft Windows SDK Blog : Using Visual C++ 2008 Express with the Windows SDK (detailed version)
E.g. you need to use the Vista (or Server 2008) PSDK or the PSDK included with the "vc2008 express" itself.

p.s. That's not so newb stuff in fact, sometimes it looks like they intentionally mix up IDE/PSDK things to push ".net" (well, at least for "express" versions).

Max M. · Feb 28, 2009, 09:33 AM

for consistency, i just have updated the sources to give less cryptic errors/warnings for screwed cl/crt/psdk configuration. (stuff like _CRT_SECURE_NO_WARNINGS, newer crt swprintf etc.)

Max M. · May 3, 2009, 04:59 PM

The SA.minus sources updated to kX SDK v46:
sa.minus.src.latest.zip

The sources archive for the kX SDK v45 is updated too -
lately Eugene found that the previous archive contained one invalid header file which would cause the compiled plugin to crash. The fixed version is sa.minus.src.latest.45.zip

(No new binaries.)

TravelRec. · May 4, 2009, 07:33 AM

Thank you Max M. - once again!

TheKezReturns · Jul 26, 2009, 01:41 AM

Hey max, I thought I'd have another stab at this as I found an old pc that I've turned into a dedicated sa+ box

I still can't manage to compile it successfully.
do you think I'd have alot better luck if I installed vista?

In the meantime, if you get a spare moment, could you please turn the polling interval into a paraemter we can change with a hotkey or something. Seeing as my new sa+ box isn't doing anything else, it may as well be working real hard at being an analyser.
Cheers.

Max M. · Jul 26, 2009, 02:19 AM

>I still can't manage to compile it successfully.

give more details about errors you get now.
(according to build output ("error in specstrings.h bla-bla-bla") you posted above, it seems you just have installed and trying to use incompatible (with each other) compiler (IDE) and Platform SDK)

>do you think I'd have alot better luck if I installed vista?

nope.
(just don't get confused by Platform SDK "title", i.e. the title "Windows XYZ Platform SDK" do not mean that you need the XYZ and you can't use this SDK in earlier OS. I.e. whatever Platform SDK of this decade is compatible with the XP (these days at least). So what you need to pay attention to is the "IDE" vs. "Platform SDK" compatibilty, e.g.: if your IDE comes with PSDK - use the one; if IDE comes with several PSDKs (or asks wich one to install) - use the default one (no matter what title that one has)). something like that.
Try to start with some "hello word" program (just #include "stdio.h" + #include "windows.h" + main + printf) to check IDE/PSDK consistency.

>could you please turn the polling interval into a paraemter we can change with a hotkey or something.

I'm afraid i cannot do that. As this will negatively affect the code (too wide/bloating variable spread) with pretty (to my opinion) questinoable benefit.
Currently the polling is hardcoded to 48ms, which is ~20Hz screen update rate, which is... well, whatever.
In other words: lack of time + my personal bias of the option -> "it's up to you"

TheKezReturns · Jul 26, 2009, 02:52 AM

Ok thanks, I'll try again when i get some time and post errors if any.

Quote:

I'm afraid i cannot do that. As this will negatively affect the code (too wide/bloating variable spread) with pretty (to my opinion) questinoable benefit.
Currently the polling is hardcoded to 48ms, which is ~20Hz screen update rate, which is... well, whatever.
In other words: lack of time + my personal bias of the option -> "it's up to you"

Ok it just doesn't seem quite as realtime and smooth as some vst plugin varieties but I guess it's ok and totally useable the way it is. If I can get it to compile I might have a play. Perhaps just a 'turbo' mode that halves to 24ms or something. Do you still think that would negatively affect the code?

Max M. · Jul 27, 2009, 12:29 AM

>it just doesn't seem quite as realtime and smooth as some vst plugin varieties

well, it's a long story actually - in fact, i doubt this perception has something to do with polling rate (maybe one just need to tweek decay time to fit personal favours?

- well, we'll know for sure when you get "turbo" version). Unfortuntely as this all all depends on how we define the stuff behind "real-time" and "smooth" words - it's hard to give some fair comments.
Maybe if you'd mentioned what specific vst analyzer you compared to - i could give more tech. details (for example: "real-time" - for instance most of FFT based analyzers actually have higher latency (e.g. the time between the moment signal changes and the moment you see that change) due to FFT algo nature - no matter what drawing rate it has))...
Well, in other words - from algorithmic point of view - it's more likely that it could be something aside of more brute polling.

TheKezReturns · Aug 2, 2009, 11:01 PM

Ok sorry max 48ms is plenty. I was running sa+ window maximized and when I shrunk the window suddenly it was smooth as silk. Maybe this old box just can't handle it (p3 733Mhz + Sis graphics).

TheKezReturns · Aug 2, 2009, 11:03 PM

I lowered screen res to 800x600 and set processor Processor scheduling to Background services and that seemed to speed it up a bit.

Russ · Aug 3, 2009, 03:48 AM

Quote:

Originally Posted by Max M.

it looks like you're trying to compile it with something earlier than vc2005 (vc6, vc2003, DDK?) - please use something newer (any version of vc2005 or higher (including "express") or WDK will do the trick).

I think the kX SDK incompatibilities have more to do with kxgui (MFC).
SA.minus compiles fine for me with VC 2003/kX SDK 3548 with the default (directory) includes (i.e. the $(VCInstallDir) stuff)... plus the kX includes of course.

Quote:

Originally Posted by TheKezReturns

I lowered screen res to 800x600 and set processor Processor scheduling to Background services and that seemed to speed it up a bit.

Yeah, I usually have to resize the SA.minus window so that it is about half it's default width/height, otherwise it uses a little too much CPU for my old beast (though it does not really affect the drawing speed, etc.).

Max M. · Aug 3, 2009, 04:06 AM

>SA.minus compiles fine for me with VC 2003/kX SDK 3548...

good, that's because i added

Code:

#if _MSC_VER >= 1400
    #define trace(...) __noop
#else
    inline void trace(...) {}
#endif

my comment was for earlier code version which won't compile with VC2003 because of "__noop" (typically i try to avoid non-standard extensions but the __noop is too sweet)

Feb 10, 2009, 01:47 PM	#31
stylus02 DriverHeaven Lover Join Date: Jan 2008 Location: germany, sb0090 Posts: 158 Rep Power: 0	Re: Spectrum analyzer possible in DSP? ok, we have to deal with this behavior of a bandpass- gear. anyway it's very useful for my mixing purposes. __________________ http://freenet-homepage.de/stylish-s...xas/index.html

Feb 10, 2009, 01:59 PM	#32
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	Îòâåò: Spectrum analyzer possible in DSP? ... sure - it does the trick anyway... __________________ Last edited by Max M.; Feb 10, 2009 at 02:08 PM. Reason: ah, never mind.. it was looking like Max called for a protection of international standards - doh!

Feb 10, 2009, 02:01 PM	#33
Russ DriverHeaven Extreme Member Join Date: Jan 2005 Posts: 4,836 Rep Power: 41	Re: Spectrum analyzer possible in DSP? You have to think of the display more like you what you would see on a (40 band) graphic EQ, where the center of each bar would be where the center frequency for each band is located, rather than the grid lines (or labels). Picture in your head each band labeled with it's center frequency, and anything in between does not exist (i.e. you only see the level of each band, not the level of stuff in between).

Feb 10, 2009, 02:44 PM	#35
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	Îòâåò: Spectrum analyzer possible in DSP? yeah, that could be painful. Backup, backup, backup personally, i was setting up the peakBarColor of the scheme i'm going to edit to the bloody red first - to easily find it through shift-c without mistake. __________________ Last edited by Max M.; Feb 10, 2009 at 02:49 PM. Reason: stop inventing new words...

Feb 12, 2009, 12:55 PM	#38
stylus02 DriverHeaven Lover Join Date: Jan 2008 Location: germany, sb0090 Posts: 158 Rep Power: 0	Re: Spectrum analyzer possible in DSP? making a color scheme for the sa.minus could be a new hype. very nice russ & maddogg. http://freenet-homepage.de/stylish-s...al_schemes.jpg http://freenet-homepage.de/stylish-s...al_schemes.zip sorry guys, can't stop doing that. http://freenet-homepage.de/stylish-s...ls_schemes.jpg http://freenet-homepage.de/stylish-s...ls_schemes.zip __________________ http://freenet-homepage.de/stylish-s...xas/index.html Last edited by stylus02; Feb 14, 2009 at 06:53 AM. Reason: want give this tread some kind of endlessness ;) again & again..

Feb 18, 2009, 08:43 AM	#39
imperia DriverHeaven Lover Join Date: Dec 2002 Location: Sofia, Bulgaria Posts: 167 Rep Power: 0	Re: Spectrum analyzer possible in DSP? Is there a chance for 'light'. This one is not very SB Live friendly. Maybe with less bargraphs.

Feb 18, 2009, 02:38 PM	#40
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	Îòâåò: Spectrum analyzer possible in DSP? well, not me - sorry. __________________

Feb 22, 2009, 08:49 AM	#41
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	SA.minus updated source code kxl binary Changes: * added settings status window (F2) * added different "band curve" modes (Ctrl+B, see details below) * fixed missing "infinite hold" (Crtl+I) command * added "always on top" toggle (Ctrl+A) * fixed other minor bugs * some source code clean-up I also included the colour schemes posted here in the kxl package (i hope it's OK i did it without asking first, kick me if it's not) Note this version is incompatible with the settings saved within kxmixer by previous SA.minus versions - so if you value your current settings make sure to save them as default (or [0...9]) preset before installing this update. "Band curve" mode details: The "band curve" mode (more correctly to be named as "band separation" but that sounds awful to me) is a combination of the two SA settings - the "band intersection" (which is simply a filter band width defined as the level at neighbour bands crossover frequency) and the "band leak compensation" (which is a sort of "magic" peak data postprocessing used to reduce the effects of the interband crosstalk ). Well, basically speaking, these modes determine the accuracy and (as a secondary effect) the smoothness/sharpness of the peak display. See this table for a quick "band curve" mode comparison. For a compatibility with the previous versions, the default mode is "I" (band intersection -6dB, band leak compensation off), though the most precise one (and hence recommended) is the "Mode IV" (band intersection -3dB, band leak compensation on). Note that the "band leak compensation" significally affects perceived peak display dynamics so (with the option turned on) you will likely need to increase visible level range by 15...25dB (and probably decrease peak decay speed a little). __________________ Last edited by Max M.; Feb 22, 2009 at 11:25 AM. Reason: yek, forgot to mention another change

Feb 22, 2009, 10:54 AM	#42
babinosman DriverHeaven Junior Member Join Date: Mar 2008 Posts: 36 Rep Power: 0 System Specs	Re: Spectrum analyzer possible in DSP? thanksssssssssss __________________

Feb 24, 2009, 03:49 AM	#44
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	Îòâåò: Spectrum analyzer possible in DSP? it looks like you're trying to compile it with something earlier than vc2005 (vc6, vc2003, DDK?) - please use something newer (any version of vc2005 or higher (including "express") or WDK will do the trick). Although for vc2003 or DDK you would fool it with: Code: inline void trace(...) {} instead of Code: #define trace(...) __noop but i'm not sure if they have other incompabilities (i suspect they have, particulary vs. kX SDK itself). * Link to kxapi.lib and gdiplus.lib * Compile as non-MFC and non-unicode dll - this depends on the building sytem you use (IDE? Driver Kit?) __________________ Last edited by Max M.; Feb 24, 2009 at 06:44 AM.

Feb 25, 2009, 07:28 AM	#46
stylus02 DriverHeaven Lover Join Date: Jan 2008 Location: germany, sb0090 Posts: 158 Rep Power: 0	Re: SA.minus updated very nice band curve modes, max. your baby becomes a professional audio tool. stylus __________________ http://freenet-homepage.de/stylish-s...xas/index.html

Feb 26, 2009, 02:03 PM	#47
TravelRec. Alternative Audioproductions Join Date: Sep 2003 Location: Germany / Sachsen-Anhalt Posts: 1,704 Rep Power: 42	Re: Spectrum analyzer possible in DSP? Hi MaxM. thank you very much for upgrading the tool - it´s fantastic! As a suggestion: it would be very fine if the analyzer would have a drop-down menu or similar (right click with the mouse thingie) for faster access and a better overview to the active/not active settings. __________________ Always take a look behind.

Feb 28, 2009, 07:42 AM	#49
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	Îòâåò: Spectrum analyzer possible in DSP? hehe, well, MS likes problems like this. It's just the vc2008 incompatible with the XP Platform SDK. see Microsoft Windows SDK Blog : Using Visual C++ 2008 Express with the Windows SDK (detailed version) E.g. you need to use the Vista (or Server 2008) PSDK or the PSDK included with the "vc2008 express" itself. p.s. That's not so newb stuff in fact, sometimes it looks like they intentionally mix up IDE/PSDK things to push ".net" (well, at least for "express" versions). __________________ Last edited by Max M.; Feb 28, 2009 at 09:46 AM.

Feb 28, 2009, 09:33 AM	#50
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	Îòâåò: Spectrum analyzer possible in DSP? for consistency, i just have updated the sources to give less cryptic errors/warnings for screwed cl/crt/psdk configuration. (stuff like _CRT_SECURE_NO_WARNINGS, newer crt swprintf etc.) __________________

May 3, 2009, 04:59 PM	#51
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	Îòâåò: Spectrum analyzer possible in DSP? The SA.minus sources updated to kX SDK v46: sa.minus.src.latest.zip The sources archive for the kX SDK v45 is updated too - lately Eugene found that the previous archive contained one invalid header file which would cause the compiled plugin to crash. The fixed version is sa.minus.src.latest.45.zip (No new binaries.) __________________ Last edited by Max M.; May 3, 2009 at 05:42 PM.

May 4, 2009, 07:33 AM	#52
TravelRec. Alternative Audioproductions Join Date: Sep 2003 Location: Germany / Sachsen-Anhalt Posts: 1,704 Rep Power: 42	Re: Spectrum analyzer possible in DSP? Thank you Max M. - once again! __________________ Always take a look behind.

Jul 26, 2009, 01:41 AM	#53
TheKezReturns DriverHeaven Lover Join Date: Apr 2005 Location: Gold Coast Australia Posts: 115 Rep Power: 28	Re: Spectrum analyzer possible in DSP? Hey max, I thought I'd have another stab at this as I found an old pc that I've turned into a dedicated sa+ box I still can't manage to compile it successfully. do you think I'd have alot better luck if I installed vista? In the meantime, if you get a spare moment, could you please turn the polling interval into a paraemter we can change with a hotkey or something. Seeing as my new sa+ box isn't doing anything else, it may as well be working real hard at being an analyser. Cheers. __________________ Dual Boot Hacky XP / OSX /Ubuntu. 2.13 C2D. 4 Gb DDR2. Intel DG965RY. EMU 1820M / TC Konnekt 24D / MOTU Ultralite mk3

Jul 26, 2009, 02:19 AM	#54
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	Îòâåò: Spectrum analyzer possible in DSP? >I still can't manage to compile it successfully. give more details about errors you get now. (according to build output ("error in specstrings.h bla-bla-bla") you posted above, it seems you just have installed and trying to use incompatible (with each other) compiler (IDE) and Platform SDK) >do you think I'd have alot better luck if I installed vista? nope. (just don't get confused by Platform SDK "title", i.e. the title "Windows XYZ Platform SDK" do not mean that you need the XYZ and you can't use this SDK in earlier OS. I.e. whatever Platform SDK of this decade is compatible with the XP (these days at least). So what you need to pay attention to is the "IDE" vs. "Platform SDK" compatibilty, e.g.: if your IDE comes with PSDK - use the one; if IDE comes with several PSDKs (or asks wich one to install) - use the default one (no matter what title that one has)). something like that. Try to start with some "hello word" program (just #include "stdio.h" + #include "windows.h" + main + printf) to check IDE/PSDK consistency. >could you please turn the polling interval into a paraemter we can change with a hotkey or something. I'm afraid i cannot do that. As this will negatively affect the code (too wide/bloating variable spread) with pretty (to my opinion) questinoable benefit. Currently the polling is hardcoded to 48ms, which is ~20Hz screen update rate, which is... well, whatever. In other words: lack of time + my personal bias of the option -> "it's up to you" __________________ Last edited by Max M.; Jul 26, 2009 at 02:32 AM.

Jul 27, 2009, 12:29 AM	#56
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	Îòâåò: Spectrum analyzer possible in DSP? >it just doesn't seem quite as realtime and smooth as some vst plugin varieties well, it's a long story actually - in fact, i doubt this perception has something to do with polling rate (maybe one just need to tweek decay time to fit personal favours? - well, we'll know for sure when you get "turbo" version). Unfortuntely as this all all depends on how we define the stuff behind "real-time" and "smooth" words - it's hard to give some fair comments. Maybe if you'd mentioned what specific vst analyzer you compared to - i could give more tech. details (for example: "real-time" - for instance most of FFT based analyzers actually have higher latency (e.g. the time between the moment signal changes and the moment you see that change) due to FFT algo nature - no matter what drawing rate it has))... Well, in other words - from algorithmic point of view - it's more likely that it could be something aside of more brute polling. __________________

Aug 2, 2009, 11:01 PM	#57
TheKezReturns DriverHeaven Lover Join Date: Apr 2005 Location: Gold Coast Australia Posts: 115 Rep Power: 28	Re: Spectrum analyzer possible in DSP? Ok sorry max 48ms is plenty. I was running sa+ window maximized and when I shrunk the window suddenly it was smooth as silk. Maybe this old box just can't handle it (p3 733Mhz + Sis graphics). __________________ Dual Boot Hacky XP / OSX /Ubuntu. 2.13 C2D. 4 Gb DDR2. Intel DG965RY. EMU 1820M / TC Konnekt 24D / MOTU Ultralite mk3

Aug 2, 2009, 11:03 PM	#58
TheKezReturns DriverHeaven Lover Join Date: Apr 2005 Location: Gold Coast Australia Posts: 115 Rep Power: 28	Re: Spectrum analyzer possible in DSP? I lowered screen res to 800x600 and set processor Processor scheduling to Background services and that seemed to speed it up a bit. __________________ Dual Boot Hacky XP / OSX /Ubuntu. 2.13 C2D. 4 Gb DDR2. Intel DG965RY. EMU 1820M / TC Konnekt 24D / MOTU Ultralite mk3

Aug 3, 2009, 04:06 AM	#60
Max M. d/h member-shmember Join Date: Dec 2002 Location: Evil Empire Posts: 2,412 Rep Power: 47	Îòâåò: Spectrum analyzer possible in DSP? >SA.minus compiles fine for me with VC 2003/kX SDK 3548... good, that's because i added Code: #if _MSC_VER >= 1400 #define trace(...) __noop #else inline void trace(...) {} #endif my comment was for earlier code version which won't compile with VC2003 because of "__noop" (typically i try to avoid non-standard extensions but the __noop is too sweet) __________________

LinkBacks (?) LinkBack to this Thread: http://www.driverheaven.net/effects-dsp/176505-spectrum-analyzer-possible-dsp.html
Posted By	For	Type	Date
CQHAM.RU :: Ïðîñìîòð òåìû - Âûáîð çâóêîâîé êàðòû è äðàéâåðîâ äëÿ SDR.	This thread	Refback	Aug 4, 2009 02:28 PM
Ôîðóìû CQHAM.RU :: Ïðîñìîòð òåìû - Âûáîð çâóêîâîé êàðòû è äðàéâåðîâ äëÿ SDR.	This thread	Refback	May 22, 2009 06:31 AM
Ôîðóìû CQHAM.RU :: Ïðîñìîòð òåìû - Âûáîð çâóêîâîé êàðòû è äðàéâåðîâ äëÿ SDR.	This thread	Refback	May 22, 2009 03:30 AM
Ôîðóìû CQHAM.RU :: Ïðîñìîòð òåìû - Âûáîð çâóêîâîé êàðòû è äðàéâåðîâ äëÿ SDR.	This thread	Refback	May 22, 2009 03:29 AM
Ôîðóìû CQHAM.RU :: Ïðîñìîòð òåìû - Âûáîð çâóêîâîé êàðòû è äðàéâåðîâ äëÿ SDR.	This thread	Refback	May 22, 2009 03:23 AM

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Spectrum Analyzer in kX?	lowenz	General Discussion	55	Dec 5, 2004 07:43 PM
Spectrum info	ROBSCIX	General Discussion	3	Nov 3, 2004 04:05 AM
Full Spectrum Warrior! MUST SEE!	Warpy	Gaming Discussion	4	Sep 16, 2004 12:20 PM
Analyzer	mzry	General Discussion	1	Apr 28, 2004 04:21 PM
spectrum analyzer!	trance1meister	Effects and the DSP	2	Mar 9, 2003 09:00 PM