Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 5,952 total)
  • in reply to: Podium refuses to run ? #42743
    Zynewave
    Keymaster

    Thanks for the dmp file. The crash happens when Podium tries to access the “WaveformImageCache.db” file that should be located in your “Projects root folder” (as specified in Preferences).

    I will fix Podium so that it doesn’t crash when the db access fails, but from the dmp file I cannot see what the specific error is. Could you check that your WaveformImageCache.db is not set as read-only and that it is not blocked by your firewall?

    If you can’t find any issues with the WaveformImageCache.db file you could try to delete it. Podium should then regenerate all the waveform images when it starts up.

    in reply to: Podium refuses to run ? #42724
    Zynewave
    Keymaster

    Please send me the dmp file to my email: info at zynewave.com

    in reply to: Podium refuses to run ? #42722
    Zynewave
    Keymaster

    I thought this sounded familiar. A forum search revealed another topic that deals with the same issue. Perhaps the recommendations at the end of the topic regarding Windows Defender can help you:

    Podium won't open

    in reply to: Podium refuses to run ? #42714
    Zynewave
    Keymaster

    Hi. Are there any error messages shown when you try to run Podium? What Windows version are you using and what Podium version are you using?

    If the Podium window doesn’t appear at all, then it could be caused by a hanging audio or MIDI driver. If you open your “Documents/Zynewave Podium” folder you should see a Podium.ini file. Try renaming that to Podium.bak and then try to open Podium.

    Zynewave
    Keymaster

    Hi Nick. You can access all the objects within a project via the Object Browser panel in the Browser page/window.

    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: Scanning of plugins is terrible #42603
    Zynewave
    Keymaster

    Hi Luc,

    If you are using Podium Free, then there have been updates to the full version since then that improves the scan/import. I just tried scanning my x64 plugin folder from Podium 3.4.2 x86, and the import dialog shows a counter status message “Skipped x files that are not x86 compatible” without requiring restart. I do recommend though that x86 and x64 plugins are kept in separate directory trees.

    Please note that Linux is not officially supported by Podium. I have no experience with Linux so I can’t test or comment on anything related to Linux. Current Podium version 3.4 can run on Windows XP even though minimum officially supported OS is Windows 7. Microsoft has ceased support of building for Windows XP in their latest Visual Studio developer tool, so to be able to take advantage of future dev tool improvements I will need to upgrade the dev tools and abandon XP support. This may mean that the future Podium version 3.5 will not run on Linux.

    in reply to: Preview 3.4: Codebase rewrite #42541
    Zynewave
    Keymaster

    Hi Andy. I’ve just uploaded the demo version of the latest 3.4.1 release. The download link is on the Podium product page. If you want to do more extensive stability testing then send me a mail and I can give you access to the latest full version. If you find stability issues with Podium I would like to get them fixed.

    in reply to: Preview 3.4: Codebase rewrite #42291
    Zynewave
    Keymaster

    Major version upgrades are traditionally being developed on an independent branch, separate from the work being done on minor feature and bug-fix updates to the current major version. Podium development is all done on one branch/timeline, and my aim is to implement and release feature updates gradually. So the major.minor.revision version numbering is somewhat misleading for Podium. I’ve been considering adopting the date based versioning scheme (“21.9”, “21.9.1”, “22.2” etc.).

    in reply to: Preview 3.4: Codebase rewrite #42263
    Zynewave
    Keymaster

    I plan to increase the frequency of Podium releases in 2022. Your Podium license is still valid after the upgrade period expires. There is a small discount if you renew the upgrade period before it expires, but you can renew it any time in the future when there are new Podium features that you may find useful.

    in reply to: Version 3.4 – Plugin database will not load to project #42074
    Zynewave
    Keymaster

    Hi dagabond. Each project still has its own plugin database embedded in the project file. The plugin database project was introduced in a Podium update with the intention of making it simpler to update your projects with changes to your plugin installations. Your description is the correct way to go about updating plugin setups in your projects.

    in reply to: Preview 3.4: Codebase rewrite #41967
    Zynewave
    Keymaster

    Final Podium 3.4.0 is now released.

    in reply to: Preview 3.4: Codebase rewrite #41942
    Zynewave
    Keymaster

    Beta3 is up. It fixes some bugs with the project and track templates which were not working properly. This version also contains a revision of the edit history undo/redo descriptions which now contain more detail. The edit texts have also all been made translatable.

    The message I get from Nuance is “Set Audio Properties”. I should add that I’ve been using Nuance in Podium for years without any problem. This recent bug followed an update from New Sonic Arts. There has also been a graphical glitch with their Granite software. So I guess they have made changes that are somehow incompatible.

    That error is unfortunately not related to the error I encountered with Nuance v2.125, so even if I create a workaround for the Nuance problem I found it is unlikely to fix all issues with this Nuance version. I’m also not happy about changing the way Podium gets preset bank data from plugins, as this may cause other plugins to start malfunctioning. I’m hoping there will be a Nuance update that fixes these issues.

    in reply to: Preview 3.4: Codebase rewrite #41835
    Zynewave
    Keymaster

    Thanks for testing. I tried the Nuance v2 demo version and I did experience a plugin crash though I am not sure if it is the same as you encountered. The Nuance plugin crashes when Podium tries to get the Nuance preset bank data from another thread than the main UI thread. I can provoke this crash by deactivating the power button in the arrangement editor with Nuance loaded on a track. This is the first plugin I’ve encountered that has this problem. To fix this I will have to move the preset sync into the main UI thread, which unfortunately means the UI can be blocked for a noticeable time depending on the number of plugins loaded. Before I make that change, I would appreciate if you can confirm if this is the bug you also see. I’ve uploaded a new beta2 in which I’ve added more details to the crash notification. Check if the message says something like: (Nuance.dll – GetBankPreset).

Viewing 15 posts - 16 through 30 (of 5,952 total)
© 2021 Zynewave