Collaborative project!

[ustk]

TODO LIST

1 - Add logos (Still need Lalaland)
2 - Add PresetBrowser LookAndFeel so the items don't look that tiny... ()
3 - Key Range to set

The rest is in process, or still to be decided below:

=> Let's keep the size as it is, right?

=> I'm pro keeping the stereo as it is, so let's forget that? (stereo wideness setting could be another possible pro feature)

=> The IR I imagine was meant to calm down the Leslie saturation since you asked for a kind of grit, but it could stay as it is already ;)
But keep in mind the IR is almost mandatory if we want some sort of saturation, or it'll sound shitty...
@lalalandsynth Since you ave access to a real Leslie, if you want to do it, the only thing you have to do is use Voxengo Deconvolver and record a sweep through the most linear mic/preamp couple you can, or better, the mic that is generally used for this purpose.
https://www.voxengo.com/product/deconvolver/ (the demo version is enough)
For this, you need to connect the source directly to the Leslie amp (I have no idea what input it has).
The ideal would be to remove the panel and orient the horns toward the mic which is at 30-40cm
Do it for both transducers separately.
I've found a video:
https://youtu.be/h6qZoC7W_EQ
If you can't do it, no problem!

=> @hisefilo The LookAndFeel is an API Christoph added "recently" so you can access element objects to customize further, compared to using the limited property editor.
It's all done in script, no need to touch C++
https://docs.hise.audio/glossary/custom_lookandfeel.html
I'm on this part then ;)

[d.healey]

Does the user ever interact with any of these controls? Also, all of the C5 and C7 controls and inaccessible.

[ustk]

@d-healey For the holder, you can use my company name so Studio427 Audio

[hisefilo]

Does the user ever interact with any of these controls?

@d-healey Nope, but I do :)

[hisefilo]

all of the C5 and C7 controls and inaccessible.

@d-healey yes, need to change panel height. but didnt since not need to touch that at this moment.

[d.healey]

@hisefilo That's a lot of components that nobody uses :p I don't know if that will slow down the plugin. We could replace all of them with a few sliderpacks

[hisefilo]

@d-healey said in Collaborative project!:

@hisefilo That's a lot of components that nobody uses I don't know if that will slow down the plugin. We could replace all of them with a few sliderpacks

Yes, don't know if it worth it now since we are on 1%~2% CPU usage on compiled. But yes, slider pack is the guy

[hisefilo]

@d-healey do we wait for you to commit something?? or I can still pushing??

[d.healey]

@hisefilo You can keep going. I'm working in a different branch.

[hisefilo]

I guess release noises are too loud. Don't know why but I need to test it compiled to get to this conclusions :P

[d.healey]

I've uploaded my code cleanup branch. So far I've just done the leakage script. Let me know if I made a mistake.

[ustk]

@hisefilo That's strange because I put click noise down last night
They are a lot quieter here... Are you sure you pulled the last commit?

[ustk]

@d-healey Leakage seems to work fine, and the project is way quicker to load

[lalalandsynth]

I havent had time to do anything today !
Just wanted to pop in and ask if the note burst issue is gone ?

[hisefilo]

@lalalandsynth never happened at my end so can't tell. Can you try the last commit? no rush

[d.healey]

I've pushed the cleanup for ScriptProcessorMain.js. This one was more complicated so please test.

[hisefilo]

@d-healey I'm away from my keys. will test itb later :)

[d.healey]

@hisefilo Cool, if everything turns out to be ok I'll merge it into the master branch

[hisefilo]

@d-healey if console doesn't claim, should be fine I guess. :)

[d.healey]

@hisefilo The console is fine but I might have messed up some of the pitch/gain/decay values or the interaction between the controls and the modulators - I don't think I have but it's nice to have a second opinion.