H-manThanks Frits.
Another giant leap for Podium!
H-man@Zynewave wrote:
PS: Possible bug? I found at one stage that I lost the ability to delete events on a track with the ‘delete’ key when there were a large number (40+) of copied or cloned events. Right click – delete would still work tho.
Hmm, the number of events should not matter. Are you sure that the tracks region had keyboard focus?
Possibly not. I will try to see in the next day or so whether I can recreate the problem and if so, provide the specific environment in which it happens.
H-manH-man@Conquistador wrote:
Please I really need two or three levels more of vertical zoom in the piano roll, it’s difficult for me see the notes with big screen resolutions, I need see the notes more bigger
Thx!
I was thinking the exact same thing today! 🙂 Totally agree.
+1
(Oh wait, I was thinking it yesterday 😛 ) The zoom does max out before you reach the ‘comfortable’ size.
H-manHi all,
I just thought that I would chime in and report that I am very happy with the 2.08 new features and fixes.
Better that anything is that testing the Comping features has got me to back playing my Guitars and not just twiddling dials and piling effects 😆 .
Most important for me is that 2.08 has got to the point where there is quite a lot of flexibilty in how one can set up the recording (auto comp activate etc.) and the resulting changes to the Punch-in/out make perfect sense IMHO.
Note that whilst possibly a little antiquated, I think that the existing Punch-in/out is a feature worth retaining in its current state.
One thing that I like (pre-existing feature I think) in Podium is the way gain, stretch and now track-swiching controls on the events become active on ‘mouse over’ which makes the Comping process all that much easier and faster.
The only aspect of the new features that I had found a little confusing (Thx for raising Mike) was that the Comp Track event (first one) would commence from the cursor position and not the first loop marker, requiring the user to have to slice the Comp track at the first loop marker to get access to the other (sub) tracks.
Maybe the Comp track event could be set to auto-slice at this point? I get it that this can be remedied using the punch-in marker however I feel that new users will find this confusing and ‘eat’ the half-hour or so that I did until I figured it out.
Just a thought. Other that that I am really pleased with the addtions.
Brilliant as always Frits!
Ben
PS: Possible bug? I found at one stage that I lost the ability to delete events on a track with the ‘delete’ key when there were a large number (40+) of copied or cloned events. Right click – delete would still work tho.
H-manNo support for skinning at this level yet that I know of.
You could however set the panel colour to extreme white or black 😉
H-man@Zynewave wrote:
Thanks. I’m going away for the holidays until the 26th, so merry christmas everyone! 🙂
Yeah Merry Xmas to you too man, and thanks for another year of fantastic updates!
I fired up an old PC that has been sitting in the corner for ages and noticed that it had Podium Ver. 1.88 on it. An experience like that really drives home just how far Podium has come on recently.
Thx again,
Ben
H-man@aMUSEd wrote:
Pity. I can’t understand why this isn’t seen as more of a priority. Is no-one else using automation with softsynths apart from me?
Yeah I agree with you for sure. The way I see it though is that Frits is doing fantastic work on some other features so for the meanthime you just apply the work-around as detailed above. The manual curve/parameter editing features are pretty sophisticated.
Gotta thank you for this one tho:
@aMUSEd wrote:
Recording parameter automation will create curve sequence events starting at the beginning of the arrangement instead of at the current play position.
H-manI also just noticed that you can re-commence the recording on the same composite and rack up another 5 takes which is cool as well 🙂
H-manHi Frits,
I’m pretty happy with this new implementation. Can you tell me though what control dictates the inital length of the composite track before it starts looping?
I was trying to use the loop markers howver the recording would go back to the start before the loop marker end.
Is it the punch in markers even though they are not active?
Also, when comping, what is your intened method for building the various parts on the comp track? Split up the existing comp track or delete it and create new events.
Either works fine, just curious as to your intended work flow.
H-manSounds cool. Looking forward to testing. 😀
H-manFrits, I think technically you have to be a doctor or scientist and I have to be some sort of internationally recognised regulatory body, however, ignoring these minor detials, I nominate you for this years Nobel Prize.
Looks awesome.
H-manThanks for this update Frits 😀
Fantastic.
H-man@Zynewave wrote:
Beta9 is uploaded, with the post-bounce gain controls. Let me know if you experience any problems.
@H-man wrote:
I also strongly agree with the others above that the PAN, if not functional on the bounced tracks, should be either locked or not visable.
Currently the text written on the pan slider/dial is dimmed, to indicate that it is inactive. I don’t think the pan control should be hidden, as you may want some indication of what the pan is set at, even when the track is bounced.
Okay, sounds great. I wasn’t aware that the bounced track could/would reflect the Pan position of the track(s) being bounced. Perhaps that is because Pan & Gain were inactive on the bounce track previously.
I look forward to testing 😀
H-manYep, makes sense :). I always found the inability to quickly adjust the gain on the bounced track a bit frustrating.
I also strongly agree with the others above that the PAN, if not functional on the bounced tracks, should be either locked or not visable.
2.06 is looking like another excellent update!
Ben