Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow user to update peaks and/or duration with setOptions #3982

Merged
merged 1 commit into from
Jan 6, 2025

Conversation

botoxparty
Copy link
Contributor

@botoxparty botoxparty commented Jan 1, 2025

Issue: Need a way to update visual progress without triggering 'seeking' events

Current Behavior

When syncing WaveSurfer with external audio/time sources (like Tone.js transport), calling setTime() triggers the 'seeking' event because it updates both the media element's time and the visual progress. This will allow seeking and interact events to continue to work when syncing with an external source.

Problem

In scenarios where WaveSurfer is being used as a visual representation of audio that's controlled externally, we don't always want to trigger the media element's seeking behavior. Currently, there's no clean way to update just the visual progress without triggering seeking events.

Proposed Solution

Add a new public method to update only the visual progress

Let me know your thoughts, maybe you have a better solution with a your understanding of the lib.

Summary by CodeRabbit

  • New Features

    • Enhanced waveform progress tracking with a new method to update visual progress more precisely during audio playback.
  • Improvements

    • Improved handling of audio data options, allowing for better management of duration and peaks during playback.
    • Improved synchronization between audio playback and waveform visualization.
    • Added conditional checks for managing duration and peaks in audio options.

Copy link

coderabbitai bot commented Jan 1, 2025

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

src/wavesurfer.ts

Oops! Something went wrong! :(

ESLint: 9.17.0

ESLint couldn't find an eslint.config.(js|mjs|cjs) file.

From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:

https://eslint.org/docs/latest/use/configure/migration-guide

If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.

Walkthrough

The pull request modifies the setOptions method within the WaveSurfer class. It introduces new conditional checks for the duration and peaks properties of the options. If options.duration is provided without options.peaks, a decoded data buffer is created using the current peaks and the specified duration. If both properties are provided, a new decoded data buffer is created from these values. The call to update the renderer options has been repositioned to occur after these checks.

Changes

File Change Summary
src/wavesurfer.ts - Modified setOptions method to add conditional checks for duration and peaks properties.
- Updated method signature to public setOptions(options: Partial<WaveSurferOptions>).
- Moved this.renderer.setOptions(this.options) to the end of the method.

Poem

🎶 In waves we dance, with peaks so high,
Options set, as time flows by,
Buffers created, a sound so clear,
Surfer's magic, we hold dear!
🐇🎧 A melody crafted, for all to hear!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 48ecb32 and e9d95dc.

📒 Files selected for processing (1)
  • src/wavesurfer.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/wavesurfer.ts

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@@ -540,6 +540,11 @@ class WaveSurfer extends Player<WaveSurferEvents> {
this.options.interact = isInteractive
}

/** Update the visual progress */
public updateVisualProgress(time = this.getCurrentTime(), isPlaying = this.isPlaying()) {
Copy link
Owner

Choose a reason for hiding this comment

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

I'm reluctant to add a low-level method like this to the public API, especially since it's targeting quite an edge case.

You can easily render wavesurfer w/o playback by providing peaks and duration but no audio. See this example:
https://wavesurfer.xyz/examples/?0f80252d71c2f4a1ead0a572e1cefad3

It will still respond to setTime or seekTo but no actual playback will be happening, so you can visually sync it to an external player.

@botoxparty
Copy link
Contributor Author

So i've updated this PR, let me know if you think this is something that should be part of the libraries functionality.

Rather than destroying and initialising the wavesurfer all over again to update the duration (my application has a time stretch feature where the playback speed can be changed, therefore the duration of the same waveform can change. e.g. Warp in Ableton)

@botoxparty botoxparty changed the title Add updateVisualProgress method Allow user to update peaks and/or duration with setOptions Jan 3, 2025
Copy link
Owner

@katspaugh katspaugh left a comment

Choose a reason for hiding this comment

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

That's a good solution! Thanks!

@katspaugh katspaugh merged commit ef0ba84 into katspaugh:main Jan 6, 2025
3 checks passed
@katspaugh
Copy link
Owner

Released in 7.8.15.

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