Zynewave@gamble wrote:
podium (2.10) crashes randomly at startup without a detailled windows message. it’s splashscreen -> new project dialog with demo reminder.
is that the specific “random crash” fixed in 2.12?
It could be. I’ve just uploaded the 2.12 demo version. Please give this a try, and let me know if you still get crashes.
ZynewaveZynewaveZynewaveI’ve uploaded an .exe beta 2.12. Could some of you that had the crash problem with 2.11 please try this beta and report if it works.
ZynewaveOOohh, bug now fixed 8)
I tried 2.11 on my netbook which has XP, and sure enough I got the crash.
After some experiments it turned out to be a timing related issue, and not related to XP/Vista. It was the popup of the splash screen which caused some code to run on unintialized data. This crash bug may well be the cause for the intermittent crashes reported by aMUSEd. For some reason the code changes in 2.12 caused this bug finally to appear on one of my machines.
I’ll release 2.12 later tonight.
Zynewave@aMUSEd wrote:
…though it keeps nagging me to resave my projects
Is that the “The ‘xxx’ project is using an older version of the Podium file format” message on project load, or the plugin crash message?
ZynewaveI have uploaded a “Podium211Exe.zip” with only the exe file and no installer. Please uninstall your previous 2.11, make a clean install of 2.10, and let me know if the Podium211.exe runs without crashing.
I’ll investigate the problem. So far I have not had any crashes on my Vista machine.
Are any of you that have the crash problem running Vista?
Are there any who have successfully installed and run 2.11?
Now, here’s something weird. I decided to reinstall 2.10. Usually I do not uninstall the previous version before installing the next (since it has worked before). This time, I did not uninstall 2.11, and installed 2.10 over the top.
The installer only automatically removes the previous installation if the version number increases. So if you want to go back to older versions, I recommend you uninstall the newer version first.
Finally, I noticed that the .msi installer is around 2mb bigger. May mean nothing, but am saying it just in case it’s relevant.
That’s the updated guide pdf file, which I have created with a higher quality setting for the graphics.
Zynewave@druid wrote:
I was using 2.10 this morning (in Aus land anyway!) and now I just installed 2.11 and it crashes on startup. Ouch! 😛
@podium.exe wrote:
AppName: podium.exe AppVer: 2.11.0.0 ModName: ntdll.dll
ModVer: 5.1.2600.5512 Offset: 0000100bI haven’t gone back to 2.10 to see if it will crash now too, but I doubt it, and I’m busy so I will try it later if this hasn’t been caught and fixed already.
Ouch. I don’t get any crash on my system. Does the main window appear before the crash?
Try deleting your Podium.ini file (make a backup of the file first), and see if this makes Podium start without crashing.
ZynewaveZynewaveDoes it also crash if you disable the plugin multiprocessing option in the Podium preferences?
I am not familiar with the Nebula plugins. Why are you using Nebula 2 Free instead of Nebula 3 Free?
ZynewaveThanks for the report and the project file.
This bug is now fixed for the upcoming 2.11 release.
ZynewaveThanks for the bug report and the project file.
The crash occurs in the curve editor, when the events on the track you delete are shown in the curve editor.
Bug is fixed in Podium 2.11, which probably will be released within a week.
ZynewaveAutomatic renaming of arrangement file folders is on my plan. It will require a bit of work, so I’m saving it for a future update of the whole project file management.
Zynewave@DanielK wrote:
Hello Zynewave,
Have you taken a look at the project file I sent you? 🙂
Daniel
Not yet. I want to wrap up the current feature I’m working on first.
Zynewave@Mike G wrote:
1 – Why can’t you bounce a group track? (I frequently divide by arrangements into 4 or 5 groups (Drums & Bass, Pads, Vocals, etc.) and I bounce the ones I am not working on at the moment.) It seems that I have to add an effect track (usually a zPEQ with no frequencies in use!) in order to get the tickbox on track properties that allows be to bounce. Or am I missing something?
Group tracks can be bounced just like normal tracks. Select the group track and press the B key shortcut, or use the bounce submenu.
2 – What’s the best way to add one group just before the Master? I sometimes put a limiter/compressor on Master but have to create a group track and move all sub tracks/groups up one at a time. I have also just added a limiter between the Master and MainOut but i’m not sure if that’s the best way to do it either.
How do other people do limiting on master track?
Are you working in expanded track layout mode and manually adjusting the group levels? This is all easily handled with the “insert effect track” and the “move effect track” submenus.
3 – If I ‘X’ (Bypass) a plug-in does it get unloaded? (This is what I do with the Master limiter during normal mixing)
No.
4 – What difference does “use as group track” make. I can see no difference with this ticked or not ticked.
Lots of small differences: You get the “new child track” command in the track menu. The track will be drawn using the “group track luminance” color setting. The track will have “(group)” appended in the inspector group panel group menus. The group track will appear in the “move to group” submenu for other tracks.