- This topic is empty.
-
AuthorPosts
-
-
March 24, 2012 at 3:57 pm #108549ThreeFingersOfLoveParticipant
Hello,
after updating to 5.6B and selecting a monolithic preset, I get the following message: ERROR- Suggest Power Down, host A : timeout. "Any key to continue" does nothing, the H8000FW seems to hang while loading program B – weird because monolithic programs are supposed to be loaded on DSP A.
Anyway, I tried rebooting several times, reinstalling 5.6B, pressing 5 at startup, pressing 8 at startup. No luck. Can anyone help?
-
March 26, 2012 at 3:41 pm #123252
Hi Three – sorry you are having trouble. Pressing the 8 key should do it- may sure you do it at the SECOND (H8000) start-up screen. If this fails, try going back to your previous version (should be available from the update page).
-
May 3, 2012 at 9:10 am #123403ThreeFingersOfLoveParticipant
So, are we going to see an official release or what? Why does it all take AGES for you to release something on time and working?
-
May 3, 2012 at 4:11 pm #134494
There will be another beta release with new drivers shortly.
This stuff takes time because it is very difficult and complicated, and there are not enough of us for all the thing we are trying to do. If it were easy, everyone would do it.
-
May 3, 2012 at 4:44 pm #134495ThreeFingersOfLoveParticipant
Thanks for the reply, Nick.
Here's what I think is a bug: after downgrading from 5.6B1 to 5.5. and loading Echospace of God, on DSP B, the H8000FW crashes (the message I get is: ERROR, Suggest Power-Down, host B: timeout,
Please, do something, I need some help here. -
May 3, 2012 at 5:19 pm #134496
Hi Three
This sounds like a problem you had earlier – basically loading the program crashes the DSP. It's usually fixable by holding down the PROGRAM key at startup, but this obviously does not resolve the underlying problem.
There are a number of possible causes:
1) Failed update leaving mismatched software.
2) Hardware problem of some kind – if it happens again, take the top off the unit and "wiggle" all socketed parts and connections in case there is a bad contact somewhere. Especially U106.
3) Software bug. In this case it would probably be repeatable and maybe only apply to certain programs.
4) Unstable clock source when using digital input.
5) Overheating due to insufficient cool airspace around unit.
If the above doesn't help, we could run some selftests. Hold down the 1 key at the first startup screen, and release it when asked. Turn the wheel until it shows "(053) Test DSP #0,1". Hit select. Let this run for a few hours. The P number will increment. If either the E= or the T= show other than 0, let me know.
-
May 3, 2012 at 5:24 pm #134497ThreeFingersOfLoveParticipant
OK I will come back later to tell you what happens, thanks for the swift reply!
-
May 5, 2012 at 11:44 am #134504ThreeFingersOfLoveParticipant
Hi again,
there is sufficient air flowing up and below my unit. I ran all these tests that you mention, neither E or T show anything other than 0. It seems to me that there's crap left from the 5.6B installation.
-
May 7, 2012 at 3:28 pm #134506
Maybe so. You could save any presets you want to keep to a card or computer, the try a "return to factory defaults" (8 key on second startup screen).
-
May 8, 2012 at 6:39 pm #134514ThreeFingersOfLoveParticipant
Nick,
pressing 8 at startup doesn't do anything. The only thing that "solves" the problem is upgrading/downgrading to 5.6B/5.5 – depending on which OS version caused the problem (they both do).
-
May 8, 2012 at 7:01 pm #134515
Are you saying that pressing 8 does nothing at all, or that it does not cure the problem. You should at least get an "are you sure.." message.
-
May 9, 2012 at 3:18 pm #134517ThreeFingersOfLoveParticipant
Pressing 8 doesn't cure the problem, nor any other number does.
-
May 9, 2012 at 3:42 pm #134519
Which presets on which DSP at what sample rate and source cause the problem ?
-
May 10, 2012 at 8:21 pm #134521ThreeFingersOfLoveParticipant
For instance Echospace of God, which I always used with 96KHz, dual analog stereo – this one worked flawlessly with 5.5. until I upgraded to 5.6B1. This is a monolithic preset that I have loaded on DSP B, though I don't think it makes any difference since, being a monolithic preset, both DSPs would be used.
-
May 10, 2012 at 8:34 pm #134522
This is not monolithic on 5.6 – maybe it should be. I'll look into it. Can you give me any more ?
Are you using internal or external sync ?
UPDATE: this one should not be a problem – it uses 55% of the dsp. Obviously it is a problem for you, but can't immediately see why.
If you haven't, can you let the tests run over night or longer ?
-
May 11, 2012 at 11:58 am #134523ThreeFingersOfLoveParticipant
I run the tests all nights, I didn't see anything weird in the display (E = T = 0). I use internal sync at 96 KHz. I think there are a couple more presets that present this problem but I am stuck with that creepy message so I need to reinstall 5.5 just to be able to tell you what other presets misbehave. If you are a little patient, I will report back soon.
-
May 11, 2012 at 12:22 pm #134524ThreeFingersOfLoveParticipant
I just upgraded to 5.6B1 again, tried to load "Echospace of God" on DSP A (at 48 KHz) and same old crap. This is getting ridiculous. 🙁
-
May 11, 2012 at 9:12 pm #134525
Even though it seems to pass the tests, it is looking more like a hardware problem. My unit does not do this at any sample rate, which suggests it is something specific to your unit. You should contact support@eventide.com with a view to getting it fixed.
-
May 17, 2012 at 7:50 am #134538ThreeFingersOfLoveParticipant
Nick,
can you please give us an estimate for the second beta version of 5.6? Will it only contain bug fixes?
Regards,
Yannis
-
May 17, 2012 at 3:33 pm #134540
Probably around the end of the month. It has fixes for a few problems found in 5.6B1.
-
May 27, 2012 at 9:51 pm #134567ThreeFingersOfLoveParticipant
nickrose:
Probably around the end of the month. It has fixes for a few problems found in 5.6B1.
It's "around the end of the month", isn't it? Let's have it!
-
May 28, 2012 at 4:01 pm #134568
What I said was "probably around ..," implying a degree of vagueness. But, to quote the song, it won't be long now ..
-
-
AuthorPosts
- You must be logged in to reply to this topic.