15-02-21, 21:26 -
Hi Ryan,
Welcome and thanks for your kind words.
As promised I will try to be of help.
First of all: editing the code itself should almost never be necessary.
Most things should be done via the configuration files. I admit this can look so intimidating that it seems like "changing the code".
But editing should normally be limited to one-time editing of *.txt and *.csv files as indicated in the docs.
I tried seriously to take out the need of editing *.py or *.cpp and such. If however there is good reason for doing so, I appreciate to be informed as this may indicate a missing feature worth adding.
Problem#1
That's right, the missing driver has to be installed in such a way. However as samplerbox is very basic, somewhat more care is needed than with an ordinary linux desktop.
As samplerbox is currently single user=root-only, sudo cannot be used for root privileges as they are default.
This also means caution and making sure to have backups or other means for rollback.
You need to have both boot and root parttions writable (see Commandline access and debugging) and you need to have the box connected (wired/wireless) to a network with an internet connection. Attaching to home network normally does the trick.
I expect that there will be an extra include in /boot/overlays and some changes in /boot/config.txt.
If this works as expected, then in best case scenario samplerbox will recognize the card an pick the right option for routing the sound (high quality cards always have several options).
I expect the the onboard IO (bcm2835) will replaced and not be present anymore.
When starting up by hand, you should see the discovery messages in the console log; points of attention are next messages:
Problem#2
For enlarging, the "Can I use the internal sample space..." FAQ points to the build page to which I have nothing to add here except for "yes, this is DIY".
The FAQ also has guidelines on how to access it
Last remark: allowing links is a bit of an experiment. If it attracks spammers I might turn it of. As for this link, you may have recognized the pin illustrations as I took "connecting peripherals" illustration on the build page from there.
Welcome and thanks for your kind words.
As promised I will try to be of help.
First of all: editing the code itself should almost never be necessary.
Most things should be done via the configuration files. I admit this can look so intimidating that it seems like "changing the code".
But editing should normally be limited to one-time editing of *.txt and *.csv files as indicated in the docs.
I tried seriously to take out the need of editing *.py or *.cpp and such. If however there is good reason for doing so, I appreciate to be informed as this may indicate a missing feature worth adding.
Problem#1
That's right, the missing driver has to be installed in such a way. However as samplerbox is very basic, somewhat more care is needed than with an ordinary linux desktop.
As samplerbox is currently single user=root-only, sudo cannot be used for root privileges as they are default.
This also means caution and making sure to have backups or other means for rollback.
You need to have both boot and root parttions writable (see Commandline access and debugging) and you need to have the box connected (wired/wireless) to a network with an internet connection. Attaching to home network normally does the trick.
I expect that there will be an extra include in /boot/overlays and some changes in /boot/config.txt.
If this works as expected, then in best case scenario samplerbox will recognize the card an pick the right option for routing the sound (high quality cards always have several options).
I expect the the onboard IO (bcm2835) will replaced and not be present anymore.
When starting up by hand, you should see the discovery messages in the console log; points of attention are next messages:
- Available audio devices: and the "sub"lines following
- Opened audio device <details> and the "sub"lines following
- Opened Alsamixer: <details>
Problem#2
For enlarging, the "Can I use the internal sample space..." FAQ points to the build page to which I have nothing to add here except for "yes, this is DIY".
The FAQ also has guidelines on how to access it
Last remark: allowing links is a bit of an experiment. If it attracks spammers I might turn it of. As for this link, you may have recognized the pin illustrations as I took "connecting peripherals" illustration on the build page from there.
This post was last modified: 16-02-21, 22:13 by hansehv.
Edit Reason: fixed links