XHip--Please finish your synth!!
-
- KVRist
- 234 posts since 30 Oct, 2004 from Greece
Me too. I w8 with crossed fingers for an "official" answer 
Wtb inspiration!
-
- KVRAF
- 12615 posts since 7 Dec, 2004
i haven't gotten around to the background or layout yet because i've been busy. if anybody wants to volunteer, set up a system where you can compile the examples in the latest xgdb, then get in contact with me and i'll send along the source i have so far for the project.
i want to avoid mentioning it because people flood the thread ranting about it, they have a serious problem with the gui obsession. yeah, sure it's a "big deal" with workflow and that kind of thing, but i really wish people would care so much about synth-related issues as they care about a graphical interface. that's just human nature though.
what i've done so far looks like this:
http://xhip.cjb.net/temp/public/bgui.png
it's just a matter of adding all the shapes and text to the background rendering script - then you just put in the coordinates for the knobs and that kind of stuff. there is a little bit of tricky implementation in updating the sc_knob code and getting all those transparent drop boxes the way branis has shown in his mock-up. it would most likely be best to implement the list-boxes without the fancy graphics and add that feature to the gui at a later time. simply coding the list-boxes is tricky enough by itself, even for me. it's rather time consuming and that's something i just don't have at the moment.
i want to avoid mentioning it because people flood the thread ranting about it, they have a serious problem with the gui obsession. yeah, sure it's a "big deal" with workflow and that kind of thing, but i really wish people would care so much about synth-related issues as they care about a graphical interface. that's just human nature though.
what i've done so far looks like this:
http://xhip.cjb.net/temp/public/bgui.png
it's just a matter of adding all the shapes and text to the background rendering script - then you just put in the coordinates for the knobs and that kind of stuff. there is a little bit of tricky implementation in updating the sc_knob code and getting all those transparent drop boxes the way branis has shown in his mock-up. it would most likely be best to implement the list-boxes without the fancy graphics and add that feature to the gui at a later time. simply coding the list-boxes is tricky enough by itself, even for me. it's rather time consuming and that's something i just don't have at the moment.
-
- KVRist
- 294 posts since 6 Jan, 2005
Thanks for feedback AD, any progress whatsoever is appreciated.
You're right about the zealous nature pertaining to GUI development, this maybe will be counterbalanced with more indepth feedback regards to synth performance eventually.
You're right about the zealous nature pertaining to GUI development, this maybe will be counterbalanced with more indepth feedback regards to synth performance eventually.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
nothing going on yet, no more work on the guis or libraries or anything?
it's to the point, other than routing of modulators (ccs, etc) that xhip really could have some patches and banks available. if anybody has been working on those, be sure to post them.
you can upload at http://xhip.cjb.net/upload
i've been busy the last few weeks, i might be back around next week.
it's to the point, other than routing of modulators (ccs, etc) that xhip really could have some patches and banks available. if anybody has been working on those, be sure to post them.
you can upload at http://xhip.cjb.net/upload
i've been busy the last few weeks, i might be back around next week.
-
- KVRAF
- 1669 posts since 4 Nov, 2007
-
- KVRist
- 105 posts since 10 Nov, 2006
Control settings not being saved per patch makes it very awkward..aciddose wrote:it's to the point, other than routing of modulators (ccs, etc) that xhip really could have some patches and banks available. if anybody has been working on those, be sure to post them.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
which control settings? none of those have anything to do with the synthesizer. i said "other than routing of modulators" which would be like bender, mod wheel, etc. that can't possibly be saved until it's correctly implemented, otherwise your patches will become useless in the old format.
-
- KVRist
- 294 posts since 6 Jan, 2005
Ok let's try and not get too distracted and keep our goal in sight please
Like many others I'm sure, once I am in a position where I don't spend over 2 hours tweaking a sound flipping from page to page (getting lost, confused and frustrated in the process), will post a bank primarily of basses and tempo synced effects.
Like many others I'm sure, once I am in a position where I don't spend over 2 hours tweaking a sound flipping from page to page (getting lost, confused and frustrated in the process), will post a bank primarily of basses and tempo synced effects.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
i was being serious, not trying to be insulting or anything. just make some real patches and it'll take five minutes to add the unison parameters later when that's supported. it might not be for a year or two since the amount of free-time i have lately is shrinking fast. the voice-unison section is global anyway, it will never be as part of the synthesizer. it will be changed to support multitimbrality and other features (key mapping, diffusion effects, parameter morph ranges, etc) so adding anything to store the one set of values now will be pretty much useless anyway.
the bender/velocity/wheel parameters are already known to be useless since they'll be replaced with event routing in the future. these parameter groups will be saved in seperate chunks in each patch and it will be user-configurable to mask these chunks on or off.
you'll be able to say, "don't load notelogic mode from the patch, keep it on monophonic lowest" so that when switching through patches you won't have annoying changes occurring.
xhip will also have parameter randomization added and a system to select desired ranges and masking of certain parameters. the last thing will be the addition of a complex sequencer/arpeggiator allowing things such as sequenced program changes for c-64 style effects and more.
i'll be working more toward open-sourcing xhip-core and xhip-gui under gpl while maintaining a private distribution of my vst-wrapper and others (au, dxi, rtas, so on) to allow the core to be used in different plugin formats.
i expect things to slow down a lot now since i still haven't received any help with the code side. the gui drawings have been great and i'm thankful for those, but they only create more work for me, not less.
the bender/velocity/wheel parameters are already known to be useless since they'll be replaced with event routing in the future. these parameter groups will be saved in seperate chunks in each patch and it will be user-configurable to mask these chunks on or off.
you'll be able to say, "don't load notelogic mode from the patch, keep it on monophonic lowest" so that when switching through patches you won't have annoying changes occurring.
xhip will also have parameter randomization added and a system to select desired ranges and masking of certain parameters. the last thing will be the addition of a complex sequencer/arpeggiator allowing things such as sequenced program changes for c-64 style effects and more.
i'll be working more toward open-sourcing xhip-core and xhip-gui under gpl while maintaining a private distribution of my vst-wrapper and others (au, dxi, rtas, so on) to allow the core to be used in different plugin formats.
i expect things to slow down a lot now since i still haven't received any help with the code side. the gui drawings have been great and i'm thankful for those, but they only create more work for me, not less.
-
- KVRian
- 607 posts since 20 Oct, 2005
You can't be serious?aciddose wrote:i was being serious, not trying to be insulting or anything. just make some real patches and it'll take five minutes to add the unison parameters later when that's supported. it might not be for a year or two since the amount of free-time i have lately is shrinking fast.
You make a fair request for users to make some patches for your synth and then tell them to wait maybe 1 or 2 years before others will be able to hear the patches as they were originally intended.
Imo you are placing unnecessary limits on serious sound designers.
For some crazy reason I tried your synth again to see how far its progressed and do you know what? it reminds me of Rice Crispies ...snap, crackle and pop
-
- KVRAF
- 12615 posts since 7 Dec, 2004
how about this: i'll remove the unison and other features from xhip so that you can make patches and have them "as they're supposed to be heard", since unison doesn't exist, how will that be?