Interesting... I've noticed t2 having very sluggish level line meters. Anyone else have that problem? I'm referring to each line out and the master out meters
RonC
T2 - Sluggish dB level updates?
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
you can adjust the refresh speed of meters in the settings.
Someone shot the food. Remember: don't shoot food!
-
- KVRist
- 171 posts since 11 Aug, 2004 from Toronto, Canada
This note is from an ongoing journal I've been keeping since starting to work with the T2 demo:
Screen redraw rate has taken a bit of a hit. Seems to be directly tied to how busy the screen is (ie number of simultaneous tracks, clips, etc.) combined with CPU hit. All things being equal, however (ie same project, same screen information, same CPU hit), T1 has less trouble with screen redraw (smoother). The master counter was used as the reference point (particularly the smoothness of the ticks counter), but this affects all 'active' screen info (ie smoothness of cursor scroll, smoothness of VU meter response for both tracks & master, etc.)
I'd like for others to try this out: using T2, open up the new 'Everyone Wants You' demo track, set the project cursor to bookmark 6, then play back. Keep an eye on the 'smoothness' of the project counter rollover in the master section, specifically the ticks counter. Having gotten a feel for it, close T2, open T1, and open the same project and playback from the same bookmark. Watch the counter - notice a difference in smoothness/response?
Interested in the group's comments on this...
_mt
Screen redraw rate has taken a bit of a hit. Seems to be directly tied to how busy the screen is (ie number of simultaneous tracks, clips, etc.) combined with CPU hit. All things being equal, however (ie same project, same screen information, same CPU hit), T1 has less trouble with screen redraw (smoother). The master counter was used as the reference point (particularly the smoothness of the ticks counter), but this affects all 'active' screen info (ie smoothness of cursor scroll, smoothness of VU meter response for both tracks & master, etc.)
I'd like for others to try this out: using T2, open up the new 'Everyone Wants You' demo track, set the project cursor to bookmark 6, then play back. Keep an eye on the 'smoothness' of the project counter rollover in the master section, specifically the ticks counter. Having gotten a feel for it, close T2, open T1, and open the same project and playback from the same bookmark. Watch the counter - notice a difference in smoothness/response?
Interested in the group's comments on this...
_mt
-
- KVRAF
- 1974 posts since 21 Jun, 2002 from Earth
So I just performed your test, and I think you are correct in your assesment that the counter is definately smoother in T1. Maybe it's not repainting as often in order to salvage cpu cycles. 
ModuLR / Radio
-
- KVRAF
- 10815 posts since 26 Nov, 2004 from UK
-
- KVRist
- 171 posts since 11 Aug, 2004 from Toronto, Canada
Modulr:
Thanks for giving it a test. This does seem to suggest that compared to T1, the overall redraw response in T2 is sluggish as more visual information is introduced. I used the counter as an example of this behaviour. Of course, the actual playback/CPU response doesn't seem to be affected here, but with busy projects the GUI might start to chug wheras in T1 it would be smoother.
_mt
Thanks for giving it a test. This does seem to suggest that compared to T1, the overall redraw response in T2 is sluggish as more visual information is introduced. I used the counter as an example of this behaviour. Of course, the actual playback/CPU response doesn't seem to be affected here, but with busy projects the GUI might start to chug wheras in T1 it would be smoother.
_mt
-
- The Teach
- 8273 posts since 23 Jul, 2002 from flatness
in terms of meters and the counter i think youre right ... T1 is slightly smoother ...
... but TBH (and ive thought this since the first beta i tried) OVERALL the T2 GUI feels quicker and smoother to me ... perhaps theres been a tradeoff between some elements (interactive ones ??? ) being assigned more cycles at the expense of other bits of the interface ???
slainte
rob
... but TBH (and ive thought this since the first beta i tried) OVERALL the T2 GUI feels quicker and smoother to me ... perhaps theres been a tradeoff between some elements (interactive ones ??? ) being assigned more cycles at the expense of other bits of the interface ???
slainte
rob-
- KVRAF
- Topic Starter
- 6490 posts since 14 Jun, 2004 from Rochester, NY
maybe this is changed in the new .4 version demo? no time to test yet 
RonC
RonC