rive-app / rive-app/rive-runtime
Unable to correctly read truncated audio assets
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
When I exported a riv file with audio assets, I chose to export the audio assets 'Second_stound' and its truncated assets 'Second_stound clip' in the referenced mp3 format, but I found that the two mp3 files had the same assetId in their names, like
‘Second_sound clip-1343663.mp3’
‘Second_sound-1343663.mp3’
When deserializing the riv file at runtime, it does not contain the assetIdPeopleKey property of 'Second_Sound clip', so the assetId of 'Second_Sound clip' will be generated separately, resulting in the inability to read 'Second_Sound clip 1343663. mp3' by uniqueFilename()
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing runtime deserialization of audio assets and the uniqueFilename() lookup, comparing how assetIdPeopleKey is handled for the original and truncated assets. Done means both exported MP3 files retain distinct, resolvable asset identities at runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100