I was moving notes up and down with the mouse, outside of the initially visible range and back in. Sometimes they don’t end up fully aligned with the grid, but usually they snap back in after moving again. It’s not really an issue.
I took a closer look at it now (with zoom) :
The notes move in a smaller grid resolution than the overlay, so when you drag a note outside of the initial view, the notes begin to move in small steps, and the overlay only moves when it snaps to the next note line.
Since the other notes move to the opposite direction in those small steps they end up misaligned if the moved note ends up where they are between two steps.
maybe you can snap all notes to grid again if the overlay has moved?
Will take a close look. Did put in a non-trivial amount of effort to make the dragging look right, so it would be nice to fix any bugs here, even if minor.
You made it so !
Bravo 
and thanks.
Many bugs are fixed in 1.0.5, but this one about dragging notes vertically and the drawing being off a bit - that one is still not fixed.
2 Likes
Our new release is all about adding features to our existing module. Seq++ has major new features: step-time recording from music keyboard, MIDI file load and save, and the ability for the user to completely re-map the key command. Saws gets a stereo output. Modular mixers get polyphonic inputs and multi-solo is back.
Here’s the complete change log for 1.0.5:
1.0.5
Seq++ has MIDI file input.
Seq++ has a step recorder.
Inputs on ExFor and Form mixers are now polyphonic.
Modular mixers now support multi-solo by control-clicking on the solo buttons.
Saws now has stereo outputs.
Seq++ bugs fixed:
Articulation setting of 100% was acting like 85%.
Notes were getting dropped when played with coarse clock.
Dragging durations with the mouse were making zero length notes.
Notes that start in the previous two bars are now drawn
Notes re-triggering seemingly randomly when there are plenty of voices
Inserting notes wasn’t scrolling the the next bar when it should have
Sometimes the purple track end marker wasn’t drawing (depending on grid settings).
Stuck notes when stopping seq in the middle and then editing.
Fixed bugs in Polygate that were causing stuck notes when CV inputs changed with gate high
Seq++ image in the module browser new looks correct, rather than a black blob.
19 Likes
done
2 Likes
Woo hoo, great news all around! Thank you so much! 
You are most welcome.
Noticed that the release notes say Seq++ can read MIDI files, but don’t mention writing them. Well, that’s just bad writing - you can read and write MIDI files.
4 Likes
Proper
1 Like
Cool Breeze
1 Like
The 1.0.6 version of our modules brings a major new feature to Seq++: xforms. These destructive edit operations allow creative possibilities like moving note pitches while keeping them in the scale, adding trills and arpeggios, inverting melodies, and more. All with full undo/redo as always. And of course there are plenty of bug fixes.
2 Likes
Here’s an example of the chop notes xform. We start with two whole notes of E.
Then we invoke the xform and enter some paramters:
When we click OK, we end up with a triplet trill from E to F#.
9 Likes
Here’s the full changelog:
1.0.6
Seq++ new feature - “xforms”.
Enhanced FAQ for Seq++.
Seq++ bug fix: Subrange loop now saved with patch. [GitHub issue]
Seq++ bug fix: Tab key frequently doesn’t work in note grid. [GitHub issue]
Seq++ bug fix: Midi File I/O shifts pitch by an octave. [GitHub issue]
Mixer bug fix: Typo in manual. [GitHub issue]
EV3 bug fix: Tooltip for waveforms comes up in wrong place. [GitHub issue]
Seq++ bug fix: Can’t reliably change snap to grid settings from context menu. [GitHub issue]
4 Likes
Proper
When we announced the new update to Seq++ we forgot to highlight some of the cool features. To the extent that current users didn’t even notice these new options after the update.
The newest features all come under the heading of “xforms”. They do offline/permanent processing of the selected notes in your sequence.
The names of the xforms are “Transpose”, “Invert”, “Reverse Pitch”, “Chop Notes”, “Quantize Pitch”, and “Make triads”.
Most of them have an option to be “scale aware” so that notes starting out “in key” remain there. This opens up creative tricks. Even the lowly transpose is more interesting – for example, in the key of E minor, transposing a B minor chord up by a step will give a C major chord!
Invert is the old staple that flips the pitches top for bottom, but again the ability to stay in a scale expands to possibilities out of the 12 tone row style.
Reverse pitch reverses the order of all the selected pitches, while keeping the start time and duration unchanged.
Both invert and reverse pitch can easily make nice melodic variations without messing up the rhythm.
Chop notes can do all sorts of things, primarily “ratcheting”, generating triplets, trills, and arpeggios.
Make triads lets you specify the root notes, and it builds up the scale appropriate triads. Some modes will generate chords in all the standard inversions.
The example in the screen capture is the result of using “make triads” on the sequence C, D, E. Key set to C major, and inversion set to first inversion. Note that the C is a major chord, and the D and E are minor, as you would expect.
12 Likes
btw, for anyone how can’t wait, our sequencer “Seq++” has extensive keyboard control. You can even re-map all they keys. It is, however, more like a midi piano roll editor than a tracker. here’s the section of the manual on the keyboard commands: https://github.com/squinkylabs/SquinkyVCV/blob/master/docs/sq2.md#Keyboard-reference
5 Likes
so, continuing from another thread, Seq++ and 4x4 will get more of my time. First opinion: underrated, these very usable modules, but need some improvements, also I have to adjust my own workflow.
Two things at first glance (edit: coming from FL studio, I’m spoiled)
-
Seq++ needs a “zoom out” function. You can zoom the plugin nearly to fullscreen via VCV’s zoom, so there’s much room for more than two bars, makes sense for me to have a bird’s-eye view of the whole pattern.
-
The settings for clock-rate and polyphony should be hidden in the context-menu, this would save valuable screen space, e.g. for more often used editing functions or options or so
2 Likes
Good points. Thanks for the message!