Syntax error with llGetListLength

Hi again.

Hopefully just a quick one. I'm being given a syntax error with the following line of code but cannot for the life of me see what is wrong. Supposedly the error is where the brackets begin surrounding mySounds.

integer listLength = llGetListLength(mySounds);

Here's the code in full to see if I'm going wrong elsewhere in the script.

list mySounds = ["FemHysteric1", "FemHysteric2", "FemHysteric3", "FemHysteric4", "FemHysteric5"];
integer listLength = llGetListLength(mySounds);
integer x;

default {
state_entry() {
llStopSound();

}

touch_start(integer num_detected) {
for (x = 0; x < listLength; x++)
{
llPlaySound((llList2String(mySounds, x), 1);
}
}

}

Thanks.

You cannot make function calls outside of a function. Declare listLength globally but then assign it in state_entry, for example. You also have an extra open-paren in the llPlaySound line.

Thanks for that.

Now I've got another problem, not syntax related. What I'm trying to do is have the sound files played one after the other when the object is clicked. What seems to be happening at the moment is that the following sound almost immediately cuts off the one before. I'm guessing I need to involve a timer, or find a way to allow the sound file to play fully before moving on to the next. Any ideas as to what would be the easiest method for this?

Thanks again.

this may work
http://wiki.secondlife.com/wiki/LlSetSoundQueueing

list mySounds = ["FemHysteric1", "FemHysteric2", "FemHysteric3", "FemHysteric4", "FemHysteric5"];
integer listLength;
integer x;

default {
state_entry() {
listLength = llGetListLength(mySounds);
llStopSound();

}

touch_start(integer num_detected) {
llSetSoundQueueing(TRUE);
for (x = 0; x < listLength; x++)
{
llPlaySound((llList2String(mySounds, x), 1);
}
}

}

That is very nearly there but unfortunately it'll only queue one sound. I don't know if there's any way to increase this by using some sort of workaround. I guess I'll keep plugging away at it. Thanks for your input, and if anyone else has any ideas i'd be glad to hear them.

ah ok, hmm, maybe put that call inside the for loop, so it does it before each sound, not sure though, i think the for loop might be too fast for it the sounds to catch up.

list mySounds = ["FemHysteric1", "FemHysteric2", "FemHysteric3", "FemHysteric4", "FemHysteric5"];
integer listLength;
integer x;

default {
state_entry() {
listLength = llGetListLength(mySounds);
llStopSound();

}

touch_start(integer num_detected) {
for (x = 0; x < listLength; x++)
{
llSetSoundQueueing(TRUE);
llPlaySound((llList2String(mySounds, x), 1);
}
}

}

you could possible try this one, adapted from the animation one i wrote a couple days ago
/54/1f/314508/1.html#post2376633

list mySounds = ["FemHysteric1", "FemHysteric2", "FemHysteric3", "FemHysteric4", "FemHysteric5"];
list times = [ 5.2, 8.1, 6.0, 5.2, 8.3];//times are just examples, change to what you need

integer i = 0;
integer len;

float time;

string sound;
string next;

default
{
state_entry()
{
len = llGetListLength(mySounds);
}

on_rez(integer rp)
{
llResetScript();
}

touch_start(integer num)
{
time = llList2Float(times, i);
sound = llList2String(mySounds, i);
next = llList2String(mySounds, (i +1) %len);
llSetTimerEvent(time);
llPlaySound(sound);
llPreloadSound(next);
}

timer()
{
i = (i +1) %len;
time = llList2Float(times, i);;
sound = llList2String(mySounds, i);
next = llList2String(mySounds, (i +1) %len);
llSetTimerEvent(time);
llPlaySound(sound);
llPreloadSound(next);
}

}

OK I've cracked it. This is what I've gone with and it's working fine.

list mySounds = ["FemHysteric1", "FemHysteric2", "FemHysteric3", "FemHysteric4", "FemHysteric5"];
integer listLength;
integer x;

default {
state_entry() {
x = 0;
llStopSound();
listLength = llGetListLength(mySounds);
}

touch_start(integer num_detected) {
llSetTimerEvent(10.0);
}
timer() {

llPlaySound(llList2String(mySounds, x), 1);
x++;
state playing;
}


}

state playing {
touch_start(integer num_detected) {
llSetTimerEvent(0);
state default;
}
}
///

Only problem with this is that there is a wait of 10seconds before the first sound begins. I wasn't sure if setting the timer to 0 in the touch_star and then setting it to 10 in the actual timer event would work correctly. Although there's no reason I can't try it. I suppose we'll soon see. Thanks again!

in the touch start you can set it to a very small amount of time, but bigger than 0.0, and then in the timer event change it to 10.0

Yup! That works a treat. Here's the revised version.

list mySounds = ["FemHysteric1", "FemHysteric2", "FemHysteric3", "FemHysteric4", "FemHysteric5"];
integer listLength;
integer x;

default {
state_entry() {
x = 0;
llStopSound();
listLength = llGetListLength(mySounds);
}

touch_start(integer num_detected) {
llSetTimerEvent(1.0);
}


timer() {
llSetTimerEvent(10.0);
if (x < listLength){
llPlaySound(llList2String(mySounds, x), 1);
x++;
} else {
llSetTimerEvent(0);
llResetScript();
}
}

}

I added the if-else so that the script won't continue calling the timer event once it's reached the end of the list. Not sure if it's necessary to have both setTimer and Reset script. The reset script has to be there or once it's finished you can't start it again. Although now I think about it I could just set x to 0 again.

Thanks again.

if you use the increment method i used it should work
notice i put

i = (i+1)%len

/54/5a/274402/1.html#post2094873
/54/5a/274402/1.html#post2094889

list mySounds = ["FemHysteric1", "FemHysteric2", "FemHysteric3", "FemHysteric4", "FemHysteric5"];
integer listLength;
integer x;
integer OnOff = 0;

default {
state_entry() {
x = 0;
llStopSound();
listLength = llGetListLength(mySounds);
}

touch_start(integer num_detected) {
if(!OnOff){llSetTimerEvent(1.0);
OnOff = 1;}
else{llResetScript();}
}


timer() {
llSetTimerEvent(10.0);
llPlaySound(llList2String(mySounds, x), 1);
x = (x +1)%listLength;
}

}

I know this sounds like a really basic question, but I can't find documentation to explain what this operation means. Can you explain?

i didn't understand it either, i just know it works for me lol.

edit: found this definition on this page http://www.answers.com/topic/modular-arithmetic

seems to fit this used, but i can't seem to understand how it works exactly. the remainder of 9/4 is 1, but so is 5/4, so 4 hours after 5 isn't 1, but 9, so i don't understand.

hmm, how about 5+4 = 9/7(12 - 5) remainder is 2? nope
5+4 = 9, 12/9 the remainder is 3, yeah, i'm all confused.

hewee! you told me about this, can you explain? lol

n.

A form of arithmetic dealing with integers in which all numbers having the same remainder when divided by a whole number are considered equivalent: Clocks use modular arithmetic with modulus 12, so 4 hours after 9 o'clock is 1 o'clock.

Cool. I love black boxes. So tell me ..... on successive calls to this black box, what output does it produce? (I can't get in world right now to experiment, or I'd play with it myself to find out.)

wait, i think i got it, the modular # is 12 with the clock example.

9+4 = 13
13/12 = 1 r1

so with a modular of 21
9+1= 10
21/10 = 2 r1 ?huh?

nope, still confused

edit: oh ok, further down, it shows that it re-wraps with the remainder once it reaches the modular, but what about for decreasing the number?

1 - 1 = 0
0 - 1 = -1
how does it know to start over at 12(or in this case 12 + -1 = 11)
because the result would be less than 0 it automatically goes to the modular?

A number mod 12 just gives results in the range 0 to 11.

0 % 12 = 0
1 % 12 = 1
2 % 12 = 2
...
10 % 12 = 10
11 % 12 = 11
12 % 12 = 0
13 % 12 = 1
14 % 12 = 2
...
etc.

So the code "x = (x + 1)%listLength" just forces the list index to be in the range 0 to (listLength - 1).

The long version of the same code is like this:
x = x + 1;
if (x >= listLength) x = 0;

Ah! Now that makes sense, especially with your translation at the end. Thanks.

that's what i meant (and thought, but wasn't sure if, that was the way it worked), just didn't know how to explain it lol, thanks ultralite

%(modulus) is the same operation as r(remainder) from grade school when you first learned long division. it's the whole leftover after dividing one number into another.

Yeah. I just couldn't see at first how modulo was relevant here, so the notation was getting in my way. Got it now, though. Thanks for being patient.