XHip--Please finish your synth!!

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

Post

aciddose wrote:it's impossible for the screen to be grey, are you saying there is absolutely nothing on the gui?

are the knobs visible?
are the displays and buttons visible?

if you have a grey window this is a far more serious problem, what size is the window?

does the normal gui work?

does the one.xhipgui work?
this is going to be the default gui after you finished right?
probably not, we'll pick which guis the installer/archive comes with when the 1.0 release happens. i don't think this will be one because it's far too grey and it doesn't include all the controls. if it's "finished" in the future, maybe. i won't include any gui that doesn't fully expose xhip's functions - although i will be happy to host them if i have the source to compile them myself.

if anybody wants to distribute their own code that's ok, but i won't distribute something i don't have the complete source for.
it works now. i copied the .png file over? is that required? its the only thing i've done differently :p

To be clear though. The size was right. It simply wouldn't display anything. It was just a grey screen. no controls. Nothing. Although I could play it.

edit the 4th! : before i got it working in minihost, it just worked fine in FL right off the bat.


here's a screener. I tried it with your "one.xhipgui"

Image

I assume the size is right. Its just not loading anything. Is there also a one.png?
Top

Post

no it doesn't need any files, that was the mistake i made in the 'b' version, i left it trying to load a bmp file from "c:/code/xhipgui/limeflavour.bmp" rather than using the compiled-in jpg data, then after i fixed that i found the jpg wouldn't decode because it was greyscale.

that's actually fairly odd, i wonder what would cause it. if the host has a bug perhaps, where it corrupts data in xhip's memory space.. or possibly it tries to access the gui pointer directly which is bad, bad, bad.

i don't know what else would cause that, and the fact it got better on it's own without you actually doing anything is really, really strange.

that isn't xhip's gui at all - it isnt even loading the gui, it's loading nothing and not even creating a window. the window background should be absolute black if the gui module even loaded.

unless you have other symptoms (other than no gui module loading) i'd say that's a host bug. does the default bank load?
Top

Post

seems to be a minihost problem
possibly some memory/cache error within its own system.

it opened fine in FL (using the one.xhipgui) and when i closed FL and reopened in minihost it was ok again.

Has to be some cache problem.

oh, and yes. the sounds all work fine. I was browsing presets using MH's internal preset manager. No problems that I could find.

It seems to be limited to a gui issue.
Top

Post

i'd bet minihost tries to access the editor pointer and manually mess with things rather than calling the proper dispatcher functions. you could give a message to the author if you wanted since they would be far better at debugging the problem than i would. all i'd be able to tell from the xhip side is if the gui is called into or not, and we can already tell it isnt due to the no-gui-window thing.

i'm not absolutely certain, i just think it can't be a bug in xhip or the xhipgui because all the error conditions are trapped. if there was a problem allocating the window a messagebox would tell you that and we can see it doesn't get as far as the window already since the background isn't filled in with black.
Top

Post


Yup! Whatever you guys are doing do not stop. Xhip is obviously becoming a very interesting synth.

Do not tell AD though, he has plenty of self-confidence already! :D

All the Best
"I speak for all mediocrities in the world. I am their champion. I am their patron saint."
Top

Post

Hskovlund wrote:

Yup! Whatever you guys are doing do not stop. Xhip is obviously becoming a very interesting synth.

Do not tell AD though, he has plenty of self-confidence already! :D

All the Best
Wow i really love that gui (Great work Limeflavor) :tu:
I hope that this will be the default look aciddose and Limeflavor great work from both of you :clap:
Top

Post

finally, the synth may be usable now....
Top

Post

i personally hate this design with a passion.
the knobs especially .... small and u never know whever its the indicator or the back part pointing....not clear at all on small screen.
just a mass of small and unusable knobs with a cheap 3d look and a silverish tacky design that makes it look like any 100s of other synthedit synths.
it looks like yet another odo synth,

the tabbed and coded gui would have never been a problem with a decent design. (the Automat osx gui was a coded and tabbed one and its become one of the most used designs in the vst world due to its style, practicality ,scalability and clarity- just think of the knobs in dbglitch, erratic and what not). and for a another minimal tabbed gui that works look at the XT synth...

i would have preferred the geek design u posted a few pages ago ...at least u can clearly see at a glance where the knobs are pointing and u can tweak them efficiently.

ps:although i hate it....still better than what was there before.
Top

Post

we should probably have seperate gui threads.. anyway i don't think the design was finished, we haven't heard back from limeflavour yet.

if you hate it feel free to create your own, it can be implemented now. also, if you like you can even write the "addswitch(), addknob(), etc) code yourself which would be really helpful.
Top

Post

Something sounds wrong when you use poly mode, glide and filter keytracking. Seems like the cutoff is raised randomly.

Limeflavour's GUI looks nice :tu:. But while I like some things about it I think that at its current state it's a step backwards in many aspects. The layout really sucks :(.
Top

Post

the synth should work fine in 16.4, so just keep using that if the problem doesn't exist there. the .5 version was just to implement the lfo delay thing for _starcraft_.

right now i'm converting things internally to float from the byte sizes since you pointed out that parameters are limited to 256 steps. i won't be done for a while and i can't post a new version until everything is converted. i think i have fixed the problem though, try this "not a release" version, just remember the byte->float conversion isnt 100% finished and tested: http://xhip.cjb.net/temp/public/xhip_not_a_release.zip

(the old GUIs probably won't work correctly with this.. the old shift-adjust was based upon the 'range' being 256, and now unlimited range controls are "1", so holding shift on the old GUIs will move 100% in one pixel)

i was going to try implementing the last example of your gui that you posted, do you have a newer one?

if not i'll use this one that i have:
http://xhip.cjb.net/temp/public/proto3_1.png
Last edited by aciddose on Wed Sep 17, 2008 2:42 am, edited 1 time in total.
Top

Post

Yep, I have newer ones, but half done. I'm hoping to find some time to work on this (design and code).
Top

Post

ok i'll just try with the one i have then.

Image

at least limeflavour's design was better than this one :lol:
Top

Post

that's a keeper :love:
Top

Post

Hey guys, sorry for the late answer but I havent been able to reply earlier than this.
The mockup picture is not even nearly finished, it's something I whipped up in an hour or so. I just wanted to see if it was possible to continue the design and after I've seen Aciddose acutally implement this skin I know that it is. ;)

I know the layout is not the "best" and there is parts missing but to change the layout is not very hard. I'm not used to skin synths btw. so any tips at all would be gladly accepted. :)
Top
Post Reply

Return to “Instruments”