Topic: 2.16
- This topic has 19 replies, 13 voices, and was last updated 16 years, 9 months ago by
DFusion.
-
May 26, 2009 at 11:48 #1943
ZynewaveKeymaster- Added a new resizable timeline navigator to the top of all editor windows. This replaces the horizontal scrollbar in the default setup. The navigator shows a miniature graphic of the full duration of arrangements, sounds, note and curve sequences. The current zoom range is displayed as a sliding transparent pane on top of the miniature. The zoom range pane can be dragged and resized to quickly adjust the zoom.
- Clicking in the navigator outside the zoom pane sets the zoom range centered around the clicked position. Double-clicking zooms out to the full range. Double-clicking either of the left/right zoom resize handles sets the zoom to the start/end of the sequence. Shift+click+dragging selects a zoom range. Middle-clicking sets the edit cursor position.
- Using mouse wheel on the navigator zoom pane will zoom in and out similar to how mouse wheel zooming works on the timeline ruler. Using mouse wheel outside the zoom pane will set the zoom range centered around the mouse position.
- Loading setup files created with earlier Podium versions will automatically be converted to use the navigator region.
- The old dual-purpose “meter” region is split into two separate “velocity” and “curve” regions.
- The embedded editor previously part of the tracks region is now a separate region.
- Clicking the “insert new” button in the profile properties dialog shows a popup menu instead of the previous “insert new region” dialog.
- When loop-recording MIDI notes, note events are only created if there is no overlap with already recorded notes.
- Fix: The transition from a spline curve point to a line or bar point were not always accurate.
- Fix: The 64-bit engine produced noise when outputting to 24-bit ASIO drivers.
May 26, 2009 at 14:03 #15200
ConquistadorParticipantThanks! 🙂
May 26, 2009 at 15:51 #15201
KlempererParticipantThe way midi gets recorded in loop mode sounds an excellent addition to me, thanks!
May 26, 2009 at 18:31 #15203
DFusionParticipantThanks 😀
I love the new navigator window.I have also found a bug….
If you add automation to a track the cpu usage gets 3Doubled.The song i was working on uses 7-9% in windows taskmanager but when i added automation to the filter cutoff on a track with Vanguard the cpu usage went up to 30%.
When i deleted the automation track it went down to 9% again.
May 26, 2009 at 19:29 #15204
aMUSEdParticipantVery nice.
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.
May 26, 2009 at 19:38 #15205ConquistadorParticipantNot seeing a x3 increase in CPU here. Just tried to automate a parameter in Trilogy. 10 -12 % fluctuation in Windows task manager (Max). A few percent difference on Podiums CPU meter. All that with at least 4 other apps running at the same time. Perhaps it is Plugin specific.
Running Vista SP2. Final not beta.
May 26, 2009 at 19:48 #15206DFusionParticipant@Conquistador wrote:
Not seeing a x3 increase in CPU here. Just tried to automate a parameter in Trilogy. 10 -12 % fluctuation in Windows task manager (Max). Perhaps it is Plugin specific.
Running Vista SP2. Final not beta.
Thanks for testing it 😀
I am using XP SP3 and i also encounter allot of random crashes with this version for some strange reason.May 26, 2009 at 23:09 #15208aMUSEdParticipantMaybe it’s a Vanguard thing – I’m not seeing it either – had a fairly intensive project with Alchemy and tried deleting all the automation but it made no difference to the cpu hit.
May 27, 2009 at 01:40 #15209
thcilnnahojParticipant@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.
Anyway, congratulations and thanks to you, Frits, for another fantastic feature implementation!
May 27, 2009 at 06:39 #15210
maximiliansParticipantvery cool 8) thanks Fritz!
May 27, 2009 at 07:43 #15211
rinxaiParticipantA sweet surprize,
thank you 😀
May 27, 2009 at 12:16 #15212DFusionParticipant@aMUSEd wrote:
Maybe it’s a Vanguard thing – I’m not seeing it either – had a fairly intensive project with Alchemy and tried deleting all the automation but it made no difference to the cpu hit.
That is my guess too or that it is one of the other vst’s i have in that song.
I will do some more testing to see where the problem is 😀
May 27, 2009 at 12:38 #15213
H-manParticipantThanks 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.
May 27, 2009 at 21:02 #15214
Mike GParticipantNice, thanks frits.
One very minor suggestion, when you click outside the zoom range, I feel the default should be to keep the same vertical position as previously, not to set the top of the zoom range to where you clicked.
If you did want to scroll the vertical zoom it feels like you should scroll down after clicking.Thanks,
Mike GMay 28, 2009 at 06:38 #15218
swindusParticipant@Mike G wrote:
One very minor suggestion, when you click outside the zoom range, I feel the default should be to keep the same vertical position as previously, not to set the top of the zoom range to where you clicked.
If you did want to scroll the vertical zoom it feels like you should scroll down after clicking.Same here.
- The topic ‘2.16’ is closed to new replies.