Here’s a video showing two strange things I noticed: http://www.youtube.com/watch?v=vfvgtDTNdUI
I hope you’ll see what I mean, otherwise I’ll have to whip out a microphone next time around. 🙂
1. Contents of events that have been time-stretched (and cut?) don’t sound, this also seems dependant on the playing start position.
2. When a time-stretched event is resized from the start, the original position of notes inside seems to change in unexpected ways. Don’t know if this is intentional – looks pretty weird to me.
As for the automation curve coloring, allow me to point to three posts starting from this one: http://www.zynewave.com/forum/viewtopic.php?p=16579#16579
The changed coloring in 2.33 makes it neither better nor worse for me, personally. I’m fine with either for the moment.
What can I say – I love it already! :D/
A possible suggestion I have would be a somehow more obvious way of marking time-stretched events (will be even more useful for audio later on), though I can’t think of any right now. The way the waveform gets a colored frame in Logic is nice, but might not be applicable as well to whole events.
Something that would be handy is a ‘reset’ command to return the event to its original setting. When I gave it a spin just now it was a bit fiddly sometimes to get the original timing back (you suddenly have to do math! :lol:). It would probably be easier to delete an event and replace it with a non-stretched copy, but only as long as it’s not unique.
I also hope that the resize/fade handles will be made more distinguishable, should you redesign them at some point.
Tap tempo: It would be much more useful if you could hear the tempo change while playing – I remember reading that this would require some rewriting, so maybe some other day. Also, when applying a tempo change to the current section that’s playing, this can result in stuck notes.
You’re doing quite well for teaching yourself! Can’t say I’ve had problems understanding anything you wrote recently.
To try and help, let me point out something:
Every now and then you leave out some words – for example, when you say you “watch few movies”, that means you don’t watch much at all. You probably meant to say “a few”!
Also, on rare occasion you use words or expressions that are probably very similar in Spanish and English, but mean different things. I’m guilty of doing that myself quite often – with German words, of course! 😳
I also learned mostly by watching films (because the way it was taught in school was far too boring), so I think it’s a good alternative if there’s no one around to practice with face-to-face.
@Zynewave wrote:
@thcilnnahoj wrote:
Well, I can’t say I’m overwhelmed by the beautiful lightshow you now get moving the mouse across an arrangement. I could probably enjoy it more if it had a short fade-in/out time, but that’d be too much to ask.
Are you saying that you’d rather not have the highlighting? I made it for consistency with the note event highlighting. I’m planning to add it to the tempo and marker events as well. Further down the line I’ll probably remove the remnant black frame highlighting.
I don’t immediately like it, no… Maybe I will by the time it’s completed and the frame gets taken care of, like you say. Well, you know best what you want it to look like, and I’m definitely not trying to spit in your soup!
– There’s a bump at the top on fades and crossfades. Don’t see it? Let’s zoom in. 😛
I’m not seeing anything unusual. What bump are you referring to?
It’s due to the volume handle. Maybe this will help – look at the top edge.
It has always been like that, but this was a good time to throw it out. You don’t want me starting threads for such a nitpick! :-#
Fix: The track event background color is now painted properly when only part of the event is record enabled with punch-in and punch-out.
Nice! But It’s still off with overlapping events:
This is a consequence of the way I layer the painting. Perhaps you can set up a poll asking if people would prefer I redesign this, rather than implement time-stretching 😉
Heh… you better not be just teasing with that! 😯
(X) TIME-STRETCHING
I have a question at the end: Maybe I’m completely crazy, but weren’t there “Undo/Redo Inside” menu entries in the event right-click menu until one or two versions ago!?
They disappared a while ago, in one of the cleanups of the edit menu.
Hm, that’s a shame. I used them on occasion, and even thought of suggesting that they could be expanded to show a list of undo steps (like right-clicking the undo/redo buttons).
Ohh… you are asking for it this time! 😆
Well, I can’t say I’m overwhelmed by the beautiful lightshow you now get moving the mouse across an arrangement. I could probably enjoy it more if it had a short fade-in/out time, but that’d be too much to ask.
Now prepare for a nitpick bombardment (among other personal observations).
– I really like the look of the new track headers! Can’t use them though, since I most often zoom out so much I wouldn’t be able to see the event contents anymore… too bad for me. 😛
– A problem I’ve occasionally had in the note editor seems to have found its way into the arrangement view now, too. Namely, short events are drawn in a weird way. It’s also very hard to see when they’re selected:
– Shadow reduction around notes looks good and everything’s much snappier now, even with tons of notes – great work! (However, I think I liked the way shadows [when they first appeared] were drawn on all four sides a little better than mostly just below events.)
Now it’s pixel-pushing time!
– With a color scheme using bright text on dark backgrounds, notes and event names expand beyond the event borders. Also, the event name box seems offset from the start, resulting in 1px of waveform not being dimmed:
– At first glance, I liked the softly colored edges of adjacent events better than the clear-cut almost black lines, although I guess it does make for a better visual separation and I’ll quickly come around to prefer it. It looks weird though sometimes, as the backdrop of the event name, phantom copy and mute symbol seem to overlap the right edge (as mentioned above):
– There’s a bump at the top on fades and crossfades. Don’t see it? Let’s zoom in. 😛
– Events look like they’re shrinking when you hover over them (this actually was the same before, but not as noticable):
Fix: The track event background color is now painted properly when only part of the event is record enabled with punch-in and punch-out.
Nice! But It’s still off with overlapping events:
Okay, sorry, I’ll stop now. This post looks like a Picasso painting already.
I have a question at the end: Maybe I’m completely crazy, but weren’t there “Undo/Redo Inside” menu entries in the event right-click menu until one or two versions ago!?
@LiquidProj3ct wrote:
Yes, and you cannto figure how do this without seeing a tutorial or reading the manual. To be honest I don’t think that problem is “sidechain”. The problem are multiple inputs and/or multiple outputs plugins. It’s difficult and tedious use them in Podium for a newbie.
I wouldn’t know how to approach this, but something like that each mixer strip would had a channel settings (1-16), and an special mini zPlugin that would send the audio between channels. Or a matrix screen where you configure each mixer strip channel (or convert it to another channel). Or something like zRoute FR.
This would be a big change… :-k
Hmm, I think the way multi-out plug-ins are set up is one of the best in any host, especially since you can drag the whole folder with mappings inside onto the tracklist). One instance of a drum sample is often enough, but not so with side-chains…
It becomes a little more tedious as in other hosts when you need a second instance (and may not know how to create one)!
I’m currently “researching” other hosts’ different ways of modular routing and signal flow display (you know I was kind of against it before :wink:), so that’s a discussion I’ll enter later on.
@LiquidProj3ct wrote:
I generally agree with those ideas. However i’m pretty busy now, it’s my birthday 🙂 so i’ll post my ideas later, everyone here know them, although
Hey! Happy birthday! Hope you got some nice presents. 😉
@LiquidProj3ct wrote:
@thcilnnahoj wrote:
>> To make working with busses easier…
… we could have an extra menu entry like
or on top (or at the bottom) of the list. This command would create a new bus instance and assign either the resulting (stereo) send or return mapping to the track. I assume it’s not a problem for Podium to find out which mapping fits.
The command would show up everywhere Podium detects a bus mapping, so it would not be limited to the default Busses folder created automatically.I didn’t understand very well, because I see the current way very good: If you add any send X and there isn’t any return X, podium ask if you want to create one, it renames and tags it and set it to “automatic solo”. What would be the advantage?
Yes, that works fine… I was talking about creating the actual send/return device mappings that you put on tracks.
The number of sends is limited in most other sequencers, so everything is taken care of by the program (though limiting). To get 8 sends in Podium you have to first create the devices yourself.
The way Podium handles these things won’t be changed very likely, and it doesn’t have to. Some of the low level operations you have to do could, however, probably be defused, like track management has been. The commands to create new busses are a little hidden away, and new users are unlikely to find them when they’re right in the middle of mixing and need a fifth bus. Sure, it’s not hard to do, maybe part of the learning curve, but probably a little steep one.
So this could be made easier if there was a
One problem with this is, because it’s so customizable, some users might have their bus mappings arranged differently in the device mapping structure. I.e., there might not be a Busses folder, or multiple folders containing bus mappings. The proposed command would have to be aware of that…
It seems when you create a new instance of, e.g., a bus mapping below which is a folder, the new mappings are added inside that folder: GIF animation (170 KB).
Just in case you didn’t know, you can move the edit cursor to the loop start/end points, too.
Press Shift+W or PgUp on the numpad to move the cursor forward, and Shift+Q or Home on the numpad to move it backward. This will snap to either the loop start/end, punch start/end, segment selection start/end, or marker events – whichever comes next on the timeline.
Edit: Maybe I misunderstood what you’re trying to do, but I don’t think you can split events at all when using the segment tool?
Something about the ghost notes opacity seems to have changed, and now they’re different on white and black keys.
It still looks fine when using the ‘colorize note events…’ option.
Default theme and default ghost note opacity setting of 25%:
Suggestion: in the drum map (but not limited to), it would be useful to have a “paint” tool, which is probably faster to use than having to draw single notes, and more precise than holding the insert key to duplicate. Or it could be available with a modifier key for, e.g., the pencil tool (Alt-click to paint?)