Colugo is a Renoise tool designed to enhance your music production workflow. It automates the process of creating samples from YouTube videos based on specified keywords, allowing you to specify the number of samples, their length, and more, to streamline your creative process in Renoise.
Cool tool idea.I tried it but nothing happens. I have ffmpeg both python 3.11 installed on my win10 machine. I do have yt-dlp but i don’t know if that’s really installed opposed to being a “portable” app. I use it all the time from window’s command prompt.
It hangs here and eventually when I hit stop sampling it mentions the script has stopped.
Thanks for getting back to me, much appreciated. I got it to work. TL:DR: It seems it doesn’t like spaces in the output path
When I ran your suggested code in the Renoise Tools folder it downloaded 1 wav file. But from inside of Renoise it was still no joy.
Words saved and Output path set.
usage: yt-downloader.py [-h] [–num_videos NUM_VIDEOS]
[–sample_length SAMPLE_LENGTH]
output_dir
Nothing happened after that. Changing the output path from F:\Samples\Random Youtube Samples to C:\Users\Vincent\Desktop\RandomSounds fixed it. After some further testing it appears the tool does not like spaces in its output folder. Once those were removed it worked, thanks!!
digging in.
well, the 100 max limit is now introduced. thanks!
for some reason, still doesn’t actually start doing anything re: saving files to my ytube folder.
and if i run the python3 yt-downloader.py – i’ll be getting files without issues.
is there some way of running this within Renoise’s Scripting Editor & Terminal, to see what Renoise is trying to output or what’s going on?
ok you’re not going to believe this. I started it from the Terminal macOS and the tool just works. no issues on Scripting Terminal & Editor - i’m seeing the console inside your tool working and doing it’s job.
I wonder what’s the difference between running Renoise from the Terminal and starting Renoise from /Applications.
how do you want that to work? All samples into a single instrument or each sample as an instrument? I could implement both - which one are you looking for first?
me personally i’d go for each sample into one instrument. so you see it being populated, can quickly edit + cut+crop and delete stuff that makes no sense.
Great idea! Could be a game changer for me but I can’t seem to get it to work. I am on Mac. I downloaded the file and installed it but when start sampling nothing happens, the button turns to “stop sampling” but that is all? Could you give me some directions?
Checking this out immediately. Awesome work!
