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

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-user@...>
Date: Friday, April 4, 2014 - 2:13 am

On 04/04/14 02:56, Tim Blechmann wrote:

> well, it is nice being able to talk to a dev, but it does not

Where anyone can publish anything of course the user needs to do a fair bit of
work filtering the worthwhile from the useless. That takes quite a lot of
commitment and time as well as a deeper understanding the field. It is much
easier to let someone else choose for you (perhaps pay them to do it), they'll
give you something ready to use for the situations they are catering for. But
then you are stuck with their notion of what is worthwhile, and whatever other
agenda they have (e.g. extracting ongoing profits from their users). I'll put
the time in to learn and choose myself, but it isn't quick or easy, just the way
I prefer to work, as much because it leads to that deeper understanding of the
field as anything else.

Simon
_______________________________________________
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:
[LAU] Bitwig: what we can learn from it, rosea.grammostola, (Sat Mar 29, 10:32 am)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Sat Mar 29, 3:42 pm)
Re: [LAU] Bitwig: what we can learn from it, Len Ovens, (Sat Mar 29, 4:14 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Sat Mar 29, 4:29 pm)
Re: [LAU] Bitwig: what we can learn from it, rosea.grammostola, (Sat Mar 29, 9:17 pm)
Re: [LAU] Bitwig: what we can learn from it, Simon Wise, (Sun Mar 30, 9:45 am)
Re: [LAU] Bitwig: what we can learn from it, Louigi Verona, (Sun Mar 30, 10:27 am)
Re: [LAU] Bitwig: what we can learn from it, drew Roberts, (Mon Mar 31, 2:02 pm)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Mon Mar 31, 2:23 pm)
Re: [LAU] Bitwig: what we can learn from it, Lorenzo Sutton, (Tue Apr 1, 11:19 am)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Tue Apr 1, 1:57 pm)
Re: [LAU] Bitwig: what we can learn from it, Lorenzo Sutton, (Wed Apr 2, 7:23 am)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Wed Apr 2, 12:01 pm)
Re: [LAU] Bitwig: what we can learn from it, Lorenzo Sutton, (Wed Apr 2, 3:19 pm)
Re: [LAU] Bitwig: what we can learn from it, Will Godfrey, (Mon Mar 31, 6:49 pm)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Mon Mar 31, 7:15 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 1:09 am)
Re: [LAU] Bitwig: what we can learn from it, Gordon JC Pearce, (Mon Mar 31, 9:02 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 1:18 am)
Re: [LAU] Bitwig: what we can learn from it, Set Hallström, (Mon Mar 31, 9:01 pm)
Re: [LAU] Bitwig: what we can learn from it, rosea.grammostola, (Sun Mar 30, 1:11 pm)
Re: [LAU] Bitwig: what we can learn from it, Robin Gareus, (Mon Mar 31, 10:23 am)
Re: [LAU] Bitwig: what we can learn from it, Gordon JC Pearce, (Mon Mar 31, 10:32 am)
Re: [LAU] Bitwig: what we can learn from it, James Morris, (Mon Mar 31, 4:19 pm)
Re: [LAU] Bitwig: what we can learn from it, David Olofson, (Mon Mar 31, 12:44 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Mon Mar 31, 11:26 am)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Tue Apr 1, 8:42 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Tue Apr 1, 9:02 pm)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Tue Apr 1, 9:06 pm)
Re: [LAU] Bitwig: what we can learn from it, Gene Heskett, (Mon Mar 31, 2:36 pm)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Mon Mar 31, 2:02 pm)
Re: [LAU] Bitwig: what we can learn from it, Chris Cannam, (Wed Apr 2, 4:02 pm)
Re: [LAU] Bitwig: what we can learn from it, david, (Thu Apr 3, 4:59 am)
Re: [LAU] Bitwig: what we can learn from it, Robin Gareus, (Mon Mar 31, 2:42 pm)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Mon Mar 31, 2:56 pm)
Re: [LAU] Bitwig: what we can learn from it, Jörn Nettingsmeier, (Mon Mar 31, 3:40 pm)
Re: [LAU] Bitwig: what we can learn from it, rosea grammostola, (Mon Mar 31, 3:59 pm)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Mon Mar 31, 3:51 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Mon Mar 31, 2:14 pm)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Mon Mar 31, 2:32 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Mon Mar 31, 2:51 pm)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Mon Mar 31, 3:07 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Mon Mar 31, 3:23 pm)
Re: [LAU] Bitwig: what we can learn from it, Nils, (Mon Mar 31, 3:16 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Mon Mar 31, 3:36 pm)
Re: [LAU] Bitwig: what we can learn from it, David Olofson, (Mon Mar 31, 1:29 pm)
Re: [LAU] Bitwig: what we can learn from it, Philipp , (Mon Mar 31, 3:55 pm)
Re: [LAU] Bitwig: what we can learn from it, Egor Sanin, (Mon Mar 31, 4:14 pm)
Re: [LAU] Bitwig: what we can learn from it, Edgar Aichinger, (Tue Apr 1, 3:08 pm)
Re: [LAU] Bitwig: what we can learn from it, Jörn Nettingsmeier, (Mon Mar 31, 5:37 pm)
Re: [LAU] Bitwig: what we can learn from it, David Olofson, (Mon Mar 31, 4:09 pm)
Re: [LAU] Bitwig: what we can learn from it, Philipp , (Mon Mar 31, 4:25 pm)
Re: [LAU] Bitwig: what we can learn from it, Gerhard Zintel, (Mon Mar 31, 1:11 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Mon Mar 31, 1:22 pm)
Re: [LAU] Bitwig: what we can learn from it, Len Ovens, (Mon Mar 31, 9:06 pm)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Tue Apr 1, 8:58 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Tue Apr 1, 9:47 pm)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Wed Apr 2, 7:22 am)
Re: [LAU] Bitwig: what we can learn from it, david, (Wed Apr 2, 8:18 am)
Re: [LAU] Bitwig: what we can learn from it, Simon Wise, (Wed Apr 2, 11:20 am)
Re: [LAU] Bitwig: what we can learn from it, david, (Thu Apr 3, 5:26 am)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sat Apr 5, 5:30 pm)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Wed Apr 2, 9:23 am)
Re: [LAU] Bitwig: what we can learn from it, david, (Thu Apr 3, 5:35 am)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Wed Apr 2, 8:33 am)
Re: [LAU] Bitwig: what we can learn from it, David Olofson, (Wed Apr 2, 8:50 am)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Wed Apr 2, 7:33 am)
[LAU] [OT] Re: Bitwig: what we can learn from it, Tim Goetze, (Wed Apr 2, 6:48 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Ralf Mardorf, (Wed Apr 2, 7:25 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Fons Adriaensen, (Wed Apr 2, 8:42 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Ralf Mardorf, (Wed Apr 2, 9:13 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Simon Wise, (Wed Apr 2, 11:13 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Fons Adriaensen, (Wed Apr 2, 9:48 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Ralf Mardorf, (Wed Apr 2, 10:20 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Simon Wise, (Wed Apr 2, 11:14 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Ralf Mardorf, (Wed Apr 2, 11:29 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Ralf Mardorf, (Wed Apr 2, 10:55 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Ralf Mardorf, (Wed Apr 2, 10:05 am)
Re: [LAU] [OT] Re: Bitwig: what we can learn from it, Ralf Mardorf, (Wed Apr 2, 9:39 am)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 9:57 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Tue Apr 1, 10:08 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 10:18 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Tue Apr 1, 10:37 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 10:51 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 10:06 pm)
Re: [LAU] Bitwig: what we can learn from it, Louigi Verona, (Mon Mar 31, 9:09 pm)
Re: [LAU] Bitwig: what we can learn from it, Nils, (Mon Mar 31, 9:21 pm)
Re: [LAU] Bitwig: what we can learn from it, Dave Phillips, (Mon Mar 31, 11:55 am)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Mon Mar 31, 1:35 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Mon Mar 31, 1:42 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Mon Mar 31, 12:54 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Mon Mar 31, 12:21 pm)
Re: [LAU] Bitwig: what we can learn from it, Esteban Viveros, (Mon Mar 31, 1:34 pm)
Re: [LAU] Bitwig: what we can learn from it, Chris Bannister, (Mon Mar 31, 1:22 pm)
Re: [LAU] Bitwig: what we can learn from it, Simon Wise, (Tue Apr 1, 2:19 am)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 2:42 am)
Re: [LAU] Bitwig: what we can learn from it, Simon Wise, (Tue Apr 1, 2:49 am)
[LAU] [off-list] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 2:59 am)
Re: [LAU] [off-list] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 3:04 am)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Mon Mar 31, 1:30 pm)
Re: [LAU] Bitwig: what we can learn from it, Robin Gareus, (Mon Mar 31, 10:42 am)
Re: [LAU] Bitwig: what we can learn from it, Harry van Haaren, (Mon Mar 31, 10:38 am)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Tue Apr 1, 8:29 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 9:01 pm)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Tue Apr 1, 9:25 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Tue Apr 1, 9:34 pm)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Tue Apr 1, 9:44 pm)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Tue Apr 1, 9:09 pm)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Tue Apr 1, 9:49 pm)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Wed Apr 2, 6:59 am)
Re: [LAU] Bitwig: what we can learn from it, rosea.grammostola, (Mon Mar 31, 10:13 am)
Re: [LAU] Bitwig: what we can learn from it, Alexandre Prokoudine, (Mon Mar 31, 10:16 am)
Re: [LAU] Bitwig: what we can learn from it, rosea.grammostola, (Mon Mar 31, 10:20 am)
Re: [LAU] Bitwig: what we can learn from it, rosea.grammostola, (Mon Mar 31, 10:22 am)
Re: [LAU] Bitwig: what we can learn from it, Alex, (Sun Mar 30, 12:21 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sun Mar 30, 12:29 pm)
Re: [LAU] Bitwig: what we can learn from it, Tim Blechmann, (Sun Mar 30, 12:43 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sun Mar 30, 12:53 pm)
Re: [LAU] Bitwig: what we can learn from it, Tim Blechmann, (Thu Apr 3, 3:56 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sat Apr 5, 5:35 pm)
Re: [LAU] Bitwig: what we can learn from it, Chris Bannister, (Sun Apr 6, 9:34 am)
Re: [LAU] Bitwig: what we can learn from it, Simon Wise, (Fri Apr 4, 2:13 am)
Re: [LAU] Bitwig: what we can learn from it, Tim Blechmann, (Fri Apr 4, 8:58 am)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Fri Apr 4, 9:59 am)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sat Apr 5, 5:43 pm)
Re: [LAU] Bitwig: what we can learn from it, Len Ovens, (Sat Apr 5, 6:12 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sat Apr 5, 6:29 pm)
Re: [LAU] Bitwig: what we can learn from it, Len Ovens, (Sat Apr 5, 6:43 pm)
Re: [LAU] Bitwig: what we can learn from it, rosea.grammostola, (Sat Apr 5, 6:50 pm)
Re: [LAU] Bitwig: what we can learn from it, Patrick Shirkey, (Sat Apr 5, 12:49 pm)
Re: [LAU] Bitwig: what we can learn from it, Fons Adriaensen, (Sat Apr 5, 2:18 pm)
Re: [LAU] Bitwig: what we can learn from it, Simon Wise, (Fri Apr 4, 10:35 am)
[LAU] List of good linux plugins (was Bitwig: what we can le..., rosea.grammostola, (Fri Apr 4, 10:31 am)
Re: [LAU] Bitwig: what we can learn from it, Louigi Verona, (Sun Mar 30, 12:33 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sun Mar 30, 12:42 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sun Mar 30, 11:01 am)
Re: [LAU] Bitwig: what we can learn from it, Robin Gareus, (Sun Mar 30, 1:48 pm)
Re: [LAU] Bitwig: what we can learn from it, rosea.grammostola, (Sun Mar 30, 4:42 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sun Mar 30, 2:23 pm)
Re: [LAU] Bitwig: what we can learn from it, Robin Gareus, (Sun Mar 30, 2:44 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sun Mar 30, 3:06 pm)
Re: [LAU] Bitwig: what we can learn from it, Len Ovens, (Sun Mar 30, 4:23 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sun Mar 30, 4:54 pm)
Re: [LAU] Bitwig: what we can learn from it, Joel Roth, (Sun Mar 30, 6:44 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sun Mar 30, 3:11 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sun Mar 30, 2:54 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sun Mar 30, 2:05 pm)
Re: [LAU] Bitwig: what we can learn from it, Jeremy Jongepier, (Sun Mar 30, 7:10 pm)
Re: [LAU] Bitwig: what we can learn from it, Chris Bannister, (Sun Mar 30, 2:50 pm)
Re: [LAU] Bitwig: what we can learn from it, Dave Phillips, (Sat Mar 29, 1:49 pm)
Re: [LAU] Bitwig: what we can learn from it, Patrick Shirkey, (Sat Mar 29, 11:25 am)
Re: [LAU] Bitwig: what we can learn from it, Ivan Tarozzi, (Sat Mar 29, 1:16 pm)
Re: [LAU] Bitwig: what we can learn from it, Patrick Shirkey, (Sat Mar 29, 2:18 pm)
Re: [LAU] Bitwig: what we can learn from it, Hartmut Noack, (Sat Mar 29, 12:57 pm)
Re: [LAU] Bitwig: what we can learn from it, Ralf Mardorf, (Sat Mar 29, 1:20 pm)