Significant audio quality drop (timbre_transfer notebook) in 0.14.0
See original GitHub issueThe recent push to 0.14.0 includes a change that seems to have messed with the performance of the pretrained models. Unfortunately, there were a lot of commits in that version push, so I’m not exactly sure what the cause is yet, but I suspect it may be something regarding loading the checkpoints improperly.
I’m looking into this right now, but for now, if you want to avoid this I recommend installing version 0.13.0, and I will make that the default for the notebook for now.
!pip install ddsp==0.13.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Bluetooth headphones drop in audio quality when running a ...
I'm watching a youtube video in Chrome, and the audio sounds perfectly normal, as expected. But as soon as I launch Modern Warfare,...
Read more >Real-Time Timbre Transfer and Sound Synthesis using DDSP
In this paper, we present a real-time implementation of the DDSP library embedded in a virtual synthesizer as a plug-in that can be...
Read more >10 EASY Ways to Improve Audio/Sound Quality on a Windows ...
This video will show you how to improve the audio and sound quality on a Windows 10 PC. I'll be showing you five...
Read more >If sound quality is reduced when using Bluetooth headphones ...
If audio quality is still reduced, try selecting your Bluetooth headphones again: Click Control Center in the menu bar, then click Sound. Select ......
Read more >Select or Change your Audio Quality - YouTube Music Help
Select your download audio quality · In the YouTube Music app, tap on your profile picture. · Select Settings. · Tap Downloads &...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Sorry you had the trouble. I believe the DAGLayer was having trouble claiming the variables of its sub components. Looks like it came from using
__dict__[]instead ofsetattr()to create modules in DAGLayer, which was skipping__setattr__where variable inheritance occurs, so the processor_group variables weren’t collecting the IR variable from Reverb.As ddsp.training is actively used for research purposes, we unfortunately don’t have the bandwidth to support complete backwards compatibility, but hopefully versions before 1.0 should work for old models and training new models with 1.0 should still work.
On Tue, Feb 2, 2021 at 7:59 AM lauraibnz notifications@github.com wrote:
I checked further and the FiltereNoise output signal was actually fine, but the Reverb was acting differently (something to do with the latest changes in the dags?), outputting a very low signal. Finally using a copy of the old RnnFcDecoder with the old nn functions and a copy of the old ProcessorGroup (even using the new synths and effects) made it possible to use the old models as before. Still haven’t figured out why this is happening though.