]]>
I have also started an 'official' thread in the additional packs section of the forum so people can find it easier and if anyone has questions they don't have to read through all my discussions about using the SDK
Statistics: Posted by caco — 06 Sep 2010, 10:14
]]>
Of course, X/Y is the solution for control parameters, but for drawing the result curve of Three filter... I dont have any ideas.
Statistics: Posted by multiphone — 03 Sep 2010, 18:46
]]>
Statistics: Posted by Floego — 03 Sep 2010, 16:03
]]>
But, if i want to create my own EQ 3 Band with three biquad for exemple the problem is to draw the result of the filter curve.
As you see i use the bitmap in and out:
but, maybe i'ts detail for now, beacose the major use of this filter are for me sound design first and not sound ingeneering.
Statistics: Posted by multiphone — 03 Sep 2010, 14:54
]]>
cool!
The logscale is, from my point of view, more appropriate since there is generally more audible difference between [0..5%] than between [90..95%]?
Moreover, the most important is to keep the same behavior with all the filters, especially regarding the built-in filter of Usine, They should have the same look and feel, be homogeneous?
Also, I have noticed that in the StateVariable you only draw the low-pass curve. Maybe you can add a selector (combo-box) to choose which curve we want to display?
senso+++
All done The logscale is, from my point of view, more appropriate since there is generally more audible difference between [0..5%] than between [90..95%]?
Moreover, the most important is to keep the same behavior with all the filters, especially regarding the built-in filter of Usine, They should have the same look and feel, be homogeneous?
Also, I have noticed that in the StateVariable you only draw the low-pass curve. Maybe you can add a selector (combo-box) to choose which curve we want to display?
senso+++
All filters now use a log scale for resonance and the state variable filter now offers a choice of plotting low, high, band or notch outputs.
I think I will leave the frequency bands fixed in the SVF EQ. The reason for this is that it is a cheap trick with the SVF filter to create a three-band EQ yet only use the CPU usage of a single filter. The bands can not not be altered seperately as a single SVF has just one cutoff. Raising the cutoff would increase the frequency for the low band but warp the frequency width and position of the mid and high band. I have picked the current setting as they give similar sized high/low bands using a log frequency scale with the mid band positioned midway across the frequency range.In State variable EQ: I'ts sem to be very nice to choose the frequency of LF, MF, HF ?
To create a true three-band EQ use three of my biquads - a lowshelf, highshelf and peaking filter in series and then all three bands can be individually set. The only downside is that you get three different displays then.
Maybe I should add a separate three band EQ to the pack made up of three biquads? It just creates a large module with a lot of parameters for the user to set though - 3 x gain, 3 x frequency, 3 x resonance, master gain etc. In a modular host like Usine maybe people should just create their own from my filter modules? Is much more flexible that way
download filter pack here
Statistics: Posted by caco — 03 Sep 2010, 13:39
]]>
First thanks for your great job on filter. This filter offer to Usine a new "sounds colors" and that's for me the most important things. I'm making sound tests with your filter and i have some comments.
In State variable EQ: I'ts sem to be very nice to choose the frequency of LF, MF, HF ?
For the drawing of state variable EQ you draw the result curve of three filter or only the LPF as Senso say ?
Statistics: Posted by multiphone — 03 Sep 2010, 11:50
]]>
@Senso - Thank you for the feedback. I have removed the blank parameters from the state variable eq and changed the resonance to log scale in the biquad filter. Do you think all filters should have a log scale for resonance? So far they are all exp apart from the new version of the biquad.
cool!The logscale is, from my point of view, more appropriate since there is generally more audible difference between [0..5%] than between [90..95%]?
Moreover, the most important is to keep the same behavior with all the filters, especially regarding the built-in filter of Usine, They should have the same look and feel, be homogeneous?
Also, I have noticed that in the StateVariable you only draw the low-pass curve. Maybe you can add a selector (combo-box) to choose which curve we want to display?
senso+++
Statistics: Posted by senso — 03 Sep 2010, 10:57
]]>
]]>
@martignasse - the sdk is very usable, it makes it easy for me to expand Usine for my needs and create new modules quickly and easily. Thanks for all your advice
I may add another few filters I am working on soon but in the meantime I will have a look at how to add a page to the wiki to document all the filters next.
And after that I have a few other modules I would like to add...
Statistics: Posted by caco — 03 Sep 2010, 09:48
]]>
and a great demonstration of the SDK usability
Statistics: Posted by martignasse — 03 Sep 2010, 08:39
]]>
Biquad : Q could be with a logarithm scale?
other filters: Q could be with a logarithm scale, (actually exponential)?
In the state variable EQ, 3 parameters are empty (blank caption)?
Statistics: Posted by senso — 02 Sep 2010, 22:12
]]>
Also updated all the other filters so that they should now pay better attention to samplerate changes
Download filters here
Statistics: Posted by caco — 02 Sep 2010, 14:18
]]>
]]>
@Senso or Martignasse - At the moment I am getting the samplerate from TMasterInfo during InitModule. What happens if the user then changes Usine's samplerate and how do I get updated about this? Does InitModule get called again or do I have to check elsewhere that the samplerate has not altered? In the VSTSDK you would generally check the samplerate during calls to suspend() or resume().
pointer to TMasterInfo is stored in TUserModule->m_masterInfo (protected member of the module base class) at init(). So, in your module, you can make a method to query the samplerate from it. Normally, the info should be updated in TMasterInfo when changed by usine, tell us if it's not the case.Hope it help
and good job on module UI, those filters are rocks
Statistics: Posted by martignasse — 01 Sep 2010, 17:57
]]>
]]>
Download Filters
Still have a few more filters to add next..
Statistics: Posted by caco — 01 Sep 2010, 15:02
]]>
Still got the Biquads and SVF EQ to finish off
Download Filters
@Senso or Martignasse - At the moment I am getting the samplerate from TMasterInfo during InitModule. What happens if the user then changes Usine's samplerate and how do I get updated about this? Does InitModule get called again or do I have to check elsewhere that the samplerate has not altered? In the VSTSDK you would generally check the samplerate during calls to suspend() or resume().
Thanks,
Martin
Statistics: Posted by caco — 01 Sep 2010, 10:04
]]>
]]>
]]>
Sorry i'm in another planet the two last days.
Very nice ! And thanks for your job !
Very clear and elegant now.
Statistics: Posted by multiphone — 01 Sep 2010, 00:26
]]>
It turned out to be a good learning experience for me to understand the FFT process in more detail so I am pleased that multiphone asked for the display. Now on with the rest of the filters..
Statistics: Posted by caco — 31 Aug 2010, 17:42
]]>
]]>
I will remove them from future versions.
Statistics: Posted by caco — 31 Aug 2010, 17:13
]]>
CODE:
'index color''index width'Statistics: Posted by senso — 31 Aug 2010, 17:08
]]>