One Synth Challenge #85: Xhip (J.Ruegg wins!)

[Dee.P.Tree]

Download link takes me to page with spinal tap video saying "give me some money". .

Does this mean that xhip makers do not want us to do this?

Antti

It's a joke about HTTP error #402 "Payment Required".

In reality that wasn't the error but the error it actually prints was generated, probably 401 (Unauthorized) or 403 (Forbidden). Something about the caching configuration I have isn't right.

Example: http://xhip.net/temp/ (will always generate 403)

Solution: hit refresh.

By the time... Our dear friend Antti gets this reply.... He's already done with his track of this month.

Salutes to my friend...!

[Dartelec]

Sorry, but being somewhat noob here, I have better check from forum:

What about the waveform samples (those which you can load to be played by oscs)? Are they allowed (Rules say - no samples)? If those are allowed they would really change the character of synth.

And what if they are allowed - do you think some kind soul would make a drum-set to be used with xhib "drum" setting?

[aciddose]

My understanding is samples aren't allowed period, otherwise you might as well sample some other complete synth part and load that to play back in Xhip

Anyway it doesn't much matter since Xhip doesn't save the samples you load/use and doesn't really support much in terms of samples.

"Drum mode" is used to play multi-timbral, such that you can do multiple sounds in a single instance. It's most useful for percussion although quite limited as it only plays middle-c and isn't otherwise adjustable.

https://soundcloud.com/xhip/xhip7-drums

This is "drum mode" with some presets I've uploaded to the synth page fed into Xhip Compressor. You can do way better if you do some layering of sounds. (Build a snare out of two or three sounds rather than attempting to fit it into a single one.)

If you need to "tune" a sound like a snare, toms or otherwise the best way is to use an available envelope (sustain max, release max) or even better a modulator (LFO) on pulse with width = 0%. Apply that to master tune (oscillators section) or filter cutoff to tune those parameters. To get multiple tuned toms for example create a single drum sound you like, then tune several duplicates of it loaded on the keys you want.

Unfortunately 7.0 maps C2 = first preset and is a bit weird (below that it seems to leave the preset as last played for the voice it uses).

Easiest way is just to start on the first preset and play C2 and set up your drum map from there as desired.

That can be saved as a bank file if you want to share it and will save in projects just fine.

[psmacmur]

So, I was very excited to see Xhip as this month's synth as I've been meaning to dive into it for ages. And indeed it sounds amazing. However, it doesn't seem to work with Control Link in Studio One. Given aciddose mentioning how everything is achieved through automation, this feels like having one hand tied behind my back. I was going to RTFM to see if there's some midi setup inside Xhip, but don't see a manual on xhip.net. Is it only automatable in Reaper? I'd hate to have to use Reaper ever again, but will if needed for this OSC.

[aciddose]

What do you mean by "MIDI setup" ?

If you're trying to control it via MIDI CCs you need to use the "Map CC" button. This is the same as a typical "learn" button.

Otherwise if for whatever reason that doesn't work for you, you'll need to use an external tool either as a part of your host or another plugin to convert MIDI CCs to VST parameter inputs which are sometimes called "automation".

There is no practical difference whether you use "Map CC" or VST parameters as the CCs received by Xhip are internally translated directly to VST parameters.

[psmacmur]

I don't really know how Control Link works, but for every other synth: I adjust a parameter on the vst interface, I see the name of the parameter in the Control Link box (and the value, which is handy, though Xhip has its own display for that), I drag it onto the track and boom there's my envelope. In essence, S1 is learning the synth, rather than the other way around, but without any "learn" button required on either side. It's brilliant, but somehow Xhip doesn't comply.

I'll give Map CC a try though; maybe that will cause Xhip to export the parameter so Control Link sees it?

There are also deeper manual ways of binding parameters, more like Reaper's approach of picking from a huge Parameters menu (but in a tidy, organized listbox, of course), but I didn't look to see if that gets populated for Xhip . Worst case, I'll try to add an arbitrary CC lane and use "Map CC" to tell Xhip to learn that.

[aciddose]

That sounds like standard VST parameter stuff (setparameterautomated) which definitely works. It may be a problem with the host expecting some sort of order of events that doesn't occur with Xhip. Automation works fine in lots of other hosts though such as Reaper. You just set the envelopes/automation to "latch" and enable record for the track. It then will automatically record any parameter you adjust creating a track for it once you've moved the control.

[Mutant]

Most often when i want to use a physical knob to control a knob on Xhip i just use REAPER way of moving an UI control, then clicking "param", then "learn", then moving a knob on the MIDI controller - no need to scroll through the big list of parameters.
But i just checked and the Xhip way also works flawlessly: Click the Map CC button, turn a knob on Xhip UI, then a physical knob or fader.

[H-man]

That sounds like standard VST parameter stuff (setparameterautomated) which definitely works. It may be a problem with the host expecting some sort of order of events that doesn't occur with Xhip. Automation works fine in lots of other hosts though such as Reaper. You just set the envelopes/automation to "latch" and enable record for the track. It then will automatically record any parameter you adjust creating a track for it once you've moved the control.

Hey Pete, aciddose. I just tested this in Studio One v3.2 (64-bit) and sure enough the parameters are not there. Tested Sonar, Podium, REAPER and Renoise with no issues at all.

Looks like Studio One is just not playing friendly. This DAW compatibility thing has got to be such a total hedfuq for the Devs

[7angram]

Having some fun noodling around with this synth for the OSC. Since there is no documentation there are a few head scratchers in there.

On Reaper 4, when I change some settings on a preset, the changes will persist if I go to another preset and back. The only way I can get back to the original saved preset is if I reload the whole bank. This is very annoying behaviour...surely this is a bug?

Can anybody enlighten me as to how the waveshaper works? Also, not really sure what the xmod options are doing.

[Mutant]

On Reaper 4, when I change some settings on a preset, the changes will persist if I go to another preset and back. The only way I can get back to the original saved preset is if I reload the whole bank. This is very annoying behaviour...surely this is a bug?

I use REAPERS internal preset manager, pretty sure it doesn't write to the current preset if i switch to another, so all changes get lost if i do.
The default Xhip bank has some very nice sounds, but i prefer making my own and saving them in REAPER, not in Xhip native adxi format, so i don't know/remember if it works like you described.

Can anybody enlighten me as to how the waveshaper works?

Haha it is one of the more mysterious parts of Xhip, i go by ear and use an oscilloscope to see what it does.

Also, not really sure what the xmod options are doing.

For example:
Set it to B!->A in oscillators section if you want oscillator B to modulate pitch of oscillator A, use XMOD knob on oscillator A to set the amount of that modulation.
Will be much clearer if you set oscillator B to -inf in MIXER, pitch to some VERY low setting (you can use oscillator B envelope amounts to set it even lower) and its shape to triangle.

Also in that configuration you can use the XMOD knob on osc B to tweak the pitch if the Xmod process threw it off too much (idk if that is its intended use or if it is an useful side effect).

[7angram]

Thanks for the rapid reply Mutant!

Yeah, unfortunately the presets do "stick" in Reaper for me regardless if I use the native browser or Reapers own. Makes it a hassle when you are flipping between presets and trying to learn a new synth. Have never seen any other synth do that, so definitely a bug. But I can just reload the preset bank, so I will survive

Ah, ok the waveshaper is as confusing as i thought!

Thanks for the info on the xmod. So, is this some kind of FM or pulse modulation? Regardless, it usually comes down to lots of knob twiddling until I like the end result

[psmacmur]

Hey Pete, aciddose. I just tested this in Studio One v3.2 (64-bit) and sure enough the parameters are not there. Tested Sonar, Podium, REAPER and Renoise with no issues at all.

Looks like Studio One is just not playing friendly. This DAW compatibility thing has got to be such a total hedfuq for the Devs

S1v3 doesn't even work?! I thought maybe my ghetto 2.6 was to blame. Frankly, if the VST has to do something right for it to work, I'm surprised it works for so many of the free VSTs that come across OSC. I can't even get Map CC to pick up lanes I create from the standard MIDI CC lanes, or pick up a knob on my controller. Guess I'll have to dust off Reaper "one last time". Yep.... automation works in Reaper. But zomg that is a horrific menu.

[Mutant]

Yeah, unfortunately the presets do "stick" in Reaper for me regardless if I use the native browser or Reapers own.

There are 2 parts of the REAPER preset display, i was talking about the "--User Presets (.rpl)--" section which is created once you click "+" and select "Save Preset", not the "--VST patches (.fxp)--" section.

Ah, ok the waveshaper is as confusing as i thought!

I use it to make the sound more "naughty", i think last time to get that nasal quality of CS-80 famous Blade Runner solo brass patch.
Most of the time i just use its filter to boost the lows (with high pass set to about 80hz and resonance to taste) or to tame highs when the main low pass filter is not enough.

Thanks for the info on the xmod. So, is this some kind of FM or pulse modulation?

Cross mod like on many synths, just much more versatile.

[aciddose]

Having some fun noodling around with this synth for the OSC. Since there is no documentation there are a few head scratchers in there.

If you have any questions or issues it will be great for me to have them answered here, although the usual issue is people don't bother to read existing threads before asking. So please do search a bit, or email me via the site instead to keep the noise-floor down.

Having these questions asked helps me with knowing what to include when writing a manual.

On Reaper 4, when I change some settings on a preset, the changes will persist if I go to another preset and back. The only way I can get back to the original saved preset is if I reload the whole bank. This is very annoying behaviour...surely this is a bug?

Not at all. The advantage is that you don't need to remember to "save" your preset as it does so automatically as you make edits. To get things to work correctly really requires one or the other, you can't have both at once. If a "edit" or "working state" is used instead you need to manually save the preset to the user bank and report to the host that the current preset is -1 (edit) as well as the plugin must ignore any "set preset" calls after loading the state as part of a project or .fxb file.

So Xhip just shuffles this around ever so slightly. If you want a "permanent" save of a preset or bank, save it to a file which you'll need to do manually. Otherwise the entire "user bank" (in memory, per instance) is used as a "working state / edit" in memory and you don't need to worry about your permanent backup/saves ever being overwritten unless you do so yourself.

It's a trade-off and to be honest I don't really mind one way or the other. In future versions it might be an option to select the preset management mode.

Can anybody enlighten me as to how the waveshaper works? Also, not really sure what the xmod options are doing.

The waveshaper is a per-voice distortion after the filter and before the second filter. It has been significantly improved in the alpha. In the 7th release it is limited to a fairly mild range as it doesn't do any over-sampling or other sort of anti-aliasing to deal with harsh settings anyway.

[prefilter high-pass] -> [waveshaper] -> [+ mix prefilter bypass]

In other words it uses a low-cut where the low frequency content can bypass the distortion.

This allows you to focus the distortion on the higher frequency content which is useful for adjusting tonal balance as well as focusing on application to filter resonance or other content for a bass sound without having the low frequency content dominate the sound.


The second filter after the waveshaper can be used as a very simple EQ in either low mode (like high-cut), high (as low-cut) or band/notch to pick out specific frequencies.

One setting I often use is 12db high-pass tuned to ~52hz with resonance adjusted to boost bass frequencies slightly. You get about +6db boost before there is too much oscillation.

Another common application for me is to add overtones with the resonance near 100%. For example you can get the primary sound from the oscillators and main filter and then add a bell-like overtone with the second filter, sometimes acting if desired on harmonics added by the waveshaper.

In future versions it would be nice to have additional filter modes (low/high shelf, peaking, etc) although the existing options are reasonably flexible already.


XMod or "cross modulation" takes the output of one or both of the oscillators and uses it to frequency modulate the oscillators. You can get an interesting effect if you sync A -> B, then apply XMod A! -> B.

This means A! ("feedback A") and "-> B" ("modulate B") with the result. In this setting the XMod knob in oscillator A acts as feedback while the knob in oscillator B acts as depth.

The XMod in version 7 is exponential only which means you can't expect the result to remain in tune.

It is best used to apply audio-rate modulation where you need the modulator to be anti-aliased. For example try "B! -> A", set the tuning of oscillator B... In fact I'll just upload this for you to play with.



I've set up a single track, then used "duplicate track" in reaper and slightly detuned and panned the two instances.

https://soundcloud.com/xhip/frehf-haem

edit fixed link: http://xhip.net/synth/releases/presets/presets.zip
(Combination of "FM" and throat clearing.)