Buy or upgrade Bitwig Studio - get U-He's Repro or Hive for free

[BBFG#]

From September 30th until October 7th, existing u-he customers can claim a 25% discount coupon applicable for all products in Bitwig's online store, excluding merchandise.

IRC, it does however, exclude getting Hive or Repro without Studio. Although I haven't taken it completely through the buy process to really know yet.

My account only shows two products available. And for me, buying the full studio makes as little of sense, although that's the idea I started with when I downloaded the demo. 16-Track seems a decent enough balance between what I can't use because of the 8-Track limitations and the bloat that I won't ever use in the Studio.
Right now, it's just about trying to find out about the effects limitation. Which doesn't seem to be covered in the manual, video tutorials or website information.

However, if it's this difficult to clarify something so basic then maybe it is not worth "bothering at all" with.

[Tj Shredder]

However, if it's this difficult to clarify something so basic then maybe it is not worth "bothering at all" with.

https://www.bitwig.com/feature-list/

But the Grid alone would justify Studio…

[enCiphered]

But the Grid alone would justify Studio…

If you like to do sound design, this might be true. I have absolutely zero use for the grid but I use Bitwig a lot. And Studio is indispensable for what it is and what it offers. For me at least.

[BBFG#]

However, if it's this difficult to clarify something so basic then maybe it is not worth "bothering at all" with.

https://www.bitwig.com/feature-list/
But the Grid alone would justify Studio…

Sure, if your into that. I spent a reasonable amount of time today with it, and I get why others would think it great, but it doesn't do anything for me. Same with the other included "feature" synths and sample loops. The ideas are great but the reality is I never use them. The one thing I like is the workflow between the scenes and arranger and of course, the BYO plugins I want and easily extend with sub-mix/patch utility plugins when needed. And that it has a Linux version.
So everything the website throws at us to increase its "value" actually kind of decreases it for me. And there does seem to be a company psychology they employ which I find slightly concerning. Which means more due diligence and taking nothing for granted as I did 8-Track. Or believing that Studio will do everything for me.

If you like to do sound design, this might be true. I have absolutely zero use for the grid but I use Bitwig a lot. And Studio is indispensable for what it is and what it offers. For me at least.

So what other things do you use that the 16-Track specifically doesn't have?

[enCiphered]

double post

[enCiphered]

So what other things do you use that the 16-Track specifically doesn't have?

I have to deal with a big number of tracks and scenes all the time, so I need the Studio version.
And I need a ton of modulation options, another important reason for me to use Bitwig. But I guess this is also available to the 16 track version.

[BBFG#]

So what other things do you use that the 16-Track specifically doesn't have?

I have to deal with a big number of tracks and scenes all the time, so I need the Studio version.

Fair enough. Sounds like we're of the same mind in many ways. I just seem to need less and less tracks as time goes on...
Especially with utility VSTs that allow me a sub mix or synth layering in a single track.

[WasteLand]

If anyone wants the -25% coupon for Bitwig store (good for full license or uprade) please PM me.

i have also a coupon, i had first to discover to get it.. don't need it, so, PM for the code.

-25% coupon for bitwig from u-he.

given away!

[BBFG#]

Well, did an actual use test and choked it with one track. (One instance of Patchwork with 3 u-He synths. Something I do regularly in Cubase on this same system without issue.) CPU usage is really high. Starting at 53% and shooting up from there. And that was the couple of times before this with one plugin per track of four and five tracks. Also noticed Groove Agent doesn't play right within it. Although AD2 works great with it.
Leaning more and more to taking a pass on it for now and revisiting on the next version upgrade. I really like one thing about it. But maybe only that one thing...

[antic604]

Well, did an actual use test and choked it with one track. (One instance of Patchwork with 3 u-He synths. Something I do regularly in Cubase on this same system without issue.) CPU usage is really high. Starting at 53% and shooting up from there...

Cubase uses ASIO Guard, which pre-buffers playback for unarmed tracks - that's why you can't change a patch, order of inserts or edit MIDI notes on the fly without it stuttering and stopping playback. Bitwig is a realtime DAW, because you can do it all easily, you can start playing back from Clip Launcher at any moment, use random and audio-rate modulators & operators that you can't "bake in" in your pre-buffer, etc. So higher CPU usage is expected, because Bitwig doesn't "cheat". Such a comparison is misguided, like being angry that your new Ferrari got stuck when you drove into a forest...

Also, why you're using Patchwork? Put those 3 U-He synths in the native Instrument Layer and Bitwig will spread their processing accross different cores. Use Bitwig's devices as much as possible, because they're optimised for its audio engine, the CPU you're running and its math instructions set.

Check the interview with Claes - the (co)founder and lead dev of Bitwig:

https://dawbench.libsyn.com/episode-10- ... ent-future

[WasteLand]

Cubase uses ASIO Guard, which pre-buffers playback for unarmed tracks - that's why you can't change a patch, order of inserts or edit MIDI notes on the fly without it stuttering and stopping playback. Bitwig is a realtime DAW, because you can do it all easily, you can start playing back from Clip Launcher at any moment, use random and audio-rate modulators & operators that you can't "bake in" in your pre-buffer, etc. So higher CPU usage is expected, because Bitwig doesn't "cheat". Such a comparison is misguided, like being angry that your new Ferrari got stuck when you drove into a forest...

this behavior was also before ASIO Guard... nothing to do with it, Reaper does the same trick, and no 'stutter'.

i am quite used to it.

order or inserts or edit MIDI notes without stuttering, that i never experienced, that goes flawlessly. that isn't a cubase problem, because it does not exist (or I never experienced it while running a project and changing midi notes, etc...).

but putting a new instrument in project, change the order of inserts, playback gap.

i prefer it above no unarmed pre-rendering.

and still, yes! it is real time DAW, cubase, or else...

[antic604]

this behavior was also before ASIO Guard... nothing to do with it, Reaper does the same trick, and no 'stutter'.

No, both of them stutter whenever you do almost anything while they're playing.

[BBFG#]

Thank you, I'll give the Native thing a try. It does seem a little counterintuitive though since Patchwork is a VST synth itself. Therefore shouldn't whatever is on that track as one instrument be spread out on the cores as well? 53% in any normal use seems extremely high to me and I think that's a limitation in itself.
JSYK, I removed the Cubase ASIO and ASIO guard in all my default templates so I'm not sure if your comparison is accurate here. I also don't see Bitwig as a Ferrari here. More like it's a Prius going into the forest where we really need the AWD Jeep to get through it.

It wasn't a stutter, but a complete collapse of the audio in distortion that repeatedly happened. Literally bogged in the mud.
Suffice it to say, I find the lack of power in anything but an urban environment to be restrictive. And throwing more instruments in the panel to distract me from the rural I live in doesn't help that.
Perhaps Patchwork is my winch to help pull me through in certain conditions. Granted, my test was using three of the heavier use synths and most of the layering I use it for is either two of those or three-four of the lite synths.

So I decided to just upgrade to the 16-Track for now since it seems 70% of the Studio is full of things that really don't impress me because I have no real need for them. But I get why others would be and am not wishing them any vexation for that. It's just a preference. I also did some testing using it with Harrison Mixbus and they really seem to compliment each other well at this point. Mixbus has its own limits as a primary DAW but what it does, it does very well. So adding Bitwig seems to be a "best of both" for me here. And they both fit my current thinking of having three OS environment available in my core setups.
I'm in a process of changing how I do things and have already realized that much of that in KVR analogies is like sticking targets on myself and walking through the KVR "shooting range". Even trying to keep behind the shooters will not be enough at times.

But again, thanks for any suggestion in using Bitwig since the manual and tutorials are overly focused on those parts I find no use for. It will help.

Add/edit: Used the native instrument layer and it chokes too, but not nearly as much as when using Patchwork. And again, I tested it using the three heavy hitters on purpose. Which is not the majority of layering I regularly use. So I have some work in redoing my saved in Patchwork regular layers. I wouldn't call this a stutter as much as a hydroplane and loss of traction. I can deal with this.

[WasteLand]

this behavior was also before ASIO Guard... nothing to do with it, Reaper does the same trick, and no 'stutter'.

No, both of them stutter whenever you do almost anything while they're playing.

incorrect. why do i even test, i tested reaper, adding an instrument. no stutter at all.
pre-rendering on. unarmed tracks. of course new track armed, on load, or of course.
in cubase i load instruments, and they are never armed. i arm them myself....

i don't know why think they stutter, with almost anything, i use both frequently, and only cubase stutters when adding an insert/send/instrument or move an insert for instance.
and strangely sometimes not...

so... i have both, have experience with both, and never experienced with the almost anything stuff...

it is nice a gapless engine, well Reaper has one... but cubase not, it isn't -how do say- the thing you want, but i can live it, quite easily. but with other stuff, it works like... bitwig...

tested twice, with Reaper, much bigger project, adding a heavy VSTi, no gap, no stutter.

[Caine123]

Hey guys 2 questions

1. I got hive and repro already, do i get still a new license which i might sell?

2. Is the upgrade price for around 120 bucks any good or does bitwig make better sales sometimes?