Will.

Apple Music was down for maintenance. It's up and running now. Track is also available on Spotify. https://open.spotify.com/album/6uePzPesWJoIyuw8dcyo4J?si=LUZ0JRPHR8y9FRVe5qbj1g&utm_source=copy-link

Good to know. Can you perhaps send us screenshots of your settings?

Apple Music: http://itunes.apple.com/album/id/1559418351 iTunes: http://itunes.apple.com/album/id1559418351?ls=1&app=itunes Spotify: https://open.spotify.com/album/6uePzPesWJoIyuw8dcyo4J?si=Q8zsxqHbRUic2IJIHFW2-w&utm_source=copy-link Youtube Music: https://music.youtube.com/watch?v=0S4Pluo8Pdc&feature=share Napster link: https://us.napster.com/artist/will-ash/album/thoughts-running-wild Amazon Music Link: https://www.amazon.com/dp/B08ZLSBN37/ref=cm_sw_r_cp_awdb_XEHWDTS0Q481HC8WAVPH As of today my track "Thoughts Running Wild" by Will Ash, is available on all major digital platforms. Appreciate the support.

Yes, there is. The latest optional KB Quality install, caused problems by me - it was slowing down my PC. As an Insider to Microsoft Windows I did report this and I wasn't the only one. It's even worse in the new 21H1 (Not out for release yet) and using 3.6GB of memory to run. This might help you to locate or identify your problem. Read Here

Your OUTPUTS can't be "None." Set all your OUTPUTS to a master bus, by creating a BUS CHANNEL naming it "MASTER" (If your using an empty template) and route all other tracks through it.

I see this is up twice.

Okay. Maybe I'm wrong OR maybe i'm being misunderstood. Either way, i see the same answer between what I said and your answer.

Oh - but it does. you need to read what I've said again, cause it expains itself. Using Double Precision in a 32bit OS does not give you nearly as much of headroom as in a 64bit OS. Read carefully what I've said. This does not affect "Quality" but only headroom between the ceiling of the wave file (Dynamically.) You don't get nearly as much of headroom in 32bit as what you get in 64bit. Like Mark said it db thing. 750db (considered as infinite) over 1500db (also infinite)

Not really. What all this mean is . . . In a 32 bit OS you could only access to 4 GB of RAM for each process, and in 64bit that = 192 GB max (if I remember correctly.) So, a 24 bit audio is exactly the same as a 32bit or 64 bit file, these numbers are for the memory address mapping of the OS, the audio is not affected in any form (other than adding headroom.) Internally, most modern DAW's work at 32 bit floating point. Most well known producers will tell you: that they still prefer a 16/48khz audio file for all its grittiness it brings to the audio - over a 24bit file. We can't even hear the difference between 32bit and 64bit. FWIW: This goes for "dithering" as well. This subject is slowly attracting the same attention the "LOUDNESS WAR" did back in 08/09. At the end of the day - its all about taste / and what works best for you at your disposal.

Long overdue.

You can remove this when duplicating tracks . Read here

True. Go into tick mode and shift your timing slight out of time - this i do.

But don't you do this with the velocity bars?

What im actually saying is, on bigger monitors a single column list might be ideal as it projects more information to the user. However, on smaller monitors those that works on laptops without a dedicated monitor - (Personally) a multi-column list will suit the workflow much better. The guy at the time I was collaborating with on a project when this topic popped up, actually brought the idea to front. His word: Can't developers of every DAW think to add this as an option to cater for every workflow out there?

Dropping 27th March 2021!

This so true.

If you say so.

With all respect: How is not having access to all you EQ's on one page, not quicker and having Instant access / over clicking 200 times to get to your favorite EQ at the bottom.

LOL! WTF? ??? ? How is it that more effecient: When the evidence here clearly shows that a flatbed is more effecient than single scrolling column. In fact: You're absolutely correct. Scrolling would be better IF IT WAS POSSIBLE, but it's click at the moment. Absolutely no logic in what you've said. (With the most repect) Sorry.

freezing tracks is pretty much a standard practice. Irrespective of your systems specs. It's old habbits.

Well, this sums everything up - from what I have heard in your mix. If you're using samples, make sure they are the same BPM as your project. Also make sure they are also line'd up with the grid.

Am I the only one checking the "Early Access Feed" first thing when I login to the site everyday? I think I'm spoiled by it. ??

USB 2.0 was released in the year 2000, which is also referred to as Hi-Speed USB. It is the most common version of the USB standard that we use every day. The maximum transfer speed of USB 2.0 device is up to 480 Mbps. Nowadays, USB 2.0 is being replaced by 3.0 in many high-end motherboards. USB 3.0 was released in November 2008/2009, which is the third major version of the Universal Serial Bus standard for interfacing computers and electronic devices. USB 3.0 has gradually become the new standard for USB devices by providing a lot of improvements over USB 2.0. The major one is the data transfer rate. The data transfer rate of USB 3.0 is up to 5 Gbit/s, which is about 10 times faster than the USB 2.0 standard. So theoretically USB 3.0 is better than USB 2.0

Avoid 1903 and 1909 build. Those builds was buggy in general. I'm currently testing the 21h1 build, which has not been released yet / and so far, this version (since the 1803 build) is much more stable. The big upgrade in new features will come in the 21h2 build of Microsoft Windows 10 Get your hands on the "Windows 10 Pro 20h2" / OR / for now, stay on the 1803 build.

Flatbed is ideal. What about those that dont have bigger monitors? We need to cater for them too and a flatbed effects list is ideal for that, but in general cakewalk needs it.