Lightly Posted October 20, 2003 Report Posted October 20, 2003 Hey Zero88-Folks, I unfortunately made some bad expierience last Weekend: my Fatfrog crashes the same way as "dominicgross" posted in this forum on Jul 1st this year. While doing a show and runnning a chase and some Submaster-programms, I pressed "edit" to configure the speed of the current memory running. "Edit"-Menu opens, but as I turned the Speed-rotary switch, a window "Saving show- please wait" opened, flickered between 0-24% and ended up in a whole blue screen with some boot-advices I think. I had to restart the frog, and now everytime I try to configure the chase-speed, same thing happens. Is this a recognized problem and may I solve just by installing the 8.1.-software once more? Greetings Quote
K-Nine Posted October 20, 2003 Report Posted October 20, 2003 Were you running the chase on the playback X or the submaster, and did you edit the memory or the submaster ? If you could send a copy of the show then we can try running it here and see if we can reproduce the problem. Quote K-Nine : Technically Advanced Roving Dog In Space Bran Media | Myspace
Lightly Posted October 20, 2003 Author Report Posted October 20, 2003 Hi, Chase was running on the Playback X, and I edited the memory directly. Gonna send you the show in a few minutes by e-mail... Quote
Lightly Posted October 21, 2003 Author Report Posted October 21, 2003 So here's to anyone who makes the same strange experiences: The problem disappears (and I hope never comes back) by reloading the show to the desk. :roll: Greetings Lightly Quote
Lichtbosch Posted January 15, 2004 Report Posted January 15, 2004 Our Frog is only 4 months old and is showing exact the same problem as discribed by Lightly. Is it a typical Frogproblem? And is there a solution for this terrible Frog-missbehaving? Quote
K-Nine Posted January 15, 2004 Report Posted January 15, 2004 I'm testing some of the new frog updates at the moment and I will try and reproduce the problem here in the demo room. The action that led to this problem may be affected by one of the new functions which allows live adjustment of chase speed for chases running on the playback X, submasters and SX buttons (Mambo). Live adjustment of chase speed is a temporary 'run mode' operation. When the chase is run again, it will run at it's programmed speed. If you wish to change the programmed speed in the chase, you will need to edit the chase, but this would not normally be done while running the chase live during a show ! Quote K-Nine : Technically Advanced Roving Dog In Space Bran Media | Myspace
Oscar Palmkes Posted January 15, 2004 Report Posted January 15, 2004 whe had the same problem last year, after installing a update the problem was gone. Quote
Yves Posted January 16, 2004 Report Posted January 16, 2004 I also have seen the blue screen, but sinci I've restarted the desk (mambo) I never had the problem again. Quote
K-Nine Posted January 16, 2004 Report Posted January 16, 2004 I tried to reproduce this yesterday in our demo room and was unable to make the desk crash. I will be doing a lot with chases as part of testing the new updates and so will try some of the things that people have reported as making the desk crash. Quote K-Nine : Technically Advanced Roving Dog In Space Bran Media | Myspace
Yves Posted January 16, 2004 Report Posted January 16, 2004 I think it was when I pressed a few buttons at the same time, but I'm not sure. If I have the problem again I'll try to remember what I did. Quote
Lichtbosch Posted February 6, 2004 Report Posted February 6, 2004 Hey Zero88-Folks, While doing a show and runnning a chase and some Submaster-programms, I pressed "edit" to configure the speed of the current memory running. "Edit"-Menu opens, but as I turned the Speed-rotary switch, a window "Saving show- please wait" opened, flickered between 0-24% and ended up in a whole blue screen with some boot-advices I think. I had to restart the frog, and now everytime I try to configure the chase-speed, same thing happens. Last night, our fatfrog crashed again, in the same way as Lightly discribed. It happend 5 times in a row :roll:. I had to restart the desk again and again. We have the 8.1.1 software. But something strange happend also. The last time I did restart the desk I went to the edit button again. But now I did change the attack, then the screen showed: "saving show" and it did so for the full 100%. After doing so the table didn't crash again that evening . Quote
Lightly Posted March 1, 2004 Author Report Posted March 1, 2004 If anyone ever gets in this kind of trouble again (hope the new release convertetd the disloyal frog specimens... :twisted: ) : In my case, the strange blue screen appearing after editing the speed vanished for ever after RELOADING THE SHOW to the desk! :idea: Quote
Yves Posted March 1, 2004 Report Posted March 1, 2004 never had the problem again. I hope to keep it this way. Quote
Yves Posted March 9, 2004 Report Posted March 9, 2004 last saturday my mambo frog crashed I pressed the program type button to program a chase and the desk saved the show, but when it came at 13% it gave a blue screen and had to reset the desk. I'm running 9.0 software Quote
John_Schlick Posted July 2, 2004 Report Posted July 2, 2004 I was programming a frog for a generic set of queues cause the board was to live in a venue. I copied a number of memories from one to the next to the next. I was then transferring those memories to the submasters (cause thats where they were going to be accessed, as they were all chases, and yes they were identical, but my plan was to modify parameters like color and gobo off the original...) As I did a transfer with time (on every desk I've used, I have to hit this key very hard to get it to "take", I'd then hit the page up or down key to get to the page to copy to, then the submaster I wanted, and when I hit OK. About every 5 or 6 queues or so the desk would crash, but that was AFTER it had transferred the memory to the submaster. I started going to the page of submasters before hitting transfer with time, and it happened far less frequently. I've also had one other desk (running 9.2) crash under these circumstances (well, I can't remember EXACTLY, but it was very similar and since it was an isolated incident, I'm going from memory as to what I was doing. It's only because I was doing a lot of the transfer with time of a memory to a submaster that I noticed it. Hope this helps get you to the right code sextion to diagnose things. John. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.