Zynewave1.31 is now reuploaded. The link is in the VIP lounge.
ZynewaveI’m running out of ideas 🙁
To eliminate possibilites of viruses, and other such things, could you try to revert to Podium 1.31, and check if that speeds up things?
Are there any other situations where Podium is slower than usual?
Are there any other applications on your PC that takes this long to quit?
Quitting Podium without any project loaded, should be almost instantaneous. On my old 800MHz PC it takes about 1 second.
ZynewaveSuggestion:
Locate your Podium.ini setup file (location is described in the setup section of the guide). Make a backup copy of it. Delete Podium.ini. Start Podium. You should see an empty project and the project wizard pops up. Close Podium before doing anything. Is quitting still taking an eternity? If not, email me your Podium.ini file.
If this fails, then I would suggest as an experiment to disable hyperthreading in your BIOS. I have recently come across posts that describe how hyperthreading can be problematic on some systems. A good example is this:
ZynewaveDoes the Podium window stay open during the 15 seconds?
P4 3ghz
Is that a hyperthread edition? And if so, is hyperthreading enabled/disabled in the BIOS?
ZynewaveIt makes no difference if I start a new project or when any other project is loaded.
So, even if your current project is completely blank, Podium is still taking 15 seconds to quit? 😯
This should take only a split second. What are your PC specs? Does the Podium window stay open during the 15 seconds? If you unselect all your MIDI and audio interfaces in the Podium interface dialog, does it still take this long?
ZynewaveI have not experienced this.
Just to see if I understood you right: With the exact same project file loaded, v1.31 took 4 seconds and v1.32 took 15 seconds to quit?
Does it take equally long if you use the ‘new project’ menu?
How big is your project file? Are there many arrangements in it?
ZynewaveStore editor zoom adjustments in arrangement object and project file
I’ll probably do this one for the next release. I have no estimates for the other items on your list.
Zynewavekeyboard shortcuts for temporary selection of the Scalpel tool
Do you mean you want the previous tool to be reselected when you release the key?
How about using the tool selection D and F key shortcuts. If you use the slice tool often, then you can move it next to e.g. the rearrange tool in the toolbar setup dialog. Then you only need to press D or F to switch between the two tools.
ZynewaveHi,
Even with this description, I can’t do anything about it until there is a demo of GURU. Please let me know when it is out.
Frits
ZynewaveZynewaveDo you think that you could improve this ?
It can be improved. I don’t know when I’ll work on it. It will require some time.
ZynewaveSo, does this mean you’ll be able to effectively encapsulate entire branches on the tree and map them to a single node?
That’s the idea. But I need to consider carefully how to design this. I have no estimate on when I will start experimenting with it.
ZynewaveYes, good point. This has also been nagging me frequently. I’ll probably change the edit behaviour. I will probably keep the painting of the bars sized to note lengths, as I think it helps to associate/identify the note that you are editing the velocity for.
ZynewaveThe maximum group level limit is a UI restriction only. I’ll increase it just slightly. I would like to keep a max limit, to avoid abuse. It e.g. affects how the mouse behaves when you drag a track to set the group level.
When I get around to implementing device wrapper mappings, there will be less need for creating deep multiple nested plugin tracks.
ZynewaveI’ve noticed that when I change some curves in the embeded editor (volume for example) while playing, the values are not send to the audio until a restart of the play ?
The engine prepares playback approximately one second ahead of time, so if you change events just slightly ahead of the play cursor, the changes will not be heard in the playback.
It seemed to be solved in the floating editor ?
There should be no difference on this behaviour no matter if you’re using embedded or floating editors.
Also, the audio is “muted” when changing the length or splicing an audio sequence until a restart of the play too.
It will be nice if it don’t affect playing…
Yes, this is a problem I will fix at some point.