or Connect
AVS › AVS Forum › Audio › Receivers, Amps, and Processors › Anthem D2/D2v/AVM50/AVM50v/ARC1 tweaking guide
New Posts  All Forums:Forum Nav:

Anthem D2/D2v/AVM50/AVM50v/ARC1 tweaking guide - Page 1261

post #37801 of 42717
Quote:
Originally Posted by p.las View Post

Anthem have the responsibility to the costumer. The manufaktur off the chip have a responsibility to anthem. This is how tings work.
If you have a problem witt you car eks Ford ....the Electric vindow jam, when you are open it. The manufaktur of the Electric motor for the Windows don't know how to fix it. The workaround is to not to open the Windows . I don't Think that Will never happens .
I know that anthem can't make the fix. But then there have to make the manufaktur make it - mabye it's time for anthem to not ask nice .
I Can see that you Think that i am a pain in the a.., becurse of my demands. But i have paid a lot of money for this processor. And i Can't not accept that this issue is not to bee fix. I have the right to not accept this.
Hope you understand my english:)

What you are asking is not an unreasonable response to a product problem. But, in reality it may never be possible to get done. Anthem like all other electronic manufacturers purchases chips from all over the world from sources supplying a premade product. The chip manufacturer probably spent years in getting the chip and software developed. The process of fixing software bugs can take an extraordinary amount of time. The product containing the chip may be obsolete by then. The product manufacturer has no control over how the final chip performs. That is why so many companies use the same chips to overcome surprises in software issues. If you do not believe this go to some of the other forum pages and scroll through the issues being talked about. With the issue being talked about here all the companies using the chip are more than likely experiencing the same bug. In Anthem's use in this product we are much more inclined to find and experience problems like this because we are the small section of audiophile and video users who understand exactly how a unit is functioning.
There currently is no high end units that perform bug free. To my knowledge the Anthem is better than almost everyone of them in this regard and that is why I purchased a D2 and then replaced it with a D2v.. If the chip manufacturer cannot get the bug fixed, possibly Anthem can work out a software work-a -round to overcome this problem
post #37802 of 42717
Quote:
Originally Posted by thestewman View Post

What you are asking is not an unreasonable response to a product problem. But, in reality it may never be possible to get done. Anthem like all other electronic manufacturers purchases chips from all over the world from sources supplying a premade product. The chip manufacturer probably spent years in getting the chip and software developed. The process of fixing software bugs can take an extraordinary amount of time. The product containing the chip may be obsolete by then. The product manufacturer has no control over how the final chip performs. That is why so many companies use the same chips to overcome surprises in software issues. If you do not believe this go to some of the other forum pages and scroll through the issues being talked about. With the issue being talked about here all the companies using the chip are more than likely experiencing the same bug. In Anthem's use in this product we are much more inclined to find and experience problems like this because we are the small section of audiophile and video users who understand exactly how a unit is functioning.
There currently is no high end units that perform bug free. To my knowledge the Anthem is better than almost everyone of them in this regard and that is why I purchased a D2 and then replaced it with a D2v.. If the chip manufacturer cannot get the bug fixed, possibly Anthem can work out a software work-a -round to overcome this problem

3 Cheers smile.giftongue.gifsmile.gif

Well Written
post #37803 of 42717
Quote:
Originally Posted by thestewman View Post

What you are asking is not an unreasonable response to a product problem. But, in reality it may never be possible to get done. Anthem like all other electronic manufacturers purchases chips from all over the world from sources supplying a premade product. The chip manufacturer probably spent years in getting the chip and software developed. The process of fixing software bugs can take an extraordinary amount of time. The product containing the chip may be obsolete by then. The product manufacturer has no control over how the final chip performs. That is why so many companies use the same chips to overcome surprises in software issues. If you do not believe this go to some of the other forum pages and scroll through the issues being talked about. With the issue being talked about here all the companies using the chip are more than likely
the same bug. In Anthem's use in this product we are much more inclined to find and experience problems like this because we are the small section of audiophile and video users who understand exactly how a unit is functioning.
There currently is no high end units that perform bug free. To my knowledge the Anthem is better than almost everyone of them in this regard and that is why I purchased a D2 and then replaced it with a D2v.. If the chip manufacturer cannot get the bug fixed, possibly Anthem can work out a software work-a -round to overcome this problem

I don't Think you are wrong. but i don't Think you are right eather.
i don't have any insight in how those things are working.....chip , decider and Electronics - but why issent it possible to implement a new dekoder chip? Becurse it issent a god busines .
If anthem want that issue to bee fixed , then there Will be a fix. Nothing is imposible. It is a matter of priorites..........and money.

Edit:
I have a integra processor also. There issent any decoder bugs of any kind. But my anthem is just the Best sounding processor that have being in my home cinema......and wii are talking about lexicon , primare....you name it. And maby that is why iam so frustrated . I Can not sell my anthem and bye another processor that Sound A's god A's my anthem avm 50v. So frankley - i am maried to it. So it Will be so fu..... Nice if it was working correct.
Edited by p.las - 7/28/12 at 2:47pm
post #37804 of 42717
Quote:
Originally Posted by Bob Pariseau View Post

The Level problem IS fixed (and is still fixed). This is a DIFFERENT problem that only affects 7.1 DTS-HD MA tracks. That problem is in the firmware you are running and has not yet been fixed. Use LPCM input when playing 7.1 DTS-HD MA tracks.
--Bob

Thanks Bob.
Quote:
Installed "test" firmware V3.03. Also re-Uploaded my existing ARC solution, as is my practice.

There's a new nasty in this one. Something is screwed up in the power up sequence. From the looks of the front panel, I suspect power up is crashing and restarting

Have you mentioned your power issue to Nick/Anthem? Lets hope they can replicate it with their units.
post #37805 of 42717
Quote:
Originally Posted by p.las View Post

I don't Think you are wrong. but i don't Think you are right eather.
i don't have any insight in how those things are working.....chip , decider and Electronics - but why issent it possible to implement a new dekoder chip? Becurse it issent a god busines .
If anthem want that issue to bee fixed , then there Will be a fix. Nothing is imposible. It is a matter of priorites..........and money.
Edit:
I have a integra processor also. There issent any decoder bugs of any kind. But my anthem is just the Best sounding processor that have being in my home cinema......and wii are talking about lexicon , primare....you name it. And maby that is why iam so frustrated . I Can not sell my anthem and bye another processor that Sound A's god A's my anthem avm 50v. So frankley - i am maried to it. So it Will be so fu..... Nice if it was working correct.

Peter,
While I understand your frustration, there is a work around that, in my experience, solves the problem without compromise. I haven't noticed any sonic quality difference using LPCM over bitstreaming using my oppo BD83. Increasing our blood pressure over this may be counter productive;)
John
post #37806 of 42717
Quote:
Originally Posted by jayray View Post

Peter,
While I understand your frustration, there is a work around that, in my experience, solves the problem without compromise. I haven't noticed any sonic quality difference using LPCM over bitstreaming using my oppo BD83. Increasing our blood pressure over this may be counter productive;)
John

You proberly right.
There are some drawbacks regards th bdp 83 decoding. But that is only in toy story 3 and jurrasic park i think. Mabye After some time i Will replaced it witt bdp 93- i like that things Being done proberly wink.gif
Thanks smile.gif
post #37807 of 42717
Quote:
Originally Posted by SimonNo10 View Post

. . . .

Have you mentioned your power issue to Nick/Anthem? Lets hope they can replicate it with their units.

Yep. Along with the other stuff. Never, ever, just post problem reports here. Nick would get worried if he didn't get at least one email from me after a firmware release. biggrin.gif


On the DTS-HD MA 7.1 decoding issue, the thing that boggles my mind is that the decoder maker was able to get that decoder certified by DTS in the first place. I mean this is not some weirdly technical mistake on the periphery of common usage. Getting audio decoded into the correct channels is kind of basic. And you know that when the problem report went to the decoder maker, the first thing that must have come back was, "We can't change anything now. The way it is, passes certification." Fortunately, there IS a workaround. It could be worse.
--Bob
post #37808 of 42717
Quote:
Originally Posted by Bob Pariseau View Post

You mean you swapped the speaker outputs AND the trigger, or just the trigger?
Also try this simple test: With the D2v connected to the power amps, try using it with the Trigger wire DISCONNECTED and make sure the power amps don't actually turn on simply because of audio voltage on the feed cables.
Also try using a different trigger output from the D2v. They time sequence with #1 going first and #3 going last.
It's possible, but not all that likely, that this could be a problem of varying ground potential in your power outlets -- i.e,. the outlets themselves, not inside the D2v. Try temporarily powering the D2v and the power amp from the SAME outlet. If that cures the problem, then you may need to get your electrician in to reconnect the separate power outlets to use the same ground -- a relatively simple procedure done inside the circuit breaker box.
--Bob

I swapped out the speaker output and the trigger. I will try what you have suggested and report back.

Thanks.
post #37809 of 42717
Quote:
Originally Posted by Bob Pariseau View Post

Yep. Along with the other stuff. Never, ever, just post problem reports here. Nick would get worried if he didn't get at least one email from me after a firmware release. biggrin.gif
On the DTS-HD MA 7.1 decoding issue, the thing that boggles my mind is that the decoder maker was able to get that decoder certified by DTS in the first place. I mean this is not some weirdly technical mistake on the periphery of common usage. Getting audio decoded into the correct channels is kind of basic. And you know that when the problem report went to the decoder maker, the first thing that must have come back was, "We can't change anything now. The way it is, passes certification." Fortunately, there IS a workaround. It could be worse.
--Bob

No problem Bob and thanks for your continued support and testing. It surprises me with this DTS issue as one would think that the same chips would be going out to other companies like for instance Denon with their flagship pre-pro. I haven't read a single problem being reported with that product and they recently had a major hardware upgrade which from reports is all good. Hope it does get resolved in some way other than the LPCM setting. I will try the latest firmware and see if I get the same issue as you have and report back.
post #37810 of 42717
I just moved the Anthem D2v from our living room to my little home theater and now have the follwing problem: The D2v doesn't recognize any HDMI-audio-signal coming from the dedicated HDMI-audio-out on my DVD iScan DUO. I've tested it with a Panasonic BD-310 and and a Toshiba XE1 HDDVD player. The firmware of the unit is 2.11 and I tried to reach the Anthem homepage to look for a newer firmware, but it seems to be down :-( Is there a new official firmware (newer than 2.11) available? I have to say that my Marantz AV8003 has no problem with recognizing the HDMI audio streams fed from the DUO...
post #37811 of 42717
Quote:
Originally Posted by p.las View Post

You proberly right.
There are some drawbacks regards th bdp 83 decoding. But that is only in toy story 3 and jurrasic park i think. Mabye After some time i Will replaced it witt bdp 93- i like that things Being done proberly wink.gif
Thanks smile.gif

So do most of us:D
John
post #37812 of 42717
Quote:
Originally Posted by p.las View Post

After some time i Will replaced it witt bdp 93- i like that things Being done proberly wink.gif
Thanks smile.gif

Don't waste your MONEY on Oppo.

Buy a Sony BDP-S790 it is way better than any Oppo
post #37813 of 42717
Quote:
Originally Posted by boostie View Post

I swapped out the speaker output and the trigger. I will try what you have suggested and report back.
Thanks.

Ok, tried a few things still the same issue.

I disconnected the 12v trigger and with the power amp OFF and turning the D2v on and off and
I still am getting the popping noise. Looks like it is coming from the anthem via feedback through the amp.

Both units plugged into the same outlet.
post #37814 of 42717
Quote:
Originally Posted by drhankz View Post

Don't waste your MONEY on Oppo.
Buy a Sony BDP-S790 it is way better than any Oppo

I have a masking system on my screen. So i have to shift the subtiles away from the blackbars. That said - i have never owned a component that have so god costumer respons as oppo.There have never being a single problem witt my Unit.
post #37815 of 42717
I've isolated the power up sequence failure in the V3.03 firmware. It has to do with sending a 3-button Source Selector command to the D2v *DURING* power up.

A 3-button sequence allows direct selection of a Source for input. For example THX-8-9 selects the TV1 Source. (See Appendix A in the Manual).

You can send such a sequence during power up and it will be buffered and executed at the right time so that the D2v powers up initially using the Source you want to use.

The new problem in the V3.03 firmware is that this no longer works. When THX-8 is sent at "the wrong time" during power up, the failure happens. No need to send the 9 as well. If you wait until the unit is fully powered up, then commands like THX-8-9 work without problem.

"The wrong time" appears to be roughly 3 seconds after the Power ON command is sent to the D2v.

When the D2v receives Power ON, its Front Panel display immediately lights up with the model announcement text. In addition you get several blue button lights on the front panel. You get Main Path in the upper left, the Source last used for input (when the D2v was previously powered down) in the lower left, and you get Main Power in the lower right.

When the THX-8 is then received at "the wrong time", the Front Panel display goes black and all but one of the blue button lights also turn off. The Main Path light in the upper left remains lit. This is something that should not be able to happen -- i.e., this is not a normal combination of lights and indicators. This is the failure.

MEANWHILE, the D2v is still trying to power up. At a certain point in the power up cycle, the D2v becomes truly live and you hear its muting relays disengaging (the mechanical click). In the failure scenario, at that instant, the Front Panel display turns back on, and the normal button lights also turn back on -- and the D2v is now properly powered up except that the Source Selector command which initiated the failure never got executed so the D2v is using the wrong Source for input (presuming that's different from whatever you last used when you last powered the D2v down).

You can now do Source Selector commands and they will work normally. I.e, once powered up, the D2v appears to function correctly.

All of the above can be made to happen even using the D2v's own remote (assuming you get the timing "wrong"), and with HDMI Sources and the Display left powered down (so it's not HDMI related).

Details on all of the above have been sent to Anthem.
--Bob
Edited by Bob Pariseau - 7/29/12 at 7:49am
post #37816 of 42717
Has anyone tested the 'no audio' HDMI issue that was introduced (for apparently early model D2Vs) in V3.0?
post #37817 of 42717
Quote:
Originally Posted by spiderv6 View Post

Has anyone tested the 'no audio' HDMI issue that was introduced (for apparently early model D2Vs) in V3.0?

I read a previous post that it did.

I've been playing lots of CDs all weekend with no issue, but I can't confirm that the specific CDs I have been playing exhibited the issue prior to 3.0.
post #37818 of 42717
Is the ANTHEM HOMEPAGE (http://www.anthemav.com)down? Can't access since yesterday :-(
post #37819 of 42717
Quote:
Originally Posted by spiderv6 View Post

Has anyone tested the 'no audio' HDMI issue that was introduced (for apparently early model D2Vs) in V3.0?

I installed 3.03 on my 50v and so far the no HDMI audio issue on HDMI ports 234678 problem persists, so for me, it has not been fixed. I did make a hardware addition; namely an apple TV (1080p black model) which is hooked up to HDMI 1. This has created a workaround, a HDMI handshake enabler if you will, allowing all the other ports to function normally. It behaves like an HDCP issue. Once the 50V has established a proper HDMI handshake with a device on port 1 or 5, it okays all other ports to receive audio. You get to the point where you just get tired of fiddling. Anyways, there is something new that has been introduced, something I have not seen before and that is sometimes a pink haze using the apple TV. If I go into the 50v's setup menu and then back out of it while using the Apple TV as source, this can happen but does not always happen. Turning the Apple TV off and on again seems to resolve the issue. Also, I believe that my HDMI 2 out is shot. The output is much lighter, almost hazy, the colours are posterized or solarized and the edges are filled with lines. It just doesn't look right, like an 8 bit computer screen. How this happened I do not know as I have never used that port before I tried it a couple of weeks ago and discovered it was faulty. Whether this is the cause of my no audio problem with firmwares 2.14 and above, I do not know. Whether this indicates that there is a failure on some level on the main mezzanine processing board I do not know. I do know that HDMI 2 is on the main board. Perhaps I should take it in to repair before the warranty expires just to have it checked out thoroughly. In any case, the 3.03 offers quick switching and better menu in/out response.
post #37820 of 42717
Quote:
Originally Posted by drhankz View Post

Don't waste your MONEY on Oppo.
Buy a Sony BDP-S790 it is way better than any Oppo

That's an interesting claim Dr.
I know it is OT for a Anthem forum.
Would you be able to explain how and why this might be possible
considering both the video and audio qualities of the Oppo ?
post #37821 of 42717
Quote:
Originally Posted by thestewman View Post

That's an interesting claim Dr.
I know it is OT for a Anthem forum.
Would you be able to explain how and why this might be possible
considering both the video and audio qualities of the Oppo ?

NEXT Generation Stuff is always BETTER.

This is the 1st 4K Blu-ray Player. For those with
the Sony 4K PJ - it is the only player to OWN.

Also for us with 2K PJs - you still get the benefits
of having a 4K Scaler chip inside.

It STREAMS everything versus the Oppo which does not.

You can START HERE and Read,.

I own it and it makes everything else OBSOLETE
post #37822 of 42717
Hope the Sony drive mechanics have improved. My 770 vibrates so loud now that STREAMING is about all it's good for.

It might also be good for SACD but Anthem has not solved the 16/176k problem yet.

So I now use an ANCIENT Oppo BDP-83 biggrin.gif
post #37823 of 42717
Quote:
Originally Posted by AVfile View Post

Hope the Sony drive mechanics have improved. My 770 vibrates so loud now that STREAMING is about all it's good for.
It might also be good for SACD but Anthem has not solved the 16/176k problem yet.
So I now use an ANCIENT Oppo BDP-83 biggrin.gif

ANCIENT is the right word

BTW I do not run the 790 video through the Anthem --- it is a better
SCALER than Anthem
post #37824 of 42717
Quote:
Originally Posted by boostie View Post

Ok, tried a few things still the same issue.
I disconnected the 12v trigger and with the power amp OFF and turning the D2v on and off and
I still am getting the popping noise. Looks like it is coming from the anthem via feedback through the amp.
Both units plugged into the same outlet.

I think the click/pop on shutdown is common to all AVM/D but most people ignore or don't notice it. The reason is the unit does not mute itself when powering down (going into Standby). The unfortunate workaround is for the user to press MUTE before Standby or powering down.

Anyone upset by this should send a request to tech support for the AVM/D firmware to implement an automatic MUTE BEFORE STANDBY sequence.
post #37825 of 42717
Quote:
Originally Posted by drhankz View Post

NEXT Generation Stuff is always BETTER.
This is the 1st 4K Blu-ray Player. For those with
the Sony 4K PJ - it is the only player to OWN.
Also for us with 2K PJs - you still get the benefits
of having a 4K Scaler chip inside.
It STREAMS everything versus the Oppo which does not.
You can START HERE and Read,.
I own it and it makes everything else OBSOLETE

Here we go again rolleyes.gif
post #37826 of 42717

Bob, hope they get that power up sorted out as I would guess the majority of us use the source command .

post #37827 of 42717
Doc1.docx 131k .docx file

Doc2.docx 255k .docx file

How do these look?? First go with ARC.
post #37828 of 42717
Installed 3.03 and decided to do a new calibration. Here are the results:







The only change this time is I moved the right surround about a foot closer into the room and angled it more towards the main listening position. I only changed the angle on the left surround and didn't move it.



The only difference this time is ARC set my surrounds to 115 where it normally sets them to 95. Here is my previous chart before doing the new cal. Notice the difference in the right surround:



I must say I watched Sherlock Homes 2 last night and the sound stage was huge and impressive, but haven't had time to test anything else. Operation of the D2v is normal and started up fine using my Logitech Harmony One turning on 3 things. So far so good. Any reason why ARC would be setting my surrounds now to 115?

Also of note is I don't get any room gain so I've added 1.2 gain and set the subs to Flat (2 Seaton Submersives).
Edited by SimonNo10 - 7/29/12 at 4:40pm
post #37829 of 42717
Quote:
Originally Posted by SimonNo10 View Post

Installed 3.03 and decided to do a new calibration. Here are the results:



The only change this time is I moved the right surround about a foot closer into the room and angled it more towards the main listening position. I only changed the angle on the left surround and didn't move it.
The only difference this time is ARC set my surrounds to 115 where it normally sets them to 95. Here is my chart before doing the new cal. Notice the difference in the right surround:

I must say I watched Sherlock Homes 2 last night and the sound stage was huge and impressive, but haven't had time to test anything else. Operation of the D2v is normal and started up fine using my Logitech Harmony One turning on 3 things. So far so good. Any reason why ARC would be setting my surrounds now to 115?
Also of note is I don't get any room gain so I've added 1.2 gain.

Usually 1.2 is too low and would be hard to detect. Try 2-2.5.
John
post #37830 of 42717
Quote:
Usually 1.2 is too low and would be hard to detect. Try 2-2.5.
John

No worries here are the results after applying 2.0 gain:







Thoughts?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Receivers, Amps, and Processors
AVS › AVS Forum › Audio › Receivers, Amps, and Processors › Anthem D2/D2v/AVM50/AVM50v/ARC1 tweaking guide