Page 1 of 1
"Subscript Out of Range"
Posted: 16 Jun 2010, 19:57
by skip1
hi again,
I get an error message saying "subscript out of range when trying to create a sequence.
What does this mean?
Re: "Subscript Out of Range"
Posted: 16 Jun 2010, 20:00
by LJ_krede.dk
looks like a bug.. can you give some more detalis what you did before you got this error? does it happen every time?
Re: "Subscript Out of Range"
Posted: 16 Jun 2010, 21:03
by skip1
yes it happens everytime. i am running windows 7 and am in need to use this program tonight.
is there any way i can get it working by then
Re: "Subscript Out of Range"
Posted: 16 Jun 2010, 21:16
by LJ_krede.dk
you can try to remove FS and install it again.
if you still have the problem try to install another version
you should report the problem to the developer:
[bugreporting][/bugreporting]
Re: "Subscript Out of Range"
Posted: 17 Jun 2010, 11:29
by remco_k
skip1 wrote:yes it happens everytime. i am running windows 7 and am in need to use this program tonight.
is there any way i can get it working by then
Tell us
exactly what you do, what buttons you press before you get the error.
Also tell us the
exact error. And the exact point when this occurs.
So as an example: you start FreeStyler, open the sequence window by clicking on the icon in the menu, ...
You fill it in. Completely!
Re: "Subscript Out of Range"
Posted: 17 Nov 2020, 11:46
by algoes
Hello i have the same problem in version 4.0
Re: "Subscript Out of Range"
Posted: 18 Nov 2020, 02:52
by Partyman
Subscript out of range usually happens when people have created fixture files on one machine and copied the folder rather than export them. When you export fixture files it includes all the pictures, icons, and gobos associated with that fixture. When you just copy freestyler folders is does not install the fixture profiles correctly and gives the subscript error. You will also get that error.
You will also get this error if you have renamed any override buttons, sequence button, ... that is used in a cuelist, submaster, override, ...
Re: "Subscript Out of Range"
Posted: 18 Nov 2020, 07:15
by Poytoy
@Partyman Thanks so much. That problem was driving me nuts too.
Re: "Subscript Out of Range"
Posted: 17 Dec 2020, 20:05
by lj_raph
Hi, if you encounter this error post it in the bugtracker with the exact steps to replicate it and if possible include your backup file. This message can appear everywhere and mostly in case of a bug or a problem with the fixture file.
In version 4.0.1 you will encounter this messgae in the cuelist playback window, this will be fixed in version 4.1.
If you encounter it elsewhere let me know where.
Re: "Subscript Out of Range"
Posted: 27 Jun 2021, 19:07
by halfbright
Hi, has the issue of "Subscript out of range" been resolved?
I just got a new system & I have installed the newest version that is offered. (running windows 10). When I try to create a cue or a chase, it does not save the dimmer value. When I bring up the cue list window, the subscript message appears. If I close the program the next time I open it, the subscript message appears during the boot up cycle & locks up the program that I have to reboot the system. It stay that way until I reinstall the program with the restore defaults check.
Is this a new wrinkle to the problem?
Re: "Subscript Out of Range"
Posted: 11 Jul 2021, 16:08
by Crrispy
I get this error too, when dragging a sequence on a cue. Only does it with 1 sequence, I'll just redo it. 4.x still needs some fixing
Re: "Subscript Out of Range"
Posted: 13 Jul 2021, 22:43
by djSupport
halfbright wrote: 27 Jun 2021, 19:07
Hi, has the issue of "Subscript out of range" been resolved?
I just got a new system & I have installed the newest version that is offered. (running windows 10). When I try to create a cue or a chase, it does not save the dimmer value. When I bring up the cue list window, the subscript message appears. If I close the program the next time I open it, the subscript message appears during the boot up cycle & locks up the program that I have to reboot the system. It stay that way until I reinstall the program with the restore defaults check.
Is this a new wrinkle to the problem?
If you havent already please make sure you all report these bugs on the bug tracker!