Plowman, if I remember right I had a sequence playing when I did one of those tests. (This was a few months ago now.)

I wonder why your machine isn't behaving the same way. And to tell you the truth, I'm not as excited about 64-bit access as I once was, because I'm able to access all the affordable RAM I need to access right now. Maybe the Intel Mac RAM will come doown, but somehow the idea of spending $250/MB (vs. the $75 I paid for the 8GB in this machine) to acccess still more RAM on a single machine is uninspiring.

A 2x2.5 G5 with 8GB and a SATA card for more storage may be 60 computer years old (1 year = 20 computer years), but it's still a very, very serious DAW. I bought this machine in April 2005; historically machines have been feeling very old by the time they get 1-3/4 years old, but not this time. I've been upgrading machines every couple of years since the mid-'80s, so this is quite a change. Part of the difference is that we're not using just one machine anymore, of course. And then Mac World is coming next week, and NAMM the week after, so it's also possible that this will sound silly. However, the point remains.

In any case, I like running stand-alone instruments outside the DAW on the same machine very much. To me it's not a disadvantage compared to having everything inside the DAW.

I have a dual 2.0 with 4.5 Gb RAM and I am running out of cpu before running out of RAM, so I optimize, freeze, and then I run out of cpu. The weird thing is that the VSL server is running clock cycles more than Logic even when the tracks are ALL frozen. I have to unload the VSL instance from within logic to get the cpu clock to go down in activity monitor. Is that normal?

For me the main issue is, yes, you can do a lot with this machine but performance is a big part of it, and to be able to play in the parts and have a decently low latency and hear what you are doing, you have to have it set to 256 buffer with small process buffer, that works nicely even though it could be better - good enough to play the parts. Of course running the machine like that means you have significantly less cpu overheads. When mixing, I reload the proejct with 1024 buffer of course, when I'm finished playing in parts, so that is fine and then you can go and load reverbs etc (whereas I just use a "cheap" reverb sound for composing to save on cpu and get more sequencing done).

Even though my machine isn't fast enough to use it - what is this I'm hearing about using other instances of VI as standalone does this really work nicely?

Miklos.

@mpower88 said:

The weird thing is that the VSL server is running clock cycles more than Logic even when the tracks are ALL frozen. I have to unload the VSL instance from within logic to get the cpu clock to go down in activity monitor. Is that normal?

I'd be interested to know the answer to this question as well. In my experience, it seems as though the VIs run at full CPU whenever dsp is running -- so in some apps that means a high-CPU idle, while in others it means high-CPU any time the transport is running. They do seem to be quite efficient, but I'm curious to know whether they mute themselves when they are not processing audio (or could they be made to do so?).

J.

Okay, I guess I need to install the V.I. player on my dual 2.0 and see whether I have the same problem. You can see the Activity Monitor dumps above to prove that my 2 x 2.5 is perfectly happy working this way.

Were there any architectural changes in the machines? As far as I know the only difference in the 2 x 2.5 is that the CPUs run a little faster and it has a liquid cooling system.

Weird.

Hi Nick,

I, too, would appreciate it if you would try that test with dual 2 Gig machine. That's the machine I have and I really, really want to get sorted out which way to go with it.

I've spent several days now going over options of combinations of ways to go. Even though Mac World & NAMM are happening right away, knowing a clear assessment of my dual 2 Gig machine would certainly help with any decision to be made.

I want to thank you in advance for taking the time and effort to check this out. Also, where do you think would be the best place to look for older dual & quad G5's?

Best regards,
Jack

Jack--

I would start with Apple's own refurbs. You'd have the confidence that they'd been checked out and the benefit of having some sort of Apple Care.

There are other options, but I'd at least start with Apple, fwiw.

For example:

Refurbished Power Mac G5 Quad 2.5GHz
Two dual-core 2.5GHz PowerPC G5 processors
1.25GHz frontside bus per processor
1MB L2 cache per core
512MB of 533MHz DDR2 SDRAM (PC2-4200)
250GB Serial ATA hard drive
16x SuperDrive (double-layer)
NVIDIA GeForce 6600 with 256MB GDDR SDRAM
Learn More
• Save 19% off the original price
Original price: $3,299.00
Your price: $2,699.00
Estimated Ship:
Within 24 hours
Free Shipping


Add
AppleCare Protection Plan for Mac Pro/Power Mac (w/ or w/o Display)
extends the complimentary coverage on your PowerMac to three years of world-class support and service.
Learn More
Price: $249.00
Estimated Ship:
Within 24 hours
Free Shipping

Compare that to cdw.com, formerly macwarehouse.com. They were selling PPC Quads at full price while they had them. I just checked that site and they don't even show them anymore.

"...I'm not as excited about 64-bit access as I once was, because I'm able to access all the affordable RAM I need to access right now."

I noted your coolness to 64-bit as early as last year's NAMM, I believe. I think the "Batzdorf Method" shows a healthy non-emphasis on the dream of one computer doing it all. Over the last year, I've stopped holding that torch. Yeah, it'll come one day -- but I've stopped actively waiting for it.

"...if I remember right I had a sequence playing when I did one of those tests." Again, that amount of RAM you've loaded is clear and inspiring. But I'd like to know what kind of CPU price you're payng just for the loaded RAM when the transport is running without anything playing back. I've seen your System Memory posts, but not CPU readings. But only at your convenience.

"I've been upgrading machines every couple of years since the mid-'80s, so this is quite a change." Agreed. About '04, we crested a VI threshold. The discussions I read now have more to do with ease of use.

"Is that normal?" I don't know if it's normal, but it's what I face all the time.

"...whereas I just use a "cheap" reverb sound for composing to save on cpu and get more sequencing done." In my search for more CPU, I was alarmed to realize how *little* Space Designer was asking of my computer. I had wrongly assumed that it was a major culprit. Finally in a diagnostic session, I removed them from my song, and the CPU savings was negligible. It led me to wonder if the caution against such things was a bit out-dated, like the way we use to worry about MIDI choke. But your results may vary.

"I would start with Apple's own refurbs." Yes, me too. I bought my Mac used from Sweetwater and still got some service and return protection. But the sad truth of the Mac universe is, there aren't a whole lot of deals out there. As Nick once pointed out, even after new lines debut, "old" Macs might drop about 150 to 200 dollars. Nice, but sometimes not worth the wait and unlike the jaw-dropping deals we can see in PC's.

Thanks JWL & Plowman,

I'm going to NAMM and plan to mine all the info I can finagle out of all the manufacturers whose VI's & plugins I own or plan to buy in the immediate future.

I've made up crib sheets of pertinent questions regarding compatibility w/ Mac Intel, what it will take to migrate their software to another computer (really my biggest concern regarding setup of a new system or network) and what the major library manufacturers need in terms of computer resources. This way I can figure out how to spread the programs over multiple cpu's and with informed consideration of the eventual upgrade to the 64-bit future.

I'm also bringing a video camera to document what I see & hear so I can remember & recall it accurately.

It's really great that NAMM follows on the heels of Mac World so closely. There should be a lot of answers available that right now are only available by reading tea leaves. I'm with those you believe that the single machine, 64-bit heavenworld is a ways off still. I use Pro Tools HD & Logic and want to see them split off onto their own platforms. Of course, there are other complications also.

Anyway, at that point I'll make my decision about which way to go to relieve my poor little dual 2 Gig from its current misery.

I'm really looking forward to this trip.

Much as I'd like to, Plowman, I don't think I can take credit for this method, and I don't think you noticed me being cool to the idea of one computer being all we need at all. I'd like that very much. It's just that I don't see it happening soon - although it's getting better.

If you look at the Activity Monitor dumps above, you can see the CPU percentage. The second one with all kinds of stuff going appears to be at about 80% - but that's of one of the two CPUs. i'll load those sequences when i get a chance and see what the CPU reading is with the transport stopped.

This topic demonstrates what I was fearing and explaining on this same board a few weeks ago. Going "full" 64-bit will *not* automatically give us the ability to use 16+ GB of samples.

I suspected that there would be a tremendous amount of rewriting before that would happen.... it could turn out that I feared right!

Jerome

Well, either way, I think it's fair to say that the industry would do well out of us consumers as a whole if it did certainly provide greater memory access for graphical, video and obviously music applications via whatever means works best. I don't see why there can't be multiple VSL servers controlled by a central administrative server that does not access the memory of the other independant apps, then we could have as many VSL servers running as necessary to utilise the amount of RAM in the machine. Then you could use 16Gb easily no problems. Of course I have no actual idea abou the technical implimentation of this but it seems to me that you could do it, after all, games do this: multiple servers controlled by a central server, only in this case, you have each server as a memory access device which accesses 1.2 Gigs RAM, not more, and once it is full it starts off handling memory holding to the next server (or rather than admin server does that).

(edit) just to add of course the host app (logic etc) would interface with the memory via the admin server. The admin server would be like a router between the memory holding servers and the host. Might add some latency but on a fast machine, wouldn't matter. On a quad intel, with 16gigs of ram the problem is ram access not cpu anyway, you could just run your system on a lower buffer setting -seems worth it to be able to access all that ram.

Miklos.

Anyway, my personal main problem is not enough cpu... The ram optimiser and freeze functions combined mean you can quickly enough optimise VI and I find it works excellently, not too hard to re-open , reset, re optimise when necessary too - with this feature you can get quite a lot out of a single instance as it is... The problem then becomes that each instance uses an amount of RAM in the server so you have to be efficient in using each instance to it's fullest in terms of loading sounds... Having multiple VSL servers seems like it would work on the surface but of course I'm sure there is a complex programming reason why it would not work well. Hats off to the masters at VSL for making VI as superb as it is. I for one am not complaining only wishing to be able to use it to the maximum capability or at least have that freedom when writing.

Miklos.

@mpower88 said:

.... On a quad intel, with 16gigs of ram the problem is ram access not cpu anyway, you could just run your system on a lower buffer setting -seems worth it to be able to access all that ram...

Miklos.

That sort of reinforces something that has been at the back of my mind for a long time.

We have clearly reached a technological impass of sorts when some aspects of hardware meet or exceed the demands of software while other necessities of code structure prove to be counter productive. As long as VI users are willing to buy and sustain a network of comptuers then it may not be a problem.

But at some point, something has got to give-- the need alone will force a change sooner or later-- always does.

So maybe users of orchestral VIs represent a minority of computer users, but the term Pro User as far as the Mac Pro is concerned is in a strange way doing as much to alienate users as it attracts them.

The Cube is an awesome accomplishment-- its sound exceeds anything believed to be possible on a computer, imho. We're just in a bit of a 3GB limbo for a while yet.

To me a network on computers is unfeasible and a pain to set up and administer and work with. I need that aspect to be as simple as possible when writing.

Perhaps we simply the problem then solutions will follow from that.

1. We need to access more RAM from VI - lets go with todays maximum - 14Gb (plus 2 for system).

What can be done to make this happen in the near future? If people are able to run multiple standalone VI's and access more RAM then *surely* this is not as impossible as it seems, it's only impossible with the existing set up, can that be modified so that we have multiple VSL servers running? Or one VSL server with memory nodes as separate apps, that it uses to store memory in RAM? That would solve all the problems NOW and no need to go 64bit at any stage, and would work with existing hosts and OS.

Miklos.

"I don't think you noticed me being cool to the idea of one computer being all we need at all."

You have been cool to Apple's touting of 64-bit when so much remains to be done after it premieres. Consequently, you have noted that the one computer solution is not imminent. I know you don't like Apple "plastering" 64-bit on their marketing materials. Don't make me go into the archives.

Not to be a pest, but you mentioned "sequences" playing. The numbers actually become less helpful in that case because we don't know how many voices and DSP's are affecting the CPU.

The baseline I'd really like to see is the CPU hit you take when Logic's transport is running with full RAM loaded and nothing playing. Then I'd know if I got a 2 x 2.5 how much CPU I'm losing right out of the gate. As I mentioned, with loaded RAM on a dual 1.8, I sacrifice about 35% total CPU just by hitting play, even before I start writing. It's nearly prohibitive. I'm hoping on a dual 2.5 with the load you've illustrated, you'd only lose about 15 to 20% CPU with the SPL running / no music.

Thanks for all you do, Nick and everyone else. And Jack, what a time you'll have. After you recoup (money, sleep, speaking voice), I'd love to know your take on things. Maybe you'll get a glimpse of Herb in the MIR. Wish I could be there.

Think of all the free dinners Nick must get.

No such thing as a free dinner, Plowman. [:)]

I'll find the seq and load it up.

Oh, and you're right about what I said about 64-bit marketing. But I don't think I'm going far out on a limb - it's obvious that this isn't all going to change overnight; we're going to be using multiple computers for the forseeable future. And I say that even before taking into account that developers always write software that pushes the boundaries and brings current machines to their knees.

Case in point: MIR.

@Nick Batzdorf said:

No such thing as a free dinner, Plowman. [:)]

I'll find the seq and load it up.

Oh, and you're right about what I said about 64-bit marketing. But I don't think I'm going far out on a limb - it's obvious that this isn't all going to change overnight; we're going to be using multiple computers for the forseeable future. And I say that even before taking into account that developers always write software that pushes the boundaries and brings current machines to their knees.

Case in point: MIR.

I think you're right, Nick. The extra hype about Leopard's 64-bit capabilities had many wondering if networks would finally get smaller at least. I never thought they'd go away, but it did instill a rather false sense of optimism for the short term which has proven to be a little disappointing.

But now that a year of Intel-Macs has passed we can at least budget more appropriately. I don't mind investing in a network if I know that I'll get 2-3 years out of it, but if computers were to really take a flying leap forward over the next 6-12 months and I've tossed tens of thousands of dollars into soon-to-be-antiquated technology-- well, let's just say it becomes less a matter of the actual dollar amount spent rather than the manner and purpose for which is might have been wasted.

I really feel a lot better now knowing what hardware upgrades will be most practical over the next year or two. This doesn't change my wish list, but it does inspire a more realistic approach rooted in fact instead of spec.

Okay, I didn't even have to load it again. This is from the article in our current issue (Virtual Instruments mag). I see from my own figure caption that the sequence isn't playing:

@Another User said:

Fig. 1: 7GB on one machine, and it’s running reliably. This Activity Monitor screen dump shows 6.96GB of memory access in a G5 with 8GB loaded. The VSL-Server program is listing samples loaded into the plug-in versions of the VSL Vienna Instruments player running inside Logic Pro, which is accessing 1.38GB. (Logic is also running other programs, including Spectrasonics Stylus RMX.)

Four stand-alone copies of the Vienna Instruments player (all named differently, which you don’t see) are running outside Logic. In addition, Native Instruments Kore is running several instruments, including Toontrack’s EZ-Drummer (a sample-playing instrument).

While the sequence isn’t playing here, you can see from the idling percentages that the CPU hit isn’t going to be outrageous. That’s what’s changed recently to make this possible.

http://homepage.mac.com/virtualinstruments/.Pictures/seq%20not%20playing.png">

Kore uses a fair amount of CPU, by the way, but the VSL and Logic programs aren't.

The fact is though that how many users need to have access to 3+ GB of memory for one single process? Besides high-end scientific and pro applications, no one.

It's really a niche market, so I wouldn't be surprised that this takes some time to work.

I'll always remember the words of one of Logic's top developers when I met with them about a year agor: "More than 3GB of Memory? What for?"

(He wasn't joking).

Jerome