|
Post by skippy1977 on Nov 14, 2015 7:49:37 GMT -5
Thanks Guys, Carlito, I have a power conditioner that is really sensitive to any fluctuations in elect. power and shuts down quickly if there is any problem. I have a 64 inch Sammy plasma. Sorry that I cannot address the comment./question about "pure audio mode" as I don't know what that is? IF anybody has any help, it will be much appreciated. God Bless, Wayne Wayne, If you are playing music with your plasma on to get the display to go dark hit the pure audio mode on the Oppo remote. The pure audio mode turns off all video output from the Oppo.
|
|
|
Post by texthai on Nov 14, 2015 7:56:52 GMT -5
Thanks, I will dig that remote out of the pile and try it. I know what you mean now, I was thinking of something on the XMC-1, So, IF I play that way, it will sort out having the TV off (so the plasma won't burn in on one source so long), not having to turn the TV on or off, should not be any thump then, but it will still be there IF I accidentally change inputs--yeah, it has been known to happen. And I can see if that stops the thump when I stop playing DSD and go back to another format. Thanks, God Bless, Wayne
|
|
|
Post by skippy1977 on Nov 14, 2015 8:10:31 GMT -5
Thanks, I will dig that remote out of the pile and try it. I know what you mean now, I was thinking of something on the XMC-1, So, IF I play that way, it will sort out having the TV off (so the plasma won't burn in on one source so long), not having to turn the TV on or off, should not be any thump then, but it will still be there IF I accidentally change inputs--yeah, it has been known to happen. And I can see if that stops the thump when I stop playing DSD and go back to another format. Thanks, God Bless, Wayne Wayne, My thoughts are if the possibility of a power draw or surge is causing the thump when turning their display on or off would cycling in and out of pure mode do it as well. Just a thought. I use the pure audio mode for exactly the reason you mention in regard to burn in on my plasma.
|
|
|
Post by tbadalaty on Nov 14, 2015 9:11:15 GMT -5
Anyone have a problem when zone to only is powered on and there is no audio and a cycle through inputs is necessary for audio to start? Let me know this was not an issue till firmware update.
|
|
|
Post by tbadalaty on Nov 14, 2015 9:13:23 GMT -5
I meant zone two sorry
|
|
hemster
Global Moderator
Particle Manufacturer
...still listening... still watching
Posts: 51,921
|
Post by hemster on Nov 14, 2015 9:21:14 GMT -5
Anyone have a problem when zone to only is powered on and there is no audio and a cycle through inputs is necessary for audio to start? Let me know this was not an issue till firmware update. I use zone 2 to pipe music to my lanai via wireless speakers. I haven't tried that after the latest firmware upgrade though as I've been traveling. Will try out later tonight/tomorrrow and update the thread.
|
|
|
Post by wizardofoz on Nov 14, 2015 19:39:16 GMT -5
You bring up an interesting point which nobody seems to have explored in detail before.... Could it possibly be that the "mystery thump" is plain old electrical noise which is being indirectly caused by the switching event. For example, if the screen on the plasma TV goes dark for a moment when you switch sources, then gets bright again, the change in the amount of power drawn by the screen might be causing enough of a jump in the amount of power consumed by the set to send a noise spike through your power lines - or even through the air. And, if that's happening, it's probably only going to happen with plasma sets, or even with certain specific sets. (And it's quite possible that our DACs, or the circuitry in the Oppo, might be more sensitive to that specific type of noise in DSD mode.) And, if that's the case, it might make sense to try a different power filter, or even move the Oppo or the XMC-1 to a different power outlet, and see if that makes any difference. (If this were the case, then it would make sense that our firmware fix for the other situation would have no effect on it... just a thought.) When listening to dsd I often turn off the tv just to save power and erroneous electrical noise interfering with system signals. If my xmc-1 is designed to play dsd then it should do so without being impacted by other equipment events. That said the issue is known and support/design is working to correct it. No Keith I don't think that's it as its only ever during DSD playback that this occurs, with exactly the same cables ports tv etc using PCM or bitstream from the oppo no thumps blips or pops at all. I can try it right now as I'm 6500kms away down under doing pool fences, but I will try just switching the tv inputs. I'll also have to try to find a a way to get DSD output from another device like maybe PC or Mac via HDMI.
|
|
|
Post by Cory Cooper on Nov 14, 2015 21:22:12 GMT -5
I may have identified another 3.1/3.1a bug. When any input is setup for audio input via optical, I cannot change the audio decoding/processing mode setting...i.e. Auto/Stereo/Surround/etc. You can select different modes, it shows on the OSD and front panel display as a different mode, but it remains on the current setting. It works fine when using HDMI connection for audio. This happens with three different input sources - Comcast DVR, Apple TV 3, and OPPO BDP-95. I have performed a Factory Reset with no change. Anyone else? C I am still having this issue with the optical inputs. I have experienced this issue under both the 3.1 and 3.1a firmware updates, have performed several factory resets, tried different cables and optical inputs, tried pretty much every type of source/output/channel setting from all devices - Bitstream, PCM, DD, DTS, 2.0, 5.1, etc. This issue was not present under firmware 3.0. -Is it possible to downgrade to 3.0 from 3.1a? -Has anyone else experienced this issue? C
|
|
|
Post by skippy1977 on Nov 15, 2015 10:59:18 GMT -5
I just checked to see if the DSD thump was there with 3.1a. I tried the different scenarios such as cycling between DSD/PCM, stopping an SACD with DSD and turning my Panasonic plasma on and off. I get no thumps at all as with 3.1. The one factor that could be different in my system than with others is that I have my plasma plugged into a different circuit than all my other components. Maybe for those getting the DSD thump when turning their TV on and off should try plugging it into another circuit.
|
|
|
Post by texthai on Nov 15, 2015 13:06:35 GMT -5
Thanks to check that out!!!! My TV is plugged into a totally different circuit. I still have the thump. But when I run the Oppo to convert DSD to PCM, then and only then do I get rid of the thumps. Thanks, God Bless, Wayne
|
|
|
Post by tbadalaty on Nov 15, 2015 13:58:47 GMT -5
Anyone have a problem when zone to only is powered on and there is no audio and a cycle through inputs is necessary for audio to start? Let me know this was not an issue till firmware update. I use zone 2 to pipe music to my lanai via wireless speakers. I haven't tried that after the latest firmware upgrade though as I've been traveling. Will try out later tonight/tomorrrow and update the thread. Any word on zone 2 issue
|
|
|
Post by Cory Cooper on Nov 22, 2015 21:51:05 GMT -5
I may have identified another 3.1/3.1a bug. When any input is setup for audio input via optical, I cannot change the audio decoding/processing mode setting...i.e. Auto/Stereo/Surround/etc. You can select different modes, it shows on the OSD and front panel display as a different mode, but it remains on the current setting. It works fine when using HDMI connection for audio. This happens with three different input sources - Comcast DVR, Apple TV 3, and OPPO BDP-95. I have performed a Factory Reset with no change. Anyone else? C I am still having this issue with the optical inputs. I have experienced this issue under both the 3.1 and 3.1a firmware updates, have performed several factory resets, tried different cables and optical inputs, tried pretty much every type of source/output/channel setting from all devices - Bitstream, PCM, DD, DTS, 2.0, 5.1, etc. This issue was not present under firmware 3.0. -Is it possible to downgrade to 3.0 from 3.1a? -Has anyone else experienced this issue? C UPDATE: I have narrowed this issue down to just the two Mode Selector buttons and the Music & Movie Mode buttons on the remote. I can successfully change the mode by clicking Menu > Main Zone > Surround Mode > and selecting a mode from the list. So, I have a workable solution for now. C
|
|
|
Post by igorzep on Nov 23, 2015 9:46:31 GMT -5
UPDATE: I have narrowed this issue down to just the two Mode Selector buttons and the Music & Movie Mode buttons on the remote. I can successfully change the mode by clicking Menu > Main Zone > Surround Mode > and selecting a mode from the list. So, I have a workable solution for now. I can confirm that I have the same issue. I thought I had been able to 'fix' it by changing mode configuration from Stereo to Auto and back to Stereo. It worked OK for a while but the problem returned back again.
|
|
KeithL
Administrator
Posts: 10,002
|
Post by KeithL on Nov 23, 2015 11:57:57 GMT -5
That is certainly weird. We tried, but were unable to duplicate that here...... (You could try re-flashing the firmware.) In answer to someone else's question.... you CAN "update the XMC-1 with older firmware". (The only limitation is that we changed the format in which configuration information is stored; but that is backwards compatible. What that means is that the newest firmware can read configuration files saved with the old firmware, but the old firmware CANNOT read configuration files saved with the new firmware.) UPDATE: I have narrowed this issue down to just the two Mode Selector buttons and the Music & Movie Mode buttons on the remote. I can successfully change the mode by clicking Menu > Main Zone > Surround Mode > and selecting a mode from the list. So, I have a workable solution for now. I can confirm that I have the same issue. I thought I had been able to 'fix' it by changing mode configuration from Stereo to Auto and back to Stereo. It worked OK for a while but the problem returned back again.
|
|
|
Post by Cory Cooper on Nov 23, 2015 18:48:47 GMT -5
Thanks igorzep and KeithL.
Yes, it is a strange issue. I have re-flashed the firmware a couple of times, and have done a couple of factory resets, but the issue persists. I was the one that asked if I could downgrade to 3.0 in a previous post in this thread, but since I have found a work-around, I will leave it as is. If I get some time, I may downgrade to 3.0, use it for a few days, then apply the 3.1/3.1a firmware files to see if it is a case of the firmware not fully applying. Luckily, I have a few USB flash drives that have saved configuration files from 3.0 and 3.1, so I won't lose anything - thanks for the heads-up!
If I find anything new, or if my re-flashing/testing project corrects it, I will let everyone know.
Thanks again and Happy Thanksgiving!
C
|
|
|
Post by wizardofoz on Nov 26, 2015 2:03:23 GMT -5
Some positive OPPO news is that the new BDT-101CI transport seems to be working quite nicely with DSD in one of my XMC-1 setups, powering off the TV doesn't seem to read havoc on the speakers with thumps and pops - I haven't tried an SACD yet - but playing from my Synology NAS is just peachy keen . Ignore the fact the input name says Sony PS3 it is my new Oppo www.oppodigital.com/blu-ray-bdt-101CI/Sexy looking too...less clutter physically and logically with no apps
|
|
|
Post by texthai on Nov 26, 2015 3:46:18 GMT -5
Happy Thanksgiving guys and girls, We are all so very blessed, we need to be thankful!!!!!! And I am thankful!!!!!!! God Bless, Wayne
|
|
|
Post by Cory Cooper on Nov 26, 2015 12:06:27 GMT -5
Thanks igorzep and KeithL. Yes, it is a strange issue. I have re-flashed the firmware a couple of times, and have done a couple of factory resets, but the issue persists. I was the one that asked if I could downgrade to 3.0 in a previous post in this thread, but since I have found a work-around, I will leave it as is. If I get some time, I may downgrade to 3.0, use it for a few days, then apply the 3.1/3.1a firmware files to see if it is a case of the firmware not fully applying. Luckily, I have a few USB flash drives that have saved configuration files from 3.0 and 3.1, so I won't lose anything - thanks for the heads-up! If I find anything new, or if my re-flashing/testing project corrects it, I will let everyone know. Thanks again and Happy Thanksgiving! C UPDATE: I downgraded to 3.0 and the issue was resolved. I then upgraded again to 3.1a and the issue returned. I also did a 3.0 to 3.1 trial and the issue persisted. So, on my XMC-1, using firmware 3.0 corrects the issue. Using either 3.1 or 3.1a, the issue is present. I will continue to use my work-around. Maybe the next revision of the firmware will correct it for my unit. Have a great Thanksgiving! C
|
|
|
Post by hifiaudio2 on Nov 28, 2015 16:42:38 GMT -5
I assume this update will not make me re run Dirac? Nor will it mess with any settings?
|
|
hemster
Global Moderator
Particle Manufacturer
...still listening... still watching
Posts: 51,921
|
Post by hemster on Nov 28, 2015 16:56:37 GMT -5
I assume this update will not make me re run Dirac? Nor will it mess with any settings? I didn't have to rerun Dirac and all my setting remained intact. However for me it's SOP to do a backup of my settings before any update. Just FYI.. you can always use the existing Dirac project if you had to. Not saying you do... but if you had to..
|
|