Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterBeta6 is up. In continuation of the crash dump support added in beta5, I ended up doing a major revision of the Zynewave Podium documents folder structure.
The Podium installer no longer creates an AppData folder for the Podium.ini file and the Color Setup and Note Map folders. Instead all setup and project files are now stored within the ‘Zynewave Podium’ subfolder in your Documents folder. The Podium.ini file will by default be saved in the main Zynewave Podium folder. Existing Podium installations will continue to use the Podium.ini file saved in your AppData folder. If you want you can move the contents of your Zynewave/Podium AppData subfolder (use the ‘Explore Setup Folder’ setup menu command) to your Zynewave Podium documents folder. After that you can delete the Zynewave/Podium AppData subfolders. I recommend you wait with that until the final 3.3.0 version is released, since previous Podium versions will be confused if the AppData folder is missing.
During startup Podium will now check several locations for the Podium.ini file, including the current directory and the directory where the Podium.exe is run from. This makes it possible to run Podium from a portable drive. You just copy your Zynewave Podium documents folder onto a removable drive and then copy Podium.exe into that folder. This is made possible by the fact that Podium no longer requires that the setup files are stored in the AppData folder.
ZynewaveKeymasterThanks. It is possible that the crash is related to the default generated Podium documents folders. I’ve uploaded 3.3.0 beta5 in which I’ve added support for generation of crash dump files. With the new beta5 please try to reproduce the crash, and then look for a file named Podium3.3.0.dmp in the Podium setup folder. If you send this file to me, I’ll be able to jump right in to the source code where the crash occurred.
ZynewaveKeymasterBeta5 is up. Apart from further updates to the inline help, I’ve added support for generation of crash dump files. The crash file is named “Podium[version].dmp” and it is written to the Podium setup folder. If you experience a crash please attach this file in an email to me. With this file I will be able to pinpoint the exact location in the source code where the crash occurred.
ZynewaveKeymasterYou can send it to info at zynewave.com.
ZynewaveKeymasterI’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?
ZynewaveKeymasterYou can time stretch MIDI sequences, but audio time-stretching is not supported yet in Podium.
ZynewaveKeymasterWith 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.
ZynewaveKeymasterMost 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.
ZynewaveKeymasterCan you provide more details about what kind of files you are referring to?
ZynewaveKeymasterI’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.
ZynewaveKeymaster3.3.0 beta 4 is now available, which has a fix for this.
ZynewaveKeymasterBeta4 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.
ZynewaveKeymasterRebuilding, 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?
ZynewaveKeymasterI 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.
ZynewaveKeymasterYou 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.