Fabian-Robert Stöter

We are about to release a js framework with all the required pre and postprocessing soon. Stay tuned

@chenei we are updating the framework to support tf 2.2. ETA next two weeks. @TheoBr we could could for sure get some help. We only implemented the pre- and postprocessing....

@AdrianButnar @TheoBr sorry for the slow response. We managed to get the full open-unmix and spleeter models working. If any of you are js devs, we would love some feedback....

@theblissprogrammer @Syps @AdrianButnar @TheoBr sorry for the long delay. We have working models but we are currently working on speeding up inference and reduce memory usage. See a W.I.P site...

@Mixerrog @skratchdot yes. RAM is an issue in long files. For now: - use chrome - try

> Hey @faroit @TheoBr, just checking on updates for the tf.js port or any JS version released for the spleeter module. > > > > Is there anything along the...

@mmoussallam sounds great > It would definitely be nice to allow writings of stem files as output of spleeter separate. Using stempeg to this aim seems to be the best...

@mmoussallam I've updated this showcase draft PR to reflect the recent changes in the stempeg beta (See faroit/stempeg#28). This PR now does __not__ implement a stems output but instead revert...

Yes, I know about ffprobe errors, I get these issue from users of musdb all the time as well ;-) > Do you think we can add an equivalent mechanism...

@turian @ashleve what worked for me as a workaround is making the experiment dirs static (especially for multiruns/sweeps) e.g. ``` hydra: run: dir: experiments/${your_run_name} job: chdir: False sweep: dir: experiments/${your_run_name}...