|
|
Post by elwicksto on Apr 15, 2010 22:28:54 GMT -5
I just noticed that I had my Oppo bdp-83 in HDMI/LPCM mode (which seemed to be working fine) & changed it to Bitstream mode - using the new Star Trek movie. This resulted in 'No audio' (which has a blinking right justified 'N' for a while before "locking on" to a no audio state) on my UMC-1. When I toggle the Oppo back & fourth between Bitstream & LPCM it always works on the latter, but never the former. Wondering if others are getting their v6 firmware to decode TrueHD bitstreams. Should I re-apply the update???
|
|
|
|
Post by snodog on Apr 15, 2010 23:34:11 GMT -5
Ill pop my Star trek in tomorrow after work and see if it does the same thing. I am going to give mine the works this weekend and find out if everything is working..
|
|
|
|
Post by elwicksto on Apr 16, 2010 0:06:59 GMT -5
sorry! false alarm - i re-applied the update & that fixed it. btw, i had done my original updates on xp, but this time i used a faster win7 laptop, which may have done the trick. thanks anyway, snowdog!!
|
|
ICBM99
Emo VIPs 
When will then be now? ...Soon.
Posts: 1,702
|
Post by ICBM99 on Apr 16, 2010 9:49:21 GMT -5
I posted in another thread specifically about Star Trek BD (which was doing the same thing), I guess I really need to try to re-apply the firmware and see if that takes care of any of the issues I'm having. Do I feel a stomach virus coming on ;D ;D
Did you have any issues installing the firmware the first time?
|
|
|
|
Post by jmilton on Apr 16, 2010 11:08:28 GMT -5
I posted in another thread specifically about Star Trek BD (which was doing the same thing), I guess I really need to try to re-apply the firmware and see if that takes care of any of the issues I'm having. Do I feel a stomach virus coming on ;D ;D Did you have any issues installing the firmware the first time? I ran Star Trek w/TrueHD and it played well on mine. However, does anyone have a UMC that has a working EmoQ? |
|
|
|
Post by brettjb on Apr 16, 2010 12:39:51 GMT -5
However, does anyone have a UMC that has a working EmoQ?Define working.  Mine ran, and it nailed the speaker distances last night (even the subs were within a foot). Crossover settings were still wonky, but easily correctable (though it amused me to see FL set to 20Hz, FR was at 250Hz). Subs are no longer set to "destroy the foundation" levels - in fact, they may be a bit low... Once the crossover points were corrected, the sound was great. I'll run REW this weekend to further tweak the settings, but I think the EMOQ settings (outside of the crossovers) are a great starting point. --Brett |
|
|
|
Post by why1504 on Apr 16, 2010 12:54:50 GMT -5
However, does anyone have a UMC that has a working EmoQ?Define working. Mine ran, and it nailed the speaker distances last night (even the subs were within a foot). Crossover settings were still wonky, but easily correctable (though it amused me to see FL set to 20Hz, FR was at 250Hz). Subs are no longer set to "destroy the foundation" levels - in fact, they may be a bit low... Once the crossover points were corrected, the sound was great. I'll run REW this weekend to further tweak the settings, but I think the EMOQ settings (outside of the crossovers) are a great starting point. --Brett The crossover adjustment may be correct depending on your room, type of speakers and Mic locations. It would also depend on the room configuration. |
|
|
|
Post by jmilton on Apr 16, 2010 13:50:10 GMT -5
However, does anyone have a UMC that has a working EmoQ?Define working. Mine ran, and it nailed the speaker distances last night (even the subs were within a foot). Crossover settings were still wonky, but easily correctable (though it amused me to see FL set to 20Hz, FR was at 250Hz). Subs are no longer set to "destroy the foundation" levels - in fact, they may be a bit low... Once the crossover points were corrected, the sound was great. I'll run REW this weekend to further tweak the settings, but I think the EMOQ settings (outside of the crossovers) are a great starting point. --Brett Close enough to be workable. Mine had everything off...distances at 30ft, xovers @ 250 and noEQ settings for any of the speakers. I took pics of my settings prior to the upgrade and was able to re-set the speakers to their working glory...but I had hoped the EmoQ would have been usable like v5. |
|
|
|
Post by roadrunner on Apr 16, 2010 13:51:38 GMT -5
However, does anyone have a UMC that has a working EmoQ?Define working. Mine ran, and it nailed the speaker distances last night (even the subs were within a foot). Crossover settings were still wonky, but easily correctable (though it amused me to see FL set to 20Hz, FR was at 250Hz). Subs are no longer set to "destroy the foundation" levels - in fact, they may be a bit low... Once the crossover points were corrected, the sound was great. I'll run REW this weekend to further tweak the settings, but I think the EMOQ settings (outside of the crossovers) are a great starting point. --Brett Based upon your post, I would have to say that EmoQ in v6 is now "working". Getting the xover readings you mentioned simply tells you that something in your room (or the positioning of the mike) is causing a 3+ dB dip in the FR speaker -- nothing more. Lonnie's EmoTV presentation on EmoQ fully explains how and why you might get such readings. As you mentioned, this is something that the user can easily manually change to match what you know your speaker's performance specs. This is not a bug or a flaw in EmoQ. This tool simply has detected that there is a 3+ dB dip in the FR speaker's frequency response. By examining the bands that EmoQ boosts EQ you can more easily identify where your room's problem areas are. Enjoy. |
|
|
|
Post by elwicksto on Apr 16, 2010 17:51:08 GMT -5
I posted in another thread specifically about Star Trek BD (which was doing the same thing), I guess I really need to try to re-apply the firmware and see if that takes care of any of the issues I'm having. Do I feel a stomach virus coming on ;D ;D Did you have any issues installing the firmware the first time? yes, i had issues, which lead me to update my firmware 3 times: 1st) on slow, old centrino xp laptop - this resulted in no audio at all (which others have seen) 2nd) same xp machine - until i tried TrueHD content in bitstream mode, i thought things were working, however i did note some slowness/audio issues (mostly slow audio acquisition) during tv channel changes 3rd) on 'newer' lenovo t61 win7, using latest usb drivers. - TrueHD _immediately_ worked after this, and it dramatically improved channel changes. since then i've only found one very minor (at least to me) issue: i have noted a ~3 times when i switch tv channels and it will report the correct audio format but no sound comes out. in all cases when i re-switch to same channel it was corrected - i consider this a very small problem. this seems to happen about once in ~30 channel changes. _my_ experience is consistent with Dan/Lonnie's message that there may be some FW update problems on some xp machines. when i got TrueHD working, both audio and video were _spectacular_. i mean really - really good. whatshername even immediately noticed! i would really recommend to folks that are still having problems to use win7 on a not too old/slow machine or have emo help. the firmware update can be a pain but when all the bits are in the right order life is good. <warning - speculation with very little data> i also have a theory on one possible problem, which is supported by a failed update experience i had in between my 1st & 2nd update: during the second (UMC-1_v6_02_04_20100413.upg) fw download the umc can 'accidentally' start to re-apply the dsp update that the umc runs after the 1st (DSP1Flash_v1_03_04_20100401.upg) download. The umc's internal updater gets reset by 2nd fw download and that leaves some internal corrupted state. (this sort of happened once to me - the umc started doing the 0% -> 100% counting on the screen, but no other text was being displayed) </warning - speculation with very little data> |
|
|
|
Post by BillBauman on Apr 16, 2010 20:38:17 GMT -5
elwicksto, thank you very much for posting. This information could turn out to be quite valuable to the community.
|
|
