[SeanS]

For what it's worth, I've just tested LHDC on my old phone, a POCO F2 Pro. It has LHDC V3.

I can listen fine by setting the sample rate to 96 kHz, the bits per sample to 24 bits and the LHDC playback quality to Best Effort (auto bit rate). Everything else stutters on these settings.

If I will change the sample rate to 44.1 kHz, I can set it to Balanced (500/560 kbps) without stuttering.

I cannot listen to 900 kbps under any setting, it's cutting off. I think this is expected, though, since my old POCO F2 Pro does not support Snapdragon sound.

Hey, @Nick24JJ, thanks for confirming it's not the Go Pods, must be the LHDC One in combination with my source that is limiting my config to 24/48.

 

[toomasg]

Hey, @Nick24JJ, thanks for confirming it's not the Go Pods, must be the LHDC One in combination with my source that is limiting my config to 24/48.

If you have any old android dap which can output usb audio it should be giving a reliable true to the content output.

 

[SeanS]

Hey, @Nick24JJ, thanks for confirming it's not the Go Pods, must be the LHDC One in combination with my source that is limiting my config to 24/48.

The more I'm thinking about this, regarding the connection to the Go Pods, the more I think the source device the "LHDC One" is connected to doesn't influence the connection between the "LHDC One" and the Go Pods. The source would only affect the content passed to the "LHDC One". The BT connection to the Go Pods is completely offloaded to the "LHDC One". So logic brings me back to my original conclusion that the combination of "LHDC One" and Go Pods can only connect at 24bit 48Khz LHDC BT.

Another example to make my point: When I make a BT connection between the Go Pods and the s20+ using 32bit 96Khz LDAC, the BT connection remains 32bit 96Khz LDAC whether the content I'm playing in Tidal is 16bit 44.1Khz or 24bit 192Khz.

 

[Nick24JJ]

The more I'm thinking about this, regarding the connection to the Go Pods, the more I think the source device the "LHDC One" is connected to doesn't influence the connection between the "LHDC One" and the Go Pods. The source would only affect the content passed to the "LHDC One". The BT connection to the Go Pods is completely offloaded to the "LHDC One". So logic brings me back to my original conclusion that the combination of "LHDC One" and Go Pods can only connect at 24bit 48Khz LHDC BT.

Another example to make my point: When I make a BT connection between the Go Pods and the s20+ using 32bit 96Khz LDAC, the BT connection remains 32bit 96Khz LDAC whether the content I'm playing in Tidal is 16bit 44.1Khz or 24bit 192Khz.

No worries

If you will consider that we are in 2024 and there's no DAP with Qualcomm Snapdragon 8 or above CPU, so none of them can utilize GO Pod's full potential, what can you expect from the LHDC One...?

Just enjoy your music, no worries

 

[toomasg]

The more I'm thinking about this, regarding the connection to the Go Pods, the more I think the source device the "LHDC One" is connected to doesn't influence the connection between the "LHDC One" and the Go Pods. The source would only affect the content passed to the "LHDC One". The BT connection to the Go Pods is completely offloaded to the "LHDC One". So logic brings me back to my original conclusion that the combination of "LHDC One" and Go Pods can only connect at 24bit 48Khz LHDC BT.

Another example to make my point: When I make a BT connection between the Go Pods and the s20+ using 32bit 96Khz LDAC, the BT connection remains 32bit 96Khz LDAC whether the content I'm playing in Tidal is 16bit 44.1Khz or 24bit 192Khz.

You're making a bit farfetched assumption that s20+ with LDAC behave exactly the same as LHDC One with LHDC. Why not just test it with different sources instead of making assumptions?

 

[SeanS]

You're making a bit farfetched assumption that s20+ with LDAC behave exactly the same as LHDC One with LHDC. Why not just test it with different sources instead of making assumptions?

I have two types of sources: multiple PCs and the s20+. I have tried 2 Windows 10 and a Windows 11 and it always connects at 24/48.

My reasoning is based on the manual excerpt I posted earlier: The BT connection is between the Go Pods and the LHDC One, and the connection is supposed to be negotiated based on the capabilities of the BT device (in my case the Go Pods), not the source. The manual states that the LHDC One isn’t controlled or limited by the source device. Since Nick proved that the Go Pods can connect to another BT transmitter at higher bit rates using the LHDC codec, then it must be that LHDC One and the GO Pod are failing to negotiate a better connection—for some unknown reason—than 24/48. Another thing to prove this point: I am able to establish a BT 24/48 LHDC connection between the Go Pods and the LHDC One with only power to the LHDC One, no source even connected, just powered with a usb cable from a power brick.

The LHDC One is just a BT transmitter that can do LHDC. Even though it is connected by USB, as far as the source is concerned, the source device has no more control over the LHDC One than if the source was connected to the LHDC One by an optical spdif connection.

@iFi audio I’m curious which versions of LHDC are supported with Go Pods? V3, V4, etc

The LHDC One supports 3, 4, and 5

 

[ssantan2]

One thing I find very annoying is every time I take the pod out, adjust the volume to my liking, which I prefer to have some level indicator by the way (Fiio control app), put it back to the case. Next time I take them out, I have to readjust the volume level blindly all over again. I wonder if anyone else experience this.

Did you ever get this resolved. I just got a pair and this is really annoying and shouldn't be an issue for a product that costs this much. I'm also on the latest firmware

 

[iFi audio]

I have two types of sources: multiple PCs and the s20+. I have tried 2 Windows 10 and a Windows 11 and it always connects at 24/48.

My reasoning is based on the manual excerpt I posted earlier: The BT connection is between the Go Pods and the LHDC One, and the connection is supposed to be negotiated based on the capabilities of the BT device (in my case the Go Pods), not the source. The manual states that the LHDC One isn’t controlled or limited by the source device. Since Nick proved that the Go Pods can connect to another BT transmitter at higher bit rates using the LHDC codec, then it must be that LHDC One and the GO Pod are failing to negotiate a better connection—for some unknown reason—than 24/48. Another thing to prove this point: I am able to establish a BT 24/48 LHDC connection between the Go Pods and the LHDC One with only power to the LHDC One, no source even connected, just powered with a usb cable from a power brick.

The LHDC One is just a BT transmitter that can do LHDC. Even though it is connected by USB, as far as the source is concerned, the source device has no more control over the LHDC One than if the source was connected to the LHDC One by an optical spdif connection.

@iFi audio I’m curious which versions of LHDC are supported with Go Pods? V3, V4, etc

The LHDC One supports 3, 4, and 5

I have asked this for you as well.

Cheers!!

 

[ssantan2]

Did you ever get this resolved. I just got a pair and this is really annoying and shouldn't be an issue for a product that costs this much. I'm also on the latest firmware

looping in @iFi audio cause this seems like a bug?

 

[iFi audio]

looping in @iFi audio cause this seems like a bug?

I was waiting to hear from a few more folks on how this works for them, and the particular phone they use.

For the most part, I use my Pods mostly with an iPhone 11 and do not experience this issue. If it is indeed a bug, or acting in the extreme volume parameters I would make an inquiry of our support folks, and let them know the Model of the Phone, Android version, and other details relevant to your situation.

I could be wrong but I have not heard a seen a ton of posts on this direct issue, so it would be best to report it.

https://support.ifi-audio.com/

Cheers!!

 

[dkjh]

I was waiting to hear from a few more folks on how this works for them, and the particular phone they use.

For the most part, I use my Pods mostly with an iPhone 11 and do not experience this issue. If it is indeed a bug, or acting in the extreme volume parameters I would make an inquiry of our support folks, and let them know the Model of the Phone, Android version, and other details relevant to your situation.

I could be wrong but I have not heard a seen a ton of posts on this direct issue, so it would be best to report it.

https://support.ifi-audio.com/

Cheers!!

I understand that we can only listen up to 320kpbs using IPhone with GoPod. Is there a way we can listen to higher bit rate with IPhone?

 

[ssantan2]

I was waiting to hear from a few more folks on how this works for them, and the particular phone they use.

For the most part, I use my Pods mostly with an iPhone 11 and do not experience this issue. If it is indeed a bug, or acting in the extreme volume parameters I would make an inquiry of our support folks, and let them know the Model of the Phone, Android version, and other details relevant to your situation.

I could be wrong but I have not heard a seen a ton of posts on this direct issue, so it would be best to report it.

https://support.ifi-audio.com/

Cheers!!

It only happens when I disable absolute volume on android. I'll file a support ticket

 

[iFi audio]

I understand that we can only listen up to 320kpbs using IPhone with GoPod. Is there a way we can listen to higher bit rate with IPhone?

Not that I am aware of at the moment, however, the discussion preceding this was related to a product called LHDC One which has a higher rate and is an attachment you add to a USB C port (the Newest iPhone has this) to transmit a higher bitrate, I have not tried it. Still, I am sure folks will be giving it a go.

At the moment there is a push for higher bitrates for Bluetooth overall, but how you get there with an older device is a bit convoluted at this time.

I am happy with my GPDs and my iPhone as well as as an Android phone I have that uses LDAC, both in their native forms. That is just my opinion and I completely understand folks wanting to squeeze every bit out of any product, it's what we do in this hobby, lol

Cheers!!

 

[ecouteurifi]

Did you ever get this resolved. I just got a pair and this is really annoying and shouldn't be an issue for a product that costs this much. I'm also on the latest firmware

I totally agree with you here.
For a high end product the volume doesn’t stay put where I set it especially when there is no level indicator either is definitely annoyed. I have to adjust based on feeling. The next day will be totally different as my music library is not normalized. Unfortunately, as of today, I haven’t received any feedback / discussion on this subject. It seems that other users are not affected by this except you and I. Anyway, I sincerely hope that this can be implemented in the next Gaiia or an official Android app. As a result, I end up using more the Fiio utws5 instead which support ldac, has stable connection, no drop out and sounds pretty close (80%), imo.

 

[iFi audio]

I totally agree with you here.
For a high end product the volume doesn’t stay put where I set it especially when there is no level indicator either is definitely annoyed. I have to adjust based on feeling. The next day will be totally different as my music library is not normalized. Unfortunately, as of today, I haven’t received any feedback / discussion on this subject. It seems that other users are not affected by this except you and I. Anyway, I sincerely hope that this can be implemented in the next Gaiia or an official Android app. As a result, I end up using more the Fiio utws5 instead which support ldac, has stable connection, no drop out and sounds pretty close (80%), imo.

I will pass this on to those in charge of it. Volume issue and wish for something to be added to the GAIA app.

It is for sure a suggestion some folks may like (Volume indicator) so good thing to mention. Some will want this, Some won't, but it's at least worth a mention.

Thanks!!

Cheers!!