KVR Audio

Kingston · Post by **Kingston** » Fri Mar 23, 2007 1:02 pm

I couldn't find the old xhipeffects filter thread so I'll just post here,

aciddose,

there's a nasty bug in the latest (?) xhipeffects_filter_v6.dll

basically every setting except headroom is saved just fine in Cubase SX3, but as I load projects where the filter is used, and save and load the same project again, the headroom will slowly creep up by itself.

What this means is that when I set an optimal value for the headroom (say 36dB), it will have crept to 6dB after about 5 project saves and reloads.

Basically that means surprise 0dB white noise blasts. :/ not cool.

aciddose · Post by **aciddose** » Fri Mar 23, 2007 9:02 pm

http://xhip.cjb.net/temp/public/binary/ ... ter_v7.dll
http://xhip.cjb.net/temp/public/audio/feltir.mp3

i hope this fixes the problem, otherwise i'll have no idea what is causing it.

Leeate · Post by **Leeate** » Fri Mar 23, 2007 10:38 pm

Hi aciddose,
I am using Acid Pro 6, and get the message a little after playing back the synth randomly (sorry for my English, I translated the alert):

Application error
The command found in "0x7c901010" linked to the "0x7baa0711" memory address. The following process can't be done: read".

For the end of the program click OK.
For an error-seeker click CANCEL.

..and sometimes it exits without any alerts.
What could be the matter?
(In an older version that I had there was only a line displayed in Acid, and when I played some notes, it quited immediately. )

disturb · Post by **disturb** » Fri Mar 23, 2007 10:56 pm

aciddose : filter v7, isn't working in Live 6.0.5 here, i get no output, not even dry.

Just thought i'd let you know...

cheers

aciddose · Post by **aciddose** » Fri Mar 23, 2007 11:21 pm

acid pro and live are the two most buggy hosts on the planet, so these things do not surprise me. you can try using another host for now, i might fix these 'problems' some time in the future.

_starcraft_ · Post by **_starcraft_** » Sat Mar 24, 2007 12:11 am

http://www.kvraudio.com/forum/viewtopic ... sc&start=0

comon guys download this utility courtesy of asseca and lets get xhip skinned !

ps:i'm tryin myself but with no luck till now...

SARcazm · Post by **SARcazm** » Sat Mar 24, 2007 1:09 am

aciddose wrote:acid pro and live are the two most buggy hosts on the planet, so these things do not surprise me. you can try using another host for now, i might fix these 'problems' some time in the future.

Odd. Though I can't speak for Live 6.x, certainly Live 5.2 is very stable on my Wintel platform and the only VSTs with problems are Mach V (a Mac product poorly coded for Windows seemingly as an afterthought) and some SE creations. I've yet to have a problem with Xhip, tho I admit I've only touched its surface.

Barbarossa · Post by **Barbarossa** » Sat Mar 24, 2007 9:26 am

aciddose wrote:... and live are the two most buggy hosts on the planet, so these things do not surprise me.

That's very strange, since Live is the most stable sequencer i ever used. For example i have had a huge FX-chain on a Z3ta hookline, i couldn't load in Reaper without crashing or becoming unstable.
It is even quite impressive to see the chain opening it's 17 plugin windows at once when inserted.

Tracktion, where i had developed this chain became extremely unstable. Also Reaper, where i tried to transfer it. But when i transferred the chain to Live, i was surprised. There occured not a single crash and i was able to complete the whole project, like: 6 instances of Kontakt, 1 Battery, 1 V-Station, subgroups, and with CPU eaters like Waves IRx and roughly 100 plugins, all easily frozen/unfrozen (within one second) on an Athlon 1.4 GHz (!!!). Everything stayed 100% stable.
The loading time of the project was shortly over 4 minutes for only the plugins and MIDI, with all audio removed.
So Live is definately not the buggiest host on the planet.

Leeate · Post by **Leeate** » Sat Mar 24, 2007 11:16 am

aciddose wrote:acid pro and live are the two most buggy hosts on the planet, so these things do not surprise me. you can try using another host for now, i might fix these 'problems' some time in the future.

Ok, then I'll do the classical method of rendering and loading back as a wav, because i like your synth very much. Greets.

aciddose · Post by **aciddose** » Sat Mar 24, 2007 11:43 am

sorry, i confused "live" with "logic". anyway i cant be bothered to fix bugs that only occur in specific hosts right now. i really need to do other things. if you can reproduce the problem in multiple hosts and you can identify specific behaviours which act as triggers, then i will be able to debug this. the messages you get by default showing an address and error code are absolutely useless.

if the problem only occurs in one specific host, that leads me to believe the problem is with the host and not with xhip. i did fix some problems with 'logic' a few weeks ago, but i still have not finished even dealing with that. i do not really want to have to add specific workarounds for many hosts until the beta phase.

disturb · Post by **disturb** » Sat Mar 24, 2007 12:21 pm

No worries, speaking for myself, i was just trying to point out that whatever you fixed in filter v7, actually made it NOT work in Live, so that'd be cool if it could be avoided in future releases, or until you have more insight on the problem...
I just wouldn't want not to be able to play with filter v8 whenever it drops

Kingston · Post by **Kingston** » Sat Mar 24, 2007 12:48 pm

aciddose wrote:http://xhip.cjb.net/temp/public/binary/ ... ter_v7.dll
http://xhip.cjb.net/temp/public/audio/feltir.mp3

i hope this fixes the problem, otherwise i'll have no idea what is causing it.

Thanks. I think it fixed it. (I'll be back if the parameter starts moving by itself again.)

[edit]

uh oh, jumped the gun. it works in wavelab5, but there's no sound going through it in Cubase SX3 at all! doesn't seem to depend on settings either. it's silent.

[/edit]

xhip synth question. Where does it save the midi CC mapping? The mapping itself works ok, but I thought it would automatically and globally recall the mapping everytime, despite the preset I'm using?

aciddose · Post by **aciddose** » Sat Mar 24, 2007 10:47 pm

cc mapping is a temporary implementation and will be removed once the event routing system is implemented. nothing is saved in project files from xhip at this point and i will not implement saving until i get everything that needs to be done first based upon the todo list finished.

i have no idea what cubase/etc problems are. i didnt change anything other than where the headroom parameter is set. i forgot to add +0.5 in order to round the input parameter rather than floor it. nothing else should have been affected other than the headroom parameter.

here is another version anyway since i forgot to implement the improvements to feedback/saturation compensation. the filter now matches the one in xhip once again.

http://xhip.cjb.net/temp/public/binary/ ... ter_v8.dll

do not be afraid to crank the saturation to 100% with 100% res now, it will automatically compensate to ensure near-zero aliasing. a sideffect is that noise bursts caused by aliased harmonics lining up with non-aliased harmonics, leading to out-of-range harmonic amplitudes are prevented due to the fact this can no longer happen.

aciddose · Post by **aciddose** » Sun Mar 25, 2007 7:51 am

i've finished testing basic changes to the modulation code required to allow for individual modulation depths for A/B sources.

it seems with individual depths xhip requires 140% cpu power. i'm fairly certain i'll be able to optimize away this extra requirement though, and i think after making these changes it will become possible to further optimize the modulation code in order to get a net speed increase.

the working section of the todo list now reads:

- implement individual modulation depths for A/B sources
- optimize modulation in order to regain original speed

i'll be working on this and after i'm part-way through the 2nd part, i'll upload version 0.6.12.0. alpha 12 due to the modulation being changed.

aciddose · Post by **aciddose** » Sun Mar 25, 2007 9:24 am

http://xhip.cjb.net/xhip/releases/v0/b6 ... 6.12.0.dll

http://xhip.cjb.net/temp/public/xhop.mp3

ok, so this is going to be difficult to optimize. i realized quickly after making the required changes to the code that it is actually not slower by any means. infact, the difference is simply that time isnt saved by being selective with what code sections are executed anymore. now, rather than being twice as cpu hungry (it is, but...) it is simply using the same amount of cpu regardless of what type of modulation is enabled.

overall, it seems there is a significant speed increase here thanks to the conditionals having been removed. it seems to be 30% faster.

in order to get the selective execution back without the conditionals i'll have to implement some pretty tricky stuff. i think i can squeeze slightly more speed with things as they are, then i'll think about being tricksy.

remember since stuff has been changed this wont load the old patches correctly, once again. i've been warning everyone not to make collections of patches with xhip for this reason. i loose all my patches too. once i get to the testing phase before beta 7, then it will be safe to create patches again.

XHip--Please finish your synth!!