ZynewaveHi Kaos, summer is going fine,
I have been looking for it, but can`t seem to find an undo option anywhere in the menu. Is there one?
Currently they’re not in the edit menu. There are two undo/redo buttons in the toolbar, and the standard ctrl+z/y can also be used to undo/redo. Maybe I should put the undo/redo commands in the edit menu as well?
Zynewavei’d like to request that at the top of each plugin GUI you have…
Why would you prefer this to the preset panel in the track inspector?
ZynewaveI have some trouble with Library Presets, Library Banks, Programs Presets and Program changes
I apparently didn’t do a good job of explaining it in the new guide pages 😥
I actually have to assign each Program Preset to the track, then assign the corresponding Library Preset to the track, then “Update program list” in order to have the new one at the same place / program number
If you want to be able to edit all the presets in a bank, and switch between them with program changes, then I suggest you use a bank library preset. Using single library presets are intended as a quick way to store the current settings of the plugin, without caring about program changes.
I have not understood how works the “New Bank Library Preset” : where are the programs inside this new Bank
The bank library preset contains an fxb file, so when assigned to a track, it’s similar to loading an fxb file within the plugin (if the plugin supports that).
Zynewaveacousmod: It must be the code for the RME dropped buffers detection that causes your problem. I’ll remove it for the next release.
It works when I resize the end of the event, but stop the sound when I resize the begining
Correct. Resizing the start position requires that the event is reordered in the event list, so that will require a slightly different implementation. That will appear in a later release.
Podium doesn’t seem to recover from stand by mode too well in windows 2000
I’ve actually never used stand by mode myself, so I’ll do some testing with it.
ZynewaveAll I had done was a ”quick setup” in the Project Wizard. Then all menus were blank. That’s all I did.
That will do it. The quick setup will load each located plugin, examine it, and unload it. Do you have the KarmaFX synth installed?
ZynewaveNo, the menus now show printing as they would normally do.
I’ve experienced blank menus in Podium, but it was caused by the loading/unloading of a specific plugin (the one spoonboiler referred to above). When you had the problem with blank menus, had you been importing plugins or loading plugins by activating arrangement monitoring?
If you load the problematic project again, does the menus turn blank right away, or only when you activate monitoring?
ZynewaveCurrently parameter events can only be used with MIDI parameters 😳
The automation chapter was written some time ago, and at that time I had hoped that I would have time to implement plugin and mixer parameter events before the next release. But I needed to release a new demo version before the old one expired in August. I hope to have it implemented for the next release 1.38.
Zynewave@acousmod wrote:
I don’t know if you have tried it yet, but the sticky red color is only a slight red coloration of the background.
When i say “red” I mean that it goes to 100 % every second…
I don’t bother the color but the crakling of sound that occurs nearly all the time.The same project in 1.36 (with the same buffer settings) shows an average CPU of about 50 % with no clics (during normal playing).
With the 1.37 it pulses between 60 and 100 %.
When there is only one or two tracks active (16 channels) the CPU spikes occurs less often, but there is always a clic each time.The CPU spikes are perhaps due to the plugins, but there is a huge difference for me between the two versions.
So I continue to use the 1.36.
You quoted my reply to Conquistador. Did you read my previous questions to your post?
Zynewave@Conquistador wrote:
The CPU indicator background remains red after an overload has occurred. Clicking the indicator will clear the red color.
Frits how about an option for this instead. While the idea of having the CPU meter red until clicked is good, I would certainly prefer at least an option to change this behaviour. Constantly clicking it would become a problem over time.
I really do not get that many CPU spikes anymore frankly, but I would prefer a simple option for the CPU meters behaviour.
What do you think Frits? ❓
I don’t know if you have tried it yet, but the sticky red color is only a slight red coloration of the background. You can still tell when a regular CPU overload occurs. Does anyone else think this should be an option?
Zynewave@acousmod wrote:
Not really a bug, but this new version is unusable for me : the CPU indicator is now always in red with constant more or less periodic clics.
So I have reinstalled the 1.36 in which the average CPU is about 30 % less, with not clics while playing, only the CPU peaks when editing.I’ve not tried to bounce with the 1.37 since it was already impossible with the 1.36 due to the fact that passages that goes well when played present the same CPU peaks when boucing.
Hi Jean-Marc,
I assume you’re using your RME multiface soundcard. What version of the RME driver software are you using? What ASIO buffer size are you using?
With this release I added support for the RME ASIODroppedBuffers extension to the ASIO spec. It is a method that allows the host to query the driver if there was a buffer under/overrun. It works on my Multiface/Cardbus but I believe it was only supported in RME driver versions 2.52 and above. If this is causing problems with some driver versions, I may have to remove this support again.
When the CPU indicator goes red, does the CPU percentage rise to 100?
ZynewaveI’ve replied to this bug report in the 1.37 release topic.
Zynewaveall the menus are just a blank box, no printing in the menus or when you right click.
Could you try this for me: Select ‘new project’, exit Podium, start up again. Are the menus still blank?
What was the previous Podium version you used without problems?
What Windows version are you using?
ZynewaveZynewaveZynewaveThe Devices section of the guide has been rewritten. There is a new Transport Toolbar chapter. The Tracks page has been extended. There are new pages for Using Presets and Parameter Automation.
The revised guide will be included in the upcoming 1.37 release.