KVR Audio

bengeorge · Post by **bengeorge** » Thu Jan 11, 2007 8:54 pm

dose bro, i hope you understand how important a good gui really is. it's not "fiddly" stuff, it's crucial.

what to you is the most exciting development, besides the GUI?

(looking at the todo list)

oh.. the beers? that IS pretty exciting!

aciddose · Post by **aciddose** » Thu Jan 11, 2007 9:37 pm

the single most exciting part for me is:
- 'state' patches
- a storage format for routing information (which would also be stored in a 'state' patch)

this means you'll be able to save the entire state of xhip (including routing for ccs, velocity, etc. pcm waveforms, voice configuration, everything) in patches and banks. that in turn means i'll be able to implement the storage of all this in vst chunks meaning fxb files will work, meaning in turn the information stored in project files will be full. this in turn means i'll be able to implement proper versioning information for all that stuff and the information in project files will then be loaded correctly in future versions.

so, that'll make it possible to use xhip in projects without worrying. infact, xhip will then be even more stable than most commercial plugins are between versions.

the gui is important from a user persective of course, but it is down the list on the order of things which really need to get done. i cant go backwards coding from a finished peice of software to scratch, if only i could, i wouldnt bother coding a single thing and just use the finished stuff.

certain things need to get done in the correct order for other things to get done. all the stuff before where it says "implement gui" technically needs to be done before i can even begin to do the guis. that is why it apears before there, of course :P

if i jump ahead and continue with this implementation of the gui without first finishing the other stuff, i'll just have to go back and spend the same amount of time recoding the whole thing from scratch anyway once i do get those other things done.

bengeorge · Post by **bengeorge** » Mon Jan 15, 2007 5:03 pm

djsubject · Post by **djsubject** » Tue Jan 16, 2007 2:56 am

Graphical User Interface,

if that was the question

Subz

bengeorge · Post by **bengeorge** » Wed Jan 17, 2007 4:59 pm

oh, not a question, just a bump-bump-biz-UMP!

aciddose · Post by **aciddose** » Wed Jan 17, 2007 11:04 pm

i'll post something once there is something to post, dont worry. the next three/four items on the todo list could take months.

sinkmusic · Post by **sinkmusic** » Wed Jan 17, 2007 11:11 pm

aciddose wrote:i'll post something once there is something to post, dont worry.

ANd on the GUI side ? Grymjack, Gsoto ? Any news ?

grymmjack · Post by **grymmjack** » Wed Jan 17, 2007 11:44 pm

sink; nothing here recently. time is spread thing at the moment. i will have more time once i finish some things up.

kilon · Post by **kilon** » Thu Jan 18, 2007 11:52 am

GUI is something very important .... not only for the VST functionality but also for the fact when you stare at your monitor for hours it better if you seeing something that makes you happy and motivates to to keep going

aciddose · Post by **aciddose** » Sat Jan 20, 2007 3:27 pm

i should replace xhip's gui by a pair of wobbly tits with big happy nipples then, i suppose.

http://xhip.cjb.net/temp/public/tittybiscuit004.mp3
http://xhip.cjb.net/temp/public/tittybiscuit001.mp3

i've been making some progress with the gui issues. having multiple layer popups is quite difficult.. in windows they added a kludge window mode of "always on top" which sets the windows into a top-level overlay, but then there are still problems when windows overlap which both have always on top properity. short of looking at the xfree source for help, i think i dont have many options. it might take me some time to work everything out.

so far i have decided that every gui object should have a background and an overlay set of objects as well as the normal set. then, in order to make sure an object is top level you can add that object to the root object overlay. it remains slightly complicated though because the events (mouse, keyboard, drawing, etc) then need to be routed by the parent object and.. well its complicated.

good news though is i'm about half way through it, i've got the whole popup menu thing working great (dropbox, listbox, etc), and i'm hoping that what i've just discribed about using an overlay layer should work fine once i figure out how to manage everything. i really do not want to have to implement a full windowing system since that is a bit extreme, it'll take a long time to implement all the functionality. hopefully this overlay thing will work for my needs instead.

pdadda · Post by **pdadda** » Sat Jan 20, 2007 4:47 pm

Thanks for your hard work. Looking forward to seeing whatever finished product you put out.

legendCNCD · Post by **legendCNCD** » Sun Jan 21, 2007 2:05 pm

gotta chime in about the filter. Absolutely fantastic stuff o_O very psychedelic...
nailed it down in one strike kaboom! excellent coding.

bengeorge · Post by **bengeorge** » Thu Jan 25, 2007 8:15 pm

hey dose, did you ever resolve the thing where xhip would cpu spike after all notes were done?

i was playing with the new version of xhip-reverb last night, great stuff... it kinda does unexpected things though. weird noise blasts, odd things like that.

bengeorge · Post by **bengeorge** » Thu Jan 25, 2007 8:24 pm

aciddose says: "it is nice to have a clear goal and motivation to follow through with it."

Pretty motivating, eh?

That's what it will feel like, when the new gui is done, x-tremely awesome.

YOU CAN DO IT ACIDDOSE!

aciddose · Post by **aciddose** » Thu Jan 25, 2007 9:58 pm

"did you ever resolve the thing where xhip would cpu spike after all notes were done?"

nope. it'll require denormal elimination, i'll do it now, and i'll put up a new version.

"i was playing with the new version of xhip-reverb last night, great stuff... it kinda does unexpected things though. weird noise blasts, odd things like that."

those shouldnt be unexpected, increase the headroom. the problem you're experiencing is wrapping distortion. it shouldnt occur with the default 12db headroom setting unless you're using very high feedback levels, but you can increase it if it does, or if you want to use those kind of feedback effects.

"YOU CAN DO IT ACIDDOSE!"

i am making progress, just a bit more effort to resolve some issues and i'll be able to continue implementing gsoto's gui. i'm actually considering doing my own quick all-on-one-screen gui, then i wont need to care about the specific parts of it or care about implementing it in a particular way. that should satisfy you guys i hope until i can get gsoto's gui going. it'll take some more time to get the stuff he wants like the context-menus working before i can really continue with his gui.

http://xhip.cjb.net/temp/public/guitest_dropbox.dll

i've been working on improving the way gui elements are structured. i'm increasing the complexity of the code by adding more object types. currently all objects are "control" objects which have a value, a pointer to the valuechange handler, and various other properties specific to controls. for stuff like the "region" objects, this isnt necessary. for objects like my dropbox, i have had to add extra functionality to the "control" object when it isnt necessary for controls to have that functionality. so, this will be solved by having an "action" object class, a "container" object class, and the "control" object class, possibly others derived from the base "frame" class. i might move other functionality around so that it makes more sense. this is what i was referring to when i said i'll be doing more back-end work, stuff that users cant really see the differences of.

the difference though is that making these changes allows me to implement all the stuff you guys want. so all that stuff depends upon this, if you think of it that way it is easier to understand that stuff really is getting done. after i do the "back-end" work, actually making the gui or making controls for the gui is no problem. i can get that done very quickly.

i actually do not spend most of my time writing code. a majority of the time i'm thinking, or fiddling with things, using kvr, irc, that sort of thing. when i'm really concentrating on getting code done, i'm still not spending most of my time writing the code. usually i'll write some code, run into a problem, and then it is time for tea and a nap. when i wake up, i have the solution for the problem and i start coding again. right now xhip has some major issues that i need to fix, one is with the refresh of the full gui, another is with using multiple guis, having them selectable at runtime and loading them from dll files. these sort of large scale problems i spend a week or two weeks thinking about, then sitting on the shitter or something like that the idea hits me. then i finally implement it and continue on. so, the solution still hasnt come to me, it just takes time.

XHip--Please finish your synth!!