I’ve now tested this and found the reason why the Podium animations stop. It seems that xt2 is occasionally interfering with the windows messages Podium uses to keep the UI timer alive :?. I’ll try with a different solution, to avoid conflicts with xt2.
@thcilnnahoj wrote:
It’s good enough for me. The only suggestion I have that’d make it quicker to use for me would be shortcut keys for the “+” button menu. I don’t know what the term is (shortcut mnemonics or something?)… I’m talking about the underlined letters for each menu option.
Come to think of it, I don’t think I’ve ever seen those used anywhere in Podium, so it’s probably not a quick thing for you to implement. Well, it’s just dandy as is! 😉
There are some menus in Podium that use the underline shortcuts, but Windows will only show them if the menu is opened with an Alt+key shortcut. You could try with Alt+E for the edit menu. Same thing with dialog boxes, where the shortcut underlining only appears once you press the Alt key.
Thanks for the suggestions.
Considering the modest amount of traffic this forum is currently seeing, I have my doubts that a competition topic that requires a lot of time investment is going to generate a lot of competition entries.
Today I have released Podium Free 2.40, and set up a new April 2011 competition. The competion topic is simple. All you need to do is write a number :wink:. I’ll consider more elaborate competition topics when more people start to join the forum and the competitions.
@thcilnnahoj wrote:
For experienced users, it’s certainly going to be useful if the “+” button remembers the last snapshot’s settings. As a personal example, since seeing what you did with the default snapshots, I’ll most likely only adjust snapshot #5 (default vertical zoom) and never have to worry about zooming in manually. Those three sizes are perfectly sufficient.
2.42 is now released. I ended up with making the “+” button always create a full snapshot. As you mentioned, new users would otherwise not realize this feature if the “+” button just creates copies of the last default partial zoom snapshot. Instead, I added four new shortcut commands to the “+” button right-click menu, for adding single option snapshots. I hope that is acceptable for quick setup of snapshots.
@bbreakz wrote:
ok thanks… any plans on adding input quantizing?
Perhaps not input quantization, but eventually I intend to continue with the groove quantize feature, as discussed in this preview topic:
Hi Aaron,
Thanks for sharing.
@Aaron wrote:
probably my favorite vst synth i’ve used. (even though I’m pretty sure it crashed my system a billion times and I lost at least one track to save file corruption)
Yeah, I have experienced random crashes as well. That is why I haven’t released a 1.0 version yet. The plugin is made with SynthMaker, which means there are some bugs that I don’t have control over. At some point I’ll check whether stability has improved with the latest SynthMaker release.
@bbreakz wrote:
also please have a way to export all the samples I’m using in the project to a folder… yes you can do it with the “New Arrangement as Unique Copy” but it copies every single instance of each audio item into the folder… so in my case for an item called FX (for example)… it would be FX1, FX2, FX3 etc… but in reality theres only one file being used… It eats up a lot of hard drive space…
That issue with the “.. as unique copy” command is fixed in the 2.41 release. In a later release I plan to add support for “consolidating” your project, which includes copying referenced sound files into the project folder. I don’t have a time estimate for when that will be implented.
@thcilnnahoj wrote:
One suggestion I have is to put the default V-zoom snapshots before the T-zoom ones, even though it seems backwards. I think most people will create new timeline position/zoom snapshots much more often than vertically zooming ones. With the default snapshots, creating a new one only stores V-zoom settings, which might be confusing to people who don’t know about the right-click options. Alternatively, maybe there’s a way to put the “+” button in a new snapshot group by itself?
:-k Hmm, thinking about it: Maybe the “first snapshot in group” option is not needed at all. The grouping of snapshot buttons could just be determined from the four other options. A space would be inserted between two snapshot buttons, if their timeline/track options differ.
The question is then, what should the “+” button add? Should it add a snapshot with the same options as the last existing snapshot, or should it add a snapshot with all four options enabled? If it should add all four options, then there would be a space between the “+” and the last existing snapshot button, if the last snapshot does not have all four options enabled.
@Pod_Boy wrote:
I actually got Podium to crash which is a rarity.
I have the file – it is consistently crashing. I have another file……….
like it which doesn’t. It doesn’t bother me, I worked around it.
Maybe you would be interested…..It happens when I import a midi
file from EnergyXT2………
If you mean Podium crashes when you in Podium try to import a MIDI file that was exported in eXT2, then please email me the midi file.
Thanks. I’m aware of this. It’s a sideeffect of the method I’m currently using for zooming beyond the end of the arrangement. I’ll fix this at some point.
Beta2 is up, with the following additions:
• Added “load default snapshots” and “save as default snapshots” commands to the snapshot button right-click menu. Snapshot defaults are saved in the Podium.ini setup file. New arrangements will automatically be set up with the zoom snapshot defaults, including the initial timeline and vertical zoom range.
• The default Podium setup is modified to include a set of six default zoom snapshots for horizontal and vertical zooming.
• Fix: Zoom snapshots were not copied when creating copies of an arrangement.
Furthermore, the snapshot options are now saved in the .pod project file. I removed the restriction of creating duplicate snapshots. I did not yet remove the zoom restore feature when re-clicking a snapshot button, but instead I changed it so that it should only restore the settings affected by the snapshot. Let me know if this still results in confusing behaviour, in which case I’ll remove the restore feature completely.