Hello all.
Just to mention, that I seem to be having less issues now with the firewire to thunderbolt adapter being used, than ever before. Just using firewire 1394B or A.. over many different systems now, always seemed problematic and issue bound....even before moving to this new home...I have been trying to get prestine recording using firewire....and not getting that state of bliss.
One thing I am noting of late...Using my specified system in my profile, and newly acquired parts/refurbished ones through rma..and power supplies, and Power surge protection, ..right down to electrician work done on the main breaker box....to help eliminate noise and anomalies, I have had in past, with the prior build Just past....
The new system rocks...is solidly stable...no over clocking, ...The cpu fan sometimes when booting up, is not up to speed, and the motherboard complains it is not sufficient to cool the cpu....I have to set the fan speed in bios to turbo...and save...to solve that, But it does not get saved..So I have to do this periodically...not all the time,...So a new fan for the cpu is next up to fix this issue.???.or a bios update of the MB?...not seeing things right? or monitoring right?
Once booted, I turn off internet, and other features this board has, and anti virus protection, if I am going to work in any DAW..I have done some tweaks to power management, and turned off auto updates on a few programs running in the background usually.....but have had internet on while working in Sonar for online help recently....Internet and my mixing desk and sonar...It does work now, when it would not work before, just using Firewire add on card, with proper chipset of manufactures suggestion to use...but claimed that it has issues with internet nics and wi fi....
Sonar so far is doing fine on this thunderbolt system so far, recording and mixing, and applying vst 2s, and the sonar stock plugs.......
Except this odd thing when opening Sonar x3d...new projects or already made ones...it states "the selected audio driver is not available" ...clicking ok continues to opens the program.
All is fine after I use the record or play function once, and nothing happens, with any audio or midi. stopping the input or playback seems to reset or find the ASIO 2 audio device...it seems to be fine there after doing this play or record before doing anything else first.
I just stumbled onto that ...Maybe editing the performance tabs , and selecting the audio device again might work also?...but I have not tried that yet.
Not that this is a Sonar issue...could be the thunderbolt connection is just slow to be detected.?...or not coded for properly in Win 7 yet?..and I found my own work around in Sonar...Does not do this with Acid Pro 7.0 or other programs I have installed for music, using the same firewire audio desk..on the thunderbolt port.
Still all in all, I am impressed with it working so well over this past month of learning from the manual.....and not having any issues other that that detection, or connection when opening the program with the firewire audio device on the thunderbolt port line....
Infact the audio seems to be awesome in terms of ...no clicks or pops, Lowest latency "64"...but it does drop out here and there...but does not get recorded....So I can live with that...for when we do dubbing and midi work...I guess.
I am using 24bit, and trying 44.1 with the lower buffers 64 in testing......But can go to 96, and suggested 512 buffer.
When I record the band mates, with this new system so far...I push it up to 512 buffer on the audio mixer, but keep it 44.1, 24 bit and record all at once...with no monitoring...Just Live tracking...so no need to worry about latency just yet....and the best sounding recordings and performance, can be made without worry of clicks or pops or drop outs...when I set it Like that...for them sessions.
I can also monitor from the mixer...so nothing is really going to make me go that low in buffer settings "64" or need to go lower than 128......Just that I can...if need be.
So ..in all Sonar x3d is rocking the house...The way I use it...for now.
Thanks again!!!
To the fine folks here, and else where, who put up with me and my system woes, and tried to help get me sorted, started, restarted, and rebuilt, and the calk walk team, and Allen and Heath...That got me to this almost state of bliss ...
Just getting started and fiddling around with the plug ins in Sonar since the new build...and man what nice outcomes so far....in renderings.
Of course, One thing lacking in this Producer Product...is the ability to make MP3s of varying degrees of...Bit rates.
I know I can buy the MP3 plug...But really it should be tossed in as a free be plug in. ...by now?...so one does everything In Sonar....as a producer would or should these days?
So I keep Acid Pro 7...to do the deeds...and touch ups for that process.
And it all works....Fantastic!
As I settle in, and start using more and more of the Program features and such....I am sure that with my understanding, and stable system coming to be as it is, and another one hopefully on the way and arriving tomorrow to use Pro Tools....I will have something finally come to finalizing and making my Studio complete, and music more enjoyable to do, without too much worrying about tech hats and troubleshooting...for a bit of time...and more mead to enjoy without hair loss.
Hope the new updates coming soon from CW solve most of the issues People are having, and to further make this program the best it can be!
Oh ...I also noted when placing my mouse in the wave edit window...the counter bar or line bar that moves when play or record is pressed, kind of goes buggy a bit, but does not cause any funny business really...it just seems to be rather stiff in moving...If I move my mouse off that wav window pain....all is fine.
Just something I think I have seen posted here over time...that I see happening sort of here.
Might be something CW might look into?...or is it video card specific?
Well back to the Manual...I need to know how to select tracks more exactingly for mix down...and using the mouse and selecting the tracks lasso feature is kind of hit a miss when not zoomed in, and when zoomed in to the nth degree, it takes a bit to get to the beginning of the some times long tunes to set the marker....and all kinds of lost, truncated, or unselected tracks dropped , as the view goes up and down and all over when lassoing...to loose focus...can occur...and have done in some attempts I did with that method.
I feel something more like a permanent select or loop region on the time line, selecting all tracks in that range set unless muted...might help people set the right start and end points easier....?
So I will check that out next....in the Manual...if it can be done like that...It would surely be better than the lasso method.
Just my observations so far....fiddling around...
Cheers!
Sir Les