Zynewave@Pigini wrote:
But we don’t have that snapping to grid timing, without doing a duration quantize at the same time yet, or have we?
If you move events with the mouse or use the “quantize start” menu, then the duration is not quantized. If you add new notes or resize existing notes then the dragged size is quantized if snap is enabled. Isn’t that the preferred behaviour?
Zynewave@Pigini wrote:
Unless I only haven’t found it yet, it looks like we can’t even change the grid (yet). As if there was nothing but 4/4 in the world of music. We really need different grids, and then we can eventually snap to it (I mean only snapping to the time value, not doing a duration quantize at the same time, like it is now. Or is that something I have only overlooked in the depths of possible configs?).
You mean different time signatures? Just add them in the arrangement, and the piano-roll timeline will adjust accordingly.
ZynewaveThanks for the tutorials.
Personally I prefer to work with a sidechaining plugin using two mappings/tracks instead of three. My description earlier in this topic explained how to combine the 1+2 In and 1+2 Out mappings into one. Thus the main mapping will work just like a compressor insert effect, and you can choose to ignore the side chain mapping if you don’t need that feature. In this setup only the side-chain in mapping has a send dial.
You could also reconfigure the three compressive mappings into two mappings using a similar setup.
ZynewaveBeta3:
Clicking the piano roll keyboard will keep the note playing until the mouse button is released. Dragging up or down the keyboard will retrigger the played note. The clicked horizontal position controls the attack velocity.
The Shift/Ctrl/Alt-click actions on the piano keyboard can be customized separately for the select and pencil tool. The available actions include various note selections with audition, and a set of commands for step editing.
Using the step-editing actions on the piano keyboard will add/delete notes at the edit cursor position. The editor quantize value determines the duration of the notes. If the edit cursor is moved using keyboard shortcuts before releasing the mouse, then the current edit cursor position determines the duration. If looping is enabled then the edit cursor stepping wraps around at the loop end position. If playback is started and the “link edit cursor to play cursor” option is enabled, then the added notes and their duration is determined by the real-time position of the play cursor.
ZynewaveThe plugin exposes itself as a multichannel plugin rather than a multiple stereo pair plugin, so to use it as a side-chain plugin you need to do some device setup in the devices list on the start page:
Right-click “Crunchessor [Stereo]”, select “New Copy…” and the properties dialog will open.
Rename to “Crunchessor #1”.
Check “link to global instance”.
Press OK.
Right-click the new “Crunchessor #1” and “New Copy…”.
Rename to “Crunchessor #1 Side-In” (or whatever you like).
Set the “plugin output” to None.
Set plugin input “first channel” to 3.
Press OK.
You can now make multiple instance copies using the “New Instance” menu, if you want to use more than one side-chain plugin instance in your arrangement.
In your arrangement, create two tracks and assign each of the two mappings you created for one plugin instance. On the “Side-In” track, raise the send level. Set the gain to zero if you don’t want your side-chain input to appear in the mix. Make sure the fader is set at or above the effect track in the chain with the side-in mapping, or else you will mute the side-in send.
Now you need to do some setup on the “Routing” page in the plugin editor.
Select “C” and “D” in In3 and In4.
Select “C” and “D” in A and B of the “Key signal sources”.
That’s it I think. If I left something out, please let me know. All this was assuming that your side-in is stereo. You could also configure it as mono. The plugin routing setup I suggested was by trial and error, so it may not be the recommended way. You need to check the manual for that.
ZynewaveZynewave@michi_mak wrote:
Frits, i’m still thinking what could cause this troubles :
i tried with several synths and got same results – sometimes first note is sounding but not recorded –> can’t be the vsti i guesswhat i found today is that there is a difference in the number of clips recorded – sometimes it is just one and sometimes there ar two!?!
I may be able to figure out the problem if you can email me a project file saved after you recorded the double clips.
ZynewaveWow, popular topic 🙂
I may not respond to each individual post, but I’ll work my way through the suggestions and pick out the features I find will fit in with this round of piano roll updates.
—
Beta2 available:
Three new options in the piano roll region properties:
“Colorize notes with track colors”
“Draw notes with shadow effect”
“Audition notes when clicking and editing”
Alt+clicking any ghost note shown in the piano roll timeline will switch the editor to the corresponding sequence.
The clicked horizontal position on the keyboard controls the attack velocity of the audtioned note.
—
Let me know if the new color options makes it difficult to distinguish the notes.
Btw. this is fun to work on. It’s been years since I implemented the old piano roll editor. The new stuff like the rescalable photographic keyboard and the note shadow effect is only practically possible with todays faster PCs. That being said, if some of you find that the the “draw notes with shadow effect” option is markedly slowing down your UI, please say so. I will then consider having the shadow option disabled by default.
Zynewave@UncleAge wrote:
Nice to see some dev time spent on the piano roll. Tell me, are you looking for ideas in this part as well or are you just tidying up the interface a bit?
Feel free to post your list of wishes.
ZynewaveZynewave@H-man wrote:
Okay, cool. What does one miss out on by not having it?
A small amount of precision. But I don’t think that it is anything you would notice with todays faster PCs. Years ago you could risk that Windows would occasionally hickup a few millisecs, so the host application would then receive the MIDI messages a little later than they were received by the driver. If you use the timestamps from the driver then these small delay variations would not show up in the recording.
Zynewave@H-man wrote:
@H-man wrote:
I have just re-confirmed the above and am now testing with the TimeStamps from driver setting disabled.
Okay …seems to have eliminated the problem. Recording resumes as expected.
Any ideas on why this occurs Frits?
Faulty driver, I would guess. This problem has popped up many times over the years. Apparently there are not many sequencers that utilize the driver timestamping so that could explain why there are so many drivers where this is not implemented/tested fully.
Zynewave@jpleong wrote:
I was wondering if it were possible for you to produce a short “Change-log” video with each new release. While it’s great to read about these new features, I have a hard time knowing what some of them actually do or how to actually take advantage of them. Now, I’m not talking about some elaborately produced video but more like a simple screen-shot video with narration (like what can be done with Adobe Captivate).
It’s a good idea, but one that I feel would take too much of my time. But maybe I should consider this at some point in the future.
ZynewaveSorry to hear that.
One more suggestion: Make sure the “use time stamps from driver” option is disabled in the interfaces dialog.