Slow screen display, sonar 8.5.3, after machine transplant

Author
peterpan
Max Output Level: -90 dBFS
  • Total Posts : 20
  • Joined: 2012/05/02 10:58:36
  • Status: offline
2012/11/09 18:08:43 (permalink)

Slow screen display, sonar 8.5.3, after machine transplant

Over the past week I had to migrate my whole system to another machine, due to a persistent motherboard problem. It was a pretty lateral move, from one old XP SR3 machine to another, both Intel P4 hyperthreaded (but no multi core), both 4 Gig of Ram and both fast 7200 RPM SATA HDs. The CPU on the new machine is marginally faster, 3.2 Ghz instead of 3.0. Anyway, as sonar is my most CPU intensive application, I was pretty happy to see the same project that required over 50% CPU usage to drop to less than 30% on the new one. Yet when I PLAY a project, despite there being no problems whatsoever in the sound or any problems with CPU or disk usage, the NOW time marker and the whole user interface now staggers along. All the screen updates are now sluggish, as are responses to my mouse click commands. This is going to be a problem when I try to manually punch in as I often do when touching up vocal tracks. At first glance, i thought surely this is a video card issue. My old machine had its own separate video card, while the new one is currently using motherboard video. I have a video card on order, but I'm skeptical. I'd think if Sonar were having trouble keeping the screen and UI updated, the CPU meter would be showing the system straining. Not so. I've tried to select Sonar in my XP task manager and boost its priority, but nothing changes. Any ideas?

-Peter Pan... second star to the right
Sonar 8.5, Win 32 XP pro, SR3.  M-Audio/Delta 96/24, ASIO

#1

1 Reply Related Threads

    peterpan
    Max Output Level: -90 dBFS
    • Total Posts : 20
    • Joined: 2012/05/02 10:58:36
    • Status: offline
    Re:Slow screen display, sonar 8.5.3, after machine transplant 2012/11/09 18:37:52 (permalink)
    Never mind... I solved my own problem, but for the benefit of anyone else who might run into this, it was a RAM memory configuration issue. This (newer machine) is a DELL "Optiplex GX620", and it has 4 slots for DDR2 memory, two marked with white tabs, the other 2 with black. Anyway, the two black slots each had a 2 gig ram module, and moving them both to the white slots changed everything. Apparently the memory manager, though making use of all the memory either way, offered much better performance one way than the other. Odd symptoms though!

    -Peter Pan... second star to the right
    Sonar 8.5, Win 32 XP pro, SR3.  M-Audio/Delta 96/24, ASIO

    #2
    Jump to:
    © 2025 APG vNext Commercial Version 5.1