What's new

Bug in Olafur Arnalds Chamber Evolutions

dubline

New Member
Hi All,

Just wanted to inform the community (current users and potential buyers) about a significant bug that I discovered in the OACE instrument. I bought it in large part on the strength of the Waves instruments, which sound good for the most part, but I realise (and have confirmed) that almost all of the close-mic samples for the Basses Waves are badly distorted. I'm not sure how this made it through QC at Spitfire, because it's glaringly obvious, and sounds like shit, but for the moment they don't have a fix but am told they are working on one. Which doesn't help me with my current project ;(

A sample of the sound attached.

Anyhow, buyers beware, and current owners hopefully there will be an update soon.

Cheers,

David

[AUDIOPLUS=https://vi-control.net/community/attachments/basses-waves-mp3.19063/][/AUDIOPLUS]
 

Attachments

HeliaVox

Active Member
Yup, just checked and my OACE have the same distortions.
So I went into the Advanced folder and played all of the bass patches in the Individual Waves folder. The only one that has the distortions is the patch called b - -Basses - Waves Ord Longest.nki.
All the other ones were distortion free.
Even the bass patches were ok in the Other Patches folder - Basses Waves (™ Pro).nki.
Now I only tried the close mics because you mentioned it.
I didn't try any of the other mic positions.
Ok, strike that, I just tried them and no distortion.
Strange, that.
I totally agree that there should be no distortion in the samples themselves, but to be honest, the bass waves are so quiet, I literally had to put my headphones on, turn up the volume almost all the way up, and then crank the volume in Kontakt itself to be able to clearly hear it.
At lower volumes, for me, it was less distortion and more of a clopping type noise, almost like horse hooves.
I'm sure Spitfire will rectify it.
 
OP
D

dubline

New Member
The problem arose for me as soon as i tried to bring the basses out of the background. I agree that it would hardly be noticeable in a dense mix, but for the cues that I was working on I wanted the waves to have a central (and close-up) presence and realize that it wasn’t going to be possible with the distortion.

Spitfire has been responsibe and have promised a fix.

/d
 
OP
D

dubline

New Member
This is all a bit dramatic for a bug that’s going to get fixed, isn’t it?
Doesn’t seem overly dramatic to me, generally just an appraisal of what the bug is. I did have a genuinely dramatic moment when I realized that the cue that I’d been working on was glitching and couldn’t figure out why. Hopefully this thread will help others avoid that situation.
 

thesteelydane

Senior Member
Doesn’t seem overly dramatic to me, generally just an appraisal of what the bug is. I did have a genuinely dramatic moment when I realized that the cue that I’d been working on was glitching and couldn’t figure out why. Hopefully this thread will help others avoid that situation.
I don’t know...maybe give the developer a chance to fix it, before you hang them out to dry in a public forum? Posts like this really hurts reputations and sales, and for no good reason. If you had received rude and dismissive customer service, then yes, sure, or the bug goes unfixed for months, absolutely, but give them a chance first, is all I’m saying.
 

jtnyc

Senior Member
I don’t know...maybe give the developer a chance to fix it, before you hang them out to dry in a public forum? Posts like this really hurts reputations and sales, and for no good reason. If you had received rude and dismissive customer service, then yes, sure, or the bug goes unfixed for months, absolutely, but give them a chance first, is all I’m saying.
I see nothing wrong with the OP. He wasn’t disrespecting Spitfire or hanging them out to dry. He was just pointing out an oversight and letting people know what to expect. From a buyers perspective, I appreciate these kind of posts.
 

thesteelydane

Senior Member
I see nothing wrong with the OP. He wasn’t disrespecting Spitfire or hanging them out to dry. He was just pointing out an oversight and letting people know what to expect. From a buyers perspective, I appreciate these kind of posts.
Sure, I can appreciate that point of view, and it’s not a big deal. But try to see it from the other side: you’re a developer and suddenly you see one of your products mentioned in a headline next to the word “beware”, on the leading industry forum, before you’ve even had a chance to address the issue. Not entirely fair, me thinks - but maybe it’s just me? I mean, nobody puts bugs in their instruments on purpose.
 

ka00

Senior Member
Sure, I can appreciate that point of view, and it’s not a big deal. But try to see it from the other side: you’re a developer and suddenly you see one of your products mentioned in a headline next to the word “beware”, on the leading industry forum, before you’ve even had a chance to address the issue. Not entirely fair, me thinks - but maybe it’s just me? I mean, nobody puts bugs in their instruments on purpose.
Yeah, it’s just the choice of that one word, “beware”. A word more suitable to danger or a scam. Normally you’d expect the same thread title without beware and maybe with a question mark at the end. Not a big deal but yeah, annoying if you are the developer.
 

rrichard63

Perpetual Novice
... maybe give the developer a chance to fix it, before you hang them out to dry in a public forum? ,,,
I think this issue is worth posting about, especially given the OP's very measured tone. It may save one or more of us from blaming the problem on our own gear or our own skills, and then chasing our tails trying to figure out what's wrong the project we are working on.
 
OP
D

dubline

New Member
Yeah, it’s just the choice of that one word, “beware”. A word more suitable to danger or a scam. Normally you’d expect the same thread title without beware and maybe with a question mark at the end. Not a big deal but yeah, annoying if you are the developer.
The use of “beware” was simply “be aware”, and not in any way to damage or question the developer’s reputation. I have been, and will continue to be, a customer and a fan of Spitfire’s products. As mentioned previously, the intention in posting was to have other users avoid the trouble that I went through in diagnosing a problem in my mix that initially had me pulling my hair out...
 

ka00

Senior Member
@dubline Yeah man, no worries. It's clear you have good intentions. Thanks for pointing out the bug. Hope it gets resolved soon. Was mainly responding so that @thesteelydane didn't think he was being overly persnickety.

I guess it's always worth me remembering this is an international forum and that English is used slightly differently in different locales (this google image result aligns with my expectation of the word). Misunderstandings are bound to happen. :)Beware.jpg
 
Last edited:

Diablo3

Active Member
I don’t know...maybe give the developer a chance to fix it, before you hang them out to dry in a public forum? Posts like this really hurts reputations and sales, and for no good reason. If you had received rude and dismissive customer service, then yes, sure, or the bug goes unfixed for months, absolutely, but give them a chance first, is all I’m saying.
From what I've read aroud this site's forum, Spitfire doesn't deserve any consideration. And OP wasn't wrong. At all. He hung them out to dry? Lol. You've got some nerve...
 
Top Bottom