GUI too slow

[MrTom]

I am just working on a bigger project in T2. The gui seems to react slower and slower.
Is this the way it is meant to be ?

[paladium]

it depends on what videocard (how much memory on card), system ram.

If that is up to date then something else might be
eating your systems resources.

[MrTom]

I have a Radeon with 128 MB. This should be ok.

[Lunch Money]

I haven't noticed any difference in speed between T2 and T1. It's possible that you're using it more ambitiously than you did before, or that other changes to your routine have been made. I'm not ruling out T2 being slower, either, but I for one haven't noticed.

[valley]

I'm also using a Radeon (9000 Pro) with 128MB. I've not noticed any difference between T1 and T2, and I am not experiencing UI slowdowns.

[Warmonger]

The graphics card shouldn't have anything to do with it anyway. JUCE doesn't make use of DirectDraw (not as far as I can tell, anyway), so all GUI stuff is done strictly on the CPU.

I wouldn't be too surprised if a larger project is slower though. After all, the more clips and tracks you have, the more objects JUCE has to deal with. Pretty much every UI object is anti-aliased and supports transparency, so it should all add up and slow down eventually.

How fast is your CPU though? Of course the slower it is, the worse the GUI performance will be.

[MrTom]

It is an AMD 3200+ with 2GB RAM. If tracktion cannot handle it, I would like to get the option to reduce gui gimmicks, because editing is getting cumbersome.
Removing waveforms does not help.

I have 16 tracks with ~10 objects per tracks, this is not so much. Also it is getting worse, when I use 2 monitors.

[Warmonger]

Hmm, you could try turning off end-to-end, and seeing if that helps at all. If so, then I guess you've just got too many CPU chomping plugins inserted. If not, then I'm not sure what could be wrong.

[Lunch Money]

I suspect something more sinister, but I'd be curious to know what plug-ins you use. Most of my music is pretty minimal at 10-15 tracks tops, so we're at least in the same ballpark, and I never both disabling waveforms. I use dual monitors, though I don't usually stretch the track view across both because I don't need to.

My CPU is an athlon 2600+ (a bit overclocked, but no more than a 2800+ in performance) and only 512 MB RAM. But with a project that size I do not get slow-downs.

There could be any number of culprits, including a video card and sound card conflict. But that's just one option. Smaller latencies put more strain on the CPU, as well, which will directly impact all CPU-related functions including Tracktion's redraw.

I don't have a solution for you, but at the end of the day, it's not likely that it's Tracktion itself causing you the problem; but more accurately, Tracktion is revealing that there IS a problem with your setup somewhere.

Greg

[rich_h]

I have a Radeon 9200 on an XP2000+ machine and have not noticed any GUI slowdown on complex edits, so it sounds like it could be a machine specific issue. It's not the first time someone's complained about the GUI being slow, though, so perhaps there is a latent issue that only bites a minority of people?

[tibenmik]

The GUI redraw in T2 is indeed slower than T1 - see this earlier post.

_mt

[ModuLR]

When my cpu is getting hammered, the screen redraw on my lappie definately slows (but it did this in T1, but not as much). On top of that I've got a very weak video card (laptop ATi w/ only 16M). That being said tho, T2's handling of the audio has been super stable even when it's getting taxed. It appears to handle it even better than T1 in my experience thus far.

It does appear that the GUI repaints are a bit slower tho...

[valley]

That being said tho, T2's handling of the audio has been super stable even when it's getting taxed. It appears to handle it even better than T1 in my experience thus far.

I'm glad you said that. I was wondering that myself this weekend. I had a tune that was hitting 85% CPU, and generally things tended to get a bit glitchy at that point on T1, whereas T2 didn't even seem to care. At the time, I figured it was a fluke...