Skip to content

[Bug?] Problems with UVR-DeEcho-DeReverb #4

@ShiromiyaG

Description

@ShiromiyaG

I tested several models, both MDX, MDXC and VR, but the only model that I had results that were actually worse than the UVR GUI was the UVR-DeEcho-DeReverb. Here is a link to a song comparing UVR-DeEcho-DeReverb and MDX Reverb HQ from the UVR api, along with UVR-DeEcho-DeReverb from the UVR GUI

https://drive.google.com/drive/folders/1_E0PzZRtK4f8Ah3rknJBDitZZvDNnFeO?usp=drive_link

And this is the code I used:

MDX = models.MDX(name="Reverb_HQ",  other_metadata={'segment_size': 256,'overlap': 0.75,'mdx_batch_size': 8,'semitone_shift': 0,'adjust': 1.08, 'denoise': False,'is_invert_spec': False,'is_match_frequency_pitch': True,'overlap_mdx': None},device=device, logger=None)
res = MDX(name)
seperted_audio = res["no reverb"]
Vr = models.VrNetwork(name="UVR-DeEcho-DeReverb", other_metadata={'normaliz': False,'aggressiveness': 0.05,'wav_type_set': "PCM_F32",'window_size': 320,'batch_size': 4,'is_tta': True},device=device, logger=None)
res = Vr(name)
seperted_audio = res["no reverb"]

Also, a photo of Audacity comparing Reverb HQ and UVR-DeEcho-DeReverb:
image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions