Jump to content
Computer Audiophile


  • Content count

  • Joined

  • Last visited


About Cebolla

  • Rank
    Cepa Computensis Musicalis

Recent Profile Visitors

7,846 profile views
  1. Nope, Sonore says I have an IP conflict. Are you certain Sonore said that? IP conflicts are normally quite straight forward to sort out. My suspicion is that it's actually an issue with the network's management of IGMP multicast, used by the A+ and the microRendu to discover each other as UPnP supporting devices. One very common cause of this is a wireless router misbehaving by preventing IGMP multicast packets from being forwarded between the wired and wireless portions of the network. This explains why the suggestion of making your UPnP devices either all wired or all wireless, should then allow them to discover each other. This problem can be solved in some routers by configuration setting change: disabling IGMP snooping and/or enabling multicast forwarding. If this isn't possible then keeping the misbehaving router will require you to go through the hassle of making your UPnP devices either all wired or all wireless. In which case it might be more practical/cost effective to change the router for one that does work properly with IGMP multicast discovery. What router are you using?
  2. No need, as you've had reponses straight from two distinguished OpenHome device developers' mouths! However, just in case it's not clear, support of any of the OpenHome provided online/cloud streaming services is not compulsory for an OpenHome renderer and therefore you cannot assume that these (extra) services will be provided.
  3. Controlling Foobar2000 via upnp using another PC

    Ah, ok - in which case as you are now using normal UPnP media server/UPnP renderer streaming setup, you should be able to control the playback with a Windows UPnP controller on the laptop. Couldn't you find a suitable Windows UPnP controller, so had to use an Android one via the Android emulator? Did you try the Windows version of the Linn Kazoo OpenHome (aka UPnP with Linn extensions) controller (so requires the BubbleUPnP Server to provide the OpenHome support to work with fb2k's standard UPnP supporting foo_upnp renderer), as described by @jcn3's post?
  4. Tidal sucks

    Ok, looks like I misinterpreted your post. So both the Aries Mini & Audirvana are in fact playing 320kbps for the first track and 96kbps for the rest of the tracks - therefore no difference here. Hence, the only difference between the Aries Mini and Audirvana is Audirvana's problem of not supporting AACplus. Therefore Audirvana decodes TIDAL's 96kbps 44.1kHz AACplus track streams as if they were standard AAC, so produces the fallback 22.05kHz sample rate, instead of the full 44.1kHz that the AACplus supporting Aries Mini produces. No new news here, after all! I thought in that post you were referring to the 'LoFi' album as an example of those ones that you mentioned in your earlier post: I understood this to mean that for some 'LoFi' albums the Aries Mini is displaying 96kbps instead of the 320kbps that Audirvana is displaying for the same album tracks. I assumed the "22.0 kHz" was a typo & you actually meant to write 44.1 kHz - since (unlike Audirvana), the Aries Mini supports AACplus, so shouldn't be displaying 22.0 kHz for the 96 kbps streams. Did I understand this correctly? If so, can you give us some examples of those albums (as I asked for earlier)?
  5. Tidal sucks

    UK account only has the lossy version too. @wklie, did you try the lossy version (https://listen.tidal.com/album/15563242 , Released 1985-01-01, Length 44:05) with the Lumin and notice the same difference with the first track?
  6. Tidal sucks

    I have not been able to stream anything other 320 kbps AAC for the first track and 96kbps HE-AAC for the rest of the tracks, for all devices that I've tried with this album - so similar to Audirvana. Well, all devices apart from the ickstream/LMS platform, of course - which streams all of the album's tracks as 320kbps MP3! However, I did notice an odd thing when the UPnP streaming devices were used with the BubbleUPnP Android app. The device's own display indicated receiving as mentioned above, but the BubbleUPnP Android app indicated 96kbps AAC for all tracks, including the first. Stranger still, the BubbleUPnP app's display momentarily displayed 320kbps AAC for the first track when it started playing it, but then very quickly changed to display 96kbps AAC as the track carried on playing. Could the Aries Mini and its Lightning DS controller app be doing the same thing - so for the first track, theAries Mini is streaming 320 kbps AAC, but its controller app is incorrectly displaying 96kbps AAC? Also, do you have any other examples of albums where the Aries Mini's controller app displays 96kbps AAC instead of the 320kbps AAC displayed by Audirvana?
  7. Tidal sucks

    You are assuming that the imposition of the low quality 96kbps HE-AAC streams is a deliberate act by TIDAL. There's also the possibility that there's some sort of bug in the system. It would explain the apparent random nature of the problem, where only some of an artist's lossy albums are affected, or, better still, where only some of the tracks of a lossy album have been affected. Plus, why when an artist does have the same album also available in a lossless format, is that lossless album never affected when its lossy equivalent is affected? Don't forget both the TIDAL provided software and some third party applications provide the following options (where appropriate) to allow the user to manually configure the quality of the stream provided by TIDAL's online server: Masters - streams up to 24/48kHz FLAC or ALAC Hi-Fi - streams up to 16/44.1kHz FLAC or ALAC High - streams up to 320kbps AAC-LC Standard - streams only 96kbps HE-AAC So any Album track, be it originally lossless or lossy, can already be set to stream in TIDAL's so called Standard quality, ie, 96kbps HE-AAC - no need for TIDAL to employ an army of workers to downgrade the files!
  8. Tidal sucks

    Indeed - I didn't want to mention that it also occurs with TIDAL Premium accounts, just in case it would confuse some as to the underlying problem, ie: a substancial proportion of the lossy album collection in TIDAL's catalogue have recently been forced by TIDAL's online server to stream in pathetic 96kbps HE-ACC (more usually used by bandwidth challenged internet radio stations), instead of the expected and far greater quality (but of course still lossy) 320kbps AAC-LC. This has been found with both TIDAL HiFi accounts (via the HIGH or HIFI or MASTERS streaming quality connection) and TIDAL Premium accounts (via the HIGH streaming quality connection), regardless of country of origin. Country of origin of the TIDAL account only appears to determine whether the user has access to a particular album in TIDAL's catalogue, be it lossy or lossless in origin. The problem has also been found with all devices/platforms mentioned as tested thus far in this thread, with the exception of the ickstream/LMS platfrom (for Squeezebox type streamers) special case (see below). There is also the related issue that a couple of devices/platforms, namely Roon & Lumin, were reported 9 months ago to have been streaming TIDAL's lossy albums in MP3 (either 320kbps or 256kbps) via the HIFI streaming quality connection, as opposed to the AAC format. However, this is no longer the case, with both Roon & Lumin both confirmed in this thread to be streaming TIDAL's lossy albums in AAC and therefore also subject to the 96kbps HE-AAC streaming issue. I have speculated that the original format of the lossy albums in TIDAL's catalogue may well be MP3, given that MP3 is the only format available for purchase of the lossy albums as a download in the TIDAL store. This would imply that even the lossy 320kbps AAC streams would be compromised by having been derived from either 320kbps MP3 or 256kbps MP3. However, I've found one platform that does still stream TIDAL's lossy albums in MP3, the majority with a bitrate of 320kbps & the rest 256kbps - the Logitech Media Center with the ickstream LMS plugin, used by Squeezebox type devices. It is therefore unaffected by the 64kbps HE-AAC problem.
  9. Tidal sucks

    TIDAL should most definitely not be providing the HE-AAC 96kbps streams if you haven't asked explicitly for them, ie, via the LOW quality connection setting. According to the OP it has only started happening recently, via the HIFI quality connection setting. In all cases the HE-AAC 96kbps streams have been found to have replaced regular AAC (ie, AAC-LC) 320kbps streams. The original AAC 320kbps streams (and their recent HE-AAC 96kbps replacements) are seemingly forced on the HiFi TIDAL account user, because TIDAL don't appear to have a lossless version of the source album tracks in their catalogue. Certainly all of the AAC album track streams (so both HE-AAC 96kbps and AAC-LC 320kbps) that I've investigated thus far have their albums available for purchase in the TIDAL store only as lossy MP3 downloads. Albums that are not restricting the HiFi TIDAL account user to these AAC streams are available for purchase in the TIDAL store as both FLAC & MP3 downloads.
  10. Tidal sucks

    Sorry, I'll try to simplify the description of the TIDAL AAC stream formats wrt Audirvana: AAC+ 96kbps 44.1kHz - Audirvana appears not to support AAC+. However, Audirvana does support (regular) AAC, so it is able to decode the AAC 96kbps 22.05kHz core part of the AAC+ 96kbps 44.1kHz stream; AAC 320kbs 44.1kHz - Audirvana supports this, so decodes it as normal; Have you tried Musicscope on the TIDAL Desktop app streaming the AAC+ 96kbps 44.1kHz albums, as @wklie suggested in his last post? You should see activity beyond 10-11kHz (22 kHz /2), unlike with Audirvana. That's very interesting. Until now, the same AAC albums have been reported as having the same bitrates, regardless of the streaming device. Could you mention some, if not the whole list of those albums streaming as AAC 320kbps in Audirvana that are streaming as 96kbps in the Aries Mini?
  11. Controlling Foobar2000 via upnp using another PC

    I presume you actually mean you are using a foobar2000 (only) remote control app on the Android emulator on the pc similar to, if not the same, as the FoobarCon Pro app you used on your Android phone. A foobar2000 remote control app like FoobarCon is not a standard upnp controller app, ie, it does not have a standard UPnP control point for controlling the playback of standard UPnP renderers (aka streamers, aka network audio file players) using music files provided by UPnP media servers. I did mention this in my last post - I hope you are not still confused about it. However, good call on using an Android emulator on the Windows laptop to run the remote control app! Which emulator are you using? I've recently been testing MEmu and it works well on my low spec Windows 10 laptop, with hardly any noticeable lag considering Windows is still there. Of course, I'm not using it to run heavy graphic using game/video apps!
  12. Tidal sucks

    Please check Tidal desktop app instead of Audirvana. Set Quality to Master. Use Exclusive Mode if possible. HE-AAC v1 has two sampling frequencies, one is for the HE-AAC SBR profile, the other is for the AAC-LC core profile and is typically at half the frequency of the HE-AAC SBR profile. This allows HE-AAC to be backwards compatible with decoders that only support AAC-LC and would explain why Audirvana may be decoding 96kbps 44.1kHz HE-AAC v1 at 22.0(5) kHz.
  13. Tidal sucks

    If you look at the info povided by TIDAL, you do get the indication that the Robert Silverman | Starry, Starry Night albums don't all have the same release date, plus their individual track times & total running times are different: https://listen.tidal.com/album/8936899 (96kbps 44.1kHz AAC+) - Released 2006-02-14, Length 2:10:53 https://listen.tidal.com/album/12686392 (16/44.1kHz FLAC) - Released 2006-02-14, Length 2:09:12 https://listen.tidal.com/album/61738233 (16/44.1kHz FLAC) - Released 2005-11-22, Length 2:10:11 I don't think it's a coincidence that the first album version being provided as lossy AAC audio track streams is only available also as a lossy (but for some reason, MP3) download for purchase in the TIDAL store and that the other two streaming versions are available for purchase as lossless FLAC downloads: https://tidal.com/store/album/8936899 https://tidal.com/store/album/12686392 https://tidal.com/store/album/61738233 Agree, that it's a bit of a chore to check though - TIDAL certainly doesn't make it simple! Perhaps the PSA Bridge II renderer doesn't support the (lossy) 96kbps AAC, or more precisely the 96kbps HE-AAC (v1) (aka AAC+, aka AACPlus), streamed version of the album. Hence, the UNK (for 'unknown', presumably) in the PSA Bridge II/DSDAC's display and is making a confused incorrect guess at it being Apple Lossless (ALAC), fed back to the Lumin app ALAC & AAC encoded audio data, though totally different, are typically accommodated in the same type of container file, usually with the .m4a suffix.
  14. Tidal sucks

    Ok, so it looks like Roon too streams AAC now instead of MP3 metioned 9 months ago.
  15. Tidal sucks

    So it looks like whether MP3 or AAC is provided, is determined by the TIDAL server doing something (or not) depending on the specific connecting client device, rather than it having anything to do with the API version being used by the client device. In all cases that I've tried so far with the ickStream/LMS platform (for Squeezebox type streamers), the TIDAL server always provides MP3 streams instead of the AAC streams reported for all the other devices, including that album you mentioned testing 9 months ago. I too cannot find more than one current version of the same album on TIDAL.