pexp 855
Titan v1.1 has crashed twice, each time i was editing chases with very high BPM.
After the first reboot the desk failed to load the current show and there were 2 error codes I failed to note the numers but i think one was around 12003 (very sorry about that)
The second reboot I tried to reboot (Titan not responding) again very high BPM chase on 20led rgb fixtures. I tried closing titan booted classic and then restarted titan. It sort of worked but ran very slowly faders reacting sparodically with juttery fades by hand. Having fully reset it is currently operating with slow response and freezing the processor bogged down and response to faders about 4 seconds. Within five minutes it appears to functioning correctly
I need v1.1 as I have need the multiple channel feature to drive the master functions of a pile of batmink blinders and tthereafter treat each cell as a fixture.
Great new feature by the way.
Regards
Alan
pearl expert titan V1.1 beta issues
Moderator: Moderators
Hi, sorry to hear you had problems.
It would probably be useful to give more details about exactly what sort of edit you were making to the chase (ie. changing speed by wheel/using edit times menu etc.) and roughly how fast it was.
It might also be useful to explain the nature of the crash -ie. blue screen/error dialog/or just stopped responding.
There are also log files which may help Avo in determining the cause.
Sounds to me like the other problems you had were most likely a result of it getting confused when show load failed and the launching of classic then titan. Chances are there was still a Titan process running that hung and never closed after it tried to read the showfile initially.
When Titan shuts down properly it writes a showfile which is then read on boot. If this file is not written then there will be no show on reboot. If, however, this file gets corrupt then it can cause an error when it tries to read it.
If this ever happens again then the solution is to navigate to c:\program files\avolites\diamond4 and delete the file shutdown.d4z. Now when you restart the software it will start with no show and you should be able to load in the last save as normal. Because this sort of situation could result in hung processes, the close/restart software buttons might not be enough. Unless you understand the software and how to manually kill processes it is probably advisable to power cycle the console first.
One thing I would advise is to disable Autosave (certainly while running a show), just in case.
It would probably be useful to give more details about exactly what sort of edit you were making to the chase (ie. changing speed by wheel/using edit times menu etc.) and roughly how fast it was.
It might also be useful to explain the nature of the crash -ie. blue screen/error dialog/or just stopped responding.
There are also log files which may help Avo in determining the cause.
Sounds to me like the other problems you had were most likely a result of it getting confused when show load failed and the launching of classic then titan. Chances are there was still a Titan process running that hung and never closed after it tried to read the showfile initially.
When Titan shuts down properly it writes a showfile which is then read on boot. If this file is not written then there will be no show on reboot. If, however, this file gets corrupt then it can cause an error when it tries to read it.
If this ever happens again then the solution is to navigate to c:\program files\avolites\diamond4 and delete the file shutdown.d4z. Now when you restart the software it will start with no show and you should be able to load in the last save as normal. Because this sort of situation could result in hung processes, the close/restart software buttons might not be enough. Unless you understand the software and how to manually kill processes it is probably advisable to power cycle the console first.
One thing I would advise is to disable Autosave (certainly while running a show), just in case.
Hi and thanks for the valuable help. I will reherse tomorrow what happened and take a little more detail than I had today. I am no software expert i merely tried the switch to classic and back the second time in a bid to save reboot time as the desk had hung twice and i was looking for options and get outs as you do. The desk hung both times with a high speed, random chase (3400bpm ish) the entire surface froze and the dmx output remained as before the stall. The vdu and keyboard had some function as I closed/reduced the HUD to acertain that Titan was not responding. I carried out a full powerdown and reboot after my first mail on this issue and it is obvious the desk remains unstable and cycles between near real time functionality and serverely delayed operation. I had left autosave on as we are still at programming stage on this production and I would sooner get to the root of the problem now rather than later.
I wondered wether to reinstall v1.1 but didnt want to distroy any perishable data you clever people might need. Going back to v1 would prevent me replicating the circumstances due the lack of functionality Please let me know if you need me to do anything?
kind regards
Alan
I wondered wether to reinstall v1.1 but didnt want to distroy any perishable data you clever people might need. Going back to v1 would prevent me replicating the circumstances due the lack of functionality Please let me know if you need me to do anything?
kind regards
Alan
There is a restart software button on the sidebar. If the problem occurs again then you should be able to use this. The issues you had after restarting the console were probably a separate matter.
That is an impressively fast chase! If it happens again try disconnecting (double-tap connect).
In the meantime I will highlight this with support.
/edit: after re-reading I wanted to clarify about the output after the freeze. Did the chase continue running on stage or did it just hold the last state sent. If the chase continued then it means Titan was running but you lost control (either Panel Server or Usb Console)
That is an impressively fast chase! If it happens again try disconnecting (double-tap connect).
In the meantime I will highlight this with support.
/edit: after re-reading I wanted to clarify about the output after the freeze. Did the chase continue running on stage or did it just hold the last state sent. If the chase continued then it means Titan was running but you lost control (either Panel Server or Usb Console)
The chase is left running on the output when the desk freezes.
I created the chase by selecting all the RGB up to 100% and then a straight dimmer chase one fixture up at a time (20 steps). Speed it up as fast as the desk can go select random and you get this fantastic twinkle effect that can sit behind basic colour washes or as a strobe effect etc.
regards
Alan
I created the chase by selecting all the RGB up to 100% and then a straight dimmer chase one fixture up at a time (20 steps). Speed it up as fast as the desk can go select random and you get this fantastic twinkle effect that can sit behind basic colour washes or as a strobe effect etc.
regards
Alan
Obviously that suggests Vis is responsible for the slowdown. Although running LED units like this with Vis is something I have done throughout testing and it has never proved cause of problems for me. Albeit not quite so fast - I tend to max at around 1000BPM.
Is there definitely only one copy of Vis running? I have been told that it doesn't like multiple copies at the moment.
Did you try disconnecting?
Is there definitely only one copy of Vis running? I have been told that it doesn't like multiple copies at the moment.
Did you try disconnecting?
No, not boring at all. It is important the software runs correctly and finding and reporting problems is key to getting them fixed.
I have performed some tests to see if I can replicate.
Test was using 1.1 on console. I created a 50 step intensity chase using 50 v-dim LED fixtures set to random. I tested at various speeds up to 3600BPM with and without x-fade. With and without Vis (including two copies), w/without HUD and w/without connect.
I found that if the chase ran above approx 1200BPM the software had increasing difficulty in displaying LCD menus or updating handle LED's. At 3600BPM it was effectively impossible show a new menu (ie. shift). I also found that at the upper speed limit a chase could overrun slightly if faded down reasonably slowly. Both of these issues were solved by disconnecting. Otherwise, however, I could find no response problems.
Vis and HUD did not appear to have any affect.
I can also confirm that these particular problems are fixed in the next version.
Unfortunately I don't see the same issue you are seeing, but hopefully devs will be able to shed some light on it.
I have performed some tests to see if I can replicate.
Test was using 1.1 on console. I created a 50 step intensity chase using 50 v-dim LED fixtures set to random. I tested at various speeds up to 3600BPM with and without x-fade. With and without Vis (including two copies), w/without HUD and w/without connect.
I found that if the chase ran above approx 1200BPM the software had increasing difficulty in displaying LCD menus or updating handle LED's. At 3600BPM it was effectively impossible show a new menu (ie. shift). I also found that at the upper speed limit a chase could overrun slightly if faded down reasonably slowly. Both of these issues were solved by disconnecting. Otherwise, however, I could find no response problems.
Vis and HUD did not appear to have any affect.
I can also confirm that these particular problems are fixed in the next version.
Unfortunately I don't see the same issue you are seeing, but hopefully devs will be able to shed some light on it.
Olie
I am away fron the desk currently my recolections are as follows.
At the point of the crashes Vis was running either in the backround or small window.
When I run it yesterday I was running it full size.
Either way it seems to slow down the desk when running the high BPM chases when vis is in run mode but not in design mode.
I have been able to rplicate the crashes however and that is both comforting and unerving.
Regards
Alan
I am away fron the desk currently my recolections are as follows.
At the point of the crashes Vis was running either in the backround or small window.
When I run it yesterday I was running it full size.
Either way it seems to slow down the desk when running the high BPM chases when vis is in run mode but not in design mode.
I have been able to rplicate the crashes however and that is both comforting and unerving.
Regards
Alan
After reading your description again I am wondering if you where running a show that was saved in v1.0 and upgraded to v1.1. Whilst this should not be a problem it might explain why we are unable to repeat the problem and you have not seen it since.
If this was the case you should see some errors in the exception log. You can find this in c:\Documents and Settings\Administator\Application Data\Avolites\Titan Pearl Expert and they are listed by date. It would help if you could send us these logs.
I will try testing shows going between versions to see if I can replicate your problem.
If this was the case you should see some errors in the exception log. You can find this in c:\Documents and Settings\Administator\Application Data\Avolites\Titan Pearl Expert and they are listed by date. It would help if you could send us these logs.
I will try testing shows going between versions to see if I can replicate your problem.
Avolites Software Team
Who is online
Users browsing this forum: No registered users and 17 guests