spritexI didn’t want to start a new thread because it’s kinda close to this subject:
Currently, it’s not possible to lenghten a sequence event to the left from the original size – it only works to the right.
Would be more logical and also useful if it worked both ways. Here is an example I just ran into:
Say, you have a 1 bar sequence event on every fourth bar on a track – for example a drum break you want to handle separately. Then you decide to merge those for editing them together. After the merge operation there is empty space on the first three bars on the track, so it’s not a neat divident by four block. You can of course create an empty event in the start and merge that too, but it’s not as intuitive as length-dragging left…
(The second handle halfway for note stretching sounds like cool GUI solution for that operation. Just make it an option to reduce clutter if not needed.)
spritexI live in the house that it’s pretty much in the middle here. “Sörnäinen” part of Helsinki, about 10 minutes from the central railway station by metro.
spritexOkay, I played with this a bit more and the child tracks can inded be used in playback – good!
But am I right that I can only record to the parent VSTi track? In this situation I always need to manually move the sequences down to child tracks from the parent track to make room for new recordings. (If I want to keep newly recorded stuff in separate sequences, of course. Which would be a pretty common need, I think.)
So, there is a totally unnecessary extra step in the workflow.
Is there some reason why direct recording to the child tracks couldn’t be allowed?
spritex@Zynewave wrote:
You mean an insert instrument (and not multitimbral)? It should be doable by placing all the MIDI tracks (without any mappings assigned) as child tracks of the VSTi track.
Hmm, I made a child track to the VSTi, but I can’t record to it. Could you look at this picture if you can see what I am doing wrong:
spritexHey, that would probably solve the confusion, Frits (can I call you by your name).
I have been playing with Podium a bit more. A few times I started out writing a question here, but then I found how I could do what I wanted.
(In case you are interested: Instantly setting MIDI in for the selected track, separately processing multiple outs from a VSTi from the same sequence, reducing clutter in Arrangement by hiding tracks.)
I still need to figure out how to have several MIDI tracks controlling the same instance of a VSTi, but I haven’t read the manual much nor looked at all the tutorials. This is possible, right?
Also, did I understand right that if I for example set up a multiout VSTi with tracks for insert FX for different outputs I can save that as a “preset” and load that part of track setup to other projects? This would help quite a lot.
The whole “from top to roots” structure is confusing at first but it probably just takes some time to get used to – and I can already see some of the benefits.
I would mainly use Podium as a MIDI sequencer with VSTi’s and FX so I am not that interested in timestretching and such. But surely you intend to add more MIDI editing options at some point after you get some more audio related stuff done? Quantising as a track property instead of fixing notes would be really nice (and would allow “auto-quantising”).
Talking about quantising, since I make mostly minimal techno I tend to quantise always after recording. I didn’t find a shortcut for “quantise inside”…
For your information, I am already pretty close to purchasing. ❗ It seems very stable and robust, so I feel I could start making music – and you seem to listen.
spritex@Zynewave wrote:
@spritex wrote:
Editing events.
To make sure I understand you correctly: The problem you experience is that inserting/editing events that are within one second ahead of the play cursor is not heard until the next loop cycle?
Exactly. 1 sec. is quite a long time when editing a four bar loop.
I trust that you are doing important things, I gathered as much. 🙂
But it would be important to have a more instant feel to the editing, so I hope that you’ll try improve it when time allows.
EDIT: I played with it for a while again, and it’s in no way unusable as is – but halving the time to 0,5 sec. would be really nice.
spritexEditing events.
(And you sure respond fast, I like!)
spritex@Zynewave wrote:
To achieve the ‘gap-less’ performance, Podium prepares the playback one second in advance before outputting the prepared buffers to MIDI and audio interfaces. This is why e.g. edits applied to events within one second of the current playback position will not be output.
This is one of the first things I noticed when I started testing Podium yesterday. It’s a bit annoying when you are editing a drumloop or whatever.
If it can’t be gotten rid of, would it be possible to make an option to change this from 1 sec. to a shorter time sacrificing CPU cycles of course?
Oh, and hello – this is my first post here! 🙂
I am currently pondering if I should purchase it (testing with the 1.77 demo).
(I wrote a couple of messages on KVR as you might remember.)