I’m attempting to make a mini music playlist GUI, but I am not sure whether to use one Sound instance and constantly change its SoundId via a looping script or to use multiple Sound instances and play the corresponding Sound and loop.
I feel it would generally be better to use one instance as it would save memory, but using it now gives me second thoughts. The scripts have to wait for the sound to load which takes a while for some clients. If I were to use multiple instances then they would all be preloaded and play instantly.
depends i mean if you have a script it would be synced but if you are planning on uploading for example 1 hour of music (very rare) then i would suggest splitting it up and if you make a radio splitting the sounds up means you know when music starts and the name so you can show the name of the song
at the end of the day i would suggest one if timing isnt really important and more if you are planning on making a radio for example
well how do you know what songs is playing on a radio i mean at first you can program it in at witch times but you cant add another song (im also making a radio and thats the problem i run into)
Your problem of implementing it;
You can make a dictionary that uses sound ID as a key for information about a song, or you can use AssetService/MarketPlace service, etc.
Don’t argue on a topic when you cannot come up with a simple solution please:pray:.Plus Instances is insanely heavy on memory and sound data does get cached anyway.
