Spaces:
Running on Zero
Running on Zero
Commit History
2 days ago
-
Finish loading in pyharp's worker before process_fn can reserve a GPU. Running
Verified signature72ad407 -
Wait for the worker's own download thread instead of failing the first request.
Verified signature889a592
5 days ago
-
Tidy the launch call and drop stray files
Verified signaturef3ba3f4 -
Roll pyharp and tidy the card description
Verified signatureab81a13 -
Prune tags that predate the taxonomy
Verified signature85e7ce5 -
Read the beat checkpoint from the weights repository, not from another Space
Verified signature2545498
6 days ago
-
Declare the more restrictive of the code and weights licenses
Verified signaturecbff866 -
Declare the more restrictive of the code and weights licenses
Verified signature7eb9512 -
Tidy the description's formatting
Verified signature9ab0a3a -
Declare the code's license and state the weights' terms in the description
Verified signaturea187165 -
Credit the original authors and link the repository and paper
Verified signature2aa88e1 -
Fix the launch keywords and the taxonomy import
Verified signature4a6e1a6 -
Bring the Space up to the pyharp example standard (taxonomy tags, __main__ guard, show_error, v0.4.0)
Verified signature5447224
-
cleanup: remove dead MAGNeT/MBD loader code, drop redundant dbn=False, remove loopgen-repo reference copy
Vansh Chugha80fd99 -
remove debug prints, restore gpu duration
Vansh Chughf8c94d1 -
note in model card that output loops twice
Vansh Chughfffb8ef -
add debug prints for loop length investigation
Vansh Chugh29294cb -
match original pipeline's loop-doubling at max duration
Vansh Chughc0089ac
-
try torch 2.10.0 to match xformers build, shrink gpu duration for testing
Vansh Chugh9da6de5 -
initial deploy
Vansh Chugh83e59db