Zynewave@acousmod wrote:
Alt+Click to create phantom copies
and
The scalpel default behaviour when clicking with no keys pressed would then still be phantom copies.
?
Yes they do the same thing. I could skip the Alt+Click shortcut then to avoid confusion. I suggested it for consistency. When you drag and drop with the select tool, holding Ctrl will create unique copies and holding Alt will create phantom copies.
ZynewaveThis means without having to select the scalpel ?
No, you will need to select the scalpel tool. When using select and pencil tools Ctrl+Click will toggle select and Alt+Click will start a resize action.
Zynewaveand the interface of Podium and Windows becomes very slow to refresh (several seconds to open a window)
This was an unfortunate side-effect of the changes in 1.63. I have fixed this for 1.64.
Zynewavewhen splitting a curve sequence, it would avoid to have to turn to “clone phantom sequence” and “crop unique sequence” each time
How about Ctrl+Click to create unique copies, and Alt+Click to create phantom copies?
The scalpel default behaviour when clicking with no keys pressed would then still be phantom copies.
Can we be the envelopes sequences automatically turned into real copies when we choose “copy this only” ?
I would prefer adding ‘select all curve events’, ‘select all sound events’, ‘select all note sequence events’ in the edit menu of the arrangement editor. Then you only need to ‘select all curve events’, and then use the edit menu to ‘clone’ them all in one go. Good enough?
ZynewaveA lasso selection instead of a time range selection will allow to do what we want.
You can start a lasso selection by shift+clicking. This also works with the pencil tool.
Delta value indication when dragging is something I’ll add eventually.
Zynewave@acousmod wrote:
Does the file helps to find a solution ?
I have downloaded it, and will look at it after the release of 1.64.
ZynewaveZynewave@darthstephen wrote:
whoa…nevermind.
i’ve been doing just alittle audio multitracking with podium until today with the quick studio setup. i just got my brain blown up by the manual device mapping stuff. cool 😯
Cool. I was just about to post that if you use the quick setup button, the multitimbral MIDI mappings will not be created. Use the ‘import multitimbral plugin’ button in the project wizard for that, or manually create the extra MIDI mappings (which I guess you have done now).
I also own GPO, and I posted a GPO example project a while back:
http://www.zynewave.com/forum/viewtopic.php?t=494
Edit: There’s a download link to the project file somewhere in the topic.
ZynewaveIs that ManyStation 1 or 2?
I went to the Manytone site, but there doesn’t seem to be a downloadable demo version. I think ManyStation is based on the Wusikstation engine, which is available as a demo. Have you tried Wusikstation?
ZynewaveBy bouncing each of the outputs and then unloading the plugin, I could gain back those precious cpu cycles and work on the mix with significantly less strain
I assume that when JamStix is idle, it does not take up much CPU? If so, would muting the MIDI track not be enough? (provided that all individual plugin output tracks are bounced).
To unload a plugin by pressing Ctrl + the X bypass button on a track, it is required that all tracks with mappings of the instance are bypassed. The plugin cannot be unloaded as long as there are active tracks with mappings to the plugin instance. I think this can get rather complicated. I chose the bounce track feature as a means to unload plugins, because this resembles what other hosts calls ‘deep freeze’.
ZynewavePodium will not unload a plugin unless all tracks with mappings belonging to the plugin instance is muted by a parent bounce track. So a parent bounce track capturing all plugin outputs is the easiest way to control unloading of a plugin.
By the way hitting the x button the jamstix track does not unload the plugin.
That is on purpose. I consider solo, mute and bypassing as temporary actions during a mix session. In these situations a plugin unload would be undesirable.
ZynewaveZynewaveCurrently numpad0 will return to start of song when pressed twice. This could be changed so that it returns to last start position, and then a third press of numpad0 will return to start of song. Opinions?
ZynewaveDoes this will include also if it is the Arrangement or the Arrangement Compact view which is selected ?
I guess a ‘total recall’ is the ultimate goal. I may implement it in lesser steps though.
Zynewavecould you add an option to “release the driver when Podium is in the background” or, perhaps easier, “when the engine is off” ?
I would prefer the ‘release driver when engine is off’ option.