Going fully Wireless IEMs. Too soon? Or are we there yet?
Feb 7, 2023 at 12:45 PM Post #50,896 of 62,408
I see azla has a sedna max specific for them. But they aren't cheap especially if picking the mixed discount up as I don't know if I would need medium or ML or large.

I find the Azla SednaEarfit Max works best for me and use them on my GB2P & APP2. Unfortunately, no matter how many of us reply you'd just have to try and see for yourself.
 
Feb 7, 2023 at 3:08 PM Post #50,900 of 62,408
I don't know what you are using as source to compare the two TWS ?
But, if it's an android smartphone like Samsung without Apx Adaptive codec, the differences you describe are very similar to the differences I can get when I switch "on the fly" in a A/B direct comparison with an android app (Bluetooth Codec Changer) from LDAC set at audio priority at 990kps to AAC 16/44 codec with a Bluetooth Receiver like the 1000XM4 is able to do => basically AAC is already quite satisfying for sound quality but when we switch to AAC from LDAC in full audio mode, very often we get exactly what you wrote.. not that bad, but rather clearly better with the proper LDAC Codec.
So maybe the Noble with an Aptx Adaptive codec, it should be a different story and maybe the 1000xm4 could be even behind ? though 1000xm4 don't handle Aptx Adaptive.

NB: If LDAC is forced to a 16/44 mode (via a profile) => AAC clearly offers a far better sound quality by a huge margin.. I would even say LDAC in 16/44 mode is a real disaster with my android DAP and smartphones

Ohh interesting. My main sources are my M1 Macbook and iPhone 14. I know Apple (at least on the Macbook) dropped AptX recently and left us with AAC. Off topic a bit here, but I looked through the console when I connect with the Noble Mystique and Sony 1000xm4 and the results actually suggest that the Sony gets shafted.

On BT connection with Noble Mystique:
Code:
A2DP configured at 44.1 KHz. Codec: AAC-LC, VBR max: 256 kbps. 1 frames * (12+744) bytes = 756 per RTP (max=879) every 23.22 ms

ACMP4AACBaseEncoder.cpp:650   (0x125244440) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 1, bitrate = 128000, quality (complexity) = 64, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 0 (bits), packetBitSizeMin = 0 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0

ACMP4AACBaseEncoder.cpp:650   (0x125244440) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 3, bitrate = 192000, quality (complexity) = 32, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 5952 (bits), packetBitSizeMin = 256 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0

On BT connection with Sony 1000xm4:
Code:
A2DP configured at 44.1 KHz. Codec: AAC-LC, VBR max: 192 kbps. 1 frames * (12+558) bytes = 570 per RTP (max=656) every 23.22 ms

ACMP4AACBaseEncoder.cpp:650   (0x124b34e40) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 1, bitrate = 128000, quality (complexity) = 64, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 0 (bits), packetBitSizeMin = 0 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0

ACMP4AACBaseEncoder.cpp:650   (0x124b34e40) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 3, bitrate = 144000, quality (complexity) = 32, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 4464 (bits), packetBitSizeMin = 256 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0
 
Feb 7, 2023 at 3:21 PM Post #50,901 of 62,408
Ohh interesting. My main sources are my M1 Macbook and iPhone 14. I know Apple (at least on the Macbook) dropped AptX recently and left us with AAC. Off topic a bit here, but I looked through the console when I connect with the Noble Mystique and Sony 1000xm4 and the results actually suggest that the Sony gets shafted.

On BT connection with Noble Mystique:
Code:
A2DP configured at 44.1 KHz. Codec: AAC-LC, VBR max: 256 kbps. 1 frames * (12+744) bytes = 756 per RTP (max=879) every 23.22 ms

ACMP4AACBaseEncoder.cpp:650   (0x125244440) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 1, bitrate = 128000, quality (complexity) = 64, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 0 (bits), packetBitSizeMin = 0 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0

ACMP4AACBaseEncoder.cpp:650   (0x125244440) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 3, bitrate = 192000, quality (complexity) = 32, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 5952 (bits), packetBitSizeMin = 256 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0

On BT connection with Sony 1000xm4:
Code:
A2DP configured at 44.1 KHz. Codec: AAC-LC, VBR max: 192 kbps. 1 frames * (12+558) bytes = 570 per RTP (max=656) every 23.22 ms

ACMP4AACBaseEncoder.cpp:650   (0x124b34e40) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 1, bitrate = 128000, quality (complexity) = 64, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 0 (bits), packetBitSizeMin = 0 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0

ACMP4AACBaseEncoder.cpp:650   (0x124b34e40) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 3, bitrate = 144000, quality (complexity) = 32, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 4464 (bits), packetBitSizeMin = 256 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0

Ok.. because you are with AAC codec in both situations, it means Sound Quality is probably even not really fully optimized with the Sony 1000XM..
So, I am bit surprised the Noble Mystique doesn't sound better for you than the Sony.
 
Feb 7, 2023 at 3:31 PM Post #50,902 of 62,408
YW. If you were to drop $400 on an adapter plus IEM (a) is it doable? and (b) what would you (err me), get? If $400 isn't enough, what is? How is the fit on the adapters?
Right now I'm in love with the Campfire Andromeda 2020 on the Shure TW2 Gen 2 and then the Thieaudio Clairvoyance on the Fostex TW2C. But I'm dabbling (again) with the UTWS5 and the Moondrop Blessing 2. Considering upgrading the MB2 to something more, but the latter is a well regarded IEM and I had forgotten how good it actually was. That setup costs around 320+140. Little more than what you want to pay. But to answer your question, YES, it's very doable. Personally, knowing what you like, I think that Shure adapter is best for calls, transparency etc, but you're bound to an MMCX connector. Shure IEMs are great, but once you look beyond them, you may never use them again. The Campfire IEMs just blew away the Shure SE846s I was using. I've tried the adapters for 2 Pin on the Shure and they just didn't work great for me. They make the TW2 adapter arm longer and messes with the fit, again, for me. The Fostex adapter is great. I got a good deal on digitaldjgear and I really do prefer the sound they put out to the Fiio. But, if you use those and want a 2pin, you'd need the 2pin modular arm. https://digitaldjgear.com/product/cable-for-tm-2-ciem-2-pin-connector/ The fit of some of the IEMs, especially the 3d printed Moondrops or Thieaudios are similar to the Noble Fokus gang, but some better. I slot my Clairvoyance and the Blessing 2 in and they fit like custom molded buds. Granted it took me a while to find my favorite combos. Took a while and I'm sure I'll keep rotating in time.

Bottom line again is that yes you can do it.
 
Feb 7, 2023 at 5:31 PM Post #50,905 of 62,408
Two new Phillips headphones, one is a tws. Both with Bluetooth 5.3 and LC3.

https://www.pocket-lint.com/philips-announces-new-fidelio-l4-t2-headphones/
I like their design
1675809041412.png


Coming with dual drivers, a graphene dynamic and an armature. Sorry, a 'specially designed armature'.
 
Last edited:
Feb 7, 2023 at 5:59 PM Post #50,906 of 62,408
Noob question, what does distortion sound like in regards to tws? I've noticed one of the new things is trying to achieve 'ultra-low distortion' or distortion of 0.0016%. I know what regular distortion sounds like but have never noticed anyone in reviews mention it nor ever heard any kind of distortion in sound on any properly connected device. Like I assume the Earfun Free Pro 2 or Fiil T1X have some kind of distortion over the ZE8000, but I can't pick it up.
 
Feb 7, 2023 at 9:47 PM Post #50,907 of 62,408
Ohh interesting. My main sources are my M1 Macbook and iPhone 14. I know Apple (at least on the Macbook) dropped AptX recently and left us with AAC. Off topic a bit here, but I looked through the console when I connect with the Noble Mystique and Sony 1000xm4 and the results actually suggest that the Sony gets shafted.

On BT connection with Noble Mystique:
Code:
A2DP configured at 44.1 KHz. Codec: AAC-LC, VBR max: 256 kbps. 1 frames * (12+744) bytes = 756 per RTP (max=879) every 23.22 ms

ACMP4AACBaseEncoder.cpp:650   (0x125244440) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 1, bitrate = 128000, quality (complexity) = 64, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 0 (bits), packetBitSizeMin = 0 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0

ACMP4AACBaseEncoder.cpp:650   (0x125244440) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 3, bitrate = 192000, quality (complexity) = 32, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 5952 (bits), packetBitSizeMin = 256 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0

On BT connection with Sony 1000xm4:
Code:
A2DP configured at 44.1 KHz. Codec: AAC-LC, VBR max: 192 kbps. 1 frames * (12+558) bytes = 570 per RTP (max=656) every 23.22 ms

ACMP4AACBaseEncoder.cpp:650   (0x124b34e40) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 1, bitrate = 128000, quality (complexity) = 64, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 0 (bits), packetBitSizeMin = 0 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0

ACMP4AACBaseEncoder.cpp:650   (0x124b34e40) @@@@ 'aac ' encoder configuration: srIn = 44100, srOut = 44100, chans = 2, bitRateFormat = 3, bitrate = 144000, quality (complexity) = 32, VBRQ = -1, speechOptimization = 0, packetSizeLimit = 4464 (bits), packetBitSizeMin = 256 (bits), mMaxPacketSize = 1536 (bytes), userBandwidth = 0, delayMode = 0, mCodecDelay = 2112, drcConfiguration = 0, mPrePostFillMask = 0x0
Looks like the XM4 has some radio issue taking the Bluetooth radio bandwidth down, hence the encoder is encoding at a lower bandwidth. i can’t tell what the radio problem is just from this bit of the log….
 
Feb 8, 2023 at 5:52 AM Post #50,908 of 62,408
Noob question, what does distortion sound like in regards to tws? I've noticed one of the new things is trying to achieve 'ultra-low distortion' or distortion of 0.0016%. I know what regular distortion sounds like but have never noticed anyone in reviews mention it nor ever heard any kind of distortion in sound on any properly connected device. Like I assume the Earfun Free Pro 2 or Fiil T1X have some kind of distortion over the ZE8000, but I can't pick it up.
Maybe it's related to distortion at high db
 
Feb 8, 2023 at 6:00 AM Post #50,909 of 62,408
Honestly, I effing hate FedEx.
So yesterday, my Fokus Mystiques were "delayed" and the tracking said "more information at 1PM", which of course didn't happen. Yet I could totally see that they were already in my country and everything... Then it changed back to "On time", which of course is bull because the original estimated date was yesterday.

So i wrote to their chat support and he only said, direct quote:
"Shipment is delayed, delay is caused by our operational issues. I will ask for delivery as quick as possible which will be tomorrow, Im sorry for situation and delay"

Seriously though. I'm FINE with waiting two more days, just have a functional tracking that can say "DELAYED DUE TO x - ESTIMATED DATE OF DELIVERY IS NOW <insert date>". I don't want to have to stay at home for several days in case they decided to deliver the package... now he told me that they were going to deliver it tomorrow, great. But why did I have to turn to their chat to know that? This is not my first experience with FedEx having completely broken tracking.
 
Feb 8, 2023 at 10:14 AM Post #50,910 of 62,408
Today, I got some used Woody JVC/Victor HA-FW1000T ........ I will probably have to do some more rolling tips before finding the optimized conf for my ears and sound quality preferred taste...
But, as it is right now out of the box and switching for a pair of hours between the woody HA-FW1000T, the Galaxy Buds2 Pro and the Jabra Elite 7 Pro => the HA-FW1000T seems :
-> to be with an impressive extension response in the low and ultra low frequencies and still less "muddy" than the Galaxy Buds2 Pro, the Jabra Elite 7 Pro are maybe a bit limited in "good impacts" with lows, though it handles also ultra low frequencies.
-> really less spicy than the Buds2 pro, I think high-mids and high frequency feels, in a nearly instant A/B comparison, even a bit muffled compared the two others TWS, but after 10 minutes listening, the JVC is maybe nearer my closed headphone feelings and can be perceived as a bit more natural if not more comfortable for long listening sessions.

So I would say that it's a rather nice (if not very good) first impression concerning sound quality "as it is" without PEQ... it's a bit more mixed impression concerning user interface (touch commands), lack of any android app, too light strength of ANC, probably some annoying drivers flex, no aptx HD or LDAC.
Though, I will confirm it later, it seems switching between AAC & APTX or activating their K2 enhancement, has some real effects on the sound quality.
I stop writing while listening the new Smashing Pumkins Album after spending a some hours with Manu Katché, and there is clearly a smile on my face due to the natural SQ available with the HA-FW1000T.
 
Last edited:

Users who are viewing this thread

Back
Top