[FEAT(extract_stems)]: tidy up bass guitar extraction from demucs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 54/100
Research direction
Start at the extract_stems entry point and trace how mute=["bass"] determines the returned keys and output filename. Check the related tests or add a focused regression test for this call; done means the bass-muted extraction no longer raises KeyError when accessing the documented result and its saved output has a consistent name.
Written by the indexing model from the issue text.
Description
testing issue forms, for a real issue
Summary
It's not clear how to access the bass only stem from current syntax
# (IN PROG) TEST EXTRACT BASS
# results = ds.extract_stems(AUDIO_FILE_11, verbose=True)
# Extract all stems
stem_result = ds.extract_stems(
AUDIO_FILE_11,
all_stems=True,
output_dir="stems",
# full=True, # LEGACY (v0.1.5)
verbose=True,
)
#print(f"Bassless track: {stem_result['bass']}")
## BASS BACKING TRACK
results = ds.extract_stems(AUDIO_FILE_12, mute=["bass"], verbose=True)
print(f"Bassless track: {results['mix']}")
NOTE: the argument mute=["bass"] works, but it saves as {song_name}_no bass
results[mix] renders an error
KeyError Traceback (most recent call last)
Cell In[11], [line 4](vscode-notebook-cell:?execution_count=11&line=4)
1 ## BASS BACKING TRACK, MAN IN THE BOX
2
3 results = ds.extract_stems(AUDIO_FILE_12, mute=["bass"], verbose=True)
----> [4](vscode-notebook-cell:?execution_count=11&line=4) print(f"Bassless track: {results['mix']}")
- Dominant language
- Python
- Stars
- 61
- Forks
- 5
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DrumScript/DrumScript
-
feature
Difficulty 1/5 Under an hour Newbie friendliness 86/100
DrumScript/DrumScript#357 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
DrumScript/DrumScript#354 ·
-
documentation feature good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
DrumScript/DrumScript#346 ·
-
documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
DrumScript/DrumScript#318 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
DrumScript/DrumScript#349 ·
All issues in DrumScript/DrumScript
Similar issues
-
kind/bug priority/medium qa_automation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37324 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 87/100
btclib-org/btclib-node#2260 ·
Maintainers usually reply within 1 day
-
ChatBedrockConverse changes the keys of JSON tool results to camelCase (`order_id` becomes `orderId`)Possibly taken @geyazheng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
langchain-ai/langchain-aws#1469 ·
Maintainers usually reply within 1 day
-
GCToggler leaves collection enabled if the body re-enables itPossibly taken @Gambit-Checkmate claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 7 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day