ZynewaveI’ve detected what the problem is, and I have sent an email to Blue Cat.
ZynewaveHrmpf, I found a bug in the new mixer code 🙁 . Podium will crash if you delete all tracks in the arrangement. I’ll release a bug fix version in a few days. Let me know quickly if you find other problems.
Zynewavea) Add a second relative path option to the Device mapping properties area?
I don’t want to complicate the mapping configuration more than needed.
Regarding the distinction between VST effect and instrument plugins: Some hosts (older Cubase version comes to mind) require that a plugin is classified as an effect, or else it will not be available in some of the UI menus. That’s why you see some instrument plugins come as two .dll versions, one compiled as an instrument and the other as an effect. There is none such UI restriction in Podium.
ZynewaveHi,
You add tempo and time signature changes by inserting events on the lane above the tracks timeline:
http://www.zynewave.com/wiki/doku.php?id=guide:arrangement#time_signature_tempo
ZynewaveWhen you use the “Import file” command, Podium will log the last folder you browse to, and use that the next time you use the import command. The path is stored in the setup file.
As for the two VST paths; I may add this later on. However I do think it’s less important for Podium than for other hosts, because of the way that you can import plugins from user specified folders. Setting up two paths for VST plugins also poses a problem with the “relative path” option for the plugin filename in the mapping properties. Podium would not know which of the two VST folders it should use to search for the plugins.
ZynewaveOpen the list panel with the “List” button at the top right corner (or open a List window with Ctrl+L). Resize the panel so you reveal the file list. From this you can browse for your wave files and then drag them onto the tracks.
Zynewave@Jaegerteam wrote:
The VST-plugin should process MIDI only, not audio.
It should be one of those which “read and write” MIDI data.
Ok, this is on the plan. Currently you cannot use MIDI-only VST plugins.
ZynewaveZynewaveZynewaveI don’t understand. Could you describe what you want to do in more detail?
ZynewaveI reinstalled Podium CM1.77, and found this packagecode with regedit:
08926EA848E5E1E4CB7D8207C781309F
After uninstalling Podium, this code were no longer found with regedit. Try searching for this code.
ZynewaveThe messages you mention is displayed by the Microsoft installer utility that the Podium installer uses.
i have PodiumCM177 through CM Magazine, i installed it, played with it then uninstalled it (did that about twice)
How did you uninstall Podium?
Have you deleted any Podium files manually with the file explorer?
Have you done any system restore or cleanup using regedit?
Have you ever installed other Podium versions than the CM1.77?
I have had this kind of problem reported once before. Have a look at this topic and see if it is similar to your problem:
ZynewaveZynewave@duncanparsons wrote:
@wanyze wrote:
I did some Orchestral stuff in the past using Cubase, which use alot of midi parameter automation to make it sound alive. Despite the fact that there are alot of midi controllers missing in Podium which cannot be automated (which should come soon), I find it quite time consuming to work with alot of midi automation data in Podium.
most of these can be added as parameters – there is full support for CC, RPN, NRPN, etc… which controllers are you missing?
DSP
I think wanyze refers to a reply I made recently, about making it easier to create new MIDI parameter objects directly from the inspector parameter panel. Just now I’m working on adding a menu button to the parameter panel, with a “New MIDI Parameter” submenu listing all MIDI parameters not already created. If you have a synth that e.g. supports sustain pedal (CC64), you just select it from the menu to create the parameter object for the device.
Zynewave