#7

introduced a small update (v0.1.2) to make things a little more responsive.

@mattlowery can you explain this a little more? i don’t do any modular and crow itself is still mysterious to me. do you mean to listen to the two crow inputs and set the play position based on one of the crow voltages (“sweeping the buffer”?) as well as starting/stopping playing based on the other crow voltage changes? i’m really happy to try implementing it just need more of an idea what i’m doing :slight_smile:

2 Likes
#8

That sample…is that you, Lubomyr Melnyk?

2 Likes
#9

i love this. quick idea to help with sample cutting… maybe holding k3 in sample mode could loop?

3 Likes
#10

@hghrlearning done. its in updated v0.1.3.

@Cloud :slight_smile: i didn’t know Lubomyr Melnyk but I do now, thanks for sharing that. the sample is actually me playing around with philip glass etude 17.

3 Likes
#11

I think if input one chose the position of the playback head, and input 2 engaged playback upon receiving a gate, it would be super cool!

But also it’s already super cool! Congrats!

4 Likes
#12

I’d love to see this implemented too. Would be a whole heap of fun and also free up my 301 for some other duties.

2 Likes
#14

Hi. This script looks awesome, but I’m getting an error init when trying to launch it, from both the norns and maiden. Is there something I’m missing ? Thanks

1 Like
#15

Are you on the latest norns update? I believe this requires some changes that were made in the October release.

1 Like
#16

Given that there’s 26 alphabetically named slots, are there plans to integrate keyboard control of sample playback?

3 Likes
#17

Ohhh. Maybe that’s the thing. I’ll update then

1 Like
#18

@PerVildman I was had the same problem. New version of the firmware have to solve it

1 Like
#20

Now the script loads, but I can’t load a sample! I’m getting this in maiden:
lua: /home/we/norns/lua/core/screen.lua:215: bad argument #1 to ‘screen_text_extents’ (string expected, got nil)
stack traceback:
[C]: in field ‘screen_text_extents’
/home/we/norns/lua/core/screen.lua:215: in field ‘screen_text_right’
/home/we/norns/lua/core/screen.lua:158: in function ‘core/screen.text_right’
/home/we/norns/lua/core/menu/params.lua:406: in function ‘core/menu/params.redraw’
/home/we/norns/lua/core/menu/params.lua:567: in field ‘event’
/home/we/norns/lua/core/metro.lua:169: in function </home/we/norns/lua/core/metro.lua:166>

1 Like
#21

This looks amazing but when I go in parameters and choose “save/load” it just hangs the whole parameters section. In Matron I see an endless stream of this sort of thing:

stack traceback:
[C]: in field 'screen_text_extents'
/home/we/norns/lua/core/screen.lua:215: in field 'screen_text_right'
/home/we/norns/lua/core/screen.lua:158: in function 'core/screen.text_right'
/home/we/norns/lua/core/menu/params.lua:406: in function 'core/menu/params.redraw'
/home/we/norns/lua/core/menu/params.lua:293: in function 'core/menu/params.enc'
/home/we/norns/lua/core/menu.lua:112: in function 'core/encoders.callback'
/home/we/norns/lua/core/encoders.lua:60: in function 'core/encoders.process'
lua: /home/we/norns/lua/core/screen.lua:215: bad argument #1 to 'screen_text_extents' (string expected, got nil)

I’m using a DIY norns shield and the latest update

2 Likes
#22

@Cementimental @PerVildman i believe this error occurs when there are no files available to load so it has trouble being displayed. however, when you start abacus for the first time it automatically copies one file to a directory (~/dust/data/abacus) that can be loaded, so that should be able to prevent the error (i thought anyways).

if you can, try deleting and reinstalling this way:

rm -rf /home/we/dust/data/abacus && rm -rf /home/we/dust/code/abacus
git clone https://github.com/schollz/abacus /home/we/dust/code/abacus

and then run.

later today/thisweek i will fix my lazy initialization with something that is more robust. sorry about that!

@cosmicsoundexplorer @mattlowery i feel more confident about the crow support with that explanation! one clarification: which of the following two scenarios do you envision for crow?

  • input 1 sets position along entire sample. input 2 gates (gate on = starts playing at position and continue playing until end of entire sample)
  • input 1 sets id of spliced sample (e.g. of the currently spliced ones, labeled A-Z). input 2 gate turns on/off playback of that sample (gate on = continous looping of current sample).
2 Likes
#23

Hell yeeeeah! Looks promising! :smiley: :clap:

1 Like
#24

Both options have their benefits.

An option for entire sample OR splice id would be amazing.
Kinda like a free run or lock to splice but this would mean only one gate option so Im thinking gate on = starts playing at position and continue playing until end of entire sample.

If only one is possible then I may lean more towards splice id and loop.

@mattlowery What did you have in mind?

1 Like
#25

i can easily do both options :slight_smile:

1 Like
#26

@cosmicsoundexplorer @mattlowery added crow support!

the parameters for modding it are in global parameters. lmk if it doesn’t make sense, or especially if it doesn’t work. i tested it out by running the functions through maiden because i don’t have crow, but i think it should work!

2 Likes
#27

I think it would be freakin awesome to have all the ABCDEF… samples on the grid : O

1 Like
#28

I think it would be unfair for me to submit an opinion yet- I haven’t had time to try this app out. But I will soon, and will certainly let you know my thoughts!

1 Like