ZynewaveOne thing I did notice tho. If you repeat the procedure above, so there are two arrangement windows open, then load a new project from file -> Access Violation… But I realise this will be a rare thing!
Thanks for alerting me to this. I tried it and managed to make my system crash as well. Hopefully it is the same bug that you experienced. The crash occurs if the track inspector event list in the separate editor window is not empty. If you select a track with no events before loading a new project, then I’ll bet you won’t see the crash. Bugfix will be in 1.22.
Dragging of events across editors is currently not implemented. Events are lightweight objects (need to be cause there can be millions of them in a project), so event drag operations are handled differently compared to when you drag objects that appear in the object lists.
ZynewaveZynewaveMany thanks. I found the bug. Fix will be available in 1.22.
ZynewaveHi Nemesis,
Glad you like the program. I tried modifying the freebees project to get this ‘stray’ parameter object, but did not succeed in crashing Podium. It would be a great help if you could email me your project file and point out which track I need to click to cause the crash. It should be easy to fix this bug.
Frits
Zynewaveone thing you could do is compare each setparameterautomated value passed, and compare it to the current host value for that parameter, and only record the change. I realise that this could be hugely CPU intensive, and so could be an option for plugs that display this kind of behaviour.
That would probably help with the Z3ta+ problem, and it would not be CPU intensive at all. It would not help with plugins that output all parameters on a program recall. Rather it would then only record curves for parameters that have changed compared to previous program, which also is undesirable. Currently Podium does not maintain its own copies of the plugin parameters, so I do not have the previous value to compare an automated value with. I’ll be looking into this when I start on the generic editor for GUIless plugins.
ZynewaveZynewaveConcerning the new plugin automation recording:
The approach I chose was to make it as easy as possible to record automation. Arm the record button on the track with the plugin, start recording/playback and drag away in the plugin editor. I find it convenient to be able to record automation without worrying about automation read/write mode and selection of parameters that you want to automate. This approach however has some disadvantages with certain plugins. Some synths output all parameters upon a program recall. Recall a preset in e.g. the SonicSynth2 demo, and whooosh… you have close to 100 tracks with parameter automation. To avoid this you need to stop playback or disable recording on the plugin track before loading a new program. I observed another undesired behaviour with Z3ta+, where simply hovering the mouse over a slider would automate the parameter.
If this becomes a problem, I will have to think of some way for the user to disable or prevent automation recording. Please report if you find any plugins that is causing difficulties.
ZynewaveZynewaveCurrently a track cannot be copied to the clipboard, but I’ll add it to the plan. Until then you’ll have to copy all the events on the track (quickest way is to use the track inspector event list), go to the new arrangement, create a new track and then paste the events.
ZynewaveHi Gabriel,
I’m doing fine, hope all is well at your end also.
I’ve been meaning to add the use of the insert key to the arrangement editor, like it is used in the note and drum editor. Selecting any single event on a track and pressing the insert key would then place a phantom copy at the end of the selected event. Pressing insert repeatedly would place a series of copies. Would this be a sufficient solution?
Frits
ZynewaveUse the ‘Import File…’ menu to import your MIDI file into your existing project. If your VSTis are properly set up with MIDI channels etc. then the plugins will automatically be assigned to the track in the new arrangement.
I wrote a short tutorial in a previous topic:
http://www.zynewave.com/forum/viewtopic.php?t=202
ZynewaveDon’t worry Francois 🙂 , I read everything that is posted here. I’m currently finishing release 1.21. After this I’ll go back to do some minor updates for 1.22. I’ll make sure to include the parameter dial improvements in 1.22.
Zynewavewill there be something similar for MIDI tracks?
Not in the first attempt. It could be added later on.
Zynewavedepending on the plug, the number of dials could alter enormously
The inlined dials would be based on the parameter objects defined for the plugin, so if the plugin has a large number of unneeded parameters, you could just delete those parameter objects.
I’m considering a more advanced solution, by adding some kind of graphic control type setting to the parameter properties. I’ll be experimenting with this when I start on the emulated editor for GUIless plugins.
ZynewaveI’ve been thinking about a solution where you in the arrangement properties can define one or more VST plugins to be used as channel plugins. Adding an EQ plugin here would then make the plugin parameters appear as dials inlined in the mixer channel strips (on the tracks where it has been enabled). This way you can more easily use your favorite VST effects as channel plugins. Implementing this would make it unnecessary for Podium to have builtin effects. Even if I could implement high-quality EQ and compression, there will always be someone who will not like the ‘flavour’ of the effects.
This idea is still in the design phase, so I don’t have an estimate on when it will be done.