Can't believe i had to dig this one up from the 4th page...
Well, nothing as been done AFAICT, so here is a big ass bump.
FR theme: Performance/Graphics issues
-
- KVRist
- 391 posts since 28 Jul, 2003
Just fired the official release on my centrino 1.5Ghz, 1024MB ram, Line6podXT ASIO@1024 samples, task monitor shows CPU at 40%, dragging the windows peaks the CPU at 90% and playback glitches and then stops...
Same problem with ASIO4ALL with a 1024 buffer.
XT2 is simply unusable ....
Samplitude 9 Pro demo and sonar 6 web trial both run flawlessly with small buffers, so does tracktion 1.6 NFR and Reaper...
Please fix this GUI rendering problem, it really looks like all the rendering is done on the CPU (feels like running KDE under linux with with no video driver installed, with no HW accel for graphics rendering)...
Same problem with ASIO4ALL with a 1024 buffer.
XT2 is simply unusable ....
Samplitude 9 Pro demo and sonar 6 web trial both run flawlessly with small buffers, so does tracktion 1.6 NFR and Reaper...
Please fix this GUI rendering problem, it really looks like all the rendering is done on the CPU (feels like running KDE under linux with with no video driver installed, with no HW accel for graphics rendering)...
-
- KVRAF
- 3627 posts since 5 Jan, 2006 from UK
I don't know if anyone's mentioned this already, but grid drawing seems to be a massive slowdown on displays > 1280x1024.
Basically, if I have a full-screen MIDI editor and set the Grid Size to "Bar", I can zoom in and out quite happily, notes can be entered easily and velocities edited easily.
However, if I set the Grid Size to "16" or greater, then suddenly everything goes into major slowdown.
I'm certain a large part of the issue is down to the graphics primitives rendering code (and, imvho, I think this carries on to every GUI-related problem in XT2). I can have full-screen displays in Podium, etc. which use fully scalable, opacity driven primitives but with no slowdown or sluggishness whatsoever.
Basically, if I have a full-screen MIDI editor and set the Grid Size to "Bar", I can zoom in and out quite happily, notes can be entered easily and velocities edited easily.
However, if I set the Grid Size to "16" or greater, then suddenly everything goes into major slowdown.
I'm certain a large part of the issue is down to the graphics primitives rendering code (and, imvho, I think this carries on to every GUI-related problem in XT2). I can have full-screen displays in Podium, etc. which use fully scalable, opacity driven primitives but with no slowdown or sluggishness whatsoever.
-
- KVRAF
- 5350 posts since 8 Aug, 2003 from Berlin Germany
Is the performace better for you guys?
-
- KVRAF
- Topic Starter
- 1958 posts since 16 Jan, 2005 from France's Dirty South
haven't been working on some songs with xt2, but just looking at the task manager's cpu meter, it doesn't seem so...soma wrote:Is the performace better for you guys?
-
- KVRAF
- 5350 posts since 8 Aug, 2003 from Berlin Germany
Anyone else who was having problems notice any changes?
I'll keep it as an issue if I don't hear back by Friday.
I'll keep it as an issue if I don't hear back by Friday.
-
- KVRian
- 961 posts since 11 May, 2004 from cologne,germany
i had extreme problems with performance as i stated somewhere. i stated i got crackles starting at 40% cpu usage. after turning off hyperthreading (using a p4 3.2 ghz) i can push the cpu up to 80-90% with 512 samples. crackles occur occasionally but not as bad as before and setting latency to 1024 cures the crackles. will do more testing and report...
my guess is that xt2 uses (when hyperthreading is on) only one cpu for audio and the other one for graphics. maybe some people experiencing problems could try this out.
that said the "big players" show still a better performance but i have the feeling that the gap gets smaller.
my guess is that xt2 uses (when hyperthreading is on) only one cpu for audio and the other one for graphics. maybe some people experiencing problems could try this out.
that said the "big players" show still a better performance but i have the feeling that the gap gets smaller.
-
- KVRAF
- 2910 posts since 26 Jul, 2005 from dun unda
Performance issue.
Comparing with energyXT1 and XT2.
XT1 has no issues with Pitch bending.
XT2 tends to not capture every single Pitch bend event, resulting in a sort of quantized, non-smooth bend, from realtime MIDI input.
Comparing with energyXT1 and XT2.
XT1 has no issues with Pitch bending.
XT2 tends to not capture every single Pitch bend event, resulting in a sort of quantized, non-smooth bend, from realtime MIDI input.
-
- KVRAF
- 5350 posts since 8 Aug, 2003 from Berlin Germany
Are people still having graphics issues?
-
- KVRAF
- 5851 posts since 9 Jul, 2002 from Helsinki
PM-740, 2Gb, XP Pro SP2, GeForge Go6400
1. Sometimes XT2 kills ObjectDock. Shuts it down. End. Exit. Bye. Can't replicate, very strange indeed.
2. Windows leave pixel traces... sometimes.
3. Moving clips causes 5-40% CPU rise, which is pretty much the same in REAPER.
1. Sometimes XT2 kills ObjectDock. Shuts it down. End. Exit. Bye. Can't replicate, very strange indeed.
2. Windows leave pixel traces... sometimes.
3. Moving clips causes 5-40% CPU rise, which is pretty much the same in REAPER.
-
- KVRAF
- 3627 posts since 5 Jan, 2006 from UK
Still sluggish midi editing fullscreen on anything > 1280x1024 ... and I have an ATI X1950... which plays Bioshock in full detail and lovely antialiasing... go figure. 
(I wish jorgen would put the GDI=1 trick back into XT, it made everything lovely and fast)
(I wish jorgen would put the GDI=1 trick back into XT, it made everything lovely and fast)