1  |   Order by index

Jun 3, 2003, 4:56pm

Say you have a mid trigger object with named objects around it in the same
area playing the same song to all them named objects.
Or just have many of the same mid all over the area you want it in.
Can you make it so the mid will not rest before it's finished playing if you
loose sight of the farthest one?

It did this in version 2.2 and earlier but only if it was the 100% same mid
on all objects.
I don't like walking around and it resets in the middle of the song just
because you lost sight of the farthest object it was on.
Shouldn't the closer ones keep it going without resetting it like it did in
version 2.2 ?

Jun 7, 2003, 12:05pm

Also please add a "nofade" command for us so we can make mid files not fade
when you walk away from them just like they where in version 2.2

Don't get me wrong, fading is good for radios and stuff in the room to give
a real feel of the music fading in and out as you walk away or to it just
like in real life.

But its not real good thing to have full area background music fading in and
out on you when it should be constant like in 2.2





[View Quote]

Jun 7, 2003, 12:57pm

The noise command is supposed to serve that purpose.

http://host.activeworlds.com/TechnoZeus/aw34/noise_command.html
http://host.activeworlds.com/TechnoZeus/aw34/sound_command.html
http://host.activeworlds.com/TechnoZeus/aw34/mp3.html

TechnoZeus

[View Quote]

Jun 7, 2003, 2:51pm

Yes it dose, but it will not loop that way, and if you come to another mid
that is different it will not start till the 1st one finished.

I need no fading, looping on, and the mid to stop when you are close to a
different one so it can start playing.



[View Quote]

Jun 8, 2003, 8:35am

Ah, okay. So what you really need is the addition of support for the "loop" argument with the noise command. Correct?

http://host.activeworlds.com/TechnoZeus/aw34/loop_argument.html

I think it would be best if parameters that are supported by any command would also have support added on any commands that they would make sense on... and this is a good example. In fact, I made a post suggesting such changes back in October of last year. There are many parameters which it would make sense to add support for on some of the commands that currently lack such support.

TechnoZeus


[View Quote]

Jun 8, 2003, 9:43am

do this on 2 objects in the same area about 5 meters apart.
"replace mymid.mid with your mid choice"
1st object = create sound mymid.mid loop
2st object = create sound mymid.mid loop
Ok now move from one to the other, notice how the one you are closest to
always plays?

Now on the same objects do this.
1st object = create noise mymid.mid
2st object = create sound mymid.mid
Loop don't work for this.
Ok now move from one to the other, notice how the one you are closest to
will never play until the other mid has played all the way to it's end and
stopped? Even if you remove that mid object it will still be playing it till
it finishes before starting any others.

This is why I can't use the noise command for this.




[View Quote]

Jun 8, 2003, 9:46am

Opps typo, sorry.
That all should read like this.

do this on 2 objects in the same area about 5 meters apart.
"replace mymid.mid with your mid choice"
1st object = create sound mymid.mid loop
2st object = create sound mymid.mid loop
Ok now move from one to the other, notice how the one you are closest to
always plays?

Now on the same objects do this.
1st object = create noise mymid.mid
2st object = create noise mymid.mid
Loop don't work for this.
Ok now move from one to the other, notice how the one you are closest to
will never play until the other mid has played all the way to it's end and
stopped? Even if you remove that mid object it will still be playing it till
it finishes before starting any others.

This is why I can't use the noise command for this.







[View Quote]

Jun 9, 2003, 7:05pm

Ah, okay. Yes, that behavior of the noise command used to be the only way that AW would play a MIDI file at all, and at that time you couldn't play them with the noise command. So, perhaps an additional parameter (or two) could allow control the relative distance based behavior such as which one plays, whether or not the other ones will continue playing also if the sound card supports it, and whether or not volume and balance are effected by relative position.

I tried the overlap parameter with a MIDI file on the noise command, and I found almost the exact opposite behavior. It starts (or restarts) the MIDI attached to an obect when that object enters visibility range, effectively making the farthest one away always play since it generally will enter the scene later than the closer ones.

Anyway, I agree that this is something that should be looked into. The situation with thhe noise and sound commands is much more versatile than it used to be, but could still use some improvements.

TechnoZeus


[View Quote]

1  |   Order by index