Slow meters

Discussion about: tracktion.com
RELATED
PRODUCTS

Post

dee ess pee wrote:For me I dont think metering is redundant, I need to know a good starting point in range for the centerpeice of the mix to hover at. I cant mix into a limiter or compressor on the master because I send out to a mastering house.
Whats that got to do with it? You have a master fader, and meters for the mix buss..

Post

Beno wrote:Well did you check the meter speed settings in the T2 settings.
Ben
I tried this yes. It's not really "speed", but they are very choppy

Post

platinumears wrote:
dee ess pee wrote:For me I dont think metering is redundant, I need to know a good starting point in range for the centerpeice of the mix to hover at. I cant mix into a limiter or compressor on the master because I send out to a mastering house.
Whats that got to do with it? You have a master fader, and meters for the mix buss..
This discussion is not about whether meters are needed or not.

In my work, they are very useful, and perhaps one of the most important components of the software. Which is mainly why I started this thread soley on the basis of the meters not responding properly, despite other portions of the software's UI not responding as well.

Post

have you tried Inspector?

Post

I have inspector, and it is my main metering plugin.

This is one of the plugins that's UI slows occasionally. Doesnt happen as so anywhere else, not even T1.

Post

I hate to say it, but I'm getting the same behavior on my Inspiron 9100 (P4 3.2, 1GB RAM, onboard sound). After some more testing, I'll see if I can figure out if this is a bug or not.
Image

Post

it's been brought up here.. http://www.kvraudio.com/forum/viewtopic ... hlight=gui

I believe the repaints in T2 are a wee bit slower... seems like something which could be optimized.
ModuLR / Radio

Post

Its more than a "wee bit here" :( Significant difference where things in T1 run super smooth, in T2 update once a second if that much.

The time display even skips a bar sometimes!! :(

I have to turn up my buffers to get T2 to play without glitches as well. Im really confused, I just want this to work properly. Wish at the very least the audio was more stable like the other reports. It does seem better when I raise my buffers, but similiarly it goes just as well in T1 with higher buffering.

Post

I just checked both with and without Hyperthreading enabled. There was no difference. Also rebooted from a very bloated XP install (60 processes and 500MB RAM usage with T2) to a much cleaner one (20 processes and < 200MB RAM used), and similarly no difference. Loaded up on heavy plugins to increase CPU usage until the meter's constantly in the red (7 instances of the Legacy Cell demo), and still no difference.

I'm starting to think this is by design. That said, I'm only noticing a difference of a factor of 2; that is, T1 seems to refresh twice as often. Maybe we can get an option to set the "frame rate" for T2?

dee ess pee, if it's really that slow, that must be a bug. I've run T2 on a P2-400, and while updates are slow, I'm still getting at least a couple updates every second.
Image

Post

I've vst bargraphs on my site (Plugins/Tools then "Phare").
But maybe, they are slow too. I don't know.
Daniel.

Post

dee ess pee wrote:I loaded the t2 demos now that I have bought it and the meters are really choppy and so is the time.

Is this typical? I can easily run projects of same size with higher cpu load in another host with perfect metering and screen updates.

Is there something I can do or am I doomed to small projects if I want this program to work smoothly?
Would the free PSP VintageMeter work for you? VU and PPM monitoring, and if you click on the name, the back panel appears and has controls for vu integr. time, 0 vu ref. level, meter delay, ppm intgr. time, ppm return time and 0vers counter.

If you made a template with one meter on several tracks and a master, you'd have very visible, responsive meters.

Post

Ill mention again to be thorough and help the bug-squashing process: It is not JUST the meters, the entire UI is very slow and many VST's that have dynamic interfaces slow as well.

This is not the case in T1 or any other host.

If someone has ideas how I can track this down, id love to make a formal bug report.

Post

mentioned it to some time ago. the whole gui IS slow. and much slower than t1. for example recording with big meters on for 8 tracks isn't possible at all. many dropouts and sluggish behavior. i have a pentium m 770 with x700 gfx and even halflife and doom3 are running smooth on it ;)
i need a lunch break

Post

I have noticed that the meters don't seem to respond instantly like they do in other applications actually. For example, if you turn on click, some clicks are visible in the main meter and some are clearly skipped - like the rendering is out of sync with the tempo so some just dont get displayed.

steve

Post Reply

Return to “Tracktion”