mcascone / boomerang-plugin Goto Github PK

Somewhat related to #8

Sometimes it can be annoying to have to hold STACK down if you're playing a long overdub.

This feature enables a mode in which STACK is a toggle instead of a momentary.

Update: this is actually a programmable mode of the Boomerang+ version:

stack dim: momentary (press & hold to add parts)
stack bright: latching (tap on / tap off).

Implement a Panic or Reset button to stop all playback and clear everything. Maybe just call it a Clear button.

One of the versions of the Boomerang had an A/B mode. I think that's the one I had? I remember it being fairly clunky to use. Regardless, it's a legacy feature that I'll want to implement.

The manual provides these details on the A/B functionality:

A/B - ONCE

This button can be programmed to be in one of 3 modes: Once, A/B or A/B1. Out of the box this button is set to the Once function.

A/B

Selecting this mode provides you with two loops, say for a verse and a chorus. We call the main loop “A”, and “B” is the secondary loop.

Please Note: The two loops are different. Whenever A is recorded, B is deleted. The reverse is not true. B can be recorded and re-recorded without affecting A.

Once they are both recorded you can go back and forth between them, stack additional parts, play, stop, play in reverse and generally freak out anyway that pleases you, but remember... when you record A you replace what was in A and B is deleted.

While recording A, A/B concludes recording of A and immediately starts recording B, and loop ‘b’ turns on. While recording B, A/B concludes recording of B and immediately starts playback of A, and loop ‘b’ turns off.

If both loops have been recorded, then A/B behaves like this: With loop A playing, A/B causes loop ‘b’ to blink; at the end of loop A, a smooth transition to B will occur, and loop ‘b’ turns on solidly. If loop B is playing, A/B causes loop ‘b’ to blink; at the end of loop B, a smooth transition to A will occur, and loop ‘b’ turns off. If no loop is playing, A/B chooses which loop to work with. A is selected if loop ‘b’ is off; B is selected if loop ‘b’ is on.

A/B1

This mode is the same as A/B with one exception. With loop A playing, A/B causes loop B to play once and then return to loop A.

Discussed in #11

the original audio fades properly, but new audio isn't added.

Add a feature to sync the loop length to a MIDI clock, like the DAW tempo.

Not sure how this would actually work, but the math is probably a solved problem elsewhere.

The OEM looper code already has a sync feature, so it shouldn't be hard to add it.

from https://www.reddit.com/r/paintaudiomidicaptain/comments/1dyyif6/is_there_any_way_to_make_it_do_a_midi_clock/

If the Boomerang Phrase Sampler is idle, pressing ONCE will playback your recorded loop one time. After pressing this button, the ONCE LED will be turned on letting you know this is the last time through your loop.

Might need the custom GUI, KUIML.

From the manual:

If DIRECTION is pressed so reverse is on before recording begins, a special continuous-reverse mode will be entered where the RangTM sampler is continually recording new sounds while simultaneously playing the previously recorded sounds in reverse. This is the way to play a reverse lead live on stage. While jamming, press RECORD twice to define a phrase length. Both record and play will be brightly lit, along with reverse, to denote this unique mode.

Pressing PLAY/STOP should stop recording and go to idle, but it doesn't.

If the Rang is recording, pressing PLAY/STOP halts the recording and the unit becomes idle; your music is recorded and ready for playback.

Thru Mute intermittently unmutes and then immediately remutes.

I think this might qualify as a dropout? Which are also happening.

Update: When running the plugin as a true Plugin, that is, exported as an AU/VST, the dropouts seem to be resolved. It could just be that the performance of the non-exported app is buggy or choppy. I will continue to test if this is true.

From the docs:

It is also possible (and strongly recommended) to add a user manual to the dsp script. It will be made available to the end user in the title bar, with an additional question mark icon (see the chapter about user interface for more details).

Both pdf and html manuals are supported for scripts loaded into Plug'n Script (whereas only pdf is supported for exported plug- ins).

Simply distribute the script with an html or pdf file in the same directory as the script, with the appropriate naming convention:the manual should have the same name as the script file, with the .html or .pdf extension. For example: myscript.cxx and myscript.pdf.

If no manual is provided, the help icon will not be visible in Plug'n Script or in the exported plug- in. Note: exported plug- ins currently support pdf manuals only.

Build the UI to look just like the physical device. This will be a project/Milestone.

Theoretically should improve performance. Tech Debt.

p.34 in the manual