Hiby R3 Pro Portable Bluetooth DAP

[AlexxxAA85]

I'm having a serious "popping" issue lately with my R3 2022 during BT receiver mode. I'm guessing it's when the amp turns on. It happens in 2 different situations. The first is the first time you press play on any media. It can be sending my music from my phone, or watching media. The other situation is when I pause for too long. You can hear the background go off with a slight pop. And when you press play again it pops HARD.
It's as if it plays at max volume for a fraction of a second, then goes back to the volume set on the device. Not sure how long it has been going on, but most likely since I updated to the new firmware a couple of weeks ago. It seems like the popping is getting worse as the days go by. It gets louder. It seems to only be happening with the BT receiver mode.
Any advice?

 

[needletalk]

I'm having a serious "popping" issue lately with my R3 2022 during BT receiver mode. I'm guessing it's when the amp turns on. It happens in 2 different situations. The first is the first time you press play on any media. It can be sending my music from my phone, or watching media. The other situation is when I pause for too long. You can hear the background go off with a slight pop. And when you press play again it pops HARD.
It's as if it plays at max volume for a fraction of a second, then goes back to the volume set on the device. Not sure how long it has been going on, but most likely since I updated to the new firmware a couple of weeks ago. It seems like the popping is getting worse as the days go by. It gets louder. It seems to only be happening with the BT receiver mode.
Any advice?

I'm not sure but do you try to lock digital volume on your HIBY R3 PRO settings, maybe that helps, and you can control volume on your phone directly, popping is a know issue unfortunately on the bright side it seem that it's firmware related and fort a hardware issues so this may be corrected in an future update, hope this helps.

 

[newworld666]

I'm having a serious "popping" issue lately with my R3 2022 during BT receiver mode. I'm guessing it's when the amp turns on. It happens in 2 different situations. The first is the first time you press play on any media. It can be sending my music from my phone, or watching media. The other situation is when I pause for too long. You can hear the background go off with a slight pop. And when you press play again it pops HARD.
It's as if it plays at max volume for a fraction of a second, then goes back to the volume set on the device. Not sure how long it has been going on, but most likely since I updated to the new firmware a couple of weeks ago. It seems like the popping is getting worse as the days go by. It gets louder. It seems to only be happening with the BT receiver mode.
Any advice?

It's difficult to figure what happens in your case.
Actually, I don't have any issue similar to yours. I don't have, when pausing, any little background hiss or clicks when BT is activated or de-activated like I do have with iFi Go Blu or a Centrance M8V2.
But, I am using a different config than yours with the latest firmware on R3 Pro Saber => I use every night the R3 Pro Saber 2022 for sleeping in BT receiver mode (locked in LDAC 990kbps). The music is sent to the R3 Pro Saber 2022 by my android Smartphone Galaxy Z Fold 4 using either Qobuz or Neutron player (access to my Upnp Server) with PowerEQ activated with adapted PEQ profiles for my IEMs.
Depending on the genre of music I will listen, but sometimes I use a Sennheiser IE600 through the 2.5mm Balanced output, sometimes I use a little Soundmagic E11 through 3.5mm output.

 

[Virtuose]

Maybe 50 is on hexadecimal In the code as 32.and only under favorites playlists inside a playlist directory. I didn't saw the code yet I'm just speculating.

Because qobuz was added later i am now searching even in everything related to tidal, but there is no 50 track limit, maybe an old part of code. Here is that what i get for searching qobuz in the hiby player file in ghidra if you want to have a look at it.

 

[losber]

the 20000 limit as 4e20 in hex

It's not just find a hex pattern but you need to analyze disassembled code with understanding MIPS assembler. The 20000 tracks limit was found like this https://www.head-fi.org/threads/the...e-dac-r3-pro-on-sale-now.872288/post-14801401
There was found li $v0, 0x4E20 [loads immediate value into register $v0]

 

[losber]

I've just found that new Shanling M1s has the newest bluetooth module (Ampak AP6256) firmware. I mean the firmware file BCM4345C5.hcd It's located on /lib/firmware/BCM4345C5.hcd in R3Pro 2.2 firmware and on /firmware/bt_bcm/BCM4345C5.hcd in M1s 1.2 firmware.
I compared two files and here is noticeable
BCM4345C5 Ampak_CL1 UART 37.4 MHz BT 5.0 [Version: 1010.1018] - R3Pro
BCM4345C5 Ampak_CL1 UART 37.4 MHz BT 5.2 [Version: 1030.1058] - M1s
I'm not sure whether it's just a label or it means related advantages.
I manually replaced the file over adb and it works fine. Only one disadvantage that I have with new BT firmware is missing connect/disconnect report to BT earphones. I mean HiBy WU1 does not not play recorded word 'connected' / 'disconnected' but it actually connected/disconnected to R3Pro quickly. All physical remote buttons on HiBy WU1 works fine.
And I have other notice that HiBy's firmwares have outdated bluetooth stack (BlueZ) package and M1s has the latest BlueZ version.
Do HiBy's software engineers plan to update BT firmware and stack package?

 

[Joe Bloggs]

I've just found that new Shanling M1s has the newest bluetooth module (Ampak AP6256) firmware. I mean the firmware file BCM4345C5.hcd It's located on /lib/firmware/BCM4345C5.hcd in R3Pro 2.2 firmware and on /firmware/bt_bcm/BCM4345C5.hcd in M1s 1.2 firmware.
I compared two files and here is noticeable
BCM4345C5 Ampak_CL1 UART 37.4 MHz BT 5.0 [Version: 1010.1018] - R3Pro
BCM4345C5 Ampak_CL1 UART 37.4 MHz BT 5.2 [Version: 1030.1058] - M1s
I'm not sure whether it's just a label or it means related advantages.
I manually replaced the file over adb and it works fine. Only one disadvantage that I have with new BT firmware is missing connect/disconnect report to BT earphones. I mean HiBy WU1 does not not play recorded word 'connected' / 'disconnected' but it actually connected/disconnected to R3Pro quickly. All physical remote buttons on HiBy WU1 works fine.
And I have other notice that HiBy's firmwares have outdated bluetooth stack (BlueZ) package and M1s has the latest BlueZ version.
Do HiBy's software engineers plan to update BT firmware and stack package?

As you discovered, there are certain incompatibilities between the updated firmware version and the rest of the hardware / software, which while not game-breaking are annoying nonetheless. We currently do not plan to update this, as we don't find advantages related to Bluetooth for audio use.

Also it should be noted that we were not provided this particular firmware version by our chip vendor, which should mean that our version of the chip is not fully compatible with this version.

"Isn't it the same chip?" You ask. Well, it's like if nVidia releases a graphics chip, there are then numerous boards on the market bearing the chip, none actually made by nVidia...

 

[Virtuose]

It's not just find a hex pattern but you need to analyze disassembled code with understanding MIPS assembler. The 20000 tracks limit was found like this https://www.head-fi.org/threads/the...e-dac-r3-pro-on-sale-now.872288/post-14801401
There was found li $v0, 0x4E20 [loads immediate value into register $v0]

I understand. What about this: because there is no limit related to 50 or hex 0032 like you already checked, i see differences in the .view files in theme folder. If you take a playlist with less than 50 tracks, it feels like he wants to show more, so could it be the theme layout which is limiting the view of fav playlists? Just a theory because of some values are now different from 1.6 to 2.2. I changed those files, then the layout was very strange, had to factory reset....

 

[losber]

I understand. What about this: because there is no limit related to 50 or hex 0032 like you already checked, i see differences in the .view files in theme folder. If you take a playlist with less than 50 tracks, it feels like he wants to show more, so could it be the theme layout which is limiting the view of fav playlists? Just a theory because of some values are now different from 1.6 to 2.2. I changed those files, then the layout was very strange, had to factory reset....

I think it's not simple as checking database limit, it might be coded in API request, or directly related, and it's not as simple exception check. I found the references to Qobuz API 0.2 in disassembled pseudocode (actually it's from Theme editor/GUI simulator) and found similarities in several projects on Github (like this one )

Edit: it looks like I'm on the right way https://web.archive.org/web/20180611030533/https://github.com/Qobuz/api-documentation

Every methods returning albums, tracks, playlists, artists and subscribers collections accept pagination:

1. All collections are limited to 50 items by default. This can be overridden by passing a limit parameter. You can paginate through a collections by passing an offset parameter and incrementing it by the limit for each request.
2. Methods will return paginated collections structured this way:
   • items
   • offset
   • limit
   • total

 

[losber]

So it looks like a bug that probably related to incorrect pagination request favorite playlist content to Qobuz API.
Qobuz: My favorites -> Albums -> shows all 74 albums that it has [correct pagination]
Qobuz: My favorites -> Playlists -> My playlist - shows only 50 tracks from 120 tracks that it actually has [incorrect pagination]

 

[Doberman Joe]

Does this support m4b?

 

[losber]

Does this support m4b?

It can play m4b coded with AAC if you change file extension from .m4b to .aac
For example Future1.m4b needs to rename to Future1.aac
I've just tested, it works.

 

[raif71]

What about .m4a ?

 

[Doberman Joe]

It can play m4b coded with AAC if you change file extension from .m4b to .aac
For example Future1.m4b needs to rename to Future1.aac
I've just tested, it works.

Does it retain Chapters and where it left off?

 

[losber]

What about .m4a ?

Checked, it plays as is, no need to rename.