lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
<Armbian-Discord> <T​onymac32> Wait for software worth using
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 265 seconds]
<Armbian-Discord> <T​onymac32> I dealt with the ASUS fork of, and the main, Rockchip kernel with the Tinker board. I will not waste my limited time on this earth dealing with such a hopelessly hacked up pile of garbage. Their SoC is too expensive anyway, I can almost buy an x86 at those prices AND IT WOULD RUN LINUX BETTER ANYWAY
<Armbian-Discord> <T​onymac32> To say I'm disappointed is a major understatement
<Armbian-Discord> <T​onymac32> I honestly think it's detrimental to this project to even look at that SoC until something changes
<Armbian-Discord> <T​onymac32> But I'm one cranky jerk among many 🙂
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 265 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
<Armbian-Discord> <b​albes150> A very strange device. To buy the "simplest radio receiver for the Internet" for such an amount???? 4k video, via 100 MB LAN or USB 2.0 ? very funny ....
<Armbian-Discord> <T​enkawa> omg
<Armbian-Discord> <T​enkawa> that couldn't even handle a 4k video
<Armbian-Discord> <T​onymac32> 100Mbit certainly can handle a 4K stream 😆. (25 Mbit required)
<Armbian-Discord> <T​enkawa> I question USB2 though
<Armbian-Discord> <T​enkawa> the latency
<Armbian-Discord> <T​enkawa> On IO bus transfers would probably bog it down horribly
<Armbian-Discord> <T​onymac32> Well USB is a pile of 🐕 💩 for sure, but 480 Mbps even with garbage latency, the buffer should hold up
<Armbian-Discord> <T​onymac32> Rememeber the video is still compressed at that point
<Armbian-Discord> <T​enkawa> Thats true.. the compression should help a lot.. fortunately it can buffer too since this isn't gaming or anything.
<Armbian-Discord> <T​enkawa> Not like you gotta have quick HID reaction
<Armbian-Discord> <N​icoD> I can't even do 4k60 with my 5Ghz wifi. So don't think 100Mbit can do it. All depends on file format. h264 are biggest files but need least CPU. h265 is a lot less but need more cpu. And AV1 is amazing small. Also again needs way more cpu processing power. Most 4K from streaming services are not really 4k. It is compressed like hell. Youtube the same.
<Armbian-Discord> <N​icoD> Like I've got here Maverick. 2h10m. And it's 22GB.
<Armbian-Discord> <N​icoD> h265
<Armbian-Discord> <T​onymac32> I think that's a driver problem, NicoD
<Armbian-Discord> <N​icoD> Why?
<Armbian-Discord> <N​icoD> If you want to stream from your NAS. I think it's a bottleneck to have 100Mbit ethernet. I'm using the OPi+ with 100Mbit and it ain't ok to stream my video. I only use it for my MP3's.
<Armbian-Discord> <T​onymac32> I think that's bottlenecked in a lot of places 😆
<Armbian-Discord> <N​icoD> Well, the device is on for years. Never went down. So I'm not bothered in replacing it. I was waiting for the Rock3B to be released for that. But no idea if that will ever be released.
<Armbian-Discord> <N​icoD> ___ ____ _ / _ \| _ \(_) _ | | | | |_) | |_| |_ | |_| | __/| |_ _| \___/|_| |_| |_| Welcome to Ubuntu Bionic with Armbian Linux 4.19.62-sunxi System load: 0.06 0.07 0.01 Up time: 122 days Memory usage: 27 % of 999MB Zram usage: 16 % of 499Mb IP: 192.168.1.41 CPU temp: 40°C Usage of /: 92% of 7.1G I guess I had a power cut 122 days ago...
tkaiser has quit [Ping timeout: 268 seconds]
tkaiser has joined #armbian-rockchip
tkaiser has quit [Ping timeout: 265 seconds]