Well I am not sure if this is a bug or not but it happens on 2 different systems one a quad-core system and the other on my new show pc.
The problem is as follows:
When editing a sequence in either 2.1.3 or 2.5.X my sequence can play and some times I can stop it and some times I cant. I can hit stop or pause with the mouse and no reaction. If I hit F7 or F8 no reaction. Looking at the task manager in Vista I can see the vixen process increasing in memory usage all by 250k each 2 to 3 seconds.
I do not seem to have this problem working on a slow pc at work.
Is anyone else experiencing this issue.
On an odd note some times when the sequence does stop I get a Plugin Error message stating:
Object referance not set to an instance of an object
Execution has been stopped
The sequence is attached to a profile and the only item active is the adj preview.
Rich - I had this happen once, on the laptop. Same exact symptoms (except I didn't check CPU usage). I can't recall what I had to do, but I think I rebooted Vixen, and it still did it, and went away when I rebooted the computer.
This was also on 2.1.1. Sorry can't be more help, but just wanted you to know, you aren't going crazy... 🙂
Roger
I am running 2.1.3 with just the Adjustable Preview - 224 channels and do see that (both the hesitation to stop and the message) every once in a while. I can go for an hour - nothing - then it will happen a couple times in a row. In my case it doesn't seem to cause any problems other than that brief moment of "confusion" - I can press F6 again to play again and off it goes... I am running Vista also on a middle of the road type machine (dual core AMD something or other).
What do you mean I am not going crazy. I am here on this forum so that makes me crazy.
I guess I just need to use the pc I took to work to edit my stuff. 🙂
Sorry boss I cant do the TPS reports today I have to finish my sequencing. 🙂
I jsut checked and the problem seems to do it on Sequences created by others.
I was trying to get some inspiration from Franks 2008 Seq and hit the stop and get the same error. This is on Ver 2.1.3.0 in case anyone is interested.
Interesting... I know at least two that I've been working on recently where I saw this problem were LOR S2 sequences that I converted recently. They were 32-channels to begin with but are now 224 channels.
I have been having this problem on my Quad Core vista x64. I moved my stuff over to a regular x86 XP, and it's better (but it still does hang once in a while).

