XHip--Please finish your synth!!

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

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

this is sooo rad.

the first version i uploaded just displayed the switch/thingie and let you drag it. that was awesome by itself. then i figured "most guis have a top-down pseudo-perspective with light from the top-left". try right clicking to change the camera angle.

this is a fully functional 3d engine by the way with full object hierarchy and hierarchial transformations. all types of projections and transforms, fully capable lighting, multiple shaders (i should really implement a flat npc textured shader) and all that good stuff.

the requirement of a zbuffer and offscreen buffer for drawing is still pissing me off though...

i really need to stop putting off the listbox/menu/etc stuff to work on this trash :lol:

Post

Hmmm... cool. I think I played with the nipple too long - I heard it moan :lol:

Post

This is actually really cool! It would be pretty fun to have a Xhip version with a true 3D GUI that can be freely moved around with the mouse. Then you just need to implement "mood lighting" for outside the "virtual GUI world" that can be tweaked for the desired effect. :D

Cheers!
bManic
"Wisdom is wisdom, regardless of the idiot who said it." -an idiot

"They don't ban hate speech; they ban speech they hate." -an oracle

Post


Post

dont ask me :shrug:

Post

:lol:

Post

HOOORAH! LOVE the gsoto gui.
FREE MUSIC NO MONEY DOWN
http://joeyhoney.blogspot.com/

Post

A 3D gui would be cool but it'd have to be very basic to ensure it would run on all vid cards. I like that little nipple thing :lol:. Are you flipping the back buffer every loop? Just curious.

Post

markdeaton wrote:A 3D gui would be cool but it'd have to be very basic to ensure it would run on all vid cards.
his 3d engine is software AFAIK (therefore not dependant on vid cards), and very efficient, as always.

Post

yeah, the whole reason i wrote my own software engine is to ensure it works everywhere, all the time and always produces exact results. this even works great on a 386, although very slowly. it doesnt use buffer flipping, it uses fast software blits.

the entire "screen"/"window" in xhip is a single buffer in memory managed by software. there is no hardware access allowed to the buffer, 100% software only. for the 3d, i keep additional buffers for the rendering. currently what happens is i'm using a fast 2x2 averaging blit which reads from and blits back to the same buffer. i oversample the 3d rendering by 4x, then apply the 2x2 averaging blit twice to get a 4x4 averaging blit. the top-left 1/8th corner of the buffer is then copied directly into place on the main "window" buffer, and that "window" buffer is then handed to the o/s for display in the system window.

i've been thinking of 100% portability and system-independance since day one with xhip. if i had a mac around, or had already written a vst host for linux, you'd have mac and linux versions with zero changes to the existing code. i'd just have to write a few additional system dependant modules. i've actually already written many for linux/xlib.

http://xhip.cjb.net/temp/public/bender3d.txt
this is the source for the bender/switch widget, sans the 3d renderer, 3d engine, graphics engine, gui engine, windowing engine, etc. basically this is the only additional code that needs to get written to make a completely new control.

Post

Ok, I finally have time to do some GUI work. :party: :D
I see grymm started his take on the GUI (cool!).
I want to finish what I started but I wonder if developing two GUIs in parallel will be a good idea. Opinions? Maybe we should aim for different goals here?

I always try to find a use for that 3d engine but it doesn't seem to fit in a GUI for me.
I was thinking that maybe, besides the clear erotic applications :hihi:, it could find a place in a cut down GUI aimed for beginners (people learning synthesis, etc.); something not efficient oriented but more for toying.

Post

doing multiple guis at once isnt a problem actually since what i need to do for both of them is basically the same. all the improvements i make to the systems to make a "X" control work in the first gui will also apply to the "Y" controls on the 2nd gui.

the actual work with creating the gui is almost zero. actually if i took the time to teach you guys how to do it, you could easilly be coding your own editor.cpp and editor.h files. i could go so far as to provide you with the gui parts of the code and get you using mingw and a quick makefile and you'd be able to produce your editor module (.dll, .xhipgui, whatever) load it in xhip and test it as you go without even talking to me.

i do not think it would be useful to have you guys doing the code parts though since i've got a lot more experiance and i'll see things which can be improved in some code structure which you guys might never notice.

all i need at this point is a complete widget design collection for the guis (i already have most of this from you gsoto, i need to implement it!) and a first layout to try.

if you can finish your basic layout and give it to me, i'll put the controls on the gui and compile it and we can start tweaking/fixing/improving. for now we might want to work in stages. if you're going to put the event routing and other systems on additional pages, we can just leave those things out for now and work with the basics.

i'll actually try just "for fun" to implement the gui that you did design so far, gsoto, and we can continue working from there.

i had the same thoughts about the 3d gui. imagine a 3d gui which is fully animated, has complex effects.. that would be terrible for real function (you'd be so distrated by the fancy colors) but very cool as a toy. if nothing else, including that type of gui in the next version of xhip will surely make it popular.

Post

gsoto wrote:Ok, I finally have time to do some GUI work. :party: :D
I see grymm started his take on the GUI (cool!).
I want to finish what I started but I wonder if developing two GUIs in parallel will be a good idea. Opinions? Maybe we should aim for different goals here?

I always try to find a use for that 3d engine but it doesn't seem to fit in a GUI for me.
I was thinking that maybe, besides the clear erotic applications :hihi:, it could find a place in a cut down GUI aimed for beginners (people learning synthesis, etc.); something not efficient oriented but more for toying.
gsoto i can wait for you to finish. i love your design :)

Post

Yes gsoto don't hesitate, both GUIs will be great.

Post

grymmjack wrote:
gsoto wrote:Ok, I finally have time to do some GUI work. :party: :D
I see grymm started his take on the GUI (cool!).
I want to finish what I started but I wonder if developing two GUIs in parallel will be a good idea. Opinions? Maybe we should aim for different goals here?

I always try to find a use for that 3d engine but it doesn't seem to fit in a GUI for me.
I was thinking that maybe, besides the clear erotic applications :hihi:, it could find a place in a cut down GUI aimed for beginners (people learning synthesis, etc.); something not efficient oriented but more for toying.
gsoto i can wait for you to finish. i love your design :)
lets turn this into a contest to see who finishes first? :D

that way we have one loser & millions of winners :)


:hug: to all involved in this project :)

Subz

Post Reply

Return to “Instruments”