Zynewave's Forum Page
Forum Replies Created
-
March 11, 2010 at 13:23 in reply to: how to use multiple midi interfaces at once for recording? #17669
ZynewaveKeymaster@MelodyMan wrote:
No Windows-DAW can do what you want. It is a limitation of the ASIO-protocol. You can just record one device at a time. Apple has an aggregate driver, but Windows doesn’t (well, Direct Sound but the latency is high).
You could try ASIO4ALL. It is free and is a shell around the WDM-drivers. The performance for this isn’t bullet-proof though.
abducted is talking about MIDI inputs and not audio, so ASIO limitations is not an issue here.
March 10, 2010 at 13:06 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymaster@Malcolm Jacobson wrote:
One thing I’ve noticed is that the editor has an “Undo Timing Adjustments” option after you’ve applied the timing, but no option to Redo. Is it possible to implement Redo so we can listen to before and after in the editor window?
You can undo (ctrl+z) the “undo timing adjustments” command. I tried different names for the command to avoid associating it with the normal undo history. I tried “revert timing adjustments” and “discard timing adjustments”, but “undo timing adjustments” I think is still the simplest description for it. Let me know if you have other suggestions.
ZynewaveKeymaster@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.
ZynewaveKeymaster@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.
ZynewaveKeymaster@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.
ZynewaveKeymaster@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.
ZynewaveKeymasterI’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
ZynewaveKeymasterBeta3 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.
ZynewaveKeymasterHi 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.
ZynewaveKeymasterI 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:
ZynewaveKeymasterNot 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.
ZynewaveKeymaster@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.
ZynewaveKeymaster@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.
