|
|
Post by mickseymour on Oct 16, 2015 8:18:25 GMT -5
The 3.1 upgrade went smoothly. Unfortunately, it has made no difference to the clicks and pops between Blu-ray/DVD logos, trailers and extras.
If I turn off Dirac, I don't get the clicks and pops, which is the same result as with 3.0. I did a fresh Dirac run with 3.1 installed to see if that made a difference and it didn't.
As this is a problem only when using Dirac I'm hoping this doesn't come under the "It is in the DSP over which we have no control" banner. Looks like I'm going to have to call the USA and log a proper support ticket.
|
|
|
|
Post by creimes on Oct 16, 2015 9:48:33 GMT -5
Has anyone else noticed that when you select the OSD display for Bitstream and are using the tuner the artist info scrolls accross the display, pretty cool, if that's your cup of tea  |
|
|
|
Post by mshump on Oct 16, 2015 9:58:05 GMT -5
Just did the Firmware upload. Smooth as silk !!
|
|
|
|
Post by novisnick on Oct 16, 2015 10:16:38 GMT -5
Has anyone else noticed that when you select the OSD display for Bitstream and are using the tuner the artist info scrolls accross the display, pretty cool, if that's your cup of tea What are your settings, mine doesn't do this. Also, when I went to tuner and changed channels, after that I tried going to Cable ( HDMI 1 ) and the app went into a crash, tryed to start over and crashed again. Only after using the Emo remote to go to cable did the crash stop. Bery strange, something may be amiss here. Is there a crash or bug thread for reporting problems with 3.1??? |
|
|
|
Post by fludimir on Oct 16, 2015 11:33:53 GMT -5
Just updated, xmc works ok, however most of my issues didnt solved: loud(can even damage speaker!) pops/clicks when switch from/to sacd content with oppo105 - still exist, despite of what "Fixed thump when going from DSD to various other modes/tracks." in changelog digital silence clicks also heared, however nobody promised to fix that  my xpa5 still powers on-off-on by xmc trigger while xmc starts slow menu updating and visual artifacts on led display goo.gl/LNJoF9 - looks like solved, thanks at least for that! But how many years will required to fix other important issues? Some new minor issue - I have both oppo105 hdmi outputs connected to xmc, oppo hdmi2(with dsd support) to xmc hdmi1 and oppo hdmi1(where oppo outputs sacd in pcm format) to xmc hdmi3. Both hdmi1 and hdmi3 in xmc has configured to use "reference stereo" mode for stereo and auto for 5.1. When I play sacd on oppo and on xmc switching from hdmi1 to hdmi3 - it sets DolbyPLX mode instead of "reference stereo". And also lot of loud pops happens when I do that |
|
|
|
Post by geebo on Oct 16, 2015 11:36:53 GMT -5
Just updated, xmc works ok, however most of my issues didnt solved: loud(can even damage speaker!) pops/clicks when switch from/to sacd content with oppo105 - still exist, despite of what "Fixed thump when going from DSD to various other modes/tracks." in changelog digital silence clicks also heared, however nobody promised to fix that my xpa5 still powers on-off-on by xmc trigger while xmc starts slow menu updating and visual artifacts on led display goo.gl/LNJoF9 - looks like solved, thanks at least for that! But how many years will required to fix other important issues? Other people report the DSD thump is gone and it is for me. You might try to backup your configuration, restore factory defaults and power down at the rear switch followed by a config restore. |
|
|
|
Post by creimes on Oct 16, 2015 12:14:57 GMT -5
Has anyone else noticed that when you select the OSD display for Bitstream and are using the tuner the artist info scrolls accross the display, pretty cool, if that's your cup of tea What are your settings, mine doesn't do this. Also, when I went to tuner and changed channels, after that I tried going to Cable ( HDMI 1 ) and the app went into a crash, tryed to start over and crashed again. Only after using the Emo remote to go to cable did the crash stop. Bery strange, something may be amiss here. Is there a crash or bug thread for reporting problems with 3.1??? I went into settings and changed the OSD to Bitstream setting and when listening to FM radio the artist info is displayed largely across the front OSD. |
|
|
|
Post by novisnick on Oct 16, 2015 12:17:04 GMT -5
What are your settings, mine doesn't do this. Also, when I went to tuner and changed channels, after that I tried going to Cable ( HDMI 1 ) and the app went into a crash, tryed to start over and crashed again. Only after using the Emo remote to go to cable did the crash stop. Bery strange, something may be amiss here. Is there a crash or bug thread for reporting problems with 3.1??? I went into settings and changed the OSD to Bitstream setting and when listening to FM radio the artist info is displayed largely across the front OSD. I guess our little towns radio station doesnt broadcast that info. on another note, my iPad app crashed afet trying to change back to HDMI 2, ive since reported it to Emotiva HQ. |
|
|
|
Post by creimes on Oct 16, 2015 12:20:20 GMT -5
Oh yeah some FM stations don't offer that I guess, like the local college station I mostly listen to does not either but the main FM station in my city does  |
|
|
|
Post by creimes on Oct 16, 2015 12:20:58 GMT -5
And I do have the XMC-1 app on an old iPhone I have but rarely use it |
|
|
|
Post by millst on Oct 16, 2015 13:29:55 GMT -5
Just updated, xmc works ok, however most of my issues didnt solved: loud(can even damage speaker!) pops/clicks when switch from/to sacd content with oppo105 - still exist, despite of what "Fixed thump when going from DSD to various other modes/tracks." in changelog digital silence clicks also heared, however nobody promised to fix that my xpa5 still powers on-off-on by xmc trigger while xmc starts slow menu updating and visual artifacts on led display goo.gl/LNJoF9 - looks like solved, thanks at least for that! But how many years will required to fix other important issues? Other people report the DSD thump is gone and it is for me. You might try to backup your configuration, restore factory defaults and power down at the rear switch followed by a config restore. I second the full power down. I don't run into the pops/clicks very often (less often with 3.1 vs 3.0), but two or three times it has started happening often, e.g. on volume changes, and a reset resolves it. -tm |
|
|
|
Post by Chuck Elliot on Oct 16, 2015 13:47:05 GMT -5
Update with no problems.
Love the fact that a saved configuration is now XML! Good move!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Oct 16, 2015 13:56:39 GMT -5
Update with no problems. Love the fact that a saved configuration is now XML! Good move! Chuck, Is your pc app still compatible with 3.1 ? I was trying to get connected last night and I wasn't getting any options in my app.. Oops.. just saw that you were already aware in your own thread.. lol.. standing by. |
|
KeithL
Administrator 
Posts: 10,276
|
Post by KeithL on Oct 16, 2015 14:06:58 GMT -5
Yes.
The new v3.1 firmware can read config files saved using older firmware.
(However, older firmware cannot read the XML config files saved by the newer version.)Will the XMC with firmware 3.1 still be able to read the old config file format?
|
|
jenix
Minor Hero
Posts: 42
|
Post by jenix on Oct 16, 2015 14:11:53 GMT -5
Yes.
The new v3.1 firmware can read config files saved using older firmware.
(However, older firmware cannot read the XML config files saved by the newer version.)Will the XMC with firmware 3.1 still be able to read the old config file format? Keith, Is the audio level now in the HDMI input setup (3.1) the correct way to address low audio when using audio "pass-through". Any danger in setting it around +10 as that would probably be the amount needed to correct the imbalance between audio from my TiVo through the XMC vs direct to the TV. Thanks ! |
|
LCSeminole
Global Moderator
Res firma mitescere nescit.
Posts: 20,867
|
Post by LCSeminole on Oct 16, 2015 18:57:56 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. I find the chroma subsampling and bit depth to be a nice touch. |
|
|
|
Post by markc on Oct 16, 2015 22:53:37 GMT -5
The 3.1 upgrade went smoothly. Unfortunately, it has made no difference to the clicks and pops between Blu-ray/DVD logos, trailers and extras. If I turn off Dirac, I don't get the clicks and pops, which is the same result as with 3.0. I did a fresh Dirac run with 3.1 installed to see if that made a difference and it didn't. As this is a problem only when using Dirac I'm hoping this doesn't come under the "It is in the DSP over which we have no control" banner. Looks like I'm going to have to call the USA and log a proper support ticket. I think this is the problem that Keith said is deep in the hardware code that they have no solution for and this is now the only irritating problem that affects me. The OSD flashing I had is now all sorted with 3.1 which is nice!
Like you though, it does strike me as odd that the clicks, faint pops, crackles and wibbles only occur when Dirac is enabled. I use Dirac for movies but not music and so am affected when I play Blu-rays.
I get the problem on the PS3 menu, others get it on set-top-box / cable / Netflix menus and had put it down to the digital zero problem and a muting circuit on/off/on/off type of problem with digital silence.
This doesn't explain though why the XMC-1 alone does not have this problem but the XMC-1 with Dirac enabled does.
I will do some proper Dirac on/off testing later and report back what is the definite pattern on my system. If this is only occurring with Dirac enabled then maybe there is a solution as it seems odd if the XMC-1 "direct" does not generate these clicks and crackles but tag a Dirac filter on the end of the processing chain and there they are.
Addendum: after testing, the clicks, crackles and faint pops are there with Dirac either on or off. They are just more noticeable in my system (by about 5dB( with Dirac on, even though the overall volume with Dirac enabled is slightly lower due to my Dirac filters. Back to the drawing board, but it looks like Emotiva can't fix this if it is DSP hardware related as Keith stated.
|
|
|
|
Post by wizardofoz on Oct 16, 2015 23:49:41 GMT -5
Keith, Is the audio level now in the HDMI input setup (3.1) the correct way to address low audio when using audio "pass-through". Any danger in setting it around +10 as that would probably be the amount needed to correct the imbalance between audio from my TiVo through the XMC vs direct to the TV. Thanks ! As far as I can tell the HDMI pass through has better volume now and seems to be working more consistently - I was on FQ-V2 before so maybe 3.0 also had some improvements I missed. I fount the higher output setting too high compared to normal and especially as it also bumps the REC and line out levels which I use between to XMC-1 systems. The DSD issues on swapping from and to the oppo inputs is really annoying / or powering off and on the TV when using audio only...doesnt happen with my other HDMI sources like ATV and cable settopbox etc. DIRAC is not in use on either of the XMC-1's yet. |
|
|
|
Post by markc on Oct 17, 2015 1:19:24 GMT -5
The quote didn't work. This is what fludmir said that I am responding to: my xpa5 still powers on-off-on by xmc trigger while xmc starts
I have two XPA-5 triggered from my XMC-1 and although I usually use "soft start" from "video on standby" mode, I have just confirmed that it does not occur for me with a full reboot from cold with the energy efficient power saving mode.
There surely has to be a difference in the way yours is configured which means yours does this and mine doesn't. It would drive me crazy to have this power cycling of the amp twice with the relays activating unnecessarily!
What are your trigger settings, your input on start-up settings and your hardware connected to that input and via what type of connection? Collectively we must be able to troubleshoot this for you!
My XMC-1 is configured to start up with HDMI 1 which has my HTPC on it. The HTPC may be on or in sleep mode, it doesn't change the triggers. Similarly, the TV display could be already on or off, it doesn't change the powering up of the XPA-5 triggering.
Trigger settings for Triggers 1&2 which have the two XPA-5's on are: Power: Zone 1 checked, zone 2 unchecked (I don't use zone 2 anyway) Inputs: All checked Speakers: All checked (I have 7.1) Headphones: Override checked (I think this must be default, I don't use headphones)
I hoped the new 3.1 firmware function of XML saving of the XMC-1's configuration settings will allow a dump of settings to a forum to troubleshoot and I bet Emotiva put this function in so that they can do just this when someone contacts customer support with a possible problem. It's much quicker and efficient to ask someone to send you a dump file of the settings than to go through each setting one by one with a customer on the phone to check where a problem may lie when, as in this case, it must be a configuration issue. However, when I open the file, it has a lot of gibberish characters with various Unicode settings and I couldn't get anything meaningful from it.
|
|
|
|
Post by wizardofoz on Oct 17, 2015 1:58:10 GMT -5
I have 2 XMC-1's and I don't recall either having any trigger issues when powering up from full off or hot standby.
I have an ATI-6012 amp on one with trigger 1, and 2 XPA-5's daisy chained on trigger 1 on the other unit.
I am overseas for a few more days but will double check this when I get back.
|
|
