Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@thcilnnahoj wrote:
Some of us are simply arguing for more horizontal space without having to zoom all the time. Please don’t dismiss it just yet… 🙁
Good night!
I’m not dismissing it. I’m just explaining why I have made an effort to avoid wasted vertical space. I’ll consider adding an option in the embedded editor region properties, to enable non-embedded editor profiles as well.
ZynewaveKeymaster@swindus wrote:
@Zynewave wrote:
How about if instead of resizing the timeline area, you zoom in on the timeline and the vertical track size. Perhaps scroll the timeline so that the loop section is outside the displayed range. Any sudden jump in speed?
No, still sluggish.
The sluggish movement stops when inserting certain FX plugins on a track. The sliding/scrolling is slow with an empty project. Just a master track and a 4 bar loop. When I insert IIEQ (equalizer) as insert on the master track the sliding is fast as normal. This also works with Devastor or Fazortan from D16. Now thats crazy …..
:-s That’s just weird.
Does the plugin “fixing” happen both with the arrangement powered on/off?
How is the Windows task manager CPU indicator behaving during all of this? Maybe the inserting of the plugin fixes a denormal issue.
ZynewaveKeymaster@thcilnnahoj wrote:
Besides the fact that I personally consider the time-locked editing a nice feature, the other consideration is space efficiency. In your screenshot I see you have added a timeline ruler to the embedded profile. I assume you also have a scrollbar then at the bottom. That’s a lot of vertical pixels that can be avoided when the embedded editor shares the timeline navigation of the arrangement editor. Vertical space is a limited resource, especially if you also have the mixer open, and these days it seems that monitor resolutions are growing wider (16:9) instead of taller.
August 5, 2009 at 17:57 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.August 5, 2009 at 16:27 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.August 5, 2009 at 12:30 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.August 5, 2009 at 12:28 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.August 5, 2009 at 12:24 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.August 5, 2009 at 10:53 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.August 5, 2009 at 10:29 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.August 5, 2009 at 10:06 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.August 4, 2009 at 23:30 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.August 4, 2009 at 15:37 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymasterYou need to create the send parameter track by right clicking the send you want to automate. So the resulting parameter track should be named something like “Send (Send 1)”. Then you need to turn up the send dB on the send track. Just like level/gain automation, the send automation is applied as an offset to the set send level.
August 4, 2009 at 11:25 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
