KVR Audio

Tj Shredder · Post by **Tj Shredder** » Thu Jun 10, 2021 4:21 pm

PieBerger wrote: ↑Thu Jun 10, 2021 6:25 am
antic604 wrote: ↑Thu Jun 10, 2021 6:20 am
Tj Shredder wrote: ↑Thu Jun 10, 2021 6:13 amThe “why you left Ableton” thread is mich more on topic and flooded by Bitwig users. Ableton should be scared…
Paraphrasing the popular saying, I'm sure they're shitting their pants on their way to the bank
Probably not, because they have people like you, me, SLiC and the rest, who still paid for/use both

I might even get Live as well, not to use it as my DAW, but to create and share some Max4Live patches. Because beside Bitwig I am still with my old love Max/MSP…

cubicruler · Post by **cubicruler** » Fri Jun 18, 2021 9:01 pm

Can we somehow analyse DAW usage by number of submissions to marketplaces like beatstars or even better - splice? Also sites like fiver and others, one could count how many producers/musicians mention a particular DAW… What do you think?

EnGee · Post by **EnGee** » Sun Jun 20, 2021 9:43 pm

If I leave Bitwig this time, it would be for good! I have left it twice and return to it since its release. I liked a lot the direction of Bitwig 3 but I'm not excited at all about version 4 except its native support for Apple Silicon chip.

What annoys me now are several things:
1. No midi files review (like in S1, Cubase and Reaper). Live is also shit in this regard by not implementing this.
2. Markers in the arrangement are not good enough as other DAWs.
3. Operators are waste of development energy and time! I'd prefer if they implemented "Grooves" like in Reason and Live.
4. Hardware support is "strange"! I wished if they just copy Live's exact functions for the hardware! Instead I have to relearn the whole implementation like using my midi controller as "Device" and "Tracks" or "Mixer" modes! For example, why not just use the buttons on my MK ii controller to separate the instrument functions from the mixer or tracks functions? There are already "DAW" button, "Analog Lab" button and "User" button, why not using that?!
5. When exit Bitwig, all my controllers seem stuck in last operation! Also, sometimes the scripts are not very stable. Some error messages about the controller has stopped are occurring randomly while working normally inside the DAW! In short, no robust support for hardware or at least much less stable than all other DAWs!

From other side, I like the Bitwig team. They are very friendly and polite. They are always welcoming me when I return and wish me to return once again when I leave

They listen always when you have something to say, but of course most of the times just listen!

Anyway, I'm faster now in Live because of the very good hardware support and I feel more integrated now with the workflow. Live also has a huge drums and instruments (like strings and keyboards) library. In synths, I say it is a Draw between those DAWs as Bitwig has wonderful synths that I like besides the Grid (Phase 4 and Polymer). However, I think Live is better in their direction (for me) while Bitwig looks more and more for geeks rather than musicians!

sQeetz · Post by **sQeetz** » Mon Jul 26, 2021 5:06 pm

I just sold my license a couple of days ago.
Mainly because of a bug that was annoying me to no end and Bitwigs Support final answer on the issue:

thanks a lot. Unfortunately It looks like currently there's not really a way to improve this due to the way the plugin hosting and window handling works between Bitwig Studio and macOS.

Best regards,
Bitwig Technical Support Team

And because I wanted to focus on Logic.

EnGee · Post by **EnGee** » Mon Jul 26, 2021 5:12 pm

sQeetz wrote: ↑Mon Jul 26, 2021 5:06 pm I just sold my license a couple of days ago.
Mainly because of a bug that was annoying me to no end ...

If I may ask, what was the bug?

sQeetz · Post by **sQeetz** » Mon Jul 26, 2021 5:48 pm

EnGee wrote: ↑Mon Jul 26, 2021 5:12 pmIf I may ask, what was the bug?

When a plugin window is open (and focussed) the mouse pointer icon changes to the ones that would be shown if the plugin wasn't there.

https://www.dropbox.com/s/whi8nnx3nav00 ... 1.mov?dl=0

Happens with all plugins. I thought that the update with M1 support could maybe fix it, but it didn't...
I know it's kinda minor, but it bugs me.

hitherepeople · Post by **hitherepeople** » Mon Jul 26, 2021 5:50 pm

That would drive me nuts! Could you at least still use the parameters with the janky bug?

sQeetz · Post by **sQeetz** » Mon Jul 26, 2021 6:02 pm

hitherepeople wrote: ↑Mon Jul 26, 2021 5:50 pmThat would drive me nuts!

Indeed it did!

Could you at least still use the parameters with the janky bug?

Yes, the plugin is, despite being frustratingly annoying, fully usable... and that's probably the reason it's not up too high on the fix-list

EnGee · Post by **EnGee** » Mon Jul 26, 2021 6:08 pm

sQeetz wrote: ↑Mon Jul 26, 2021 5:48 pm
EnGee wrote: ↑Mon Jul 26, 2021 5:12 pmIf I may ask, what was the bug?
When a plugin window is open (and focussed) the mouse pointer icon changes to the ones that would be shown if the plugin wasn't there.

https://www.dropbox.com/s/whi8nnx3nav00 ... 1.mov?dl=0

Happens with all plugins. I thought that the update with M1 support could maybe fix it, but it didn't...
I know it's kinda minor, but it bugs me.

I haven't noticed this before! Is it a Mac only bug? I'll give it try on Linux/Windows and see.

sQeetz · Post by **sQeetz** » Mon Jul 26, 2021 6:12 pm

EnGee wrote: ↑Mon Jul 26, 2021 6:08 pmI haven't noticed this before! Is it a Mac only bug? I'll give it try on Linux/Windows and see.

I think it's Mac only. Don't know if it also happens with Intel Macs, though.

MuzikFreq · Post by **MuzikFreq** » Mon Jul 26, 2021 6:16 pm

Mainly left because the odd way everything works is more for experimental and too basic. Requires nesting of plugins to do a simple job.
EQ+ which is amazing is also dumb on why they force latency for each instance used.
The business model just doesn't sit well with me as well.
Went and bought Live 11 Suite instead

antic604 · Post by **antic604** » Mon Jul 26, 2021 6:39 pm

MuzikFreq wrote: ↑Mon Jul 26, 2021 6:16 pm Mainly left because the odd way everything works is more for experimental and too basic. Requires nesting of plugins to do a simple job.
EQ+ which is amazing is also dumb on why they force latency for each instance used

How is that any different in Live? Its native devices are also mostly basic and you need to layer & nest stuff in Instrument/FX Racks to get something equivalent to a basic VST)?

Also, EQ+ will likely be fixed whereas Live's EQ8 is years behind it in terms of workflow. If you can work with EQ8, you could've worked with Bitwig's EQ5 until EQ+ is fixed.

Both DAWs are awesome so it's not like you made a mistake switching, but your rationale for switching is weird

syntonica · Post by **syntonica** » Mon Jul 26, 2021 7:12 pm

sQeetz wrote: ↑Mon Jul 26, 2021 5:48 pm
EnGee wrote: ↑Mon Jul 26, 2021 5:12 pmIf I may ask, what was the bug?
When a plugin window is open (and focussed) the mouse pointer icon changes to the ones that would be shown if the plugin wasn't there.

https://www.dropbox.com/s/whi8nnx3nav00 ... 1.mov?dl=0

Happens with all plugins. I thought that the update with M1 support could maybe fix it, but it didn't...
I know it's kinda minor, but it bugs me.

This is Mac-only? Because then, somebody is not respecting the tracking areas that should be set up by both the host and the plugin maker of the focused window. The focused window should be catching all the mouse events and not passing them on to the host to respond to, i.e. changing the cursor pointer to follow what's underneath.

Sounds like a simple bug to me to fix. ¯\_(ツ)_/¯

SLiC · Post by **SLiC** » Mon Jul 26, 2021 7:20 pm

Live 11 'Suite' devices aren't basic, the (AAS) instruments, fx (like the new hybrid reverb), new MAX stuff and bundled sound packs are absolutely top notch. Probably the reason (along with PUSH 2 integration) I seem to boot up Live more than Bitwig, just so much great content to explore.

'EQ+ will likely be fixed'....its been out a long time and we have had a lot of updates (including 4!) without it being fixed...Bigwigs 'update plan' model puts them under a lot of pressure to keep putting new stuff out, sometimes that can be detrimental to finishing of the details I think.

xbitz · Post by **xbitz** » Mon Jul 26, 2021 7:23 pm

btw. open<>closing/focusing plugins(groups) can be key assigned

I like it in BWS (AFAIK AL also knows it just AL blocks the macroed plugin params) ... so can live with nesting

Why you left Bitwig?