Misconceptions about my work and product

From reading threads and posts on the Meridian Unplugged forum it is clear there are many misconceptions about my work and product. The main problem is that they do not have the facts straight, so any discussion is meaningless. I would love to react about this on the forum, but they banned me because I mentioned I downgraded DSP-C. Now there is a lot of talk about DSP-C on the forum, which has been already discovered and posted here 4 weeks ago.

So what are the facts?

  • I do not provide an alternative firmware as is consequently said on the forum, I only provide a self developed up-sample filter.
  • A filter is comprised of a set of coefficients, which are derived from characteristics. So it is just data, not code, and quite similar to MRC data which is calculated by the config app based on room measurements.
  • Therefor I have never reverse engineered a single line of firmware code.
  • Consequently, not a single line of code is patched by my software.
  • The new filter is 100% developed by me, so does not contain any 3rd party data. Even more so, I wrote the software to design this filter myself.
  • The filter installer only exchanges the filter coefficients in the firmware, and is therefor 100% safe to use because no code is changed at all.
  • The installer runs independent from the Meridian firmware upload tool, so not a single line of code of the tool has been reverse engineered, and therefor not a single line of code is patched by the installer.
This entry was posted in Firmware, Meridian. Bookmark the permalink.

10 Responses to Misconceptions about my work and product

  1. Dave says:

    Why don’t you offer a VST upsampler for computer work?

    • Mr Apodizer says:

      This may not sound professional or commercial, but I had no use for that myself. However if enough people are interested in this, I may look into it. Which application do you have in mind for use with my up-sample filter?

  2. Marcus says:

    Hi Mr Apodizer,
    A question: How did you know where to “put” those coefficients within the Meridian code? Didn’t that involve some sort of reverse engineering to indentify where they needed to be changed?

    • Mr Apodizer says:

      Depends on what you consider reverse engineering. For me this means that you disassemble the code to see how it is working. However, to find the place of the coefficients there was no need to reverse engineer any code, so no disassembler was ever used. Actually it is so ridiculously simple I found it in a few minutes time. If I am ever forced to disclose how I did it, people would have a good laugh.

      So just for the record: only common knowledge is needed to find the place of the coefficients, and therefor no Intellectual Property of Meridian has been reverse engineered to discover the working of it.

  3. Marcus says:

    Very interesting…
    By “discover the working of it.”, I assume you mean “discover the location of the coefficients”. However I am not sure if I understand the phrase “common knowledge”.

    Anyhow, if I am reading this correctly you are actually stating that you:
    a) changed “variables” (in this case coefficients) not logic.
    b) found the location of these “variables” using knowledge that would be “commonly known” (if you were a firmware programmer?)
    c) did not view, decompile or change any Meridian code logic (Meridian Intellectual Property)
    d) created an upload program that only changed the coefficients (i.e. this does not touch the Meridian core code)

    ( I personally do not own any Meridian equipment that would “take” this modification but I just wanted to understand what was going on because noone on the HH site seems to have asked you for your side of the argument and it is not really possible to make a correct judgement without fully understanding both sides).

    • Mr Apodizer says:

      By discovering the working of the code (aka reverse engineering) it is very well possible to find the location of the coefficients. As said, that is not the way I did it. I used common knowledge of the working of filters (defined by mathematicians long ago) and some basic specs from the hardware platform used (Motorola DSP 56K, as stated in their datasheets). This is common knowledge because it is not something Meridian invented (IP) or is discovered from their firmware code.

      a) Yes.
      b) Yes. All basics were covered in my study of Computer Science.
      c) Yes. I am aware that people on the forum proclaim otherwise.
      d) Yes.

      Actually my posts and posts of George Mills on this subject were deleted by the moderators (Carl). Still lots of posts and parts of posts disappear into thin air on the forum.

      • Marcus says:

        Thank you for your quick and honest replies. It is very interesting to hear your side of the story. I have a hunch that Meridian wanted all owners to engage with their “local” dealer with the prospect of additional sales for some time. I also think that the idea of giving free firmware upgrades to anonymous Meridian owners is not a good business model and that there were probably moves afoot to remove the free download facility from their web site. Maybe your work was simply a means by which to accelerate the inevitable change in the underlying business model?

  4. Dave says:

    Why don’t you make a foobar plugin. Screw messing with firmware, 8x usb is here.

    thanks

    • Mr Apodizer says:

      The answer is essentially the same as for a VST plugin.

      However, the filter is available for OEM, so any manufacturer of audio hardware or software can get a license on using the filter in their products. So if you want to have support for my filter in a certain product, you can point the maker of it to my filter.

      • Dave Kysar says:

        Well I doubt any big companies will be working with you, this is the stagnation of big business, if you aren’t on thier file you don’t get business.

        Skip all that, make a VST plugin with paypal download.

        Time to start braking the mold folks, the computer is set to replace the digital section of standalone dacs, innovators like this gentleman will put an end to paying $5-$10k on a DAC that consists of $200 in parts and $5000 in oversampling algorithm expert programmers.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s