Jump to content

Calamity1911

Member
  • Posts

    117
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About Calamity1911

  • Birthday May 8

Profile Information

  • Gender
    Male
  • Location
    USA / More or less Chicago
  • Interests
    Consumer Electronics (soldering)
    PC Electronics
    Video Games
    Chemistry
    CAD
    Some Video Editing
  • Occupation
    Some Generic Low Paying Job

System

  • CPU
    Ryzen 5 5600X3D
  • Motherboard
    MSI MAG B550M Bazooka
  • RAM
    32GB (2x16) DDR4 3600
  • GPU
    AsRock Challenger RX 7800XT
  • Case
    NZXT H510i with the side panel always off
  • Storage
    1x Generic 512GB NVME (Windows) 1x 1TB WD Black SN750 (Games) 1x Samsung 870 EVO 2TB (Storage)
  • PSU
    Some 750W 80+ Bronze unit
  • Display(s)
    HP Omen 27i 1440p 165Hz
  • Cooling
    DeepCool AK500 Zero Dark
  • Keyboard
    Logitech G915
  • Mouse
    Razer Basilisk X Hyperspeed
  • Sound
    Sennheiser HD58X w/ Antlion Modmic Uni
  • Operating System
    Windows 11 Pro
  • Laptop
    Dell XPS 15 / i7 10750H / 16GB 3200MHz / 1TB WD SN550 / GTX 1650 Ti / 2560 x 1600 / Linux & Windows 11 dual boot
  • Phone
    Galaxy S21 5G

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well, I did some research and I found some extra information, but I still don't have a solution. If someone stumbles across this forum post, it appears as if the scale video filter in FFMPEG ruins HDR mapping, and additionally FFMPEG was automatically trying to convert the bt2020 raw file to bt709 without tonemapping, which caused the washed out colors. Handbrake still works, but it's significantly slower. Hopefully they add proper support for AMD GPU video decoding.
  2. Hi All, TL;DR Do either the MKV container or MP4 container support 4K AV1 content with HDR10? I've been having issues getting it to work. More Details: Recently I've been backing up my own and my father's Blu Ray collections which consist of both regular Blu Rays and 4K/HDR Blu Rays. I haven't had any trouble with the regular Blu Rays yet, but lately I've noticed some strange issues with the 4K HDR ones. For some context, I recently got an AMD RX 7800XT which has support for both AV1 decoding and encoding. I decided I should try to compress the 80GB 4K Blu Rays using AV1 because why not! The movie I used as a test subject was my Dune 4K Blu Ray, which contained both Dolby Vision metadata and HDR10 metadata according to dovi_tools The 4K Blu Rays are encoded using HEVC/H265 which my graphics card should support for decoding, and starting with the 1.7.x builds of Handbrake, they also support AMF AV1 encoding so I gave that a try. I found out that Handbrake doesn't support AMF decoding at all, so I was limited to around 40fps by the CPU decoding. This wasn't that big of a problem personally, but still kinda irritating. So I used the FFMPEG command line executable since they support AMF decoding through both the existing DirectX 11 Video Acceleration API and the new Vulkan Video API. This did technically work, and I was now able to transcode at closer to 80fps! Although when I went back to play the 4K AV1 MP4s, VLC wasn't tone mapping the HDR properly and everything was washed out. Strange. I checked that the original media was tone mapped properly by VLC, which it was (not desaturated at least). I did a bit of research and found out that some people were reporting that the MP4 container doesn't support all of the metadata needed for HDR (which I eventually proved false... Sort of) so I retired the transcoding but now into an MKV file. Same problem, although the HDR10 metadata was being detected by VLC, just without tone mapping for some reason. So the AV1 MP4 didn't have the proper metadata and wasn't getting tone mapped, and the MKV had the correct metadata but still wasn't being tone mapped. I re-tried the same steps, but instead of AV1, I used HEVC so basically I was just compressing the original by reducing the bitrate. That time, both as an MP4 and MKV, the HDR10 metadata and tone mapping worked properly in VLC. I was able to use dovi_tools again to verify that HDR10 metadata was present in at least the AV1 MKV as well as the HEVC MKV and MP4, so I'm beginning to think it might be a problem with VLC. I tried using Handbrake anyway to create the 4K AV1 files instead of just FFMPEG and confirmed the same exact behavior; metadata was present for both codecs in and MKV container, but VLC didn't tonemap the AV1 video properly. I made sure VLC was updated, same with FFMPEG and Handbrake. Any insights would be welcome
  3. Thanks, that was a good resource! I made sure to download the aarch64-linux-gnu-gcc package for cross-compilation from my 64-bit WSL image (Ubuntu 22.04 LTS) and made sure to enable my desired features in the menuconfig. When actually performing the build, I get a few errors relating to GCC: aarch64-linux-gnu-gcc: error: unrecognized argument in option ‘-mabi=aapcs-linux’ aarch64-linux-gnu-gcc: error: unrecognized command-line option ‘-mtp=cp15’ aarch64-linux-gnu-gcc: error: unrecognized command-line option ‘-mfpu=vfp’ aarch64-linux-gnu-gcc: error: unrecognized command-line option ‘-msoft-float’ When I did a little bit of googling, it seems as if it's an issue with cross-compilation. Any tips/pointers? I have work in a little bit though so my response might be a bit delayed **EDIT** Rookie mistake, I specified ARCH=arm instead of ARCH=arm64. Specifying the latter seems to have fixed it
  4. Hi guys, this is a continuation of my thread over here. I purchased a Raspberry Pi Zero alternative and was looking into modifying a Linux distro with an up-to-date kernel. The manufacturer provides a couple distros based on the 5.10 and 6.1 kernel, but I was looking to build a 6.5 kernel and potentially use Debian 12 or some other distro with the Panfrost Mesa3D driver for the GPU included. I was able to get the DTS file from their github, but I have never built a kernel before. The u-boot source code is also available if that is needed. I don't really know where to start now that I have these. I know I should probably clone the most recent Linux kernel from Torvald's repo and insert the new DTS file, and I read a little bit about building a DTB from the DTS files. Beyond that, I have no idea what to do. Any tips or pointers would be appreciated
  5. I just hopped over to the OrangePi GitHub and lo and behold, under their Kernel 6.1 Linux branch, I found their official DTS for the OrangePi Zero 2W! I have absolutely no idea what to do now, but that's something I guess. Also, they refer to the processor as an Allwinner H616 in the DTS, but it's actually a H618. The only difference I found in reading is that the H618 has a larger L2 cache. Any pointers on what I should do now that I found the DTS?
  6. Sorry for the late updates everyone. It's approaching the end of the delivery window for the OrangePi Zero 2W and tracking still shows it sitting in California after arriving in the United States. I could be mistaken but I think they are extremely similar, maybe just the board layout is different. I found a post here claiming that the OrangePi Zero 3 booted on kernel 6.5-rc with minor tweaks, which could be good news if the board even arrives. If not, I might just get a name-brand Pi 4 4GB. Also I am finishing up college for computer engineering, but I have yet to compile a Linux kernel so I have absolutely no idea what to do in that regard. All of my experiences have been with lower level embedded systems programming so I haven't tinkered much with that kind of stuff. I know OrangePi's docs show how to compile the Linux kernel and a bootable image, but I think it uses a slightly older kernel. Ideally I'd get Debian 12 or similar working since the Panfrost Mesa3D driver for the Mali G30 on the SoC was incorporated in that release **EDIT** I should add I'd love to do some tinkering with building the kernel but I have absolutely no idea where to start. Since starting with Kernel 6.5 it seems like the H618 should boot, wouldn't that mean any Distro based on that kernel should just work or would the bootloader on the board not necessarily see the OS? Again, bear with me here, operating systems and kernels aren't my strong suits
  7. Well, I was able to find some documentation on OrangePi's github, although there is no mention of the Zero 2W as it was apparently released last month roughly when I ordered it. From what the specs say though, it seems similar in architecture to the Zero 2, as the Zero 2 uses an H616 where the 2W uses a H618 which are pretty similar afaik. I also found some of the official firmware bins in the orangepi github as well. I just need to do some more reading I guess.
  8. Hi All, this is my first post in quite awhile. I recently purchased an OrangePi Zero 2W and it should be arriving some time this week. Here's the official link for those interested. Anyway, the OrangePi website claims the board supports a whole host of different operating systems, but OrangePi just provides a somewhat sketchy shared Google Drive folder with the Linux ISOs that they list as compatible. I was wondering if anyone has any knowledge on re-spinning an ISO for an ARM SBC. I know the processor on the SBC I bought is an Allwinner H618 with 4GB RAM, but I don't know how to bundle the necessary drivers, or if the generic Ubuntu ARM ISO will work out of the box. Ideally, I'd like to use something pretty lightweight like the Lubuntu distro since I have had good luck with it on official Raspberry Pi boards, but that goes back to the same question; how to I include the necessary drivers or will they be available out of the box? It also looks like the GPIO for the OrangePI Zero 2W is pin-compatible with the Raspberry Pi, so GPIO drivers would also be nice since one of the features I occasionally use on name-brand Pi's is the UART console so that I can interface with the board without a network connection. Eventually I would also like to configure a self-hosted WiFi AP so that a client can connect directly to the SBC using something like VNC, but the UART console can do a similar thing but without a GUI. In summary, I guess what I'm looking for is some insight into bundling WiFi & GPIO drivers for my OrangePi Zero 2W into an already existing Linux ISO. Thanks for any input
  9. I did get a new adapter that just so happened to use the same chipset and now it is reporting a USB3 connection. I also switched to TrueNAS Core to host the NAS. When writing to the NAS, it still gets ~40MB/s but when reading, it gets ~80MB/s so it's definitely using USB3. That's good enough for now.
  10. Alright new issue. I got a new ethernet adapter and it definitely reports using USB3 instead of USB2. However, I determined that using lsusb -vvv on a ubuntu install. I switched over to TrueNAS Core to give it a shot, and now it seems like it's back to USB2 speeds. Give me a break. **EDIT** Now it seems to do 40MB/s writes but it can actually do 80MB/s reads to/from the NAS now? Sure, man. Good enough for me.
  11. Hi all, In one of my previous posts I was discussing some possible limitations of a Samba share I have set up for a home NAS. Basically, for black friday I got myself a WD 4TB external hard drive for use as a home NAS. I tried setting it up a couple ways. First though, I tested the disk's speed and I got about 200MB/sec sequential over its USB3 interface. I was also recently given an old laptop from a family member who recently upgraded. It's an "old" dell Inspiron 15, but I don't remember the exact model. It has a 6th gen i3 mobile chip in it which should be powerful enough to host a gigabit NAS. The first problem I found was that the on-board LAN port is only 10/100Mbit instead of gigabit. I happen to have a USB3 to ethernet adapter laying around, so I decided to try that. It definitely was faster than 10/100M LAN, but I was running into a different problem. Lubuntu and Kubuntu both were reporting only a USB2 link to the adapter, but still a USB3 link to the hard drive. Even more strange. So I then tested the gigabit ethernet adapter on my Dell XPS15, but on there it was able to get a full gigabit link. I tested that by setting up a network share hosted on the XPS and I was saturating a gigabit link. The one other thing I can think of is the fact that the gigabit adapter uses a USB C connector, but the old dell laptop doesn't have a type C port. I also have a few female USB C to male USB A adapters too, so I have been using those. I know they can do full USB 3 speeds as I use them occasionally on my desktop which doesn't have USB C. (Similar to these, but I cannot find the same exact brand I have laying around) At that point, I thought it could be the driver for the adapter. I was able to find a driver for the ethernet controller chip in the adapter I use, but the linux driver fails to compile due to a code error. I don't know very much C so I just gave up on that and installed Windows 10. Still having a USB 2 link to the adapter. At this point, I think it is most likely the USB 3 controller in the laptop's fault, but I don't know what I can do to fix that. Any advice would be greatly appreciated.
  12. I'm gonna have to eat my words here a bit. It turns out that on Linux, the adapter was only using a USB 2.0 link. My testing methodology for the Ethernet adapter was flawed. Either way, I tried the same dongle on a windows laptop, and it legitimately got gigabit speeds. I ensured that by setting up a windows folder share on the network and it got ~100MB/s. So I then looked into possibly updating the drivers for it on Linux, and I did find some Linux drivers but there were some compilation errors for the drivers. I gave up on Linux all together and then tried windows on the server. Still 40MB/s limit. No idea why at this point. I tried the Ethernet adapter in both of the laptop's USB3 ports to no avail. I have one more thing I can try tomorrow after my college classes.
  13. When I ran lsusb -vvv both the external drive and the gigabit adapter reported being connected over USB3. If I remember correctly, they actually reported USB3.10 but still, basically the same.
  14. I verified that the hard drive is indeed connected over USB3 by using lsusb -vvv and verified the gigabit connection to the local network.
  15. It's 40 megabytes, not bits. Sorry for any miscommunication. I made sure to connect both the gigabit ethernet adapter and the external drive to separate USB3 ports.
×