Am I the only one who couldn't care less about touchscreen?

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

Post

You are going to hate this:
Lumit - new multi-touch DAW to be released at NAMM
http://www.kvraudio.com/forum/viewtopic.php?p=6351578

For me if it requires single touch the mouse may be the better solution. Most DAW functions work great with a mouse. If it requires or works better with two fingers or more consider getting touch-screen as I did. I have a 23" ViewSonic 10-touch screen and an iPad Air to use as midi controllers. My main interest for multi-touch is for real-time performance/Creation of music. So a multi-touch DAW is not my preference as the multi-touch takes up more space to accommodate the touching. Lumit could change my mind?

Post

Kalamata Kid wrote:You are going to hate this:
Lumit - new multi-touch DAW to be released at NAMM
http://www.kvraudio.com/forum/viewtopic.php?p=6351578

For me if it requires single touch the mouse may be the better solution. Most DAW functions work great with a mouse. If it requires or works better with two fingers or more consider getting touch-screen as I did. I have a 23" ViewSonic 10-touch screen and an iPad Air to use as midi controllers. My main interest for multi-touch is for real-time performance/Creation of music. So a multi-touch DAW is not my preference as the multi-touch takes up more space to accommodate the touching. Lumit could change my mind?
They even have VST3® SUPPORT lol
Pretty nasty daw though compaired to bitwig
desktop: windows 10 x64, i5 4690k, 32gb ram 1600mhz, 2x ssd 128 gb +2x3 tb, asus gtx 970, asus proz gamer motherboard, no external audiocard
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750

Post

I just wish Bitwig would've stayed primarily on the DAW path. For now I am going to sell it and some stuff and save up for Ableton

Post

it's just a small side project, don't get all the moaning.
JamWide - a cross-platform Ninjam client for DAWs

Post

shonoob wrote:I just wish Bitwig would've stayed primarily on the DAW path. For now I am going to sell it and some stuff and save up for Ableton
don't forget to demo it, quite crashy( tending to crash) at this moment https://forum.ableton.com/viewtopic.php ... 24&start=0 Bitwig is rock stable compared to AL (for me too) 9.5
"Where we're workarounding, we don't NEED features." - powermat

Post

I'm getting a surface pro for my lives, and i think it will be super writing tracks in planes, buses, etc.

I think it's great they are taking this seriously from the start.

Post

shonoob wrote:I am still a beginner but I bought Bitwig because I heard promise of it being a new, albeit cheaper, take of what Ableton was, and possibly even an innovative new DAW in comparison. Sure there have been cool features that were innovative from the start; sandboxing, PDC, grouping, a nice interface etc etc. But now looking at it, still simple stuff like an updated sampler, piano roll update (it colors etc look horrible IMO), basic features like fader adjustment, side browser template size, and automatic replay of samples not saving etc... And now new bugs like sample playback clicking? How can something so crucial like this pass by your team to a full version release? It makes me feel skeptical that Bitwig isn't focusing enough on their DAW nowadays.

....And now with these new advertisements with Microsoft and the touchscreen, and now at NAMM, there is hardly anything to do with the DAW itself AT ALL?, it is just continuous product advertising of roli, surface pro etc... (stuff I cant care less about). It seems Bitwig is pooling all of their efforts into the touchscreen market and other nonsense (In terms of a DAW product).

Am I the only one who is disappointed here? I don't mean to rant, but I bought the DAW for strict computer music production, I didn't buy a 'touchscreen' or surface pro tool, and was hoping the DAW would be backed by a company with the same intent, to innovate a DAW for the desktop/laptop computer platform, not some Touchscreen or touchscreen laptop hybrid.

It seems Bitwig is focusing to take the touchscreen market now? I feel this sort of thing strays from the path of a traditional DAW which is what I had originally purchased. If I had foresight of what is occurring now when I had initially bought Bitwig, I wouldn't have made the purchase, and am greatly considering to switch to Ableton.

Can anyone chime in and give me their 2¢ on this whole thing? Am I overthinking this, or does anyone else feel somewhat ambivalent about the path Bitwig is taking as of late with NAMM and otherwise?
As much as I love the bitwig crew and will support them till the end I have to kind of agree with you. I don't care about touchscreen very much and I hope that isn't their main focus. After 1.3 I felt like the load times for the app start time took a major hit. Suspiciously enough that is when the touchscreen support was released. I really hope bitwig understands that there is a huge hardware resurgence these days and I hope they make that a top priority as well. Still love bitwig but I hope their main focus isnt this whole making music on the fly mentality with touchscreen etc. I hate to quote deadmaus but he said it the best. I hope bitwig doesn't become focused on kids that want to spam VSTs all day long. I mean dont get me wrong I use VSTs to mix and hardware for sounds but I just hope it wont become all VST focused for the laptop touchscreen artists in the long run. On the other side of the coin though maybe its a good thing that they have this niche to help them along quicker with everything. Financially speaking.

Post

Judging on all the silly FR's on this forum, I'm very afraid of this too.
Let's make it functional stable workhorse, not a gimmik that'll wear of.
I don't see myself using a touch screen in the near future.
Bitwig as it is now has enough flaws that need to be dealt with first.

Post

owensands wrote: As much as I love the bitwig crew and will support them till the end I have to kind of agree with you. I don't care about touchscreen very much and I hope that isn't their main focus. After 1.3 I felt like the load times for the app start time took a major hit. Suspiciously enough that is when the touchscreen support was released. I really hope bitwig understands that there is a huge hardware resurgence these days and I hope they make that a top priority as well. Still love bitwig but I hope their main focus isnt this whole making music on the fly mentality with touchscreen etc. I hate to quote deadmaus but he said it the best. I hope bitwig doesn't become focused on kids that want to spam VSTs all day long. I mean dont get me wrong I use VSTs to mix and hardware for sounds but I just hope it wont become all VST focused for the laptop touchscreen artists in the long run. On the other side of the coin though maybe its a good thing that they have this niche to help them along quicker with everything. Financially speaking.
100% mate. I just feel that a touch screen interface is by design a lot less complex, and if that aspect of simplicity skews into the overall Bitwig product then it is a total reason for me to switch towards something like Ableton, which is already developed and has its primary focus on its DAW. Bitwig is still in its preliminary stage of production, where it still needs to develop in many deep ways, and now it's sidetracking toward a touchscreen? It is very disconcerting as a customer. I will certainly find no use for a touchscreen, ever, as I am 100% working out of a studio room, where a mouse and keyboard have the most streamlined & precise workflow with hotkeys and accurate mouse control on faders etc. the touchscreen sounds like a toy in comparison.

As you said, I hope they are just using this ploy for financing, which is understandable, to boost the quality of their DAW as well... If not, I'm afraid they have lost my interest for the foreseeable future (and that of many others that I know.)

Post

PHY6 wrote:Judging on all the silly FR's on this forum, I'm very afraid of this too.
Let's make it functional stable workhorse, not a gimmik that'll wear of.
I don't see myself using a touch screen in the near future.
Bitwig as it is now has enough flaws that need to be dealt with first.
+1
desktop: windows 10 x64, i5 4690k, 32gb ram 1600mhz, 2x ssd 128 gb +2x3 tb, asus gtx 970, asus proz gamer motherboard, no external audiocard
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750

Post

PHY6 wrote:Judging on all the silly FR's on this forum, I'm very afraid of this too.
Let's make it functional stable workhorse, not a gimmik that'll wear of.
I don't see myself using a touch screen in the near future.
Bitwig as it is now has enough flaws that need to be dealt with first.
Exactly, they are in no position to subvert their focus yet. A well developed DAW company would have this privilege, as they would be backed by a professional-level DAW, but Bitwig still feels like it is a Beta-level DAW even after its release, so how can they justify sidetracking and slowing its development already?

Post

shonoob wrote:
PHY6 wrote:Judging on all the silly FR's on this forum, I'm very afraid of this too.
Let's make it functional stable workhorse, not a gimmik that'll wear of.
I don't see myself using a touch screen in the near future.
Bitwig as it is now has enough flaws that need to be dealt with first.
Exactly, they are in no position to subvert their focus yet. A well developed DAW company would have this privilege, as they would be backed by a professional-level DAW, but Bitwig still feels like it is a Beta-level DAW even after its release, so how can they justify sidetracking and slowing its development already?
bitwig needed to slow down their features anyway and work on bugs. But i agree that touch should first come when its privilege to have touch, like first all functions. but something important is stability which bitwig focus on now. That i dont complain about. I dont complain about touch anymore. i agree i dont like the choise. But for the company to bring in money it might be the right choise, they need money to keep devoloping by hitting that small userbase that no one else does. I really dont know what goes on behind the scenes thats why i dont wana say to bad about it anymore. But right now i think bitwig do the right thing working on those bugs making it moore trustworthy so it sounds the same 30 hours later. When i say stable, i dont mean that the software crashes. I mean wierd behavor like velocity when looping a file that someone else brought up. Stuff that makes music sound as not intended. But i love bitwig.

About beta level? not true! Its a version 1 daw. Nothing really to expect! However bitwig is soo good for a version 1 daw. Bitwig actually is soo good that people expect it to be full grown allready. When they try it out they feel so supriced with how well bitwig works and after a while starts to feel they miss those important features. Bitwig had such a positive effect on people that they toally forgot that bitwig was a version 1 daw, but with time they sure notice but still that positive feeling is what makes us be here at kvr. Trying to force our needs to the software we love and want to grow faster then possible. Features are missing and we know but sometimes we forget its a version 1 daw.
desktop: windows 10 x64, i5 4690k, 32gb ram 1600mhz, 2x ssd 128 gb +2x3 tb, asus gtx 970, asus proz gamer motherboard, no external audiocard
laptop: windows 10 x64, i7 mq4700, 12gb ram 1600mhz, 1 tb, asus gt 750

Post

My guess is the DAW market is a crowded one and touch is something that can differentiate Bitwig from it's competitors. For me I'd never use it, and I'd like for them to focus more on core features (and more Linux hardware support) but if touch allows them to stand out and make some $$ to further development - I say go for it. :tu:

Jim

Post

thecrumb wrote:My guess is the DAW market is a crowded one and touch is something that can differentiate Bitwig from it's competitors. For me I'd never use it, and I'd like for them to focus more on core features (and more Linux hardware support) but if touch allows them to stand out and make some $$ to further development - I say go for it. :tu:

Jim
Things like granular synthese stuff is nice with a touch screen. I'm far more interested in controllers that get you NOT to see a screen at all. :party:

Post

thecrumb wrote:My guess is the DAW market is a crowded one and touch is something that can differentiate Bitwig from it's competitors. For me I'd never use it, and I'd like for them to focus more on core features (and more Linux hardware support) but if touch allows them to stand out and make some $$ to further development - I say go for it. :tu:

Jim
By all means, if it boosts the whole productive quality of Bitwig then I am all for it... But from what I understand Bitwigs team is quite small, and I feel they have to pool the majority of their resources into the touchscreen if they are 'supported' by Microsoft or whatever. That is my only qualm, that it will slow the DAW production. If they can somehow expand their team/do both at the same time then I wouldn't have made this thread.

Post Reply

Return to “Bitwig”