$ npm run build

[email protected] build /home/michael/repos/mmckegg/loop-drop-app
node build -d

** REBUILD ERROR **
module "observ" not found from "./context/index.js"
** REBUILD ERROR **
module "observ/watch" not found from "./context/index.js"
** REBUILD ERROR **
module "bopper" not found from "./context/index.js"
** REBUILD ERROR **
module "observ/watch" not found from "./views/audio-meter.js"
** REBUILD ERROR **
module "observ" not found from "./editor/index.js"
** REBUILD ERROR **
module "observ/watch" not found from "./editor/index.js"
** REBUILD ERROR **
module "observ" not found from "./loop-launchpad/index.js"
** REBUILD ERROR **
module "observ/watch" not found from "./loop-launchpad/index.js"
** REBUILD ERROR **
module "observ/watch" not found from "./loop-drop-editor/raw.js"
** REBUILD ERROR **
module "observ-grid" not found from "./loop-qwerty/index.js"
** REBUILD ERROR **
module "observ-grid/grabber" not found from "./loop-qwerty/index.js"
** REBUILD ERROR **
module "observ-grid/indexes-where-contains" not found from "./loop-qwerty/index.js"
** REBUILD ERROR **
module "observ/watch" not found from "./lib/map-watch-diff-stack.js"
** REBUILD ERROR **
module "observ/watch" not found from "./controller/grid-state-hook.js"
** REBUILD ERROR **
module "observ/watch" not found from "./params/wave-hook.js"

• loop-drop-app needs observ and bopper
• loop-qwerty needs observ-grid
• loop-drop-editor needs observ
• loop-launchpad needs observ

multiple controllers should be able to access the same midi port, but this should be managed by some kind of stack, so that only the top most controller gets control.

switching setup tabs should reorder the midi stack so that the focussed setup's controllers are connected to the midi ports

• what to add to loop-drop-app
• what to fork / copy as a starting point for custom controller implementation

Sync all clocks

Minimal server that broadcasts any received messages to all connected clients.

Ability to direct message clients. When a client learns about a new connection, direct message all current state and nickname.

Client ID is assigned by server.

Clients can set a display name

Use hash of samples as the filename so we can ensure unique files. Ideally everyone ends up with a copy of the samples and they will only be downloaded if unavailable locally. The server can cache them for a short period as well.

Request sample from server via GET. If server has sample in cache, return. Otherwise broadcast message to all clients asking who has the file. Tell one (or more) of the clients that reply to POST the file to the sample url. As soon as the file starts being received, pipe to all pending GET requests for that file.

also on stable chrome, sometimes will just crash when it all gets too much, although in canary it doesn't crash, but the lag seems to be worse.

currently all control mappings are switching between store and flatten loop modes depending on current transforms. this can be quite annoying when laying down repeating notes, and accidently just looping the one.

maybe split the two into separate functions so you always know if it is going to flatten the transforms, or loop what was just played.

will require some documentation rewriting (but it's all useless anyway so who cares)

It's a bit unwieldy having chunks all over the place for all the different setups in one list. How often do you really want the chunk to update bidirectionally?

what if the chunk library was just a repo of reusable chunks?

they show up in the external chunk editor and can be edited directly or linked

• rename
• allow link to modulator chunks

the current mercury stuff is too slow for the 60fps audio meter
move to cached element, class swapping
or use an html5 element, svg, or canvas?

Disabling the meter freed up about 20% of the frame time for scheduling audio

Prompt for creating new project, loading existing, or installing demo content

So it can be used without a midi-controller.

Not sure if it should be it's own "controller", or if all loop-grid instances should support qwerty input.

When building I get this issue I presume a module needs to be included/uploaded to npm.

** REBUILD ERROR **
module "loop-qwerty" not found from "C:\Users<username>\Documents\GitHub\loop-drop-app\midi-controllers.js"

currently doesn't clear currentDrag on dropping outside of a controller

rather than using soundbank, each device (chunk -> setup) generates it's own sounds (audio slot)

would allow for all sorts of fancy chunks (e.g. audio loopers, samplers)

caused by rincewind-precompile-transform which is incompatible with windows paths

Triggers

• record
• clear

Options

• loop length

Use DelayNode+feedback?

Move to 'setup as a directory' approach.

Remove separate chunk browser pane. Replace with a single hierarchical tree browser. Double clicking on a directory attempts to load an index.json. Hide index files from browser.

This is a major breaking change. Probably will have to bump major.

New project structure:

Project Root
  - Setup 1
     - index.json
     - chunk 1.json
     - chunk 2.json
     - sample 1.wav
     - sample 2.wav
  - Setup 2
     - index.json
     - chunk 1.json
     - chunk 2.json
     - sample 1.wav
     - sample 2.wav

on debian linux, requires libasound2-dev package, which can easily be installed with sudo aptitude install libasound2-dev.

this is for the 'global-setups' branch.

not sure what best to call it.

it's not currently obvious that chunks need to be dragged in from the sidebar. Need to figure out how to make the interface communicate this.

maybe this bundles javascript as a static gist that can be hosted to play the loop at that url.
maybe this contacts a "loop server" which hosts a page to play the loop at that url.

in the future, the "loop player" pages can have a link to open up the loop in the "loop editor".

even after removing launchpad control (or the controller completely) the launchpad continues to remain active.

• drag and drop
• browse for samples

slices target sample into slices based on chunk shape

timestretch option (uses granular)

• set tempo
• trim

play to end option

I was able to run npm install (etc fine on the master branch)

However when I tried to run npm install on the global-setups branch npm complains: No compatible version found: loop-grid@'>=3.1.0-0 <4.0.0-0'

Do you need to push the latest version of loop-grind to npm? (the current version is 3.0.0)

npm WARN package.json [email protected] repo should probably be repository.
npm WARN package.json [email protected] No README data
npm WARN package.json [email protected] No repository field.
npm ERR! notarget No compatible version found: loop-grid@'>=3.1.0-0 <4.0.0-0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["1.0.0","1.1.0","1.2.0","1.2.1","1.3.0","1.4.0","1.5.0","2.0.0","3.0.0"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install"
npm ERR! cwd C:\Users\<username>\Documents\GitHub\loop-drop-app
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! code ETARGET
npm ERR! not ok code 0

no drop unless over sample node

Instead pass project context as second argument to node creation.

Available audio-nodes can be set like controllers or chunks in an audio-nodes.js config file.

See #36 and #44

instead of just on first load

sometimes save only persists part of the file to disk, causing corruption.

example / sample code:

• http://zya.github.io/granular

allows a crude kind of timestretch, but is just a pretty cool effect in general!

Setups get a share button.

It generates a torrent and starts seeding giving the user a sharable loop drop url.

When a user accesses the url, it puts the remote setup into their own project.

The current keyboard control lets you use a 3 by 10 input grid

I you included the 1-0 keys you could get a 4 by 10 grid which would be more like a launch pad grid.

Instead of having individual spawners for each controller, maybe have just one "loop grid".

The loop grid node allows specifying sub nodes which would be the different controllers. Then they can share a lot of the render code and styling.

Maybe need to rethink the code hierarchy of controllers inheriting from loop-grid?

grab input from mic, etc

stereo pair, or single channels

by default, chunk pane is hidden

setup pane is fullscreen

• should the chunks load into the main tabbed view? rather than split
• would give a lot more room for customizing chunks
• could do a proper grid selector for the chunk editor

When spawning external chunks from chunk spawner, rename on chunk reference, instead of in file browser. Don't open it immediately.

Do the same renaming with local chunks too.

shave off 6% cpu time under heavy refresh

make available for audio scheduling