Something else I considered when looking at the ENC8. It shows output (encode) at 1080P30x8. If using all eight input, does the encode really max out at 30 FPS?
1 Like
20260731
- Added support for pushing pure audio streams on the [Live Streaming] page.
- Added MP3 format recording on the [File Recording] page under Extended Features.
- Fixed English translation issues on the [Serial Port Control] page under Extended Features.
- Optimized file upload prompts and fixed an issue preventing the deletion of files with Chinese names on the [Storage Management] page under Experimental Features.
- Adjusted the logic for uploading and updating upgrade packages.
- Optimized TRTC streaming for SS524V100 series devices.
stealing my job! LOL
Speaking of firmware updates. I recently (and very carefully) updated my enc1-v3 unit from version 3 to the latest version, using the web interface - carefully doing this in sequence not skipping versions. As of today i just updated again. Thanks @mackid1993 and especially @hancox (lol) for keeping us alerted to the firmware updates
Since my update i have noticed a very infrequent annoying pixelation issue. Its been very hard to consistently duplicate the issue. I never had this before. But on certain shows, like house of the dragon, out of 1 hour of program material i might get 1 or 2 instances where the pixalation occurs for about a second.
Is there a consensus what bitrates and other settings to use? I changed mine to H.264.main, upped my GOP from 1 to 2, changed from CBR to VBR. But im still seeing the same issue.
I even disabled all the subchannels, my mix output, etc to reduce cpu load.
And it “seems” to only occur on this one show. When i re record a repeat, i see the same pixalation issue, but at different random times.
Any ideas folks?
I've been fighting similar in recent weeks. I'm still on 5.2.0 build 20260531. most of my pixelation was fixed by cleaning up my w11 a bit and most impactfully doing a flea power drain on my mini pc (unplug power & ethernet + power btn 30+sec) 
I haven't noticed it too much the last few days, but i think it is still there sometimes.. if it is related to linkpi, my guess would be something in the network stack since my minipc's network adaptor was a major source of mine.
also I just checked and noticed one of the times I changed usb encoders, TS Config - flow control turned itself on.
my understanding is we don't want the flow control but that is based on tcp/ip flow control so hopefully someone can enlighten if there's any difference with TS flow control.
I hate to suggest it because of what happened to @jsfullam but if you know what you're doing and you're very careful, it might be worth doing a full flash rather than an update. I've done it several times on my units, troubleshooting things, and it's quite easy to just pull the rootfs image and flash it off a USB stick. You basically just reinstall the operating system rather than updating it in place, and it might clear up any weird issues.
Well circling back to this I just bought the bullet and ordered another linkpi. Im still having this pixalation issue after changing my encode settings all over the place.
Surprisingly it seems to be just happening on specific networks live streams. It may not even be the encoder,
Worst case ill do a reflash now that ill have a back up unit.
Which one did you order because if you get it from YouYeeToo, sometimes they have coupons.
1 Like
I picked up another enc1-v3 for $129 on amazon. Sept 2 delivery
What I learned after buying three of those is to just buy an ENC5 V2.
1 Like
Well you wont sell me (for real cheap) one of your spare enc1-v3s, so they cant all be that bad
Sorry, I want to keep them just in case something breaks and I need a backup until I can get either repaired or replaced.
I actually have had luck getting pretty good deals on AliExpress on these too.
1 Like
No need to apologize, thanks for all the valuable tips!
AliExpress has a coupon for the LinkPi Enc8 bringing the price down to $382.77.
Link Pi ENC8 4K-HDMI Video Codec 8-channel HDMI Encoder 4K Decoder SRT NDI vMix RTSP/RTMP/HTTP/HLS Multi-protocol Live Streaming
2 Likes
5.3.1 is out. I don't really know what it does, because the changelog is the same. I have a feeling it fixes a memory leak, because the previous two builds have had a massive memory leak that has only gotten worse. So I'm hoping that's what it was there to solve. My encoder that's been up for a few weeks now was at 87% memory usage. So that's obviously not normal or good.
Moving this here as I believe this isn't a ADBTuner problem but either a LinkPi problem or a problem with all 5 of my various generation ONN devices:
Gearing up for college sports and noticed that my ADBTuner source is showing a new "wrinkle". I have 5 ADBTuners setup using 5 ONN devices and a 5 Port LinkPi device feeding my devices.
I see both under NBC Sports using the YTTV app as well as ESPN based sources using the ESPN app that I am getiing "micros" stuttering. What I mean by that is that every 1 second, i'll see a micro stutter. It's like for every 200 frames, about 10-20 are skipped so I get about 9/10ths of smooth playback and then a micros jump. It's not so bad that I would abandon ADBTuner as a source, but the OCD in me says there has to be a fix. It's happening on all 5 ONN devices (different generations of ONN devices).
I'm using Wifi for the devices, but they are withing 3-4 feet of the router (synology router, and rarely do I have more than 1-2 devices running concurrently, so I can't imagine it's a wifi bandiwtch issue.). I don't recall this being an issue previously, but last year most of my sources were fed by non-ADBtuners, so it may have been persistent and I just didn't notice.
Thanks for any input, fortunately these early games are not "must see", so happy to work through this over the first 2 weeks of the season.
Thanks for any suggestions on how to trouble shoot.
Since 5 different variations of ONN devices are showing the same behaviour and they are different generations and different APPs have been tested, this leads me to think it's the LinkPI. Here's the current version I am on (updated a few weeks ago, that may be the culprit):
I did reboot the device and still seeing the same symptoms.
In the past I recall the suggestion was to use AVBR as opposed to VBR. I bet you are using VBR for a reason... Care to share your findings?
1 Like
Just the opposite in fact:
Check out the 2025 edit in this post. Also, H.265 is fine to use in ah4c, and also in ADBTuner now.
Thank you for the quick response, I have updated my settings. I have not had any issues to date using ADBTuner but I am about to add 5 more inputs so I wanted to see what the latest was.