Envelope plugin usability #4068
Unanswered
BillGoldsmith
asked this question in
Q&A
Replies: 1 comment 1 reply
-
You should define at least two points with volume 1, e.g. at the 0 mark and at the end mark (= duration). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all. I'm new to Wavesurfer. Overall I am extremely impressed with the project. In many ways it is absolutely perfect for my use case.
However, I'm having an issue. I'm wanting to use the envelope plugin to manage fade-in and fade-out on files in a radio automation system. I need to be able to easily adjust the timing and duration of the fades so that users can preview how song transitions will sound when played back on the air.
I'm assuming that there must be some way to load the plugin with the default volume at 1 rather than 0, but I haven't found it.
If I load the plugin with no points defined, the volume stays at 0, ignoring the setting:
const envelope = EnvelopePlugin.create({
volume: 1,
lineColor: 'rgba(162, 0, 255, 0.59)',
lineWidth: 4,
dragPointSize: 12,
dragLine: true,
dragPointFill: 'rgba(93, 0, 255, 0.85)',
dragPointStroke: 'rgba(0, 0, 0, 0.5)',
});
Is that the expected behavior? Even setting wavesurfer's volume to 1 after the plugin is registered doesn't help.
I'm also having some major problems with how envelope's canvas is rendering. You can guess what it should look like. Here's what I'm seeing:

The bottom waveform has envelope (and only envelope, no other plugins loaded), the top one does not. My fear is that the small canvas size (360px x 120px), which would be very difficult to make much larger, coupled with large files (FLAC, most at least 3 minutes) is pushing envelope's capabilities too far. To manage fine-grained adjustments on those files, envelope would need to play nicely with zoom & regions. I can see where that would be tricky.
Currently, not only is the display mangled, but the points aren't really adjustable. Even small mouse movements are greatly exaggerated and unpredictable.
I'm hoping that there's just some dumb little thing I'm doing wrong, as is often the case. Or am I asking the impossible here?
I was looking for a way to easily provide all of the operating parameters (ie contents of the wavesurfer object) but didn't find one. Suggestions welcome.
Beta Was this translation helpful? Give feedback.
All reactions