19-02-21, 21:49
Hi,
Windows only recognizes only the first partition on SD devices, so your action will not give the result you want.
And worse, as the the sample partition is loaded unconditionally at boot as ext4 while its FAT, startup will give alarming error messages and refuse to mount the /samples. In short: don't do that.
If you want convenient access to samples from windows, you have to use a thumb-drive and if you want to use the internal space, you'll either have to use a non-windows machine to mount the SD or sftp to samplerbox.
As this is not a forum for complaining about windows, we have to silently accept that as a fact
Regarding the test and missing sound:
I assume that you ran the speaker test after the crippled startup as described above.
If you didn't stop samplerbox, this holds you device busy. So this being busy is OK.
If you used above startup without the samples, samplerbox cannot play anything. Nothing wrong here.
What you absolutely should do when debugging samplerbox: stop the automatic started box and restart manually so you can see & report console messages. Having no sound can have so much causes - the only thing I can reply to such a statement is: "I have sound, so something is possibly wrong at your side"; very unsatisfying.
....and in the log you would have seen that no sample could be loaded or other lead...
Windows only recognizes only the first partition on SD devices, so your action will not give the result you want.
And worse, as the the sample partition is loaded unconditionally at boot as ext4 while its FAT, startup will give alarming error messages and refuse to mount the /samples. In short: don't do that.
If you want convenient access to samples from windows, you have to use a thumb-drive and if you want to use the internal space, you'll either have to use a non-windows machine to mount the SD or sftp to samplerbox.
As this is not a forum for complaining about windows, we have to silently accept that as a fact
Regarding the test and missing sound:
I assume that you ran the speaker test after the crippled startup as described above.
If you didn't stop samplerbox, this holds you device busy. So this being busy is OK.
If you used above startup without the samples, samplerbox cannot play anything. Nothing wrong here.
What you absolutely should do when debugging samplerbox: stop the automatic started box and restart manually so you can see & report console messages. Having no sound can have so much causes - the only thing I can reply to such a statement is: "I have sound, so something is possibly wrong at your side"; very unsatisfying.
....and in the log you would have seen that no sample could be loaded or other lead...