ZynewaveI 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
ZynewaveHi Jean-Marc,
Many good suggestions. I have copied it to my list and will work my way through them.
ZynewaveHi 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
ZynewaveHi 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.
ZynewaveHi comp,
Martin is right. An old-style tracker interface is not going to be implemented in Podium.
Frits
ZynewaveZynewaveI have added ‘MIDI key transpose setting in track properties’ to the future plan.
ZynewaveI’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
ZynewaveHi 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
ZynewaveI 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
ZynewaveRemember to turn the gain on track 1 down to ‘off’. Otherwise both the dry drums and compressed drums will be mixed. If your track 2 with the bass is only intended for controlling the side chain pumping, you should turn the gain on this track to off as well.
I briefly tried this setup (this time I actually listened to the plugin output) and it seemed to work as intended. I had a problem when enabling the ‘listen’ button, which produced a distorted output of the sidechain input. I assume this is an issue with the plugin though.
ZynewaveGo into the about page in the plugin (press the ?). Enable “ext. sidechain”. The plugin notifies you that it has changed its input configuration and that it needs to be reloaded. You need to remove the crunchessor plugin mappings in your project, and reimport the plugin. Then you will have 1 output mapping and 2 input mappings. My guess is that the second input mapping is the sidechain input.
ZynewaveSo, when entering notes in the pianoroll or the drumeditor the velocity defaults to 64. Is there a way to change the default value?
Not currently. But I was going to change the behaviour to this: First note you enter in a sequence will be at 64. You change the velocity of the note, leave it selected, and click with the pencil tool to draw a new note which will take its velocity from the previously selected note. Good solution?
While in the drumeditor, could we have a way to re-arrange the drummap to the left?
You can change the order of the drum lanes by dragging the drum key preset objects around, but you’ll have to do it with the browser or a list window. If popular opinion would rather have the default order of the drum kit keys in reverse order, I can easily change this. I originally made the low keys at the top of the list, because this is typically how drum kits are listed in the data-lists that accompany drummachines/workstations. So if anyone prefers the present ordering, now is the time to speak up ❗ or else I will change it for the next release.
I’ll add the scrub tool to the plan.
ZynewaveZynewave