Closed elanhickler closed 7 years ago
hmm - i'm not getting these warnings. this is warning level 4, right? in what project do they occur?
spiral generator. couldn't you just not divide by zero? not good practice i think.
#define INF (1.0/dummyFunction(0.0))
whyyyyyyy
Edit: do a fresh build (delete build files) to get the warnings.
not sure anymore why i did it this way. this is code from about 15 years ago. can probably be replaced with a better expression now, like std::numeric_limits
...and could you use your modified envelope-generator class from your folder, so i/we don't always have to replace the file in my library?
...and could you use your modified envelope-generator class from your folder, so i/we don't always have to replace the file in my library?
Don't know how to do that without compile errors. Was planning on eventually wrapping the envelope generator class.
Yes I'm using your latest commit.
Just got your LATEST latest commit, I think I am not getting the warnings anymore. Will keep an eye on it.
good. i have now set the warning level for my module to 3 (corresponding to "medium" in projucer) in the code. level 4 (high) complains a lot about things that i actually consider non-issues
Don't know how to do that without compile errors. Was planning on eventually wrapping the envelope generator class.
hmm...should i try to do that for you? ...for free, of course - i think, it should be a small thing
edit: i mean not the wrapping but using a different file
i think, it will just be a matter of renaming the class (maybe use a prefix "se" or "eh" or whatever you like) and adding it to your synth-framework. ...and then using the renamed class instead of the original one in your project
yeah you could try it for me. I tried it and got stuck.
so, it is the file rosic_EnvelopeGenerator_elanEdit.h/cpp in Shared/EalnSynthLib, right? i think, there are at least two options:
(1) just manually add the files to each jucer project where they are needed (as you have done with ElanSynthLib in SpiralGenerator)
(2) wrap the code into a juce library module - i specifically created the se_framework library module for that purpose. it currently contains only the licensing code, but the idea is that you could put customized (shared) dsp-code, gui-code, utility-code, etc. there, too. i would propose to make a folder dsp in se_framework and put the envelope generator code together with ElanSynthLib. then you don't have to bother with manually adding the code files to your jucer projects. you just add the se_framework module to the module list and drag in all code at once
I already tried (1), was hoping you'd give it a shot. Adding to the jucer project is trivial, that's not the issue.
(2) No idea how modules work, I can learn about that another time.
done.
...oh...just fixed a little bug
haha! it's fun to play with the parameters of spiralgenerator. i'm getting funny sounds out of it!
...but i think, the funniness of the sounds is mostly due to the pitch detoriating in weird ways when tweaking parameters
Pitch deterioration is good for fx. Also you should be using spiral generator with a 2d scope, everything makes a lot more sense. But I plan on addressing pitch deterioration. There are interesting timbres that are desirable but unfortunately tied to the pitch deterioration.
yeah - using a 2D scope for sound analysis and design is probably something i should do much more anyway. i like it when synthesized sounds are intrinsically stereo
ok thanks for sorting out the envelope issue.
My code is a bit of a mess, I'll be cleaning it up for the next version.
I'd like to release a paid version of Spiral Generator with anything to anything modulation and other features, but I am waiting for you to give me GUI features. Also it needs polyphony.