PeteLinn

Newbie Wammer
  • Content Count

    60
  • Joined

  • Last visited

Community Reputation

51 Excellent

About PeteLinn

  • Rank
    Junior Wammer

Recent Profile Visitors

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

  1. You can indeed. The reason for discrepancies between Konfig and the Linn account is that they read from different feeds to pull artifacts such as firmware and Exakt crossovers. Konfig is unaware of the Linn account feeds, hence the issues in Konfig when your system has been setup in the Linn account, as you mention), but the Linn account is aware of the Konfig feeds (the issue you mention here was actually due to a short delay in publishing the new K350 filters in the Linn account feeds, but that should now be remedied, with a v5 now present). As a little background, the entire storage architecture of Exakt was overhauled for the Linn account to better handle a few issues, including (but not limited to): - Exakt crossovers were tied to devices, and so not all crossovers were available on all devices (despite their capability to implement them), and so the Linn account was designed to allow any crossover your device is capable of implementing - due to the above, the filter versions were sometimes confusing (what was v7 on a K350E would be v3 on a K350E with Katalyst), which the Linn account has standardised (though this may have resulted in some naming inconsistencies vs Konfig) - there were a vast slew of redundancies in the Konfig feeds (re-releases of crossovers, duplicated firmwares, etc.) which have been removed from the Linn account feeds, allowing for a more streamlined feed and simpler publication of new artifacts. Hopefully that clears things up a little at least!
  2. This is actually unrelated to SO, and was due to some issues with the previous 350 filter.
  3. You should not. Please report the issue (either through the Linn Development Forum at https://development.linn.co.uk/forum-30.html, or through the Linn service team).
  4. You can run 2-way speakers if you have 2 cartridges/4 channels, or up to 3-way speakers if you have 3 cartridges/6 channels. And this has nothing to do with the passive 'dorik/'barik end-of-life. Correct.
  5. Selekt actually already has an internal Exakt engine. Thus, once you have enough outputs (2 cartridges/4 outputs or more) you can effectively use the Selekt as a one-box stereo Exakt solution.
  6. The model was implemented due to the belief that the environmental and absorption settings are constants (i.e. once you have tinkered to find the best values they will never change) since, just like you wouldn't change your floor plan very often (unless you undergo serious construction work, at which point I'm sure updating your room in SO is the least of your worries), you will have a thermostat set at a consistent temperature and won't be knocking down concrete walls to replace them with partition very often. This model has caused few issues prior to this beta, as @timster pointed out, but since you guys are the real tinkerers this is the first time it has been tested in anger (or hopefully in joy for the majority of you), and so your comments will be taken under advisement to improve usability in the future!
  7. First off, it is worth noting that an optimisation (as listed in your optimisation history) actually contains three parts; 1. a reference to the room data used to create the optimisation, 2. the speaker locations used to create the optimisation, 3. the optimisation filters. When adjusting an optimisation, the Linn account will do then do two things; a. create a new optimisation, with a reference to the updated room data, the updated speaker locations, and updated optimisation filters, b. retain the original optimisation, whose reference will now point to the UPDATED room data (the Linn account assumes any changes to the room are due to physical changes in the real room, therefore overwrites the original room, hence the "The room has changed since this optimisation was created..." warning in the Details modal), the original speaker locations, and the original optimisation filters (note that adjusting an optimisation has NO EFFECT on the optimisation filters of the original optimisation). The only slight strangeness in this model is that if you adjust an optimisation, but then go into adjust that same optimisation again at a later, it will appear to reference the updated room (as per step b above).
  8. There was a change to support the "Plus Subwoofer" Exakt filters (2.4.0) and a bug fix to the speaker delays (2.4.1).
  9. Just to clear this up, Exakt Akudorik stands (either those as part of true Exakt Akudoriks or those as part of converted passive-to-Exakt Akudoriks/Akurate 212s) are not supported in the beta. This is in fact due to them supporting both Akudoriks and Akurate 212s, which puts them into a different class from Exaktboxes (which can handle any speaker) and Exakt speakers (which can handle only their dedicated speaker), making their configuration slightly more involved. Support for these should, however, be coming soon.
  10. The rotation is performed around the reference point for measurement. So, for the below (this dialog will show when you have a speaker selected in the SO wizard), the rotation would be performed around the outside top front corner of cabinet.
  11. SO optimises the loudspeaker-room interactions in three ways: 1. room mode optimisation; SO looks at the difference between the long-term response of your speakers in their practical locations in your room and in an anechoic environment, thus this optimisation depends only on your room, your speakers, and their practical locations 2. boundary (or placement) optimisation; SO looks at the difference between the short-term (or power) response of your speakers in their practical locations and ideal locations in your room, thus this optimisation depends only on your room (in truth, only really on the boundaries nearest your speakers), your speakers, and both their practical and ideal locations 3. time-of-flight optimisation; SO looks at the distances from your speakers to the listening location, thus this optimisation depends only on your room (at least in SOv2 were room environmental conditions are considered), your speakers, their practical locations, and your listening location. We thus see that changing the ideal location (such as in a virtual TuneDem) will only change part 2 of the optimisation; this is the part that "makes your speakers sound as if they were in their ideal positions".
  12. For further information please refer to my latest post in https://development.linn.co.uk/thread-283.html The team here are registering any requests for sign up to the beta, but you won't get any response until the beta goes live, so please hold tight!
  13. Hence my guidelines earlier. If you are at all concerned I would advise you to change only the filter version (i.e. version 1, 2, 3, etc.) and not the filter variant (i.e. Standard, Plus Subwoofer, etc.) - this way, all connections will remain as stated in Konfig.
  14. There are some filter variants for earlier Exakt-ready speakers (e.g. 350As) which included an output for a subwoofer (in the Linn account these variants will be called "Plus Subwoofer", and are to be deprecated); the connections for these variants will differ from the standard filter variant (which does not include an output for a subwoofer), and so in this case care should be taken that the speaker is connected correctly (in particular when moving from the standard variant to the plus subwoofer variant, where the channel which was outputting the tweeter signal will now be outputting the midrange signal).