Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Systems Trifield (again)

Wow, be interesting to see another firmware release on the old 568.2 !!

Will they still call it "beta"

I shudder to think of the outcome had we tried to resolve this through a dealer. Hopefully, Hitchhikers will be accorded special status through some sort of ombudsman along the lines Ian suggested. We are special, aren't we?

Hi Frank, Let's not spoil the good news of the day. Suggest we try and keep the dealer/support comments in that thread. cheers

And after all I reckon most will have it set to wide,. as it is now, but it is nice to be able to adjust it and know your not going crazy.......Good result, Chris

I'm SO pleased that M has finally found this problem. I originally posted this issue on 31 July, 2008 (did a search to find the thread). I sure hope they update the 568.2 beta code (v2.5), rather than the officially released (v2.12) code - it is sonically far superior.

Thanks all for hanging in there with me!

John

Hi,

This is excellent news, we are fortunate to have this information. I wonder what will Meridian do for all the owners affected who are not members of this forum?

Regards I

MI'

They probably never upgraded a firmware in the first place and are in blissful ignorance that the issue is there. What Meridian will do is correct the firmware so if you're a non-HH user and do manage your f/ware you will be sorted.

Is there an update for this now? Or can we expect one soon?

Thanks

an update ? what? since yesterday ? Just what time scale are you working on

Yes the message is good,
BUT doesnt that also mean, that M makes no listening tests ?
And maybe there are more such things?
I dont want to criticize M here, but how will M check that in the future?

The problem was that the wrong but of code got inadvertently released, not that the code was not tested, however M do that, possibly including listening tests. I guess it depends on the impact that the coding change has as to what type of testing it undergoes.

As for it happening in the future, one can only guess the development lifecycle that M use. But I suspect that it is quite informal with code possibly being developed until quite late in the development lifecycle, but this means that some testing may not occur on the physical release build, so build issues may fall through the net as would appear to have happened here. In a larger commercial environment, with formal testing, the code cutoff will occur much sooner in the lifecycle and the release build will be used much earlier resulting in build issues being caught.

I don't think that Meridian did anything wrong, its just they may not have the benefit of time and/or resources to devote to thoroughly testing the actual release build and that in this case, the errant code slipped through checks on at least two occasions, once when the build was first released and subsequently rechecked.