Trouble Uploading Custom Sounds

[AGreen]

Hi there!

I am having trouble uploading custom sounds onto the configurator app. I used Audacity to record the sound at 11025 Hz and exported it as an 8-bit .WAV file. When I try to upload the sound, I get the error message below. I just uninstalled and re-installed the configurator app on the Microsoft Store to make sure I am using the most up to date version but I am still receiving the same message. Whenever I go to the "Sound maker" section it just says "Search" with a loading bar but never actually loads anything. 

Any help would be greatly appreciated! Thanks!

[Service]

On 9/5/2019 at 10:29 PM, AGreen said:

Hi there!

I am having trouble uploading custom sounds onto the configurator app. I used Audacity to record the sound at 11025 Hz and exported it as an 8-bit .WAV file. When I try to upload the sound, I get the error message below. I just uninstalled and re-installed the configurator app on the Microsoft Store to make sure I am using the most up to date version but I am still receiving the same message. Whenever I go to the "Sound maker" section it just says "Search" with a loading bar but never actually loads anything. 

Any help would be greatly appreciated! Thanks!

Hello.

Please check your application version. It must be 1.1.60, the latest version for now. This bug was already fixed. Also, make sure that there is no any additional information in this sound file, such as artist name, album and etc. (no metadata). 

[DanielTERRAN]

On 10/17/2019 at 1:40 PM, Service said:

Hello.

Please check your application version. It must be 1.1.60, the latest version for now. This bug was already fixed. Also, make sure that there is no any additional information in this sound file, such as artist name, album and etc. (no metadata).  

The latest version for the X-Gen Software in Microsoft Store is 1.135!!!

[Robert Wilson]

The version mismatch is the likely culprit here — if Store is offering 1.135 while the fix landed in 1.1.60, those aren't the same build line, so reinstalling from the Store may just keep pulling the newer package with the bug intact. Worth confirming the exact build string in the app's About panel rather than trusting the Store listing. On the WAV itself: Audacity often embeds metadata unless you clear it in the export dialog, and 8-bit PCM is picky. Try re-exporting with metadata stripped and check whether Sound maker still hangs.

[Robert Wilson]

The version mismatch is the likely culprit here — if Store is offering 1.135 while the fix landed in 1.1.60, those aren't the same build line, so reinstalling from the Store may just keep pulling the newer package with the bug intact. Worth confirming the exact build string in the app's About panel rather than trusting the Store listing. On the WAV itself: Audacity often embeds metadata unless you clear it in the export dialog, and 8-bit PCM is picky. Try re-exporting with metadata stripped and check whether Sound maker still hangs.

[Robert Wilson]

The version mismatch is the likely culprit here — if Store is offering 1.135 while the fix landed in 1.1.60, those aren't the same build line, so reinstalling from the Store may just keep pulling the newer package with the bug intact. Worth confirming the exact build string in the app's About panel rather than trusting the Store listing. On the WAV itself: Audacity often embeds metadata unless you clear it in the export dialog, and 8-bit PCM is picky. Try re-exporting with metadata stripped and check whether Sound maker still hangs.

[Robert Wilson]

The version mismatch is the likely culprit here — if Store is offering 1.135 while the fix landed in 1.1.60, those aren't the same build line, so reinstalling from the Store may just keep pulling the newer package with the bug intact. Worth confirming the exact build string in the app's About panel rather than trusting the Store listing. On the WAV itself: Audacity often embeds metadata unless you clear it in the export dialog, and 8-bit PCM is picky. Try re-exporting with metadata stripped and check whether Sound maker still hangs.

[Robert Wilson]

The version mismatch is the likely culprit here — if Store is offering 1.135 while the fix landed in 1.1.60, those aren't the same build line, so reinstalling from the Store may just keep pulling the newer package with the bug intact. Worth confirming the exact build string in the app's About panel rather than trusting the Store listing. On the WAV itself: Audacity often embeds metadata unless you clear it in the export dialog, and 8-bit PCM is picky. Try re-exporting with metadata stripped and check whether Sound maker still hangs.