Apologies for the repetition from my previous posts but here’s the list of changes for this update:
New: Chromatic (diatonic) chords and other templates. These are inside the Building Blocks folder in your chord browser.
New: LA Vibes Pack. This is a new pack with funky chords and shimmering analog synths inspired by the West Coast vibe and artists like Tyler, the Creator.
Improved: Hovering chord previews in The Lab now shows the chord names
Improved: Windows oscilloscope no longer shows artifacts when no sound is playing
Improved: Dropping MIDI into The Lab / Chord Sampler now extracts the chords correctly
Improved: Cleaned up various popup windows
New: FLAC Files can now be dropped into The Lab / Chord Sampler
New: Create your own Multikeys instruments. Read more about Multikeys here.
( Quick note if you want to test out making your Multikeys, make sure your samples area already tuned to C before you drop them in.)
Fixed: clicks in sampler when in monopoly voice mode (finger pointing down icon)
“Daw Edit Mode” added to Note Settings
When ON: black keys activate transformers while held/sustained for people who prefer to draw in their MIDI.
When OFF: tap the black keys to turn on transformers for people who prefer to play live on their keyboard.
Chord mode ON/OFF is no longer shared across multiple instances of Notes
You can now easily drag MIDI chords out of The Lab into your DAW
When you add chords from The Lab, the chords now use the session key
When you open and close the interface, your chords in The Lab stay in place
When you drop MIDI into the Chord Sampler, it now adds the chords from the MIDI file
Please check it out and let us know if you run into any bugs
Hello! Finally giving a go to the Windows version of the beta
I don’t know if it’s a bug or something I didn’t get, but from the beginning I have encountered an issue with Notes, still there in the last version.
Let’s say I load the preset “PC Police” on Notes, in Reaper 7 / Windows 11. I don’t understand how the synth engine chooses whether it’s the Instrument A (blue) or B (yellow) which is supposed to play the notes. How does it work?
I see the chord function displaying those colours whenever I hold a note with my MIDI controller (EE Osmose in classic keyboard mode, without the MPE enabled). In general I see the note I play in orange, and then I see some blue notes being triggered (for example strummed). But here is the main problem here: whatever I do, I can never ever hear the engine A (blue)! The mix control at max in the A position just silences any sound from being played. I set the volume at maximum, I even see the envelope for the engine A being triggered. But I can’t find any way to hear any sound from there.
It doesn’t do that for all the presets, some of them don’t have the problem, others have them. And if I try to change the instrument for A, the audition mode allows me to hear the samples.
Ok, so what you’re saying is that Engine A is making no sound?
The colours that you see on the keyboard chord section are not meant to represent the engines. Now that you mentioned it, there could be some mix up as they are in the same colour more or less.
I see, there is no link between the colours and the engines, I was a bit confused about it, I guess all the confusion would have been lifted with the manual but yes, it might be a good idea not to have the same colour for the chords and strummed notes than for engines A and B
So if I load the preset PC police, I can’t find any way to hear anything from engine A, ever. I have the mix control at A at 100%, I removed all the FXs, all the volumes are at maximum etc. With a fresh start preset or some other presets, I can hear A though, even if I select the very same Instrument preset from PC police engine A.
LA vibes is a lovely addition - soulful, crushed chords. I also wanted to congratulate you on you on the pace and quality of development - oustanding job, team.
Onto a bunch of testing - sorry I’m late to the party.
“Widest Bass” (and some other presets) have macro values that suddenly jump when I load the preset and click Macro A or B to move it a little, and it ends up changing values drastically. Seems related to an earlier issue I reported where clicking on some values jump to 50% or another.
@Gavin_FAW@JuliaFeature Request: As I have been testing the Notes plugin, one thing I wish Notes had were Dice buttons on all the different parameters (presets, instruments, effects, etc.) to randomize the parameter individually, as well as a Global Dice button to randomize the whole plugin. However, also accompanied by Lock Pad buttons for locking the parameters a user wishes to remain unchanged.
This makes for all sorts of fun and happy accidents.
@iamheroTV yes, we totally need to add randomise. One thing was if we made it smart, so if you have a patch that has a keys tagged instrument….it swaps it with another keys tagged instrument, that way it keeps the sound in the same area more or less and randomise gives you something close, but switched up?
@Gavin_FAW I like the smart tagging approach? Were you thinking of making the FX randomization smart too, to where it provides variations of the same effect or would randomize populate completely different FX modules? From a sound design perspective, I could see a use for both angles.
macOS Beta 4 Installer
Quick note if you want to test out making your Multikeys, make sure your samples area already tuned to C before you drop them in.)
Feature Request: As I have been testing the Notes plugin, one thing I wish Notes had were Dice buttons on all the different parameters (presets, instruments, effects, etc.) to randomize the parameter individually, as well as a Global Dice button to randomize the whole plugin. However, also accompanied by Lock Pad buttons for locking the parameters a user wishes to remain unchanged.
