-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose AudioStreamMP3 loop properties to the editor inspector #55570
Conversation
What's the use-case for this? The only thing I can think of is that it could be useful for making many copies of the same audio resource without making many copies of the same file (e.g. by opening the audio stream in the inspector, making edits, then doing a save-as operation to persist those changes in a |
In the editor properties, you can set the loop and loop_offset for ogg type of audio however currently you can't set the loop and loop_offset for mp3 type of audio. |
This is the main reason. AudioStreamMP3 is the only AudioStream type that doesn't have these properties exposed, so this is mainly for consistency and to avoid confusion. To add, not having to re-import just to change the |
I don't agree that this will avoid confusion, but I'm approving it anyway because I don't like that MP3s are different from the rest of the streams right now. If anything I think it's pretty confusing that these properties will now show up in the inspector and the import options screen, but that's just a quirk of the way Godot works. Thanks for finding this and bringing the mp3 stream to parity! |
Yes it's a source of confusion for users that needs to be addressed more generally for all audio formats. It's good to make MP3 match the current status quo indeed. |
Thanks! |
Cherry-picked for 3.5. |
Cherry-picked for 3.4.1. |
Exposes
loop
andloop_offset
properties ofAudioStreamMP3
resources to the editor inspector to mirror behaviour of otherAudioStream
resources. Addresses #53855.I'm not 100% sure this should be both an editor property and an import setting, what's the general consensus on this?
Bugsquad edit: Fix #53855