-
-
Notifications
You must be signed in to change notification settings - Fork 912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Audio transcoding not working #1663
Comments
You can try bisecting the issue, if it worked previously there is some commit that will break it. Once that is identified a solution can be worked on. |
I tried a few versions back to the oldest available stable one (4.3-2098~g44bf691ac) on Cloudsmith but all of them seem to have this bug. Where can I find older releases (ARM 64-bit preferred for testing)? |
Older versions are not available on Cloudsmith, you will have to self-compile older versions. |
Now you are comparing 2 completely different branches. You need to go back on the 4.3 branch to figure out where the issue was introduced there. |
I'll investigate further, but it appears that the transcoding has never worked in the 4.3 branch. |
IIRC it did work a few years ago. But there have been many library updates in the meantime, so it probably broke somewhere along the way. |
Good to know thanks. |
Thats quite old, I'd expect it to work on that old releases. You are compiling with static ffmpeg, right? The dynamic versions that use your system ffmpeg might fail if it is a ffmpeg bug. |
Hello, During compiling I noticed:
I built with: I already had installed libfdk-aac0, libfdk-aac2 and libfdk-aac-dev on my system. Any ideas how to fix? |
I've tried compiling commit versions back to 2017 and I haven't found a version of 4.3 Build:XXX that has a working transcode. If anyone knows a version of 4.3 that does work, I'm happy to trace the commits to identify where it stopped working. Currently I just use 4.2.8-22~g67e75a932 for transcoding needs. Docker builds have the same issue |
Tvheadend Version
v4.3 (development)
Build Number
4.3-2286~gae51d24fe
Platform
Ubuntu 20.04 (Focal)
Architecture
ARMv8 (arm)
Category
Transcoding
Description
Hello,
asked this before without getting a solution: I am currently using HTS Tvheadend 4.3-2286~gae51d24fe on several root servers.
Due to limited mobile data volume I want to transcode video and audio to a lower bitrate.
Video transcoding is working fine but currently I can only use "copy" for the audio streams.
No matter which codec profiles I want to use for the audio transcoding to AAC 56k (or any other) no sound seems to be transcoded or at least output by TVH.
The audio stream in VLC is always empty, using all kinds of different settings. Tried this for different networks and on different servers. Switching back to "copy" the original audio is working. FFProbe and the stream output on VLC show that there is no audio stream sent at all when transcoded.
It affects pretty much all recent versions (stable, development, unstable) of tvheadend.
I know this worked before (years ago though) and I have no clue what causes this behaviour. I have no stream filters applied. All neccessary codecs are installed and working. Manually transcoding the same input streams via the command line produces the desired audio output.
Would be really thankful for any help on this.
Logfile
mpegts: channels - ARTE HD - tuning on IPTV #1
subscription: 0007: "HTTP" subscribing on channel "ARTE HD", weight: 100, adapter: "IPTV #1", network: "xxx", mux: "channels - ARTE HD", provider: "FFmpeg", service: "ARTE HD", profile="mobi", hostname="xxx", username="xxx", client="VLC/3.0.18 LibVLC/3.0.18"
transcode: 0005: 02:H264: ==> Using profile 400
transcode: 0005: 01:AAC: ==> Using profile 56k
libav: AVCodecContext: using SAR=1/1
libav: AVCodecContext: using cpu capabilities: ARMv8 NEON
libav: AVCodecContext: profile High, level 3.0, 4:2:0, 8-bit
Reproduction
Tested on several devices with different linux distros and different TVH versions, different sources -> no transcoded audio output.
The text was updated successfully, but these errors were encountered: