hey, i'd really like to give it a try ... where can i get it?aciddose wrote:the source code can be made available to anybody who wants to take a whack at it.
XHip--Please finish your synth!!
-
- KVRAF
- 6242 posts since 26 Sep, 2003 from right here, as you can see ...
regards,
brok landers
BIGTONEsounddesign
gear is as good as the innovation behind it-the man
brok landers
BIGTONEsounddesign
gear is as good as the innovation behind it-the man
-
- KVRAF
- 5200 posts since 13 Jul, 2004 from Earth
Does this version work in Sonar or will it continue to play beyond tomorow after i hit stop in Sonar like the other versions?aciddose wrote:"About the patch issues, we could 'unofficially' pick some version, lock it for patch production, and acid, maybe you could code a patch format 'updater' for that version once the official release is out."
http://xhip.cjb.net/xhip/releases/v0/b6 ... 6.14.9.dll
sure, the version posted here should do.. like i said nothing is going to change in the synth from now on even if it seems a useful change. all changes from here on are going to be held until after xhip 1.0.
as for the bug, good catching that however it's completely unrelated to the one we were discussing. this was just a simple mistake with a post/prefix decrement mix up in a loop.
by combining xmod with sync you can get fairly cool sounds.. it's exactly like the input fm on the filter. it's designed for bell sounds and that sort of thing. in combination with ring mod you can do really good bells.. like this: http://xhip.cjb.net/temp/public/audio/dingdong.mp3
it does allow a lot of other sounds though, not just bells. it's similar to ring mod though as the result usually is a aharmonic metallic sound.
-
- KVRAF
- 12615 posts since 7 Dec, 2004
"will it continue to play beyond tomorrow"
no, i added the allnotesoff/allsoundoff hack. any host which sends those commands will now trigger note cuts. you should still keep in mind that any host doing so is not keeping with the midi spec.
the latest version is the highest version number available at http://xhip.cjb.net/xhip/releases/
no, i added the allnotesoff/allsoundoff hack. any host which sends those commands will now trigger note cuts. you should still keep in mind that any host doing so is not keeping with the midi spec.
the latest version is the highest version number available at http://xhip.cjb.net/xhip/releases/
-
- KVRAF
- 5200 posts since 13 Jul, 2004 from Earth
Thank you ADaciddose wrote:"will it continue to play beyond tomorrow"
no, i added the allnotesoff/allsoundoff hack. any host which sends those commands will now trigger note cuts. you should still keep in mind that any host doing so is not keeping with the midi spec.
the latest version is the highest version number available at http://xhip.cjb.net/xhip/releases/
It works fine now
-
- KVRian
- 709 posts since 16 Dec, 2005 from Novato, California, USA
Using the same logic, you could argue that any synth not implementing "All Sound Off" and "All Notes Off" does not keep with the midi spec. In general, passing the blame on other software does not help the musician much.aciddose wrote:no, i added the allnotesoff/allsoundoff hack. any host which sends those commands will now trigger note cuts. you should still keep in mind that any host doing so is not keeping with the midi spec.
Xhip sounds great!
-
- KVRAF
- 12615 posts since 7 Dec, 2004
"Using the same logic, you could argue that any synth not implementing "All Sound Off" and "All Notes Off" does not keep with the midi spec"
midi spec says these commands need not be implemented, and any synthesizer without both a midi input and local keyboard should NOT implement them. this means by implementing these commands xhip is breaking the spec.
it also says sending allnotesoff as a replacement for individual noteoff is absolutely unacceptable. it says all noteon commands must be followed by noteoff commands - allnotesoff is a command to signal that the sequencer stop button has been pressed and it is intended to shut off all notes sent to the midi-input while leaving local keyboard notes alone - the spec adds that if sustain is held, notes from both the midi input and local keyboard should sustain until it is released.
allsoundoff is a 'panic' command which is issued to immediately cut all sound and it can be implemented, but again should only be used in a 'panic' situation like on a mixer when you want to solo a track - it is absolutely not a replacement for noteoff commands.
the host in this case is breaking the spec.
midi spec says these commands need not be implemented, and any synthesizer without both a midi input and local keyboard should NOT implement them. this means by implementing these commands xhip is breaking the spec.
it also says sending allnotesoff as a replacement for individual noteoff is absolutely unacceptable. it says all noteon commands must be followed by noteoff commands - allnotesoff is a command to signal that the sequencer stop button has been pressed and it is intended to shut off all notes sent to the midi-input while leaving local keyboard notes alone - the spec adds that if sustain is held, notes from both the midi input and local keyboard should sustain until it is released.
allsoundoff is a 'panic' command which is issued to immediately cut all sound and it can be implemented, but again should only be used in a 'panic' situation like on a mixer when you want to solo a track - it is absolutely not a replacement for noteoff commands.
the host in this case is breaking the spec.
-
- KVRian
- 709 posts since 16 Dec, 2005 from Novato, California, USA
I dug through the copy of the spec. and I see you are right. So I'll change my wording to "Using slightly flawed logic, you could argue ... "aciddose wrote:midi spec says ... [snip] ...
it also says ... [snip] ...
allsoundoff is a 'panic' command ...[snip] ...
I'm glad you break the midi spec. to solve problems... it's like the movie "the prestige", when borden says you need to get you hands dirty to produce great magic
-
- KVRAF
- 5851 posts since 9 Jul, 2002 from Helsinki
-
- KVRAF
- 12615 posts since 7 Dec, 2004
(makefile)
http://xhip.cjb.net/xhip/releases/v0/b6 ... allgui.dll
Code: Select all
#GUI
#src += ./etc/editor_vertical_sliders.cpp
#src += ./etc/editor_standard.cpp
src += ./etc/editor_standard_large.cpp
#src += ./etc/editor_gsoto.cpp ./etc/xhipeditor_gsoto_osca.cpp
#src += ./etc/editor_gen_adv.cpp
Code: Select all
#GUI
#src += ./etc/editor_vertical_sliders.cpp
src += ./etc/editor_standard.cpp
#src += ./etc/editor_standard_large.cpp
#src += ./etc/editor_gsoto.cpp ./etc/xhipeditor_gsoto_osca.cpp
#src += ./etc/editor_gen_adv.cpp
-
- KVRian
- 889 posts since 10 Jul, 2004
i have given up xhip cos of the clickin in monomode which i cant deal with.
http://www.kvraudio.com/forum/viewtopic.php?p=2885491
http://www.kvraudio.com/forum/viewtopic.php?p=2885491
-
- KVRAF
- 12615 posts since 7 Dec, 2004
which settings are you using, send me a patch and describe it's use.
"the Pro one ...only analog i have experience with does not click."
minimum attack is 2.5ms - 5.0ms.
certain settings were designed to "click" as requested by other users. for example if you use waveform sync-to-noteon you'll get clicks, and the clicks will always be the same. (this was it's purpose)
if you say you lose the punchiness of the sound by reducing the attack to a few ms, really you must not be realizing that the only difference between the sounds IS the clicking. if you want to get very exact sounds, you'll need to sample and then use a sampler to replay those samples - of course you'll lose the "living" feel of the synthesizer - but again the only difference IS the less-precise nature of the synthesizer vs. the sampler.
there are ways to eliminate clicking in patches which "shouldnt" have them if that is the case. we can use sync-note-state-to-osc-phase or something similar. samplers eliminate some 'clicking' by creating more than one voice for the same note, even in legato modes. the voice being released is set to a quick release time of about 5ms, while a new voice is created for the next note. if the 'click' is part of the patch itself however even a sampler wouldnt help you - in fact a lot of the time you need to go to a great deal of effort with a sampler to eliminate clicking, popping and phase-matching issues due to this overlapping while a correctly patched synthesizer simply doesnt suffer from them.
all systems have trade-offs. if you need to have your attack time limited to 2.5ms, i can do that for you as well - or you can buy an analog which you assume doesnt click and have 0 = 2.5ms without ever knowing it, only to find that it has other quirks and issues that you have never imagined. ultimately it's all about knowing what, why, and how, both in terms of the problems you have and fixing them. in this case i'm pretty sure you simply misunderstand the function of the synthesizer and so are unable to identify those parts of the problem that will be required to allow you to fix the patch.
it may not be the case however, so you should send me an audio clip, a midi sequence file and a patch so i can reproduce the clip, and a description of your feelings and what exactly you think the problem is in this case. i can either fix the patch for you and explain to you those things you needed to know, or if it is a real problem i can fix the synth.
just remember not to keep issues to yourself because that is the only sure way to make sure nobody will ever care and that they'll never get fixed.
"the Pro one ...only analog i have experience with does not click."
minimum attack is 2.5ms - 5.0ms.
certain settings were designed to "click" as requested by other users. for example if you use waveform sync-to-noteon you'll get clicks, and the clicks will always be the same. (this was it's purpose)
if you say you lose the punchiness of the sound by reducing the attack to a few ms, really you must not be realizing that the only difference between the sounds IS the clicking. if you want to get very exact sounds, you'll need to sample and then use a sampler to replay those samples - of course you'll lose the "living" feel of the synthesizer - but again the only difference IS the less-precise nature of the synthesizer vs. the sampler.
there are ways to eliminate clicking in patches which "shouldnt" have them if that is the case. we can use sync-note-state-to-osc-phase or something similar. samplers eliminate some 'clicking' by creating more than one voice for the same note, even in legato modes. the voice being released is set to a quick release time of about 5ms, while a new voice is created for the next note. if the 'click' is part of the patch itself however even a sampler wouldnt help you - in fact a lot of the time you need to go to a great deal of effort with a sampler to eliminate clicking, popping and phase-matching issues due to this overlapping while a correctly patched synthesizer simply doesnt suffer from them.
all systems have trade-offs. if you need to have your attack time limited to 2.5ms, i can do that for you as well - or you can buy an analog which you assume doesnt click and have 0 = 2.5ms without ever knowing it, only to find that it has other quirks and issues that you have never imagined. ultimately it's all about knowing what, why, and how, both in terms of the problems you have and fixing them. in this case i'm pretty sure you simply misunderstand the function of the synthesizer and so are unable to identify those parts of the problem that will be required to allow you to fix the patch.
it may not be the case however, so you should send me an audio clip, a midi sequence file and a patch so i can reproduce the clip, and a description of your feelings and what exactly you think the problem is in this case. i can either fix the patch for you and explain to you those things you needed to know, or if it is a real problem i can fix the synth.
just remember not to keep issues to yourself because that is the only sure way to make sure nobody will ever care and that they'll never get fixed.