Page 9 of 11

Re: Bitwait....I mean Bitwig

Posted: Thu Jan 31, 2013 7:28 pm
by JuanSOLO
agent314 wrote:Going to have to experiment tonight.
if you're on the L9 beta,
please vote for the thread I started about "Device Snapshopt Rec, Clear"
AND
"Session Automation recording on Returns" thread

Re: Bitwait....I mean Bitwig

Posted: Thu Jan 31, 2013 7:45 pm
by regretfullySaid
With Bitwig I'm really looking forward to checking out the audio editing inside the clip view and hopefully being able to drag bits and pieces from where ever to bring inside the clip and do further editing.

Re: Bitwait....I mean Bitwig

Posted: Thu Jan 31, 2013 7:51 pm
by stringtapper
I want that.

Image

Re: Bitwait....I mean Bitwig

Posted: Thu Jan 31, 2013 9:04 pm
by agent314
if you're on the L9 beta,
please vote for the thread I started about "Device Snapshopt Rec, Clear"
AND
"Session Automation recording on Returns" thread
Done

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 10:50 am
by simpli.cissimus
agent314 wrote: What I would still love but don't expect to see any time soon, is clip-specific effects. Like, I'd love to be able to have multiple clips on a single track, each with their own effects (and possibly automation).
Have a look at Studio One v2.5 ! It has that exactly !

I love the Macro commands in S1 where you do complex editing with just one click.
Overall same workflow as in Live.(why I switched over to it...)

I'm waiting for Bitwig too.
I like all the new features it promises.
Using 32bit plugins in 64bit mode is the way to go for a DAW these days.
Sandboxing VST's is just genius !

I hope they take their time and sort any great bugs,
so that it comes out usable from the beginning.
I'll rather wait for it..., then have another bugfest !

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 10:59 am
by simpli.cissimus
stringtapper wrote:I want that.

Image
That will be the most coolest thing ever !
Having Reaktor in DAW-form !

Build your own instruments and effects, or change the original ones to your taste.
Exchange the new creations with others too.
That's going to be huge and will be much better, less buggy
and lighter on CPU then MAX4Live.

Wish that would be available in version 1.0 !
Hope it comes before 2.0 !!!

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 2:41 pm
by GUY SMILEY
funken wrote:Image
fucking brilliant.

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 2:53 pm
by JuanSOLO
simpli.cissimus wrote: That's going to be huge and will be much better, less buggy
and lighter on CPU then MAX4Live.

Prove it

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 3:24 pm
by andydes
JuanSOLO wrote:
simpli.cissimus wrote: That's going to be huge and will be much better, less buggy
and lighter on CPU then MAX4Live.

Prove it
The screen shot clearly shows fewer bugs and lighter CPU than m4l

What are you? Some kind of ableton fanboy or something?

Although I would hope it's a bit easier to use. Being able to simply string together modules would probably be more my kind of thing. I didn't get far with m4l. But that's just me.

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 3:24 pm
by leisuremuffin
JuanSOLO wrote:
simpli.cissimus wrote: That's going to be huge and will be much better, less buggy
and lighter on CPU then MAX4Live.

Prove it
you will see. half of all worst abbleton life sheepmen will be biggest bitwig fanboys year from now.

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 3:28 pm
by stringtapper
andydes wrote:
JuanSOLO wrote:
simpli.cissimus wrote: That's going to be huge and will be much better, less buggy
and lighter on CPU then MAX4Live.

Prove it
The screen shot clearly shows fewer bugs and lighter CPU than m4l

What are you? Some kind of ableton fanboy or something?
:lol:

The Bitwig modular environment looks fun, but now that Gen is here with Max 6 the possibilities for creating your own effects with M4L just increased in a big way. Being able to drop raw C code into a Gen patch to create your own Lexicon reverb in Live? Sheeeeiiit.

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 3:29 pm
by leisuremuffin
only idiot without brain like on this forum are using pathetic appleton life. no pdc, badder cpu usage with buggs, no midi toast funktion.

i use drdrum now like all pros.

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 3:32 pm
by andydes
All the programing talent left ableton for bitwig. One year later, they left bitwit and started Dr drum.

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 3:49 pm
by JuanSOLO
I realize M4L can be CPU heavy, especially when building certain audio processing fx.
Yet it can also be very light and useful when doing simple things like building a custom controller device for something like an APC40.

Max objects have superb documentation that make it simple to learn such a complex piece of software.

Reaktor on the other hand, can be very CPU efficient on a lot of fronts,
yet the documentation is not geared towards learning it, and you need tools builders made to learn to build, tools that are not in the manual.

So, those things have been around a while now, and there're great.
How many of YOU guys are even building or editing with them?
How many people are?
This bitwig 2.0 editing looks awesome, I predict it will be relatively the same on CPU maybe a little lighter in areas than M4L.
I dont think it will process audio in a buffer nearly a efficient as Reaktor,
I think it might be easier to learn than Reaktor,
but harder to learn then Max, less documented.
I bet less people will build with it than M4L or Reaktor.
Over the course of 5 years maybe that will change.

andydes is right, my CPU was untouched by looking at that image.
very nice bitwig!

I've been an Ableton fanboy since version 2 and a bitwig follower a lil over 2 years now, DUH :roll:
Cant wait to use it.

Re: Bitwait....I mean Bitwig

Posted: Fri Feb 01, 2013 4:16 pm
by simmerdown
anyone over-using the words fanboy or hater should be beaten mercilessly about the head and neck