- Eventide Audio

Home Forums Products Rackmount H8000 remote Reply To: H8000 remote

nickrose wrote:

Sorry about removing the jack – the main chip that drove it was discontinued by Mr. Intel, and we had no choice but to remove the Eve/Net circuitry. Given the low take-up for Eve/Net, it did not seem worth doing a major redesign to support it further.

Hey Nick-

We met at AES in NY, and spent some time talking tech about all things Eventide. Previously we had communicated back and forth through Jerome and directly, fixing a couple of bugs concerning some presets, and one of the “search by” functions on the H8000FW, arriving at version 5.610

I have been a strong advocate for the rack-mount processors over the years, and know from a technical perspective that they have no competition.

It wasn’t so much the removal of the Eve/Net port, but (as far as I’m aware) the oversight on the part of the company when it came to mentioning it.

I was one of the people with an EVE/NET that picked up a third H8000FW expecting to integrate it into my system, only to receive it, remove that black plug and shake my head in disbelief at the fact that the port had been removed.

Yes, EVE/NET was discontinued (due to the fact that the encoders reached EOL as I was told by Jerome), but there were still those of us who purchased them with the idea of continuing to build-out our Orville/H8000 systems.

For those uninterested in EVE/NET, this is a non-issue, but for those like myself and the O.P., it is worth noting so informed decisions can be made.

This is especially true in his case when buying second hand, as returns for something like this can be nightmarish to say the least.

While we’re at it, speaking of remotes and compatibility…

I’ve been working with the H9000 for over a year and the last eMote/H9K update apparently does not support Windows 7. This is something worth telling those who run their studios offline on a stable system without, “upgrading” on a constant basis.

Previous Eventide software (VSig for example), remained backwards-compatible with Windows 3.1

After downgrading back to the “last-known good” versions of eMote/H9K that worked on my system, they still will not communicate and eMote keeps crashing.

At this point, even tech-support does not know how to rectify this, leaving me with the choice of exclusively testing the H9K from the front panel, or changing my whole offline system over to Windows 10.

I am aware that the thinking of the public at large, and the rate of technological advance has changed significantly since I began doing this in 2004.

However, it would help the few of us left out there if Eventide would either still consider backwards compatibility (RME is a champion when it comes to this), or would state publicly and clearly when a hardware/software revision would significantly affect it.

That is a policy I’m sure we can all agree would satisfy everyone from the developers to the end-users, and keep redundant tech-support tickets to a minimum.

…The most diplomatic and efficient solution -at least in my estimation.