The Avolites Discussion Forum

Hi,

DTS XR250 Wash 16 Channels personality causess visualizer / visWiz not to start, they tell EAccessViolation.

Windows 2000 / Visualizer 6.11, with dongle..

Some more info, from logs..

Tue Aug 30 18:27:00 2005 System information Software version 6.11
Tue Aug 30 18:27:00 2005 Recoverable Error Exception:C:\vis_6-10\run.cpp,line784:EAccessViolation
Tue Aug 30 18:27:00 2005 Recoverable Error Exception:C:\vis_6-10\run.cpp,line3447:EAccessViolation
Tue Aug 30 18:27:14 2005 Recoverable Error Exception:C:\vis_6-10\run.cpp,line2994:EAccessViolation
Tue Aug 30 18:27:16 2005 Recoverable Error Exception:C:\vis_6-10\run.cpp,line3447:EAccessViolation
Tue Aug 30 18:27:19 2005 Recoverable Error Exception:C:\vis_6-10\run.cpp,line2994:EAccessViolation

If the problem is with the personality files, why is it so hard to catch this Exception in code? I don't understant that the hole software fails to work when one personality is somewhat faulty.

Is this with the latest personality files on our website (I can't find a copy of the DTS XR250 for visualiser here at Avolties) or a file that you wrote yourself?

The most likely reason for this problem is that the file doesn't have any blank lines at the end. It's difficult to believe, but at the moment Visualiser requires at least one blank line after the final "End" for the file to be properly read by either program. The other possible reason is that you don't have an R20 file in the Personalities directory with a matching filename and Device name in the personality.

The reason that this isn't caught properly by the software is twofold. Firstrly Visualiser isn't currently our main priority for the software team, and secondly, since we here at Avolites write most personality files for vis and provide an easy to use update mechanism for the personalities, usually this doesn't cause our customers any problems. I have been meaning to find time to try and track down the cause of this exception in the code and fix the problem (since it often causes us problems when writing personalities here at Avolites), but haven't yet had the time to do infortunately.

Yes, I modified it after that.

After 2 hours of ripping the file in pieces found the error.

3 1 s 1 100 1N E 1 "Pan" 128 -1 -1
0 0 L 2 100 1N E 1 "Pan Low" 128 -1 -1
3 61 s 3 100 1N F 1 "Tilt" 128 -1 -1
0 0 L 4 100 1N F 1 "Tilt Low" 128 -1 -1

E(=pan) and F(=tilt) attribute types were mixed.

Does it really need and blank line or CR and LF or both (carriage return and line feed) ?

"The other possible reason is that you don't have an R20 file in the Personalities directory with a matching filename and Device name in the personality. " -> you mean vis file?... I couldn't make vis file because visualizer nor the vizWiz start..

OK, desk software is 1st priority, but I thinki is something that is basic coding/ error catcing when writing software...

But now I'm glad that I solved the problem. I made also a bug report about this file.

the original personality was like this..

3 1 s 1 100 1N F 1 "Pan" 128 -1 -1
0 0 L 2 100 1N F 1 "Pan Low" 128 -1 -1
3 61 s 3 100 1N E 1 "Tilt" 128 -1 -1
0 0 L 4 100 1N E 1 "Tilt Low" 128 -1 -1

the previous post had ok values...

Sorry, my mistake!

I thought you meant a .vis extension file rather than a .r20 personality, and so assumed the problem was something different

I'll take a look at the personality file later today and get any problems with it fixed in our fixture library.

The space at the end of a file applies only to .vis extensions and not to .r20 files. I believe that both CR and LF are required for it: all files are saved in a Windows format, which requires both. (If you open a unix file in notepad, you'll find everything on one line, whereas with our .vis files, you can open them in notepad and see plain text fairly well spaced out).

As for the bugs, I can only hope that at somepoint we can fix them to prevent others from having similar issues in the future. Thankfully, our quality control and code writing standards are such that our software tends not to crash these days, even if you do sometimes get some obscure problems. Hopefully these forums and the stability of the Pearl 2004 software show that we're on the right track!