What DAW is you using Pro5 ?Pro5 wrote:Yes... lets hope any honey users can help with cross ref to the Great R*ver 32 if they have it..
btw I WOULD leave this next bit in your Navy topic but you don't seem to have one?
I just downloaded the updated (B) version of Navy as A was FULL of bugs and unusable, I heard the gain problems (adding masses of gain when you just enable a band or filter + + + + ) was fixed in "B"? but it's not fixed for me! I'm @88.2khz so this may be why, having read of gain bugs resulting from 'missing vectors' for other acqua plugs at samplerates other than 44/96 (btw 88.2 is getting more common by the day after Dan Lavry's "60k" advice a while back so please don't skimp on testing for 88k!).
The gain bug means I have to drag the output almost to infinty/silence to make it usable, and then it's touchy anyway... I'm going to uninstall Navy again (only just put it on today but it's pointless trying to test it in any meaningful way sadly)
The knobs on Navy are still very 'lightweight' and jerky, they don't rotate at all in a pleasing way, the mouse has no dead zone and interferes with itself when using the middle wheel to scroll a value. Gain bugs are the main thing though, you should let me beta your releases cos lots of stuff seems to slip through (and I used to do QA for a living @ codemasters software testing massive releases pre-sony / microsoft submission which cost a lot if we got it wrong - and I was shit hot at bug testing ) - seriously though, no I don't have time as am trying to finish an album up but I do notice small details that others seem to miss (even if just GUI stuff like the honey pre-amp button shifting over some pixels when activated). I would still suggest a good polish up and a revised honey (separate VCA / channel selectable) before pushing out a slew of new plugs or you'll end up getting the reputation of releasing fast buggy stuff that no user can feel secure purchasing (this is mainly why I'm STILL holding off buying Honey because I just don't know if the CPU spiking will be fixed *for me* on i72700k - this lack of clear information and just 'we'll look into it' is very (too?) relaxed for the kind of prices you are asking.
I say this as a fan of your tech and the sound they can bring, and I'm tired of the rip offs in other algo plugs (Uad, Slate, Waves...) so would like to see your company do very well to show THEM how sound should be done, but maybe you need to slow down new releases and make the current ones solid, some of them already feel 'abandoned' (even if they will get engine updates as default due to the shared tech - they have other non core bugs in some cases).
Please take my posts as well intended feedback, I'm sure you get plenty of it elsewhere too but I'm not 'complaining' I'm just hoping you can polish these plug-ins properly and silence the nay-sayers of your tech (in good time - but don't rush new plug, new plug new plug... until they are ALL solid on ALL DAWS at ALL sample rates!)
Oh.. well actually DO rush your 1176 and your 'pink' C-Strip I've heard of cos I'd love to demo those, and the 'pink' especially before deciding if I still prefer Honey (I am and already was a fan of the H32 mixing desk and its style of eq, its sound, the records it made (not just Jacko either but British stuff mainly!) for years before honey so my heart will always lie with that vs any N3VE, ESS ESS HELL, or APE-EE-I but nonetheless I'd like to compare because I'm not a plug in horder, I want only a few reliable great sounding pieces, certainly only ONE main channel strip and maybe 1-3 other flavours of EQ (inc a surgical algo Pro Q2 etc)... anyway, like I said elsewhere if honey and other plugs were 1/3 cheaper or on a good sale (or combo discount) then there wouldn't be so much over thinking, it's not that I can't afford them, not that I'm not "pro" enough to (hey my music's just been on US TV again this month on a very popular ABC show with 8 million viewers so I can afford.. ) my point is I hate being stuck with plug-ins I end up not using but paid good money for, it's such a waste... especially with your NO RESALE POLICY!? HENCE all my questions up front about honey, cpu spikes, separating the channel/VCA/main thing etc
Lastly I'm not looking for any replies (only from other users - not personal service from 'support' ), I know you are all very busy working on stuff. I just wanted to write it so that you may possibly find something useful in my feedback.
thanks - and back to the music!
Studio one for example is not wery optimized with the aqua's
If you dont use reaper , just try the demo to see if the spikes are still there
Im not saying you should change your preferred daw just to be clear hehe
Its Acusticas job to make the Aquas work on all systems
Reaper is wery optimized with the aquas on a windows computer but i dont know if that fits my workflow in midi
And from what i have heard from other users about reaper it only works really optimized on a pc and not on mac
So right now im using an mac mini late 2012 i7 quad 3rd gen intel 2,2 Ghz
I dont have spikes with the honey in logic x, so it seems aquas do not have a very good compability on different systems and daws to me,
this has to get fixed
not give us blend answers like get a new cpu when the same plugin with same computer works well in another DAW with exactly the same cpu
Honey is working fine on my system even on a 3rd gen cpu quad i7 2,2 Ghz
this is a matter of optimization on all systems and DAW's from Acustica's side
Im getting a little tired of Acustica blaming the user