It’s weird because the missing symbol shouldn’t be needed at all for video playback. I’ll have a look, maybe I can find the reason by just reading the code 
.
I don’t think I can share DVBViewer or OSMC with WAN. My network is complex and security wise completely blocked from outside to in. But willing to help you with testing etc. to get this solved.
We could use an SSH tunnel so you don’t have to port forward.
Let’s wait, that symbol shouldn’t be used at all. So there is an issue somewhere in libamcodec.
1 Like
Sorry I have no clue how to make SSH work on my side unfortunately.
Can you run an SSH command from the DVBViewer instance or another machine that has access to the DVBViewer instance? That would be all that would be needed; but let’s wait for @tanio99.
I have SSH access to OSMC.
DVBViewer is running on a Windows server to which I have full access.
Should be possible to arrange something then if needed.
I think I found and fixed that issue. It should be part of the next update.
I will push a fix to staging for testing later today
Sounds great, thank you. Will install as soons as available and will keep you posted about the outcome. Would be great if this issue is solved 
Hopefully the issue is now addressed
I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:
- Login via the command line
- Run the following command to add the staging repository:
echo 'deb http://apt.osmc.tv bullseye-devel main' | sudo tee /etc/apt/sources.list.d/osmc-devel.list - Run the following commands to update:
sudo apt-get update && sudo apt-get dist-upgrade && reboot - Your system should have have received the update.
Please see if the issue is resolved.
I also recommend you remove /etc/apt/sources.list.d/osmc-devel.list after updating.
This will deactivate the staging repository. You can do so with the following command:
sudo rm /etc/apt/sources.list.d/osmc-devel.list.
Please note that we will automatically disable this update channel after 14 days on your device in case you forget to do so to ensure that your system reverts to the stable update channel.
I have installed the update and removed the requested sources.list part.
Update went fine. WIll keep you posted.
Great, let me know how it goes.
Unfortunately still sad faces once in a while. Haven’t been able to make a new log file yet. Will share this as soon as possible.
Just to jump in here as a fellow DVBViewer user, I had a couple of sad faces when the update first loaded but then it settled down and I haven’t had any since. But I will look out for it.
I did have an issue at the system level with time zones, which obviously affected LiveTv, but I just found it in the system settings and fixed it. My Australia Melbourne changed to Lord Howe Island
Will need to see a log to see if it’s the same problem and verify you have indeed received the update
Sam
Yes of course, first thing this morning :-). Didn’t had time yesterday evening.
It took about 4 of 5 start moments of recordings before I got the sad face.
I think it is still the same symbol lookup error.
Did I install the update well? I got all the update messages from SSH, so I think I did?
You’re still running the old build
ii vero5-mediacenter-osmc 21.1.0-5 armhf Media Center package for OSMC
You should get 21.1.0-6. Can you try to update again using the steps @sam_nazarko mentioned above?
That’s strange. I did all steps, but will do it again. Thank you for checking.
Did the update again, log file says I have:
vero5-mediacenter-osmc 21.1.0-6
So will do some more testing. Thank you!