Collaborative project!

[lalalandsynth]

Lower panel interface .
Need to work on the material, a bit too clean maybe.
100% Orthographic as is , its possible to have some perspective ?
Light reflections and materials tend to look a bit better with some perspective.

So, rotary knob on the left is Leakage , and the one on the right is Volume.
Leaving a bit of space for markings . 16´ 8´ etc.
Doing this in Ipad compatible resolution.

[hisefilo]

@lalalandsynth wwow looking super cool. yep. but scratches and desaturation can de added on Photoshop. I think this is getting super cool. Don forget place for labels (slow stop fast on rotary) . don't know how perspective will work. u are the Master Jedi

[hisefilo]

@lalalandsynth @ustk what about naming? BFree looks commercial in some way. any ideas?

[hisefilo]

@lalalandsynth texture reference

[d.healey]

I don't know if it will improve performance but I noticed a few of your scripts have 2000+ lines of code but a lot of it is the same stuff repeated. This could be written in a lot less lines.

[ustk]

@hisefilo said in Collaborative project!:

@ustk Working here!!!! Still like a "theremin vibrato" like. or it's me?

Is it something obvious or just fine-tune? Because it seems rather ok here...
An audio example maybe to see if we are speaking about the same thing?

@ustk I can tell smoothing that may work.... but cannot find the node to try that!!!

No no, just changing the modulated value range is enough...

[ustk]

@d-healey Yes, I noticed that too... Also, many of the big 2D arrays (leakage) can be replaced by just a unique value.
The loading time of the project is rather big on my mac (i7 3.5)

On my side, I still haven't found a solution for the Leslie and the frame issue... I'm still on it though ;)

[d.healey]

@ustk

I still haven't found a solution for the Leslie and the frame issue

I'm not up to date with everything you've been working on. What's the issue?

[ustk]

@d-healey In fact, I know what I have to do, but it doesn't seem to work... I need to replace a frame2 node for a fix16block, which should help the CPU... But I get straight crash each time. I on a workaround...
There's a second workaround, which is exporting as a custom node, but this means that everyone needs to activate the corresponding flag in the Projucer and download the said custom node...

[ustk]

@hisefilo Now I think I see what you mean... Each time I reopen the project, the Leslie goes crazy and I don't know why...
So yes the vibrato like effect is garbage, but it's not what I hear when working... Gonna kill this so#$*%of^ç+#tch

[d.healey]

@ustk said in Collaborative project!:

but this means that everyone needs to activate the corresponding flag in the Projucer and download the said custom node...

You could add the .jucer file to the git repo then it will already be setup.

[ustk]

@d-healey Yes but each time you fetch, if the custom node has been modified, you need to replace the customNode.cpp manually in your own directory and recompile Hise, which makes this solution not practical for collaborative projects imho
But once the project is done, this solution is good so people have everything to work with

[lalalandsynth]

Bit of progress , still need to work on materials , most notably now the drawbars.
Added a bit of grunge/dirt , dents in wood etc. Had to remake a few parts .
Getting there.

BTW. Not sure if I can call it Leslie , dont think so.

Also , for the tonewheels , maybe instead of having it a linear slider/knob , make it 5 settings of age from new to old ? Using a knob but make it snap to 5 settings?
And maybe the Leslie should be called Off ,slow, fast , rather then off 1 ,2

[ustk]

@hisefilo Ok so the issue apparently, comes from the ramps. When I reopen the project, the Gains that are controlled by the Ramps don't initialise as they should (These gains are controlling the amount of doppler/vibrato).
This might be an issue of the frame again. because the ramps are outside of it, I have seen a similar issue before (modulating something to/from a frame node always lead to issues)
I could, however, place everything in a frame, but the CPU would rise even more...

[hisefilo]

@ustk it's necessary to oversample it?? artefacts are gone on fix16 block at my end

[hisefilo]

@d-healey yea that's true. Lot of repeating code. You can improve it if you wish :) I don't know if runtime will be improved. At this point CPU is max 4% on compiled

[hisefilo]

@ustk :)

[d.healey]

@hisefilo It might improve initial start up time but I don't think it will have an effect on overall CPU usage since it looks like most of it is GUI stuff.

[lalalandsynth]

Proposed layout.

[ustk]

@hisefilo Nope, I tried to remove the oversampling as well but no luck
With a frame only you still have artifacts (maybe not once compiled though)
And with a fix16, well... I can't use a fix16 successfully in this graph :)