Collaborative project!

[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 :)

[ustk]

@lalalandsynth Looks amazing man!

[hisefilo]

@lalalandsynth wow man! I like it a lot!!!!!!!!!

[lalalandsynth]

@hisefilo great , still needs some work but its definitely getting there .

So , top menus will be enough , right ?
For Settings and presets.

Notice the top right corner on the controls panel ;)

btw, I will prepare all graphics , test etc and then I think its smart if I wait and work on the final Hise project .

[hisefilo]

@ustk if you take a look to the super simple ugly thing I did, I'm using fix16 and no oversampling at all and no glitches. (turn it on, is already on the patch)

Are you on 30Jan2020 or later HISE??

[ustk]

@hisefilo Yep I'm always on the last working version

I know where I need to put it (I often work directly in the xml in order not to loose the mod connections) but it just crashes in this graph.

Even just removing the frame and oversampling crashes hise...

[hisefilo]

@ustk well maybe we can just resign that CPU usage (10% at my end) and go ahead. IMO your Leslie on position 1 (slow) sounds AMAZING!!! I guess faster need that pitch crzy thing get fixed. but we are almost there

[hisefilo]

@lalalandsynth i was thinking in >> settings >> presets >> contributors (a panel with names, links, logos, also some link to WHO or anything that we want ) and also a place for #StayHome hashtag

what do you think??

[lalalandsynth]

@hisefilo Yes, that sounds cool .

[lalalandsynth]

@hisefilo Can you guys send me links,names, website links and Logos?

[lalalandsynth]

Ok, I am off, been on this all day :)
Need to fix some shadow issues but yeah.. :)