rive-app / rive-app/rive-flutter

Unable to correctly read truncated audio assets

Open
#489 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Dart
Stars
1.5k
Forks
240
PR merge metrics
No merged PRs in 30d

Description

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()

Image
Source .riv/.rev file

button-with-audio

Expected behavior

Truncated assets 'Second_stound clip' has it own unique assetId.

Screenshots
Image
Device & Versions (please complete the following information)

Rive editor BETA 0.8.3105

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing runtime deserialization of the audio assets and the uniqueFilename() lookup described in the issue. Use the linked button-with-audio .riv/.rev asset to reproduce the truncated asset case, then verify that the truncated asset retains a distinct assetId and can be read by its generated filename.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart, flutter
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.