ZynewaveSearch for these strings in your registry:
CDE9BBF42A5CA67498F7485D9893DEC3
4FBB9EDC-C5A2-476A-897F-84D58939ED3C
78C7CFC92127A4F4F9F132D7C313C4B2
These are unique identifiers created by the installer tool for Podium 1.64. When I search for them with Podium 1.64 installed, I get the keys listed below. When I search after uninstalling Podium, there are no occurrences of the three unique identifiers.
HKEY_CLASSES_ROOTInstallerFeaturesCDE9BBF42A5CA67498F7485D9893DEC3
HKEY_CLASSES_ROOTInstallerProductsCDE9BBF42A5CA67498F7485D9893DEC3
HKEY_CLASSES_ROOTInstallerUpgradeCodes78C7CFC92127A4F4F9F132D7C313C4B2
HKEY_LOCAL_MACHINESOFTWAREClassesInstallerFeaturesCDE9BBF42A5CA67498F7485D9893DEC3
HKEY_LOCAL_MACHINESOFTWAREClassesInstallerProductsCDE9BBF42A5CA67498F7485D9893DEC3
HKEY_LOCAL_MACHINESOFTWAREClassesInstallerUpgradeCodes78C7CFC92127A4F4F9F132D7C313C4B2
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUpgradeCodes78C7CFC92127A4F4F9F132D7C313C4B2
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserDataS-1-5-18Components … a bunch of entries
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserDataS-1-5-18ProductsCDE9BBF42A5CA67498F7485D9893DEC3
HKEY_CLASSES_ROOTpod.DocumentDefaultIcon
HKEY_LOCAL_MACHINESOFTWAREClassespod.DocumentDefaultIcon
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerFolders … C:WINDOWSInstaller{4FBB9EDC-C5A2-476A-897F-84D58939ED3C}
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall{4FBB9EDC-C5A2-476A-897F-84D58939ED3C}
ZynewaveIf I used this util, what should I look for?
I believe the utility presents a list of all problems it detected, before doing anything to the registry. If you see anything in this list with ‘installer’ or ‘upgrade’ in the name followed by a cryptic hex string, then that could be it.
It’s 4:30 AM here, eyes are getting heavy, so support is offline for the next 7 hours.
ZynewaveI’m not using a reg cleaner-I’m not going to buy one just so that I can install one application that won’t install. I don’t trust them because they often make assumptions about what to do with reg. entries that they find. The net result being that often your system can get fubar’d and screwed up worse than if you had’nt used it.
A quick search revealed at least one freeware alternative:
http://www.snapfiles.com/reviews/eusing-free-registry-cleaner/eusingregistry.html
As I said, I don’t have any experience with these types of programs, and like you I would not feel safe using one. But I would think it is more safe than removing keys manually with regedit.
The problem can lie with the installer utility I’m using. I was considering upgrading to a more common tool, like Installshield, but that costs several hundred dollars. This is the first time I have heard of problems with the Podium installer.
ZynewaveThis is weird, in 17 years of using computers I have never had this happen. The software won’t install, there is no trace of Podium or Zynewave in the registry and there are no related files in the C: drive locations that you specified previously.
I haver never experienced anything like this either.
The installer tool I’m using is very basic, and only requires inputting a few file references and setting options. There is no real programming involved. It relies on the Microsoft Installer service which automates most of the installation logging in Windows.
You say you have removed all occurrences of Podium and Zynewave in the registry, but it can go a bit deeper than this. When I check my registry I see e.g. a PackageCode attribute in the Podium products group. The value of this PackageCode is present in e.g. …InstallerFeatures… and …InstallerUpgradeCodes… where there is no reference to neither Zynewave or Podium. It is possible that if these entries remains it will mess up a reinstall, although I’m surprised if this is the case.
Otherwise I’m running out of ideas. Perhaps it is a good idea to use a registry cleaner utility. I don’t have any experiences with these though.
Or you could reinstall Windows 😯
ZynewaveTry running the installer for the Podium version that was on your system before 1.64. If it detects ‘itself’ on the system it should present you with two options; ‘repair’ or ‘remove’.
ZynewaveAs I have previously described, after several minutes of playback and editing Podium becomes to be far less responsive and Windows too.
Making a window coming in the first plan or moving a plugin Gui can take several seconds to process and if it is done while Podium is playing it can result to red spikes in the file indicator and big drop outs.
This is most likely due to Windows swapping memory to the cache file. Podium attempts to buffer streamed sound files in memory and uses up to a certain percentage of available physical memory. It starts freeing the memory buffers if available free memory grows smaller (loading plugins etc.) That way Podium don’t have to reload the files from disk when you are looping a small section or if you have few sound files that all fit in available memory. I apparently need to fine-tune this memory buffer system.
Perhaps is there something with the poor graphic cards ?
No.
Zynewave(new hard drive)
So this is a new Windows installation? Meaning that Podium was absolutely not on the system prior to the first installation that failed? Which Windows version?
Try installing when logged in as administrator.
Before installing, check that the “C:Program filesZynewave” folder is deleted, and that the “C:Documents and Settings[user]Application DataZynewave” folder is deleted (back up the Podium.ini setup file if you have customized Podium).
ZynewaveError message: ‘The older version of Zynewave Podium 1.64 cannot be removed. ‘
1.64? So you had installed 1.64 once, uninstalled, and then couldn’t reinstall?
If you look at the ‘add/remove programs’ control panel, is Zynewave Podium listed at the bottom?
ZynewaveAre you thinking along the lines of offline solutions or realtime solutions like Ableton Live?
I hope I can make it realtime. So you have the option to resize sound events to time-stretch instead of adjusting the sound length.
As for time stretching algos, Zplane may be what you are looking for…
I already have contacted Zplane to inquire about their licensing fees. At present time the price is too high for me. I’ll probably try to implement time-stretching using commonly available techniques, and then consider upgrading this in the future.
ZynewaveJust tried 1.64 and…
Thanks for testing. I’m glad weeks of meticulous optimizations resulted in a noticeable improvement.
Zynewave@darcyb62 wrote:
@Zynewave wrote:
So do you want to be able to switch the samplerate of the arrangement between e.g. 96 and 48, when recording final bounces, versus when just working with the arrangement?
This is going back but is this doable?
No. I need to implement sample rate conversion & time stretching before this would make any sense. Otherwise your 48 kHz sound files would play at twice the speed when rendered at 96 kHz.
Over the last couple of weeks I have looked at various time stretching solutions. I feel tempted to start work on this, but I need to do more research.
ZynewaveCare to share what exactly you did here? Or is that a trade secret?
Just boring stuff :wink:. Lot’s of small adjustments using a profiler tool to pinpoint the places that used most CPU time.
ZynewaveZynewave@darthstephen wrote:
is there any sort of crash report i can send you?
No.
I have just emailed manytone, asking if he would be interested in swapping a manystation NFR license for a Podium license.
ZynewaveAny chance to see this in 1.64?
Short answer: no