The Top 3 Things You Hate About Your Main DAW ?

[fedexnman]

Might have to do the Laptop thing on a Saturday or Sunday ..... No way during the week though , thanks for the tip .

[Kalamata Kid]

In Cubase when overlapping two audio clips only the top clip is heard. Yes, I like stacking clips on the same track.

In FL Studio no sign that ARA will ever be supported.

In Studio One

1. Just about anything related to MIDI. No MPE, no Input Transformer/Logical Editor, no Event List, no Staff View, no Articulation Management. There's like 50 things that go into this particular item.

In Reaper the mile long drop down menus.

[lfm]

StudioOne v4

#1. GUI colors - everything is shades of gray.
Mostly inspector - that have no distinct colors difference between modules.
But also plugin popup - caption bar completely blend into background, unless looking at X-button to close I don't see it at all.
I find my eyes wondering about to find what I am looking for - often 5-10s.

But color scheme also regarding coloring tracks, you cannot see what is highlighted and selected.
There should be a bar on top all through the track, or something, that is clearly seen being selected.

#2. GUI Colors
#3. Midi configuration so external gear get one definition, not as now you need to create one for keyboard input and one for output. Even though each have selectable port for in/out - they don't show up other than on one side in selecting ports. Really weird choice.

That's it, I love it otherwise. Light on system, stable as anything.

[mumpcake]

My main DAW was Cakewalk Project 5.

1. Did not support 64 Bit
2. Could not get jBridge to work correctly with it to support 64 bit plugins.
3. Has not been developed for maybe a dozen years, so no hope of getting 64 bit to work.

That led me to go to Bitwig

1. You cannot audition midi files from the browser and have them played on a current track.
2. There are certain things which are not at all intuitive in their implementation. For example tap tempo or removing plugins from collections. Worse, these are not documented in the manual.
3. The developers don't seem to get that #1 and #2 are issues.

[Elektronisch]

On Fl Studio:

1. Some plugins that require certain option to play audio rate after rendering are not delay compensated. But team is working on fixing that.
2. Mixer is still not attatchable
3. Chanel strip cannot be selected as a separate window

Studio One:

1. Cannot change the tempo of audio files (very useful when doing pre-mixed dj sets). It always timestretches audio unlike in other existing daws. And they are not working on implamenting such feature despite community asking for this.

[kelldammit]

DP:
1) Latency compensation needs to be expanded. Some very high latency plugs basically end up causing the channel they're on to be delayed once max compensation is reached.

2) Would love a better mechanism for rendering stems

3) Better metering on channels (display of peak values would be nice, being able to assign meter colors to values is even nicer...k-meters on master out would be great, too).

Cubase:
1) When selecting a clip in the arrangement, it'd be nice if the other clips on that track were visible/accessible in the editor.

2) Following on #1, a visibility tab in the editors would be nice, so that you don't have to constantly refer back to the arrangement for visibility/selection.

3) The usual vst3 annoyances...obnoxious vst2 sidechaining, preserving mono channels, etc.

[J. Smith]

Studio One
1) Bad looking waveforms.
2) Bad looking fonts.
3) No pool for MIDI clips.

FL Studio
1) Browser hasn't seen proper updates in years.
2) No proper fades or clip gain system in the playlist.
3) The existence of the channel rack.

[mholloway]

Ableton Live 10

1. Where the hell is Bounce In Place? Every other DAW has added this, most of them added it YEARS ago. It's completely missing from Live.

2. I'd like it crash a bit less, or, dare I ask, not at all.

3. oh I dunno, better video support I guess?

[Coxy]

Logic Pro X

Its dogshite overly limited sample browser. Which doesn't support removing columns, reverts to random order (not alphabetical) on every new project and it's tedious audition ability where if you're browsing samples via arrow down or arrow up and allow the preview to finish playing you won't be able to continue browsing samples this way and now need to click with the mouse to reactivate audio preview. This cycle continues till nausea kicks in. Apple should be embarrassed.

Its dogshite overly complicated mixer. The way it handles bus sends, the way it handles audio routing in it's 'environment' the way I cannot easily render send FX tracks.

Its dogshite handling of combined midi and multi out plugins (think drum samplers) An absolute abomination that makes it feel like some sort of torturous ritual.

Its dogshite drum machine designer Looks simple and intuitive on the outset but if you've tried to set it up as a multi out sampler triggering custom (that is, your own) samples to independent outputs that are triggered via independent midi regions you'll know how much more tempting it is instead to insert splintered cocktail sticks into your urethra for fun.

Other than that it's great, generally we get along fine and it suits my needs. It's no Samplitude though least it's stable.

[jancivil]

Logic Pro X

Its dogshite handling of combined midi and multi out plugins (think drum samplers) An absolute abomination that makes it feel like some sort of torturous ritual.

Someone once had a question at VSL forums, they couldn't figure out how to set up VE Pro, take its outputs in Logic so I went in to have a go (I decided not to use it behind a related reason, the tortuous workaround for multiple MIDI ports) and I got tired, I never did sort it.

[jancivil]

Recently I, for the first time tried to use Cubendo Track Quick Controls (and VST QC, though I don't know how this is different) and it was pretty hateful. It works, but having only 8 is ludicrous. It turns out the device isn't compatible with current versions anyway. But a PITA set up as already indicated in here.

Otherwise I don't hate anything but buggy behavior.

[Freaqpeak]

1. Remote control of plugins suck. 8 Quick Controls? Needs something like Studio One's Control Link.

1. +1. Its almost laughable.....no real remote controlling in 2019.

2. No controller macros

3. No modulators for vst parameters (not midi).

[chk071]

Recently I, for the first time tried to use Cubendo Track Quick Controls (and VST QC, though I don't know how this is different) and it was pretty hateful. It works, but having only 8 is ludicrous. It turns out the device isn't compatible with current versions anyway. But a PITA set up as already indicated in here.

It sucks. I don't know why Steinberg never implemented proper MIDI controller support. Studio One shows how it can be done. In Cubase, there are like 3 different methods, which are all pretty obsolete/less functional.

[Funkybot's Evil Twin]

Recently I, for the first time tried to use Cubendo Track Quick Controls (and VST QC, though I don't know how this is different) and it was pretty hateful. It works, but having only 8 is ludicrous. It turns out the device isn't compatible with current versions anyway. But a PITA set up as already indicated in here.

It sucks. I don't know why Steinberg never implemented proper MIDI controller support. Studio One shows how it can be done. In Cubase, there are like 3 different methods, which are all pretty obsolete/less functional.

What I have hard time reconciling is how robust Cubase's overall feature set is in relation to how piss-poor their hardware control of plugins is. A "Control Link" type system in Cubase (along with ARA which should be here soon) would be just about all I'd need to never want to use another DAW again.

[jancivil]

All I ever did with Cubase back when was Mackie Universal, and I didn't do that much with it.

I have this little NanoKontrol by Korg, a nifty little thing and it works as a transport control and faders, and switch banks of faders and all of this perfectly as Mackie Universal. But I want it to control MIDI CC, and it doesn't. It's a known issue for High Sierra and Cubendo, who knows when it'll get fixed. I think I had looked at QC and confirmed it works for someone once years ago but this was the real test, and this is something that should have been deprecated LONG ago IME.