mighty, a polycount in the range of 100-300 would be best, but the most important part is to logically arange objects in the tree. rather than having a single "knob" object, it's best to have the knob, the pointer, any extra effects like tab/protrusions etc since i can then render parts which need special qualities with those specific properties. same deal as with bitmaps, if i have the individual parts of the knob in 3d objects, i can render them individually and that will improve my ability to generate masks, diffuse/specular layers, shadows, etc.
currently i only discard objects before rotation, i dont deal with individual polys, and i use a bounding sphere so it isnt very accurate in terms of discarding unnessicary polygons.
it is easy to manage 1000-3000, or even 10,000 polys but the rotation/projection occurs in software and is naive (not sse) so it will become proportionately slower.
XHip--Please finish your synth!!
-
- KVRian
- 673 posts since 15 Nov, 2004 from Montevideo, Uruguay
Ok, new thread!
grymmjack, I'm designing a UI for Xhip but acid pretends to make different UIs available. I won't consider it rude at all if you want to design another one. You can help me with mine too...
sink, sorry about the UI teasing
. Hopefully the work will continue in one or two weeks.
grymmjack, I'm designing a UI for Xhip but acid pretends to make different UIs available. I won't consider it rude at all if you want to design another one. You can help me with mine too...
sink, sorry about the UI teasing
. Hopefully the work will continue in one or two weeks.-
- KVRian
- 536 posts since 8 Dec, 2004
"how easy would be to implement 5 tabs to be one click away from the pages."
LOL
thanks a lot!!!
LOL
thanks a lot!!!
-
- KVRAF
- 12615 posts since 7 Dec, 2004
-
- KVRist
- 71 posts since 26 Feb, 2006 from Amsterdam
I just want to say that I like the recent changes very much, like the tabs & the 'new' letter font. Soundwise, I love it already for quit some time...
Personally, I don't need I GUI with knobs and all, I really like the Gui as it is now.
Personally, I don't need I GUI with knobs and all, I really like the Gui as it is now.
-
- KVRAF
- 3846 posts since 15 Mar, 2002 from Underworld
Precisely, Okke. The GUI is fine and very usable. Maybe just switches instead of sliders where needed would be nice to avoid the confusion and then see what goes where .
Cheers and Happy Christmas all!
.Cheers and Happy Christmas all!
It is no measure of health to be well adjusted to a profoundly sick society. - Jiddu Krishnamurti
-
computercontrolled computercontrolled https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=89419
- KVRist
- 260 posts since 29 Nov, 2005
I find the GUI makes the sound design harder , im not a sound design genious but still xhip is so awesome that at the aned of the day i cant complain
-
- KVRAF
- 9590 posts since 17 Sep, 2002 from Gothenburg Sweden
The tabs really made a world of difference for me.
It is awesome as it is now.I really really like it.
For some reason Xhip just clicks with me. Have'nt really been impressed with synths for a long while but this one excites me to no end. Some questions though:
1. Are we set on the preset format ? I've started doing a bank and it would be sad if it changed once again and all work (fun) would be lost.
2. There isn't pulse witdh modulation on osc. B is there ? Or am i too stupid to find it?
3. Pulse witdh on the ramp wave does'nt sound anything like i expected. I vaugely remember it being a supersaw instead and it kinda sounds like it. Is this correct ?
I tried to do an alternative GUI but so far it looks like crap with puke on but maybe some day i get something useful. There was a thread about what synth sounds like a SCI Proone and i thought Xhip could do it. And it could! I made a cover of Don't go by Yazoo and came pretty close. I post it some day when i finish it. Coolness.
It is awesome as it is now.I really really like it.
For some reason Xhip just clicks with me. Have'nt really been impressed with synths for a long while but this one excites me to no end. Some questions though:
1. Are we set on the preset format ? I've started doing a bank and it would be sad if it changed once again and all work (fun
) would be lost.2. There isn't pulse witdh modulation on osc. B is there ? Or am i too stupid to find it?
3. Pulse witdh on the ramp wave does'nt sound anything like i expected. I vaugely remember it being a supersaw instead and it kinda sounds like it. Is this correct ?
I tried to do an alternative GUI but so far it looks like crap with puke on but maybe some day i get something useful. There was a thread about what synth sounds like a SCI Proone and i thought Xhip could do it. And it could! I made a cover of Don't go by Yazoo and came pretty close. I post it some day when i finish it. Coolness.
-
- KVRAF
- 9590 posts since 17 Sep, 2002 from Gothenburg Sweden
http://www.filelodge.com/files/room34/950841/DontGo.mp3
Here's my attempt to make Xhip sound like a SCI ProOne.
For those of you who don't know the original was pretty much ProOne all the way except for the drums.
Which incidently is what sounds the least like the original. Everything is Xhip. Apart from the snare which is eq'ed and has a touch of DaTube on it the only effect i used was Cubase's Roomworks which is on the Snare,the lead synth and the wroom sound.
Here's my attempt to make Xhip sound like a SCI ProOne.
For those of you who don't know the original was pretty much ProOne all the way except for the drums.
Which incidently is what sounds the least like the original. Everything is Xhip. Apart from the snare which is eq'ed and has a touch of DaTube on it the only effect i used was Cubase's Roomworks which is on the Snare,the lead synth and the wroom sound.
-
- KVRAF
- 2841 posts since 23 Feb, 2004 from Planet Earth...for now
A better thread title would be " Please release your synth from beta" as the idea of finishing it might be a mental turn off to aciddose, and I for one would certainly like to see him continue being mentally invested in it with his focus of "improving things". Although, I think it's pretty much THERE already.
My biggest irk is that until it's out of beta I don't feel comfortable using it within projects, for obvious reasons; and preset development is also hampered.
IMO it's done - put a fork in it, and Release it. If you make/find some improvements that are backwards incompatible, just start an Xhip 2 synthy.
And Thank You Aciddose, you rock!
My biggest irk is that until it's out of beta I don't feel comfortable using it within projects, for obvious reasons; and preset development is also hampered.
IMO it's done - put a fork in it, and Release it. If you make/find some improvements that are backwards incompatible, just start an Xhip 2 synthy.
And Thank You Aciddose, you rock!
-
- KVRAF
- 12615 posts since 7 Dec, 2004
it isnt done until all the features on the todo list are implemented. beta 7 (the next beta) will most likely be the last beta before i release a v1.0.0.0 version. the things on the todo list right now though are absolutely required for me to release that. for example:
- kludges are not acceptable in a full version release. that will explain why i say "i'd have to remove ... in the v1 release" several times below.
- since there is no dropbox control to select pcm waveforms, you cant select more than the 8th pcm. simply allowing you to select 1 - 8 is a kludge anyway. it should allow selection of each wave directly. obviously also no editing of waves, saving of waves. waves are not saved in patches or project files. you cant adjust the settings of wave playback like sinc, spline, linear or no interpolation. different looping modes. tuning, etc. without this implementation i would have to remove the pcm feature before making a v1 release.
- you cant correctly map events to parameters. the velocity and bender are currently hard-wired into a system which is capable of dynamically configuring event routings so that you can map any type of event to any parameter. some of xhip's parameters like cutoff should have the ability to accept negative input. for example if you use the bender, there is a negative range. you should be able to bend downward even when the cutoff parameter is already set at zero. this requires some redesign of the synth which i'll be doing soon. without having list controls, context menus and drop boxes i cant implement configuration for event mapping on the gui. in order to release v1 i'd have to completely remove the velocity and bender features.
- patches currently only contain a subset of the data in the synth. people would like to be able to also save polyphony modes, event routing, and all that other configuration. without first having the event routing system and other systems working, i can not possibly implement a patch format to save their configurations.
- vst chunks are currently not used. this means the data saved in your project will only be a subset of the data present in the synth. any even extremely minor change to xhip will mean it is not backward compatible with project files you made based on an older version of xhip. this isnt acceptable since it means you're forced to maintain old versions if you use them in projects.
- see all the additional missing features in the todo list.
- variant versions of the gui need to be available. some people like the current gui, some people want something different. in order to satisfy everyone the gui needs to be selectable, or you might say "skinnable". it already is, that isnt the problem. the problem is i need to create the additional guis for you to use, and i need to finish implementing and test all the systems involved with this.
jupiter: those three questions are answered here: http://xhip.cjb.net/xhip/faq.cgi
- kludges are not acceptable in a full version release. that will explain why i say "i'd have to remove ... in the v1 release" several times below.
- since there is no dropbox control to select pcm waveforms, you cant select more than the 8th pcm. simply allowing you to select 1 - 8 is a kludge anyway. it should allow selection of each wave directly. obviously also no editing of waves, saving of waves. waves are not saved in patches or project files. you cant adjust the settings of wave playback like sinc, spline, linear or no interpolation. different looping modes. tuning, etc. without this implementation i would have to remove the pcm feature before making a v1 release.
- you cant correctly map events to parameters. the velocity and bender are currently hard-wired into a system which is capable of dynamically configuring event routings so that you can map any type of event to any parameter. some of xhip's parameters like cutoff should have the ability to accept negative input. for example if you use the bender, there is a negative range. you should be able to bend downward even when the cutoff parameter is already set at zero. this requires some redesign of the synth which i'll be doing soon. without having list controls, context menus and drop boxes i cant implement configuration for event mapping on the gui. in order to release v1 i'd have to completely remove the velocity and bender features.
- patches currently only contain a subset of the data in the synth. people would like to be able to also save polyphony modes, event routing, and all that other configuration. without first having the event routing system and other systems working, i can not possibly implement a patch format to save their configurations.
- vst chunks are currently not used. this means the data saved in your project will only be a subset of the data present in the synth. any even extremely minor change to xhip will mean it is not backward compatible with project files you made based on an older version of xhip. this isnt acceptable since it means you're forced to maintain old versions if you use them in projects.
- see all the additional missing features in the todo list.
- variant versions of the gui need to be available. some people like the current gui, some people want something different. in order to satisfy everyone the gui needs to be selectable, or you might say "skinnable". it already is, that isnt the problem. the problem is i need to create the additional guis for you to use, and i need to finish implementing and test all the systems involved with this.
jupiter: those three questions are answered here: http://xhip.cjb.net/xhip/faq.cgi
-
- KVRAF
- 2841 posts since 23 Feb, 2004 from Planet Earth...for now
OK - Of course you'd know all the imperfections,and are the ultimate judge of when it's ready, so just we'll keep waiting....patiently....Carry On. 
-
- KVRAF
- 12615 posts since 7 Dec, 2004
well, if anyone is willing to stick with a particular version they can do that. i keep older versions around and i've started releasing them with filenames based upon the version.
that means when you load up a project, it will load with the version of the plugin you used in that project assuming the host uses proper identification of plugins and not just the dword id code.
if a specific version of xhip is "good enough" you can just keep that version and continue to use it in your older projects, ignoring newer versions. that means of course though that you will be locked into that version for that project unless you want to go through the whole process of reloading with a new version and updating patches, automation and everything else.
the only reason i wont release something i'll call a "final" or "full" version is because people will complain like !@#$ing %^&* and drive me nuts about things they cant understand. "why doesnt it have blah blah blah?". i'd have to tell them "stuff it" since there is no way i could explain 100 times the same things to a ton of different people. hopefully, HOPEFULLY! the version that i do release in the future will have a minimum of complaints, and for the people who still do complain i CAN say "stuff it" and be totally justified in doing so
that means when you load up a project, it will load with the version of the plugin you used in that project assuming the host uses proper identification of plugins and not just the dword id code.
if a specific version of xhip is "good enough" you can just keep that version and continue to use it in your older projects, ignoring newer versions. that means of course though that you will be locked into that version for that project unless you want to go through the whole process of reloading with a new version and updating patches, automation and everything else.
the only reason i wont release something i'll call a "final" or "full" version is because people will complain like !@#$ing %^&* and drive me nuts about things they cant understand. "why doesnt it have blah blah blah?". i'd have to tell them "stuff it" since there is no way i could explain 100 times the same things to a ton of different people. hopefully, HOPEFULLY! the version that i do release in the future will have a minimum of complaints, and for the people who still do complain i CAN say "stuff it" and be totally justified in doing so
-
- KVRist
- 77 posts since 24 Aug, 2005 from Phoenix, AZ, US
Way to go Acid! I know I like trying betas--when I KNOW the software is beta. But I'm also tired of companies (do I hear "Microsoft"... 
) turning out software to the public that is clearly still beta and charging for it.
I like to hear that you want xhip to be fully tested and a good final product when released. Thanks for all the work you've done on making it sound this good so far!
) turning out software to the public that is clearly still beta and charging for it.I like to hear that you want xhip to be fully tested and a good final product when released. Thanks for all the work you've done on making it sound this good so far!