Zynewave's Forum Page

You don’t need to create the MIDI parameters for each track. The MIDI parameters are created for the device, so they will be available on all tracks that use that device. If you save the track as a track template, the MIDI parameters you create are saved in the template as well. You can use that template in future projects, and not have to create the parameters again.

A while back I managed to compile a x64 version of Podium, but I have not had an opportunity to test and debug this on an x64 OS. I need to purchase a new PC with Windows 7 x64 before I can go further with this.

When Podium x64 is made available, it will only support x64 plugins. I don’t plan to implement my own 32/64 bit bridge system. For that purpose, you can use third-party plugins, such as:

http://jstuff.wordpress.com/jbridge/

@batman42ca wrote:

I think one solution to my problem might be to connect the output of my sound card to the input of my sound card. Podium could output on midi port 10 and record from the audio in. I was just hoping there was some internal way to do that.

That may be the only solution, if you want to record the audio output of the synthesis engine on your soundcard. Some soundcards expose an alternative “loopback” audio input that you can assign to an audio track. This audio input will then record the synthesis output before it goes to the physical audio output. My old Yamaha soundcard supported this. I don’t know if soundblaster cards support it.

Hi Mike,

I agree that the Podium guide is written more as a reference guide than an introduction for newbies. Writing it as a reference is the quickest way for me to document features, so that at least I’m not the only one in the world that are aware of how to use certain features. If you want to change something in the Podium guide, you can do that on the wiki site. The Podium pdf guide is printed from the wiki pages. If you have suggestions for major changes or additional chapters, I suggest you post your ideas on the forum first for discussion.

Frits

Well, I agree this may be confusing. Podium tries to make the intelligent decision, that the input selector should be hidden from all tracks in the bus return section, since having an input assigned in the return section is useful only in rare cases. When you assign a child track as a bus return, the entire group under the master track will become part of the bus return section. Perhaps it would be less confusing if the input selector always remain visible?

@pj geerlings wrote:

What features will be delivered next?

The development path some times twist and turn in mysterious ways. Mostly it is prompted by discussions on this forum. I’m happy to follow these byroads, as long as I feel it leads in the same overall direction. I’ve previously made predictions or promises for what new features I’m going to work on next, only to find that the development focus shifts to something else. It pains me that I always have to disappoint some users, so I no longer make any promises as to what lies beyond the next version. All I can say is that on the surface, 2.40 will be a minor bug fix version. Under the hood, 2.40 has a lot of code “housecleaning” that I needed to do in preparation for things to come.

@duncanparsons wrote:

Because I always have a number of projects on the go, I don’t update my main machine terribly often, only when there’s something I NEED. So I’ve been running v1.80. I’ve updated and now running 2.38 (for some reason 2.39 wouldn’t download).

1.80 is almost 4 years old :shock:. A lot of things have happened since then. I’d prefer not to backtrack my code changes for 4 years, to try to determine which update may have changed this behaviour.

I just tried downloading 2.39 and had no problems. Maybe just try again?

Does it show the error dialog also when using ASIO4ALL and Wave drivers?