BB1

Wammer
  • Content Count

    195
  • Joined

  • Last visited

Community Reputation

38 Excellent

About BB1

  • Rank
    Junior Wammer

Personal Info

  • Location
    Germany

Wigwam Info

  • Digital Source 1
    Linn KSH
  • DAC
    Linn KEB/1s
  • Power Amp/s
    Linn A4200s
  • My Speakers
    Linn Misos
  • Trade Status
    I am not in the Hi-Fi trade

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. My personal conclusion based on this thread: I prefer paying more for a working solution (e.g. Qobuz) over having to fiddle around with Amazon HD’s limitations… Just my 2 cents.
  2. I totally agree with you and what you’ve said is not limited to speakers. The usual way of measuring THD+N for sources or amps is applying A-weighting just because the obtained figures most often do look much better than the ones obtained by ITU-R468 weighting. And both weightings provide a serious attenuation in the 50 Hz range, i.e. a device producing audible hum might have the same THD+N figure as a device not showing this issue... Btw, is it coincidence that 42 is also the answer to the ultimate question of life, the universe and everything?
  3. I’d raised this as a feature request as well. From my technical point of view a "Pin" is nothing more than a link to content and it really doesn’t matter where this link is stored. Hence pinning a single track on any server shouldn’t be a problem at all as this link would point to a unique URI. It might be more complicated to pin an album on a UPnP server.
  4. FYI I’ve done some tests on my setup: - late 2018 Mac mini, 8 GB RAM, six-core i7 @ 3.2 GHz - library containing 2710 albums located on an external USB 3.0 drive - Minim Server, Kazoo Server and Roon Server running in parallel - iPad mini 4 running the control point ("Linn" / "Roon Remote") Memory usage after boot (all servers idle) is as fallows: Please note that the total memory usage of Roon is the sum of „RoonAppliance“, „RoonServer“ and „RAATServer“ The following figures were observed while streaming FLAC in 192/24. Minim Server 0.8 update 129: Memory usage remains nearly constant at about 260 MB, CPU utilization is <= 1%. Kazoo Server 4.10.1.0: Memory usage varies between 770 and 950 MB, CPU utilization is <= 1 %. Roon Server 1.6 (build 416): The only way is up… After streaming one album, RAM usage has reached 2.1 GB. Average CPU utilization is 12 %, peak values are reaching 25 %… It’s worth to note that the maximum memory usage of a software running on a machine with more than enough RAM is no indicator for its minimum RAM requirement to run (sort of) smoothly. It only tells that the software will not benefit at all from more available RAM. As soon as Kazoo Server reaches a memory consumption of about 950 MB, it drops down to about 770 MB on my machine. Hence I’d assume that Kazoo Server is written in programming language supporting garbage collection and heavily relies on it. Usually the trip point where garbage collection happens does depend on the available RAM. By no means it should happen after virtual memory has to be used unless the software really needs this amount of RAM. Hence I’d ask Linn what’s the minimum RAM requirement for Kazoo Server. Sad, but true: The availability of much more powerful hardware does often not lead to smoother working software, but sloppy programming just wasting the available resources.
  5. Thanks, Phil. If I’m not mistaken Series 3 is the only speaker revealing its maximum SPL on Linn’s website. 101 dB are quite impressive for a speaker of this size and I wouldn’t have expected 109s being able to play louder. What’s the Series 3 bass roll-on frequency?
  6. True if compared to MinimServer, but if compared to Roon both servers have very moderate hardware requirements… Not so much on the search functionality, but Linn specific functionality. I’m still failing to see why pins only work for Kazoo Server, but no other local servers. This might be in line with Linn’s design decision not to support grid view in "Linn" (the new control point app) for any other local server than Kazoo. It makes no sense at all, since Kazoo (the control point app) does support this feature and not supporting it in "Linn" is a major regression. Yes, it will.
  7. To be fair, quite a lot of my feature suggestions has been implemented "silently" sooner or later into new beta releases. Of cause it’s frustrating not to get any feedback in the forum, but from my experience Linn’s developers do listen although not replying officially. That’s the reason why I’m still providing feedback. I think timster hit the nail on the head with "everyone’s different". Until Roon supported Qobuz it made no sense to me at all to give it a try. IMHO the preferred control point is a matter of personal taste and how well it performs on someone’s daily use cases. If I would use the control point app for changing the volume regularly, I’d rate Bubble DS lower than Kazoo or Linn, but as I’m actually using the remote for this task, it doesn’t really matter in my use case. There is and most likely never will be the one and only control point suiting everyone.
  8. Let’s wait until the actual specs of Series 3 are published. I may be wrong here, but my bet ist that a 301 does contain at least o part of the DSM’s functionality in a Kiko system, i.e providing additional inputs besides Bluetooth.
  9. If reading between the lines I’d sum up this "review" as follows:: It’s a "wireless" system requiring a physical link between 301 and 302 and its Bluetooth implementation is buggy. I’m aware that Linn is desperately seeking for new markets, but I’d very much doubt that Series 3 is the answer.
  10. Yes, that was just wishful thinking which unfortunately will most likely not happen in reality…
  11. Given the link to the first "review" of Series 3 in an other thread I’d like to add that prioritizing development efforts is sometimes mainly driven by marketing assumptions which might hold true or not…