whoisp

So what about the current Cakewalk, will it still work? But basically one day when we update windows or load a new plug its will stop working or something along those lines

Beautiful, Intro is sublime. Just my brain, at about 27sec when it drops in, my mind is telling me something but i don't know what, maybe just acoustic with no bass for split second or a pause to a slide down on bass with acoustic comes in, silly i know might be just me. There a couple similar places like this where there could be the split second pause for a big hit for greater emphasise, don't get me wrong love the production, it tick a long nicely and you probably tried it, but sometimes these gaps work or don't. I am only nit picking because you asked haha great work

Basically Pow-r3 as lots of dynamic range (*Smother) and Pow-r1 is more squashed for dance (Lounder)

I still bounce MP3 at 48 (320) highest quality possible you will notice the width is much better on test and less anti aliasing problems with sibilance, not that i use mp3 only to send to friends for demos over wattsapp etc Differing i use POW-R 1 as there seems to be no difference to 3 but im told its better to use Triangular for the perceived loudness where im sure loudness would create more noise and dithering logically, which is not a good thing What differing you sue tom?

100% with you, same for guitar an bass. Doesn't matter how great our systems are, loads of tracks, automation, fx and plugins can eat engine load and processing. Some plugins are very naughty haha

Yes we can become bogged down in tech settings with DAWS and devices. I still will mess with my buffer for mixing vs recording. On a busy project i might bounce project and automation down to one track so i can track vocals. I like to have a stable system so i can just get creative. I still get the odd crash but its normally me rushing in a busy project or a problem plugin. I still bonce my -6db premaster 48/32bit but there is little difference on imagining to check loss even if i bounce pr master at 24, very rare a issue. The only loss what i use to get is repeatedly bouncing down samples i created. I use to have a sample project for creating my samples to then export them in to projects after bouncing. Like an idiot, i didn't realise i could bounce a track(s) and "automation" to a new tracks within a project durrr. So i was using patches and sends to record etc old school. So now my samples and tracking i do in same project im working on. I only used short cut key bounce (no automation only clips) and never new i could bounce automation with track menu, embarrassing lol

I only can record at 24bit my SPDIF and Audio interface are 48/24 stable, i use the 64-bit Double Precision Engine in project for maximum dynamic range and precision but bonce back to 48/24 for digital platforms and video. I create my samples with in the project which is set to 32bit render so there's min loss. I think i defaults at 32bit floating point is the internal processing protocol that Cakewalk employs anyway but it is set at 32 Would you set record to 32 even though my ad on 24

Sorry i was meaning using 48/24bit files instead of 32bit files. Meaning if i remember, 32bit takes about 33% more storage space? If you keep rendering every thing off in 32bit .i.e if you create your own samples like i do and use loads in a project like i do with lots going on, automation plugins and FX etc project gets big and slow. I do say some where in the thread keep files and all setting to 48/24 just so everything a standard. CbB does have the 64 DPE which i use

anything that eats and shits ..... passes gas but im not sure the fart dynamic range that can be represented by a 32-bit (floating point) file is 1528 dB 🤣 but you could get some sonar blip at 700khz

I am not sure why anyone would need more, current DAW with PC and software does not benefit from anything more. 24-bit audio recordings can capture a dynamic range of up to 144.5 dB and you don't need more than that in music on any digital platform. Meanwhile, 32-bit float audio can capture the absolutely ludicrous range up to 1,528 dB. That's not only massively beyond the scope of 24-bit audio, but it's beyond the scale of what even counts as a sound on Earth that will eat your file system when tracking to record etc

In my experience SPDIF is always 44.1 however some modern system where being upgraded to what we was sold SPDIF 48khz and some devices did not work, i am guessing there is something in the PCB chain given its hardware that caused issues. We always got issues when set at 48, sometimes the internal clock and the optical SPDIF clock would create driver and compatibility problems, the days when you wanted to hit device manger with a hammer. There was a time we always got random phantom clicks in recording, tuned out wifi was interfering with the SPDIF hardware and optical cable. We was like great SPDIF no noise from jack plugs etc then we had a phantom click lol We mess about with all the technology to plug a guitar or mic jack plug in anyway lol

What I can tell you working on, pre, post and live broadcasting for ITV as a sound and video engineer. The reality is we want 48/24 for video and music, less issue with dynamic range loss and anti-aliasing can be a real problem, especially with digital platforms. If you need to know more anti-aliasing varying factors with loss and noise read about Nyquist frequency is a good start. Why we often resample 44 up to 48 due to those above issues, but why use 44 in first place and resample you ask. Well only because some studios use a desk that have SPDIF or ADAT at 44 or gave us CD or Digi Tape at 44 and not 48 due to upgrading studio is costly. Don’t forget, you lose some of that vintage tech classic sounds of the pre amps etc with some old gear. i have a desk with AD Conversion: [24 bit Guitar/Bass] [24 bit phantom mic (Mic)] [24 bit (Line)] [24 bit (Simul) great desk pre amps ] back to DA Conversion: 24 bit with Internal Processing: 24 bit (digital mixer section) however its limited to SPDIF 44.1 kHz so i take a line out to 48kHz s to bypass the SPDIF as a hybrid work a round 48/24 is not about our ears, we can’t ear the difference from 44/16 but the digital world does due to things like Nyquist frequency, plugins, software algorithms etc, why we get issues like anti-aliasing, drop outs and much more with massive file size when we push our sampling with audio and midi. If i use the SPDIF, you have to set the cakewalk project, interface and system drivers all to 44.1 kHz or its will create noise, anti-aliasing, cackles and drop outs. That is important to note when working with any standard make sure everything is the same standard or you will get bugs and issues. Cakewalk project, your interface drivers and system drivers are all set to your preference which should be 48/24 and why i bypass SPIDF as im forever changing my setting if i don't and you want a stable system first. Some interfaces have a higher internal clock than 24-bit but i say 48/24 is a safe mode standard At one time, 44/16 was better due to CPU restrictions of audio interface, hardware and CPU etc. 48/24 can still be pushing CPU restrictions mixing with large recorded sample files size, plugins and loads of tracks (play/record tracking hammers your system) but everyone should be on 48/24 standard really unless you have NASA power and hardware,

The reality of it is more disturbing for sure, and governments are still causing wars

Thanx Freddie, ive actually got a job from this song bizarre yesterday, to do a track for a singer in the Philippines and now have to write something in the key of A Major for a young lady that ive not seen or heard lol

Cheers lynn

Nicely polished with great space. I am liking the Indie edge vibe that's coming through on all your work. PS: i am digging all your guitars, iv'e always wanted a Les Paul im still suffering on a squire strat and a Tanglewood jazz box haha

Cheers Nige, i didn 't know what to do so had a noodle

That's how i feel with headphones, shut the whole world out and just feel the music and nothing else.

It's funny, i now preferer doing everything on headphones and will only test on speaks, its how we train our ears i guess

Boeing CH-47 Chinook, tailgated one on those beasts

According to statist survey, 87 percent of the respondents use their headphones to listen to music. In fact in the workplace, 93% reported wearing headphones to listen to music. You haev more and more engineers now mixing on things like air pods and a quick test on monitors which i find interesting. Appears more and more musicians, engineers, and producers do it all the time.

I did manage to finish this at the weekend and in the irony called it The Minds a Battlefield which is how its been feeling

Cheers Tim, first track for about 3months but im still not feeling like my music mojo is back

Yes, the video sync on the vocal got nudged in the render for some reason, gives a talking point haha I guess context of ever "at any time" when never is more so past or future and there is still time as its in the process, but i am no expert in legalese code

The Minds a Battlefield, got a bit of meaning behind it and here's the metaphorical context lol