Sorry actually it’s the same ENC1V3.
Seems like after an update, when using the mp3 audio encoder it will fill the memory, previously this would not happen.
Setting to AAC and rebooting fixes the issue.
Was using mp3 as it was working better with my HomePods I felt like, but will just stick with AAC.
Thanks for the tips though, if I run into issues in the future will try what you recommended.
I tried to change my ENC5V2 audio encoding to +6 dB because the LinkPi channels are slightly quieter than the TVE and HDHR ones but doing this seems to make the streams inaccessible - has anyone been able to change the audio settings on the Encode tab under overall config?
EDIT: after further review, apparently, after changing something on this page and doing a "save to local" or "save to group", then after a nightly reboot, sometimes the LinkPi ends up in a state where the streams are unavailable - sometimes changing a setting and doing a "save to local" and "save to group" can fix the problem as well - has anyone experienced this? Any solution?
App version:
3.5.1 build 20241031_2405
SDK version:
3.5.1 build 20241031_29857
Sys version:
3.5.2 build 20241031
Anyone found any settings to change to get the picture to be a little more crisp and less soft?
App version
3.5.1 build 20241031_2405
SDK version
3.5.1 build 20241031_29857
Sys version
3.5.2 build 20241031
20241231 is out
The laboratory has added a system log function, which supports viewing/downloading system operation logs
The interface output page has added Line Output control
The encoding setting page has added AAC-HE encoding for audio encoding
The file recording page has added loop recording, segment recording, power-on recording and other functions
Fixed the problem that audio mp3 encoding does not work
Optimized the scaling and performance issues of watermark special effects
Modified some page text descriptions
I just updated one of my linkpi from 1.0.0 to the latest version, however now the led screen infront is upside down. Anyone else face something similar? and how do you fix it?
how did you update? i seem to remember this being a byproduct of back-door installing the firmware.
I downloaded the file from the website and put it on a USB thumb drive, and reloaded the software like that, since the old one was very old, version 1.0.0 The update went fine, and it looks like it's running well, it's just the screen that is upside down.
I believe the next update from normal means will fix this.
I see that that there is a new LinkPi 4k60 encoder available - LinkPi ENC1Pro. This looks interesting and although significantly more expensive than the other 1 input models looks like a price breakthrough for a 4k60 HDMI encoder. I don't know if HDR is supported.
I'd be interested in anyones feedback of ENC1Pro if they decide to buy one.
The MiniENC1 looks interesting as well and is powered by USB-C.
I've ordered the MiniEnc1. I've currently got the ENC1V2 which works very well. Hopefully, the MiniENC1 is powerful enough to encode one stream well. The specs for the MiniEnc1 state that it can encode one full 1080p 60fps stream or 2 1080p 30 fps streams.
LinkPi ENC1Pro $320
4k60 encode is nice but WOW on price for single input.
Really wish someone would come up with a reasonably priced one that did 5.1 audio encoding even more than 4k60 instead of everything being down converted to stereo.
I picked up a MINIENC1 a month ago to try it out. It works just as well as the ENC1V2 for what Channels users would be using it for.
Just make sure you upgrade the firmware as the shipping firmware has a bug that locks it to 30fps.
It’s a tiny thing:
Sharing some info: I have noticed with the ENC5V2 and the MINIENC1 that the AVBR encoding mode doesn’t work as well as it does with the ENC1V2. The bitrate often drops way too low during scene transitions which results in a few seconds of really blocky video. Based on this experience my recommendation now is to stick with VBR or CBR mode.
—
And sharing some more info:
The Onn 4k Pro streaming devices are a good combo with most of the LinkPi devices (not the MINIENC) because they are also powered by 12v DC (5.5mm connector).
A power supply like this:
https://www.amazon.com/gp/product/B0C3LBN71Q/
combined with a simple splitter
https://www.amazon.com/dp/B06Y1Y94PR/
can power the whole setup without any additional adapters.
Here's a bit more detail (in Bash function form) on using the LinkPi API. For my purposes, I've found that logging in (to get the needed tokens), followed by performing the task and then logging out to be the best way to go. The tokens are valid for a period of time, but there'd be more code required to deal with that.
This function should give you an idea what it looks like to send a JSON payload to change the crop values for given HDMI input port on a LinkPi:
linkpiCrop() {
linkpiStreamID=$(echo "$encoderURL" | awk -F'stream' '{print $2}')
linkpiCropLeft="\"$1\""
linkpiCropRight="\"$2\""
linkpiCropTop="\"$3\""
linkpiCropBottom="\"$4\""
linkpiPasswordMD5=$(echo -n admin | md5sum | awk '{print $1}')
linkpiJSON=$(curl -v -c linkpi_cookie --digest -u "$LINKPI_USERNAME:admin" "http://$LINKPI_HOSTNAME/link/user/lph_login?username=$LINKPI_USERNAME&passwd=$linkpiPasswordMD5")
lHash=$(echo "$linkpiJSON" | jq -r '.data."L-HASH"')
pHash=$(echo "$linkpiJSON" | jq -r '.data."P-HASH"')
hHash=$(echo "$linkpiJSON" | jq -r '.data."H-HASH"')
# echo "L-HASH: $lHash"
# echo "P-HASH: $pHash"
# echo "H-HASH: $hHash"
curl -s --digest -u "$LINKPI_USERNAME:admin" -b linkpi_cookie -X POST -L http://$LINKPI_HOSTNAME/link/encoder/set_cap_chns \
-H "L-HASH: $lHash" \
-H "P-HASH: $pHash" \
-H "H-HASH: $hHash" \
-H "Content-Type: application/json" \
-d '[{"id":'$linkpiStreamID', "L":'$linkpiCropLeft', "R":'$linkpiCropRight', "T":'$linkpiCropTop', "B":'$linkpiCropBottom'}]'
curl -s --digest -u "$LINKPI_USERNAME:admin" -b linkpi_cookie -L http://$LINKPI_HOSTNAME/link/user/lph_logout \
-H "L-HASH: $lHash" \
-H "P-HASH: $pHash" \
-H "H-HASH: $hHash"
}
I posted this late last year too, but here's the LinkPi API documentation, for those interested in getting the most out of this intriguing device:
I am coding a VB.NET application to get API control
I am able to login with Digest Authentication and can get the 3 HASH values
When i send a new request to api call what do i have to add to the request header to work?
Must the request header be the same as in the login request?
Is there any example of doing this?
Welcome to the Channels DVR community!
The post you replied to includes an example Bash function for the entire process of logging in, and extracting the hashed tokens.
In addition, this function then re-uses those tokens to send crop values to the encoder before logging out
It is possible to continue to use the same tokens, until they expire after some hours, but that would require additional logic.
Thanks for fast reply!!!
I tried to send the api request after successfull login with the three tokens L P H but get the response to first login?
Then you're probably not sending the tokens correctly. This part of the above function shows how it's done:
curl -s --digest -u "$LINKPI_USERNAME:admin" -b linkpi_cookie -X POST -L http://$LINKPI_HOSTNAME/link/encoder/set_cap_chns \
-H "L-HASH: $lHash" \
-H "P-HASH: $pHash" \
-H "H-HASH: $hHash" \
-H "Content-Type: application/json" \
-d '[{"id":'$linkpiStreamID', "L":'$linkpiCropLeft', "R":'$linkpiCropRight', "T":'$linkpiCropTop', "B":'$linkpiCropBottom'}]'
I got it working!!!!
Thanks for the hint