From: Florian J. <flo...@we...> - 2012-04-18 22:54:38
|
Am 05.04.2012 01:31, schrieb Tim E. Real: > > Howdy list, Florian: > > Been busy lately, no coding, nothing to report or commit right now. > > Can reproduce routing bug I mentioned, but haven't found fix yet. > > On April 4, 2012 7:13:48 PM Florian Jung wrote: > >> Hi all, >> >> i'm writing a softsynth offering: FM-synthesis, analog synthesis (both >> combined), unlimited oscillators, a fairly limited number of LFOs, >> envelopes for almost everything... the synth is JACK-only (jack-midi-in, >> jack-audio-out) >> >> now i've some problems and questions: >> >> the (command-line-)UI is... something between crappy and nonexistent. >> manipulating programs currently means editing text files (fortunately, >> they're at least auto-reread but that's still not good enough). >> so i want to add a _proper_ GUI, supporting fiddling with the programs >> etc. what should i use for this? >> i quickly read about OSC, this sounds not bad... >> >> and: i'd like to integrate my synth with muse (not "into". it is a >> standalone synth and should stay one). that is, muse should be able to >> automatically launch an instance (multiple instances are possible, but >> usually not needed, because my synth can serve 16 channels with 128 >> programs. and that's only a MIDI limit, no limit of my synth), and, more >> importantly, muse should be able to launch the GUI of the synth, >> allowing the user to tweak the sound from within MusE. >> >> it would also be great if MusE could store the synth config (that is, >> program data: how many oscillators, which settings for FM, filter etc) >> within the song files. currently, my synth only supports loading >> program-files, but replacing the loading-routine would be no problem. >> > As Robert mentions, for MusE your best (only) option is DSSI right now. > (You could but I doubt you'd want to, make it a native MusE MESS synth.) > yes, DSSI sounds what i want, thanks > Some folks prefer a lighter-weight GUI toolkit for their DSSI GUIs, > such as FLTK. You can use any toolkit you want. > i'll use QT, because that's the only toolkit i can write code with ;) (thanks to muse development ;) ) > DSSI is basically LADSPA with some extra features in a higher layer. > DSSI uses OSC for communication. > > You can open a DSSI synth in MusE with a generic GUI which will show > all of the 'standard' LADSPA-like 'float' or 'int' adjustments. > But the generic GUI will NOT show other special adjustments or settings, > such as Presets. > So one typically opens a DSSI synth in MusE using the native GUI which > shows everything including special adjustments/settings, the exact way > the synth GUI was designed. > did i understand this correctly, muse just launches some executable which will then open a network connection with my synth plugin and communicate? > MusE will (should hopefully) store any such special settings, in the song. > My memory's a bit muddy but IIRC these special settings are communicated > as OSC strings rather than parameters. I'd have to study it again... > > Install the wonderful Calf DSSI plugins and take a look at how MusE works > with them. Try the Rotary Speaker or Organ for example. > > You may recall when Luis G. made his FLAM program, I beefed up our DSSI > to support it. He last reported some settings were not being stored. > Hopefully fixed by now. Check out FLAM. > Still out there, Luis? > > I went to such greeeaaat lengths to ensure all this DSSI stuff worked. > Lemme know if any troubles seen or if more questions... > i will, but first i need to make it DSSI-ready ;) i hope it won't be too hard to change a jack synth (jack-midi input, jack audio output ports) into DSSI? i think both use the "pull" model with "process" callbacks which to the work, right? >> mine can do it all and even combine it. dunno >> about cpu-usage however. >> > Sounds cool. Looking forward to... er... seeing it :) > the synth itself is pretty functional now, and should be bug-free under certain circumstances: if you just generate sound with it, it will be stable if you have too much xruns, or use the in-synth-CLI, it might occur that the synth segfaults, because the communication isn't synchronized properly (the CLI was intended for me as developer to quickly test stuff like the sustain pedal etc) i think i could upload it somewhere soon. btw, i was able to greatly improve the performance (+40% :) ) i have however some optimisation ideas which i think should speed it up even more, but in fact seem to slow it down... maybe someone can help me with these? btw, about that audio widgets library thingy: i dunno what exactly it's for, but i wrote a nice envelope editor widget (supports ADSR-envelopes and has a hold-checkbox) in qt which is _portable_ (not with all that hardcoded and deicsonze-related stuff in the deicsonze-synth). should i add it to the awl (although i actually don't use it in MusE, only in my external synth gui)? if so, how? greetings flo > Tim. > > >> greetings >> flo >> >> > > ------------------------------------------------------------------------------ > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > > |