yeah of course. there are differences of around -140 dB RMS or less.dawmaster wrote:not all 64 bit daws are equal..yes i knew that reaper has "64 bit compatability"
(what am I doing in this thread?
yeah of course. there are differences of around -140 dB RMS or less.dawmaster wrote:not all 64 bit daws are equal..yes i knew that reaper has "64 bit compatability"

They are? Where is the proof? Have you done the tests? I mean, you say you own EVERY SINGLE HOST, and have MASTERED them all. Surely it's a simple thing for you to prove, right?dawmaster wrote:not all 64 bit daws are equal..yes i knew that reaper has "64 bit compatability"
See, now THIS is something I know. Why? My dog told me he heard the difference once.zeoy wrote:yeah of course. there are differences of around -140 dB RMS or less.dawmaster wrote:not all 64 bit daws are equal..yes i knew that reaper has "64 bit compatability"
(what am I doing in this thread?)
i will kindly leave you and this forum to its own devices...i am sure i am not the first you have run off with your lord of the flies mentality...but in the interest of dignity and my precious studio time i wish you well...may god bless you and yours..i know when i am not wanted. thank you for your time and allowing me to speak on your forum.koolkeys wrote:OUR EGOS? You mean, WE are the ones with egos, Mr. "I have every host and all the great plug-ins because I can afford them. You are just mad that you can't, blah blah blah"?dawmaster wrote:ok guys when you are done finger banging your egos
I think you need a reality check.
Ummmm, no we don't agree. Why? Because proof has been provided for our view. You have provided zero.i think you would agree i made a valid point..that not all code is equal as per sound processing.
I fail to see any real point in this entire quote.granted its all ones and zero's but there is alot behihnd the coding in audio processing and there are newer albeit more cpu intensive processes' that software like protools, cubase 5 and yes even studio one pro are now utilizing within the realm of 64 bit data calculation.if you are like me you might remember the first daws with their 16 bit awesomeness...look how far we have come.look lets not get personal. i know i embellish for dramatic effect but cmon...it makes for good reading along with our technical jargon!!
Brent
Nobody said you weren't wanted. But if you're going to make claims, back them up. Then we can all be friends in this virtual world. By pouting and leaving, you just show that you don't have anything to back up what you said.dawmaster wrote:i will kindly leave you and this forum to its own devices...i am sure i am not the first you have run off with your lord of the flies mentality...but in the interest of dignity and my precious studio time i wish you well...may god bless you and yours..i know when i am not wanted. thank you for your time and allowing me to speak on your forum.koolkeys wrote:OUR EGOS? You mean, WE are the ones with egos, Mr. "I have every host and all the great plug-ins because I can afford them. You are just mad that you can't, blah blah blah"?dawmaster wrote:ok guys when you are done finger banging your egos
I think you need a reality check.
Ummmm, no we don't agree. Why? Because proof has been provided for our view. You have provided zero.i think you would agree i made a valid point..that not all code is equal as per sound processing.
I fail to see any real point in this entire quote.granted its all ones and zero's but there is alot behihnd the coding in audio processing and there are newer albeit more cpu intensive processes' that software like protools, cubase 5 and yes even studio one pro are now utilizing within the realm of 64 bit data calculation.if you are like me you might remember the first daws with their 16 bit awesomeness...look how far we have come.look lets not get personal. i know i embellish for dramatic effect but cmon...it makes for good reading along with our technical jargon!!
Brent
I don't know what is behind each application code-wise, but I'm just waiting for somebody to make a legitimate definition of "bloat". Everyone says the host they like is slick and fast, and others are bloated. Why? What IS bloat? And why does it make a host worse than another?sys2074 wrote:Ah host turf wars! always entertaining!
The really interesting question is: How did the Reaper-guys manage to write such a slick, efficient application where other big companies fail immensely with this task and write bloatware instead?!
using too many shared libraries and/or frameworks, instead of coding the needed functionality yourself. those libraries: 1. take up too much RAM, 2. are sometimes coded a lot less efficiently, therefore are slower.koolkeys wrote:I'm just waiting for somebody to make a legitimate definition of "bloat". Everyone says the host they like is slick and fast, and others are bloated. Why? What IS bloat? And why does it make a host worse than another?
Software that come with truckload of "content" that one might have no use for, but force download/install it anyway.(arheu...live anyone?)koolkeys wrote:So yeah, define "bloat" in a host.
Brent
I always thought that the term bloat refers to features only <0.1% of the DAW users need but they are included and make the whole app more complicated.Goratrix wrote:using too many shared libraries and/or frameworks, instead of coding the needed functionality yourself. those libraries: 1. take up too much RAM, 2. are sometimes coded a lot less efficiently, therefore are slower.koolkeys wrote:I'm just waiting for somebody to make a legitimate definition of "bloat". Everyone says the host they like is slick and fast, and others are bloated. Why? What IS bloat? And why does it make a host worse than another?

Do you know which hosts use too many shared libraries? Have you seen their code? Has anyone seen it who uses the word "bloat"?Goratrix wrote:using too many shared libraries and/or frameworks, instead of coding the needed functionality yourself. those libraries: 1. take up too much RAM, 2. are sometimes coded a lot less efficiently, therefore are slower.koolkeys wrote:I'm just waiting for somebody to make a legitimate definition of "bloat". Everyone says the host they like is slick and fast, and others are bloated. Why? What IS bloat? And why does it make a host worse than another?
So delete it, or choose not to install it. MOST hosts give you the option of what to install or not.bullshark wrote:Software that come with truckload of "content" that one might have no use for, but force download/install it anyway.(arheu...live anyone?)koolkeys wrote:So yeah, define "bloat" in a host.
Brent
How many applications do you know that ASK to write to the registry? That's just silly. The registry is a part of Windows. As long as it's related to the program, who cares?Software that "take ownership" of your station, spreading files and folder all over the place, changing association and writing a full encyclopedia to the registry without even asking.(arheu...Sonar anyone?)
Well, any software should check for a newer copy. I'll agree with that. But bloat? I don't think so. Sloppiness, maybe. But this isn't something that most hosts do as far as I have seen.Software that insist on updating you system dll with... older freaking copies!(arheu...Vegas anyone?)
Give an example. I mean, when it comes to functionalities of a host, who decides what is useful and what is bloat? Maybe I'm misunderstanding what you mean?Any software that let secondary functionalities obscure the primary functions.
Honestly, I don't. All I see are things that you or somebody else may not personally like. But it's not something that I would call "bloat".I could go on, but you get the general idea.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026