peterm6881 has joined #Speedsaver
<peterm6881> mpv default cache out of the box is 1 MByte, which is 9 seconds at flac 2ch 44100 Hz
<Xogium> sounds relatively decent
<peterm6881> hmm.... mplayer is, rather unhelpfully, 28 to 45 %
<peterm6881> whatever the fuck that means
<Xogium> lol
<peterm6881> how's u Xogium ?
<Xogium> alive ;)
<peterm6881> do you know this song?
<peterm6881> its edgy hard rock, it'll sound good in your ears
<peterm6881> Pearl Jam
<Xogium> hmmm nop, didn't know
<Xogium> but sounds nice
<peterm6881> I can confirm your findings that you are indeed alive
<peterm6881> ;)
<peterm6881> Thankfully
<Xogium> good
<peterm6881> I would miss you if it were not the case
<Xogium> awww, thank you
<peterm6881> this content has been accessed 81 million, seven hundred and seventy eight thousand and six hundred and sixteen times
<Xogium> that's a lot of views
<peterm6881> i live in a lot of peoples memory. I prefer it, to having them in my FACE
<peterm6881> But yeah, you're a cool person to hang out with
<peterm6881> so keep alive as best you can, for me. I'm selfish that way
<Xogium> ;)
<peterm6881> ;)
<peterm6881> any idea where the config file would be hiding in mplayer / mpv?
<peterm6881> "/usr/bin/mplayer /etc/mplayer /usr/share/mplayer"
<peterm6881> which of those is the best place to look
<peterm6881> gotta be "/etc/mplayer" surely..
<peterm6881> # cache settings
<peterm6881> #
<peterm6881> # Use 8MB input cache by default.
<peterm6881> #cache = 8192
<peterm6881> its all commented out.... dunno what to make of that
<peterm6881> but 8 MByte is unquestionably a shit load more than 1 MByte
<peterm6881> well, given mplayer works, and 8 Mbyte is obviously significant in some way, guess I'll take a punt on that
<peterm6881> and set mpv to 8 Mbyte
<Xogium> 8 mb, holy shit
<peterm6881> meh, why not
<peterm6881> wanna know what "/etc/mpv/mpv.conf" says?
<Xogium> hehe sure
<peterm6881> hwdec=vaapi
<peterm6881> thats literally all she wrote
<peterm6881> to be fair, its not commented out
<peterm6881> :)
<Xogium> weird
<peterm6881> weird, and more importantly, unimportant
<peterm6881> Invalid value for option cache: 8000
<peterm6881> no
<peterm6881> auto
<peterm6881> yes
<peterm6881> Valid values are:
<Xogium> hmm
<Xogium> maybe it has another option like --cache-size or something
<peterm6881> hmm.... curiouser and curiouser, said Alice
<peterm6881> yes gives me the 1 Mbyte
<peterm6881> no gives me none, so evidently yes is the default
<peterm6881> now for auto
<Xogium> auto would probably decide weather to enable it or not if the thing to be played is local or remote
<Xogium> is my guess
<peterm6881> very probably, since its identical to yes
<peterm6881> ok wait
<peterm6881> let me try your suggestion
<peterm6881> by the way, do you think it would be worth offering a Buildroot image of this?
<Xogium> of what exactly ?
<peterm6881> I'm think know, go with Armbian only, or Armbian and Arch
<peterm6881> no *
<peterm6881> the radio on the OPi0
<Xogium> dunno ?
<peterm6881> since mangopi-r3c is unuseable
<Xogium> I mean, opi is already supported in upstream buildroot
<peterm6881> yes that makes it more attractive
<Xogium> as for arch, there's no official support so I wouldn't recommend it
<Xogium> honest, the only distro that ever bothered supporting the opi boards far as I know is armbian
<peterm6881> is there such thing as official arch support for any arm board?
<Xogium> sure
<Xogium> check out archlinuxarm.org
<peterm6881> And a big thanks to the individuals and companies that provide us with the hardware and resources to continue development.
<peterm6881> Hardkernel
<peterm6881> ARM
<peterm6881> Marvell
<peterm6881> GlobalScale
<peterm6881> AMD
<peterm6881> Olimex
<peterm6881> CubieTech
<peterm6881> CircuitCo
<Xogium> globalscale is questionable, but… heh
<peterm6881> yeah theres a bunch of Allwinner armV7 boards.....
<peterm6881> it should be entirely possible to get added to that list
<peterm6881> if i could be assed
<peterm6881> since we already know it works without any hassle at all
<Xogium> there used to be a lot more stuff before, when armv5 and armv6 were still supported… ah well
<Xogium> well any hassle, yeah and no, since they run mainline kernel there won't be audio nor anything like usb even I believe !
<peterm6881> dunno never tried it
<Xogium> this are the patches I carry for our buildroot orange pi build
<Xogium> 0001-DTS-sun8i-h2-plus-orangepi-zero-added-audio-codec.patch
<Xogium> 0002-DTS-sun8i-h2-plus-orange-pi-zero-added-i2c-buses.patch
<Xogium> 0003-DTS-sun8i-h2-plus-orangepi-zero-enable-usb.patch
<Xogium> sooo… erm. Yeah
<peterm6881> its interesting the H2+ worked at all for Arch, since ALL their officially supported stuff is either A10 or A20, with one A64
<peterm6881> the A64 is also listed in the armv8 section, wtf
<Xogium> there is a generic armv7 tarball you can use for this
<Xogium> it means you have to setup the bootloader yourself and know how to boot the platform, but in theory
<peterm6881> how can it be both
<Xogium> how can it be both… both what ?
<Xogium> I mean to say that there are different tarballs for each platforms, including a generic armv7 and generic armv8 tarball
<Xogium> that's in case your hw isn't supported but you still want to try arch on it. But like I said you have to know how to boot it up properly since there'll be no hand holding. You have to know the bootloader and what it expects to manage a successful boot, and configure yourself
<peterm6881> --cache Choices: no auto yes (default: auto)
<peterm6881> --cache-dir String (default: ) [file]
<peterm6881> --cache-pause Flag (default: yes)
<peterm6881> --cache-pause-initial Flag (default: no)
<peterm6881> --cache-on-disk Flag (default: no)
<peterm6881> --cache-pause-wait Float (0 to any) (default: 1.000)
<peterm6881> --cache-secs Double (0 to any) (default: 36000.000)
<peterm6881> --cache-secs is the key
<peterm6881> although secs is overrated tbh
<peterm6881> 36000 seconds is 10 hours
<peterm6881> umm.. what the actual fuck?
<Xogium> is it seconds ?
<Xogium> lol
<Xogium> that would sound incredibly stupid if it is
<peterm6881> Error parsing commandline option cache-secs: option requires parameter
<Xogium> sounds like you need an = sign
<peterm6881> yeah but what do they mean by (default: 36000.000)
<Xogium> no idea, honestly
<peterm6881> I think maybe thats a stupid developers joke
<Xogium> it might not be measured in seconds or do what you think it actually does
<peterm6881> yeah but how do you choose the default
<peterm6881> let me try specifying default
<peterm6881> The cache-secs option must be a floating point number or a ratio (numerator[:/]denominator): default
<peterm6881> meh, lets just try 20
<peterm6881> still 10 seconds 1 MByte
<peterm6881> this is a crock
<peterm6881> 5 worked
<peterm6881> it wont let you go above 10 seconds
<Xogium> --cache-secs=<seconds>
<Xogium> How many seconds of audio/video to prefetch if the cache is active. This overrides the --demuxer-readahead-secs option if and only if the cache is enabled and the value is larger. The default value is set to something very high, so the actually achieved readahead will usually be limited by the value of the --demuxer-max-bytes option. Setting this option is usually only useful for limiting readahead.
<peterm6881> we can only drop the stupid thing
<peterm6881> im gonna do some more troubleshooting of the actual error
<Xogium> I reckon its network being bad
<Xogium> well… if you want to check if it is or not really
<Xogium> use ethernet and disconnect from the wifi on the board
<Xogium> I'm fairly sure this is related to the xr819 chip being crap, at least partially
<peterm6881> theres something mpv doesnt like about the xr819, because it never cuts out with that error on the NEC. And yet mplayer is fine, extremely reliable
<peterm6881> yeah indeed
<Xogium> yeah… but mplayer is basically dead by now so…
<Xogium> stuck between 2 hard places, I reckon
<peterm6881> yeah plus it doesnt control the volume / mute
<peterm6881> thats why im having another stab at mpv
<Xogium> I figured so… but honest, with that wifi being so crappy, its not worht turning it into a buildroot demo
<Xogium> especially not since on buildroot it tends to freeze the system and do all sort of weird shit
<peterm6881> yeah plus demonstrating Buildroot is kinda like demonstrating a house brick
<Xogium> and in theory you don't really demonstrate buildroot
<Xogium> you demonstrate some self-compiled OS you built using buildroot, to showcase the hardware
<peterm6881> yeah and people go oh wow cool ok how do i update this, at which point you go, umm... yeah... about that
<Xogium> because people think buildroot is a linux distro when it isn't
<peterm6881> id prefer a demo image people could actually fuck with. Buildroot is for products
<Xogium> well then opi, just tell them to install armbian lol
<peterm6881> I didnt even know what it was, but i do now. Its roll your own Linux
<Xogium> well, its an easier sort of roll your own linux, and strictly for embedded systems
<Xogium> if you want the hardcore way, check out linux from scratch
<peterm6881> have you mastered it ;)
<Xogium> no
<Xogium> that's too advanced, even for me
<peterm6881> do you know what usermod -a means?
<peterm6881> the -a part
<peterm6881> actually it doesnt matter, ignore that
<peterm6881> long story
<Xogium> hmm I never actually use usermod
<peterm6881> brb
peterm6881 has quit [Remote host closed the connection]
peterm6881 has joined #Speedsaver
peterm6881 has quit [Quit: Leaving]