Zynewave@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.
Ok, this is now fixed in beta4. If you saved your project with beta3, you need to correct your time signature, and resave with beta4.
Another small addition to beta4:
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.
Zynewave@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.
Zynewave@Malcolm Jacobson 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.
Thanks Frits, that works pretty well. As a future, enhancement, it would be great if the MIDI input worked with the Child Tracks too. 8)
Agreed.
In other news, I’ve started getting a half-bar delay on any MIDI I record since version 226. If I play a kick drum on each beat of a 4/4 bar, it plays back 1/2 a beat late and I have to quantize all the notes. Has anybody else noticed this?
Check if you have cleared the “use time stamps from driver” option for your MIDI input in the interfaces dialog.
Zynewave@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.
ZynewaveI’m a bit short on supply of demo projects 😳
There are a couple of user created projects in this topic, that you may find useful:
http://www.zynewave.com/forum/viewtopic.php?t=1854&start=15
ZynewaveBeta3 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.
ZynewaveHi John,
Yes. You download a zip file with the installer on your internet connected PC. You can then copy that installer to the USB stick, and run the installer on the music computer.
ZynewaveI bought it too. It’s nice for testing that new swing feature in Podium 😉
I’m also fond of physically modeled drums. My next big purchase is probably going to be the new Korg Wavedrum:
ZynewaveNot as an input. You can record the MIDI output of a VSTi as a note sequence, which you then can drag to another track for use with other instruments. Currently you cannot route MIDI between plugins. To record the MIDI output of a plugin, select the “enable recording of VST plugin MIDI output” option in preferences/plugins.
Zynewave@Lion wrote:
Have you considered doing this non-destructively?
I have not tried the beta yet, but this is a feature I really love about Reason. It’s not a definite ‘Must-Have’ feature, but it IS a desirable one.
The final 2.27 release will save any timing adjustments made to each event in the project, so that you at any time can revert back to the original timing. That’s sort of semi-destructive I guess. If you mean a way to set up quantization or swing to be applied only during playback, then that is not something I have planned.
Zynewave@zamrate wrote:
Any forecast when this will be fixed? Ableton & EnergyXT are so far the only sequencers I tried that don’t mess up the MIDI timing..
I have a shortcut to this topic, so I will eventually examine it. At the moment I have a lot of stuff on my todo list that I find is more important.
Zynewave@Merkury wrote:
Ok,license bought ! 😀
This program rocks so much ,I’m addicted to it . If you really make the advanced quantize tool,it will be sequencer heaven. Much respect.
Thanks 🙂
Remember to check out the topic below for discussion of the quantize dialog:
ZynewaveBeta2 is up. There are some refinements to the dialog, and bar positions are now quantized correctly.
Zynewave@thcilnnahoj wrote:
@Zynewave wrote:
@michi_mak wrote:
this window looks very promising – maybe it lacks an entry for adjusting velocities?
I considered a single big dialog with controls for adjusting all note event properties, like velocity and transpostion. There would then be similar dialogs for sound events and automation point events, with controls for adjusting fade curve etc. I felt the dialogs became too big, so I decided to split out all timing related adjustments into this dialog. In a later release I’ll add the adjust dialogs for the other event properties, including velocity.
Have you considered still putting all (future) event properties in one dialog, but one using tabs?
It might just be a little quicker and more comfortable if you want to adjust note quantize values, velocities, and maybe other things in one go, compared to closing and opening multiple dialogs.
Yes, that may be a solution. But it’s a bit into the future. After this adjust timing dialog, I’ll return to my previous development schedule.
Zynewave@LiquidProj3ct wrote:
I don’t know what is “Quantize within range”, it seems a sensivity, and it seems that 100 is maximum sensivity.
Yes, it is a sensitivity. Maybe a name change can improve this. What about “Sensitivity min/max” or “Magnetic range min/max”?
Now is where I’m confused. Quantize duration and set duration, what is the difference? They seems to work in the same way.
Quantize duration adjusts towards the nearest quantized duration. Set duration adjusts towards a duration of the grid note value. If the duration of all your events are within one grid unit, then you won’t see a difference between the two. Anyone has a better naming for the “Set duration” option?
The notes, when I quantize start, always move to the left, when the right grid line is closer even, same with end and duration. I’m used to FL Studio quantizer which quantize to the nearest quantize point (left or right).
It does quantize towards the nearest grid line. There may be a problem if your sequence doesn’t start on a bar, because I haven’t yet made it sensitive to bar positions.
Anyway when I change the comboboxes it seems that the quantizer doesn’t work anymore (bug?) that was the reason because I was really confused.
Works fine here. What are you changing?