
Titan version 7.1
Moderator: Moderators
-
- Posts: 21
- Joined: 29 Aug 2012, 15:37
Re: Titan version 7.1

Re: Titan version 7.1
Sorry to up this old topic but I am having this exact problem, but I'm on 7.4? So the fix should already be in it but it still occurred! Anyone else having this freeze&snap-issue with 7.4?
Should I have gone 6.1 > 7.1 > 7.2 > 7.4 instead of 6.1 > 7.1 > 7.4 ?
Should I have gone 6.1 > 7.1 > 7.2 > 7.4 instead of 6.1 > 7.1 > 7.4 ?
Re: Titan version 7.1
I don't think the upgrade path should matter but there's no harm in running a recovery to ensure everything's as fresh as possible.
I spend most of my time using Experts. The only time I've seen pauses in fades in the past (excluding the 7.1 issue) was during autosaves. This should no longer occur, especially on a pro, but you could try disabling when running shows just in case.
I spend most of my time using Experts. The only time I've seen pauses in fades in the past (excluding the 7.1 issue) was during autosaves. This should no longer occur, especially on a pro, but you could try disabling when running shows just in case.
Re: Titan version 7.1
Thank you for your reply, not a software fault then. Could do the recovery although since the "dongle not found" I am a bit scared to run anything update-wise
Health check says something about low disk space, could this also affect lagging? Maybe in combination with the autosave.
PS: I am on Expert, not Expert Pro, got confused about that earlier.

Health check says something about low disk space, could this also affect lagging? Maybe in combination with the autosave.
PS: I am on Expert, not Expert Pro, got confused about that earlier.
Re: Titan version 7.1
Generally the health check warnings are important. You should look at exactly what it says. I suspect it is 'low disk space'. I would say this certainly could cause these sort of problems if it is having difficulty with disk access.
Regarding the update I would not be afraid - I have done countless recoveries over various Experts, pro and non-pro. But, unless you have no other option (ie. console is not working) then it is always a good idea to allow plenty of time and preferably on a weekday during UK working hours so that you can easily get support should you need it.
As for the pausing, I am in the middle of programming a show on a standard Expert with a spinning hard drive running 7.2 (for compatibility reasons). I tested autosave while running a combination of shape, effect and fading chase. This was over approx 100 fixtures. At the point of save there was a pause of just under 1sec. This measurement was based on watching the Avo vis, which might not accurately reflect the timing of the actual output and will itself be putting some additional load on the processor. Therefore the actual pause is probably a bit less.
So there is a pause during autosave. How much will depend on factors such as how many fixtures are fading, pro or non-pro (CPU speed), spinning hard drive or SSD (SSD faster), whether vis is running and possibly if HUD is open or not.
As a rule I always turn autosave off.
Note that the fix in 7.2 was specific to fades occasionally pausing when firing or killing playbacks.
Regarding the update I would not be afraid - I have done countless recoveries over various Experts, pro and non-pro. But, unless you have no other option (ie. console is not working) then it is always a good idea to allow plenty of time and preferably on a weekday during UK working hours so that you can easily get support should you need it.
As for the pausing, I am in the middle of programming a show on a standard Expert with a spinning hard drive running 7.2 (for compatibility reasons). I tested autosave while running a combination of shape, effect and fading chase. This was over approx 100 fixtures. At the point of save there was a pause of just under 1sec. This measurement was based on watching the Avo vis, which might not accurately reflect the timing of the actual output and will itself be putting some additional load on the processor. Therefore the actual pause is probably a bit less.
So there is a pause during autosave. How much will depend on factors such as how many fixtures are fading, pro or non-pro (CPU speed), spinning hard drive or SSD (SSD faster), whether vis is running and possibly if HUD is open or not.
As a rule I always turn autosave off.
Note that the fix in 7.2 was specific to fades occasionally pausing when firing or killing playbacks.
Re: Titan version 7.1
Photo below shows what it says, indeed low disk space. I will look at it during a weekday indeed so I can call for support if needed. I think the autosave may very well be the cause for the lagging, I did a show on Friday as well and nothing happened but it was an easy and calm show, though yesterday was a hardcore party with loads of movement and strobes.
Thank you for pointing this out, wouldn't have thought of that.

Thank you for pointing this out, wouldn't have thought of that.

Who is online
Users browsing this forum: No registered users and 60 guests