I have an "interesting", repeating Sonar X1 issue that I would like to diagnose.
 
First my system specs. (a few years old, but this is just a hobby for me, and the gear meets my needs):
Windows 7 64-bit,  3ghz Core 2 Duo, 8 GB RAM, (3) SATA 7200 RPM drives (3rd drive is used just for multi-boot for Windows XP), Creative SoundBlaster X-Fi Platinum audio card.
 
Sonar X1 is a fresh 64-bit install of Producer Expanded, with the (correct) "C" and D" updates installed.
The program is installed on the system drive, with all the Cakewalk content, VST's, and multisamples on a 2nd drive.
Everything appears to be working as it should, UNTIL I start to load an existing project (and this occurs even if the "project" is nothing more than the default, empty audio and MIDI tracks using the default normal template):
 
After selecting the project to open, Sonar will "lock up", the Sonar window will essentially go blank,  and display the "not responding" message in the Sonar window title bar.  After several seconds (around 10 to 15 seconds average), the screen returns to normal, with the project loaded, and everything - apparently - functioning normally.
 
So, any idea what might be causing this temporary "lockup", and if it might be indicative of some other issues that might develop as I start putting "real" projects together?
 
Thanks in advance!
 
Randy

It's "normal" and happens to me all the time when opening large projects that contain many plugins and VST instruments. I guess it takes some time for SONAR to start all those plugins. There could be some kind of indicator for the user saying "hey, i'm still alive - do not panic"...

There is a progress bar in the Control Bar / Transport Module during project open.

rivers88


I have an "interesting", repeating Sonar X1 issue that I would like to diagnose.
 
First my system specs. (a few years old, but this is just a hobby for me, and the gear meets my needs):
Windows 7 64-bit,  3ghz Core 2 Duo, 8 GB RAM, (3) SATA 7200 RPM drives (3rd drive is used just for multi-boot for Windows XP), Creative SoundBlaster X-Fi Platinum audio card.
 
Sonar X1 is a fresh 64-bit install of Producer Expanded, with the (correct) "C" and D" updates installed.
The program is installed on the system drive, with all the Cakewalk content, VST's, and multisamples on a 2nd drive.
Everything appears to be working as it should, UNTIL I start to load an existing project (and this occurs even if the "project" is nothing more than the default, empty audio and MIDI tracks using the default normal template):
 
After selecting the project to open, Sonar will "lock up", the Sonar window will essentially go blank,  and display the "not responding" message in the Sonar window title bar.  After several seconds (around 10 to 15 seconds average), the screen returns to normal, with the project loaded, and everything - apparently - functioning normally.
 
So, any idea what might be causing this temporary "lockup", and if it might be indicative of some other issues that might develop as I start putting "real" projects together?
 
Thanks in advance!
 
Randy

 
 
That's normal my friend! It's because you load stuff in the background VST plugins etc..
That means that actually have start working with real projects and X1.  
Has been like that as long as I can remember...

I appreciate the feedback!

I do have several "heavy duty" plugins behind the scenes, so if what I'm seeing is considered "normal", I can live with that.

Thank you for your help! 

Randy

Wait until you have a project with a lot of samplers in it. Its always fun to bet on when it will be ready. its really not that bad.

Keep in mind that with 64 bits things want to be in memory.

This has answered a question I have had for quite some time...sometimes I have to wait around 5- 10 minutes...is this excessive? I am only running 4 gigs of RAM on a dual 2.4 core...it's a Dell XPS. Would doubling the RAM improve this issue? It's not something critical, but I would like to speed things up if I could! Thanks David

Frostysnake


This has answered a question I have had for quite some time...sometimes I have to wait around 5- 10 minutes...is this excessive? I am only running 4 gigs of RAM on a dual 2.4 core...it's a Dell XPS. Would doubling the RAM improve this issue? It's not something critical, but I would like to speed things up if I could! Thanks David

I don't know much about hardware but I think it's a question of both RAM and Harddrives loading time.

I use SSD Hardrives with 24Gb RAM (Win7 Ultimate) and everything loads in seconds. I use very heavy orchestral VSTs with a template that loads a minimum of 80 tracks so that's around 15 VST synths.

A while ago I read something about not loading each synth to the brim. So if it takes for e.g. 16 instruments, you load 8 into. For some reason unknown to me, if you load 2 of the same VST synth with 8 each instead of 1 with 16 instruments, it makes a difference. It's counter-intuitive to me, but I tried it and the computer handles everything smoother.

It would also depend on whether you softsynths stream from disk or have to load everything into memory.

scook


It would also depend on whether you softsynths stream from disk or have to load everything into memory.

Hey scook


If you asking me(?) - a bit of both. I use VSL and EWQL mostly and they have streaming from HD settings. But I also see the RAM usage on the UI of the VST interface climbing up. So a bit of both I guess.