I’ve also been knocking holes in my 12 string and added a humbucker coil, so I now get the choice, Humbucker or piezo + pre-amp, and with a suitable stereo lead these can go straight into the synth. All very compact.
So I have two quite different inputs rather than provide an amplifier could a stereo input ‘pan’ solve this rather nicely in one control main control and a separate overall gain ?
Channel one (L) (Peizo + preamp from guitar) High level
Channel two ® passive humbucker Low(ish) level . . .
It’s a WAV cos it’s more measurement than pleasure …
Here’s the ogg . . . for comparison. . .
Here’s the mp3 for comparison again, . . .
Goodness I make you suffer ! but this looks interesting…
For those, that words like git have little meaning, Wikipedia says Git is a distributed version-control system for tracking changes in source code during software development. . .
It accesses where teams & oneself keep stuff when developing code. It’s also where one can easily grab the project at various points in it’s history, which is very helpful. I’ve known people who keep audio collections under git. It does its job very well but it has a certain surrounding mythology for the infrequent user.
One needs a suite of programmes loaded on your machine to access the git repository and these are run by either the command line using the word git . . with a command and parameters, or a GUI, perhaps for instance, built into an Interactive Development Environment (An iDE).
so
the line described in the page pointed to by the weblink in the definition of the lv2 plugin . . . .
so git clone git://github.com/x42/xfade.lv2.git
will copy the recognised structure defined at this site . . .
which is:- I’ve opened the clone dialog to show how this can be picked up from the site itiself… at github which surprise, surprise is a place for git repositories to hang out.
But this programme needs to be connected or linked to the machine it will run on and this is where make comes in. it makes sure that the details are all up to date and choose the versions of code libraries on the machine that will be used.
we can see some response and notice it’s now built a directory called build
which contains two text files and an .so file
the so file An .so file is a compiled library file. It stands for “Shared Object” and is analogous to a Windows DLL.
So we have descriptions of the lv2 setup and a programming plug & socket ( .so file) to allow the programme to connect to the bits and pieces it needs. . .
sudo make install PREFIX=/usr
well sudo is the magic invocation that allows you to take on poweruser status to modify files in the structure that would normally be blocked from you. Now in the zynthian we run with root power all the time, so we can do this anyway but the sudo does no harm . . .
so we are running the next command as superuser, and the next command is
sudo make install PREFIX=/usr
so we are running make again but with the install command which is actually defined in the Makefile, and a specific setting of a parameter called prefix with a specific value
. . .
and just checking we can see the file that the make install has created.
notice these are owned by root, which is why the sudo would have been needed.
sadly the encoder for A A+B B only selects those values not a gradual fade… . . .
But this is probably because I now realise it’s a stereo input device so has 4 inputs that ar being mapped to 2 so that might well explain it…
. . .
( I’m not sure how but hey …!)
