(12-May-2016, 06:00)Eddye Wrote: [ -> ] (11-May-2016, 20:37)Rufus McDufus Wrote: [ -> ] (11-May-2016, 20:22)SwissBear Wrote: [ -> ]I have the same issue here with Audirvana 2.5.0. When not upsampling, changing sample rates requires to 'reload' the driver, ie re-select it in Audirvana's preference. In upsampling mode, I have been facing some long drop-outs (a few seconds) every hour or so.
Hope others continue to enjoy 
Interesting. I've been using Audivarna 2.5 today with AIR 3 and it's working OK for me but I find it seems to take a few attempts to play another file with a different sample/bitrate to the one I just played - it's not immediate. Maybe 20 seconds or so before it seems to become playable. otherwise it just sits there on 00:00 not doing anything. But I don't have to do anything else.
I seem to remember with earlier versions of AIR that there was an option to set sample/bitrate. Is it my faulty memory? AIR 3 seems to be auto-sensing.
Last night I played a few more songs. I'm not patient enough to wait 20 whole second, so that didn't cross my mind to try. What worked was clicking on the "Stop" button (pauze doesn't work) and after that again selecting the song. It's just a problem when you play songs with different sample rates. Since Guillaume doesn't have this problem with version 1.5 it could be a problem with the interaction between AIR and Audirvana 2.x. I'm going to try some different settings coming weekend.
Yep, I've found exactly the same. The '20 seconds' was a bit of an exaggeration. I tried again and it's maybe 5-10 seconds with stop/play perhaps repeating it a few times. It's not a big deal but is a little confusing.
(12-May-2016, 07:29)Rufus McDufus Wrote: [ -> ]Yep, I've found exactly the same. The '20 seconds' was a bit of an exaggeration. I tried again and it's maybe 5-10 seconds with stop/play perhaps repeating it a few times. It's not a big deal but is a little confusing.
Well it can certainly become a problem when you are listening to a playlist on Qobuz with different sampling rates for every two or three tracks...
Yes, I can see that would be a problem!
Looks like I am the the first to be the bearer of bad news on plain 16/44
I have twice had stuttering followed by silence. Pausing and restarting allows the music to restart
The console log on both occasions contained ...
12/05/2016 08:40:43.000 kernel[0]: IOAudioStream[<ptr>]::clipIfNecessary() - Error: counted 1 clip more than one buffer ahead errors.
This is on a 2014 mac mini using iTunes over ethernet using all the latest software
(12-May-2016, 08:45)canyelles Wrote: [ -> ]Looks like I am the the first to be the bearer of bad news on plain 16/44
I have twice had stuttering followed by silence. Pausing and restarting allows the music to restart
The console log on both occasions contained ...
12/05/2016 08:40:43.000 kernel[0]: IOAudioStream[<ptr>]::clipIfNecessary() - Error: counted 1 clip more than one buffer ahead errors.
This is on a 2014 mac mini using iTunes over ethernet using all the latest software
Hi canyelles,
Probably worth sending to support@
devialet.com if you did not do already
Well, I've never had many dramas with AIR on 16/44 but it never worked on 24/96 or beyond. Now it even plays 24/192 so there's definitely an improvement.
I'm running it through Amarra. Too early to say anything about the sound quality because I normally don't listen to this kind of music.
(12-May-2016, 08:48)SwissBear Wrote: [ -> ] (12-May-2016, 08:45)canyelles Wrote: [ -> ]Looks like I am the the first to be the bearer of bad news on plain 16/44
I have twice had stuttering followed by silence. Pausing and restarting allows the music to restart
The console log on both occasions contained ...
12/05/2016 08:40:43.000 kernel[0]: IOAudioStream[<ptr>]::clipIfNecessary() - Error: counted 1 clip more than one buffer ahead errors.
This is on a 2014 mac mini using iTunes over ethernet using all the latest software
Hi canyelles,
Probably worth sending to support@devialet.com if you did not do already
Done
Jumping on this thread, I'm having quite disappointing results with this AIR 3 Beta version on Mac.
I installed it on my dedicated RoonServer on a (old) MacMini (2009), connected via USB to the Devialet and via Ethernet/Wi-Fi for AIR (MacMini=>Ethernet=>Switch=>Router=>WiFi=>Devialet...).
Once AIR is configured in Roon (same settings as Jnan), I can only play for a couple of seconds (about 5) and then the music stop, whatever the bitrate of the file.
So, I reverted to USB!
Perhaps you guys who are having problems with roon could look at the console log to see if there are any relevant errors at the time it goes wrong.
All good news on air 3 from me. I have a pretty simple setup in comparison to many of you out there on the leading edge;
Mac mini 2012 running el capitain => iTunes or Qobus => wifi (5ghz) => AirPort Extreme => Ethernet => devialet 800
Listening for several hours last night, drop out free compared to air 2 which would have dropped out at probably once an hour.
I also tried eliminating the Ethernet connection to the devialet and instead using wifi end-to-end. This had previously been unacceptable because drop outs / white noise would occurring every few minutes. Only listened for 1/2 hour or so, but no dropouts at all!
On SQ - not so sure - I've just taken delivery of new speakers so I'm still 'learning' my new system but I couldn't honestly say there was a significant improvement. However I do have a spare MacBook that I will setup with air 2, mirror the rest of the config and do some a/b comparisons.
Happy Days
Sent from my iPad using Tapatalk