-
Posts
1,613 -
Joined
-
Last visited
-
Days Won
1
Everything posted by Mark Morgon-Shaw
-
Please add colour customization at least for PRV
Mark Morgon-Shaw replied to Maria P's topic in Feedback Loop
Well it's good enough for Hans Zimmer so....🙄 -
Please add colour customization at least for PRV
Mark Morgon-Shaw replied to Maria P's topic in Feedback Loop
Nobody? I’ve got to disagree there. Cakewalk’s MIDI core is solid, but it’s missing a lot of things other DAWs have had for years: humanize, iterative quantize, non-destructive quantize, probability/randomisation tools, per-note expression, proper MIDI FX racks, etc. Even the Articulation Maps — while useful — aren’t as tightly integrated as Cubase’s Expression Maps. There’s a reason most big Hollywood film scores get written in Cubase or Logic. They just offer deeper, more modern MIDI toolsets that streamline the workflow. Cakewalk still feels stuck in the mid-2000s on that front. -
Mine works fine..just a cheap M Gear Pedal and an M Audio Midi Controller I don't recall having to set anything up , it just worked
- 4 replies
-
- sustain pedal
- effects
-
(and 1 more)
Tagged with:
-
Music PC - New Build specs - feedback
Mark Morgon-Shaw replied to TracingArcs's topic in Computer Systems
I specced one up for a friend of mine who also works in production music, and even with the best prices over at PC Part picker it was only ÂŁ100 less to get all the parts than over at Scan, inc the build, delivery and 3yr warranty. So he ordered it from them and it arrived yesterday - I persuaded him to go for the 12 core Ryzen instead of the 8 core and not pay what were asking for Windows 11 -
Not Liking the look of the New Sonar Interface
Mark Morgon-Shaw replied to mark foster's topic in Cakewalk by BandLab
They made a clear design choice to move away from the skeuomorphic style and go fully 2D flat, paired with a more muted colour palette that has noticeably less contrast and saturation than Skylight ever did. Add to that some overly abstract icons and font choices that don’t always read well, and the end result feels less functional as well as less engaging. That's the problem in a nutshell. -
Before Cakewalk I used MusicX ( Amiga ) which was a great sequencer, and this was hooked up to Fostex X28H 4-track cassette via Midi Time Code with various outboard gear. No digital audio recording in those days unless you had a sampler. Then I switched to the midi-only Cakewalk ( V4 I think ) in the mid 90s as the Amiga was a dying platform and I've used various versions of Cakewalk or Sonar ever since. At one point I had an ADAT synced with Cakewalk Pro Audio 9, plus outboard which gave me quite a bit of flexibility. I've dabbled with others, made tracks in Reaper, Bitwig, Studio 1 & Cubase but I know Sonar too well to re-learn a different DAW unless I have no other choice. I use what use , there's loads of features I've never touched even in CbB & Sonar..like I've never found a sampler much use even when I had a hardware one back in the day, I don't use the built in Pro Channel FX or things like Worksapces because I learned to use it before these things existed. Since Bandlab took over , the best things they added IMHO were the new Export module and Arranger tracks which both make my life easier for making deliverables for production music libraries. The worst thing they did was downgrade the visuals and make everything flat and drab looking.
-
Thanks for that but I don't mean pasting a note, I am either drawing or playing it in
-
I constantly have to do this ! I'm not sure if it's me but did they changed the way it works at some point? The issue I have is when adding even just a single a midi note via the PRV to an existing track, it always seems to create a new clip in the track view. This is maddening as stray notes become hidden 'behind' other clips and I have to bounce them to a single clip afterwards to consolidate so I can see them all properly. I might be mis-remembering but I thought at some point if you placed or recorded new midi data that overlapped an existing clip it was automatically consolidated.
-
Whilst these aren’t features I’d personally use, I 100% agree with @Xel Ohh – it’s crazy that the BandLab App and Next have features missing from the flagship DAW. More modern tools, tighter BandLab integration, and workflows that give continuity for BandLab App users would definitely broaden Sonar’s appeal, especially to a younger audience. I genuinely thought when BandLab acquired the Cakewalk IP that’s where we were heading – Sonar would become the pinnacle of the ecosystem, with all the same features as the entry-level apps so users could move through the product stack seamlessly. Yet all these years later, it still feels like we’re miles apart.
-
Try Waves Torque
-
Sent you a PM
-
I’ve run into this as well – at first I thought it was user error, but it’s consistent. I just opened several recent projects and in all of them the PRV keyboard strip was closed by default. When I switch to Cakewalk by BandLab, the same projects open with the strip visible in its normal position. In Sonar, if I drag the strip back into place and re-save, it seems to remember it the next time I open the project. I also noticed the track pane is closed in all these projects. I’m pretty sure it should have been open in at least some of them – I do occasionally close it, but the PRV keyboard is something I always leave open.
-
Make CbB perpetual license for 100-150 euro.
Mark Morgon-Shaw replied to Kurre's topic in Cakewalk by BandLab
The BandLab Membership itself doesn’t seem to cater for professional users. It’s clearly aimed at up-and-coming artists who need promo tools, distribution, mastering, etc. That’s a completely different crowd from the hobbyists we see on these forums. Right now you’ve got three very distinct groups: Hobbyists (mostly older) – just want a solid DAW to make music for themselves. They’ll happily buy once, maybe pay for an update every few years, but they aren’t spending monthly. Aspiring/“wannabe” artists (younger) – they’re chasing exposure, playlists, distribution, branding tools. BandLab Membership is built for them, but they don’t care about a heavyweight DAW like Sonar. Most of them are in FL Studio, Ableton, Logic, or just on the BandLab app itself. Professionals – We don’t need distribution bundles, mastering gimmicks or social features. We just need a rock-solid DAW that lets us work quickly and reliably, with clear licensing so we know our projects will always be accessible. That’s it. The problem is BandLab’s marketing is all over the place. They’re trying to pitch Sonar to three very different audiences at once — but the product and business model don’t properly serve any of them. Hobbyists resent subscriptions, pros need ownership and stability, and the younger artist crowd doesn’t see Sonar as relevant or modern enough compared to the competition. It just feels scattershot — like they’re tone-deaf to the core user base and missing the expectations of the next generation at the same time. So instead of capturing new users, they’re bleeding their legacy base while failing to onboard the younger crowd. -
Make CbB perpetual license for 100-150 euro.
Mark Morgon-Shaw replied to Kurre's topic in Cakewalk by BandLab
There are two major missteps with Sonar that have caused the most backlash and driven users to jump ship to other DAWs: The new GUI – They’re only now starting to fix it almost two years on, but it should never have been released in that state. The licensing model – Deeply unpopular from day one, with still no alternative option. Both were completely avoidable own goals. With a bit of foresight and genuine engagement with the user base, neither issue needed to happen. It’s a real shame — Sonar used to be one of the major DAWs in the industry. Now, for most people, it barely registers. Hopefully, now that they’ve finally addressed the GUI problem, they’ll listen to their users and rethink the licensing model. -
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.
-
An important announcement from Cakewalk
Mark Morgon-Shaw replied to Starship Krupa's topic in UI Themes
Why do you think it's called Reddit..'cause once you've read it , it's gone -
Excited to know theming will be back
-
An important announcement from Cakewalk
Mark Morgon-Shaw replied to Starship Krupa's topic in UI Themes
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