andyshand / modwig Goto Github PK

Fix ASAP to prevent problems further down the line

We lose track of the process ID for Bitwig and for some reason it isn't updated, even tho we attempt to account for this.

Move personal mods out of the repo, and better categorise, name and describe existing mods. Adding settings for things that should be customisable

Stops plugin-window related functions from working

An event with Meta, Control, Alt and Shift will come through to JS land with all the flags set to false.

Perhaps something to do with freeing already freed memory with NAPI Function references

Some mods aren't helpful in their current state without customisation of the code by the user. It would make things easier for non-devs if mod-specific settings could be changed via the UI.

Would be a good candidate to be completed along-side #19 Mod-specific settings, where users can customise colors for specific tracks. Perhaps something simple like a regex to enter for each track set and a color choice using the BW colour palette?

Partially complete (see "Built-in" tab of settings view). A user may want to simply remap some built-in Bitwig actions so that they may be triggered while VSTs are open, or while other panels are focused which usually block an action from working.

A bunch of built-in mods currently do not account for when the inspector panel isn't open. We should detect when this is the case and ensure it's open, or open it in a similar fashion to how we currently open the device view.

Shown in asm code when calling CFRunLoopAddSource, not sure the best way to work around this. Seems to be responsible for crashes on startup.

For some reason this doesn't occur at all during development.

https://stackoverflow.com/questions/56008262/why-is-my-app-really-slow-to-start-when-i-authorized-it-to-control-my-system

See above link for possible explanation. Apps must be signed even with a self-signed certificate, or it will perform some kind of scan on the app which is what slows things down.

Removing the call to AXIsProcessTrustedWithOptions speeds things back up again, which seems to explain that the scan happens only when checking if the process is trusted. Unfortunately, we need this for accessibility access.

Reduces need to write our own code for listening for events across OSs

Something like this:

Arranger clips have names visible which makes scanning easy, but group tracks require you to look to the left side of the screen all the time to figure out what the content is.

Would just require grabbing the image portion of track name from latest screenshot and repeating it across the x axis.

Potential implementation:

• Share memory across main and render Electron process
• Pass screenshot data as Napi::Buffer to renderer process (ensuring kept alive as long as not GC'd)
• Pass the track location data to renderer process, and use it to map each image to its track

Any improvements on the idea welcome.

Probs doesn't make sense to do until functionality is more stabilized