Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-230724] Add new LSL functions to play sounds via child prims #8336

Closed
2 tasks
sl-service-account opened this issue May 9, 2021 · 7 comments
Closed
2 tasks

Comments

@sl-service-account
Copy link

sl-service-account commented May 9, 2021

How would you like the feature to work?

Add at least four new LSL functions: llPlayLinkSound, llTriggerLinkSound, llLoopLinkSound, and llStopLinkSound. These should operate as their non-link versions, but offset to a specified child prim.

Why is this feature important?

There are often times you need to offset a sound source from the root prim. The root might be offset to allow for better rotational handling, or might be something that handles multiple sound sources (something that governs multiple doors, for example). Currently, the way to achieve that is with secondary scripts that communicate with the primary one, one for each new sound source. This can quickly clutter what would otherwise be a one script project with half a dozen four line scripts that only play sounds off of commands from the main script.

Being able to call sounds in link prims would thus reduce the amount of total scripts (and costly script communication) for a swath of project types, but also make things cleaner, easier to understand, and more in line with the powers singular scripts typically have over root prims (with llSetLinkPrimitiveParams et al). 

PS: The Feature Request form seems to be having an issue and wiped all my input. This was manually recreated.

Links

Related

Duplicates

Original Jira Fields
Field Value
Issue BUG-230724
Summary Add new LSL functions to play sounds via child prims
Type New Feature Request
Priority Unset
Status Closed
Resolution Duplicate
Reporter Alkaia Exonar (alkaia.exonar)
Created at 2021-05-09T15:30:53Z
Updated at 2021-05-12T17:55:56Z
{
  'Build Id': 'unset',
  'Business Unit': ['Platform'],
  'Date of First Response': '2021-05-09T16:40:40.531-0500',
  'How would you like the feature to work?': 'Add at least three functions to LSL: llPlayLinkSound, llTriggerLinkSound, and llLoopLinkSound. They should operate like their non-link versions, just attached to (or at the position of) the child prim specified.',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'Target Viewer Version': 'viewer-development',
  'Why is this feature important to you? How would it benefit the community?': "There are a lot of times when you need to play a sound in a child prim for one reason or another - combining multiple doors into a single script, making speaker sets, having the root prim be offset for rotational reasons but the sound source elsewhere. Currently the only way to do that is to put in a secondary script that communicates with the primary one.\r\n\r\nBeing able to handle it all from one central script would cut down on lag, cut down on script usage, and be generally cleaner and more in line with other things LSL can do via link. This would also allow things like sound amplifiers to be lighter loads on a sim's script resource budget.",
}
@sl-service-account
Copy link
Author

Aliton Firehawk commented at 2021-05-09T21:40:41Z

This would be an extremely useful feature, and will heavily reduce certain projects I have on their script resources.

@sl-service-account
Copy link
Author

yasmina.zimminy commented at 2021-05-09T21:42:11Z

Would be a useful feature

@sl-service-account
Copy link
Author

JIRAUSER337086 commented at 2021-05-09T22:31:58Z

This feature would help save on script resources, which is extremely important in a variety of environments in Second Life.  I think it would be greatly appreciated. 

@sl-service-account
Copy link
Author

JIRAUSER337083 commented at 2021-05-10T21:26:28Z

I work at Fantasy Faire, and we face many challenges relating to scripts. Any project which will be of benefit to SL at large, but our specific challenges as well, would be greatly appreciated.

 

@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2021-05-11T18:23:52Z

Note for Lindens: I think this suggestion is already filed internally at SL-11982

@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2021-05-11T18:24:42Z

PS: The Feature Request form seems to be having an issue and wiped all my input. This was manually recreated.

Yes, this is a known bug with JIRA. The Lindens are working on fixing it.

@sl-service-account
Copy link
Author

Kyle Linden commented at 2021-05-12T17:55:57Z

Hello,

This is a duplicate request of BUG-227641

Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant