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

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-user@...>
Date: Sunday, March 30, 2014 - 7:10 pm

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--INpIr4LwQoc31AiJslOE4bTL0ujud2NVM
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 03/30/2014 04:05 PM, Ralf Mardorf wrote:

> as setting up a Linux DAW

It does. It takes several skills:
- being able to hear subtle differences between different pickups
(unless you replace the pickup with an exact copy)
- being able to choose a pickup that matches your guitar (unless you
replace the pickup with an exact copy)
- knowing how to restring your guitar
- knowing how to solder
- basic knowledge of electronics, unless you want to go for that Peter
Green sound
- knowing how to mount a PU with regard to the distance to the strings

And then we're not talking about actually playing the guitar.

Bye,

Jeremy

--INpIr4LwQoc31AiJslOE4bTL0ujud2NVM
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJTOGwFAAoJEF63J34m6LiUCHkP/RpgE5fjRHRG7QEoeP4BacgQ
+x4xAvAHGpN5CQWkxKzuZVUdZjdOXz2PLs8RBNsel9zwUuEfSr+VR9eoJMSZKtOZ
pnhvGHuWCyVmJdtrm7zpDXbFqree0G9cx0V4Or9L/OMMHSdKYwVYeW2eiFIXnB24
V9pqIK2KsRFW0urdBrtqI5ZOkGl4Ic0AH5EepGwSG4ZroCBnovszwvPdgyHnaqrA
dHQZ0mbYsd/IrOsFzaWGZbQJijMODWgyuBBjNegMql03GOK2FNdpxMKJP7p1oZM3
d4BEQPI+ka1K/36b3GbHHvoMB4qK3Ekg9ICpo+B03ECp55gnsEsyaYl/hDzGIbur
fFc4SBG+dez7rOCkhvzkIhHr/kVk/yRu3Uk2hpUy7s+ck3wbMoZBE0e6mbt+Bm+v
JgJq9/5d8/qtiCM/Xc9kGyEUjasDapSmseCVoL5q/KZnUYURWXSHEDbLMigTI2ty
lNFXSY08ioZVPUe/F960QwbUHMUO6j/l9QvW3NAqrlDaKg2vSk2t+yC8w2+VEIP8
REBu11D+UNjEGrVvLGrWps9r7+NMKETBw4limJh1NeXeRM20CVmfdV371dr9S/M9
8PrjE7skdVvhoDoHi9soTlw3vZrWg+oPVExVNK0UlsTQx2nRLZ20YRwiFKPtfGsy
gU5HWPQi4/wbIwc6UVGK
=2fjH
-----END PGP SIGNATURE-----

--INpIr4LwQoc31AiJslOE4bTL0ujud2NVM--

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)