I’m surprised renaming Podium.ini didn’t work. If there is no Podium.ini file when Podium starts up it won’t initialize any drivers so updating your drivers should not solve this problem.
Please try the following: Open the Windows Task Manager, start Podium, and watch the Task Manager apps list for the Zynewave Podium app. Does it disappear from the list after the logo splash screen disappears?
Was the Podium.ini file recreated when you tried to start Podium again? If so, please email it to me.
Have you updated your graphics card driver recently?
You can time stretch MIDI sequences, but audio time-stretching is not supported yet in Podium.
With the project open in Podium, open the browser file panel, right-click the address bar and select ‘Go To Project Folder’. The file list now shows the contents of the project folder. There are pin icons at the left side next to each file that is still used in the project. You can then right-click sound files that are not pinned and use the ‘Delete’ command. Be careful though, because it is possible that you may have other projects that reference these unpinned files.
Most common reason for this behavior is that either the audio or MIDI drivers crashes when Podium tries to access them. Did you change your interfaces or update their drivers recently?
You can bypass the driver initialization by temporarily renaming the Podium.ini file, so that Podium will start out without drivers configured. Enter the following line in a Windows Explorer address bar:
%appdata%\Zynewave\Podium
Rename the Podium.ini to something like Podium.bak and then try to start Podium again.
Can you provide more details about what kind of files you are referring to?
I’m close to releasing version 3.3. You can read more about it here:
This is a major release so it has taken quite a while to finish. After the 3.3 release follows more frequent releases with minor updates.
3.3.0 beta 4 is now available, which has a fix for this.
Beta4 is up. In this beta I believe I have solved all the problems with copying stuff between two open projects, both when dragging and when using copy/paste. In addition to other minor bug fixes, the start page now remembers if an arrangement is open on the project pages and will reopen those on next startup.
I will now go back to completing the missing parts of the inline help, and then the 3.3.0 release should be ready. If you find any bugs, please let me know.
Rebuilding, Updating or Loading Plugin Setup from Template, yields an empty Device List, until you navigate away from the Project Page, and back again.
Fixed in the new beta4. Thanks.
i still have the issue whereby a crash in Podium x64 (Win10 x64) doesn’t release ASIO driver. i have to physically unplug, or power down – then power up my external soundcard (Roland TriCapture). Switching Audio driver in the Setup isn’t sufficient.
What causes the crash?
I have another (slightly off topic) feature suggestion for 3.3. Would it be possible to add an option for colour coding the track markers? i.e. verses are red, choruses are blue (I know I know there’s a song in there somewhere 😉), bridge yellow etc.
This would be immensely helpful when recording at a distance from the computer screen. I think that even if I had a young person’s eyes I would still struggle to read the markers from half way across the room, & it’s probably simple enough to code without taking time away from the main features of the update.
Your feature request is noted. This requires an update to the Podium file format to be able to store a color property for marker events, so I’d like to postpone it for an update with other additions to the Podium file format.
You mentioned working on copying tracks and such from project to project – have you considered being able to drag and drop the same? As in dragging, say, an object by hovering the object over the target tab which opens it.
Good suggestion, 4mica. The previous Podium versions allowed you to drop objects on the tabs for moving objects into that object folder, but that no longer makes sense with the new single page per project. I’ve changed it so that dragging over a project tab will open that page.
I’m about to start patching the drag-drop and copy-paste code so that it handles moving from one project to another project. There are a lot of tricky situations to take care of, like when you drag a plugin onto a track in another project, it will possibly need to copy over all the device objects that define that plugin if the plugin is not already imported in that project.
You can’t download older installers after your upgrade period expires, but I can email the 3.2.4 installer to you if you send me an email with some kind of verification of your identity; either the purchase ID from the purchase receipt email or write the approximate date of your original purchase.
I’ve just installed the Synthmaster 2.9.6 demo and I get the crash when I try to open the plugin editor. I noticed that the demo version actually doesn’t open the editor window immediately, but first displays a “When you try our demo version…” message box. This delayed creation of the plugin editor window is the reason the crash occurs. I would guess that the full version does not have this problem.
Edit: I’ve now added a double-check in the Podium code so that the Synthmaster demo doesn’t crash. Fix will be available from Podium 3.3.0 beta4 and onwards.
I noticed in your screenshot that you are running the 3.2.5 beta2. Is that the latest version you had access to? I can’t remember if there were crash issues with this particular beta, but generally I wouldn’t recommend using beta versions for production work. If possible, try to revert to the 3.2.4 release version and let me know if you still get crashes.
Hmm, I’ll need to spend some time investigating this. The code for the latency compensation is quite complex, so if you don’t mind I’d like to finish 3.3 first and then look into the problem for a subsequent minor release.
Thanks for reporting the problem.
