Dust Analyzer (still "beta") [was: quickie signal analyzer proto]

[Dunc]

Tried using 64bit DustAnalyzer in 64bit Studio One Version 2:
DustAnalyzer crashes the initial startup of Studio One (at the point where it is scanning DustAnalyzer).

I've found the Studio One scan log file, but unfortunately because I have to close Studio One via "Task Manager" after it hangs whilst scanning DustAnalyzer nothing is written to the log file.


On the plus side it's working in Samplitude ProX ok.

[mystran]

Tried using 64bit DustAnalyzer in 64bit Studio One Version 2:
DustAnalyzer crashes the initial startup of Studio One (at the point where it is scanning DustAnalyzer).

Thanks.

I was already going to test Studio One myself, but then realized Presonus forces you to register a freaking online account so you can do an activation just to run a demo, and figured I'd just wait for someone to confirm that there's a problem..

.. well .. I guess I'll have to deal with that non-sense then (why oh why can't they put a "max 1 VST" or some such limit in the free version, ffs).

[brok landers]

>snip< OpenGL is a graphics API (and provided by graphics card drivers), but you should get an error message if there was a problem with that (same thing if your CPU doesn't support SSE2).

ahh, i see.

- did some earlier version work?

i wasn't able to check earlier versions prior the one before 0.5.5, i didn't find the time.

- does that version work in eXT for you?

yes, 0.5.5 does work in ext. the previous version triggered an error on loading and did not load the gui.

- are you using the 32 or 64 bit version?

i use the 32bit version.

btw, now that i was able to have a sneak peek on dustanalyser, there's 2 things i would love to see implemented:
- free resizing of the plugin window
- seperate attack/release settings

just mentioning it, you just do as you wish of course.

[mystran]

btw, now that i was able to have a sneak peek on dustanalyser, there's 2 things i would love to see implemented:
- free resizing of the plugin window
- seperate attack/release settings

Free resize could be nice yeah, but the current code isn't really designed to handle that (well, there's partial support internally, but the current analyzer drawing code makes some compile time assumptions), so making it work would need quite a bit of work. It's definitely something that I'll probably try doing some time in the future, but it might take a while.

As far as attack/release goes.. the way the FFT works (and also how it's implemented in the plugin), I'm not sure if ballistics would really provide much useful information. An FFT is already a bit of an average in some sense, so I'm not sure how the ballistics could provide that useful information.

You did get me thinking about a more "musical" bar-graph style analyzer mode based on regular minimum-phase filtering (rather than FFT) and I think ballistics would be more useful for such a mode.. but I'll have to implement that first and see what happens.

[mystran]

Found (and fixed) a race condition that apparently caused Studio One to occasionally (about 90% of time) to fail (typically hang) the plugin scan. Once the scan succeeds, it appears to work fine for me. Could theoretically have affected some other hosts that do a plugin scan at start-up as well..

Will upload a fixed version as soon as I've checked the x64 build.

[mystran]

Update 0.5.6:
- fix race that was causing Studio One to fail plugin scan most of the time
- added another "phase-plot" mode left/right: works like "normal" but 45 degrees angled (left on y axis, right on x axis); mainly intended for things like wave-shaper debugging (eg plotting "almost memory-less" functions: feed "wet" to left, and "dry" to right, etc..)

[mystran]

Oh btw, here's a Studio One tip (probably most S1 users already know, but just in case) if you'd rather not do a full "reset blacklist" on a folder full of garbage: in the folder "%appdata%/Presonus/Studio One 2/x86" (or /x64 for 64-bit) there is an XML file Vstplugins.settings which one can open in Notepad and find a part that looks something like this:

Code: Select all

	<Section path="2DA22021/Dust Analyzer.dll">
		<Attributes>
			<DateTime x:id="modifiedTime" time="2013/06/06 17:32:18.000"/>
			<VSTPluginInfo x:id="default" smiley=":(" name="Dust Analyzer"/>
		</Attributes>
	</Section>

Removing the <section>..</section> for a particular plugin (and saving the file) will then cause it to be checked on next rescan without having to reset everything else that might have been blacklisted previously.

Please don't blame me if something goes wrong. It worked for me while troubleshooting the issue though. YMMV.

[brok landers]

Oh btw, here's a Studio One tip (probably most S1 users already know, but just in case) if you'd rather not do a full "reset blacklist" on a folder full of garbage: in the folder "%appdata%/Presonus/Studio One 2/x86" (or /x64 for 64-bit) there is an XML file Vstplugins.settings which one can open in Notepad and find a part that looks something like this:

Code: Select all

	<Section path="2DA22021/Dust Analyzer.dll">
		<Attributes>
			<DateTime x:id="modifiedTime" time="2013/06/06 17:32:18.000"/>
			<VSTPluginInfo x:id="default" smiley=":(" name="Dust Analyzer"/>
		</Attributes>
	</Section>

Removing the <section>..</section> for a particular plugin (and saving the file) will then cause it to be checked on next rescan without having to reset everything else that might have been blacklisted previously.

Please don't blame me if something goes wrong. It worked for me while troubleshooting the issue though. YMMV.

to be precise - everything that is between the "<section>delete all this here, too</section> marks. i can in general confirm that this method works, i do this all the time, if a plugin fails to work and is set on the blacklist.
will check the analyser asap...

[mystran]

Oh btw, here's a Studio One tip (probably most S1 users already know, but just in case) if you'd rather not do a full "reset blacklist" on a folder full of garbage: in the folder "%appdata%/Presonus/Studio One 2/x86" (or /x64 for 64-bit) there is an XML file Vstplugins.settings which one can open in Notepad and find a part that looks something like this:

Code: Select all

	<Section path="2DA22021/Dust Analyzer.dll">
		<Attributes>
			<DateTime x:id="modifiedTime" time="2013/06/06 17:32:18.000"/>
			<VSTPluginInfo x:id="default" smiley=":(" name="Dust Analyzer"/>
		</Attributes>
	</Section>

Removing the <section>..</section> for a particular plugin (and saving the file) will then cause it to be checked on next rescan without having to reset everything else that might have been blacklisted previously.

Please don't blame me if something goes wrong. It worked for me while troubleshooting the issue though. YMMV.

to be precise - everything that is between the "<section>delete all this here, too</section> marks. i can in general confirm that this method works, i do this all the time, if a plugin fails to work and is set on the blacklist.
will check the analyser asap...

While debugging, I actually had to use it to force rescan when a plugin did NOT get blacklisted (because if it previously passed, then it would work happily ever after since it wasn't blacklisted so "reset blacklist" would do nothing.. even if the scan would fail 90% of time).

[mystran]

Oh and .. at least "my version" of ILBridge (FL 10.something) is currently broken again (trying to run in "bridged" mode in relevant FL versions can cause the plugin to hang on startup). I suspect it's a timing-sensitive bug in the bridge though, so might work with more recent versions (should update and see, but updating FL tends to take half a day).

[brok landers]

have you uploaded the new version already? i don't see a comment on the initial post...

[mystran]

have you uploaded the new version already? i don't see a comment on the initial post...

yes, I uploaded before posting about 0.5.6.. just forgot to copy to the OP.

[brok landers]

mystran, btw, check your pm...

[mystran]

mystran, btw, check your pm...

Does the analyzer work now, though?

[brok landers]

just tried it - sadly no. still the same behaviour as 0.5.5. s1 doesn't scan it, it's like it isn't existing at all... ist's working in energy xt, used as a subhost though...