CPU/Disk meters...why aren't they there?

SHTUNOT wrote on 1/22/2002, 5:05 PM
When I use cubase I have them, I downloaded the Sonar demo and IT has them, and I go back to mixing a song in Vegas Video 3 and I'm stunned that it wasn't added.

How is everybody elses experience with mixing without them? Has anyone's system ever crash on them when they peak/max out their cpu or disk? A while ago I was mixing in cubase and it crashed on me when my cpu got to around 85-90%. Luckily I saved often but I couldn't believe that it froze. Now that I'm using Win2000 and VV3 I'm able to use even more plugins per song than I did in cubase but I'm still afraid of being in a mixing session and having it lock up!

Any tips...ideas? I love how much more I can push my system. My mixes sound so much more clean/tight/clear/FULL sounding. Should I be worried? Will this feature ever be implemented again? Why/Why not?

[BTW...the Sonar demo is a fully functional version that times out in 30 days. Totally amazing piece of software! One question for everybody...How many similarities between Vegas Video 3's audio side and Sonar can you pick out? I'm having a bit of a feeling that I've been here before so to speak. Either graghically {interface} or functionality.HMMMM?]

Comments

Control_Z wrote on 1/22/2002, 6:34 PM
I dunno anything about the audio products, but I know with modern computers you want a program to use as much of your CPU as it can get away with. There's no need to monitor the CPU - what are ya gonna do. stop it if it gets used too much?

I have Prime95 running all the time anyway, so my CPU is never below 100% 24/7.

We could use disk throughput meters though.
wvg wrote on 1/22/2002, 8:53 PM
Congradulations Shtunot, you're the first poster to make it into my bozo bin (ignore this user feature) because of your endless ranting and obsession over cubase. By the way if you knew anything about how computers and operating systems function, which clearly you don't... you'd realize how stupid your latest rant is. Forget CPU meters. If this forum had a bozo meter, you'd pin the needle to the right on just about every post.
SHTUNOT wrote on 1/22/2002, 10:44 PM
Dude...
1. I compare to cubase because thats all I know besides protools. I do not like cubase...I repeat...I do not like cubase. Thats why I'm here.
2. If I'm mistaken and someone corrected me I'd appreciate it.
3. If Sonar/Cubase has it then I'm confused and would like an explanation[ie:I'm not bitchin' about anything! Just asking!]. Did you ever here the old saying of "There are no stupid questions?" It wasn't a rant dumbass!!! I gave a personal experience that I had a short time ago with someone elses program[cubase]. My cpu meter was almost maxxed with all the plugins I was using in a mix...it froze on me and I didn't save one or two changes prior. I was able to re-tweak my settings and saved of course more often afterward. Now I don't have a cpu meter to work with...so I now don't exactly know how much overhead I have to play with. Ok I could try to just keep using plugins untill it crackles and pops on me then back off a bit...sure. But thats why I asked for other peoples opinion on their working technique/experiences.
4. WVG...If your opinion is that a crash with VV3 is not likely with using win2k, even with my CPU maxxed then thanks for the info. I'm not sure why but thanks for the vague answer. One thing though. Dude...If you cannot control yourself and talk to me in a rational/intelligent way and "discuss" a issue, please do not respond to any more posts of mine[why are you wasting your time anyway?]. I am not here to piss anybody off and I'm not going to get into a stupid argument with you. If I give someone some info and you see that I'm incorrect...correct me...trust me I read it and I take note. I'm only human and I make mistakes.
5. Control_Z...Like I said dude my system crashed with cubase and I'm just scared that now I can't even watch how much I'm pushing my system. Have you had any experience with pops/crackles/drop outs/clicks when you add to many plugins to your mix? Has it crashed,froze? If not then I'm relieved because I'm glad to be away from all those PROBLEMS I had with cubase.
5. To spell it out for you [wvg]...I don't understand the workings of not having a CPU/DISK meter. Obviously SOFO thinks this is a great idea and I want to know why...not "JUST BECAUSE"! I am ASKING for help from people who have the time to educate me. Isn't that what the forums are for? I'm not sure of what I said to make you think that I haven't a clue about anything...I'm learning constantly and daily I'm getting better at what I do. I just completed a "Music Electronics degree" at a college so I can't be THAT dumb [can I?]. And I'm still getting hired for audio/video projects so it looks like I'm doing something right. Clients are leaving happy!... I'm just trying to stay consistent with that. Hence my questions, good and bad...DEAL WITH IT DUDE!

I admit recently I've been a bit of a bother to said VV3 because of all the delays of VA3. With a lack of responses that everyone got from SoFo...the namm show "no booth"...I fell victim to a rumor. Thankgod it was just that...keeping my fingers crossed. But to think that video had a priority much higher than audio bugged me a bit. My post was not meant to show a weakness of VV3 but to have me understand how to use it "BETTER".

Thankyou in advanced for any tips/experiences.


BTW...WVG...I havent read many posts on you correcting me on a bad opinion that I have given to anybody. So if I make a post and you haven't corrected me, how do I know I'm wrong? And what was the basis on your "BOZO" award.I really do not appreciate the post you did. I have read other posts that you made for other people and you "seem" to know what your talking about. Why you decided to vent in my direction is confusing...I really didn't say anything that deserved it. I'm not the one wrong here. And like it or not I'm going to ask questions whenever I feel like it. I'd like a response...but don't do me any favors. Later...You can count on that!

stakeoutstudios wrote on 1/23/2002, 6:29 AM
If anything, I think it would be useful to have a CPU meter for the audio side of things, so that when we add a new plugin, we can see how much horsepower it uses up, and then use that plugin accordingly. I've often tripped over my system by finding a really nice plugin, and not realizing until I've added three or more that it's already eaten up all the CPU power!

Disk meters would be useful so we can see if the disk is ever stuggling... then we could cut down on the number of tracks till it's not a problem anymore.

I think this is a perfectly valid and sensible suggestion for a feature! Maybe it doesn't matter so much for the video purists among us... but for audio it would be immensly useful!

What would be outstanding, was if we had a little CPU meter on either each track and buss... or even each plugin (though that may be overkill). That way you could suss which track or buss load of plugs was using the most CPU. Say buss A was taking 5% , and buss B was taking 78% ... you might wanna make it more efficient... knock out a few plugs etc...

but ultimately, one CPU meter and one disk meter would be a good start!

OK better go do some work!

Jason
wvg wrote on 1/23/2002, 9:24 AM
You want to monitor CPU performance? Simple. Install Windows XP as your operating system, click Ctrl-Alt-Delete, then select the performance tab. Watch all you want. Real time montoring of CPU useage, RAM load, cache, etc., if you're worrying about load on your system. Shrink the window down to a reasonable size and let it float on top of your other applications.

I'm not a video purist. I just think adding bells and whisles and that's all a CPU or Disk meter would be, is really just eye candy not only would it be needless clutter in an already "busy" layout, it would do the opposiite of what you claim to be worried about and for sure overkill. Such gizmos may be "pretty" to watch, however they also sap the strength of an application and eat up the resources you claim you're worried about... especially if you want some kind of real time visual meter on each track. Geez, what next, strobe lights and Vegas showgirls that dance according to the beat of your music in the bottom frame?
stakeoutstudios wrote on 1/23/2002, 12:48 PM
LOL, sounds like laugh. but what I suggested would not require a huge processor overhead. simple numerical text would be enough for the meters! ah well.

I know about sysmon, cheers, but isn't the point of vegas being able to do everything from one compact screen! I need the whole of that vegas screen without floating windows, ta.

The Vegas interface certainly doesn't seem cluttered to me yet! It's very functional, and quick.

Jason
SHTUNOT wrote on 1/23/2002, 1:51 PM
Thankyou for the responses...I can't believe I didn't think of using the CPU/RAM meter in win2k[also in XP]. I'm definitely going to be using that. I've just switched from using win98se all the time to win2k for audio/video only a month or so ago. I have already figured out how to tweak it a bit to run a bit faster.[article at www.prorec.com] I'll get the hang of it soon. Because of my layla 20bit soundcard "beta" WDM drivers and the fact that cubase cried when you tried to run it on anything other than win98lite I've been in the dark about win2k.

So far my question of crashes because of cpu maxing out[too many plugins] hasn't really been dealt with. I'm taking that as a no[noone has had any problems]. Thats great...no awesome. I'll be mixing the rest of this tune today and I'll try the technique descibed and see how far I get.

Anyone else? Later.
Chienworks wrote on 1/23/2002, 2:12 PM
Processor load really should only be a concern while previewing. The
worst that should happen is that your playback may stutter a bit if you're
trying to do more than your processor can handle in real time. If that
happens, Vegas lets you pre-render sections of the project and then
play from a rendered version, which should play back fine no matter how
complex the project is.

The final destination of your project of course will be a fully rendered
output file. Even if you have thousands of tracks and effects, the render
will just take as much time as is needed. Processor load will only affect
the length of the render, not the quality of it. I wouldn't expect the
complexity of the project to crash Vegas due to processor load no matter
what you toss into it. Of course, it may crash due to bugs, but these
wouldn't be load related.