I have a small problem with my Vero 4K+, I can’t set the volume of my soundbar with Vero Remote (same for TV remote by the way).
So if I increase or decrease the volume for music tracks or movies, a weird distortion happens, sounding like too much loudness or not enough loudness. You can still listen but It happens everytime, and you always hear it.
The problem doesnt occur with spdif, but only with HDMI.
I can use the dedicated samsung remote, it s working fine with it, but since I do everything with Vero remote, I’m searching for a solution to make that work with it.
Equipement: sony TV kd43xf2096, samsung hw-N550 3.1ch SoundBar, vero 4k+. Linked with HDMI Arc.
I think the problem could be, after reading other posts, the hdmi cables but before buying, can someone please confirm?
I tried multiple various settings in system audio settings, nothing is making any change.
CEC is working fine for standby and lauching both TV and SoundBar.
Rather than a screenshot, can you record what it sounds like? Do you get distortion only when changing volume? I’m puzzled by what you get when you decrease the volume.
Is the vero connected to the soundbar (preferred) or the TV?
I’m guessing this has to do with a function on the soundbar being activated through CEC which is not a normal volume control. It happens with both Vero remote and TV remote - suggests it’s an issue in the soundbar. It doesn’t happen with S/PDIF - expected since S/PDIF doesn’t support CEC and the Vero remote will be changing the volume in Kodi (you should see a symbol top centre of the screen showing the volume), not in the soundbar.
Have a close look at the soundbar manual. Does the soundbar have an on-screen display that might reveal something?
Thanks for the help again, but changing PCM to HDMI did not fix it unfortunately.
For samsung soundbar, CEC is called “Anynet+”. I have to activate it for volume control with Vero and TV remote (and for cec shutdown and launch). I have not seen anything relevant in the sounbar manual.
Sending the log file hoping it makes sense. First I used vero remote, then “CecLogMessage” refers to samsung remote which i used for volume.
DRC on/off and SURROUND on/off gives no result.
Re-linked the subwoofer, changed hdmi arc connecting vero to tv before soundbar, same problem.
I’ll check a different pair of hdmi cables.
Tried new hdmi cables. Sound gets messed up when controlling volume with Vero remote.
Same thing with using TV playing music to soundbar + controlling volume with TV remote.
Must be the samsung soundbar which is not fully compatible with CEC.
Will ask samsung support.
I found a compromise which is turning off CEC.
I control volume with kodi remote on the kodi audio output, and I shut down soundbar+tv with an extension cord.
I can get rid of CEC problems, samsung support cannot fix it and other cables neither.
Thanks for the help anyway!
I found that when I use the terminal and send volup/voldown libcec commands, it’s working good, the audio stay clean. Is that a good track?
Hope I’d know how make it useful inside osmc, also for audio passthrough option which get worse without cec in my system. Tried some research at libcec github but I’m quickly stopped by my lack of coding knowledge.
Maybe something noteworthy, if I shutdown and unplug tv the osmc remote doesnt control volume anymore. I think I’ve tried all tv settings for audio.
Libcec scan:
osmc@osmc-Gilbert:~$ echo scan | cec-client -d 1
log level set to 1
No device type given. Using ‘recording device’
CEC Parser created - libCEC version 4.0.4
no serial port given. trying autodetect:
path: /dev/aocec
com port: AOCEC
opening a connection to the CEC adapter…
waiting for input
requesting CEC bus information …
CEC bus information
device #0: TV
address: 0.0.0.0
active source: no
vendor: Sony
osd string: TV
CEC version: 1.4
power status: on
language: fre
device #1: Recorder 1
address: 3.1.0.0
active source: no
vendor: Pulse Eight
osd string: CECTester
CEC version: 1.4
power status: on
language: eng
device #5: Audio
address: 3.0.0.0
active source: no
vendor: Unknown
osd string: Soundbar
CEC version: 1.4
power status: unknown
language: ???
currently active source: unknown (-1)
hey, I got back on my CEC quest and tried everything again: no way to get rid of that weird CEC volume issue
But! ssh commands echo volup/voldown | cec-client -s -d 1 are still working without the weird issue I thought maybe I could map my remote with special cec volume actions?
You can’t directly run that from a keymap but you can make an external python script and map to that. There is two downsides to this however. It is slow, and from what I remember when I played with this you couldn’t hold down the key to repeat. The mapping currently with an OSMC remote would look something like this…
Thanks for the quick tip!
if its going to be slow as the ssh delay yep, not very practical for volume adjusting.
Is it possible that it would be a CEC configuration issue? Having tried all my TV/AVR settings I went through different forums, and finaly came to libcec github, I don’t know if can post an “issue” there, this place looks oriented to more advanced users than I am. Anyway, I saw different commits related to volume control with libcec 5.0 label but I don’t know at all if its related to my issue… Is there a way to try libcec5.0 ?
Here are the logs if it can help
cec-client -l -d 1
osmc@osmc-Danforth:~$ cec-client -l -d 1
libCEC version: 4.0.4, compiled on Sun Jul 7 00:43:28 UTC 2019 by root@compiler2 on Linux 4.9.0-3-amd64 (armv7l), features: P8_USB, DRM, P8_detect, AOCEC
Found devices: 1
osmc@osmc-Danforth:~$ echo scan | cec-client AOCEC -s -d 1
opening a connection to the CEC adapter…
requesting CEC bus information …
CEC bus information
device #0: TV
address: 0.0.0.0
active source: no
vendor: Sony
osd string: TV
CEC version: 1.4
power status: on
language: ???
device #1: Recorder 1
address: 3.1.0.0
active source: yes
vendor: Pulse Eight
osd string: CECTester
CEC version: 1.4
power status: on
language: eng
device #5: Audio
address: 3.0.0.0
active source: no
vendor: Samsung
osd string: Soundbar
CEC version: 1.4
power status: unknown
language: ???
I think Kodi normally just needs to see an amplifier on the CEC bus (which it does, it device type 5 in what you just posted) to switch from adjusting the signal level to sending CEC commands instead. With CEC enabled on the Vero, on the soundbar both anynet enabled, as well as the woofer button setting set to ALL‑TV REMOTE, and the TV set to whatever to have CEC and ARC enabled (no clue as the model number you provided does not produce any web search results) then I would expect it to just work. You would have to reboot after using any cec-client command though as that kills CEC from working in Kodi.
Maybe one day someone will add the ability to force the CEC volume control switch to work around issues such as this, but currently I know of no way to do this.
Actually CEC adapter volume control of soundbar is effective in kodi but the audio gets messy. Adjusting the volume mess with bass, maybe the subwoofer is forget in the process I don’t know, the weird thing is that it’s not the case with cec-client ssh commands.
Anyway it’s surely not an osmc bug and I can get around it. I appreciate your help, OSMC is awesome
I don’t understand how there would be a difference between Kodi and cec-client sending the CEC volume commands. Are you running the most recent firmware on your soundbar? When you switched over to Kodi using CEC vol control did you make sure that the volume in Kodi was set to full volume before you made that switch? This messed up sound issue is it with stereo sound as well or just surround sound sources with the issue?
Since this is an issue metnioned in another thread, I would like to see a debug log so we can check all your audio settings; till today there is no helpful debug information provided.
The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
