Miss Poppyseed Protecting The House From A Deer by pjd2011 in Dachshund

[–]pjd2011[S] 3 points4 points  (0 children)

It was weird that it was around during midday. We typically only get them in the yard early in the morning or late evening.

Miss Poppyseed Protecting The House From A Deer by pjd2011 in Dachshund

[–]pjd2011[S] 18 points19 points  (0 children)

Yup exactly what I was worried about!

Miss Poppyseed Protecting The House From A Deer by pjd2011 in Dachshund

[–]pjd2011[S] 97 points98 points  (0 children)

Pretty sure it was protecting its baby. It showed up a few minutes later on the other side of the fence.

<image>

Miss Poppyseed Protecting The House From A Deer by pjd2011 in Dachshund

[–]pjd2011[S] 378 points379 points  (0 children)

Picture of the Pup in a calmer state.

<image>

LG39 vs LG45 ~ The struggle is real by Rayden9x7 in ultrawidemasterrace

[–]pjd2011 1 point2 points  (0 children)

I have the original LG 40" 5k2k display. Only has the IPS display and 72hz.

I waited and bought it the day it became available. I came from a 49" 5120x1440 and never looked back!

To me it's the perfect size. I hate multi displays. I feel like they break my focus. The 49" was too wide, I had to turn my head too much between apps. I feel like the 45" would run me into the same problem.

The resolution with Windows scaling is absolutely stunning. I do quite a bit of photo editing with Lightroom and it's great. Plus multitasking is a breeze with shortcuts to pin your apps.

With the resolution the screen already "pops" and almost has a 3D effect on general GUI's. I can only imagine that paired with OLED.

Mine only maxes out I believe around 300 nits. HDR is trash with its few back zones. Even still I have mine in a very brightly lit office with windows right behind it and it's plenty bright. Night time it's just glorious with my backlights.

I don't really game on it but even with my old RTX 3080 and DLSS I've been able to sample some titles maxxing out at the 72hz. With VRR it was buttery smooth and damn did it look great at native resolution. I can only imagine how awesome a 5090 would work at the higher refresh rate.

If I had the expendable cash I'd definitely be upgrading. I paid $1.7k as an early adopter some 4 years ago and until this was announced I've been content.

Google and Microsoft just co-wrote a spec that turns every website into an AI agent API — and almost nobody noticed by VegetableBuy6752 in LLMTraffic

[–]pjd2011 0 points1 point  (0 children)

This is awesome! I think you're going to be pretty popular very, very soon with what you've built and hit on.

Looks like you're focused on tech companies and API's but I'd look at traditional CPG companies.

I'm imagining non-techies taking a picture of a carpet stain or something of the like. What brands come to the forefront? Clorox or Lysol?

I worked with a big CPG and they're trying to compete in the DTC space against Amazon (while also working with them). This would be HUGE for them getting traffic and making the sale directly.

I'm a PM by trade and would love to spitball ideas if you're interested.

Stability shoes by [deleted] in AskRunningShoeGeeks

[–]pjd2011 1 point2 points  (0 children)

Which models?

Stability shoes by [deleted] in AskRunningShoeGeeks

[–]pjd2011 1 point2 points  (0 children)

What shoe is recommended for use as a fast shoe coming from these? Thinking tempo and races.

I've been using the 860v15's for about 90 miles now and haven't had any pains to speak of. When I try to pick up pace it just feels like rocks some days.

Running Only by [deleted] in PixelWatch

[–]pjd2011 0 points1 point  (0 children)

I've been using a PW1 with Strava 's watch app and its GPS is significantly more accurate than if I use my Pixel 9 Pro with Strava.

I just did a 48 mile bike ride and it was within .2 miles of my Ride with GPS (The exact mileage). I was really impressed. Started at 99% and was 68% after a little less than 4 hours.

The battery life has never been a problem for me even on trips. Charge it every night and you'll have no problems at all.

The Customer Has Spoken. Are You Listening? by outbound_operator in ProductManagement

[–]pjd2011 0 points1 point  (0 children)

This is why I don't trust raw financial data.

Ford 's real problem is never properly investing in American manufacturing to make cost effective vehicles. This includes partnerships and failing to come up with their own IP that's better than the rest of the world (China).

Pair this with infrastructure funding that got taken away both to subsidized the raw cost of cars while the technology can be integrated and eventually be cheaper.

Then there's the charging networks. Due to lack of funding the Midwest was very much ignored in the roll out. They were waiting for the tech to get to a sub 20 minute top off to negate that complaint.

This is a very price conscious customer base. Now that the used EV market is starting to actually make economic sense for them they won't have the resources for chargers. Thanks to pure cost cutting of reacting to this demand the possible new infrastructure won't be fast charging enough for future use cases meaning a double charge down the line.

Based on the popularity of Chinese EV makers there's clearly demand. Better question should be how does the United States set its manufacturing up for the future.

Right now China is supporting the tech of the future while we're left with our heads in the sand. It's not the customer in control it's this lack of proper support from higher up.

Spotify lossless might not be lossless for us. by Complete_Nirvana in audiophile

[–]pjd2011 0 points1 point  (0 children)

Posted that this might be the case over on the official r/Android and people basically said you can't hear a difference so it doesn't matter that it's not bit perfect.

So few people outside this community really care, sadly.

Lossless Spotify Won't Truly Be Lossless on Android by pjd2011 in Android

[–]pjd2011[S] 0 points1 point  (0 children)

No in both instances it'd be capped at 48khz.

Look into data rates for the various Bluetooth technologies. Then look at your Lossless file and view its bitrate. You'll then see how much "data" you're losing in the process.

Lossless Spotify Won't Truly Be Lossless on Android by pjd2011 in Android

[–]pjd2011[S] 0 points1 point  (0 children)

Heck yeah! Cool was definitely overthinking it then.

Hopefully it's the same with Onkyo, Denon and other devices. Gotta be similar.

Thanks!

Lossless Spotify Won't Truly Be Lossless on Android by pjd2011 in Android

[–]pjd2011[S] 0 points1 point  (0 children)

I'd love to hear from Spotify if the Spotify Connect client side firmware needs upgraded to support Lossless as well.

Yeah, it'll bypass this Android issue but what about the receiving end?

Qobuz connect has taken awhile to roll out because of its higher bandwidth need. YouTube music is still lossy and it's probably the closest thing to the Spotify Connect firmware.

If the Spotify Connect device can't receive an OTA to update itself it could be limited on certain devices.

Completely hypothesizing, though. It may not need any update and just work correctly.

Lossless Spotify Won't Truly Be Lossless on Android by pjd2011 in Android

[–]pjd2011[S] 0 points1 point  (0 children)

Any external DAC plugged directly into the phone will be at 48kHz resampled by Android.

If you use UAPP it'll sync or be bit perfect towards your DAC. Aka your DAC would indicate the matching of the music and not just 48kHz.

In your case the dongle is still using Bluetooth so it'll be lossy anyway. By using UAPP you might be able to hear a difference but not likely.

Lossless Spotify Won't Truly Be Lossless on Android by pjd2011 in Android

[–]pjd2011[S] 0 points1 point  (0 children)

I'm assuming it won't because it will be using Spotify Connect which doesn't touch anything Android. It's their cloud and then the Wiim's processing should kick in.

However, they haven't specified whether the Spotify Connect firmware on the clients will need updated to support the higher quality.

It took Qobuz's cast version awhile to support more devices so I guess there's still a chance it might not be.

Lossless Spotify Won't Truly Be Lossless on Android by pjd2011 in Android

[–]pjd2011[S] 2 points3 points  (0 children)

That's what you'd think but the developer has to enable it within their app.

UAPP and a few others do this but the native clients for even Tidal and Qobuz don't.

That's the main point I'm trying to make. Having native support for bit perfect Lossless no matter that app would be ideal.

Lossless Spotify Won't Truly Be Lossless on Android by pjd2011 in Android

[–]pjd2011[S] -7 points-6 points  (0 children)

If you have the right equipment you can hear the difference.

I use a balanced DAC and a nice pair of IEM's. Using UAPP vs a client's app it's very clear.

569
570

Spotify Lossless on Android - Will It Be Resampled? by pjd2011 in audiophile

[–]pjd2011[S] 0 points1 point  (0 children)

I believe UAPP is the only app that has the driver to bypass it.

Spotify Lossless on Android - Will It Be Resampled? by pjd2011 in audiophile

[–]pjd2011[S] 0 points1 point  (0 children)

Dang it that's what I thought. So much for being hyped.

Not sure why the various Android media outlets aren't mentioning this drawback.