Zynewave@sam c wrote:
Frits, can you explain source to me? When I right click on a track, with no fx, auto, etc I see source and the choices are not something I understand. I see busses, instruments, Powercore, and Voxengo. None is a complete list.
The Source submenu is what previously was labeled “Instrument/Return”. I changed it to the shorter “Source” because the mapping name is now appended to the submenu label.
Zynewave@sam c wrote:
i’m glad there is a way to do it but why lose my pan option? the mono wav file starts off with a pan, as it should, why lose it because i ad an fx?……..
The panning process takes a mono or stereo source and outputs a panned stereo signal. Since a mono effect only processes one channel, you can’t route the panned stereo signal through the mono effect and expect the panning to be preserved. If you route a stereo signal into a mono effect, Podium will merge the two channels into a mono signal before sending it to the mono effect.
ZynewaveZynewaveFrits, can you explain the logic of setting a parameter to 0 when a clip is not present?
The parameter is not set to 0 but to the default value defined in the parameter properties.
To my way of thinking, it should be one of two things:
– Last set value plays until new automation is reached
Or preferably;
– On playback (when pressing space or PLAY with a MIDI keyboard) find the previous clip in the timeline for a given track, take its last value, and apply it.
– Last set value plays until new automation is reached
What I don’t like about this approach: The parameter value will be random when you start playback at a position where there are no curve sequences on a parameter track. The parameter value will depend on where you stopped playback last.
When the parameter snaps back to the default value whenever there is no curve sequence present, you are guarenteed that parameter automation is determinate no matter where you start playback.
– On playback (when pressing space or PLAY with a MIDI keyboard) find the previous clip in the timeline for a given track, take its last value, and apply it.
I may add an option for this behaviour in a future update.
Zynewave@Conquistador wrote:
@Zynewave wrote:
Added “Load Device Setup” submenu to the Project Templates submenu. This can be used to replace the device setup in the current project with the setup from a project template.
Strange. I cannot find the Load device Setup in the Project Templates Sub menu. Is there some sort of trigger to get it to appear?
I only see these three commands…
Save Project As Template
Explore Templates Folder
Update Templates List
The “New Project” and “Load Device Setup” submenus only appear when you have saved at least one project template. How can I make this more obvious? Should I add empty submenus and grey them out to indicate that there are no templates?
I noticed the graphics in Podium (cursor) will sometimes stop if I am moving a knob or similar on an FX GUI is that normal? I have a powerful graphics card 8800GT 512MB so it seems a bit odd to see Podium not updating the cursor…or is this normal ❓ ❓
It depends on the plugin. When you drag a knob/slider on a plugin editor, it’s the plugins responsibility to periodically provide the host with idle calls so that the host can update its UI. Some plugins may fail to do this, and thus the host animations appears to stop until you release the mouse button. It has nothing to do with the graphics card.
Zynewave@Conquistador wrote:
@Zynewave wrote:
I had a good look at the entire multi-processing code and managed to optimize some parts of the code.
Hmmmm…I loaded up a project in P2.B4 and I cannot see *any* differrence in CPU time. Am I looking in the wrong place or is there some sort of scenario that would produce even a slight difference in CPU readings?
It’s a minor optimization. You probably won’t notice it on the CPU % meter.
Zynewave@estwing wrote:
I found if i switched to expanded mode i could delete them no problem.
That’s because the old expanded mode track menu does not have the parameter submenu. In 2.00 the expanded mode track menu is now the same as the compact mode track menu.
ZynewaveZynewaveThere’s also been some discussion in this topic:
http://www.zynewave.com/forum/viewtopic.php?t=1379
Druid, let me know if this answers your question.
ZynewaveZynewave@Zynewave wrote:
@UncleAge wrote:
@Zynewave wrote:
@UncleAge wrote:
Now with the beta3 running I’m getting strange behaviour when assigning audio inputs to tracks (sometimes after assigning).
Please send me a project file with the track setup that has the unwanted muted audio input.
Disregard my PM. I sent it to the info@ address
Ouch. It turns out that a fix I made in 1.99 regarding the multi-processing had the unfortunate side-effect that only one audio input can be active. I’ll get that fixed.
Thanks for bringing this to my attention.
Beta4 is available.
While searching for a fix for this I had a good look at the entire multi-processing code and managed to optimize some parts of the code. The bug should be fixed, and CPU usage is slightly optimized (both with and without multiprocessing enabled). I would appreciate if you could check that this beta is playing your projects as expected. If all is ok, I’ll probably release 2.00 this week.
Zynewaveif I drag Stylus RMX onto a track, then right-click “Create Bounce Track” it creates a parameter track If I try to delete this parameter track using the menu, it creates a second one. No more, and I can delete them with the delete key, but this only happens with Stylus…
Thanks for the project file you emailed me. It turns out that Stylus reports it has 18719 parameters. This causes the Podium track menu (which shows all parameters in a submenu) to exceed the number of available menu IDs, and thus the parameter menus are confused with other menu commands such as the delete track command. I have added a limitation of 5000 on the parameter submenu to avoid this problem. You’ll still be able to access all 18000+ parameters in the inspector parameter panel list. Fix is available in the next 2.00 beta.
ZynewaveZynewaveZynewave