Tiny Core Extensions > TCE Bugs

TCE 10.0 32bit, flit.tcz, Lenovo b4030

<< < (4/5) > >>

Rich:
Hi chattrhand
Here's the problem:

--- Quote from: chattrhand on March 04, 2019, 09:25:57 AM ---no sound found
Playback open error: -2 No such file or directory
--- End quote ---
For whatever reason, the sound system isn't ready.


--- Quote ---# /home/tc/.X.d/autostart
sleep 1
[ $(which flit) ] && flit > ~/flit.txt &
sleep 1
speaker-test -c2 -t wav -l1 &
--- End quote ---
Try increasing the first sleep command to see if it's timing related.

Juanito:

--- Quote from: chattrhand on March 04, 2019, 09:25:57 AM ---no sound found
Playback open error: -2 No such file or directory

--- End quote ---

Is it possible that you have more than one sound device, for example hdmi and analogue, and the default could change on reboot?

For me, if hdmi comes up as default, flit will not find any sound device. If analogue comes up as default, things work fine.

One other thing I have noticed is that if the sound volume is adjusted via flit, it is not saved and reverts to the default volume on reboot.

Rich:
Hi Juanito

--- Quote from: Juanito on March 05, 2019, 01:07:23 AM --- ... One other thing I have noticed is that if the sound volume is adjusted via flit, it is not saved and reverts to the default volume on reboot.
--- End quote ---
Wouldn't adding  alsactl store  to  shutdown.sh  fix that?

Rich:
Hi Juanito

--- Quote from: Juanito on March 05, 2019, 01:07:23 AM --- ... One other thing I have noticed is that if the sound volume is adjusted via flit, it is not saved and reverts to the default volume on reboot.
--- End quote ---
I worked out the code for saving and restoring the volume if you are interested. There is one caveat however. I think there's a
truncation error in the volume calculations. Place the mouse cursor over flits speaker symbol and wait for the tool tip to pop up
with the current volume level. Using the mouses scroll wheel, alternate one click up, one click down, one click up, etc. You'll
see the volume level takes larger steps going down than going up. The error gets smaller as the volume level drops. It appears
to be caused by converting 0 to 100 volume levels to the mixers 0 to 31 scale and back again. Set versus read back values
look like this:

--- Code: ---Set   Read
100    100
 90     87
 80     77
 70     67
 60     58
 50     48
 40     38
 30     29
 20     19
 10      9
  0      0
--- End code ---

Juanito:

--- Quote from: Rich on March 05, 2019, 10:54:24 PM ---Using the mouses scroll wheel, alternate one click up, one click down, one click up, etc.

--- End quote ---

I didn't realise you could do that - this thing is smarter than it looks  :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version