This is the first part (theory). The part 2 will be ready in an hour.
http://www.youtube.com/watch?v=sXN7tuUJ04s
I’ll post it here too
I was just making a video tutorial about this, in few hours I’ll post the link here
Not sure about that, all my samples are 44.1Khz, but I remember I had the same problems in my old hosts. All I can say is that you could use a massive resampler
(or you could do music at 44.1kHz too, I think it sounds good, if your samples are at 44.1 they aren’t going to sound better if you resample them at 96khz or 180khz)
Are standart wav, or are they compressed?
Which is their frecuency?
Maybe those properties can cause that
Frits, if you start to implement midi timestretch remember please that it’s important time stretch clips [to fit loops, as example] and group of events [to fix bad timming recorded events, as example].
What I cannot think it’s in a shortcut key to timestretch :S maybe Alt before start dragging clips with the bottom dots, but don’t know with events without those dots. Or right shift key, maybe.
Thanks, however I tried to talk few times with Shannon but we couldn’t find a reason or solution for that tiny problem. Anyway, good luck! 🙂
God had to bless your eyes, and leave mine with myopia because he would be exausted after the effort, thcil 😉
My experience with mouse wheels is that few plugins, as D16 (Drumazon, Syntorus…) or Fabfilter (One, Simplon) don’t have any problem when you’re moving the knobs with mouse wheel in Podium
But others as Poise’s browser don’t work at all. However it works on other hosts.
You’re welcome, I’m very old’skool headed when thinking about problems 🙂
As I see it there are two points while dragging an event, As and Bs, where As are relative snap points and Bs absolute snap points.
Once you start to drag the event and the mouse arrives to A1 the event is lenghten until the next gridline (B1). Once you arrive to B1 the event is shorten to its original value, because Podium takes closest the relative snap point, as you just explained.
My solution would be once you arrive to A1 paint until the next absolute snap point (B1), and once you arrive to B1 paint until the next relative point (A2). Always you arrive a relative point, paint until the next absolute snap point, and viceversa.
If I understood you right this should work… well… I think O:)
Edit: also, you could do an abstract sum/subtraction to the previous/next relative/absolute snap position, if you find this is difficult to program
Thanks Frits for your present:
Lowered the minimum size of note events when resized by mouse dragging. The minimum size is now a 1/256 note instead of the current grid value.
It will help a lot! 😀
Very fast release! I like the new GUI changes, it give more consistency aspect.
Lowered the minimum size of note events when resized by mouse dragging. The minimum size is now a 1/256 note instead of the current grid value.
Thanks! I noticed there is a little bug here… it’s my well know “dancing event”. When you resize the lenght of any event (which it’s lenght is between to absolute snap points) it do unnatural things, it resize one step fowards, one step backward, step foward, step backward, commo’n and dance girls! 🙂
My snap options are snap to previous gridline, and snap to cursor and relative enabled. Best regards 🙂
@thcilnnahoj wrote:
@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. 😉
Thanks 🙂
@thcilnnahoj wrote:
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.
I understand you now. I never need more that 2 or 3 busses, that’s the reason I never asked myself how to create a new bus. And yes, it’s a good idea.
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)!
It isn’t bad, but I saw better ways to manage that. One of problems I frecuently have is that, as I cannot hide individual mixer/track strips, I prefer to use the version of the plugin that has one input and one output because it doesn’t clutter the screen with unuseful tracks. But later, some times, I realize that I need an extra input or output, and I have to mangle all the track, saving/loading plugin presets… etc. Other host as Orion are pretty cool with multioutputs plugins, you can change all the times you need the number of outputs (which create in the mixer automatically new strips). However it doesn’t support multi input plugins. Other host nice for this is EnergyXT, with multiple inputs and multiple outputs plugins. MuLAB have too a modular enviroment, but it seems to cluttered when you compare it with EnergyXT.
I’m currently “researching” other hosts’ different ways of modular routing and signal flow display (you know I was kind of against it before 😉 ), so that’s a discussion I’ll enter later on.
yes, I remember that :). I think, personal opinion, that the best modular enviroment is EXT 🙂