Topic: Okay, point-blank…

Viewing 6 posts - 1 through 6 (of 6 total)
  • #1279
    AngelicLight
    Participant

    Okay,

    I have a confession. I am so “not-the-right-host”-drained that I would be willing to give up if Podium wasn’t around. I just downloaded the demo and would like to ask a point-blank question to the current users, ESPECIALLY the ones who switched from other hosts.

    WHY DOES THE HEIRARCHAL WAY THIS IS SETUP “DO IT” FOR YOU, EITHER MUSICALLY OR PRODUCTIVITY-WISE?

    I have Cubase 4, Sonar 5, and Tracktion 2. Of the three, I almost use T2. Why not? Drum programming. I am primarily a guitarist who doesn’t have any keyboard technique. The other two are just too cumbersome and too “production” oriented than “output, flow, and creation” oriented.

    Also – since I’ve got some serious CPU-heavy guitar-amp-sim plugs, does the “bounce” feature work quickly to “dispose” of the vst’d track to fre up the CPU? I can get around 3 “live” Revalver II tracks in T2 with what else I’ve got going on and T2’s track freeze seems to be a little buggy.

    Finally, how easy is it to “copy,” “ghost,” or whatever the term is, a MIDI clip throughout the next x# measures or so? In creating a (rock) drum part, for example – with the Drum Editor – it makes more sense productively to just create one measure if the next 15 are all the same and then just copy them forward, if you know what I mean.

    I don’t need the most features, bells, whistles, plugs, in the world – just want something that helps me get my music out without as many hinderances as those hosts previously mentioned.

    Thanks all, a bunch, for any input, direction, or guidance,

    – A

    #9851
    darcyb62
    Participant

    If drum programming was the only issue I would recommend looking at drum product. There are many around that aren’t keyboard based.

    Having said that I came from the Traction space and I although I liked most of what Tracktion did I did not like how it handled “Track Freezing” and it had a very poor implementation of track grouping.

    The bounce featrure is among the best implementations I’ve seen/used and does a great job of freeing up resources. The best part about it is that you can add further effects to the bounced version if you so wish.

    To me the greatest value in the hierarchal approach is the ability to group and visually see your grouping. You can bounce your group and then continue to process effects to the bounced group. So I can create a group for my drums with snares on 1 track, bass on another, toms on another, etc. I can then add effects to each instrument/track (i.e. eq) to get the mix I want. I can then bounce that to save some resources and the add reverb to the bounced group. It’s just so easy when you get into it.

    The copy/qhost could use some improvement but it gets the job albeit 1 copy at a time.

    #9854
    Zynewave
    Keymaster

    Finally, how easy is it to “copy,” “ghost,” or whatever the term is, a MIDI clip throughout the next x# measures or so? In creating a (rock) drum part, for example – with the Drum Editor – it makes more sense productively to just create one measure if the next 15 are all the same and then just copy them forward, if you know what I mean.

    The quickest way to do this: Select the one-measure sequence event in the arrangement editor, and press the Insert key for each “phantom” copy you want to append. If you want to paste a large number of copies, you can hold the Insert key and let auto-repeating kick in.

    #9873
    AngelicLight
    Participant

    How does the heirarchal structure do things like parallel bus compression, like, on a drum track?

    For things like routing, is that all done in the mixer part, or on some part of the “heirarchy” for lack of a better term?

    Thanks a lot,

    – A

    #9874
    Zynewave
    Keymaster

    How does the heirarchal structure do things like parallel bus compression, like, on a drum track?

    What do you mean with “parallel bus compression”? Side-chaining?

    For things like routing, is that all done in the mixer part, or on some part of the “heirarchy” for lack of a better term?

    The signal routing is defined by the visual layout of the track hierarchy. Everything flows from the bottom of the hierarchy towards the topmost master track. You organize the hierarchy in the tracks region, by dragging tracks or by using the commands in the track menu. The mixer currently does not support dragging tracks, but I’m working towards that.

    #9875
    pernst
    Participant

    My understanding of parallel compression, with Podium

    Drum Group
    …….Bus Send
    ……………Kick
    …….Bus Send
    ……………Snare
    ……..Bus Send
    ……………HiHat
    Compressor
    ……..Bus Return

    All three channels (Kick, Snare and HiHat) go to the Drum Group. The Bus Send allows variable leves of each to be mixed to the Bus Return, which is routed to the compressor. The level sent to the compressor is regulated by the Gain on the Bus Return. Sorry, I can’t do images.

    I do this all the time with reverb and JamStix. I buss the everything but the Kick and put a reverb on the bus. This gives me a dry group and a wet group. Then send both dry and wet to a overall drum group, that allows me to adjust the total drum mix relative to the rest of the mix.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.
© 2021 Zynewave