Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by DavidHB

  1. From An E3 supplier's website: "The Goldring E3 ... benefits from a superior bonded, super-elliptical (0.3 x 0.7 mil) stylus. This gives it better high frequency groove detail retrieval ability over ordinary elliptical (0.4 x 0.7 mil) or spherical (0.6 mil) styli due to its smaller front to back radius." Sounds plausible to me, and at least the specified difference is easy to understand. David
  2. IIRC, Majik cases are formed from 2mm sheet, while Akuraked cases are 3mm thick. A 50% increase in case thickness is, I guess, anything but trivial. David
  3. ... which is much better option for Exakt than an older Majik DSM (which was much the same price new as the AEDSM). With the MDSM you are paying for analogue outputs and onboard amplification which are pretty much useless in an Exakt system. David
  4. As I noted, the Linndocs page doesn't provide one. In the circumstances described, that is unsurprising. David
  5. ... which the Trampolin (designed for the job) would provide, of course. And as upgrades to the LP12 go, the Trampolin is not the most expensive; in fact it would cost you little more than a set of fancy pucks. Can you tell us why you removed the baseboard in the first place? David
  6. I relate strongly to this, which is why I stick with the combination of MinimServer and BubbleDS. Ease of browsing, incidentally, can (depending on user requirements) be as much a function of server capabilities as of the control point UI. For example, standard servers that only know about Albums, Tracks and Artists are nearly useless for classical music. The Linndocs page I linked to in my earlier post only offers Kinsky for older iOS devices, older MacOS versions and Windows. This is tricky with scalable apps, because there is not enough room on most phone (and even spaller tablet) screens to fit both the library view and the playlist on the same screen. IMO BubbleDS has the best compromise, because it shows the Library, Playlist and Now Playing views separately (and so full screen), but allows you to swipe quickly from one to the other. If you or your device do not like swiping, selection tabs are offered as an alternative, as one of the many configurable options in Bubble. Another good thing about Bubble is that you can have it on the same device as Kazoo, and use whichever one takes you fancy at the time. David
  7. I'd add "superstitious" to the list. You know: "If I flick this small speck of dust off the top of my speakers, will they suddenly start sounding like a dyspeptic camel?" ... David
  8. Er, I'm not sure about that. Your definition of of 'proper' is IMO legitimate, but it is not the only one with some claim to coherence. Doesn't "If it ain't broke, don't fix it" come into the discussion somewhere? And I'd say that your example implies that Linn are not saying that no power conditioning device, ever, can be used in a 'proper' (howsoever defined) setup, but only that some such devices are unsuitable for use with a Dynamik PS. Why apocryphal? That's one of the clearest and most precise customer requirements for a Hi-Fi system that I have ever heard ... David
  9. You missed the point. I was saying that I don't have (and don't want) any MacOS devices or iThingies to discover what "unsupported" actually means. I do have and occasionally use Kinsky on my Ethernet connected Windows 10 computers, where it is pretty stable, as is Kazoo. On Android, IIRC, it was pretty much as unstable as Kazoo. Upgrading my most used WAP and the Android devices (phone and tablet) I now use to AC standard WiFi has made Kazoo pretty stable on Android as well. However, that is pretty academic, because I know of no reason why an Android user should not prefer BubbleDS to Kazoo as their regular control point. Going back to the OP, when he asks the answer is that no one will tell him that, not even Linn, who are developing the Linn App after all, albeit at snail's pace and so far for only one platform. But Kazoo is a perfectly usable control point when used in a stable networking environment. It is probably the best control point for Windows, albeit in limited and rather undistinguished company. Even in Windows, if only Asset Control were more finished, I reckon that it would be better than Kazoo. David
  10. There's a specific link to "unsupported software" on the Linn main site Software page. It takes you to https://docs.linn.co.uk/wiki/index.php/Unsupported:Home where there are links to Kinsky for Windows, MacOS (Catalina and later not supported), and iPhone/iPad (iOS 11 and later not supported). I do not have the wherewithal to test whether "unsupported" means "does not work". The version for Android seems to have disappeared from the Google Play store. David
  11. The current stable Davaar is 4.79; the current beta is 4.80.389. The most significant element of the latest update is the changes required to support the new Tidal login process, which require compatible Davaar and Kazoo versions. There may be some incompatibility that is causing your problem. Alternatively, something could have gone wrong during your latest update, and the problem could be fixed by uninstalling and reinstalling Kazoo. Which Model of DS/DSM are you using and which server software? It could be that, on Android, you would be in any case better off switching to the BubbleDS control point for normal use. David
  12. My Bask Plus worked very well with a K5 fitted with a Paratrace stylus. Graham67's friend might well wish to consider a VM95 series cartridge with a more sophisticated stylus profile than the VM95E. The VM95ML with a microlinear stylus profile, at £150 will not break the bank. David
  13. One person's tweak is another person's major upgrade is a third person's sonic disaster. And try telling the significant other ion your life that changing the furniture in your living room is "just a tweak". David
  14. Digital data is carried on an analogue signal. The difference from analogue data is that, with digital, the carrier signal can be much more noisy and distorted before the data is compromised. Any noise can however remain present in the system and can affect the signal when it is converted to analogue. So, if issues arise, they will be a function of (1) the extent to which the power cables induce noise into the Exakt and/or HDMI leads and (2) the degree to which the receiving device is able to suppress that noise and prevent it from getting into the analogue domain. Running the Exakt Link next to the power cable will not be exactly helpful, but it is not necessarily a recipe for disaster either. I'd guess that this is a situation where using shielded Ethernet cables for the Exakt Links might be a sensible precaution. David
  15. I'd have to agree. But Gilad has a bit of a fetish for hiding cables. And, in style terms (these are Series 3, after all) it makes no sense to route the signal cables up the pipe and leave the power lead dangling. Form vs function strikes again ... Of course on my 109s, as on any passive standmounts, there is only a single speaker lead to consider. David
  16. Is that Windows or Android? 4.13.74 is working perfectly well on both for me, so very possibly not a Linn issue. What version of Davaar are you on? David
  17. That's reasonable. My new 109 stands each have two tubes of about that diameter and thickness. The rear tube has holes top and bottom to accommodate the speaker cable. I'm not sure that those holes are big enough for an IEC power connector, however. David
  18. I'm not sure that you can. In the present case, it has just occurred to me that a user might want to route a power cable with IEC connector, 2 Ethernet cables and an HDMI lead through the pipe. Is there enough room for that lot? David
  19. Yes, they do. See https://www.linn.co.uk/speakers-and-amps/accessories/speaker-stands#series-3-stand David
  20. To be fair to Chris, from what I hear from him and others he wants to give all his customers good service. I consider him to be a friend, but that is to no small degree because we both understand the respective requirements and obligations of both dealers and customers. We agree a deal before an order is placed, and then we both stick with that deal until it is complete. As the French say, "les bon comptes font les bons amis". David
  21. It's not just about the kit, it's also about the ecosystem that supports it (or not as the case may be). I wonder whether the real issue with your Polo was not that it had a fault, but that the service agent did not have the skills and/or knowledge to identify and fix what was really wrong? So, when Stingray says he in fact makes my point for me. I have seen many cases, on this forum and elsewhere, where equipment and/or software is blamed for problems that are really caused by failings in the network. The equipment and software is up to the job, but the infrastructure is not. In such circumstances, trying to allocate blame is typically a waste of time, because fixing the problem is likely to require input from a number of different stakeholders. Manufacturers know this. We have been seeing improvements in home networking, with AC standard wireless access points and mesh systems becoming more prevalent. At the same time, equipment manufacturers have tried to make their products more robust in less than ideal networking environments. Part of that is the provision of knowledge; Linndocs has much more comprehensive troubleshooting information than used to be the case. (A good example is the advice now offered on the infamous "Waiting for room" problem, which is found at https://docs.linn.co.uk/wiki/index.php/Troubleshooting#Kazoo_states_.22Waiting_for_Room.....22. ) David
  22. Welcome to the forum, and thanks for your helpful and informed input. There are two realities that both manufacturers and users of streamers (of whatever brand) have to grapple with. The first is that, particularly where control software is concerned, there is a vast range of use cases and an equally wide range of expectations. People who moan that this or that software app is bad or useless need to be clear about (1) what their expectations are, (2) why those expectations are reasonable and (3) the specific way in which the software in question fails to meet those expectations. All too often, criticisms of software fail to meet those necessary requirements. The second point is that streaming has not had that much time to develop. We are probably at the stage that motoring was in in the 1920s. Things mostly work, most of the time, but some understanding of the technology and a self-help capability (not to mention a bit of patience) can come in very handy. The point of many of our responses to the OP is that it is self-defeating to give up too soon. After all, we're all here to help. David
  23. The Davaar firmware, in my experience, is much more stable than the control software, in part of course because it is not dependent on local WiFi conditions. I have been on the Davaar beta channel for several years, and I have never had a significant software glitch with my DSMs. Occasionally new stuff has not worked as described in the release notes, but the core functionality has always remained stable. Linn firmware is built on the OpenHome stack, which originated in the very earliest days of the DS, and is pretty solid by now. By contrast, Kazoo and I think the Linn App as well, are built in Microsoft's cross platform Xamarin development environment. As you are using Android, Have you tried the BubbleDS control point?. It has IMO a far more consistent and intuitive UI than Kazoo, provides lots of useful user options, and also has a proper Exit button so that you can force a restart and a network rescan if and when the WiFi loses touch with your system. There is a licence cost, but it is tiny. As regards MinimServer, it may well be that version 0.85 works with Kazoo beta Pins; I just can't test that combination. And I don't regard the MinimServer 2 cost (£28 up front for up to three instances, plus £10 p.a. thereafter to receive updates and continue using MinimStreamer) as unreasonable, given that the author, Simon Nash, has to maintain a lot of platforms on which to test development builds ahd installations. David
  24. The support for UPnP pins, I now find, has only been implemented in Davaar 80, which is still in beta. Are you on the Davaar stable channel? Presumably because the release is beta, the main documentation has not been updated. I'm on MinimServer 2, and I don't know whether any corresponding change was required in MinimServer. There is no mention of it in the MinimServer release notes David
  25. I'm using Minimserver, But, for this purpose, it ought to work in the same way as Kazoo Server. The display you show looks very similar to the one on my Google Pixel 4 phone, running Android 11. I'm using Kazoo version MinimServer gives me a "Playlists" item on its top level menu. Within Playlists, I select (you've guessed it) the Radio stations playlist, with a list of radio stations as its 'tracks'. If I select the "three buttons " (More) menu for the station/track I wish to pin, it gives me a blue menu at the top of the screen with the caption "1 track selected". This in turn has a More button, and the drop-down menu which then appears has a Pin option. You can also pin complete playlists in the higher level menu, though this obviously doesn't make sense for a playlist with multiple radio stations. The procedure for pinning a complete playlist is a little different, as there is no More menu; you just press and hold to select the relevant list, and the blue menu appears. I note that, in the screen shots, the Source is shown as Net Aux. I always use the Playlist Source to pin items. That might be your problem. I hope this helps. David
  • Create New...