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

[psmacmur]

My entry for KVR One Synth Challenge #85: Xhip
https://soundcloud.com/peter-macmurchy/ ... apart-xhip

psmacmur - Everybody's Falling Apart (Xhip)

Thank you aciddose for Xhip, it is everything an OSCer could want from a VA.

Made in Reaper 5.16 x64 (begrudgingly and under duress )


14 Xhip instances

DAW FX:
JS Time Adjustment Delay x1
ReaComp x1
ReaEQ x7

Free FX:
A1StereoControl-x32 x1
BlueARP 2.17 x6
Loudmax64 x1
MJUC Jr x1
u-he Protoverb x1
Voxengo Stereo Touch x2
Voxengo Tube Amp x2
Xhip Compressor x7
Xhip Limiter x2
Xhip mDelay x3
Xhip Reverb x3

Tonecarver Nova3 for generating the initial lead sequence, though I recorded it to MIDI and hand edited the result, so Nova3 wasn't in the final mixdown per se.
JS Oscilloscope for understanding Xhip

DR7

[aciddose]

Thank you aciddose for Xhip, it is everything an OSCer could want from a VA.

Except for THREE OSCILLATORS

[Mutant]

Thank you aciddose for Xhip, it is everything an OSCer could want from a VA.

Except for THREE OSCILLATORS

Or even FOUR OSCILLATORS !

[alphahinge]

My entry for KVR One Synth Challenge #85: Xhip
https://soundcloud.com/peter-macmurchy/ ... apart-xhip

psmacmur - Everybody's Falling Apart (Xhip)

Thank you aciddose for Xhip, it is everything an OSCer could want from a VA.

Made in Reaper 5.16 x64 (begrudgingly and under duress )


14 Xhip instances

DAW FX:
JS Time Adjustment Delay x1
ReaComp x1
ReaEQ x7

Free FX:
A1StereoControl-x32 x1
BlueARP 2.17 x6
Loudmax64 x1
MJUC Jr x1
u-he Protoverb x1
Voxengo Stereo Touch x2
Voxengo Tube Amp x2
Xhip Compressor x7
Xhip Limiter x2
Xhip mDelay x3
Xhip Reverb x3

Tonecarver Nova3 for generating the initial lead sequence, though I recorded it to MIDI and hand edited the result, so Nova3 wasn't in the final mixdown per se.
JS Oscilloscope for understanding Xhip

DR7

Nice one

[aciddose]

Or even FOUR OSCILLATORS !

Can I have 20 oscillators and 10 LFOs in a patch if I want?

[doctorbob]

Just a quick note to say I have updated my mix a little - automating the synth and hats for the second part (volume, reverb size and reverb mix) to add a little more musical dynamic interest. Also, have reviewed the whole master EQ and compression and hopefully made that sound a lot better - to my ears it does sound better - but, who can tell with these nearing 70 year old hearing tubes?

DR now a better 8 (rather than a 6!!)

Enjoy my friends.

dB

[loris16148]

I was inspired by another OSCer....whose name shall remain hip....-hip-hop-anonymous (ggeurJ) who managed to pull some crazy sounds from xhip. Anyway had some free time so I created this.....The drums are not created by xhip, and neither is the riser...but everything else is......One instance of xhip for the crazy bass sounds


https://soundcloud.com/loris-solic/xhip-madness

[alphahinge]

Looking forward to sitting down and voting. Only a week left!

[RichardSemper]

Here's my entry:-

https://soundcloud.com/richard-semper/r ... y-romantic

No of instances of X-Hip - 14. (22 patches, 11 used in drum mode over 3 instances)
Made use of velocity control and voices spread in the control area.

DAW - MuLab
DAW Fx Used - MuEcho, EQ, Limiter, HiPass and LoPass filters
3rd Party fx:- TAL Reverb 4, Voxengo Span

DR= 12

For anyone interested the Mulab project file is here:-
https://www.dropbox.com/s/t7rewyetq123p ... s.zip?dl=0
And here are the patches I created for this challenge:-
http://www.kvraudio.com/product/xhip-by-xhip/downloads

[urlwolf]

I bought bitwig this week. And to my surprise, it crashes consistently using the 'released' version of xhip. The only way I can get some kind of stability is by running it inside chainer, a vst wrapper. Argh.

UPDATE: 'released' version crashes, even inside the vst host 'chainer'. The alpha doesn't work inside the chainer, but it seems not to crash bitwig (yet) and it accept changing fxp files. But of course it cannot save presets as fxp, this being bitwig (reason I was using the chainer wrapper). This is really an uphill battle. My only option is to:
- use the alpha
- save presets in the native format, knowing full well it won't be future proof
- hope for the best (not crashing bitwig)

[urlwolf]

Richard, thanks for sharing your presets.
I loaded the 'melodic' bank you uploaded, but it seems to be drums as well. Could it be that it was named incorrectly?

[RichardSemper]

Richard, thanks for sharing your presets.
I loaded the 'melodic' bank you uploaded, but it seems to be drums as well. Could it be that it was named incorrectly?

I've checked the download and it seems ok to me. Make sure you are loading RS XHip Bank1.adxb and that drum mode is disabled, all patches in this bank are melodic ones.

[aciddose]

I bought bitwig this week. And to my surprise, it crashes consistently using the 'released' version of xhip. The only way I can get some kind of stability is by running it inside chainer, a vst wrapper. Argh.

I've just downloaded bitwig 1.3.8 and Xhip 7 works perfectly in both 32-bit and 64-bit.

There must be something peculiar about your system which causes it to fail. Are any of the paths to system files (c:/program data/, etc) using non-ASCII characters? Xhip 7 did not support UTF and relies upon the system providing a ASCII path to the application data directory. Since the ASCII version of these functions are used I can't see any possibility that it should fail although there is literally no other system interaction which could possibly fail. This is assuming the plug-in initially loads and displays the GUI correctly. In which case the bitmaps were loaded and some other system-specific issue must lead to the failure.

Likewise, is the VST plug-in directory containing Xhip in ASCII? Xhip attempts to resolve the plug-in dll path upon load and imports the "default.adxb" init "factory bank" file. Again the functions used are the ASCII version and I can't see how they might fail, although there is a possibility for failure here. Windows may provide a NULL result which Xhip 7 may not have checked for which would then lead to a crash in the plug-in instantiation/init functions.

During the crash bitwig should report the location of the crash. Without a proper stack-trace it is impossible to say whether Xhip actually crashed itself or some other component of the system caused the crash. The authors of bitwig would be much more able to debug an issue from within their own code. I don't have the bitwig code or the ability to fill in information about the host functions involved.

If we could identify the cause of the issue (specific to your configuration) I could then reproduce this condition on my debugging machine and reproduce the crash. From there I could identify the crash location and if within Xhip I could step through the code to identify what the cause may be.

I've tried both routing MIDI and automation as well as switching presets, I'm not able to make it crash no matter what I do.

[aciddose]

I'm able to cause a crash if I place the plug-ins in a non-ASCII path such as users/public/VST/ソース/xhip/. This may be the sauce of your problem.

The solution/work-around in which case would be to create an ASCII path to a VST plug-in directory and install the plug-in there.

[urlwolf]

Thanks Aciddose,
No non-ASCII chars on the path. I think the way to reproduce the crash is to try to load an fxp preset (from the bitwig preset browser). I'm at work now and can't try it.