@Conquistador wrote:
@Zynewave wrote:
It already has a semi transparent handle on both sides. You’ve mentioned this quite a few times now, but you’ll have to create a mockup image so that I can see what you are suggesting.
Ok…here is the mock up…
These small handles could be visible on both sides of the Navigator. Even when the arrangement is fully zoomed out. That is what I have been trying to say. 🙂
The current handles do not show up when the project is fully zoomed out.
HTH
I have to agree. Unless one thinks instinctively to mouse-wheel on the Navigator, there is actually nothing to indicate the features within.
edit: Apart from the tool tip of course 😉
I might just suggest that the zoom scale be changed so that more of the existing handle is shown ‘when zoomed out’, however the arrows suggested by CQSD provide a little more information to the user.
The obvious problem is that half the time the arrows would be pointing in the wrong direction :P.
@Zynewave wrote:
@LiquidProj3ct wrote:
Hey Frits, this is a bug (I think it’s a bug) present in olders Podium version also, but I didn’t know how replicate it, now I do know. The bug is that sometimes you cannot delete selected clip in arrangement view with SUPR key (DELETE).
Create any clip in any track, and edit it (add notes/audio/…). Then rotate between profiles with F8 until you reach again the original profile. now try to erase the clip with DELETE/SUPR key, you cannot.
Got it!. Fixed. Thanks.
Way to go LiquidProj3ct! I spent quite some time trying to replicate this bug without any success.
Top effort! 😀 😀 😀
Whoa! I just voted and now it’s 50 – 50. Who’s gonna win uh? 8-[
I really, really like the Podium track hierarchy as it is. I spent a lot of time testing the compact mode betas and now it’s second nature to me.
Additionally the project and track template capabilities combined with Comp-tracks, and the recent updates to the browser and track-bouncing make this a very fast environment for me to daydream some music into existence.
I own licenses for a number of other DAWs but I just don’t use them, and so for that reason I guess I’m not affected by the desire to have Podium behave as they do.
Now which way did I vote…
:-k
I should make clear that I’m all for healthy discussion on the topic. Forums work, that’s why there are so many, and the issue of first impressions for new users is as important as it is complex.
Thanks Frits 😀
@thcilnnahoj wrote:
@aMUSEd wrote:
The only thing I would add is when you double click to expand the zoom range to full screen another double click should return it to what it was previously.
Yeah, I think so too, as I wrote in the beta thread.
I like this idea also.
Sad news indeed.
I’m sure everyone here respects the work you have put into Podium. Good luck with whatever it is and well be glad to see you back some day.
Very cool Frits.
I noticed that track colours (for the events) and the play cursor show up on the new navigator. Do you have any plans for enabling display of Segments, Loop and Punch-in/Punch-out as well?
As for the mouse function I’d be happy to have the mousewheel zoom (like on the timeline) available on the ‘lens’ 😛 as well. This would save users from going to fetch the handles all the time as they seem to snap to the full length of any event.
@LiquidProj3ct wrote:
It would be nice that you can resize the “lense” or “focus” vertically also, and move it around.
That’s a wicked suggestion +1
@LiquidProj3ct: Might be time to lose the ‘Noob’ status? I think it’s pretty well safe to say you’ve got your Podium wings now 🙂
@druid wrote:
IE, if I’m correct, STILL has never corrected their .png support bug, where images would be darker than they should be.
That problems I remember was in 5, and I was excited about 6 only for it to still exist. I have no reason to believe that they’ve fixed it, although I can’t imagine why they would want .png files to not load correctly. I may be wrong about current versions however, I stopped using IE since long ago.
Still, if I’m right, it means any program that uses MS’s built-in IE functions to view .png files probably will also be dark. Or at least, views them in a way like a webpage, like in help viewer etc. That may or may not explain all the problems, but should at least explain one of them if not more.
Nah. it’s dark in Adobe, Chrome etc. Still think it’s too dark 😛
Great update. Thx Frits! =D>
+1
I think it’s too dark (subtle?).
@aMUSEd wrote:
@swindus wrote:
MIDI control change != VST automation
You can record midi controller messages like VST automation. Have a look here:
http://www.zynewave.com/forum/viewtopic.php?p=12407#12407
You need to create the cc message first then it works. Would be better if Podium creates a parameter track on incoming cc messages in record mode automatically.And there is no mapping between controller messages and VST automation. So a knob controlled by cc messages does not create a VST automation sequence. I think that is what aMUSEd is talking about.
Oh right – I don’t really understand why if I move it with a mouse it’s VST automation but if I move it with hardware it’s treated so differently. Ideally I’d prefer to use hardware to tweak knobs where possible (many plugins do have built in midi learn on knobs)
+1
I could have sworn that I was able to do this however it may have been using MC and changing the parameter values using the mixer faders 😕
Hi all,
Just chiming in to say that once agian I’m diggin’ the updates 😀 I think that most of the bugs or misunderstandings have been worked through already.
One question tho Frits, does the record button on the parameter track(s) do anything?
Is it meant to be linked to the device automation record buttons? :-k
Thanks 😀
@bladerunner wrote:
hi phigital 🙂
try downloading again. i just re uploaded the file. i need to find some free hosting that doesn’t run out after a week!
Easy 😉