Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterOk, I answered too quickly. I got your revised project file now.
The problem with the last track where you have the level parameter assigned, is that the track is audio enabled. That means the level automation adjusts the gain on the level track itself (and any tracks that would have been below the level track), and the level on the parent track is not affected. Just remove the ‘enable audio mixing’ option for the level automation track.
ZynewaveKeymasterGot your project. I could not find any automation tracks in your ‘template’ arrangement. Here’s a procedure to set up a level automation track:
Select the track you want to automate, e.g. the ‘Drums’ group track. Open the ‘Param’ panel in the inspector. Click the ‘Mixer’ button. Double-click the ‘Level’ parameter. You should now have a new track with the level parameter assigned, and a strip in the mixer with a slider. Moving the slider will create a curve sequence on the track. You can also use the pencil tool to create curve sequences on the track.
ZynewaveKeymasterI’ll check it out.
ZynewaveKeymasterNoted.
ZynewaveKeymastercan u tell me when the next update will be available and how it’s going on with the manual?
The next update will only contain minor improvements/fixes and it will be released within a week. The last couple of weeks I have been doing some research that will be put to use in a later release. So the manual has been on hold for a while. I’ll get back to it soon.
ZynewaveKeymasterI assume you have created a track with the ‘level’ parameter assigned, and created a curve sequence on the track. This track must be placed as a child track under the track you want to automate. Automation will search upwards in the track hierarchy until finding a track that can use the automation data. Note that if your track with the audio file has no plugins assigned, then you need to select the ‘enable audio’ option in the track properties, to make the track a mix point. Otherwise the level automation will continue further up the hierarchy.
If this does not make any sense, you could email me your project file, and I can then tell you where the problem is.
Frits
ZynewaveKeymasterHi Jean-Marc,
Many good suggestions. I have copied it to my list and will work my way through them.
ZynewaveKeymasterHi antem,
What i meant with ‘process gain’ is the option to add or remove db’s(volume) to/from a waveform(or part of it) in the sound editor
That’s a good suggestion. I was thinking of creating a dialog box that would allow you to set up a gain change value, and optional fade in and fade out times. I’ll add it to the plan.
Thanks for the help Martin. I don’t have further knowhow about recording into eXT or Fruityloops. But if you can use your MIDI keyboard to play the Fruityloops synths through a track in Podium, and if you can get the Fruityloops sequencer to sync with Podium playback, then it should be possible to make the Fruityloops plugin record the received notes into its own sequencer.
Frits
ZynewaveKeymasterHi Eli, good to hear from you again.
If you are recording separate sessions, I would suggest having separate record prepared arrangements for each session. When finishing recording one session, press stop, press backspace (to get back to the project page), press arrow down (to get to next arrangement), press enter and space to start recording in the new arrangement.
If for some reason you prefer to have all sessions in the same arrangement, you can use the punch in to make the clean cut. The recording extends the audio events in chunks, so after stopping a recording, press ‘W’ to step the cursor to the end of the arrangement. Press shift+I to set the punch in location. Starting recording again should then create a new set of events at the punch in location. I say ‘should’ because that is the way it was supposed to work. I tried it yesterday and found that Podium still extended the previous events, even though punch in was set. I have fixed this and it will be available in release 1.31.
ZynewaveKeymasterHi comp,
Martin is right. An old-style tracker interface is not going to be implemented in Podium.
Frits
May 9, 2005 at 07:58 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterI have added ‘MIDI key transpose setting in track properties’ to the future plan.
ZynewaveKeymasterI’m assuming you want the pitch shift to be performed on audio and not MIDI notes. To pitch shift audio I will have to implement a pitch shifting DSP algorithm. Good quality pitch shift/time stretch algos are not easy to make, and I would probably try to license one of the existing algos instead of trying to implement it myself. It will be a while before this will happen though.
The ‘reverse’ mode of an audio event is something I intend to make at some point, but again I cannot promise when it will arrive.
Frits
ZynewaveKeymasterHi ravasb,
I have never had the chance to try Stylus RMX, so I don’t know how well it works with Podium. Perhaps another Podium user could post about his experience with the Stylus RMX?
Frits
ZynewaveKeymasterI kind of spent an hour because, when I changed my mind about the background color, It changed another parameter’s color (the next one actually), and so on.
Is this a known one ?
I am not aware of any bugs with the colors.
Do you need me to be more specific ?
Yes please. What do you mean with ‘another parameter’s color’?
Ow, by the way, it’ll be cool if you told us where is this registry line that remembers all this color customization – or make a little “save as” button….
This is explained in the setup section in the guide.
Frits