Posts by Da Flex

Quote from kjsanders86

Have anyone seen this before?

No. If you did a clean shutdown after your last session, then maybe your 24 hour test created an overload of temporary data.

Read here about Allo Boss DAC on RPi.

Quote from badluck

...although the usb controller does support USB3...

Unfortunately you need the xhci_hcd driver to make the controller work (source).

Quote from badluck

All disks use usb-storage driver, but the root_hub uses xhci which might be the problem?

If the root hub is USB3 then you can't do anything. If it's USB2 then blacklist the xhci_hcd driver.

Login by SSH, and open the settings file by nano /storage/.kodi/userdata/guisettings.xml.

My "audiooutput" part looks like this:

<setting id="audiooutput.ac3passthrough" default="true">true</setting>
<setting id="audiooutput.ac3transcode" default="true">false</setting>
<setting id="audiooutput.atempothreshold" default="true">2</setting>
<setting id="audiooutput.audiodevice">PI:Both</setting>
<setting id="audiooutput.channels" default="true">1</setting>
<setting id="audiooutput.config" default="true">2</setting>
<setting id="audiooutput.dtshdpassthrough" default="true">false</setting>
<setting id="audiooutput.dtspassthrough" default="true">false</setting>
<setting id="audiooutput.eac3passthrough" default="true">false</setting>
<setting id="audiooutput.guisoundmode" default="true">1</setting>
<setting id="audiooutput.maintainoriginalvolume" default="true">true</setting>
<setting id="audiooutput.passthrough" default="true">false</setting>
<setting id="audiooutput.passthroughdevice">PI:HDMI</setting>
<setting id="audiooutput.plladjust" default="true">0</setting>
<setting id="audiooutput.processquality" default="true">30</setting>
<setting id="audiooutput.samplerate" default="true">48000</setting>
<setting id="audiooutput.stereoupmix" default="true">false</setting>
<setting id="audiooutput.streamnoise" default="true">true</setting>
<setting id="audiooutput.streamsilence" default="true">1</setting>
<setting id="audiooutput.truehdpassthrough" default="true">false</setting>
<setting id="audiooutput.volumesteps" default="true">20</setting>

Then go to the bottom of the file content and check that audio is not muted and has a noticeable volume:

<audio>
    <mute>false</mute>
    <fvolumelevel>0.900000</fvolumelevel>
</audio>

Does it affect all audio formats, even mp3?

Do you have all other audio settings on default values (especially amount of channels should be 2)?

Set audio output to HDMI and analogue. Then plugin headphones on your RPi to check whether you hear audio.

A second test is to disable audio pass-through at Settings -> System -> Audio.

Maybe new drivers increase efficiency, but don't solve the real problem. Your kodi.old.log has a couple of errors, which maybe affects playback indirectly.

You have a lot of add-ons, so I would try a fresh LE installation. Don't install add-ons, and disable audio pass-through at System -> Audio settings. If this vanilla installation runs without playback errors, add add-ons step-by-step to identify trouble makers.

I noticed that HiassofT was reading here, so I'm optimistic that things start rolling.

At similar issues people often blacklist a Linux driver, but that's just another dirty fix.

Quote from Zordrack

Finally to make this stick i'll finish off with adding it to autostart.sh:
echo "xrandr --output eDP1 --off && xrandr --output HDMI1 --mode 1920x1080 --rate 60.00" >> /storage/.config/autostart.sh

Selecting this HDMI mode at the LE video settings doesn't work?

This part of the log looks weird to me:

2020-01-02 19:05:45.206 T:140066466821888  NOTICE: Enumerated PULSE devices:
2020-01-02 19:05:45.206 T:140066466821888  NOTICE:     Device 1
2020-01-02 19:05:45.206 T:140066466821888  NOTICE:         m_deviceName      : Default
2020-01-02 19:05:45.206 T:140066466821888  NOTICE:         m_displayName     : Default
2020-01-02 19:05:45.206 T:140066466821888  NOTICE:         m_displayNameExtra: Bluetooth Audio (PULSEAUDIO)
2020-01-02 19:05:45.206 T:140066466821888  NOTICE:         m_deviceType      : AE_DEVTYPE_PCM
2020-01-02 19:05:45.206 T:140066466821888  NOTICE:         m_channels        : FL, FR
2020-01-02 19:05:45.206 T:140066466821888  NOTICE:         m_sampleRates     : 5512,8000,11025,16000,22050,32000,44100,48000,64000,88200,96000,176400,192000,384000
2020-01-02 19:05:45.206 T:140066466821888  NOTICE:         m_dataFormats     : AE_FMT_U8,AE_FMT_S16NE,AE_FMT_S24NE3,AE_FMT_S24NE4,AE_FMT_S32NE,AE_FMT_FLOAT
2020-01-02 19:05:45.206 T:140066466821888  NOTICE:         m_streamTypes     : No passthrough capabilities
2020-01-02 19:05:45.219 T:140066458429184   ERROR: CActiveAESink::OpenSink - no sink was returned
2020-01-02 19:05:45.219 T:140066466821888   ERROR: ActiveAE::InitSink - returned error

Especially m_displayNameExtra: Bluetooth Audio (PULSEAUDIO) doesn't sounds right.

Disable Bluetooth at your UEFI settings, and try to boot LE again.

Quote from HanSoloDK

Would it be "a good idea" to change my home system away from Amlogic in regards to more easy support from you in the future?

My plan for 2020 was to change it to a system that can handle 4K playback since I just got a 4K TV.

An Intel NUC or an RPi 4B has much better Linux support, compared to Amlogic. They can both handle 4K.

Both have good support, but the RPi 4B has more sites of work until software will be optimized.

Quote from donbrew

On reboot it finds the tar in the update folder and updates and crashes.

...

I'm getting a supply of SD cards tomorrow.

Good. Maybe your current microSD has errors, and the OS can't expand. I would do full check on it. If you use Windows, you can use this tool.

Quote from donbrew

Is 9.1.002 supposed to update itself to 9.2.0?

No, you have to select the 9.2 branch at the LE settings menu.

If you use Etcher to write 9.1.002 to microSD, what happens when you boot the RPi 4B with it?

Read the thread I mentioned above. It contains several tricks you can try to finish booting.

The bottom line is my suggestion to install LE 9.1.002 first, because I think the settings wizard has trouble to start in LE 9.2.

Please try this, I still don't have feedback from the other user. If you're successful, you can update to LE 9.2 by GUI.

We had a nearly identical question a couple of days ago.

We have some threads like this, but I can't verify the fixes, because I'm an RPi 3B+ guy.

Someone said that audio config affects the issue. Read here.

Go into deeper research by using the search function of the forum, doc.