Re: [LAU] Bitwig: what we can learn from it

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-user@...>
Date: Wednesday, April 2, 2014 - 3:50 pm

On 04/01/2014 03:40 PM, James Harkins wrote:

[..]

apples vs oranges. If you're a casual blues guitarist, linux audio is
about as useful to you as a Bassoon :)

[.. description of an algorithmic composition ..]

Actually, I do mind.

This is a very nice real-world example. You have an idea, managed to
describe it using abstract concepts which in turn can be formulated in a
language which - in this case - is interpreted by a computer. There's
nothing *geeky* about it at all.

> if I were writing dots on paper and debating whether to use

exactly.

In some cases can do away with pen and papers, too. Just shout the idea
to the musicians next to you during a jam-session in whatever language
they understand.

I still find it hard to accept that creative people prefer a
point-and-drool user interface to express and realize their ideas.

> I don't know Bitwig, so I have no basis to evaluate Robin's assertion that

I chose the word 'toy' carefully. You can have fun with toys, play with
toys and use them creatively. However, toys are usually limiting,
limited and often unreliable.

Don't get me wrong, I have the utmost respect for the Bitwig team to
pull this off this project.

Anyway back on subject.

I think what we learned in this thread is that the expectations of many
[potential] linux audio users does not match the idea that many
developers have in mind.

Now, that's a bold provocative statement, but there you go.

2c,
robin
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAU] Bitwig: what we can learn from it, James Harkins, (Tue Apr 1, 1:40 pm)
Re: [LAU] Bitwig: what we can learn from it, Robin Gareus, (Wed Apr 2, 3:50 pm)
Re: [LAU] Bitwig: what we can learn from it, Len Ovens, (Thu Apr 3, 1:02 am)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Wed Apr 2, 5:11 pm)
Re: [LAU] Bitwig: what we can learn from it, James Morris, (Wed Apr 2, 3:57 pm)
Re: [LAU] Bitwig: what we can learn from it, Robin Gareus, (Wed Apr 2, 4:02 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Wed Apr 2, 5:59 pm)
Re: [LAU] Bitwig: what we can learn from it, rosea grammostola, (Wed Apr 2, 4:36 pm)