cawgijoe
Emo VIPs
"We made too many of the wrong mistakes." - Yogi Berra
Posts: 4,914
|
Post by cawgijoe on Oct 14, 2015 20:55:05 GMT -5
Too late for me tonight. I'll do the update tomorrow after work. Sounds good rhough.
|
|
|
Post by wizardofoz on Oct 14, 2015 22:13:54 GMT -5
Well on my stereo rig I have done the update...so dsotm SACD is playing fine on the oppo with no noises skipping or stopping the disk tracks, and best of all no missing audio without the tv being on. BUT WHEN SWITCHING THE TV ON WHILE PLAYING ITS A DIFFERENT STORY....CRACKS AND POPS ABOUND, now I expect an audio mute while the HDMI resumes but not nasty noises. So as usual still some work to do in the HDMI department Now the DSD rate seems to display correctly too so that's good. Now where is the sleep feature...this thing runs linux so it's got a clock in there...let's use it...and have it optionally displayed too on the front
|
|
|
Post by millst on Oct 14, 2015 22:40:21 GMT -5
Tried a Game of Thrones blu-ray that was acting up on 3.0. The clicking/popping sounds were gone. Hasn't happened to me very often, but I definitely won't miss it. My biggest issues have been resolved: 1) Bad sample rate on digital output 2) Missing or broken network interface commands 3) OSD glitches I'm interested in the high output mode since I have to crank my trims in my second zone. Can any one from Emotiva comment on some specific situations that would lead to "note that, when set this way, very loud content may clip." KeithL, maybe? -tm
|
|
novisnick
EmoPhile
CEO Secret Monoblock Society
Posts: 27,230
|
Post by novisnick on Oct 14, 2015 22:40:48 GMT -5
How long does the typical install take?
|
|
|
Post by millst on Oct 14, 2015 22:42:27 GMT -5
Less than 15min for everything. Unless it bricks.
-tm
|
|
|
Post by wizardofoz on Oct 14, 2015 23:01:13 GMT -5
Here is the result of turning on the tv and off again while a DSD is playing on the oppo105. Note this does not happen on other HDMI sources like set top box that I have tried so far. This the volume was turned down a lot as the speakers get close to vmax excursion limits!!! Nice to see the bitrates correct and the app works now too
|
|
|
Post by doc1963 on Oct 14, 2015 23:09:00 GMT -5
I, also, can confirm that 3.1 has fixed my three biggest issues.... "DSD thump", "erratic OSD" and "random blocks of color upon boot up". Bravo... The only other bothersome issue that I've encountered is the infamous chopping off of the first few milliseconds of "certain" CDs mastered using absolute digital silence at track "lead in" (of which I seem to have more than a few). Since Keith has already confirmed that this is a " hardcoded" DSP muting issue, I don't expect this to ever change, but I will toss one of my troublesome CDs in anyway (at some point) to see if there is much of a difference. Since I play almost all of my "digital" music collection from CD rips through JRiver or (formerly) Audirvana, and have long since figured out a way around the issue, I'm not much bothered by it if there is no change. Thank you, Team Emotiva, for putting these issues to rest. It's nice to be able to turn my OSD "on" again and to be able to play a SACD without the fear of pressing "stop" before remembering to press the "mute" button.....
|
|
novisnick
EmoPhile
CEO Secret Monoblock Society
Posts: 27,230
|
Post by novisnick on Oct 14, 2015 23:09:39 GMT -5
Is it the DAT file that has the update that goes on the zip drive?, this is my first update of an Emo product. Please excuse my ignorance.
|
|
|
Post by doc1963 on Oct 14, 2015 23:14:59 GMT -5
Is it the DAT file that has the update that goes on the zip drive?, this is my first update of an Emo product. Please excuse my ignorance. Yes. For safety's sake, make sure you format (Fat32) the USB thumb drive first.
|
|
Lsc
Emo VIPs
Posts: 3,348
|
Post by Lsc on Oct 14, 2015 23:21:35 GMT -5
Is it the DAT file that has the update that goes on the zip drive?, this is my first update of an Emo product. Please excuse my ignorance. Either that or one of the 2 PDFs.
|
|
novisnick
EmoPhile
CEO Secret Monoblock Society
Posts: 27,230
|
Post by novisnick on Oct 14, 2015 23:25:16 GMT -5
Thanks, got it. I love the smoke coming out of the top!!
|
|
novisnick
EmoPhile
CEO Secret Monoblock Society
Posts: 27,230
|
Post by novisnick on Oct 14, 2015 23:29:33 GMT -5
Heres a picture of the screen of my XMC-1 after the new update! Love it!
|
|
|
Post by total2727 on Oct 14, 2015 23:45:51 GMT -5
Went without a hitch, love the new options for the main menu. SACD with oppo fixed.
|
|
|
Post by mick on Oct 14, 2015 23:49:48 GMT -5
Hi Guys
Updated to 3.1 firmware all went well BUT I have noticed a change on the small screen on the xmc-1.
It used to read YCbCr 8 but now reads YCbCr 4448 just wondering if this is ok or not?
thanks Guys
|
|
|
Post by doc1963 on Oct 14, 2015 23:57:24 GMT -5
Hi Guys Updated to 3.1 firmware all went well BUT I have noticed a change on the small screen on the xmc-1. It used to read YCbCr 8 but now reads YCbCr 4448 just wondering if this is ok or not? thanks Guys Yes. "YCbCr" represents the colorspace, "444" (4:4:4) is the sampling rate and "8" is the bit depth. It's actually now a tad more informative.
|
|
|
Post by mick on Oct 15, 2015 0:21:09 GMT -5
Hi Guys Updated to 3.1 firmware all went well BUT I have noticed a change on the small screen on the xmc-1. It used to read YCbCr 8 but now reads YCbCr 4448 just wondering if this is ok or not? thanks Guys Yes. "YCbCr" represents the colorspace, "444" (4:4:4) is the sampling rate and "8" is the bit depth. It's actually now a tad more informative. Cheers for the reply, one more question if I could please, If I play a DVD, CD or a movie from a USB it shows 24bits however from Foxtel it shows 20bits even though I have foxtel HD, does this seem right?
|
|
|
Post by wizardofoz on Oct 15, 2015 0:40:49 GMT -5
Mine shows 23bit in Singapore. Odd format but more likely a bug. I'll see what the dc 1 thinks when I'm back next week
At least the remote app is good now.
|
|
|
Post by doc1963 on Oct 15, 2015 1:07:39 GMT -5
Yes. "YCbCr" represents the colorspace, "444" (4:4:4) is the sampling rate and "8" is the bit depth. It's actually now a tad more informative. Cheers for the reply, one more question if I could please, If I play a DVD, CD or a movie from a USB it shows 24bits however from Foxtel it shows 20bits even though I have foxtel HD, does this seem right? Sure... The XMC-1 is reporting what it is receiving from the source device. The bit depth (or word length) is being "padded" at the source. Not a problem as the full resolution of the original is there, the padded data is meaningless. If it went the other way (24 bit > 20 bit), you'd have reasons for concern. The JRiver Wiki has some great information on bit depth and "padding". It's worth a read.....
|
|
|
Post by creimes on Oct 15, 2015 2:16:00 GMT -5
Heres a picture of the screen of my XMC-1 after the new update! Love it!
View Attachmenthmmmm strange I now have this sweet looking display
|
|
|
Post by consul on Oct 15, 2015 4:45:19 GMT -5
Hello,
all works really fine, but I'm really wonder, why no any bi-amping support for 5.1 (or 5.2) configuration was added?..
I was already in contact with Emotiva support regarding bi-amping outputs via XLR... here was the last feedback about this in JANUARY 2015: ---- Bi-amping is pretty hi on the wish list, but we are tackling higher priority items at the moment, like Upgraded Dirac version, and other thing. So I don't have any idea when or if Bi-amping will be available. Or it's sound field capabilities. If we do anything it will just be a re-allocation of the output path of the surr. back channels... outputting the exact same as the fronts. So what ever signal is going to the front (no matter the sound field) the surr. back channels will see the same signal. Like say, I am not sure the functionality or firmware update availability for that feature. ---- Is it means, that bi-amping is technically not possible or never will be realized?..
Best Regards from Germany, Alexander
|
|