Zynewave@LiquidProj3ct wrote:
Frits, I don’t understand the most of the controls, but it seems that only quantize notes towards the left, I’m a little confused
Please be more specific about what you find confusing. From the above quote I don’t know whether I should throw away the whole dialog and start over.
ZynewaveBeta1 is up. Everything is implemented, except the backup storage of original timing and the “extract groove…” option. So all changes are applied destructively. The “perform adjustments on original timing” checkbox has no effect yet.
Please try out the different settings in the dialog, and let me know if it all makes sense.
Zynewave@Malcolm Jacobson wrote:
@thcilnnahoj wrote:
Workaround to get real-time bounce recording working: …
I seem to be having this problem in 2.26. In order to get Realtime Bounce working I have to create a blank item in the track by doing an offline render first.
Is Realtime Bounce working properly in 2.26 on your system?
Cheers,
Malcolm.
Automatic creation of sound events for realtime bounce is something I have on my todo list. It’s going to be fixed as part of one of the next track-related releases.
Zynewave@LiquidProj3ct wrote:
I’d say that a MIDI file is more flexible, because you can save it (for a future use), exchange it with other users, edit it easily (timming and velocities!), and you can extract a groove using any third party vst slicer or audio editor
You can also do that with the solution I suggested. To create a groove file, just export the note sequence to a MIDI file. To apply a groove, drag the MIDI file onto a track, copy the note events to the clipboard, delete the sequence event again, and use the adjust timing dialog. I could remove a couple of those steps, by adding a “Copy events to clipboard” command when you right-click a MIDI file in the browser.
Zynewave@kyran wrote:
@LiquidProj3ct wrote:
2. Custom grids, as FL Studio. You can load any midi file in quantizer tool and it will work as a grid (and velocities). Take a look to its help file: http://flstudio.image-line.com/help/html/pianoroll_qnt.htm
I like that FL feature a lot. Interface wise you could replace the first editor box (where you select the grid snap) with a selector for the midi file containing the snap grid.
What I had in mind was to add an “Extract groove from clipboard events” option, either as a new checkbox option or as an entry in the grid combobox. This is simpler, and also a bit more flexible. You could for example: Beat slice a drumloop sound on a track, press Ctrl+C to copy the events, undo the beat slice command, open the piano-roll, select the note events, select “Adjust timing” and use the “extract groove…” option to apply the timing of the drumloop to the MIDI events.
ZynewaveZynewave@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.
any plans on providing ‘direct access’ shortcuts ( like adjusting swing amount once and then only performing swing without bringing up this window everytime? )?
I’ve thought about it, but it may come in a later release. After I implement the other adjust dialogs, I plan to make a preset system for the adjustments. You’ll be able to create presets named “Swing 5%”, “Quantize 1/8 20%”, “Set 10 ms fade-in”, etc. and be able to apply them through key shortcuts.
ZynewaveSam, did you try the ASIO4ALL driver? If so, did it show the same problems?
ZynewaveZynewaveZynewaveZynewaveZynewaveDoes this also happen when using the ASIO driver in other hosts than Podium?
If it’s the Presonus ASIO driver that is faulty, then perhaps the ASIO4ALL driver will be better at communicating with the interface.
ZynewaveZynewave