Zynewave.
Mike GHi,
First in praise of tags…
Not used them before (been away for a while!) and they are super easy to get the hang of and make my arrangements very easy to handle.
(thanks)
Question:
If I copy and paste, should theb track keep the same tag?
(Or should it … now I think about it maybe this isn’t always what you’d want!)
Anyway… Main issue:
If am scrolled down at track number 12 (out of 15) through the tracks and then click Tags so that only track 9,12 and 13 are shown. Now I am looking at blank space. Tracks 9,12 and 13 are way way far up and I have to scroll up to find them.
Possible solutions:
When you click a Tag button, I think it should keep the selected track selected and in view
If the selected track becomes not visible then at very least should scoll up to the last visible track so you’re not looking at blank space.
Thanks,
Mike G
TrancitYeah, that´s my problem too…
Another one, is for me, that often I like to have different views for the arrangement and the mixer…some tracks I need in the arragement I would like to hide in the mixer, but that´s not possible at the moment by tags, isn´t it?
Trancit
druidSorry to bring this old thread up, however I am trying to create a send and hide it from the mixer, and seem unable to do so.
Currently, my template has a range of visualisation plugins on its effect list. Due to unnecessary space usage, I thought why have that on the master chain? I’m not always monitoring deeper details. Why not create a send for it? So I tried that, moved the effect chain (manually, because master track has no effect chain saving…) across to the send track (which has a return as source), lowered volume to 0 (as I don’t want it playing, only monitoring) and set the fader to after all effects, to make sure all effects get the level sent to them.
Excellent, I thought, now I can monitor signals by adding a send on a track. But now the analysis track, naturally, shows up on the right side of the Podium mixer.
I can just not show sends, but what if I want to have a reverb, delay, and whatever other send there?
For that matter, as I am trying to bring some of the simple routing out of energyXT and into Podium, I’m planning to use track-specific sends. The problem is, that means if I create even 4 track-specific sends, I will have at least 6 sends listed at the end of the mixer! Reverb, Analysis, Track 1 Return, Track 2 Return, Track 3 Return, Track 4 Return.
Ideally, as I don’t have modular routing available to me in Podium, and as the idea of tags was meant to tidy things up, I would like to be able hide certain tracks from the mixer. If that means using tag viewing separately for mixer and timeline, so be it. I suppose a simpler option would be to allow tags to hide from mixer as well, which means I could create a Hidden Busses tag and make sure they almost never show. Unfortunately, I noticed that sends show regardless of tags.
So I wonder why the default Podium tag Busses shows up? What’s the point of tagging them if they never disappear?
Anyway, if anyone can help me with this (if there’s an option currently) that would be appreciated.
I had a sudden thought, though it is less preferably to me. If a person creates multiple mixer views, can you set each mixer up individually? That way, I could have a send mixer and a track mixer..?
thcilnnahojTrack tags will work on return tracks in the mixer only when the tracks are not docked (View menu -> Customize Region -> Mixer: disable bus return docking). They’ll thus not always be in view anymore, and appear in the tracklist as you’ve arranged them.
The reason the busses tag doesn’t work for you is because you’re probably still using a Podium setup file that has been carried over from a much older version. The default setup no longer has return tracks docked since track tags were implemented – maybe you’d want to take a look at what else might’ve changed. 😉
Anyway, in this case, it seems you’re pretty much routing each track separately to this analysis track by using sends? Then perhaps a better way would be to place the analysis effects on a group track that contains all your normal tracks, like so:
Master:
- Bus Track (might or might not be part of analysis group)
- Analysis Group Track:
- Track 1
- Track 2
- Track 3
...You could then create a tag for this group track (without child tracks), and only show it when needed. Saves you a few send level sliders, I think!
druidArgh, I brought up the issue of upgrading Podium but not the profiles a while ago. Being able to just update profiles is good, but if you have customised them even slightly, then it reverts them. I try not to customise editor profiles now for this very reason, so then why have them customisable?
I’m not really sure where the balance is between customisable and updating your version to newer ones, though. They are two different paths, after all.
Thank you for your suggestion. The new profile does solve that for me, and I’d already found that option but didn’t realise it was default now. I’d never worked with sends in Podium before due to not having much time for music work (but being in Brisbane with the floods, I can’t work so found some more time!).
One of the reasons I was going to put it on a send was so the audio only went to it if I told it to, otherwise it didn’t. However, it’s true that I don’t want a send taken up with it, the idea was based on organisation more than anything.
Having a group track do it does resolve the issue of having master effects space taken up, however, so I will probably do it the way you suggest. Thank you for your help!
Coming from a modular environment, I still find some things awkward to achieve in such a setup. More on that in another thread soon, no doubt!
druidAs it turns out, this solution fails due to the input selector being removed in child tracks.
I’m not entirely sure why input selectors for child tracks were removed, but perhaps child tracks were not intended to be used in the way I am.
So I will in the end need to create the bus as I planned before, which won’t show anyway because of the new editor profiles I have now loaded which don’t dock return tracks.
There may be times where I want to assign specific midi channels of specific midi devices to child tracks, and it would appear I am unable to do so, without first setting the track up outside of the group, and then moving it into the group afterwards.
Still, currently the send is the best choice. I will only be adding it when needed so it won’t add a lot of space wastage.
Frits, would you consider allowing input selectors on child tracks? Maybe not all child tracks, but sometimes group tracks are used just as an organisational tool and it doesn’t make sense to prevent them from being separately controlled. I may have missed discussion on this due to me being unable to keep up to date recently.
druid@druid wrote:
Frits, would you consider allowing input selectors on child tracks? Maybe not all child tracks, but sometimes group tracks are used just as an organisational tool and it doesn’t make sense to prevent them from being separately controlled. I may have missed discussion on this due to me being unable to keep up to date recently.
After having tried a bit more, I worked out what the issue is. On my template, I have six tracks, a bass, lead and percussion track (which is a group track containing two child tracks), and a reverb bus track.
Only the reverb bus track has anything connected, which is of course the Reverb Bus Return that I set up.
I noticed all input selectors stay selectable up until I put the reverb bus track inside the “Analysis” group track. Everything else can be in there, but once I put the track with a bus return on it, the input selectors vanish.
Frits, is this intentional, or an oversight? I don’t really want midi going to my group track for analysis, just want audio to run through it, almost for it to be invisble.
I also tried to do the following: In my percussion track, I have two layers. I thought to create, say, 3 tracks for kick, snare and hats, under a group track called Layer 1 (as there is also a Layer 2), under a group track called Percussion. On the kick track, I tried to assign a VST output 1, the snare VST output 2, the hats VST output 3. Then on Layer 1, I tried to assign the same instance’s VST midi input. The idea was that midi would control the whole layer, but I could then add FX on each output. I don’t think this agrees with Podium’s hierarchical way of working, but still, I can’t see why this would be a problem? I haven’t tried, but I wonder if I had two separate tracks, one for all the audio outputs and one for the midi input, would that work, without having groups? I will try that later.
Still, that was a side comment (paragraph!). My main concern is that as soon as I put a child track with a bus return on it in a group track, all input selectors vanish.
I preferred being able to have a group track for analysis as that way everything I add automatically goes through there. Currently, whatever I want to analyse needs to have a bus send added and volume set, and it seems easier to just solo whatever I want to analyse rather than do it the current way.
thcilnnahojOops, I must’ve missed your second post on January 15th!
You’re right in that the input selectors becoming unavailable is strange… I don’t think it’s intentional, but we’ll have to wait for Frits to clear things up.
Zynewave@druid wrote:
Frits, is this intentional, or an oversight? I don’t really want midi going to my group track for analysis, just want audio to run through it, almost for it to be invisble.
Input selectors are removed from all tracks in the bus return section. When you move a bus return track into a group track, this group track becomes the bus return section (which can be shown docked in the mixer). This was done as I thought it would be confusing to be able to assign inputs in the bus return section. So it is intentional, but I’ll consider removing the auto-hide of the input selector.
druidIs there any reason you thought a group should become a bus return group if a bus return track was inside? Or has this been covered before? I may well have missed it. You already seem to check for feedback loops in some setups so I can’t see that being a problem. I don’t see a problem if you were to disable the input selector on the track, but not the group track. I am not sure what others’ thoughts on this are? (I remember someone wanting to have an input on a bus return track too!)
Zynewave@druid wrote:
Is there any reason you thought a group should become a bus return group if a bus return track was inside?
The group track will only be marked (internally) as a bus return group/section, if it is the only group that has bus return tracks child tracks. Podium uses this to include the group track in the docked bus return section in the mixer, if you have enabled the docked bus option in the mixer region properties.