Sometimes I look at the code and realize it does things I had no idea it could do. In this case the text width function doesn't discount the color codes (a bug) but it does nonetheless otherwise work as intended.
... that is, assuming I had ever intended for it to work at all.
Lack of unison and a few pops/clicks while editing is what ruined it. Unison is somewhat easy to get over because I can easily do some stereo work in my DAW but the pops and clicks really do it in. Who honestly likes to hear a random *POP!* right in the middle of their track? Those two brought it down to 7/10. If unison was added I would rate 8/10. Fix the pops and clicks and I would rate 9/10. Fix both and you got 10/10.
If you could identify how to reproduce any clicks or pops and check that they also occur in the alpha version and report them to me, I'd appreciate it a lot. I have never experienced any clicks or pops during normal use of the current release of Xhip. It does produce some pops when changing specific parameters such as waveform, filter mode and others but "random" isn't accurate when describing those.
The latest alpha version has fixed the pops generated when switching oscillator waveforms.
If you have any issues you should consider trying the alpha version available at http://xhip.net/alpha/ and reporting any issues you also find in that newer version.
Unison in Xhip is a "true" unison - it simply activates a multiple number of voices and applies detune to them. These are complete voices including 100% of the processing such as filters, waveshaper, envelopes, LFOs and so on. The CPU time required is exactly equal to that required for an equal number of voices. The voice counter will display 64 voices when using 16 polyphony and x4 unison, for example.
Oscillator unison is only supported for the ramp waveform but I hope to allow it on every waveform and provide more functionality in future releases.
Yes. It means that the domain name xhip.net remains the only available. The domain presetexchange.com is now left, so returned back for sale by the Domain Marketplace for any new interested future owner, xhip.net remaining the only available for the Aciddose users and visitors.
Therefore Aciddose should now update the developer link in the current KVR product page, simply. He will probably do after having read our two comments.
Actually it seems someone picked up the domain and this is a nasty parked page with redirects to advertisers.
One would hope they would "fix" the mangled corpse of the domain name system by limiting the number of registrations one person/corporation can make using some sort of sliding pricing scale but they seem to have decided to launch a zombie army of fresh TLDs instead.
That is odd actually, I suppose I must have never bothered to update the developer link. I'm certain the product page link was working though as I regularly get redirects from it to http://xhip.net/synth/.
Thanks for the heads-up! Unfortunately KVR doesn't allow no URL on the "developer" section so I suppose this can just remain the link to the main Xhip site.
You can always contact me via PM or email if you like. The alpha page on the site describes that and I've tried to list as many issues as I'm aware of there.
As for any issues in the previous (7) version, these won't ever be "fixed" as they are until the next release unless they're major, such as a crash or similar. I haven't heard any reports of such issues. If that sort of issue did exist it would be possible for me to fix it, but these sort of "fixes" would just be back-patches to the old version while the same issues are most likely no longer present in the alpha.
Xhip has never really been "0.7", not as in a fraction at least.
Xhip is complete, the current version is the seventh release. I have laid out my plans to a tenth version and beyond, although after the tenth version Xhip will no longer be free.
Due to this, the future versions after the tenth will need a new name. Currently I refer to this as "Xhip 2.0" although this is only an abstract thing we could just as well refer to as "garden salad" or some code-name. To be honest it is just as likely it actually will be called Garden-salad... what I can tell you is it will not be named Xhip.
For people to consider the current and past releases "beta" is incorrect. Not because they are not "beta", but because people do not seem to understand what the letters of the greek alphabet represent in this case.
In the version string "0.7.0.0" each number is divided by a point. The first number is a major release, sort of like a sequel if you will vs. the original series. The current version is the first series for Xhip. Beyond that, the next digit represents the release number which in this case is 7. It is more correct to label the version "7.0.0" than it is to label it "0.7" because of this fact. Nothing will ever go in the leading digit which still counts as "Xhip", therefore it has been dropped.
I hope this will help people to understand the version system although I will continue to use the same system internally, from now on you can simply consider the last release "7.0" and the next release to come "8.0".
Going a little further with this, the first number wouldn't be "version 1", it would be "gamma 1".
The last number is a revision, used to represent something like a bug-fix or a change in the installer or other components that aren't core to the plugin. Essentially the same version (alpha-beta-gamma) only "fixed".
The alpha versions are "latest" stuff. Mostly untested, likely to change but this doesn't mean "unfinished".
The beta versions are the main versions, these are like episodes or releases "1.0" and so on which is why I've changed the number on KVR to match this.
The gamma versions are major versions, as I said more like a sequel or complete remake. You wouldn't expect "gamma 0" to be compatible with "gamma 1" because that is what that number represents. It could be compatible of course, but it would be a completely separate new version and not just another episode of the same series or so on.