Latest restricted WACUP beta release is build #18798 (April 7th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #17040 (September 30th 2023) (x86 only)


NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.

Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.

Author Topic: Send to Wavepeak  (Read 3979 times)

Dr.Flay

  • Evil Genius
  • Beta Tester
  • Hero Member
  • *****
  • Posts: 145
  • AMIGA Forever
    • View Profile
    • About Me
Send to Wavepeak
« on: July 02, 2018, 05:30:28 PM »
How about being able to batch process wave peaks the same way volume peaks are done ?
eg. I use the sendto function to level a new track someone gives me while doing my live show. It would be handy to see the waveform already done when actually first playing the file, as sometimes I may need to skip an intro.

could they not be a single plugin with both features so you can have it do either or both at the same time ?

Often a podcast or long-mix shows a quiet waveform with little visible variation, so I volume level it, then rescan the waveform again.
3 time-consuming scans in total.
This could be more optimal I think.
My weekly radio show on Source FM ☛ 15% Extra

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 4488
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: Send to Wavepeak
« Reply #1 on: July 02, 2018, 07:04:57 PM »
I think there's an existing request for the waveform seeker plug-in to be able to batch process but I'd not thought about also doing it as part of the replaygain calculations.

Probably a simpler way to just get something working would be for the waveform seeker plug-in to know if a file has been processed for replaygain & if the tags get updated then it send out a quick notification which can be caught & at least allow the waveform seeker plug-in to either delete it's cache for that file &/or attempt a re-process. I'd probably lean more on just delete the cache as there's already a lot going on when doing a batch tag update (as tag writing can be a bit delayed so you might re-process before the new values are seen) without also doing a re-processing of the audio to make a new cached render.

-dro