Was just playing with this again after a while … great stuff. And scrub mode is so cool.

Idea : quad scrub mode, where you scrub all 4 samples with the 4 arc encoders at once. Some kind of demented 4 deck minimalist DJ deck … boom!

1 Like

Rolled up my sleeves and did my first actual norns scripting. :slight_smile:

After a misstep or two I noticed encoders 2 and 3 don’t actually do anything, so I used them as proof of concept scrubbers. By default they scrub tracks 1 and 2. Hold alt to scrub 3 and 4.

I won’t do a pull request or fork just yet, as I want to keep tinkering, and do the scrubbing on the arc as planned.

For those that want it the code change is simple;

function enc(n, d)
  if n == 1 then
    params:delta(track .. "volume", d)
  end
  
  -- begin experimental quad scrubbing enhancement 
  
  if n == 2 then
    if alt then
      scrub(3, d)
    else
      scrub(1, d)
    end
  end
  
  if n == 3 then
    if alt then
      scrub(4, d)
    else
      scrub(2, d)
    end
  end  
  
  -- end experimental quad scrubbing enhancement
  
  last_enc = n
  time_last_enc = util.time()
end

There may be unexpected consequences, but seems ok so far.

2 Likes

Hmmmm… I wonder if I should just make parameter for switching between quad scrub mode and “classic” mode. I could even assign it to one of the unused encoders… turn right for classic, left for scrubs? Setting the 4 arc rings to scrub their buffers should be easy enough, I think. I need to look at the script again :sweat_smile:

Edit: @ether, I had completely forgotten about this, but a while back I wrote a Gist/mod of Angl called HC-ft (human controlled file transport lol). This might be of interest to you :slight_smile:

7 Likes

FYI I’m continuing to tinker with this, and have now experimented with adding grid support for more control, to good effect.

I’m thinking through ui ideas, and will probably fork this off into a new scene, tentatively to be called tangl.

5 Likes

Does this one support four stereo tracks, or are they mono?

Maybe @artfwo can clarify, as Mangl uses the glut engine, but looking at the engine code makes me think the current version is mono. Specifically this line/comment…
// TODO: load stereo files and duplicate GrainBuf for stereo granulation

1 Like

Correct, only left channel is loaded from the audio files right now.

1 Like

I just built a fates and I’m trying to get my DIY Arc working with this script, any tips and tricks?

What are you current symptoms?

After a reboot everything works fine, false alarm :laughing:

1 Like

ran into an issue tonight…
(running latest norns OS and MANGLE)

was running MANGL with no problem at first.
wanted to run into a second norns running COMPASS.
the norns running COMPASS for some reason would not see the ARC.

so i switched the ARC from the MANGL norns and it wouldn’t see it either.

then everything went to shite…
:frowning:

now i can’t get either norns and either ARC to light up with MANGL on either of the two norns machines.
ARGH!!!

tried a RESET on both norns.
tried SLEEP.
tried hard RESET with the little button on the bottom of norns.
tried running a different script and then running MANGL.

both norns are fracked now.
(well…both are acting the same way now)
the ARCs just won’t light up when MANGL is running (or COMPASS).

it looks like both norns will see the ARC under devices but they just don’t light up or make any changes to the sound parameters.

HELP!!!

(sorry if i am sounding super frustrated…everything was working and i was getting ready to broadcast when it all just failed on me)
:dizzy_face::dizzy_face::dizzy_face:

I ran into this the other night as well – a bit of frustration is totally understandable.

the way out was essentially clearing all the devices (by selecting none in each slot) and making sure my connected device was in slot 1 for each device type. while a script could support many devices at once, they automatically default to slot 1 unless coded otherwise.

hope this helps!

2 Likes

so sorry for the, completely understandable, frustration! hopefully @dan_derks advice gets you sorted.

1 Like

i’ll try that as soon as i get home!

THANK YOU!!!

1 Like

ok…

finally got to this.

so USB port 1 is closest to AUDIO IN and USB port 4 is closest to the power LED.
(found out the hard way)

FIRST - unplugged all USB doodads.

  • plugged in the ARC on first norns and added it in the devices menu.
  • lit up!
  • started working.

on the other norns…
having unknowingly plugged into USB port 4…
same problem…however, this time i was able to:

  • unplug it and remove any instance of it in devices menu
  • plug it back in on USB port 1
  • add it back on USB port 1 of the devices menu and BING!..back to noiz.

THANK YOU SO MUCH for all the help guys!!!
again…apologies for the snark-ness and frustrated previous post.

now…
should all of this be posted in the norns help as well or at least brought to the attention for being addressed in the OS updates?
because…this happened to everything(including GRIDs and other scripts) i tried to plug in last night when it all went haywire.

i could swear that i was hot swapping GRIDs and ARCs the other night and trying out different scripts without any need for a restart or any of this Device Menu business.

1 Like

There may be a bit of a misunderstanding here. The physical USB port doesn’t matter. The slots listed in the devices menu are virtual and not tied to a physical port.

you should be able to plug Arc into any of the physical ports, and select it in slot 1 in the devices/arc menu. the only time that i have had troubles is when the same arc (or grid) was listed in two device slots. (the solution in this case was to remove all but the arc/grid in slot one in the devices menu.)

2 Likes

update v1.4

  • tracks have been increased to 7
  • grid support (via @artfwo’s wonderful glut script)
  • navigating between tracks has moved from key3 to enc3
  • key3 now sets the selected track speed to 0
7 Likes

Nice! Can you point me towards more info about the grid integration?

k3 sets speed to 0 , bug or intentional? thanks for the new update, great stuff!

1 Like

I will be updating the docs with a grid control image soon! Until then…

row 1 is track stops (buttons 1-7), pattern record buttons (buttons 9-15), and alt (button 16).
row 2 - 8 represent track buffers, row 2 is track 1etc… pressing a button in a row will jump to that position in the buffer.

recording patterns

pressing a pattern record button arms recording.
play a pattern on the track buffers portion of the grid.
press pattern record again to stop recording and begin playback of the pattern.
hold alt and press a pattern record button to clear pattern.

edit:
@swhic That is intentional, but I forgot about it :sweat_smile:

8 Likes