Zynewave's Forum Page

Beta5 is up. I delayed the release because I found a flaw in the plugin import, while trying a demo of the Rocket sidechain compressor. I ended up doing an overall revision of the plugin import and the Create New Project page. I would appreciate if some of you could try to create a new project and import your plugins with beta5, and see if your plugins are still imported correctly. I’d also appreciate comments on the new plugin naming convention. The list of changes in beta5 are:

Imported plugins now use the plugin filename instead of the VST reported plugin name, if the plugin name is identical to the first part of the filename. This makes it easier to distinguish the mappings for a plugin that has multiple dll files for different output configurations, such as some Native Instruments plugins.

Importing effect plugins that support 3 or 4 inputs and stereo output will now by default be configured as sidechainable effects.

Right-clicking a global device in the inspector device list will show the “New Instance” command. This command was previously only available in the device list on the project start page.

Made some layout changes to the Create New Project page.

Simplified the naming convention for device mappings that are generated by creating a new project or by importing plugins.

Creating a new project will now create default MIDI mappings for any enabled MIDI outputs. Previously you had to use the “import hardware definition” command from the devices menu.

Creating a new project will set up additional mono mappings for the busses.

Using any of the import plugin commands will only create surround mappings for the plugin if there already are other surround mappings in the project.

Renaming a folder containing device mappings will popup a messagebox asking whether device mappings that share the name of the folder also should be renamed.

Fix: Some VST plugins that reported multi-channel support would not be imported correctly as stereo effects.

@Malcolm Jacobson wrote:

One thing I’ve noticed is that the editor has an “Undo Timing Adjustments” option after you’ve applied the timing, but no option to Redo. Is it possible to implement Redo so we can listen to before and after in the editor window?

You can undo (ctrl+z) the “undo timing adjustments” command. I tried different names for the command to avoid associating it with the normal undo history. I tried “revert timing adjustments” and “discard timing adjustments”, but “undo timing adjustments” I think is still the simplest description for it. Let me know if you have other suggestions.

@Malcolm Jacobson wrote:

Found one bug with beta 3 – each time I open my test project the Time Signature of the Metronome is reset to 4/16, even though I created and saved the project at 4/4.

Ouch 😳 That happened during some cleanup of the code, when I added the timing adjustment info to the events.

I’ve removed the beta3 download link, until I fix this. Please don’t save your projects with beta3.

Many thanks for reporting this bug.

@Lion wrote:

@Zynewave wrote:

• Fix: Adding child tracks to a group track that had a plugin instrument assigned would wrongly create the child track as an audio track.

Does that mean comping works for MIDI as well? Cause if so I LOVE you. 😆

Sorry. MIDI comping is not implemented, yet. I’ll get to it eventually.

Beta3 is up.

Unless bugs are reported, this is the last beta before I release 2.27 in a day or two. I need to write the help page for the adjust timing dialog, while I still remember what all the settings do 😉

The changelog so far reads:

• Added “Adjust Timing…” command to the edit menu. This opens a dialog with advanced quantization options. There are controls for setting grid, quantize mode, strength of start/length quantization, min/max sensitivity, randomization and swing.

• Timing adjustments on each event are now saved in the project. This allows you to at any time undo adjustments or redo timing adjustments based on the original recorded timing with the “calculate adjustments from original timing” option in the adjust timing dialog.

• When events have been modified with the “quantize” or “adjust timing” commands, the edit menu shows two additional commands: “undo timing adjustments” and “commit timing adjustments”. The commit command allows you to do iterative timing adjustments.

• Fix: Adding child tracks to a group track that had a plugin instrument assigned would wrongly create the child track as an audio track.

The extract groove feature I mentioned earlier in this topic will come at a later time.

Note that the .pod file format is not yet updated to save the undoable timing adjustments, but with this beta you can at least try out the commands and see if they work as you expect.