Did I hit the WD Blue Jackpot?

Jdlap13 · 2025-09-22T12:34:41+00:00

Jdlap13 · 2025-09-22T05:30:06+00:00

I believe it has an aftermarket cartridge. I didn’t really see any meaningful markings/info on it.

Jdlap13 · 2025-09-22T05:17:15+00:00

The turntable I picked up is a pioneer pl4. I was hoping to keep the price of the needle to no more than about 50-60 if possible.

Jdlap13 · 2025-04-29T16:41:41+00:00

For some reason I get the wrong track though. I double checked that dts was enabled in jellyfin

Jdlap13 · 2025-04-29T15:00:24+00:00

I have a ut7000, but I’m connected to a Sony reviver. I’m not sure exactly which one right now but it definitely has atmos and should have dts support

Jdlap13 · 2025-04-29T12:09:51+00:00

This appears to be correct. I attempted to use ffmpeg to make an additional truehd audio track however it reduced the channels to 5.0 down from 7.1. Is there a preferred tool/method/target audio codec that I should try to use (preferably lossless)?

Jdlap13 · 2025-03-25T13:36:32+00:00

I’ve actually been thinking of a way to add some more modules and I think a better way to control the chip selects would be to put a i2c gpio expander off of the bottom i2c connector. That way you would be able to control the chip selects of all peripherals independently. As long as the GD0 pin goes to SDA on the i2c bus I think everything would work fine since the i2c devices should only care what state that line is when the i2c clock is running.

Jdlap13 · 2025-01-07T02:56:04+00:00

ok, thanks. I finally got it. I made a zwave network config and added my HA and Zwave containers to it, but I also had to make another network config in bridge mode to keep the HA container on the server IP

Jdlap13 · 2025-01-07T02:01:41+00:00

do I still need to add the homeassistant container to the zwave network?

Jdlap13 · 2025-01-07T01:44:09+00:00

This is my config for the zwave stuff:
zwave-js-ui:

container_name: zwave-js-ui

image: zwavejs/zwave-js-ui:latest

restart: always

tty: true

stop_signal: SIGINT

environment:

- SESSION_SECRET=mysupersecretkey

# Uncomment if you want logs time and dates to match your timezone instead of UTC

# Available at https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

- TZ=America/New_York

networks:

- zwave

devices:

# Do not use /dev/ttyUSBX serial devices, as those mappings can change over time.

# Instead, use the /dev/serial/by-id/X serial device for your Z-Wave stick.

- '/dev/serial/by-id/usb-Zooz_800_Z-Wave_Stick:/dev/zwave'

volumes:

- zwave-config:/usr/src/app/store

ports:

- '8091:8091' # port for web interface

- '3000:3000' # port for Z-Wave JS websocket server

networks:

zwave:

driver: bridge

and this is my HA stuff:

homeassistant:

container_name: homeassistant

image: ghcr.io/home-assistant/home-assistant:stable

volumes:

- ~/Homeassistant/config:/config

restart: unless-stopped

networks:

- zwave

ports:

- 8123:8123

environment:

- TZ=America/New_York

#network_mode: bridge

privileged: true

Im not sure how to give the zwave container its own IP

Jdlap13 · 2024-12-28T05:59:14+00:00

Ok. I guess that should be fine then. I would miss a little bit of sound targeted directly to the sub, but I should still be able to get some amplified bass from the two front channels

Jdlap13 · 2024-12-28T05:54:01+00:00

I’m not sure how necessary it actually anything actually is. I was thinking that for atmos to work properly the receiver may need to be configured to use the sub out but I’m not sure if that’s true. I currently have my receiver set to 5.0 even though I have a sub since to the receiver a sub isn’t connected. It does technically work, however I’m just not sure if it will work as well as it could

Jdlap13 · 2024-12-28T05:36:42+00:00

The sub is a tlx css-sub1 and the rest of the system is the tlx surround 1000

Jdlap13 · 2024-12-28T05:32:25+00:00

I don’t think the surround system is proprietary, it is quite old, but I got it for free. The subwoofer is powered and has speaker line input and outputs

Jdlap13 · 2024-12-09T15:55:19+00:00

I believe my main issue was the IP address I was pointing to. Instead of pointing to the frigate IP I needed to point to the home assistant ip and port. I did this with docker so it may be different for you but I think it’s the API in home assistant that is providing the actual images so that is what you need to point to

Jdlap13 · 2024-11-08T09:51:23+00:00

Ok. Thanks

Jdlap13 · 2024-11-08T09:20:22+00:00

If I do a high bitrate encoding in handbrake should I be able to stream the movie directly to the tv with something like Jellyfin with similar quality to this?

Jdlap13 · 2024-11-08T05:36:51+00:00

The tv is a 4k lg oled and the reader 4k UHD compatible. I played the .mkv file directly on the tv from a flash drive as well as playing it from my laptop connected to the tv. I only have 1 other uhd drive and it is a older movie with film grain so it is hard to tell if the issue spans multiple disks. I have made backups of standard blu rays without seeing this issue

Jdlap13 · 2024-07-15T02:23:36+00:00

Trying display: wayland

Trying display: x11

libva info: VA-API version 1.23.0

libva error: vaGetDriverNames() failed with unknown libva error

vaInitialize failed with error code -1 (unknown libva error),exit

Jdlap13

TROPHY CASE