Well the on-going PC build saga continues... Doesn't look like my new 3900x CPU will ship out until the 19th :).. Meaning I probably won't get it until the 22nd or 23rd.
It has been absolutely crazy just trying to get one on back-order. You would think with a roll-out of a new CPU AMD would have plenty in stock, but apparently they were not ready.
Reinstalled Dave's build after 6 months of using the stock firmware ( don't even ask why ) ... and ran again into the annoying error below when diagnosing that everything was being setup correctly with logread ...
Hi,
Just upgraded my already great r8373 to latest r10307 and so far so good.
Unfortunately I use ffmpeg with libffmeg-full to transcode the audio track of a video stream from MP2 to mp3 for my camera server and noticed that libffmpeg-full still has no SSL (https which is basically what every serious server uses now) support. I had to recompile it manually with openssl support AND libshine support (it's a mp3 encoder optimized for embedded systems with no float acceleration) but was a real pain cause I'm basically a newbie and took much time. So my request to DavidC: If it's not a issue can you enable openssl support and libshine for the whole ffmpeg package in the next-ish release?
Also I read somewhere that wrt3200acm has NEON acceleration support which if enabled should be great for transcoding. Is that true? If so can it be enabled somehow?
This is what I basically need (plus NEON support if possible should be amazing):
I've searched the configuration up and down for ffmpeg-custom and doesn't exist. When I do a search for all available packages, according to it, ffmpgeg custom should be next to -mini and -full, but it doesn't exist. This may be a situation where another package has to be turned on before it shows up. However, I have no idea what that package would be. I'm still looking though.
I'm searching for -custom because it contains libshine and probably ssl support.
You need to patch the source of OpenWrt first to make the toolchain "neon aware", then you most likely want to get ffmpeg 4.X as 3.2 is "very old" by todays standards.
Works but needs some tweaking due to changes in OpenWrt's toolchain, I'm slowly moving stuff to another distro so updates will most likely not be very frequent.
I did do a PR about it way back but I lost interest trying to convice people when there's little to no interest despite others also wanting this change and showing nice improvements. https://github.com/lede-project/source/pull/1211
Feel free to resubmit it if you want, I wish you the best of luck.
You need to first turn ffmpeg-custom on under Libraries to be able to select; if you seach on the string, first turn on 2, then you should have 1 as being selectable. But as diizzy stated, without neon enabled its usage is questionable, but that breaks the mamba; but that is somewhat addressable by using the per-device rootfs functionality
The WRT3200ACM does have a SoC that supports NEON instructions (Armada 385) however neither (lib)shine or LAME uses it for encoding however ffmpeg does use it for resampling in some cases. If you're looking for performance you're probably better off using AAC which is available via the fdk-aac library.
Thanks a lot guys for trying. I'd send the .config I used to compile mine but it was a very dirty hack giving errors which I had to correct at every step and probably doesn't even work anymore. If it can be useful just let me know though. I have saved it just in case I need to recompile.
(NEON support should be amazing also. Maybe with it real time video transcoding could be possible on wrt3200 and not just audio as I do now. Turning this router into a full multimedia box. I gotta stop dreaming and go out more).
Thanks for the great advices.
I tried fdk-aac but it was definitely slower than shine mp3 encoding. I needed cause container for segmented video streaming using nginx-rtmp doesnt support mp3 but just AAC. It was very usable though, just slower than shine mp3. Proibably quality was much better though.
EDIT: my AAC string (I ddint need to install additional package:
ffmpeg -i "udp://mymulticastip:xxx?buffer_size=266240&overrun_nonfatal=1" -g 2 -vcodec copy -acodec aac -ar 44100 -ab 128k -strict -2 -rtmp_live live -f flv "rtmp://myserver:xxxx/live/xxxx?e=mysecretkey"
yeah, it makes sense but I guess you have to compile ffmpeg with it's support to use it cause it gives Unknown encoder 'libfdk_aac' even after I "opkg install fdk-aac". I'll try as soon as I recompile the whole damn thing .
openssh-server appears broken in r10307 on my wrt1900ac (v1). After upgrading and installed openssh-server, every client connection results in the dreaded "sshd[]: fatal: Couldn't obtain random bytes" (which kills the sshd server process...).
While the workaround let's me use openssh-server again, would it be better to have something that worked for everyone out of the box?
@cotequeiroz - did you find any openssh problems with the default CIPHERS=ALL and DIGESTS=NONE when you were tracking down the earlier issues in March?
David - Thanks for continued great work on these builds.
Currently on r10307 and using wrt-32X
Has anyone had any issues with having to manually set "Request IPv6-address" to "try" or "force" every time the router has been reset to get an ipv6 address from the ISP? I am not sure if this is an issue from my isp or router. I have to alternate between try and force anytime I have reset the router. Here is the config
I just thought I'd also share my findings on dnscrypt-proxy and ipv6. I noticed I wasn't getting a proper DNS lookup for my ipv6 address after installing dnscrypt-proxy (v2). It was just a matter of updating the config file and restarting.