ZynewaveIf you have experimented with the dialogs for customizing the editors, the mixer profile may have gone. Try using the ‘Setup > Restore Default Editor Profiles’ menu. The profile buttons should be located just above the transport button, as shown in the various screenshots here:
ZynewaveHi Russil,
Sorry to hear that. I assume you’ve looked at the getting started section of the guide, and perhaps watched some of the videos. Can you pinpoint where it is you’re having trouble?
Frits
ZynewaveI agree. I’m compensating all existing customers with an extra year of free upgrades once the next Podium update is ready. I’ve posted in the VIP lounge why development has been slow lately.
ZynewaveZynewaveZynewaveI gave answers in another topic, which I think applies here as well:
http://zynewave.com/topic/bad-performace-with-enabled-plugin-multiprocessing/
ZynewaveIf you restart Podium, and it doesn’t show the error, then it should be configured ok. I just checked the ASIO4ALL website, and there is a new 2.12 released a few days ago.
ZynewaveIt sounds like your editor profiles may have been corrupted. Unless you have made editor customizations that you don’t want to redo, you can use the ‘Setup > Restore Default Editor Profiles’ menu.
ZynewaveDo you have a Podium project file you can send me that produces this crash? Preferably a project file that uses only freeware plugins, so I can test it under the same circumstances.
ZynewaveIt won’t affect the current ASIO support in Podium. It will just be an alternative driver you can select in the Interfaces dialog.
ZynewaveYou could create a new sub-master group track under the master, move all your regular tracks into this group, and move the master effects to this new group track. Thus, you will only have the sub-master and Track 8 feeding directly into the non-effects Master track.
ZynewaveWith all the recent reports about ASIO driver problems, I’m thinking I should put a higher priority on implementing WASAPI driver support, and remove the old WAVE driver support.
ZynewaveSorry for the delay. I’ve been busy with another job, and I’m just starting to catch up with some of the unanswered posts.
ZynewavePodium uses the standard Windows GPI for graphics, and it doesn’t distinguish between what kind of video card/driver is in use. Podium does request a few smaller bitmaps be stored in video ram for increased performance. Perhaps you can increase the amount of available onboard Video RAM in the BIOS?
Another potential issue with the onboard video card is that it probably supports fewer hardware acceleration features than your discrete video card. So some graphics operations may be partly performed by the main CPU, which could cause the occasional sound dropouts.
Zynewave3-6 is an average CPU usage percentage, which is not a lot. If the CPU indicator is showing red overload, it means that occasionally the ASIO buffer could not be filled in time, causing dropouts in the sound. This can happen due to plugins that occasionally perform some heavy initialization, perhaps as a result of preset or parameter changes. It could also be other programs/drivers on your Windows PC that blocks the CPU for a brief period. Some network drivers have been known to cause these issues, although that was years ago I last heard such reports.
Could you try to increase the ASIO buffer size to see if this reduces the occurrences of overload?