Skip to content

Upgrade Symphonia dependency to 0.6.0 - #157

Merged
tesselode merged 4 commits into
tesselode:mainfrom
Eagisa:symphonia-0.6-upgrade
Jul 16, 2026
Merged

Upgrade Symphonia dependency to 0.6.0#157
tesselode merged 4 commits into
tesselode:mainfrom
Eagisa:symphonia-0.6-upgrade

Conversation

@Eagisa

@Eagisa Eagisa commented May 26, 2026

Copy link
Copy Markdown
Contributor

Updated Symphonia from 0.5.4 to 0.6.0.

I tested the upgrade locally and did not encounter issues during playback testing.

I also ran cargo test, and all tests passed successfully.

Since there was a previous note mentioning that updating Symphonia would require investigation into the changes, I wanted to share this update in case it helps.

Comment thread crates/kira/src/sound/static_sound/data/from_file.rs Outdated
@tesselode

Copy link
Copy Markdown
Owner

Please run rustfmt on the files to reduce diff noise. Thanks!

@Eagisa

Eagisa commented Jun 8, 2026

Copy link
Copy Markdown
Contributor Author

Hey, I've addressed your feedback! Removed the UnexpectedEof special case in from_file.rs and ran rustfmt, turns out no changes were needed since the code was already following the project's formatting. All 98 tests pass. Let me know what you think!

.try_into()
.expect("could not convert u64 into usize"))
let actual = seeked_to.actual_ts.get();
Ok(if actual < 0 {

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this an actual thing that can happen? Can the timestamp be less than zero or more than the number of frames?

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK I did some investigation on this. mp3 and ogg files can start at and seek to negative timestamps. I tried changing Decoder::seek to return an i64 timestamp, but this lead to a bug with looping streaming sounds where the decoder would run out of frames before the decoder_current_frame_index reached num_frames. So in practice, this seems to be a good way to handle negative timestamps.

@tesselode

Copy link
Copy Markdown
Owner

thank you for the PR!

@tesselode
tesselode merged commit 20e1f5c into tesselode:main Jul 16, 2026
24 checks passed
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