Voxengo SPAN pre 2.0 public beta-testing (update 3)

[Aleksey Vaneev]

I've posted version 2.0.2 - see the first post.

this update's changes:
* Mid-side spectrum view bug fixed.
* The "Mode" selection now works in all channel groups.
* Narrow-band sweeping now affects all channel groups at once.
"view all channel meters at once" function is yet to be implemented

[daxliniere]

Looking good, Aleksey!

[Arksun]

I've posted version 2.0.2 - see the first post.

this update's changes:
* Mid-side spectrum view bug fixed.
* The "Mode" selection now works in all channel groups.
* Narrow-band sweeping now affects all channel groups at once.
"view all channel meters at once" function is yet to be implemented

YES!!!

Whilst I was having major spiking problems in the audio using the older SPAN in Cubase 5. The new v2 SPAN is spike free, and just seems to run smoother overall, great update

[dsp music]

Thanks for the update.
Like it!

[I.P]

thanks for the update!!!
excellent job!
I love the new colors and features!

Just a big + for that

Note that it also affects how "correlation meter" is shown.

I believe density mode is how correlation should always be displayed, it gives more information.

correlation have to respond faster ...
right now it will show only positive values most of the time ...
comparing with other meters atm and dont seem to be right (except when it is in density mode)

[vicious_angel]

Hi there,
I take different rms values between span and TT dynamic range from brainworx.

Edit: Also the correlation meter is somewhat slow comparing it with the brainworx one.

[Aleksey Vaneev]

SPAN accumulates RMS value until reset.

I will make correlation meter a bit more "quick", but I do not see this as a very important thing, because average correlation is what matters more - not an instant correlation.

[vicious_angel]

Well i mean if i reset it to a point of a song that tt dynamic range shows -8rms span shows somewhat -9 -11.

[Aleksey Vaneev]

To my knowledge, SPAN shows RMS statistic correctly.

[contrary]

Which is which ; Pure is AES-17 or not ????



I've never quite got the whole point of that one aleksey, what is your take on why they wanted to add the 3db ( sorry , probably just my little brain can't grasp !! )

[Aleksey Vaneev]

"Pure" is a pure mathematical metering, without any biasing used.

I do not know why anybody wants 3dB adjustment - be it for peak or RMS reading - it's due to a lack of good understanding I think.

[bugbug]

[tibenmik]

My favorite analyzer...loving the update (Mac version at last!)

I'd like to address the K-Meter functionality as this plug is potentially *the* (only?) freeware cross-platform K-Meter.

I've had PSP's VintageMeter serve K-Meter duties for a long time, but I do work cross-platform (Mac/PC) so I'd love to switch over to SPAN v2 as there is currently no Intel Mac version of VintageMeter.

I have VintageMeter set up as follows: VU mode, 600ms integration time, 0vu reference set to taste (i.e. -14dbFS for K-14). In SPAN v2 I set the meter to 600ms integration time, 600ms release time (as per Bob Katz's guideline to have the release time mirror the integration time), and peak level hold time to the lowest value (100ms). I set the peak hold time this way to approximate the K-Meter idea of having the peak level and average level viewable at the same time on the same meter; it's set to the lowest value so that it refreshes more like a "live" peak meter (so it'd be great to have this value go even lower!).

Having done all that (and after feeding in a -14dbFS 1KHz sine tone from mda TestTone to calibrate both meters to K-14), there is a difference between what VintageMeter shows and SPAN v2 shows.

With the -14dbFS 1KHz test tone, both meters correctly point to 0. But when monitoring a drum loop peaking at the 0 point on VintageMeter, SPAN v2's meter (right side of the GUI) reads about 4dB higher. However, the values in SPAN v2's "RMS" section display around 0, mirroring the readout from VintageMeter.

If SPAN v2's ballistics are accurate to K-Meter specifications, than perhaps the VintageMeter has always been showing values 4dB higher than they should be. If not, is there a way to resolve the 4dB discrepancy? If there's a better way to set up the integration time etc. please let me know. Also, feature request wise, it'd be great to have a dual scale on the meter in K-Meter mode, perhaps K-Meter on the left of the meter and dbFS peak scale on the right...

Great work Aleksey! Will be following your progress with great anticipation.

[Dandruff]

With the -14dbFS 1KHz test tone, both meters correctly point to 0. But when monitoring a drum loop peaking at the 0 point on VintageMeter, SPAN v2's meter (right side of the GUI) reads about 4dB higher. However, the values in SPAN v2's "RMS" section display around 0, mirroring the readout from VintageMeter.

Maybe that's the 4dB red level as explained by Bob Katz?



-> you see, at +4dB the meter goes into the red. not at 0dB!


I didn't try Span2 yet but Elephant 3.5 perfectly matches RME's DIGICheck (with Weighting Filter disabled) and REAPER (with 600ms Window size, 3dB display gain as per AES-17 and 4dB Red treshold).

[tibenmik]

Thanks for the comments, Dandruff. The VintageMeter was always an *approximation* of K-Metering (a deep search on KVR will reveal past threads on this). Still, the same programme material should be hitting 0 on both after synchronizing calibration.

I checked a section of a 2 channel mixdown in REAPER v3.31 (Mac), with REAPER's master meter set as you described and still see a +1.5-2dB difference in SPAN v2.