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 - 5:11 pm

Am 02.04.2014 17:50, schrieb Robin Gareus:

Bitwig is not that limited. In fact it has more opportunities under the
hood than most musicians will even search for. Of course it can happen,
that a musician does not find one or more opportunities in it, that
he/she would like to have. I do not find a opportunity to edit and
arrange samples as flexible and convenient as I find it in Ardour but I
see opportunities for working with loops and automatisation that surpass
Ardour. Yet I do not need those as much as the former named editing
features, so I see, that Bitwig can do a lot but still choose Ardour for
it suits *me* better(plus: I am a zealot, I use free software
excluselively...).
Others will find the MIDI/Automatisation features more attractive.

In any case: Music should not follow tools, to limit possibilities can
be a sane choice but to make music in a certain way, because a tool
favours that way, is questionable at best.

If a musician with a strong vision uses Bitwig (or Ardour or CSound),
he/she will find the ways in the software, that support his/her vision.

And what LA can learn from Bitwig is IMHO: make a concept, implement it
to the full, make it stable, reliable and give it a understandable
interface. As easy as possible, but not easier....

>

This may or may not be true. It at all, then the free audio scene who
writes software for Linux has a tendency towards some more individuality
than usual. But if the individual pattern between the dev and the
musician match(for me this would be Ardour, Guitarix, AMS, Seq24 and
some others), the musician gets exactly what he/she wants, even more
perfectly than any marketing-crew could find out for Steinberg...

>

_______________________________________________
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)