bitwolf

joined 1 year ago
[–] bitwolf@lemmy.one 3 points 14 hours ago

Oh wow! That goes back far, I had no idea. Thanks for enlightening!

[–] bitwolf@lemmy.one 1 points 16 hours ago (2 children)

What do you mean by putting Honda and VW in the list?

[–] bitwolf@lemmy.one 6 points 16 hours ago
  • Stray cat strut - the stray cats
[–] bitwolf@lemmy.one 6 points 16 hours ago

It'll be very hard to prove they respect the button. Considering they probably sourced the data immediately after the button was put in place.

[–] bitwolf@lemmy.one 1 points 21 hours ago (1 children)

Verify that your device does not share your contact book and texts over bluetooth (will break the infotainment built in "call X person" feature should you use that over your phones assistant for some reason)

Its usually in the bluetooth settings for a particular device paired to your phone

[–] bitwolf@lemmy.one 1 points 21 hours ago* (last edited 21 hours ago)

Anyone happen to know where the sim card is?

I would find it appealing to have WiFi only

[–] bitwolf@lemmy.one 1 points 1 day ago

Been using vite for a while and haven't had to think about it.

Glad node is catching up. But it'd spare even more headaches if it natively supported ES6 modules

[–] bitwolf@lemmy.one 6 points 1 day ago* (last edited 1 day ago) (1 children)

What I would do if look at every point in the video and audio chain and validate they all support hardware decoding (or passthrough / direct stream) for your supported codec.

Based on what you told me. I know your chain might look something like this:

Server
  > Network
     > streamer
        > HDMI
           > TV
        > audio cable
           > receiver or amp
              > audio cable
                 > speaker

For your two speaker setup, is it hooked up with a digital cable or analogue?

If the stereo is analogue, does it support audio at a different sampling and bitrate than what the player puts out?

Or if it's digital, does it support AC3? In a quick search I saw complaints about EAC3 not working well despite being advertised as such. So I wouldn't rule it out.

When you stream from the Roku, you can look in your media servers settings to see if it's transcoding the video or audio. However for the stereo system, or whatever is powering the speakers, you would have to reference its supported formats.

I did find the Roku Developers page and something noteworthy is

Supported video codecs

Videos can be encoded using H.264, HEVC (H.265), VP9, or AV1 (DASH only) codecs.

Something else that may be a good lead, looking at their supported audio codecs it lists

16bit | 48 Khz | Passthrough

For AC3, this is a but ambiguous to me, if given 44.1hkz (much more popular), will it pass through 44.1khz? Will it be delayed? Will it refuse to play? They also don't specify if this is hardware accelerated or software decoding within the Roku.

If the Roku's cpu is being fully utilized decoding video in software, it may not have the cpu to decode the audio reliably. This is unlikely as most streamers are built with hardware decoding support to enable cheaper smaller lower power components to be used.

I did see on the forums people recommend AAC for general support but Roku themselves recommenf E-AC3 for 5.1 audio.

People often recommend forcing Direct Stream and disabling transcoding as a troubleshooting step to force out the container formats that won't work. It may also be worth a test and see if you lose audio.

As for where I look specifically, I tend to look for the most verbose documentation I can find, the Roku developer docs i linked would be what I would look for. I also did a lot of research on audio gear which helped as prior knowledge. Audio-science review forums taught me a lot over time from reading reviews.

As an aside I generally recommend Open Source formats where possible (AC3 and EAC3 are not) because they tend to have broader support in perpetuity. I also find Android players tend to have very broad codec support (piggybacking mobile phone components).

But I don't like to recommend new hardware in general because not everyone can buy a new device.

This is a bit all over the place at this point, but I hope it gives you some leads for determining the cause!

[–] bitwolf@lemmy.one 12 points 1 day ago* (last edited 1 day ago) (3 children)

I usually don't skip an opportunity to rip on Roku but it's possible the player supports the video codec but the audio is being software rendered.

Our stereo system also added delay for some codecs so we had to change that as well

We had to retranscode some of our library because my dad really likes his Roku

[–] bitwolf@lemmy.one 5 points 1 day ago (3 children)

Trickle down economics?

[–] bitwolf@lemmy.one 13 points 1 day ago (1 children)

The thing is the 7800x3d is a gem of a CPU. It's has more compute than I could use and it's low power and runs cool.

I'm going to run it until I can't anymore, and I'll continue to upgrade around the AMD ecosystem unless they stop being awesome.

 

I noticed with QPR3, the back gesture in Sync now shows a black screen during the animation.

Could this be fixed? I read it'll become default in Android 15.

42
submitted 1 year ago* (last edited 1 year ago) by bitwolf@lemmy.one to c/linux_gaming@lemmy.world
 

I don't know if this is desired, however I personally would appreciate compatibility reports for newly released games.

Since I preordered with early access I can contribute.

System:

CPU: 7800x3d
GPU: 7900xtx Nitro+
Memory: 32gb ddr5 6000mhz
OS: Fedora 38 KDE (Wayland session)
Runtime: Proton Experimental

Game launches flawlessly and remains stable when alt+tab'ing out of the window.

Steam overlay flickers if you open it in game but does function.

Settings:

4k medium, VSync off, no FSR gets me mid 60's fps.

4k medium, VSync off, FSR2 Quality gets me 80fps (with dips into low 70's).

(Default) 4k medium, VSync off, FSR2 with 50% resolution scale. In this configuration I get 100-120fps.

Unfortunately, the game does not have VRR so it locks to the monitors refresh rate (manually set to 120hz in my case).

As such the game does stutter when it dips in frames so you may want to target your 1% lows or avg fps to guarantee a smooth experience.

8/10

At medium the game does look good, although the sprites for fire could be better and have more bloom.

If they add VRR, and steadily work to optimize performance this could easily reach a 10/10.

view more: next ›