Open letter of advice to Bitwig

[hibidy]

When will the collaboration feature become available?
This feature is planned for version 2.0.

This is the kinda stuff that gets me. Why are we discussing 2.0 when it's at least 1/3rd of a year away in availability for 1.0

It's really no wonder cat pics fill the world of bitwig

[OzWozEre]

Sorry guys, you can't make the argument that "because Linux has a large user-base in things like web-servers, super-computers, and embedded-systems etc., it should be able to make the jump to desktops".

All the use-cases for Linux are very specific use cases, we are not talking about general computing needs, i.e. the kinda stuff that folks want from their computers, and by extension, their OSes.

And in the general computing sense, Linux is severly lacking, which equals -- "no-one gives a damn" -- no one wants to be "held back" when it comes to their main OS, the thing that they use for *everything*.

Now, I don't think that means we *can't* have strong Music Production Apps in Linux, in fact I think that would be great, why?

Because, just like web-servers, there is a very strong case for having a computer *that just does* music production.

I think about this all the time when I use my MacOS to run S1 and various VST plugins etc. -- I don't *really* need to be running MacOS -- If the underlying OS was some flavour of Linux and all my plugins and DAW etc. worked just the same -- why not?

It would certainly be cheaper, freer (as in freedom) and more "cleaner" (in the one-use-per-system sense of the word).

Afterall, most if not ALL the DAWs out there, except for of course Logic, have their very own Non-OS-Specific GUIs and UX constructs *anyway*.

Imagine, if we start focusing on Music Computers [1], like we did in the 80s [2], and not OSes.

[1] http://www.musiccomputing.com/studioblade



[1] http://www.old-computers.com/museum/computer.asp?c=88\

[justin3am]

I have no advice for Bitwig. They are smart guys and I think they know what they are doing. Maybe I wouldn't have made announcements so early but I wouldn't say it was a mistake on their part. On the contrary, it appears to have worked in their favor in many respects.

Bitwig will get here when it gets here (and yes folks, it is real).

Without saying anything specific... there is a lot to be excited about in Bitwig Studio. As soon as I get the go-ahead, I'll talk about what has me excited about Bitwig Studio but until then, I don't think it helps anyone to speculate.

[jeffh]

Try to ask M-Audio or Native instruments to code drivers for super computers or smart phones. Have you noticed the subject of my post?

Dude, just admit that you have no idea what you're talking about, you're just repeating things you've heard, where I have actual experience and expertise in the subject matter.

Don't believe me?

http://www.alsa-project.org/main/index. ... nstruments
http://www.alsa-project.org/main/index. ... dor-MAudio

AND NATIVE INSTRUMENTS THEMSELVES:
http://www.native-instruments.com/knowl ... nder+Linux

Knowledge Base
Native Instruments hardware under Linux
All NI audio interfaces can also be used under Linux operating systems. This includes AUDIO 4 DJ/AUDIO 8 DJ, AUDIO KONTROL 1, GUITAR RIG MOBILE I/O, the KORE 1 controller, the second and third generations of the RIG KONTROL, and the SESSION I/O interface. Both the audio and MIDI functions of these devices are supported.

The necessary ALSA drivers are included in kernel versions 2.6.22 and above. Native Instruments does not provide any kind of support or guarantee for these drivers or for using its products under Linux.

STRAIGHT FROM THE HORSES MOUTH. Go ahead with your snappy reply, I'm waiting...

I have personally tried a half dozen soundcards under Linux, and they all worked great... You don't even need to install drivers, as they're already in the Linux kernel (Firewire devices are the only ones that require a separate driver, but they mostly "just work" too).

This is where you can admit that you were wrong and apologize, or continue making a bigger arse of yourself by repeating the same old obsolete knowledge from 15 years ago.

[fedexnman]

Im excited about Bitwig coming to Linux , they are using JACK instead of REwire on Mac and Windows too .

[debra1rlo]

Without saying anything specific... there is a lot to be excited about in Bitwig Studio. As soon as I get the go-ahead, I'll talk about what has me excited about Bitwig Studio but until then, I don't think it helps anyone to speculate.

i was VERY excited about the USB-to-feline interface you were describing... uh oh, i mean, um...



yes, i meant, ummm, lovely weather we're having

[standalone]

Try to ask M-Audio or Native instruments to code drivers for super computers or smart phones. Have you noticed the subject of my post?

Dude, just admit that you have no idea what you're talking about, you're just repeating things you've heard, where I have actual experience and expertise in the subject matter.

Don't believe me?

http://www.alsa-project.org/main/index. ... nstruments
http://www.alsa-project.org/main/index. ... dor-MAudio

AND NATIVE INSTRUMENTS THEMSELVES:
http://www.native-instruments.com/knowl ... nder+Linux

Knowledge Base
Native Instruments hardware under Linux
All NI audio interfaces can also be used under Linux operating systems. This includes AUDIO 4 DJ/AUDIO 8 DJ, AUDIO KONTROL 1, GUITAR RIG MOBILE I/O, the KORE 1 controller, the second and third generations of the RIG KONTROL, and the SESSION I/O interface. Both the audio and MIDI functions of these devices are supported.

The necessary ALSA drivers are included in kernel versions 2.6.22 and above. Native Instruments does not provide any kind of support or guarantee for these drivers or for using its products under Linux.

STRAIGHT FROM THE HORSES MOUTH. Go ahead with your snappy reply, I'm waiting...

I have personally tried a half dozen soundcards under Linux, and they all worked great... You don't even need to install drivers, as they're already in the Linux kernel (Firewire devices are the only ones that require a separate driver, but they mostly "just work" too).

This is where you can admit that you were wrong and apologize, or continue making a bigger arse of yourself by repeating the same old obsolete knowledge from 15 years ago.

No Smart TVs?

[Crackbaby]

very snappy!

[robogone]

i was VERY excited about the USB-to-feline interface you were describing... uh oh, i mean, um...

Pussy plugins?

[jeffh]

No Smart TVs?

If smart TVs use the same Linux kernel with the same ALSA drivers, then I'm going to let you do the Google-ing on whether or not smart TVs are supported by ALSA.

PS: Just in case you thought chip architecture makes a difference, it doesn't... I have done a writeup of myself running Ubuntu on ARM on me website, and the Alesis IO2 Express interface I used worked just fine without having to install anything... So the only reasons that a USB soundcard wouldn't work with a smart TV are:

1. It has no USB ports, or
2. The manufacturer provided no way to switch between the built-in soundcard

Linux audio drivers: 1
Windows audio drivers: 0

[debra1rlo]

i was VERY excited about the USB-to-feline interface you were describing... uh oh, i mean, um...

Pussy plugins?

all i can say is the workflow gives the phrase "singing from the diaphragm" a whole new meaning

[hibidy]

See this is what happens when there is a "real" bitwig thread.

[dsan@mail.com]

See this is what happens when there is a "real" bitwig thread.

EDIT: Sorry, was laughing so hard I forgot to include some text.

That USB to feline connector is barbed and very difficult to extract once mating has completed.


Happy musiking!
dsan

[LawrenceF]

See this is what happens when there is a "real" bitwig thread.

A cat fight?

[hibidy]

See this is what happens when there is a "real" bitwig thread.

A cat fight?

haha!

Oh, and it's one "under the table"