thcilnnahojthcilnnahoj@Zynewave wrote:
Some tips, that you may already be aware of:
In the start of the video you rename the individual mappings. You can rename the folder (e.g. from “Addictive Drums” to “AD”), and all mappings will be renamed accordingly, provided that you do it before customizing the individual mapping names.
Thanks, that’s neat – didn’t know that yet.
I initially did not notice how you extended the loop range. You could also have right-clicked the loop button and selected “set loop around selection”.
Now that, unfortunately, I couldn’t, because the dropped MIDI event is 1/16th, 1/32nd, or whatever too short (you know that by now :lol:), which would’ve resulted in a weird loop…
But those general things (also selecing a tag, zooming out) weren’t part of the tutorial, so I didn’t give it much thought.
Just curious: What don’t you like about Kontakt & Kore Player?
Mostly I find the routing extremely confusing. Besides that you have three different DLLs for different output channel numbers, the “host channels” in Kontakt seemingly cannot be configured or at least renamed, and so some instruments end up being routed through “Kt. aux n” (though they aren’t used as busses anymore).
I’m also getting nasty intermitting distortion (as if a CPU overload occured) even with just one instrument loaded and generally rather high CPU use – that doesn’t mix with recording video on my poor computer…
By the way, there also seems to be something Kontakt Player is doing that causes Podium to always ask to save changes upon closing the project, even after you just saved.
thcilnnahojOkay, here’s a non-flashy video of how to set up Addictive Drums as multi-output instrument: http://www.youtube.com/watch?v=RbrtFct9b38
It should be applicable at least to other drum samplers as well – for Jamstix too, apart from that you can/must assign which instruments go to which outputs, and that its MIDI export is broken for me.
Maybe Frits would like to do a video for GPO? Because Kontakt & Kore Player are not nice to work with… 👿
thcilnnahojAfter playing with it some more, I can’t seem to get around the problem that it only writes MIDI note events on C1 for all instruments. The same happens when trying to export its output to a MIDI file, also in energy XT and Reaper demo…
But like I said, I’ve got zero experience with Jamstix, so it might just be user error. :-k
The upside is that all those kickdrum hits it produces for me can be very easily bounced to audio. 😉
You said you get a signal on outputs 1+2 – did you disable the “downmix” option in the Jamstix mixer?
thcilnnahojHmm, I wrote in the preview topic that I don’t find vertical position locking useful, but I neglected the other editors besides the arrangement view… It is certainly very useful especially in the curve editor! 😳
Thank you for another great update!
thcilnnahoj
1. The original note, with an example snap setting of 1/16th
2. First snap point – the note is extended to a length of 1/16th
3. Second snap point – relative snap
4. Third snap point – grid line
Steps 3 and 4 can then be repeated for every 16th step.
Is this by design? I kinda expected the note to first snap to the .3 grid line (as it’s the closest point to snap to) instead of getting quantized to the snap setting, but it seems it won’t snap to this particular grid line at all.
thcilnnahoj@Zynewave wrote:
@thcilnnahoj wrote:
The problem is that the events are cut off at the end of the last note: GIF animation (this one consists of 32th notes, and is cut off one 32th early). It is created correctly in other hosts. The same seems to be happening when dragging events from the inspector’s track panel…
I take it that the bit that is cut off contains silence. So it doesn’t actually corrupt the playback, but it is an annoyance when you want to repeat the pattern snapped to bars?
Yup, just a little. I rarely ever drag MIDI files from a plug-in myself, but since it happens when using Podium alone (rfom the inspector’s track panel, and probably when dragging them from the browser, too?) it may become annoying to more people.
By the way, when dragging things from the browser, inspector, track chain panel, etc., right-clicking of course cancels, but sometimes also opens the menu afterwards.
It seems this starts happening once you’ve opened any menu by right-clicking in the arrangement view, track headers, timeline and other regions, menu buttons, inspector panels, or in the mixer. It can be reverted by starting to drag any event and cancelling it… weird! 🙂
It doesn’t happen when opening right-click menus inside the chain panel.
thcilnnahojI’ve never used Jamstix, but I believe it’s meant to be used somewhat differently… Meaning that there are no actual MIDI events in the arrangement, but rather Jamstix plays along all by itself, no?
That could explain why bouncing doesn’t work for you…
Edit: Oh, I see you first recorded Jamstix’ MIDI output, thus creating a MIDI event in the arrangement. Anyway, I managed to get it bouncing with multiple outputs just now, but I don’t quite know my way around its interface yet.
I could see about making a video with multi-timbral instruments the coming week. However, I only have Addictive Drums and the free Kore Player right now.
thcilnnahoj@LiquidProj3ct wrote:
@thcilnnahoj wrote:
@LiquidProj3ct wrote:
– Dragging clips from inspector to arrangement doesn’t work, it’s buggy
Aha! It does the same thing that happens when I drag MIDI files from Addictive Drums into the arrangement
As far as I know Podium never supported memory exchange between plugins and its interface (you cannot drag samples from browser to plugins and you cannot drag samples from plugins to arrangement), is it that right?
Maybe not audio, but you can at least drag-and-drop MIDI files from plug-ins.
The problem is that the events are cut off at the end of the last note: GIF animation (this one consists of 32th notes, and is cut off one 32th early). It is created correctly in other hosts. The same seems to be happening when dragging events from the inspector’s track panel… But maybe you’re talking about a different bug?
@LiquidProj3ct wrote:
Collapse tracks doesn’t work when a tag is currently selected, or sometimes it works in mixer but not in arrangement – don’t know how reproduce this last situation but I’ve a pod file that I could email you if needed.
It’s most likely because the child tracks are also tagged, which makes them impossible to collapse – Frits said it’ll be fixed.
thcilnnahoj@Zynewave wrote:
@thcilnnahoj wrote:
Middle-click on the timeline will set the edit cursor snapped. Holding Shift while clicking will set the edit cursor without snapping.
I really like(d) this one. 🙁
Moving the cursor with snapping enabled can already be simply done by clicking on the timeline. I think not everyone uses, or even has a middle button available, so I preferred it doing something special.Hmm, I actually was annoyed by the old behaviour. I use middle-click to quickly position the edit cursor on the grid when I’m editing events. Though this change may be a minus to you, I hope you overall find more plusses in this release.
It’s fine – I can live with the Shift+MMB combination to still set it without snapping. I’m generally very happy with this release, especially with being able to override the selection rectangle snapping, which sometimes bugged me quite… a… bit. 😉
Modified the behaviour of the Q/W key shortcuts: Q/W moves the edit cursor in steps of the grid value. Shift+Q/W steps the edit cursor between marker events and active loop, punch and segment ranges. Ctrl+Q/W will set the edit cursor to the start or end of the current event selection.
Hmm, this is fine, but you also seem to have swapped the actions of the numpad home/pgup and left/right arrow keys…?
They were swapped automatically by the change I made to the commands, but I’ve now swapped them back to their previous numpad keys. I’ve also added numpad 1/3 as shortcuts for setting the edit cursor at the start/end of the current selection. I don’t use the numpad myself. Would you perhaps prefer a different setup? Maybe the shortcuts you use the most should be on 1/3.
Sounds perfect. Though I always used the numpad (especially because I like how the enter key restarts playback instead of toggling play/stop), I thought about switching to Q/W to make use of those new ‘move to selection start/end’ functions – but them getting added to the numpad is even better! 🙂
thcilnnahojMy observations:
Alt+Shift as it is in beta1 is pretty useless. It does the same as just holding Alt when dragging vertically, and for horizontal dragging… I think it’s not that hard to keep an event on the right track.
Ctrl+Alt+Shift is equally useless. In beta1, it doesn’t do anything different than Ctrl+Alt when dragging vertically, and again, locking the x position isn’t really necessary, in my opinion.
Something I came up with:
Ctrl – Create phantom copy
Alt – Lock x/y position
Shift – Override snap
Ctrl+Alt – Create unique copy
Ctrl+Shift – Create phantom copy and override snap
Alt+Shift – Create phantom copy and lock x/y position
Ctrl+Alt+Shift – Create unique copy and override snap
It’s not great either, especially Alt+Shift is weird, and there’s no shortcut to create a unique copy while locking the x/y position.
I don’t know of any programs that add the right mouse button as a modifier, and think I’d find it uncomfortable…
Something will have to be sacrificed in the end… Personally, I’m fine with losing ‘create unique copy’ and getting ‘override snap’.
Thinking of the future – I’d say it would be fine if time-stretching, for example, was done by clicking on the resize handles while holding some modifier key. I don’t think anyone would time-stretch at a zoom level where this becomes impossible.
thcilnnahoj@LiquidProj3ct wrote:
– Dragging clips from inspector to arrangement doesn’t work, it’s buggy
Aha! It does the same thing that happens when I drag MIDI files from Addictive Drums into the arrangement – it cuts the event off right at the end of the last note. So a one bar long event consisting of four 8th notes on the beats will be one eight too short, meaning you have to change the event’s length by hand in order to make copies of it without messing up the timing.
thcilnnahoj@Zynewave wrote:
Added Ctrl+R as shortcut for resetting current event/segment selection.
Nice! This comes as a present to me. 🙂
Middle-click on the timeline will set the edit cursor snapped. Holding Shift while clicking will set the edit cursor without snapping.
I really like(d) this one. 🙁
Moving the cursor with snapping enabled can already be simply done by clicking on the timeline. I think not everyone uses, or even has a middle button available, so I preferred it doing something special.
Modified the behaviour of the Q/W key shortcuts: Q/W moves the edit cursor in steps of the grid value. Shift+Q/W steps the edit cursor between marker events and active loop, punch and segment ranges. Ctrl+Q/W will set the edit cursor to the start or end of the current event selection.
Hmm, this is fine, but you also seem to have swapped the actions of the numpad home/pgup and left/right arrow keys…?
While I’m comfortable with 99% of the default key and mouse configurations in Podium, customizing them would still be nice. Though I guess it’d be some hard and boring work, or you would’ve already done it.
Oh, and I love how snap works with all three new options enabled!
Edit: The help text for the note editor’s velocity buttons, and the curve editor’s draw mode buttons should be returned back to point to Ctrl instead of Alt.
thcilnnahoj@tumult wrote:
@thcilnnahoj wrote:
It’s the other way around in Podium, though – the signal flows upwards, so MIDI or audio data does not get passed from parent to child. But some kind of feature to easily layer synths, or otherwise send MIDI data to multiple tracks has been requested.
Yes, that’s what it was implying 🙂 It flows from the children through their parents, towards the root, just like Podium.
Ah, yes, I misread. You wrote about feeding multiple MIDI events to one instrument – I thought it was about sending MIDI data from one track to multiple instruments, which can’t be done currently.
In Logic, I can put the entire chorus (even though it’s made up of multiple clips across multiple, unrelated tracks) inside of a single clip, except for the one part that will be different between the two copies, the drum fill. So picture this: the entire chorus inside of one clip, and the two drum fills that are different outside of that clip in their own separate clip. Now I can make a phantom copy of the entire chorus, except for the drum fill, which is exactly what I want.
Does that make sense? It’s kind of hard to explain with words.
Okay, I think I get it too. So I guess Logic would display this chorus as a single meta-event, which you can then “open” to edit its contents? All the events inside it (if they’re phantom copies) would still remain linked with their counterparts on the normal arrangement level. Plus, the meta-events themselves can be phantom copied… sounds good.
@Zynewave wrote:
Some day I’ll extend the markers to have a collapse button, like the circular one used on group tracks. That can be used to collapse part of the timeline that you don’t work on currently.
I hope Some Day arrives soon. 8)
thcilnnahojThat’s a long read. 😉
I don’t know either of those two programs inside-out, so I can’t comment much on it, apart from these two things:
In Cubase, REAPER, Podium and most others, you can do the same thing by creating tracks which have MIDI sends to a single track with the instrument plugin on it. In REAPER and Podium, you can create the tracks as children of the track which contains the plugin, and you would not need to explicitly use sends to pipe MIDI data across. The signal would flow towards the root of the tree, through its parents.
It’s the other way around in Podium, though – the signal flows upwards, so MIDI or audio data does not get passed from parent to child. But some kind of feature to easily layer synths, or otherwise send MIDI data to multiple tracks has been requested.
It allows for a real separation of data which is related to the semantics of time (the musical sequence, edits, etc.) and data which is related to signal flow and audio routing (the connections between audio objects, plugins, effects, etc.)
As the amount of stuff in a project increases, it becomes more and more difficult to work with. Creating a chorus section which is repeated in two places in a song, but not identically, usually means copying the clips from one place to the next, and then changing them as necessary in the second location. [2] Now we have a problem — if the musician later finds something that must be changed in all of the choruses, like a mistaken popping noise from a bad edit, she has to remember, somehow, to change it in both places.
How do these observations relate? You can separate devices (e.g., routings, instruments, effects) from events (e.g., MIDI, automation) in many programs, like Energy XT or Mu Lab, but how would that help with the “bad edit” problem… Usually you’d have linked events (phantom copies in Podium), but if every chorus part should be a little different, I don’t see a way around keeping separate events.
