XHip--Please finish your synth!!

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

Post

:hug: :hug: :hug: :hug: :hug: :hug: :hug: :hyper: :hyper: :hyper: :hyper: :hyper:


...come on people !!!


let's just drop this stupid issue and focus on the fact that Poly-Ana and Xhip are both tools for creating music...and Aciddose and Admiral Quality are both humans with their own problems, their own solutions, their own ideas, etc...

i never tried poly-ana...but many people say it is really nice.

xhip is no the best synth in the world...but it sounds really good...i like it...

if you both guy have so much trouble...take a bus...meet each other....and beat the crap out of each other...

but Aciddose...please...before that...finish your synth

and Admiral Quality....fix the aliasing in your synth that i have never tried !

:hug: :P
whooooooooooooooaaaaaaaaaaaaaaaaaaa !!!

Post

@aquar: aciddose needs to drop the trash talk too. Everyone does.

Post

Kloz wrote:and Admiral Quality....fix the aliasing in your synth that i have never tried !
It's not broken. It's just different than what you're used to (you're not used to being given CONTROL). Try it, THEN complain.

Does the new version of XHip let me control vibrato from the mod wheel yet? And if so, how can that possibly be patch compatible with earlier versions? Were users expected to produce banks of sounds when they couldn't set up something as obvious and common as mod wheel routing?

Oh and to whoever accused me of not being helpful in here; way, way back I already told aciddose what his stuck note problem probably was and showed him where in his code he needed to handle all notes off messages. But a user above is still finding it a show stopper. Anyone in here asking for features or trying to nudge him into working instead of telling us yet again how unworthy we all are is perfectly on topic. Aciddose can't resist telling every other developer on this board his/her business, so you gotta figure it's going to happen the other way sometimes too.

I'd use XHip occasionaly myself if it didn't have gaping holes in the featureset that made it completely useless.

S'all. I REALLY would like to see this "product" reach a useable state. And I obviously have enough experience to know what's involved in getting there. That gives me as much right to post in here as any of you. (Plus, I was summoned.)

Post

Mighty Pea wrote:Piz has one of those as well, Vurt, it's not entirely unheard of. I much prefer that interface, though.

first id heard of such a thing, not that im against it, i would like more idea of why than how? ie what do i gain from it? althpugh how controllable it is might be useful too, can it be automated?
:ud:

Post

men...i was writing a reply...a really long one...but...then..i realize...

it just don't matter at all...

...Xhip is free

...Xhip makes me happy

...I didn't pay anything for it

...And i don't think i have the right to complain.

...If Aciddose solves the bugs and all....GREAT

...If Not....Mmmm...well that is a sad...

...But i rather have Xhip as it is than not having Xhip at all.

...Xhip rocks now and in the future...Xhip is going to rock even more...and i understand people can be afraid of that !
whooooooooooooooaaaaaaaaaaaaaaaaaaa !!!

Post

Shy wrote:AdmiralQuality, I didn't know you're a xhip fan by the way. Did you ever fix the aliasing in PolyAna?

You forgot the predictable, almost obligitory swipe at the interface. (where's Walton when you need him??).

Honestly , It's getting soooooopredictable. :)

Anybody wants to listen and decide for themselves should just demo.


It's a subjective choice . Opinions are allowed to vary.

Post

aciddose wrote:we can fix it any time you have the ability to devote about a full day to running debugging tests, and you're able to chat with me and exchange dlls and logs over something like irc or msn messenger.
Sounds fair. Thanks for offering your help in that matter. I'll PM you to set a day for it. A whole day I'm not sure I can, but I'll try my best. MSN it will be.
aciddose wrote:i'd like instructions or a midi file to perfectly recreate the issue if you're capable of providing that.
Yes I'll make a simple example to demonstrate the issue.

Thanks.

Cheers

Post

based upon your description it sounds like the "host violates midi spec, uses allnotesoff without sending individual noteoff messages first" issue.

try going into the control page on this version and activate the new flag, "respect allnotesoff".

http://xhip.cjb.net/xhip/releases/0/6/1 ... 6.16.1.dll

this should fix it, if not the problem is a more serious bug. i won't enable this flag by default because it violates the midi spec.

as i'm implementing the event routing stuff i'll make the internal flag definition dynamic and i'll modify the configuration (ini) file to use my ad-db format.

xhip.ini

Code: Select all

guipath = "c:/vst/default.xhipgui";
defbank = "c:/vst/default.adxb";
flags
{
 respect all notes off = 1;
}
something like that will be much easier.

i should add: the midi spec states that "allnotesoff" is simply a confirmation to be sent from a sequencer that says all active notes on the sequencer side have now been shut off, and all the "noteoff" messages have been sent. i suppose this is to allow a synth to show a "midi error" or something if a voice remains active without a "noteoff" when the "allnotesoff" is received. the spec is kind of vague on this, the exact purpose for the command, but it does strongly state that "allnotesoff" need not be implemented by instruments or sequencers and that controlling devices such as sequencers MUST NOT depend upon the message for any purpose.

it could be useful to signal legato for example, where a chord is played by a single key and "allnotesoff" is only sent if no keys are held. the sequencer could for example transmit chords in lowest to highest note order and have the synthesizer allocate voices likewise to allow for effects like full chord glide. "allnotesoff" would then signal that the next chord should not glide, or perhaps should be retriggered, or something else like lfo sync or whatever other feature you can think of.

one of the mostly useless and bug-inviting features of midi.

Post

Kloz wrote:men...i was writing a reply...a really long one...but...then..i realize...

it just don't matter at all...

...Xhip is free

...Xhip makes me happy

...I didn't pay anything for it

...And i don't think i have the right to complain.

...If Aciddose solves the bugs and all....GREAT

...If Not....Mmmm...well that is a sad...

...But i rather have Xhip as it is than not having Xhip at all.

...Xhip rocks now and in the future...Xhip is going to rock even more...and i understand people can be afraid of that !

Hey Kloz,
Do u have any presets u could post, or anyone else for that matter?
Cheers
:)

Post

aciddose wrote: i should add: the midi spec states that "allnotesoff" is simply a confirmation to be sent from a sequencer that says all active notes on the sequencer side have now been shut off, and all the "noteoff" messages have been sent
http://www.midi.org/about-midi/table1.shtml

"All Notes Off.
When an All Notes Off is received, all oscillators will turn off."

I'd assume oscillators means voices in that instance.

http://www.midi.org/aboutmidi/glossary.php

"ALL NOTES OFF : A MIDI channel message that tells a MIDI sound-generating device to shut off all currently active notes. This is a life-saving device to cure 'hanging' MIDI notes."

Anyway my understanding is that you shouldnt use "AllNotesOff" in a lazy way, you should send individual noteOff messages. But "AllNotesOff" should actualy turn off all notes aswell, it's a panic function.

Post

that's either changed recently, or the page differs from the actual spec. the spec states clearly that all note-on messages must always be followed by note-off messages, even if a allnotesoff is presented - and that the allnotesoff message must be presented after all note-off messages have already been.

we've been through this before. it's "ok" as a panic command or to allow a signal for some kind of error when it's received unexpectedly. it's poor coding practice, coder laziness and over-all bad design for a host or sequencer to depend upon it and this is all i'm trying to state here: for the future authors of hosts and sequencers - send all your bloody note-off messages and design your host that way from the start.

if anybody is offended that i've called them lazy or their coding practice "poor", well, cry me a river.

Post

Hosts usually have this feature. If it's not STOP/PAUSE, it's VSTi Power ON/OFF.

Post

nollock wrote:
aciddose wrote: i should add: the midi spec states that "allnotesoff" is simply a confirmation to be sent from a sequencer that says all active notes on the sequencer side have now been shut off, and all the "noteoff" messages have been sent
http://www.midi.org/about-midi/table1.shtml

"All Notes Off.
When an All Notes Off is received, all oscillators will turn off."

I'd assume oscillators means voices in that instance.

http://www.midi.org/aboutmidi/glossary.php

"ALL NOTES OFF : A MIDI channel message that tells a MIDI sound-generating device to shut off all currently active notes. This is a life-saving device to cure 'hanging' MIDI notes."

Anyway my understanding is that you shouldnt use "AllNotesOff" in a lazy way, you should send individual noteOff messages. But "AllNotesOff" should actualy turn off all notes aswell, it's a panic function.
This is just more classic aciddose. In his mind, it's the fault of every other product that came before that didn't "disrespect" the all-notes-off message. This is why he didn't fix it months ago when I pointed it out. They guy's got some serious mental block.

And if we do convince him he was wrong, he'll just claim to have never said that in the first place.

"Simply a confirmation". As if! It's a COMMAND. You live in a fantasy land all your own aciddose.

Post

Speaking of mental issues, what do you even want in this thread, Admiral Quality? As for me, I'm just one of the people who like to read this thread and what aciddose has to say. While aciddose always explains things and says exactly why he does or doesn't do something, you just attack his personality. If you're trying to prove you're better, by attacking one of the many people that you clearly dislike in a thread about a synth of his, it's not working.

Post

Shy wrote:Speaking of mental issues, what do you even want in this thread, Admiral Quality? As for me, I'm just one of the people who like to read this thread and what aciddose has to say. While aciddose always explains things and says exactly why he does or doesn't do something, you just attack his personality. If you're trying to prove you're better, by attacking one of the many people that you clearly dislike in a thread about a synth of his, it's not working.
I'm attacking THIS. Listen to how he's ordering around the rest of the industry to conform to HIS deluded interpretation of the MIDI spec:
aciddose wrote: for the future authors of hosts and sequencers - send all your bloody note-off messages and design your host that way from the start.
And as another developer, I'm pointing out that perhaps everything isn't always EVERYONE ELSE'S fault.

MIDI was a CABLE SPEC. And as such you couldn't know for sure that the receiving apparatus had received all the note offs it would need. And processors were slow back then, sometimes notes and events went missing. So the all-notes-off made perfect sense as, yes, a "panic button".

But even on a modern DAW it's pretty easy for the state to get mixed up. So all-notes-off still functions perfectly as a state reset. It's like the host saying "Just so everybody understands, our shared imaginary keyboard is all keys up now, got it?" And just because aciddose deems this uncool, thinks the world should be perfect and any host or plugin that missed an event for any reason (and I've seen spikes in CPU cause notes to stick in some hosts) invalidates the whole goal of making music on your computer.

It's in the spec. It's NOT open to interpretation. He was not doing his "customers" any service by imposing his limited interpretation of the MIDI spec on them. Aciddose should fix HIS software and stop placing blame on EVERYBODY else. Do you really think the rest of the world is wrong and aciddose is right? C'mon. I'm doing you a favour. You're going to get a feature out of this. You can enable ALL the "respect" options! :hihi:

Post Reply

Return to “Instruments”