Piece for 2024 ICSC

[gogins]

I actually will prepare the following pieces in parallel and submit the best:

• [x] cloud-5 always-on piece.
• [x] Visual music.
• [x] Fixed medium.
• [x] Right now I am going with an anonymized version of http://localhost:8000/cloud5-example-visual-music.html.
• [x] Add key bindings for controlling the composition parameters in fullscreen mode.
• [x] Add a key binding for a coarser level of control (metaKey, seems to be the Apple key).
• [x] Make the canvas what goes to full frame, not the body.
• [x] Button to record and download recording.
• [x] Fixed length in the .csd file, with fade in and fade out.

Finishing the piece:

• [x] Get the controls for the piece running on the laptop screen while the visual music itself runs on the projected screen.
• [ ] Sync the controls on the two screens, or hide the controls on the laptop screen.
• [ ] Make certain that the fullscreen on the projected screen always works (permissions), see https://developer.mozilla.org/en-US/docs/Web/API/Window_Management_API#examples.
• [x] Make certain that the controls window is always cleaned up.
• [ ] Add a control for number of canons (up to 3 in addition to the original).

Things I need to do before the conference:

• [ ] Fix up the paper (camera-ready submission due August 1st).
• [ ] See if I can attend and present via Zoom.
• [ ] If not, see if I can get Nathan to help Heidi milk.
• [ ] Register for the conference (deadline July 7th).
• [ ] Book a flight (roughly $500 with stops to $1,000 nonstop round trip).
• [ ] Book a hotel (roughly $150 to $200 per night with breakfast).

[gogins]

For cloud-5 type pieces, add a button to start/stop recording to file with fade in/fade out. Victor has a tutorial that shows how to upload and download files that Csound can read or has written here.

[gogins]

Create key bindings for the following inputs:

cloud5_piece.menu_slider_addon(Composition, "NoteTempo", 0, 200);
cloud5_piece.menu_slider_addon(Composition, "NoteDensity", 5, 200);
cloud5_piece.menu_slider_addon(Composition, "NoteDurationFactor", 0., 5.);
cloud5_piece.menu_slider_addon(Composition, "GraphicsTempo", .0, .25);
cloud5_piece.menu_slider_addon(Composition, "GraphicsHue", 0., 1.);
cloud5_piece.menu_slider_addon(Composition, "GraphicsValue", 0., 1.);

Key bindings will be as mnemonic as possible and use [Ctrl][Alt] with [Shift] for decrease and no shift for increase:

n NoteTempo
d NoteDensity
f NoteDurationFactor
g GraphicsTempo
h GraphicsHue
v GraphicsValue

The handler will increment (no [Shift]) or decrement [Shift] the parameter value in steps of size range/100; minimum and maximum values will simply peg.

[gogins]

I wasted time getting the fade in and fade out to work because turnoff2 turned off the master output without releasing its cossegr envelope. Changing that to linsegr works.

[gogins]

Submitted the piece, 2024-ICSC.html here at commit 03e599266139bb18baa9ec18d1580ed5c7a1ff1f.

[gogins]

Perhaps not done here. Control the piece from my phone or from a dedicated MIDI controller.

[gogins]

Possibly usable sensors on the phone:

1. TYPE_GRAVITY, force of gravity relative to X, Y, Z.
2. TYPE_ROTATION_VECTOR.
3. But see https://developer.android.com/develop/sensors-and-location/sensors/sensors_position#sensors-pos-orient, how to compute rotations in radians of device relative to magnetic north.

Note: X is left to right, Y is bottom to top, Z is back to front.

[gogins]

The Csound for Android app claims to have the OSC opcodes. I could design a custom GUI and send control parameters from a piece running on my phone through OSC to the actual piece running on my MacBook. I will try this.

[gogins]

There are Android apps for OSC including OSC Controller, TouchOSC, and Sensors2.OSC.

I will test with OSC Controller and if things work, will switch to TouchOSC.

[gogins]

The receiver is controlling data in the JavaScript context so needs to be JavaScript, see https://github.com/colinbdclark/osc.js/. This looks good, but there are hoops to be jumped through. Maybe MIDI would be better.

[gogins]

CsoundAudioNode doesn't implement OSCinit. I must use either MIDI, or OSC on NW.js.

[gogins]

The Midi Studio on the MacBook does not recognize the MIDI Commander app.

[gogins]

Maybe I can use WebMIDI directly to do this job. See https://webmidijs.org/.

[gogins]

I believe I can use requestFullScreen with options to select the screen. That would be far the best if it works for me, so that is what I will try first. Supposedly works with current Chrome.

I should then also add a parameter to select which screen.

[gogins]

Partly there with opening a separate browser window with HTML controls on the secondary screen. Now to get it talking.

[gogins]

Apparently in the HTMLControls window, window.opener contains a live reference to the window for the piece, so I should be able to run the controls without using postMessage, just assigning new values to the piece parameters members.

That works.

[gogins]

The thing is basically working, but the two sets of controls should mirror each other somehow.