@xis23 wrote:
i would like an ‘open in external audio editor’ button….. .
Yes. 😉
The ideas for MP3 usage with Lame are worth a try as well I think. MP3 support in Podium of some sort would be nice.
@Podianer wrote:
Hi Frits,
I don’t know if you have already considered to improve this, but dragging and dropping of files from VSTi is a hazzle at the moment. Take the Universal UVI Player e.g. It is free. There you can drag and drop audio loops directly into the host. Or ezDrummer. It is not fun dragging the included Midi rhythms into Podium. Phrazor would utilize this too. There are a lot of popular VSTi that use drag ‘n drop. Please, do you have any idea, when we will be able to drag directly to a place on a certain track?
Max
Well…as a Stylus RMX user it really is a big deal for me. Being able to drag and drop from certain VSTi’s makes a huge difference. I think it has been brought up before. I guess Frits is juggling a few ideas for 1.77 already no doubt. When this feature does appear in Podium it is certainly something I will make use of straight away.
But “Siegried” remains way ahead at the top of all my FR’s. But yes drag and drop would be a great help especially since I use Stylus RMX. 🙂
@Podianer wrote:
Have you considered to make the cool looking faders of parameter tracks available for audio tracks? Perhaps with an option to keep the “old” dials?
Max
Absolutely. 8) Those parameter faders showcase Frits design skills in a big way. They really look great. To have those faders on audio tracks as well would be a very nice graphical touch for the mixer. 🙂
@Zynewave wrote:
This will conflict with the way bounce track works. If you disable the bounce feature of the track, then both the sound events on the bounce track and all the child tracks will play simultaneously.
The primary purpose of bounce tracks is to be able to create an exact rendering of the child tracks (hence the disabled fade properties) and then be able to switch back to the child tracks to make modifications and redo the render. If you want to use the rendered sound events as a regular clip, then the recommended procedure is to move it to a regular audio track.
Thats fine Frits. I just wanted to understand why and how it worked that way. But you have clarified that now, thanks! 😉
@Zynewave wrote:
This is on purpose. If it was possible to set gain or fades on bounce track events, it would mean that playback of the bounce recorded track would not be identical to the unbounced playback. So the fade properties of a sound event are disabled when placed on a bounce track.
Ok I see why you have done it this way but it might confuse new users. It certainly caught me out.
Perhaps some sort of option to allow bounce recorded events (on bounce enabled tracks), to have fades on them can be considered. 😉 While I can certainly work around it by
a.bouncing a midi event to audio then dragging that track to a new track (not bounce enabled)
OR
b. disabling track bouncing on the same track as the bounced track event (enabling the fades).
I thnk it would be a bit easier to understand if this behaviour was optional. The most logical place to first attempt a fade IMO is the track that an audio event (that had just been bounced to) resides. That would be a bounce enabled track.
As it stands right now I have to go to the track properties to disable bouncing on that track first (after bouncing to an audio event) to get fades working but I may very likely still want to bounce another midi event to the same track as audio.
Problem.
Because now I must go back to the track properties to re enable track bouncing which of course disables fades on the other already bounced audio event on the same track (which I would have moved further down the same track).
Unless it is a preference of yours in particular or it really will break something in Podium, please do consider either a global option or track option to Enable fades on bounce enabled tracks. 😉
I understand why you would want the playback of a bounced track to match that of the child track (with the unbounced events) but the actions I am talking about would be after the event has already been bounced.
I could easily hear from playing back / bouncing in real time that the bounced event is identical to the midi event for instance on a child track under it anyway. No problem there.
But having to then create another track and then drag the bounced event to that track making sure it is not also bounce enabled when creating it) is a step that does not seem necessary, unless it is a case of breaking something in Podium or causing issues elsewhere if it is made optional. ❓ ❓
How about an option maybe that automatically disables track bouncing after an event has been bounced on a bounce enabled track, this would then re – enable fades, crossfades e.t.c on that clip without the need to drag the event to another new track just to use fades?
Some feedback… 😉
@Zynewave wrote:
- The waveform displayed on sound events are scaled according to the fade curve.
The first time I saw this kind of feature I was really impressed. It was in Samplitude. Considering how much that costs compared to Podium it really is just great to see this in Podium. It not only works for the fades but also the veritcal volume adjustments on clips as well. 8)
- Added “Show sound event fade curves” option to the tracks region properties dialog. When enabled, all sound events show their fade curve. When disabled, only the event under the mouse cursor shows a fade curve. The option is enabled by default.
This feature makes such a difference. 🙂
- Right-clicking the fade-in or fade-out handles on a sound event will show a menu with default curve shapes. Right-clicking on the fade curve will also show the fade menus, and if there is a crossfade then the curve of both the overlapping events will be set.
My pick of a great bunch. The right click menu is just so well done. It is just so simple to choose fade types in Podium, I actually prefer this implementation to ACID’s 😉
- It is now possible to create multiple MIDI input mappings for the same MIDI interface input. A single MIDI controller can thus be assigned to multiple tracks allowing layered control of multiple devices.
I just layered Atmosphere and Dimension, layering in Podium 🙂 Great! 8) I can easily save layered synths in a new project and save that as a new Project template. 😉
- Added “Release drivers when Podium does not have focus” option to the preferences dialog.
This works very well thanks 😉
But there is just one problem with fades and crossfades…
When working on an instrument track for instance I will wrap it in a bounce enabled track. Of course the midi is then converted to audio. Fine so far.. but when I try and apply any fades to the audio clip they are simply not available.
This was puzzling as I knew it did work before.
However, if I create a new track and drag the sound event there, the fades and crossfade handles become visible and are fully functional.
Something else as well…disabling track bouncing on a track will re – enable fades and crossfades on an audio clip. Of course re enabling track bouncing disables fades and cross fades for clips on that track.
Why are these features linked to one another? Bounce enabling, fades and crossfades?
Hey! Best wishes to you too Frits and everyone! 🙂 Enjoy the Christmas break. 😉
Cheers Frits, a huge update! 🙂
@Zynewave wrote:
The only remaining track count issue is instrument tracks as unless I have missed a crucial step I cannot insert an FX mapping on the same track where an instrument mapping resides.
It should be possible to route both the effect and the instrument plugins in a zGrid instance, so you can do it on a single track if you want to.
🙂 Great!
It really looks like the “Siegried” will really refine FX processing in Podium in a very clever and creative way. 😀
@Zynewave wrote:
I’ve thought about building the functionality into Podium, but there are various reasons why it is a good idea to keep it as a plugin. For one, you can use the existing preset library system to store your zGrid routings.
Also as Podium does allow for one FX mapping on a track (processing audio events), that mapping can now be the zGrid… 8) keeping the track numbers used within Podium to comparable levels found in other hosts. With the exception of tracks with instrument mappings.
I also think the group track idea would mean that Podium would still need one extra track (when processing audio events) for the zGrid to work. That will also mean that Podium, would still need twice as many tracks compared to other hosts when using FX to process audio tracks.
The plugin idea is more flexible as it can be used on a new track or of course, even on a group track if my understanding of Frits comments on the zGrid so far are correct.
The only remaining track count issue is instrument tracks as unless I have missed a crucial step I cannot insert an FX mapping on the same track where an instrument mapping resides.
They must be on separate tracks.
Hopefully the zGrid can in some way or another eliminate that track count issue as well by providing a way to process tracks with instrument mappings on them without the need for a group track.
Perhaps a zGrid plugin for tracks with no mappings on them and another type specifically for tracks with instrument mappings already on them.
Or…
A default mapping of the zGrid plugin similar to Haiku’s idea but placed on any track by default but allowing for an instrument mapping to be added to the same track so that Podiums flow of processing upwards towards the master out is maintained.
I have no idea what needs to be changed under the hood to make that happen 🙂 😆 just trying to help with some ideas, but on the surface perhaps that might be something to consider to do away with an additional group track to process a track with an instrument mapping already on it. 😉
@Zynewave wrote:
That’s a good guess. It will be a user configurable X*Y grid where signal flows from the left edge of the grid to the right. Placing effects on a row creates a serial routing, and placing effects in a column creates a parallel routing. There won’t be any wires to drag. The placement in the grid decides the routing.
I think the ZGrid or ZMatrix will offer some very interesting options 8) serial or parallel routing would be great!
The first version may not support it, but it should be possible later on to support routing MIDI through the grid as well. You could then layer synths and play them with a single track/MIDI input.
Yes the ZGrid ‘framework’ seems ideal for this. It just gets better
@darcyb62 wrote:
I use the hide lane feature but I do find it a bit a bit of a burden to make adjustment to the hidden tracks or even see what is contained in the hidden track.
Same problems here.
If the chainer panel would allow you to view the entire chain when selecting any track in the chain it would be a heck of a lot easier to see what’s going and to adjust as you want. I could go for that.
As you now probably know now, the zMatrix looks like the ideal answer. 🙂
This architecture (once you understand it) truly separates Podium from the other products out there.
No question. In a busy mix simply dragging up the mixer to see the relationship between tracks is unlike anything I have seen. It is very clever but…FX usage can introduce very high track levels which was my problem. With the zMatrix however everything changes. 😉
That is indeed the way I intend to go. Working title for the plugin is zMatrix.
I have not started implementing it yet, but I have a good idea of how it is going to work. There is going to be a couple of novel features in that plugin.
Sounds good, very good. 🙂
I would have started it a long time ago, but there have been so many requests for other “standard” features that I felt I needed to get them out of the way before starting on some of the “unexpected” features.
Yes, I totally agree, that is exactly why I have not brought this up until now. There really were many “standard” features that Podium just did not have. I do not think that is the case anymore though hence this thread.
If the host plugin calculates the latency of its plugin processing chain and reports it back to Podium, then PDC should be ok.
Thanks for the clarification but I think I will now wait for the zMatrix 8)
I might do a clean install of Windows XP soon but with Vista on the horizon and Podium consistently performing so well ‘as is’ I might wait a bit longer. 😉
But yes a clean wipe can be a huge help. 🙂