Zynewave.
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.
Malcolm Jacobson@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)
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?
Cheers,
Malcolm.
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.
Malcolm Jacobson@Zynewave wrote:
Check if you have cleared the “use time stamps from driver” option for your MIDI input in the interfaces dialog.
Yes, I had. Clearing the check box fixed the problem. Thanks!
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.
Cheers,
Malcolm.
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:
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.
Malcolm JacobsonHi Frits,
Thanks for fixing the save issue. Works fine in beta 4.
I’ve been playing around with the timing adjustment trying to understand how it works and it looks pretty powerful. Good to hear that you’re going to write a manual entry for it. 🙂
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?
Cheers,
Malcolm.
Zynewave@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.
roninHi everyone,
I’ve tried beta4 yesterday and wanted to share some thoughts:
Honestly, I have to admit that I don’t really understand what the controls are doing. I had to read through this thread to get an idea. After that I knew that it wouldn’t be very useful to me but I can imagine that other users might have a good use for it.
Anyway I have some suggestions/notes for these new dialogs:
1. I don’t like modal dialogs at all. Sometimes I wish to inspect another part of the arrangement while tweaking. Maybe the new dialog can be non-modal and just stay on top?
2. There is “Adjust timing” in the piano roll editor and in the arrangement editor. I couldn’t figure out how “Adjust timing” works in the arrangement. I’ve selected events etc. but nothing happend during tweaking the knobs ( “preview” was activated). Only the timings editor in the piano roll did change something.
3. A double-left-click action resetting the knobs to their initial value would be great.
4. How about something like “randomize velocity/volume”? That would be useful to me in conjunction with the other timing commands to humanize drum parts.
ZynewaveBeta5 is up. I delayed the release because I found a flaw in the plugin import, while trying a demo of the Rocket sidechain compressor. I ended up doing an overall revision of the plugin import and the Create New Project page. I would appreciate if some of you could try to create a new project and import your plugins with beta5, and see if your plugins are still imported correctly. I’d also appreciate comments on the new plugin naming convention. The list of changes in beta5 are:
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.
Importing effect plugins that support 3 or 4 inputs and stereo output will now by default be configured as sidechainable effects.
Right-clicking a global device in the inspector device list will show the “New Instance” command. This command was previously only available in the device list on the project start page.
Made some layout changes to the Create New Project page.
Simplified the naming convention for device mappings that are generated by creating a new project or by importing plugins.
Creating a new project will now create default MIDI mappings for any enabled MIDI outputs. Previously you had to use the “import hardware definition” command from the devices menu.
Creating a new project will set up additional mono mappings for the busses.
Using any of the import plugin commands will only create surround mappings for the plugin if there already are other surround mappings in the project.
Renaming a folder containing device mappings will popup a messagebox asking whether device mappings that share the name of the folder also should be renamed.
Fix: Some VST plugins that reported multi-channel support would not be imported correctly as stereo effects.
Malcolm Jacobson@Zynewave wrote:
Beta5 is up. I delayed the release because I found a flaw in the plugin import, while trying a demo of the Rocket sidechain compressor. I ended up doing an overall revision of the plugin import and the Create New Project page. I would appreciate if some of you could try to create a new project and import your plugins with beta5, and see if your plugins are still imported correctly. I’d also appreciate comments on the new plugin naming convention.
Hi Frits,
I did a brief test and it seems to work OK with my plugins. I own the Rocket compressor, and I can see the sidechain in the list now.
Unfortunately the Multi version of Garritan Personal Orchestra 4 still imports with only 2 outputs. I made a Track Template a while ago that included the 16 MIDI inputs and 16 stereo outputs, but it doesn’t work in 2.27b5, or 2.26 for that matter. Do I have to create a new template, or is there some way to get the import to recognise that the plugin has 16 stereo outputs?
Cheers,
Malcolm.
Zynewave@Malcolm Jacobson wrote:
Unfortunately the Multi version of Garritan Personal Orchestra 4 still imports with only 2 outputs. I made a Track Template a while ago that included the 16 MIDI inputs and 16 stereo outputs, but it doesn’t work in 2.27b5, or 2.26 for that matter. Do I have to create a new template, or is there some way to get the import to recognise that the plugin has 16 stereo outputs?
Can you describe what doesn’t work? If the template won’t load at all, please email it to me you.
Is there a setup screen in the GPO4 editor where you define how many outputs you want to use?
I have the GPO2 Kontakt based version.
Malcolm JacobsonAll of the tracks in the template load, but the plugin itself does not.
There’s a screenshot of the plugin/template here:
http://www.zynewave.com/forum/viewtopic.php?t=2167
When you open the plugin you can route the 16 instruments to separate stereo outputs. The template used to load the plugin with all of the routing set up.
If the plugin import process would set up the 16 MIDI inputs and 32 audio outputs as part of the device definition, it would negate part of the need for the template.
Cheers,
Malcolm.
Zynewave@Malcolm Jacobson wrote:
All of the tracks in the template load, but the plugin itself does not.
There’s a screenshot of the plugin/template here:
http://www.zynewave.com/forum/viewtopic.php?t=2167
When you open the plugin you can route the 16 instruments to separate stereo outputs. The template used to load the plugin with all of the routing set up.
If the plugin import process would set up the 16 MIDI inputs and 32 audio outputs as part of the device definition, it would negate part of the need for the template.
What I’d like to know is whether you think that track template loading is broken. You said it doesn’t work with 2.26 or later. If you mean that the template file loaded ok in 2.25, but not in 2.26, then please email me the template file. As far as I can remember, I haven’t tampered with the template loading in recent versions.
If the multi dll version of GPO4 doesn’t import with all supported output mappings, then it’s the plugin that works in a different way than all other multi-output plugins I’ve tried. There is no demo of GPO4, so I can’t test this until I pay the 50$ to upgrade my GPO2 to GPO4.
z_sfyrHi. Just on the subject of plugins – since the last few Podium updates I’ve had a couple of plugins that have lost the ability to save presets at all, and thus lose the settings when I close the project. In particular, Kjearhus MPL-1 , and Ruction – I don’t know if it’s me or a bug so I thought I’d mention it. Cheers.