Mark Morgon-Shaw

In theory if the whole thing is vectors, shoudn't you be able to drag out the entire timeline display to whatever size you want? Otherwise what's the point.

Why do you think it's called Reddit..'cause once you've read it , it's gone

Excited to know theming will be back

It’s rare to see such seamless crossover between heavy-handed moderation and questionable artistic output. At least they’re equally committed to both.

Finally !! I’ve been banging on about the lack of clarity in the new GUI for 18 months and really hoped they'd have done something sooner. It took a flood of users jumping on the free tier to really force them to acknowledge just how badly this interface misses the mark. At least now there’s a promise of making it more comfortable to use — about time. Let’s see if they actually deliver.

Most people I know who make production music work in this type of way, it's rare that a contempary drum sound comes straight out of any single VSTi, there's a lot of layering and processing going on to make them sound modern.

I’ve been working this way for years, and it’s not because I don’t know how to use multi-outs — it’s because it offers flexibility you simply can’t get when everything is tied to a single AD2 mixer. Why I use one AD2 instance per drum element: Total sound independence – I can load a kick from one kit, a snare from another, toms from a third, and cymbals from yet another without being locked into a single kit’s tonal character. Easy layering – Two kicks? No problem. One clean, one heavily processed, perfectly phase-aligned, each with its own FX chain. Separate routing for sidechains – Kick can hit the bass sidechain, snare can trigger reverb ducking, hats can sidechain a synth gate, etc. Creative FX freedom – I can slam the snare with distortion, gate the toms, and run the hats through a delay — all without touching the other drums. Simple freezing/bouncing – Each drum’s audio is frozen independently, so I can commit parts without printing the whole kit. Yes, it uses more CPU/RAM, but on a modern system it’s barely noticeable. For me, the workflow gains outweigh the tiny performance hit. Multi-outs make sense if you want to treat AD2 like a traditional kit, but for hybrid, layered, or heavily processed productions, multiple instances is the way to go.

I had one of these. A Pioneer CTF-950 ( early 80s ). It was my Dad's originally but he never used it much so I persuaded him to let me buy it off him to use in my studio. I think I gave him £80 for it in 88 or 89 But I used TDK MA-XG cassettes with it , with the metal chassis inside the cassette case. Recorded all my original demo masters on it.

Well it's better than nothing, I've put it at 105%...I don't need to do this any other software though so I am not sure why CWS is less legible , maybe just a perfect storm of drab colours, lack of contast and 2d flatness

Be good if it worked for audio as well

There's no native per app scaling as far as I can see and as Sonar is the only app that seems problematic, plus I don't really want to lose the screen real estate on all the other programs I use daily. CbB was fine, as is every other DAW I've demoed - I don't think it's me.

Yet it's still more legible than Cakewalk Sonar

Maybe we could have a GoFundMe

Why don't you all just switch to the new Sonar Free Tier

You can't tell which DAW was used just by listening, so I guess it proves it doesn't matter which one it is - more how you use it.

RME has an internal Loopback so he uses that

Watch the video , they already did that

Pro tip: The best-sounding DAW is the one you actually finish music in.

Interesting point on White Sea Studio's new video today about UI/UX design of DAWs

Slate VSX does this auto-bypass thing on export - might be worth removing it first just to make sure it's not acting up

A friend of mine started gigging again recently and said Studio One's performance mode was a revelation

For the record I am still on Win10

I may have it - just figured out a difference between Sonar and CbB If you minimise a plugin in Sonar with plugin re-cylcing enabled, the next plugin you open appears in the same location with just the title bar visible. If you do this is CbB the new plugin opens in the 'old' location before it was minimised. Maybe this is what's causing the confusion.

I usually have my plugins open on monitors 2 or 3. I don't typically have them open on screen 1 as this is used for my main track view and I don't want anything obscuring it.