Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterHi polysix,
Was Podium 1.74 the first time you installed Podium? If you have tried previous versions, did they work ok?
Does it always crash immediately when you start it, or have you had a chance to configure the MIDI/audio interfaces in Podium?
Try deleting the Podium.ini file before starting Podium. The file should be located here:
C:Documents and Settings[your user name]Application DataZynewavePodiumPodium.iniFrits
ZynewaveKeymasterI’m glad you got it working. Although I’m surprised it didn’t work for you with the project file you emailed me. I tried setting up a similar arrangement with my GPO installation, and playback of sustain parameter events were ok. It is a valid way to automate parameters with individual parameter events, but when you have more than a handful of them on a track (as you did) it makes more sense to use curve sequence automation instead.
ZynewaveKeymasterWhen you play the instrument without recording, does your sustain pedal have an effect on the sound, i.e is the CC#64 getting through to the plugin?
Do you have the same problems with recording other MIDI parameters like modulation, pitch bend? (perhaps not relevant with a piano patch).
ZynewaveKeymasterGot the file. I see that you have recorded the sustain as a series of parameter events. Try enabling the “record as curve sequence on separate track” option in the parameter properties dialog, delete the existing sustain parameter track and redo the recording. Let me know if you can get sustain to work this way.
ZynewaveKeymasterEmail me your project file and I’ll check if your parameter setup is correct.
ZynewaveKeymasterHi Mark,
if I want to keep multiple takes and then mix and match later, can I do that without just making tons of tracks?
I assume that you are referring to the fact that loop-recording creates a new track for each loop. There is no other way to make the multiple takes appear as one track. You can collapse the track group with the multiple takes if the problem is that the tracks take up too much space in the editor.
Frits
January 5, 2007 at 00:23 in reply to: Let’s teach the world about Zynewave and Podium on Wikipedia #8572
ZynewaveKeymasterI see there is a “speedy deletion” notice on the page now, claiming that it is advertising. I better not get involved in editing the wiki. I would not want to get the reputation that Babya enjoys on kvr 😆
January 4, 2007 at 20:55 in reply to: Let’s teach the world about Zynewave and Podium on Wikipedia #8568
ZynewaveKeymasterNice, did you create the entry?
I can confirm that the so far single line of information is correct. 😆
ZynewaveKeymasterthat is why I suggested to put the fader in the middle of the two level indicators… How about that?
Hmm, I think that will place the left and right channel meters too far apart. And what then with mono and surround meters?
ZynewaveKeymasterIt seems you misunderstood me. To try to make it clearer, here’s a screenshot of a track configured both for level automation and audio mixing (which is a setup that I’m not recommending because it is of little practical use):

The fader requires more pixels than the width of the dB labels, even when the fader overlaps the labels. On top of that, one of my design criteria is that the level meters are centered on the strip, which results in some wasted space to the right of the meters.
January 4, 2007 at 18:52 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymasterIn your screen shot the Map: and Track: panels do not appear to reflect the contents of the currently selected track / that has focus. Although it is difficult to tell for sure just by looking at the screenshot, it does appear that way. Please confirm or deny
The raised track with the drop shadow is the currently selected track. Clicking on any of the track boxes (except the dials) will select that track, and all panels in the inspector will update accordingly. Clicking on a parent track will not remove the child tracks shown in the group panel, until you select a track from a different branch of the hierarchy.
ZynewaveKeymaster@swindus wrote:
Another thought: Would it be possible to add the vst parameter to the track panel in the inspector (like the zEQ and zReverb does) for the used effects on the selected track? So there is no need to open the vst gui at all to change a parameter.
I’m not sure I understand you correctly, but: If you enable the “use generic editor instead of plugin editor” option in the plugin mapping properties, the track panel will show an embedded generic editor with all VST parameters.
ZynewaveKeymasterI defintely want the faders next to the meters. As for the strips being to wide…I don’t understand why you said this.????
Try setting up a normal automation track with the mixer level parameter. Now “enable audio mixing” in the automation track properties. This will show you what I mean with wider. Btw. this possibility of assigning a track both for audio mixing and automation is not something I recommend. I may remove this feature at some point.
ZynewaveKeymasterThanks for the reminder 🙂
I also deleted:
# Assignment of the same MIDI input to several tracks, to allow control of layered synths.
