Inspector

This may be a post for the bug forum but I can’t rule out that I might be doing something wrong.

Inspector is a monitoring plugin that lets you see the levels (peak and rms) and a spectrum anylizer. My problem is that the spectrum view is blank. Once I could see the spectrum for about 2 seconds but it updated like every 10 seconds. I have a 2200MHz AMD with 512MB of ram so it should not be a hardware issue. The level meters are working fine.

I’ve seen people talk about inspector on the board before. I believe that was you marc. Do you see the spectrum?

I’ve also tried some of the other plugins from elemental audio systems and they produced strange graphical errors and even caused renoise to crash to desktop without notice… so it does seem as this is a line of either very crappy plugins… or maybe a bug in Renoise.

Anyway. I would really like to get this plugin working. I would settle for a similar plugin so if anyone has a suggestion I would be grateful.

Hey Phonkey… here’s a nice almost-free vst spectrum analyser
have a look… maybe it can be usefull

Inspector works perfectly for me in Renoise, as do all off Elemental Audio’s plugs.

same for me, works perfect.
try playing around with the processbuffersize, a bigger or smaller value might fix your problem.

i think this post belongs into the bugs department, cause since you can set the processbuffersize in renoice (was it release 1.2?) it seems impossible to get all plugs working. some setting will work for some plugs but brake others, an other setting fixes some plugs but brakes others…

Well, I’ll be damned. Thanks marc!

I’ts working fine with buffersizes 512 and 1024. strange…

glad i could help
i wonder how that internally works… ok, ffts of course need an certain minimum amount of samples to calculate something (512 in this case?), but doesn’t a plugin handel the filling of it’s internal buffers by itself, not having to rely on the host sending right-sized chunks?

doesn’t a plugin handel the filling of it’s internal buffers by itself,
not having to rely on the host sending right-sized chunks?

that’s the way it should be, but not all plugins follow that rule…

i see, so it’s the plugin’s fault. i just wondered if renoise probably forgets to tell the plugin the current size of the processbuffer (if something like that is specified in the vst protocol), so it has to make an assumption on the size of the incoming chunks? but then again, it’s the plug’s fault if it can’t properly count

Some plugs already have a hardcoded fixed buffersize in Renoise. This is obviously hacky, and not ideal at all. But it works.

must be a real hell to cope with all those non-standard-following plugins out there i guess…
there is such an big amount of different plugins floating around on the net… why don’t you make that hacks aviable to the user with a config file for example? then people could try to fix a faulty plug by themselves, saving you some work?

why don’t you make that hacks aviable to the user with a
config file for example?

I just suggested that to taktik myself
We could possibly have an xml-file where buffersizes could
be set. This shouldn’t be available through the GUI anyway,
because you ought to know what you do if you edit it.

I dont really like the idea. Its not THAT many plugs that need a static buffersize and as soon as someone reports of such a plug I will add it as usual for the next release.
Having a XML file and an option is something I would like to avoid to show the user. Normally he shouldnt care. Only we should This makes things easier and stops people from f****ing up their settings by accident cause they dont know what they do …