listas_fede

Ok. Sorry for my confusion. That IS the kind of answer I was waiting for. 3.2.18 should be fine. Thabks for your help, damien78 !

Not the kind of answer I was waiting for. What if I want to keep an older version? You’ve always given a choice not to have the latest version. Lots of your users tend to wait a few weeks or months before updating, waiting to know if the update doesn’t brake more things than it fixes. As a matter of fact, I’m not convinced of the new interface yet and stuck with version 3.2.15. This is the first time in many years that I’ve used Audirvana that you’ve forced your users to have the latest version, with no option at all. Not nice. Hope you find a solution for us.

Has anyone experienced problems logging in TIDAL? I've got 2 Macs running Audirvana 3.2.15 and 3.5 as well. Both say "Login failed to TIDAL - Invalid token". I double checked, logged out and in again, logged in via web and everything worked. I even went as far as installing a fresh MacOS and Audirvana, with no success. Someone having the same issue?

OHHH! Pretty interesting! Specially for those (like myself) who still are on the fence between FW versions.

Thanks for your detailed explanation, @AMR/iFi audio ! I know the bigger one does more stuff, but only on the amplification/battery/headphone/filter department, not on the DAC department, which I clearly stated. Even though I/we appreciate what you've done and that on top of that we all have a choice to go back and forward with these 2 different flavored firmwares, I still can't understand why a DAC which is more powerful can't do more than one that is less powerful.

I’m on your same page (micro iDSD), but still deciding between keeping 5.30 or going back. I have a few DSD256 files I’d like to keep enjoying, and am giving a thorough listening test to see if there’s any audible benefit from playing MQA rendered by hardware or if I’d be OK having Audirvana do the first unfolding on MQAs and then upsampling to DSD256 which sounds super musical to my ears (but can’t do it now).

Doug, You're making the same mistake I did. I admit I have been claiming iFi unfairly on this matter for the last 24hs: Prior to the firmware update, you and I had DSD512/PCM768; but on Mac that translates to max DSD256/PCM768 due to DSD-over-PCM (aka DoP), our only method to get DSD playback con Mac, since there's still no driver to play NativeDSD. Windows and Linux can, while Mac can't. It takes PCM768 to "transmit" DSD256-over-PCM. This was the highest DSD you and I could previously play. Since PCM768 has been lowered to PCM384, all we can achieve now is DSD128-over-PCM. So, in the end, iFi is not "lying" to us when they say after the upgrade we get DSD256/PCM368. Hope I made that clear. You will be able to play DSD256 as long as it is natively, through ASIO drivers in Windows or Linux. (I won't for the matter. I'll stick to Mac and Audirvana and weigh in the pros and cons and decide whether I will keep the previous or the newest firmware). What still bugs my mind is how it is possible that machines with a double-core DAC (micro iDSD and micro iDSD BL) are now exactly as capable as their smaller siblings (nano iDSD and nano iDSD BL) which have just a single-core DAC. What are we getting in exchange for all that extra horsepower? As far as the DAC department goes, I perceive we get ZERO differentiating features, which is just crazy. I hope we can get some kind of differentiating feature, maybe get back DSD512/PCM768 (which would get us Mac users DSD256/PCM768 playback, remember that), or MQA full unfolding, decoding and rendering, since these units are more capable (MQA implementation on the whole iFi lineup as of today is just rendering; you still need the first unfolding to be done by the playback software). Secretly hoping this 5.30 firmware is just a draft and sooner than later iFi will correct all these things, giving us back what we had before, just adding MQA support on top of all our loved features we got used to. Federico from Argentina

After a whole day of fiddling with the MQA novelty and getting in touch with other iFi users in the same situation as myself (or similar), I just can't understand how it is possible that the iFi crew need to cripple some units, rendering machines that are technically double as powerful as the nano iDSD BL (double core vs single core DACs) become as useful as the lower end sibling. Before MQA introduction, the decision was clear: nano gets you DSD256/PCM384 and micro gets you DSD512/PCM768. Want more power? Get the bigger brother. How is it possible that from now on both units are equally capable on the DAC department? Is the micro not really more powerful than the nano? Is the new 5.30 firmware just a transcription of what was already implemented for the nano, so higher sample rates can't be included now without re-writing the whole code? I wonder what exactly is going to drive purchases toward the micro iDSD BL when the small brother (nano iDSD BL) is capable of exactly the same formats and qualities. It was supposed to be a more powerful machine. I know, there's other stuff that's also important other than the mere DAC capabilities. There's different amplification circuits, etc; but still, makes someone wonder if it's really good idea to invest on the more expensive unit. I'm really grateful for the MQA addition and have been experimenting (and probably will continue for the next days to come), comparing MQA vs other formats, and mainly Audirvana unfolded MQA + up sampling vs "full MQA". But I really hope the iFi guys can deliver just MQA support on top of what we already had and had come accustomed to. Or some other differentiating feature between the nano and the micro; maybe full unfolding and rendering. What's the extra horsepower for otherwise?

Worked!! Reinstalled app on my iOS devices and problem was solved. Thanks for your help!

Just wondering if anyone encountered the same problem I have and came to a solution. Running A+ 3.0.7 on a Mac mini, Sierra OS and A+ Remote on my iPhone 7 and iPad 3. I just can't pair more than one device at a time. If I pair my iPhone, my iPad gets "kicked out" so next time I want to control A+ with my iPad I need to re-pair, entering the displayed numbers, while kicking my iPhone out. On Preferences - Library, I can see at the bottom of the screen, "Paired devices: 1". I tried clearing out the paired devices list, deleting all system files created by Audirvana (plists, etc) and had no success. After all the deleting I had to add my music folders, re-create my playlists, sign back in on Tidal, etc. So I can confirm I've cleared pretty much all the config files. Same A+ version on other Macs work fine with 2 (or more) remotes on iOS devices. So there´s gotta be something I'm missing. Someone else had this problem and solved it? It seems no matter how much I clean up my A+ installation ad re-install, it won't be solved.

I contacted iFi support and they suggested I installed firmware 5.1. Only 5.1 is compatible with automatic input switching to SPDIF. I'm on 5.2 so that would be a downgrade. Still trying to get courage to do so. Maybe this info helps others having this same problem. Just want to clarify I haven't yet tried if this solution actually works or not.

That's exactly my situation. If I want to play any SPDIF / Toslink I need to have USB physically disconnected and start draining the battery. But the site above says that is not necessary. All it needs is to stop receiving a PCM signal through the USB port to start listening on the SPDIF port. As a matter of fact it starts by listening on the SPDIF and it switches to USB if there's any PCM sent that way. So I believe we both must be doing something wrong. Or is it really a Computer-only audiophile forum and nobody even tries to hook anything other than a computer to their DACs? Sent from my iPhone using Tapatalk

I'd like to understand the auto-input switching system. According to this site: iFi Audio Micro iDSD: Features - TechnoHeadphone The micro iDSD switches automatically between SPDIF and USB depending on wether if its receiving a PCM signal through its USB port. I have a Toslink source connected using the provided adapter to SPDIF to the back of the unit as well as the USB port connected to my Mac. Normal operation though my Mac works perfect. Playing through Audirvana lots of Hi-Res music. But whenever I try to play through the other input, that's where problems arise. I was never able to play anything through the SPDIF port unless I completely unplug the USB port and start draining the battery. That's the only way I can bypass the USB input. Of course, as soon as I reconnect the USB input, I lose the SPDIF signal. According to the above cited site, switching should be effortless, as long as I'm not sending any PCM signal through the USB port. I double-checked to have selected as default audio output in my Mac its internal speakers and only have the DAC selected as output from within Audirvana (and making sure of course to have it STOPPED, not PAUSED). What am I doing wrong? Please enlighten me. Thanks in advance for your help. Sent from my iPhone using Tapatalk

Does your cpu usage go high as mine?

Fans are running 1500 rpm but cpu temp can easily get near 90 °C which scares the hell out of me.