From the original SynthMaker forum (2004–2014), with its members’ names and dates.
exonerate ·
right i done another version, using edit boxes. i'm more than sure the frequencies are NOT correct.
whats confusing me echopark is you have stretched the splitter out for it to show the right frequencies but this shouldn't make a difference, because percentage wise if you had the high band set at quater of the way up, and then you had it set at the same on a splitter that was twice as long you would get the exact same value on both.
now on this version the frequencies to me look totally wrong but the edit box shows 500hz at nearly half way which i take it is right. i have got the frequency values by turning the 0-1 value to a logarithmic scale which you have to do to get the freq value. so in theory this one should be right, the 0-1 is no longer logarithmic and it set the way you had it echopark, so maybe it's ok, but for me the high band is ok but the low band is totally off, i got a lot better results with the log10 . this is more than confusing me now
link....http://www.box.net/shared/p27istvaik
cheers
echopark ·
This drag box is a better solution than the labels I think.
I found a little bug: I simply connect a VSTi Synth and when I doubleclick the
editwindow for the Low Band and type in 100 then you hear a short click and the module lost the sound.
Maybe you can change to the "return key" to confirm a new value in the editbox. I think most vst does it this way.
whats confusing me echopark is you have stretched the splitter out for it to show the right frequencies but this shouldn't make a difference, because percentage wise if you had the high band set at quater of the way up, and then you had it set at the same on a splitter that was twice as long you would get the exact same value on both.
No,I didn`t stretch to show the right frequencies, I only wanted to show that
changing the size is also a good solution to get a better resolution.
With a bigger gui size you can make finer adjustments because the way from
100 to 200 Hz is now longer.
right i done another version, using edit boxes. i'm more than sure the frequencies are NOT correct.
You`re right , I tried to read out from my voxengo analizer:
I don`t know why the High and lowpass have different values.
Is it maybe a solution to send another values to the drag box then to the filter ? For example a multiplier with 10 only before the dragbox.
the filter cutoff input get the version without a multiplier.
echopark ·
I don`t know what happened, now better to read out.
Hallo exonerate, I don`t know who did this shelving filter, but theres a readout box. I tested it and it shows the freq very accurate. Maybe you can take a look inside.
http://www.box.net/shared/c3xr51p0u4
exonerate ·
Ok thanks for the example,
the example is making me think that the problem with the freq is something to do with the filters them selfs, in the example you have show, the 0-1 value from the knobs is turned into a logarithmic scale the same as is shown on the edit boxes, and then in the example the scale is then turned into a 0-1 value inside the code component. the filters i'm using actually take a 0-1 value as the input, instead of turning it into a 0-1 value inside the code component.
anyway i've done another version and in this one the low band look to be better and the high band is ok but the mid band is still fairly large, this is because i'm having to use different scaling on the low and high band, so for the middle band when the points are at the same postion the low and high band will have a slightly different cutoff value causing the mid band to be wider. sound wise i think the splitter now sound about right the mid band does let a bit to much through but i think it sounds Ok.
its weird that the low and high bands have not been responding the same because they had the exact same cutoff values, now they are a bit different the low band is better but like i said because they are not the same the mid band suffers from this.
i'm thinking that the best thing we can hope for now with this is that it 'sounds' about right, i'm not sure why we've been having these problems because all filters use a 0-1 value for the cutoff, and i'm feeding it a 0-1 value so i can't see where the problem is coming from. obviously if the cutoff value is the same on both bands then that should mean that both the low and high bands cut off at the same value, but for some reason this has not been the case .
heres the file....
http://www.box.net/shared/p27istvaik
this one should be better on the low band but the mid band is now a bit bigger.
cheers
echopark ·
Edit box works now like it should.
The highband is great now ! The edit box shows now a value that match with my Analizer.
Maybe you find solution for the bassband.
exonerate ·
Ok i'll try a bit more tweaking, and see if i can maker it better, is the low band still far out for you?
cheers
echopark ·
I liked the version with the smaller midband more, but I can live with it.
exonerate ·
Ok i've had another play around with the frequencies, and they look about right to me, the mid band is still quite wide but i'm pretty sure there not much that can be done about that now.
heres the file...
http://www.box.net/shared/p27istvaik
cheers
echopark ·
I think it`s time to find a new home in the wiki for the Freq Splitter.
Now it shows the low freq also very good. well done !!!
Wrote something here? To have a post removed or your name hidden, write to [email protected].