|
Post by aud on Sept 30, 2014 19:55:03 GMT -5
YES
|
|
|
Post by ansat on Sept 30, 2014 19:59:16 GMT -5
My XMC-1 takes 35 seconds to boot up. Is that normal? Set the standby option to video always on.
|
|
|
Post by badong on Sept 30, 2014 20:01:17 GMT -5
Is that under the "low-power" standby setting.
|
|
|
Post by ansat on Sept 30, 2014 20:13:38 GMT -5
Is that under the "low-power" standby setting. Yes. It will use more power. But it will shorten the time down alot Tony
|
|
|
Post by geebo on Oct 9, 2014 6:51:04 GMT -5
Everyone, Please check and confirm this one...................... When I go to the speaker setup menu and set the back surround speakers to "none", then go to the Equalization menu, I lose the System EQ and Reset Filter selections. The only way to have these features available is when the back surround speakers is set to "2 small". This occurs with both speaker presets. This is not good for 5.1 users. Looks like this may require a firmware update................ Checked with the 1.2 firmware last night. I now get System EQ with backs set to "None".
|
|
|
Post by springwright on Oct 9, 2014 19:32:41 GMT -5
Everyone, Please check and confirm this one...................... When I go to the speaker setup menu and set the back surround speakers to "none", then go to the Equalization menu, I lose the System EQ and Reset Filter selections. The only way to have these features available is when the back surround speakers is set to "2 small". This occurs with both speaker presets. This is not good for 5.1 users. Looks like this may require a firmware update................ Checked with the 1.2 firmware last night. I now get System EQ with backs set to "None". That's a good thing. I'll load my firmware this weekend. What about the Filter Reset function?
|
|
|
Post by geebo on Oct 9, 2014 19:42:22 GMT -5
Checked with the 1.2 firmware last night. I now get System EQ with backs set to "None". That's a good thing. I'll load my firmware this weekend. What about the Filter Reset function? I've been unable to find it but I haven't looked real hard. I didn't find it even with backs enabled.
|
|
|
Post by goozoo on Oct 12, 2014 0:04:00 GMT -5
I have been playing with my XMC-1 as well. One of the bugs is the reduced audio output from HDMI sources. I am running an Oppo 105 via HDMI out into the XMC-1, but have had to set all my levels (except sub) to max to compensate for the low volume. Still have to set the volume to -27db just to watch movies. Has anyone else experienced this as well, or am I missing something.
|
|
edrummereasye
Sensei
"This aggression will not stand, man!"
Posts: 438
|
Post by edrummereasye on Oct 22, 2014 21:52:14 GMT -5
I have been playing with my XMC-1 as well. One of the bugs is the reduced audio output from HDMI sources. I am running an Oppo 105 via HDMI out into the XMC-1, but have had to set all my levels (except sub) to max to compensate for the low volume. Still have to set the volume to -27db just to watch movies. Has anyone else experienced this as well, or am I missing something. Not necessarily a bug... The volume control may work different than you're used to (linear vs. logarithmic)...hard to say without knowing your other equipment, connections, etc. did you calibrate to reference level at volume setting 0? There have been reports of lower volume when using the "Auto" output modes...if you're set to "Auto" for either 2.0 or 5.1 source material on the input that concerns you, try a different mode and see if it's louder. But as long as you have the headroom to get to reference level, it doesn't matter much what volume setting it takes to get there, (except that if you calibrated it to hit reference at '0', then it should do so...if you haven't calibrated, then it means nothing...and if you *don't* have the headroom, you won't be able to calibrate...) That said, it does seem that you have to get "up there" in volume for many sources...and it might be desirable, once more pressing issues are sorted, for Emo to make an adjustment via firmware so more of the volume range is useable...otoh, if -1 dB on the display is really -1 dB in volume, then there's nothing to adjust; it just is what it is...
|
|
edrummereasye
Sensei
"This aggression will not stand, man!"
Posts: 438
|
Post by edrummereasye on Oct 22, 2014 21:59:52 GMT -5
Just noted a display glitch; I don't want to say "bug" because it may be a one-off...just started from "high-power" standby and noticed the display is blank, except when I change something...i.e., change the volume or input or mode..."Rethink..." Screen displays, but display then goes blank until I make something come up...in other words, the normal info display is not appearing. Persisted across a front-panel off/on cycle, Considering this will be my first rear-panel induced, cold boot in approximately 2 months of daily use and one firmware upgrade, I'm not terribly concerned, just thought I should record it here for posterity...no osd either...
Woah... Went into menu, "front bright" was set to '0'....didn't do that and I doubt my kids did...kicked it to 100%, but when I came out, I had only top and bottom lines of display....pressing buttons on the remote caused one of the 9 or so I data fields to be added each time, then back to blank...Interestingly, pressing buttons on the TiVo remote had the same effect, except at one point I was accidentally holding a button down, and it actually caused the volume to display and turn down...then I realized that is actually okay, that particular TiVo remote was programmed to control my UMC-1 many moons ago, so I guess the XMC-1 was responding to valid commands, as it should.
|
|
|
Post by wizardofoz on Oct 24, 2014 1:52:24 GMT -5
I've seen odd display stuff in the old FW as shipped so this seems to be a thing thats still happening in the new FW
I guess there are still some issues to iron out with this display getting corrupted from warm starts and other changes...I think I had it when changing brightness too.
|
|
|
Post by rogersch on Oct 24, 2014 13:39:29 GMT -5
Today I received my XMC-1 (Firmware 1.3).
As I'm living in Europe I tested FM tuning and to me it seems to work. The Europe/Asia setting stays after a power cycle.
But I'm having a serious problem.
I power up the XMC-1 from Low power consumption and after around 35 seconds, when the progress bar has dissapeared, I hear three really load plops from my speakers and sub-woofer. I did a factory reset and re-loaded my backed up settings. Just once there were no load pops. Does anybody else experience this problem? My power amplifiers are switched on via master/slave power strip and are powered up before the boot process of the XMC-1 is finished.
|
|
|
Post by wizardofoz on Oct 25, 2014 8:19:11 GMT -5
I've heard the pops too on the original firmware as shipped 1.0 or 1.1 I forget but I'm not using triggers...seems to be an issue when starting from low standby option (not instant start). I'm still away overseas so no way to test the latest fw for my setup.
|
|
KeithL
Administrator
Posts: 10,273
|
Post by KeithL on Oct 27, 2014 11:23:31 GMT -5
WORKAROUND FOR "it's cutting off the beginnings of songs". We are looking into whether this is happening in a location where we can change the behavior (some code modules are internal to the DSP - and so we can't change them). (Also, since we have to avoid the risk of nasty noises making it through the muting, and we're handling a wide variety of different formats, there are going to be compromises....) That said, there are several factors that together contribute to why only certain people seem to be having this problem. First: you're only going to get muting to begin with if the digital audio stream is interrupted. If you play a series of songs at the same sample rate, most players will play them as part of the same digital audio stream, with no interruption - and so no muting. This means that, when playing an entire disc (like Dark Side of the Moon), the muting shouldn't come on between tracks - because the digital audio stream is never interrupted. However, sequential songs at different sample rates, if played bit-perfect, will require a break in the audio stream every time the sample rate changes. Second: with audio CDs, and other digital audio content, dithering is typically applied as the last step in the audio processing and mastering chain. So, assuming that there is a lead-in consisting of a second of digital silence on the beginning of each track, that silence typically is dithered when the track is mastered. (Dithering is considered to be necessary when creating 16 bit CD content from 24 bit digital masters). Of course, content produced from analog (tape) masters doesn't have to be explicitly dithered because the background noise on the master acts as dither (and background noise should be faded into the track to avoid a sudden jump in noise level at the precise beginning of the track). NOW... for anyone willing to go to the effort of re-ripping tracks... there is a much easier workaround. You really shouldn't re-dither the entire track... because that means that you're altering the audio bits of your music. It's much simpler to simply create one second of DITHERED AUDIO SILENCE (as a separate track), then cut and paste that one second of audio onto the beginning of each affected track. Opening the track, pasting one second of "audio" onto the beginning, then re-saving it, should NOT trigger the editor to alter or re-encode the audio. (You'd simply have to make up a "one second dithered lead in" at each sample rate for which you have files to fix.) Thanks for the feedback bluescale. Unfortunately, much to my dismay, I have no problem reproducing it. Granted, this issue doesn't occur with every track I throw at it, but once you know it "is" there, it becomes an obsession. The tracks I find that "do" exhibit this issue during playback are consistent and repeatable. I've spent much of the entire weekend tweaking settings on the XMC-1, tweaking settings in Audirvana and re-ripping CDs to FLAC (using every setting possible) to overcome this issue. I couldn't fix it. Normally, I use Exact Audio Copy (EAC) as a ripper, but I even went as far as downloading the trial version of dBpoweramp. Unfortunately, that didn't change a thing (although I do like the software). After a long day of trial and error, I decided to take one of the files that I've used (Toto's " Hold the Line" - due to its very sharp and articulate snare drum strike upon the song's intro) into Audacity to study the file. To my surprise, the track has nearly a half second of silence which I thought would have been sufficient to open the gating circuit to the DAC. For the hell of it, I added an additional half second in order to bring it up to a full second of silence. No dice…. It still chopped off "half" of the initial drum strike intro. After thinking long and hard about this, I attempted yet another test. I took the original unaltered FLAC file back into Audacity and re-exported it. This time using shaped " dithering". Dithering is a 16/44.1 mastering technique that adds a trace of inaudible "white noise" to the file to inhibit the least significant bits. It does have useful mastering benefits, but that's a whole different topic. If done correctly, it is entirely inaudible to the listener, but the silent portions of the audio file are never truly "silent". I did this merely to test a theory... The dithered file played perfectly, repeatedly and without issue. Played back-to-back against the unaltered original met with the same repeated results. The unaltered file " clipped" the first half second, the dithered file played flawlessly (including skipping both backwards and forwards to the track start). So… my " theory" is that the gating threshold tolerance of the XMC-1's digital signal path needs a bit of tweaking. The problem seems to manifest itself around " how silent is the digital silence" on the lead in. Also, FWIW, I also found that having Audirvana "up-sampling" the 44.1k FLAC to 96k resulted in the proper playback of all affected files as well. Unfortunately, none of this (short of a permanent fix from Emotiva) will help this same issue coming from my (digitally connected) ERC-2. There's nothing I can do to help the AES/EBU digital path. However, the ERC-2, via the "Reference" analog connection, plays every track without issue. It would be helpful to have anyone who is also experiencing (or notices) this issue… (CLICK HERE) … also report it this thread. Please keep in mind that I'm not referring to the slight delay as the mode is acquired. That slight delay is normal. Doc I have the exact same issue playing FLACs from both a PCH-A400 and a Mede8er through HDMI. Not every track but the majority of them so I do feel your pain.
|
|
|
Post by thecrusherk on Oct 28, 2014 18:29:39 GMT -5
Running firmware 1.2 listening to PCM 2.0 through HDMI in, I noticed that in Direct mode signal is sent to my sub. I would expect that with 2.1 but not 2.0 right? Reference Stereo mode same source and no signal to sub as expected. Anyone else reproduce this. Am I mistaken in my understanding of direct mode and its operation?
|
|
|
Post by multicore on Oct 28, 2014 18:37:55 GMT -5
Running firmware 1.2 listening to PCM 2.0 through HDMI in, I noticed that in Direct mode signal is sent to my sub. I would expect that with 2.1 but not 2.0 right? Reference Stereo mode same source and no signal to sub as expected. Anyone else reproduce this. Am I mistaken in my understanding of direct mode and its operation? "Direct Mode provides a relatively pure listening experience, and eliminates most processing, but still retains bass management." See page 9 of manual.
|
|
|
Post by thecrusherk on Oct 28, 2014 18:46:53 GMT -5
Running firmware 1.2 listening to PCM 2.0 through HDMI in, I noticed that in Direct mode signal is sent to my sub. I would expect that with 2.1 but not 2.0 right? Reference Stereo mode same source and no signal to sub as expected. Anyone else reproduce this. Am I mistaken in my understanding of direct mode and its operation? "Direct Mode provides a relatively pure listening experience, and eliminates most processing, but still retains bass management." See page 9 of manual. Thanks multicore! It was indeed my understanding. It comes to mind now that this was discussed before early on. I will blame a stressful week at work so far. I hope a copy of the manual is posted under the products resources tab soon.
|
|
|
Post by tunatamer on Oct 28, 2014 19:00:00 GMT -5
"Direct Mode provides a relatively pure listening experience, and eliminates most processing, but still retains bass management." See page 9 of manual. Thanks multicore! It was indeed my understanding. It comes to mind now that this was discussed before early on. I will blame a stressful week at work so far. I hope a copy of the manual is posted under the products resources tab soon. emotiva.com/resources/manuals/XMC_user_manual_PRELIMINARY_v01.pdf
|
|
|
Post by robcoff on Oct 29, 2014 12:01:18 GMT -5
I have been playing with my XMC-1 as well. One of the bugs is the reduced audio output from HDMI sources. I am running an Oppo 105 via HDMI out into the XMC-1, but have had to set all my levels (except sub) to max to compensate for the low volume. Still have to set the volume to -27db just to watch movies. Has anyone else experienced this as well, or am I missing something. I noticed the same thing with my Oppo 105. Since I prefer the Oppo's DAC's I use the balanced input on the XMC1 for 2 channel and analogue 7.1 input for multi channel.
|
|
|
Post by rogerlons on Oct 29, 2014 16:58:16 GMT -5
I found that by bumping the HDMI input gains up about 6dB I was able to get very close to the same gain structure between HDMI and the Balanced Ins. Agree that the HDMI input stage is low, but the input gain sure seemed to work well...
|
|