Jump to content

psme

Members
  • Content Count

    164
  • Joined

  • Last visited

About psme

  • Rank
    Sophomore Member

Recent Profile Visitors

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

  1. IMO, use cases of Leedh Processing volume control are: For Analog output - normally use pre-amp or integrated amp volume control, but also very tempted to use LUMIN volume for quick adjust with the convenience. Before Leedh Processing, it's not preferable. Now we can have our cake and eat it without any ill effect. - set pre-amp or integrated amp to unity gain (or at a fixed gain position), or use pre-amp/integrated amp "by-pass" input, then control LUMIN volume with Leedh Processing. * if your pre-amp has no "by-pass" input, and you want to connect LUMIN player directly to the power amp, you may consider add a simple audio switch device like this: https://www.audio “science” review/forum/index.php?threads/nobsound-3-in-1-out-xlr-audio-switch-review.11062/ And connect both pre-amp and LUMIN to the switch, then to the power amp. - direct connect LUMIN to power amp and control LUMIN volume with Leedh Processing. For Digital output - before Leedh Processing, user is advised to NOT use volume control in LUMIN. Now it's free to use with Leedh Processing. User can try which way do they prefer. The theory of Leedh Processing is to avoid too many bit of information. Because many least significant bits will be lose in DAC conversion, hence Leedh Processing try to use as little (number of) bit as possible to represent volume value, so that when the audio data reach DAC, many least significant bits are already at zero value, then the bit truncation in DAC conversion doesn't matter and the integrity of audio information is retained (lossless). These are the 2 very different approach toward volume control calculation. Many bits (64bit for example) approach aims for accuracy (but some data will be lost in DAC conversion), while Leedh Processing approach aim for exactness (use as little bit as possible for an exact volume number). The proof is in the listening! And it seems by actual listening, most people prefer the sound of Leedh Processing! OK, I'll shut up now!
  2. The story of LUMIN and Leedh Processing Volume Control. We have a long relationship with Joël of 6Moons reviewer. We see each other during each year Munich show. During High End show 2018. Joël kept bugging me with this new end-of-the-world revolutionary new Volume Control algorithm, Leedh Processing! Frankly I was not that interested at that time. But Joël was raving about it so I kept it in mind. In 2018 Sep, we had a tour visiting many dealers in Europe. We were in Paris and visited Joël setup in his home. Joël bought along the inventor of Leedh Processing and gave us a demo using their evaluation system. The difference was night and day IMO! Joël said he compared to many software and hardware (pre-amp) volume control and nothing came close. But my teams were not that convinced. We audiophile all have very different taste! So the development was stalled a bit. I want to push this feature ASAP. But our engineers said from a technical point of view, it is nothing special. Just another way to do volume calculation! And there was the cost issue! It's not free! Another big Hi-Fi brand charge a premium for this feature upgrade! We had discussed how to market to users. In theory we can setup a system to charge for this new feature. So the development stalled more. Eventually, I said cut the crap and just do it! So we had a test version by the end of last year. Joël tried the test firmware with position feedback. It's certainly better than the original volume control in LUMIN, but there was still something not right. Leedh Processing party went to Joël's setup and did some measurement and found some volume adjustment were out of specs. Turned out our engineer took some shortcut, because that was easier (to integrate with our existing data flow) and the result "should" be the same! So we re-did the whole thing from the ground up! After 6 months of hard work (to implement Leedh Processing on our whole LUMIN lineup), everyone is happy now! According to our engineers, if you really study all the document from Leedh Processing web links, it's possible to work out the algorithm on your own (Sorry Leedh Processing party!). But we need to pay respect to where's credit due. So we pay license to Leedh Processing and offer free upgrade to all LUMIN users. Enjoy the music! https://6moons.com/audioreview_articles/lumin8/
  3. Thanks for the feedback. We will fix it in the next app update.
  4. A new app is currently waiting App Store approval, and should be released in a few days. Hopefully it will solve the iPad Gen 1 issue...
  5. Sorry for the trouble! If possible, please send us the crash log. Please see instruction here: How to Send an iOS App Developer a Crash Report: 12 Steps Please email crash log to [email protected] We will study the problem. On the other hand, if the issue is too hard to handle in the long run, we may be forced to drop iPad 1 support. The first generation iPad has only 256MB RAM, which the iOS itself already takes more than 200MB RAM. It will soon becomes quite impossible to run the full LUMIN app (especially with a decent size of music library) within 50MB RAM! Thanks!
  6. Sorry about the trouble! Sadly the app works fine here with a few iPads running different iOS version. Anyway, a new app is already submitted last week and should be released in a day or 2. Hopefully it will fix the issue...
  7. @ESL, I just checked with a iPad 2, iOS 7.0.3, running LUMIN app 5.01, without any issue. Please make sure your LUMIN player is using the latest 7.0 firmware. And make sure the iPad storage space is not fully used up. If problem persist, please do a full iPad Off/On How to Completely Power Down Your iPad: 6 Steps (with Pictures) Try to run the LUMIN app while the LUMIN player is unplugged, and check if the LUMIN app still self closed in 2 seconds! If all test fail, please PM me for further assistant.
  8. Sorry for the trouble! We still have an old iPad 2 in the office. I will try to test tomorrow. What is your iOS version?
  9. @cebolla, OpenHome does cover TIDAL service. TidalStreamingService - OpenHome
  10. @Distinctive, sorry, I meant the method of accessing TIDAL login/account information is proprietary between Aries and it's controller app, I think! I don't have a Aries, hence I ask if Aries works with BubbleDS Next app for TIDAL integration. If it works, it should work with LUMIN app.
  11. @Distinctive, maybe it's me causing some confusion? We already tried to be more compatible with existing software/hardware on the market, that's why we use the open protocol same as Linn is using. Hence BubbleDS Next app works with LUMIN renderer, and LUMIN app works with Linn renderer. LUMIN app does not work with other pproprietary system (Aries etc) is not really a LUMIN app problem...
  12. @Distinctive, are you using a LUMIN renderer with firmware 6.0? (Or a LINN renderer with latest firmware?) BubbleDS Next TIDAL integration work with LUMIN renderer, meaning after you added and playing TIDAL content on LUMIN, the playlist playback will continue, even you completely killed BubbleDS app or totally shutdown the Android device.
  13. Do Aries work with BubbleDS Next for TIDAL integration? Both LUMIN app and BubbleDS Next app use the same protocol for TIDAL integration. Linn Kazoo app also use similar protocol, but sadly Kazoo also check if it's a Linn renderer, so it won't work on LUMIN renderer!
×
×
  • Create New...