#33

ah!
i missed that there was an update!
:stuck_out_tongue:
updating right now before tonight’s session.

thanks for the info on the sample size!

#34

v1.1.0 is up now on github/maiden. This version implements preset loading and saving, see https://github.com/lylepmills/buoys/blob/main/README.md#meta-mode for more details.

load_preset_ss

8 Likes
#35

Let the buoys be buoys!

#36

i gotta update a lot of samples…
i keep running into the warning.
:stuck_out_tongue:
DARIUS-warning

2 Likes
#37

wanted to thank you for this great script, got it up last night and was excited to show my wife the blinky lights even though I hadn’t figured out how to get sound out of it. eventually I got a cool jazzy drummer thing going with the 808 folder but found when I changed pylons to buoys, it muted everything. what am I missing with the buoys?

#38

@fourhoarder - I’m not entirely sure I understand what you’re describing. Here’s some thoughts which might help, but feel free to send a video if not

  • Pilings appear as circles on the norns display, buoys as a square within a square. Only buoys make sound. When a buoy is playing the inner square lights up brighter. Is that happening for you?
  • Buoys need to be triggered by the tide to start playing (see the “play threshold” setting). It’s possible that if there are pilings in front of your buoy that the tides aren’t reaching the buoy to trigger them.
  • Besides the play threshold, depending on the buoy settings there are various reasons it might not make sound. For instance if no sound is associated with the buoy, or if the zenith/nadir volume settings are low, or if the filter settings are such that most or all frequencies aren’t being heard.

Let me know if that helps!

1 Like
#39

ah ok, I think I am just getting pylons and buoys confused, I thought both made sound but that makes sense for what I am seeing. cheers!

1 Like
#40

Truly wonderful script, I lost ages to this earlier today. Also everyone in my household was fascinated, crowding round and hammering buttons or dials to see what happened.

5 Likes
#41

Are there limitations on the tapes which work with Buoys? I’m finding most of my tapes are unavailable despite conforming to 48khz/24bit. Length doesn’t seem to be the variable here, but I didn’t explore the issue deep enough to say for certain.

Tried Crow outputs for the first time today and found them so useful!

1 Like
#42

When you are in the menu to select a sample folder, and you select a specific sample in that folder/directory, it actually doesn’t matter which sample you pick - buoys will try to load that whole folder in (I think) alphabetical order. This is probably a bit non-intuitive but it’s a shortcut I took in order to be able to use a particular helper library for navigating the file structure (I will very likely try to improve this experience in future versions). The total sample length that can be loaded into buoys is currently ~349 seconds. So I suspect what is happening is when you try to load a particular tape file, the other tape files that came before it alphabetically in that directory are filling up the available space in the audio buffer. If that doesn’t jibe with what you’re seeing, please let me know.

Sorry for the suboptimal experience. Until I find a more elegant in-app approach, a solution would be to connect to the norns filesystem (https://monome.org/docs/norns/fileshare/) and create a new folder in the audio directory, and just move the tapes you’d like to use with buoys into their own folder. If you don’t want to move the existing files, you could also create aliases/symlinks and just put those into their own folder.

2 Likes
#43

Hi all - I recorded a series of six video walkthroughs totaling about 45 minutes, for the interested (also now linked in the first post). They cover a lot of the same ground as the README but with real audio examples, as well as a few new topics.

I apologize for any A/V issues, I’m a beginner when it comes to making videos. Enjoy!

11 Likes
#44

what if there was a folderselect param ??

#45

Thanks for these! Really helpful.

1 Like
#46

Thanks, this makes sense. I’m loading from my root tape directory, so I’m certainly exceeding 349 seconds. I’ll try making a folder specific to the project and see if that helps.

#47

thank you so much for this script! i’ve really enjoyed watching all the tutorial videos this morning and playing with the 606 samples. i’ve tried to load my own folder of buoy samples, but no matter what i try i keep getting the warning about non-48k files. i read the comments above about total length and i’m way way under that. wondering if you can clarify how i should prepare my samples so they are 48k?

3 Likes
#48

Amazing! It does so much more than I initially thought. Guys, check the video manuals :slight_smile:

2 Likes
#49

you reminded me to watch these! so cool. particularly want to highlight the 4th one which really clarified for me what’s actually happening:

(amazing work lylem!)

5 Likes
#50

@andrew - not sure what exactly you’re suggesting, care to elaborate?

@instantjuggler - good question, it’s definitely not as easy as it should be to convert things to 48K. I know some DAWs have ways of doing it but they seem like kind of a pain, especially in bulk. The best tool I know of for converting sample rates is ffmpeg. The documentation isn’t the friendliest but it’s actually fairly easy to use - not sure what OS you’re on, but here’s a basic guide for Mac (I assume it would be similar for Windows, etc. but I don’t have anything else to test with)

  1. download ffmpeg
  2. put it on your path (something like mv ~/Downloads/ffmpeg /usr/local/bin in Terminal)
  3. convert your files. I just tested this out with some of the files that get preloaded with norns, e.g.
    ffmpeg -i drumilk.wav -ar 48000 converted/drumilk.wav. Note that the output path has to be different than the input path, so I had already created a converted directory. That approach is one file at a time though - here’s a super quick bash script that converts a whole directory (just replace the SAMPLE_DIRECTORY path at the top).
2 Likes
#51

I used the SoundConvertor tool on Linux - which is a gui front end for various convertors such as ffmpeg - and a version may exist in some form or other for Mac OS. Then it was simply a matter of dropping a folder of samples into the window and selecting the right sample rate and destination.

2 Likes
#52

On that subject you got me searching around a bit and I just found this one for Mac and tried it out and had a good experience: https://amvidia.com/to-audio-converter

1 Like