Thought this one deserved its own thread. Really excellent multi-effect. I love seeing these kinds of theme-driven effects come out.
Question for the Betabuggers, how come just the one knob? There's so much great stuff under the hood. I use Audiomulch, which lets you flip over to a default GUI to use all exposed parameters, but then I don't get to work with Mully's lovely graphics.
For anyone who hasn't tried it, get the Bugpack already!
Cheers,
Steve
Betabugs Chorrosive
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Cheers for the ups!
After discussion on the one-knob subject, Duncan convinced us that one knob was the way to go-- each of the presets represents a different 'starting point' for the "under the hood" settings, so the one knob plus the presets gives you a HUGE palette.
Then, because we know that some people are power-tweakers, we left the other parameters to be editable via automation and so forth.
So, short version: one knob plus parameters is all you "need", and it appeals to people like me who just want to throw it on a track and go. Access to 'hidden' parameters is easy for power-users anyhow, so no need for a million knobs for thos particular users.
Greg
After discussion on the one-knob subject, Duncan convinced us that one knob was the way to go-- each of the presets represents a different 'starting point' for the "under the hood" settings, so the one knob plus the presets gives you a HUGE palette.
Then, because we know that some people are power-tweakers, we left the other parameters to be editable via automation and so forth.
So, short version: one knob plus parameters is all you "need", and it appeals to people like me who just want to throw it on a track and go. Access to 'hidden' parameters is easy for power-users anyhow, so no need for a million knobs for thos particular users.
Greg
-
- Banned
- 6127 posts since 1 Apr, 2004 from Et in Arcadia Ego
I get zippering when I automate the chorosive parameter.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Perfect!
-
- Banned
- 6127 posts since 1 Apr, 2004 from Et in Arcadia Ego
heh.
-
- KVRist
- 152 posts since 23 Sep, 2003 from Oregon
Flofi and SVF2 kill my audio engine. Granted, this is my crap-ass on-board sound at work. Are there any known problems with FL Studio compatibility?
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
To be perfectly honest with you, I'm not entirely sure that any FL Studio beta-testers have come forth to volunteer their services yet. 
No known issues, but that doesn't mean that everything's flawless. Thanks for the report!
No known issues, but that doesn't mean that everything's flawless. Thanks for the report!
-
- KVRAF
- Topic Starter
- 12235 posts since 18 Aug, 2003
Seems to me that an awful lot of incompatability mentions round here are FL related. Maybe FL has some tricky requirements for hosting?
Chorrosive may have some denormal problems. I get a sort of system atrophy after I kill input. Running a constant input of very quiet white noise seemed to remove the problem.
Chorrosive may have some denormal problems. I get a sort of system atrophy after I kill input. Running a constant input of very quiet white noise seemed to remove the problem.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
I'll mention the possible denormal on the Betabugs forum. It's a public forum, so anybody who wants to swing by and share in the madness may do so by clicking my sig and then following the "Bughouse" link on the menu.
Cheers!
Greg
Cheers!
Greg
-
- KVRAF
- 7879 posts since 16 Apr, 2003 from -on the outside looking in
I'd beta for FL if you could use me:Lunch Money wrote:To be perfectly honest with you, I'm not entirely sure that any FL Studio beta-testers have come forth to volunteer their services yet.
No known issues, but that doesn't mean that everything's flawless. Thanks for the report!
WinXP(sp2), FLS
All the bug pack works for me except widebug which reports a missing msvcr70.dll component. I copied the .dll to the same directory as the bugpack, to no avail.
I might offer a couple of bugpack thoughts:
1. Keep the 1 knob gui approach! it is so cool. One reason FL users might not be offering much is because many of these fx come with FL. The strength of BetaBugs (besides the sound
) is that they are so visually easy to use. The guis expedite making sound instead of programming sound parameters for me. In particular, Moneo and the filter Bugpass just hit something visually that makes them great to use.2. For me, in FL, I would love it if the plugin .dll files could have BetaBugs or BB and then the name of the plug. So, "BB Corossive.dll" instead of "corossive.dll" -It is a totally insignificant point, but it avoids name conflicts and makes them easier to find in big plugin lists
3. Keep the 1 knob gui approach! it is so cool.
Who needs the pressure of developing the next all-in-wonder bells and whistles box. Betabugs does simple necessary things, and you do them well. The user interface makes them more powerful for me. Thanks much for these freebies. ..what goes around comes around..
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Cheers, Ouroboros!
- msvcr70.dll should be put into your C:\WINDOWS\system32 directory rather than the bugpack directory.
- we will continue to do as many one-knob plug-ins as possible! From time to time, a plug-in requires more than that, but we try to keep 'er to a minimum.
- We actually tried a few different naming conventions for our plug-ins in the pre-launch phase and in practice, not having a name 'prefix' seemed the better all-around option. At least one of the Betabugs had the same idea as you and preferred that option, but a decision ultimately had to be made, so we went with no prefix.
Doesn't FL have another way to organize plug-ins, or do they just appear as one great huge list?
Greg
- msvcr70.dll should be put into your C:\WINDOWS\system32 directory rather than the bugpack directory.
- we will continue to do as many one-knob plug-ins as possible! From time to time, a plug-in requires more than that, but we try to keep 'er to a minimum.
- We actually tried a few different naming conventions for our plug-ins in the pre-launch phase and in practice, not having a name 'prefix' seemed the better all-around option. At least one of the Betabugs had the same idea as you and preferred that option, but a decision ultimately had to be made, so we went with no prefix.
Doesn't FL have another way to organize plug-ins, or do they just appear as one great huge list?
Greg
-
- KVRian
- 1313 posts since 29 Mar, 2002 from Salt Lake City, Utah - U.S.A.
FL organizes them in one big list. BB corrosive.dll would work much better. All of ouroboros comments are good ones that I would also recommend.
-
- KVRAF
- 12977 posts since 29 Sep, 2003 from Ottawa, Canada
Even if we adopted the BB - PlugName convention, that wouldn't solve it for your other plug-ins. I suggest, rather, that FL make a more flexible way to sort plug-ins.
Greg
-
- KVRAF
- 8389 posts since 11 Apr, 2003 from back on the hillside again - but now with a garden!
wrt to BB MyPlug.. we did think of that once upon a time, but elected to keep them as they are. Most hosts I have encountered show them alphabetically, so they would be grouped accordingly... hmmm.. ho hum!
wrt denormal- I thought I had checked this - there are already some denormal constants thrown in for good measure.. Maybe I should add some more!!
HTH
DSP
wrt denormal- I thought I had checked this - there are already some denormal constants thrown in for good measure.. Maybe I should add some more!!
HTH
DSP
