3.2 speculations

Official support for: bitwig.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Well guys I will bring MY theories to the table:

- I think they are taking their time because a big update is coming... there.. I just said it, I don't think next update is gonna be just "here.. 3 new modulators and a new funky audio glitching device" , there's probably either a lot of workflow improvements coming up, or a new feature that we are probably not seeing coming.

- I'm betting on either the real time collaboration ( at least a first pass implementation of it) or better controller support ( they implemented a whole new hardware API that looks like is gonna be used for a new feature )

- I can't talk about it but I discussed with one of the team members about a feature, that if implemented would be killer... jus teasing you guys a bit ^_____^

Post

brunomolteni wrote: Thu Apr 09, 2020 8:54 am I don't think next update is gonna be just "here.. 3 new modulators and a new funky audio glitching device"
Saving this quote for when the update arrives and it's just that :hihi:
Signatures are so early 2000s.

Post

brunomolteni wrote: Thu Apr 09, 2020 8:54 amthey implemented a whole new hardware API that looks like is gonna be used for a new feature
Can you elaborate on those changes and what features they - in theory - enable? It would be fantastic if we got some kind of object-oriented graphical environment for controller support :o
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

machinesworking wrote: Thu Apr 09, 2020 3:54 am
apoclypse wrote: Wed Apr 08, 2020 2:05 pm I wish people would stop making authoritative statements about Logic without actually knowing how the DAW works. I barely even use the DAW now (S1 user) but I was a user since 5.5 platinum on PC. It's an extremely powerful DAW that is as straightforward to use for the most part as an other DAW. It's just that its so old that I've seen feature requests for things that have been there for many year or people saying ti doesn't do something that it's been able to do since at least version 8.
I flatly stated I've used Logic since pre Apple days, and you throw in nonsense... I have the latest version right here, the way it operates for multi instruments is awkward and lame. It works, never said it didn't, and setting it up is completely ridiculous. + signs next to tracks in a mixer... blehgh! It compromises flexibility with software instruments left and right. I really like Logic for a lot of things, but the way it treats and addresses software instruments is not one of them. Logic flatly refuses to give software instruments the same flexibility as hardware MIDI tracks, the rest of the program is great, but that part is not so great.
People say a lot of things, you haven't shown you know how the DAW works you've just said you do. Just based on the statement I've seen you make about Logic. That doesn't mean jack imo. Sorry (not sorry) if that offends you.

I have multiple DAWs on my computer now. I have had Reaper installed on my machine since at least version 3 or so. Doesn't mean I can make any statements about it's usefulness since I don't actually use it (it's too ugly for me) and I wouldn't either.

Logic is as flexible as any other DAW when it comes to multi instruments. It's certainly easier to use and less awkward than Bitwig where you have to create multiple midi tracks and manually assign the channels, or Ableton where you have to setup Audio tracks manually or whatnot to get those to work. I can get a full instance of Maschine with all 16 outs setup in Logic far more easily than I can with Bitwig. Having to manually set 16 tracks of audio to In in something like Ableton.

Logic's plus sign workflow is similar to how other DAWs work as well, Studio One and Cubase works similarly (thought with a slightly different workflow). It's the way Bitwig works with the Add Chains functionality. I'm not even sure what that means in your view. You can route the output of those anywhere you want, just like any other DAW. So how does it compromise flexibility? What other flexibility are you looking for multi out instruments? Which DAW in your opinion is more flexible. Again an authoritative statement without any actual examples.

Again how is Midi to software instruments compromised? How are software instruments less flexible. Less flexible than what? Please follow up your statements with examples.
Last edited by apoclypse on Thu Apr 09, 2020 2:42 pm, edited 2 times in total.
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post

Double post. Sorry.
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post

machinesworking wrote: Thu Apr 09, 2020 5:32 am
JHernandez wrote: Thu Apr 09, 2020 4:36 am
machinesworking wrote: Thu Apr 09, 2020 3:57 am
SLiC wrote: Thu Apr 09, 2020 12:11 am I think this may be the longest run without an update (we are spoilt) but them maybe it just feels that way as I am locked down!
Wasn't there an update a month ago?
I just got into Bitwig, so I have a while to go before I have update desires besides unrealistic ones, like it getting articulation mapping like Logic or Cubase. or comping.
BWS 3.1 was released Dec 18 2019

Last "update" was some bug fixes and a Arturia MicroLab controller extension on Mar 10 2020

A couple days after that there was a content update in the form of 150+ presets called Space, Time, Color
Where's our collaboration features?
Hopefully in some parallel universe where a version of me actually has a use for it. :D
-JH

Post

They seem to do about 3 real updates a year, so every 4 months or so. Probably spring (April) summer (August) and Xmas (December)

It’s anytime now...but was hoping for before the long weekend 😉
X32 and 24C mixers, S88MK3, Live + PUSH 3, Osmose, RedShift 6, Pro3, S4, Tempera, Syntakt, Digitone, OP1-F, OPXY, TR-1000, Eurorack, TD27 Drums, Guitars, Basses, Amps and of course lots of pedals!

Post

SLiC wrote: Thu Apr 09, 2020 5:16 pmIt’s anytime now...but was hoping for before the long weekend 😉
Bitwig license + free U-He plugin deal ends today, so... ;) :pray:
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

Yeh, you would think something new would have to go on the website by tomorrow...but its kind of late now and tomorrow is good Friday (is that a Public Holiday in Germany? It is in the UK!)
X32 and 24C mixers, S88MK3, Live + PUSH 3, Osmose, RedShift 6, Pro3, S4, Tempera, Syntakt, Digitone, OP1-F, OPXY, TR-1000, Eurorack, TD27 Drums, Guitars, Basses, Amps and of course lots of pedals!

Post

apoclypse wrote: Thu Apr 09, 2020 2:13 pm Again how is Midi to software instruments compromised? How are software instruments less flexible. Less flexible than what? Please follow up your statements with examples.
This is a thread on Bitwig, not sure why you feel the need for this here?


Logic only addresses software instruments by MIDI channel. So with MIDI to the external world, Logic is not broken this way, you can select a specific hardware controller and port on that controller. Software instruments are not given the flexibility of hardware in Logic.

A real world example of how this affect you as an end user is obvious if you like me happen to have multiple MIDI controllers and MPE devices. MPE right away takes up all 16 MIDI channels that Logic allows for AUi's. You can probably go into the Environment and give birth to some abortion of a set up to allow you to use more than one controller in this case, but Logic on it's own isn't going to.

This all plays into Logics set up for multi instrument out, it really looks like they haven't changed anything in the underlying code, you create a multi instrument and it assigns or ties in environment in the background, a 'track' to your instrument. No, none of this is easier and more clear than Live for instance, where it's literally obvious, plain and simple, you select a MIDI track and assign the track to send MIDI channel 2 to Kontakt for instance, if you want you create an Aux or audio track and assign audio out from Kontact.

Here's the stupid part of this, I'm still messing around with Logics multi out system, trying to figure out how to assign additional MIDI inputs to Kontakt etc. I'm sure it's possible but it's not intuitive or easily figured out. You're claiming I need to know Logics system etc. to comment on it and I'm just laughing here. This is exactly what I'm talking about, I could go up to DP, Live, even Reaper, and figure out how to set up multi midi input to a software instrument, without knowing how to do it before. That's simply not the case with Logic, it's a system you need to learn.


Let's get back to Bitwig here. :neutral:

Post

machinesworking wrote: Thu Apr 09, 2020 7:12 pm
apoclypse wrote: Thu Apr 09, 2020 2:13 pm Again how is Midi to software instruments compromised? How are software instruments less flexible. Less flexible than what? Please follow up your statements with examples.
This is a thread on Bitwig, not sure why you feel the need for this here?


Logic only addresses software instruments by MIDI channel. So with MIDI to the external world, Logic is not broken this way, you can select a specific hardware controller and port on that controller. Software instruments are not given the flexibility of hardware in Logic.

A real world example of how this affect you as an end user is obvious if you like me happen to have multiple MIDI controllers and MPE devices. MPE right away takes up all 16 MIDI channels that Logic allows for AUi's. You can probably go into the Environment and give birth to some abortion of a set up to allow you to use more than one controller in this case, but Logic on it's own isn't going to.

This all plays into Logics set up for multi instrument out, it really looks like they haven't changed anything in the underlying code, you create a multi instrument and it assigns or ties in environment in the background, a 'track' to your instrument. No, none of this is easier and more clear than Live for instance, where it's literally obvious, plain and simple, you select a MIDI track and assign the track to send MIDI channel 2 to Kontakt for instance, if you want you create an Aux or audio track and assign audio out from Kontact.

Here's the stupid part of this, I'm still messing around with Logics multi out system, trying to figure out how to assign additional MIDI inputs to Kontakt etc. I'm sure it's possible but it's not intuitive or easily figured out. You're claiming I need to know Logics system etc. to comment on it and I'm just laughing here. This is exactly what I'm talking about, I could go up to DP, Live, even Reaper, and figure out how to set up multi midi input to a software instrument, without knowing how to do it before. That's simply not the case with Logic, it's a system you need to learn.


Let's get back to Bitwig here. :neutral:
My issue with this is that one, anyone who googles how to do this in Logic may find your post and be terribly misinformed because of you biased and frankly uneducated opinion being posted as fact and two, long time Logic users know how to do all of this because it's worked that way since at least Logic 6 or 7. Not sure why it's an issue now "for a long time Logic user".

I wrote a fairly quick walkthrough on how to do what you want in the Hosts forum.

Create Multitimbral instrument, assign Channel in Inspector. Go to Track > Other > Create track using Next Midi channel. Done. Or Just press Ctrl+Return on your keyboard. Done.

How is that different than Bitwig: Create multi-instrument, create other tracks re-assign channels.

S1: Create Multi-timbral plugin, create instrument track route to multi, assign channel.

Live: Create multi, create midi tracks, assign channels.

Logic even makes that easier because it creates the channel with the next available midi channel for you and already routed to Kontakt or whatever multi you have setup. No need to take 3 steps, Logic does it in one. It's as easy if not a bit easier to in Logic as any other DAW imo.

On top of that if you create a track this way it will let you change and route the channel however you want.

So yes I agree let's get back to Bitwig because you clearly don't know Logic as well you purport to.
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post

Would really like to be able to save default presets for all of the objects in the Grid. It can get a bit tiring making the same movements each time you drop something in.

Post

apoclypse wrote: Thu Apr 09, 2020 7:35 pm My issue with this is that one, anyone who googles how to do this in Logic may find your post and be terribly misinformed because of you biased and frankly uneducated opinion being posted as fact and two, long time Logic users know how to do all of this because it's worked that way since at least Logic 6 or 7. Not sure why it's an issue now "for a long time Logic user".
You seriously can't be reasoned with. :neutral:

Logic's method is easily more convoluted than the rest, there's nothing to argue about. It doesn't make it a terrible DAW, it just makes it a bit harder to set up if you're new at it. You basically calling me stupid and a liar isn't helping your case at all. It has not been that way since 6 or 7, but whatever I'm done talking to you about this.

Post

brunomolteni wrote: Thu Apr 09, 2020 8:54 am
- I'm betting on either the real time collaboration ( at least a first pass implementation of it) or better controller support ( they implemented a whole new hardware API that looks like is gonna be used for a new feature )
I thought the controller API changes just made it easier for developers. How would it benefit a new feature other than just being easier to develop all round?

Post

machinesworking wrote: Fri Apr 10, 2020 12:42 am
apoclypse wrote: Thu Apr 09, 2020 7:35 pm My issue with this is that one, anyone who googles how to do this in Logic may find your post and be terribly misinformed because of you biased and frankly uneducated opinion being posted as fact and two, long time Logic users know how to do all of this because it's worked that way since at least Logic 6 or 7. Not sure why it's an issue now "for a long time Logic user".
You seriously can't be reasoned with. :neutral:

Logic's method is easily more convoluted than the rest, there's nothing to argue about. It doesn't make it a terrible DAW, it just makes it a bit harder to set up if you're new at it. You basically calling me stupid and a liar isn't helping your case at all. It has not been that way since 6 or 7, but whatever I'm done talking to you about this.
Sure. It is. OMG! Its so convoluted and hard to do.

Screen Shot 2020-04-09 at 3.58.02 PM.png
You do not have the required permissions to view the files attached to this post.
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post Reply

Return to “Bitwig”