Jump to content

Quasimodo

Newbie Wammer
  • Posts

    31
  • Joined

  • Last visited

Reputation

13 Good

About Quasimodo

  • Rank
    New Wammer
    New Wammer

Recent Profile Visitors

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

  1. I'm sorry to hear that Matteo, old man. I have to say, I'd be mighty annoyed, too. It's all very well using a federated search across sources, but you need to be able to restrict it to selected sources, too. I appreciate that we can try to be practical and opt for Lumin or Roon or an alternative, but it doesn't address the issue that Linn doesn't seem to care an iota about this customer touch point. Using Linn control software is an exercise in accepting futility or restriction, or at best, playing something through gritted teeth after swearing because you can't find what you're looking for. That's inexcusable. Not at those prices. Perhaps it really is time to ditch and switch.
  2. Hello Linn enthusiasts, Over the years my exchanges with the Linn Helpdesk have left much to be desired, but somehow the last two take the biscuit. Just before Xmas 2020 my Linn DSM blew a gasket, so I called the Linn telephone number and was told outright that Linn categorically did not do repairs. I was at a total loss. It was helpful members on this forum who set that untruth to rest and pointed me in the right direction. (I'm still thankful to those helpful members.) Now, again I contacted the helpdesk to ask why it is that I can search my classical music collection for a composer using Audirvana and Lumin and get results whereas on the Linn (iOS) app or Kazoo, nothing is returned at all. I was told that it was my media server not supplying this info. It's the same music collection where the music is tagged using 'Composer' and the same media server. Audirvana and Lumin are test cases. This is a limitation of the Linn control points. I suggest that it is routine at Linn to lay the blame elsewhere. It's always iOS, or Airplay, or the NAS, or the media server. It's never Linn. Linn have just released a new Klimax, costing a whopping £30k. Plenty of people don't have that deposit amount for a property. For equipment that is this eye-wateringly expensive, providing software that is this shambolic is a farcical, laughable, absurd situation. As it the culture of fobbing customers off. It's contemptuous. Am I alone in my misery or have others received short shrift? Have I simply been unlucky? Q
  3. @grommeteer You are not alone, matey. Over the years I've tried various things to eliminate this annoying Airplay hiss including: Changing router - no effect Alternating sources e.g. Airplaying from different iOS devices / Mac computers - no effect Optimising my home wifi network - no effect - on the plus side, I now have an excellent network with good RSSI and low noise. (The signal is solid - I can airplay for hours without any drop-outs). Testing on my other music systems - the issue persists on my other Linn system and Naim MuSo QB.** Contacting Linn support - I think they pointed me (unhelpfully) towards the LinnDocs wiki. **For a time I did wonder if it might be amps adding noise, but I can play LAN music (from my NAS) and internet ratio (both via cat6 ethernet) without the aforementioned hiss, so that can't be it. Then I questioned whether it might be the periphery of routers/switches where the signal is affected, but again the signal path for music on my NAS / internet radio is via the same router/switch periphery (via ethernet) and these audio sources are free of hiss. So, if the listening gear and the networking periphery can't be the culprit, I'm left with the conclusion that Airplay is simply prone to noise. (When you eliminate the impossible, whatever remains, however improbable, must be the truth.)
  4. Thanks for weighing in, Jamster, with some good points well made. Not least for making abundant the two prevalent pricing models. You say that you didn't want to pay for it. Well, that's just the thing - I did. I would be prepared to pay for Roon if it were based on a license model at a level reflective of its ongoing value, which, as has been pointed out, is a highly subjective thing. And that, I suppose, is the crux, and where we see eye to eye - neither of us thought the value justified the price. As for the underpinnings of Roon's operations, I would also go some way to agreeing with you about the justification of model #2, but I struggle with this. Principally because Roon describes itself as a service, but it's far removed from SaaS (software as a service). Typically, SaaS organisations allow their users access the service either via browser or a client while the production (back-end) servers deliver the functionality. The more successful ones recognise the importance of having one production release which they incrementally update with features and support. Already there are two important differences with Roon: In SaaS Users are kept on one version Only one main codebase available On Roon Users can keep older versions Multiple codebases need support (*for installation client side) (*Roon needs to be installed on a LAN i.e. on-premise to do its work.) Perhaps the purest example of SaaS might be online banking and the app on your phone. Once the bank has a new version, it typically deprecates the old version and it stops functioning, forcing you to update the app. Some users find this mildly irritating, but this streamlined operation allows the bank to eliminate the maintenance burden you described. (Years ago Spotify used to aggressively deprecate clients every few weeks when an update was available, so this can be taken too far.) Among the many upsides though is that it's far more cost-effective, so ultimately, the end user prices are kept lower. If Roon adopted this approach, it might be cheaper and could, perhaps, claim to be a service. But, I suspect that the reason they don't do this is that the inherent complexities of compatibility with a plethora of local devices means that they know users will want choice over versions. As it stands, the characteristics of Roon mean that it has more in common with a licensing model than a subscription model. It's the platypus that convinced some it could fly.
  5. It isn't. The more keen-eyed will have noted my willingness to pay under a different pay model. It's not collecting income OR paying taxes - a functioning economy needs both. The themes central to this posting are value v price. And, at a stretch, ethics.
  6. Today (Christmas day) my free trial of Roon came to an end and I was glad to be shot of it. Good riddance, I say. Why? Not because of the interoperability, which is best-in-class, or the interface which is very slick, but it's something more fundamental and visceral than that, to my mind. Frankly, their billing model is the epitome of avarice. In a nutshell, Roon is on-premise software that aggregates 3rd party content and services into a top-level interface, so I would gladly pay a one-off fee for a license, but not periodic billing for ongoing usage. Secondly, the annual costs costs they charge are twice what they should be. $60 for a license which includes sub-version updates for (say three years) is reasonable. Three years of usage at their present prices would cost $360. The question which then looms is "for what in return?" Examine it. Subscription-based enterprises provide the infrastructure and deliver fresh value / utility per period. Roon, on the other hand, expect customers to buy/own the infrastructure and then pay for privilege of enjoying the same utility as you get on day one for the entirety of the billing period (ad infinitum). This may seem like heresy to those already bewitched by Roon, and this being the festive season, I realise that I may have unwittingly stepped into the role of cantankerous, penny pinching miser counting his last groat, but I have come away from the trial thinking that it's Roon who're rubbing their hands with glee, watching their overpriced gains trickling in. Tra la la la la laa, la la la laa.
  7. For what it's worth I, too, have thrown my hat into the Roon ring to give it a test spin. And like @Alexxus I've stumbled upon music I didn't know I had. Hurrah. But one thing is grating on me already - the album background info. To my mind, these are equal parts information and opinion. There are a few things wrong with this. Firstly, too many of these opinon pieces are riddled with errors. Secondly, they're just too opinionated. On the errors, I don't mean inaccuracies, but sloppy, inexpert writing. They are a far cry from the poised, well-written reviews or the incisive gems one finds in CD/LP/SACD booklets. Those have usually been penned by carefully-selected wordsmiths and gone through an editorial process. These, on the other hand, appear to be the hastily-cobbled together half-thoughts of blogging brats who think spellcheck is for the seniors and whose elevated opinions of their thoughts means they are too busy monetising their words before they've learnt their craft. Take this example for Rossini's Overture to La Gazza Ladra (The Thieving Magpie): "The Overture to La gazza ladra (The Magpie Thief, 1817) is a staple of the curtain-raiser slot in symphonic concerts. It is chock-full of colorful orchestral strokes that populate the whole group of Rossini overtures, beginning with a pair of side drum rolls at the very start that add military color and are just long enough to seem a bit ominous. They introduce an opera, designate a melodramma, that shades comic elements with darker overtones; the plot deals with a servant girl accused of stealing some silverware with which the magpie of the title has absconded for its nest." >>The translation isn't The Magpie Thief, but The Thieving Magpie. Nobody is stealing magpies. 'Melodrama' is misspelt. The drum rolls which "...add military colour and are just long enough to seem a bit ominous" is clumsy. More apt would be "... extended drum rolls that add military color and evoke a portentous opening." I won't even mention the grammar since nobody seems to care a hang anymore. Here's an exerpt from the album background info for Duke Pearson's 'Sweet Honey Bee': "The frameworks are quite intelligent, everyone doesn't solo on each section, and the improvisations are concise and clearly related to each tune's melody and mood. Although not quite essential, this set has some rewarding music." The writer may be entitled to this view, but perhaps an on-the-nose, low opinion by a stranger isn't the first thing one wants to see at the top when exploring an album. Perhaps these deserve a tab all to themselves and the background information should concentrate on the facts. What do you think?
  8. @All, Given the previous discussion concerning the multitude of parameters that can be adjusted, this may seem a blockheaded question, but I'll take the risk. Do you account for your radiators in your SOv2 profile in any way? If so, how? Thank you. Q
  9. Thanks @kelly200269, yes, I briefly looked into Roon, but my NAS isn't supported. (The cpu architecture needs to be either intel / arm and over a certain spec, too.)
  10. Hi @DavidHB, yes, I'm Davaar 4.79.383 on my Linn DS and DS-I. I only upgraded to this to take advantage of Space Optimisation v2. The thought of letting beta software (from Linn) run amok gives me cold sweats. I'm already struggling with Linn's control apps as it is, which seem to be in perpetual beta. The Linn helpdesk didn't mention anything about upcoming support for other media servers in future versions of Davaar and I'm not all that keen on signing up to an annual licence for MinimServer 2, especially if I'm not sure it'll have the outcome I want. Thanks for looking into it anyway.
  11. Thanks, @DavidHB. I'm using MinimServer 0.8.5.3 (update 134) (on Synology) and can't reproduce the options you're seeing on Kazoo. (I'm on Kazoo v4.13.74), so I'm so confused. Also today on this point Linn (Helpdesk) replied with the following: "The Pin option is only available for the Linn KazooServer media server – the media servers you are using are not compatible for assigning Pins." I give up.
  12. @DavidHB et al, I wonder if you can help with me with this. I've been hitting my head against this particular brick wall for some time now. I recently placed some .M3u8 files on Minimserver to stream radio. (It's my workaround to the BBC-TuneIn fallout.) When I navigate to them on Kazoo, I can add them to the queue and play them. So far so good. But I can't find the option to pin them. The only options I see are Play Now, Play Next, Play Later, Add to+. Are you using Kazoo Server? See attached images. What am I doing wrong?
  13. @DavidHB As one who might be taking the plunge on a MDSM/4 myself, I'd be interested in your write-up, David. Incidentally, is this your first MDSM?
  14. @Ian H For weeks I, too, kept seeing the dreaded "Something went wrong" message. This was consistent across browsers, but in the end it was resolved by upgrading Davaar. Credit to Richard (from Linn Helpdesk) for resolving the issue. Background: My version of Davaar was pre-Space Optimisation v2 and I was trying to initialise SO2 online. (Battle-scarred, I'm always weary of the old helpdesk favourite "try updating" for fear of untested software unleashing a Pandora's box of bugs, but this is a rare instance when an update did actually make things better.)
  15. Far from it. I've also written to Linn to report this issue. This is the case on iOS12 and on both Kazoo v4.13.72 and Kazoo v4.13.74, which was released yesterday with a release note about fixing crashing! Another half-baked release.) (Before anyone asks why I'm in the stone ages with iOS12, it's because iOS 13 broke Linn's implementation of AirPlay. The buffers used in Linn DS are too small to allow an uninterrupted stream and why users experience drop-outs when AirPlaying to their Linns. Linn tell me that this is a hardware restriction and cannot be corrected by firmware.)
×
×
  • Create New...