Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@thcilnnahoj wrote:
Okay, here’s a non-flashy video of how to set up Addictive Drums as multi-output instrument: http://www.youtube.com/watch?v=RbrtFct9b38
Excellent! =D> I added that as a favorite on the ZynewaveDotCom channel.
Some tips, that you may already be aware of:
In the start of the video you rename the individual mappings. You can rename the folder (e.g. from “Addictive Drums” to “AD”), and all mappings will be renamed accordingly, provided that you do it before customizing the individual mapping names.
I initially did not notice how you extended the loop range. You could also have right-clicked the loop button and selected “set loop around selection”.
Maybe Frits would like to do a video for GPO? Because Kontakt & Kore Player are not nice to work with… 👿
Just curious: What don’t you like about Kontakt & Kore Player?
ZynewaveKeymasterMenu: Setup > Explore Setup Folder.
Open the “PluginQuarantine.txt” file and remove the lines for plugins you believe are safe to try again. Save the file back.
On the project start page, use the menu: Devices > Update and Load Plugin Database.
ZynewaveKeymaster- Relative snap and edit cursor snap options.
- Revised the mouse key modifiers and made Shift key work as snap override.
ZynewaveKeymaster@thcilnnahoj wrote:
1. The original note, with an example snap setting of 1/16th
2. First snap point – the note is extended to a length of 1/16th
3. Second snap point – relative snap
4. Third snap point – grid line
Steps 3 and 4 can then be repeated for every 16th step.Is this by design? I kinda expected the note to first snap to the .3 grid line (as it’s the closest point to snap to) instead of getting quantized to the snap setting, but it seems it won’t snap to this particular grid line at all.
Yes. The minimum resizable length when snap is on, is one grid unit. If you want it shorter, then either disable snap, or reduce the grid size.
ZynewaveKeymaster@LiquidProj3ct wrote:
What I would ask is: It’s very difficult move small events due to resize arrows. Maybe you can do the resize limits a little outside of the event. Look this video, it will be deleted once you’re aware of it:
http://www.youtube.com/watch?v=-gqIVz1etZg
My experience making music is that you need move more frecuently the pitch of notes than altering the groove. This is specially important when you’re seeing a big arrangement, 8 or 16 bar, where you want to have a global vision and move the notes up/down in that view.
A tip: If the event is so small that it only shows the resize cursors, you can override the resizing by ctrl+click+hold on the event, and then release the ctrl key to move the event.
Extending the drag handle area beyond the event border is something I will consider in the future.
ZynewaveKeymasterGood news. I traced the the code that consumed a lot of CPU, and luckily it was easy to speed optimize. Please test again with the next 2.30 demo, and let me know if you still see slow UI response to fader movements. 2.30 will be released within a day or two.
ZynewaveKeymaster@LiquidProj3ct wrote:
Small suggestion, not as critical as the reset suggestion but it could be good, I think it’s a good idea allow that marquee work with Ctrl+LMB with pencil tool. Nowadays if you keep down control and LMB in a empty area you write an event, the same that if you simply press LMB. So the suggestion is that Ctrl+LMB start a marquee that doesn’t reset the existing selection with pencil tool.
Done. Applies to the tracks, piano roll, drum map and format regions.
ZynewaveKeymasterBeta4 is up. This will probably be the last beta, and if no serious bugs are reported, I’ll release 2.30 within a couple of days.
Additions to beta4:
Shift+clicking to start a marquee selection will reset existing selection first. Ctrl+clicking an empty area will start a marquee selection adding to the existing selection.
Assigning an audio-enabled device mapping to a non-audio track will automatically enable the fader and meter on the track.
Fix: A child track that is tagged can now be collapsed if the group track is also included in the tag selection.
Please test that the fix for the tagged child tracks behaves as you expect.
ZynewaveKeymaster@thcilnnahoj wrote:
The problem is that the events are cut off at the end of the last note: GIF animation (this one consists of 32th notes, and is cut off one 32th early). It is created correctly in other hosts. The same seems to be happening when dragging events from the inspector’s track panel…
I take it that the bit that is cut off contains silence. So it doesn’t actually corrupt the playback, but it is an annoyance when you want to repeat the pattern snapped to bars?
ZynewaveKeymaster@thcilnnahoj wrote:
Something I came up with:
Ctrl – Create phantom copy
Alt – Lock x/y position
Shift – Override snap
Ctrl+Alt – Create unique copy
Ctrl+Shift – Create phantom copy and override snap
Alt+Shift – Create phantom copy and lock x/y position
Ctrl+Alt+Shift – Create unique copy and override snapIt’s not great either, especially Alt+Shift is weird, and there’s no shortcut to create a unique copy while locking the x/y position.
I don’t know of any programs that add the right mouse button as a modifier, and think I’d find it uncomfortable…Thanks for the effort. You’re right that Alt+Shift is weird, because suddenly the Ctrl is not used for dragging copies.
The way I approached it was to make the three modifier keys have a specific function, and not deviate from that. After you have memorized these three modifiers, you could easily figure out what combinations of the keys would do. The downside is that there are some key combinations that may be less useful.
ZynewaveKeymaster@thcilnnahoj wrote:
Middle-click on the timeline will set the edit cursor snapped. Holding Shift while clicking will set the edit cursor without snapping.
I really like(d) this one. 🙁
Moving the cursor with snapping enabled can already be simply done by clicking on the timeline. I think not everyone uses, or even has a middle button available, so I preferred it doing something special.Hmm, I actually was annoyed by the old behaviour. I use middle-click to quickly position the edit cursor on the grid when I’m editing events. Though this change may be a minus to you, I hope you overall find more plusses in this release.
Modified the behaviour of the Q/W key shortcuts: Q/W moves the edit cursor in steps of the grid value. Shift+Q/W steps the edit cursor between marker events and active loop, punch and segment ranges. Ctrl+Q/W will set the edit cursor to the start or end of the current event selection.
Hmm, this is fine, but you also seem to have swapped the actions of the numpad home/pgup and left/right arrow keys…?
They were swapped automatically by the change I made to the commands, but I’ve now swapped them back to their previous numpad keys. I’ve also added numpad 1/3 as shortcuts for setting the edit cursor at the start/end of the current selection. I don’t use the numpad myself. Would you perhaps prefer a different setup? Maybe the shortcuts you use the most should be on 1/3.
Edit: The help text for the note editor’s velocity buttons, and the curve editor’s draw mode buttons should be returned back to point to Ctrl instead of Alt.
Fixed. Thanks.
ZynewaveKeymaster@LiquidProj3ct wrote:
When you import zReeverb the Mono version is confused as a Mono In version with one input and two outputs
The “Mono In” indicates that it is stereo out instead of mono in/out. I’ve never heard of a reverb plugin that had mono output ❓
ZynewaveKeymasterBeta3 is up. This fixes two bugs:
@LiquidProj3ct wrote:
I don’t understand the point of “snap to previous grid line”, but “snap to closest grid line” works for me, it seems more consistent bacause when you drag a note horizontally it doesn’t “dance” (behavior that seems buggy).
Even though the jumping back and forth was highly confusing, I found it was actually correct behaviour when I debugged it. It happened because snap relative was still snap to “closest” relative position, so you would get a jump backwards when dragging across the grid line because that suddenly made the “snap to previous grid line” closer than the relative position. I’ve fixed this confusing behaviour by making the relative mode snap to “previous” relative position when the “snap to previous grid line” mode is enabled.
Maybe you’re aware of this: If snap is on, and you click in the border of a note, then press shitf and you move the note you can do the note as tiny as you want. But if you start to resize the note without keeping down shift key and while resizing you press it you cannot do smaller than snap value.
I was aware of it, and it is now fixed. Thanks.
ZynewaveKeymaster@confusador wrote:
ok, that all makes sense. is there a thread somewhere about how to show the hidden track and draw the event to enable realtime bounce?
1/ Enable the “realtime record bouncing” mode on the group track.
2/ Right-click the empty “effect” button on the track header or the inspector, and select “options > hide track lane”. That should reveal the hidden bounce track with the “B” button on the track header.
3/ Draw the sound event on this track.
4/ Hide the bounce track lane again, to tidy up.
5/ Select “Arm bounce recording” from the bounce menu.
6/ Enable record mode in the transport toolbar.
7/ Start playback.Step 2 to 4 will not be needed once I implement the automatic creation of the sound event.
is it possible once you’ve drawn the events for the realtime bounce recordings to save the whole setup as a track or track group template?
It should be. If you enable the copy events option when saving the group track as a template.
i’m not sure about rendering offline with jamstix. i haven’t been able to get it to work as far as i can tell, but i’m clearly missing something here, so it may well be possible. thanks for the detailed response regarding the presentation of the multi-out instance of jamstix. i think this is related to the global/insert plugin architecture detailed in the manual yes?
Yes.
ZynewaveKeymasterBeta2 is up. Some bugs are fixed, but there are still a few left that I’ll look at tomorrow.
The “snap to previous grid line” option is added to the snap menu.
When an event drag operation has started, each press of the Ctrl key will toggle between phantom and unique copy. I think it works ok. Let me know what you think.
