-
Notifications
You must be signed in to change notification settings - Fork 426
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
updated wavesplit implementation. Tested only distance loss
- Loading branch information
1 parent
8d1ca2e
commit d8e7ef7
Showing
8 changed files
with
154 additions
and
184 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,11 @@ | ||
### WaveSplit | ||
|
||
things currently not clear: | ||
--- | ||
- not clear if different encoders are used for separation and speaker stack. (from image in the paper it seems so) | ||
- what is embedding dimension ? It seems 512 but it is not explicit in the paper | ||
- mask used (sigmoid ?) | ||
- when speakers in an example < sep stack outputs loss is simply masked or an embedding for silence is used ? (Probably masked) | ||
- is VAD used in WSJ02MiX/ WHAM for determining speech activity at frame level ? Some files can have pauses of even one second | ||
- loss right now is prone to go NaN especially if we don't take the mean after l2-distances computation. | ||
|
||
--- | ||
structure: | ||
- train.py contains training loop (nets instantiation lines 48-60, training loop lines 100- 116) | ||
- losses.py wavesplit losses | ||
- wavesplit.py sep and speaker stacks nets | ||
- wavesplitwham.py dataset parsing | ||
we train on 1 sec now. | ||
|
||
tried with 256 embedding dimension. | ||
|
||
still does not work with oracle embeddings. | ||
|
||
not clear how in sep stack loss at every layer is computed ( is the same output layer used in all ?). | ||
Also no mention in the paper about output layer and that first conv has no skip connection. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.