Thanks for testing. Next you can try the alsa mixer this way:
Code
amixer -c 0 set Digital 80%Posts by Da Flex
-
-
Is there a way to install LibreElec in headless mode?
No, but you can turn off the display by using the tvservice command on autostart.sh.
Currently, my strategy is to install Raspbian Buster Lite and install Kodi with "sudo apt-get install kodi."
Most headless LE users only do it, because they need special add-on's, which are not available for other RPi OS'es. If that's not the case for you, go the Raspbian way.
Don't forget that you will run into display package dependencies when you install Kodi on a headless Raspbian. So using a standard Raspbian and switching off the display by tvservice could be the best strategy.
-
Please check whether editing the volume setting of guisettings.xml (bottom of the file) makes a difference for your apps.
-
To my knowledge there is only one sound server available for RPi. The HiFiBerry driver feeds that sound server, and players use both components. It's on you to try different players from add-on repositories. If the sound server is the weak part, then they will have no effect.
There is an exotic Korean LE mod, optimized for audio. Currently I only see RPi 2/3 builds. Maybe they start RPi 4 support, soon.
-
My Ubuntu PC is only an example for issues like yours. I had exactly the same double-start issue on local audio files. It was a local buffering issue, not a stream buffering issue. I assume you have the same issue when playing an audio file locally.
-
Find add-on's for audio playback.
I had buffering issues on my Ubuntu PC. Using a different sound server for the same player fixed the issue.
-
I think it's a buffering issue, related to the audio driver. Maybe the buffering process interrupts the playback for a short time. Because you don't have the option to select a different audio driver, my advice is to contact the HiFiBerry support. They are responsible for providing a proper device driver.
-
You could buy this adapter to use your analogue headphones at the same time as your S/PDIF headphones.
Using the bad RPi DAC for analogue output just doesn't make sense.
-
Not at the moment but how is it going to be related to spdif? I do not need HDMI audio at all.
Sorry, I forgot that HiFiBerry has to be selected as LE's audio output device. Selecting PI: HDMI and Analogue or PI: Analogue will deactivate this DAC, but should activate the analogue jack of the RPi.
I assume you have been followed the official instructions. If this doesn't solve the problem, ask the HiFiBerry support. They are pretty firm.
If it turns out that it's impossible to have both outputs at the same time, then maybe an RC button switch is an option for you.
-
Do you have "HDMI and Analogue" activated at the LE audio settings?
-
-
Not a good idea to build an audiophile LE version for RPi's. Not just what chewitt mentioned is a problem.
Two more problems:
People often want HD audio on RPi's HDMI, but it looks like this hardware (or software implementation of audio pass-through) is too slow for native (non-PCM pass-through) HD audio (and other high speed) formats.
When trying to do the same thing with an USB DAC, then you need a real-time Linux kernel to deliver high speed audio data in time to USB. That's probably what the LE mod guys did, but it slows other tasks down.
-
Playing the same file several times in a row will get a different front speaker to get the center channel...
That's kind of a proof of my theory for HD audio and other formats with high data rate.
HD audio can work on LE (with better Intel NUC hardware), as proofed here: click.
-
Please attach your dongle and provide a link to a log file.
-
Missing HD audio is a known issue on RPi's. Having partially audio is a sign of an overload at the RPi data bus to me. So this issue might never be fixed due to hardware limitations.
Some TV's have S/PDIF or TOSLINK audio output. If you go RPi -> TV -> Amp, then you could have 4K, if supported by your TV.
-
Hi all, would this work on the ASUS Tinkerboard too?
Take care about the GPIO compatibility and give it a shot. Chances are good.
-
I updated the boot firmware and not the LE!
That's what I mean, too. LE updates include boot firmware updates, whenever necessary.
You can verify script execution by creating a file. Do an internet research to learn how to do so.
I can only continue to help you, if you answer my questions. Investing energy to get the latest boot firmware, but ignoring LE updates is a mismatch to me. LE updates are more important to get stability and best performance.
If you did a typo like at chmod +x, you should inform us about it's correction. Other users will benefit while reading the thread.
-
You did a typo, it's chmod +x, not chmod + x.
LE does the firmware update. If you do it yourself, then stuff like a change of the config.txt syntax can happen. So I don't suggest this.
Is there any cause why you don't update to the latest LE version?
