Skip to content

Conversation

@shiva-padakanti
Copy link

Implement a feature in the winrt-toast-reborn library to allow users to specify a custom audio file for Windows Toasts. This will provide greater flexibility and customization options for users who want to personalize their audio for their notifications.

@shiva-padakanti shiva-padakanti changed the title Add support for custom audio file in Windows Toasts [FEAT] - Add support for custom audio file in Windows Toasts Sep 8, 2024
AtifChy pushed a commit that referenced this pull request Aug 3, 2025
feat: better input handling
@AtifChy
Copy link
Owner

AtifChy commented Aug 3, 2025

I couldn't get it to work; can you also provide a sample working audio file?

@shiva-padakanti
Copy link
Author

I couldn't get it to work; can you also provide a sample working audio file?

It has been working as expected without any issues for my Tauri application (installed). However, given your feedback that it doesn't work, I re-tested it and found that custom audio only functions if the file is located within the application's installation directory or C:\Program Files. I also found relevant documentation from Microsoft: https://learn.microsoft.com/en-us/windows/apps/develop/notifications/app-notifications/custom-audio-on-toasts.

Therefore, I'm currently unsure about the precise behavior, but I will investigate further and provide an update. In the meantime, please try placing the audio file in C:\Program Files to see if that resolves the issue on your end.

@AtifChy
Copy link
Owner

AtifChy commented Aug 5, 2025

I checked doc and found these mentioned there.

Supported audio file sources:

  • ms-appx:///
  • ms-resource

Not supported audio file sources:

  • ms-appdata
  • http://, https://
  • C:/, F:/, etc.

I don't think we can support it. And putting the file in C:\Program Files is not an ideal way for handling this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants