ZynewaveCrash. Within a second of the Demo limitations window starting.
Sounds like a bug. Please send me a copy of your “Podium.ini” file, found in:
C:Documents and Settings[user]Application DataZynewavePodium
That is, unless you have already used the “Load default setup” command.
ZynewaveHi Dayl,
But the problem is, when I un/reinstall, there it still starts with my preferences. How do I get a clean slate to start with again?
Use the “Load default setup” in the setup menu.
There have been a few reports recently on plugin crashes during scanning, so I think I’ll do something to improve the safety. The problem with the current plugin crash test is that it is only after the scanning is completed that it informs if there were any crashes. I’ll add a check after each plugin is scanned and if it crashed, the plugin will be added to a “PluginQuarantine.txt” file in the Podium application data folder, and a popup message will recommend you to restart Podium. The next time you do a scan, the offending plugins will be skipped, and eventually you should be able to complete the scan without crashes (and without having to uninstall plugins). I’ll implement this for the next version, and release a demo version of it. Hopefully sometime next week.
ZynewaveThis is one of the next things I’m going to work on. I’ve occasionally referred to it on the forum as SRC (sample rate conversion). Currently Podium does not behave as you’d expect if you use sounds with a different samplerate than the arrangement.
ZynewaveThat is too many options in my opinion. Being presented with a dialog with that many options/decisions would possibly discourage a lot of users. I think it makes sense to always adjust to zero crossing if not too far away from the detected transient point.
Zynewavethe audio event itself is cut some specified samples/ms _before_ that snap point. The region from the start of the new audio event (slice) to the snap point is applied a fade in curve. This is the was it’s done now, right?
Yes. I’ll consider adding zero-crossing alignment. Should both the fade-in start and the snap position be adjusted to nearest zero-crossing?
ZynewaveZynewaveZynewaveor, better namend Quantize Points
“Sync point” is perhaps a little ambiguous. How about “Snap point”?
Or creating a quantize pattern from the sliced material for quantizing other (Midi) sequences
I think that is what I refer to as “Groove templates”. It’s on the plan.
I’m not sure I follow your thoughts about the snap point behaviour in beat slicing. Let’s discuss this when I have implemented the feature and you’ve had a chance to try it out.
ZynewaveZynewaveI think we all agree here. I take care that each feature I add does not interfere with the workflow for people that have no need for that new feature. Time-stretching of sound events will be an optional feature, so the current arrangement editing behaviour will be the same. The support for time stretch will not have a negative impact on the performance if you are not using the time stretch feature.
ZynewaveZynewaveZynewaveIf I stick to my current rate of releasing, then V2 should arrive in about 8 months. Time-stretching should be implemented way before that. I doubt however that notation will be available in V2.
ZynewaveZynewaveThanks for the report Darcy. I’m curious to hear how well Podium performs emulated within OSX. I have not kept up with the OSX development in the last couple of years. Is “Parallels” something that is built into MacIntel OSX? It would be sweet if Podium could run “emulated” directly from a standard OSX installation.