ZynewaveHi Michael.
This is a confusing behavior that I have considered changing. What probably happens in your case is that when you use the segment cut/copy commands, the hidden sound events on the bounce tracks are also manipulated and can become fragmented. You can verify this by temporarily showing the master bounce track: In the track inspector rack, right-click the ‘Bounce’ button in the master section, and uncheck ‘Hide Track Lane’.
An alternative solution could be if Podium excluded the hidden bounced audio from any segment editing to avoid the fragmentation. The downside would then be that any segment editing will cause existing bounced audio to be out of sync with the edited segments.
Which of these two behaviors would you prefer?
A quick way to ‘clean up’ the fragmented bounce track is to disable the ‘Enable Offline Render Bouncing’ mode on the track, and then reenable it.
ZynewaveAnd 3.3.0 is now finally released:
In hindsight, I think I ended up including too many new features into this release. The Start page feature and the new translatable help system should have been two separate releases. The next releases will follow more frequently. Already started on 3.3.1.
ZynewaveHi Jeffrey. Can you describe in more detail how you are recording the guitar: Are you using a microphone or have you connected your guitar directly to your audio interface? When you say ‘reverb’ do you mean a reverb plugin you have inserted on the track?
ZynewaveI have uploaded a new beta6 which includes a revision to how Podium organizes the Zynewave Podium documents folder. The .dmp file will only be saved if you experience a crash, so let me know if you manage to reproduce the crash you experienced previously.
any project I try to load from the default location says “Could not save file ‘[project name].pod’ File is inaccessible.”
What is the path of the default location? Is it possible that the .pod file somehow has become read-only?
ZynewaveBeta6 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.
ZynewaveThanks. 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.
ZynewaveBeta5 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.
ZynewaveYou can send it to info at zynewave.com.
ZynewaveI’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?
ZynewaveYou can time stretch MIDI sequences, but audio time-stretching is not supported yet in Podium.
ZynewaveWith 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.
ZynewaveMost 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.
ZynewaveCan you provide more details about what kind of files you are referring to?
ZynewaveI’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.
Zynewave3.3.0 beta 4 is now available, which has a fix for this.