That's a bold statement. Where's your evidence for that?
You should use whatever fits best. If Bitwig no longer works for you, then good for you. Find something that does work.
The horror, a modulair DAW focussing on their modulair philosophy.
That's a bold statement. Where's your evidence for that?
You should use whatever fits best. If Bitwig no longer works for you, then good for you. Find something that does work.
The horror, a modulair DAW focussing on their modulair philosophy.
1. My bold statement comes from the fact that there were no user request ever addressed by bitwig. I know you will bring to my attention the MSEG and how great they are. Well, people asked for MSEG in 2016 with release of V2. Making them in 2023 is not addressing user request. Probably they just wanted them themselves as what they always do. So no, they never ever made user request to come to life.
It's not a fact because it's a demonstrable false statement.vroteg wrote: ↑Fri Mar 29, 2024 5:58 pm 1. My bold statement comes from the fact that there were no user request ever addressed by bitwig. I know you will bring to my attention the MSEG and how great they are. Well, people asked for MSEG in 2016 with release of V2. Making them in 2023 is not addressing user request. Probably they just wanted them themselves as what they always do. So no, they never ever made user request to come to life.
Why is it idiotic? If something can make you so angry, I guess it's time to move on or change your priorities. Or go in therapy (not even making a joke here).vroteg wrote: ↑Fri Mar 29, 2024 5:58 pm 2. "Its not for you and you need to move on". This is the most idiotic statement one can make. It is by the way for me. Because what I need the most is stability of the host. And I can forgive them anything as long as they keep platform stable. So can I use it, please? Sorry I did not ask you in the first place. My bad. I apologize for using it without your permission master...
Based on what? On your own bias because you don't care about any of the devices?
The audacity of people to reply on a public forum! Even worse when they don't agree with me! You sound like a little child with entitlement issues.vroteg wrote: ↑Fri Mar 29, 2024 5:58 pm PS: Oh yeah, I forgot I'm on bitwig forum among bitwig community and I'm not allowed to say anything other than "What a great update". I know, how dare I constructively criticize this program that show you C7 note every time you open midi editor. But as bitwig developers say: its not a bug, its a feature!
Bye!
Yup... I'm so glad they got rid of that old messy thing. The new one is so much better...
First of all, no software company, including Bitwig, has any obligation whatsoever to listen to you.
The problem with your statement there is that there are very few, if any, bugs that have been in the code for years.
i've never used any version of Bitwig's browser pre-v5. This looks like generic Windows Exploer/old school Mac Finder. That kinda sorta looks like how other DAWS all have the expandable lists but it's all pre-expanded and taking up your whole screen. No thank you.
1. His sluggish movement but was there from V3. What are you talking about?...pdxindy wrote: ↑Sat Mar 30, 2024 1:31 amFirst of all, no software company, including Bitwig, has any obligation whatsoever to listen to you.
Second your supposed fact, isn't. There are more counter examples than I could list. During the 5.1 beta cycle, users were asking for Bitwig to address the sluggish movement of automation points and they did, in the next beta. There were multiple such examples in the 5.1 beta cycle alone.
The problem with your statement there is that there are very few, if any, bugs that have been in the code for years.
I have pitched this to them a year ago:zerocrossing wrote: ↑Fri Mar 29, 2024 7:25 pm The only things I'd like to see are an audio looper, like Live's but better, mono audio render, and sub-bar length audio export.
Looking through your posts on KVR, they are nearly all negative comments. So I understand that you don't like Bitwig fanboys here
What’s awesome about Ableton’s Looper is that it allows you to set the project tempo by defining the first loop.nowiamone wrote: ↑Sat Mar 30, 2024 8:33 amI have pitched this to them a year ago:zerocrossing wrote: ↑Fri Mar 29, 2024 7:25 pm The only things I'd like to see are an audio looper, like Live's but better, mono audio render, and sub-bar length audio export.
https://bitwish.top/t/looper-live-loopi ... tions/4610
Since then, i also built a working audio looper (video is posted there, too).
But maybe you already know that, and just ask for a native device. I agree;
Despite having built my own Bitwig Looper, i would prefer it, if they integrated what my Looper does as Looper Panel. Wouldnt that be awesome?
However, touch osc has certain advantages, which would be hard to emulate in Bitwig, unless that new (imaginary) Looper Panel also was a highly customizable Editor for custom controls. For instance, it’s possible to auto-arm the right tracks necessary to record midi vst instruments into the audio looper via a button in my touch osc interface - such individual needs could only be met if Bitwigs looper system would be highly customizable and not some tiny (crappy) standard plugin like Abletons looper. I mean, Abletons Looper is a prime example of what not to do in any future Loopers, imho. Like forcing users to a mouse action of dragging and dropping the audio into the clip Launcher. Not having access to single overdubs. No latency compensation. No visual overview of several loopers...
So i m quite happy we can directly record and access overdubs in Bitwigs launcher now, while also having great visual Feedback
Yea, this is more of a general Ableton strength though. Bitwig doesn’t give access to that function, sadly. We d have to ask Bitwigs team to please include that function in the Api and make it accessible via grid , for example. I have heard about workarounds but they seemed incredibly fiddly and non workingzerocrossing wrote: ↑Sat Mar 30, 2024 2:32 pmWhat’s awesome about Ableton’s Looper is that it allows you to set the project tempo by defining the first loop.nowiamone wrote: ↑Sat Mar 30, 2024 8:33 amI have pitched this to them a year ago:zerocrossing wrote: ↑Fri Mar 29, 2024 7:25 pm The only things I'd like to see are an audio looper, like Live's but better, mono audio render, and sub-bar length audio export.
https://bitwish.top/t/looper-live-loopi ... tions/4610
Since then, i also built a working audio looper (video is posted there, too).
But maybe you already know that, and just ask for a native device. I agree;
Despite having built my own Bitwig Looper, i would prefer it, if they integrated what my Looper does as Looper Panel. Wouldnt that be awesome?
However, touch osc has certain advantages, which would be hard to emulate in Bitwig, unless that new (imaginary) Looper Panel also was a highly customizable Editor for custom controls. For instance, it’s possible to auto-arm the right tracks necessary to record midi vst instruments into the audio looper via a button in my touch osc interface - such individual needs could only be met if Bitwigs looper system would be highly customizable and not some tiny (crappy) standard plugin like Abletons looper. I mean, Abletons Looper is a prime example of what not to do in any future Loopers, imho. Like forcing users to a mouse action of dragging and dropping the audio into the clip Launcher. Not having access to single overdubs. No latency compensation. No visual overview of several loopers...
So i m quite happy we can directly record and access overdubs in Bitwigs launcher now, while also having great visual Feedback
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement