For Damper, I also don't like that behavior but so far I am not smart enough to figure out how. Oversampling, we're trying to do "as much oversampling as we need" but we can let you force it on/higher for sure. For the varispeed, I'm also not smart enough to do it in real time - maybe if we load the sample into the plugin, I dunno. I'll put all this on the roadmap !!
Sure. It does lots of research, especially for math papers and things that I'm unable to find like repair manuals, published numbers, things like that. It explains the math / algorithms to me (for example, I don't know calculus very well at all, so I need handholding). In terms of "how much of the code does it write," I don't have a percentage for you but generally if it suggest something to add to the testing suite I will allow it and if it wants to make changes based on a code review I will allow it. For bug hunting or "why doesn't this sound right" analysis, I make audio files (say, a guitar recording or a drum loop) and have the AI analyze deltas so it can give me information about what might or might not be happening. There are only two people working on this, so we let the AI keep track of roadmaps (like if I get an issue on Github or a comment in this forum, I might say something like "don't let me do a release without addressing this: [comment]" or "remind me that I wanted to research such and such." I'm a software engineer as my day job, but I'm sure that I would not have been able to do this without AI. I understand that AI can be a touchy subject and that's why I chose to not charge anything. There are a couple of other audio-related things that I haven't put out yet that are almost entirely AI from start to finish.
I hope that helps and doesn't turn you off too much.
yoyo, I don't have a Mac myself, but it SHOULD be working as far as I know now. The only thing I could find was that I had the build arbitrarily set to 11.00 and up - If it still doesn't work lemme know and I'll see if I can figure something out
Thank you so much!! From what I understand, what I want to do is similar or perhaps even the exact same thing as those other things - just let you have more or less "a console channel" without making you put a bunch of stuff together yourself. Essentially, put everything in WD Strip. I'll put out the decap preview tonight if I can !
It's hard to find real numbers for the Kush unit - we can defo do something that you could describe the same way that you could describe the Kush, but it surely won't be a faithful representation. I'll put it on the list and see where we can take it.
I love getting requests, so feel free to request any and everything you want !! For the UI stuff, I need to take a gander - I still don't really love the UIs and it's definitely a weakness for me.
As for what's next, currently there's a Soothe-type of thing in the pipe that I'm trying to figure out, a Decapitator-type thing, and a plate reverb. Trying to make progress with the Digital plugin suite but UI is much more important there and I'm bad at it :( Thanks for your comment !!
Noise is a weird one; the chips are noisy but the circuit is also designed to defeat the noise as much as possible so the knob doesn't do all that much.... I'll see what happens if we make the knob do more. HPF and LPF will be there next release, new Strip update, maybe a new thing. Maybe tonight. Maybe. Thanks!
A lot of it is like once you have "a thing" like al algorithm that describes a tube for example, it's a lot easier to just use that again and again and it takes so much less time than making a whole new thing - like you make one VCA compressor and the next 5 are 90% done already. SO as we get more and more "components" like preamps, transformers, eq, whatevers, it opens up more and more lower-effort things. Like dolby is basically just an eq in front of a preamp and then another eq after it etc etc. It's like building a bigger and bigger collection of legos in some ways. It's also why I will probably never end up doing anything super unique or revolutionary... all this stuff is stuff other people figured out a long time ago and we're just translating it.
I can probably make Delta work faster to let you gain match anything you wanna put between the send and return on wet mode, if that helps. Another thing I'm trying to figure out is "what would Soothe be like if it was all analog." Dolby is also in as WD 361 but I didn't update the page yet. A type is Dolby A-ish, Broadband is the dbx implementation of the same idea and it's a little weird imo - it does a lot and it's really slow to let go so it has a really alive feeling. B is Dolby B-type which is like the cassette tape version.
Thank you thank you thank you !! I think all of that stuff is address in... whatever version is next. 0.7.6 maybe.
Your comments have been a big help; it's awesome to hear from people from the outside who don't necessarily know what all this crap is supposed to be doing. I'm pretty pleased with a lot of the plugins, but I'm still not really happy with the "sound like a cranked console channel" solution yet. As it turns out, people who do this for a living are pretty good at it.
If you're interested, this is the other thing that's in the works. It's all pretty early. I think it's perhaps "more useful and less exciting" than all the analogy stuff. Thanks again
For no reason in particular, the build is set to require Mac OS11 - I don't think we need to do that so we'll get a release out tonight to remove that requirement if we can. Thanks for letting me know
Hell yeah. Rack + Channel + Summer Channel + Summer Bus is basically supposed to do what you're saying, but I really haven't done a good job explaining all that. It probably needs to be condensed into less things and be more clear what you're supposed to do with it - it prob could use a rework and some rethinking.
We got spring coming up for sure, and I'm pretty sure we've got all the components needed for Dolby scattered across various things so we can surely put that together. And more!!
heyhey, 0.7.2 is going up now - hopefully all these fixes work for you! thank you so much for trying it out, your kind words, and your bug reports. There are a couple more things in the works, but I'm just curious - if we could make anything next, what would you want it to be?
I did a little bit of research, it's POSSIBLE that the new version references some new DLLs that the old one didn't and the new ones need a newer version of the C++ runtime. You might try updating aka.ms/vs/17/release/vc_redist.x64.exe to see if that helps. We'll start bundling that with an installer in the future just in case. Good luck
What happens when you try it? I should have 2025, I will check it out asap
edit: Hey, I am able to load all of them in FL 2025 - do you think you'd be able to locate an error log that I could look at? I might also try doing a rescan with verify. If there's anything else you can tell me, I'll try my best to get it taken care of
