simon, i'm under the impression you don't like the arguments and therefore reiterate some details divorced from context ...

from back to forth: increasing the preload buffer means higher usage of RAM -> expected immediate response: i can't load the instruments on my computer.

you mentioning you're not a programmer and i have to admit i'm a poor if not actually no C++ programmer, but i can assure you: the engine and it's design is pretty brilliant.

if you get another motu (possibly actually on a mac) hopefully the drivers are working flawless - something one can not say about all drivers for this devices.

please consider we are not blaming any sound card or operating system or method of connecting a harddrive - i just want to explain in words as simple as possible the context for performance of a computer for certain combinations you should prefer or avoid if you need or like a good audio system.

in a nutshell: average computers can play less articulations from less demanding libraries at a given performance, more demanding libraries with more articulations require more than an average computer.

there are a few, but often decisive factors a sample library producer can only influence up to a certain pont - an example is the newest *pro application update* from apple, i'd assume they wouldn't provide it if everything works also fine without it, another one the still applying limit of gigastudio to 1 GB, the limit of number of exs instruments, ect ... endless list

of course also VSL is continuously developing to provide the best possible performance for our users, but also i'm trying to shed some light on various other general conditions which should not be ignored.

christian

@Another User said:

there are a few, but often decisive factors a sample library producer can only influence up to a certain pont - an example is the newest *pro application update* from apple, i'd assume they wouldn't provide it if everything works also fine without it, another one the still applying limit of gigastudio to 1 GB, the limit of number of exs instruments, ect ... endless list

of course also VSL is continuously developing to provide the best possible performance for our users, but also i'm trying to shed some light on various other general conditions which should not be ignored.

christian

It just seems like it doesn't matter how much evidence you are provided from users which all have the same problems with very well equipped machines, the only reaction we get is: This is an OS X problem, the VSL player is flawless.

simon, we have a reference machine here almost identical to the one you mention, and it is actually in an extraordinary bad condition (regarding a clean system and the amount of applications installed) and it plays really huge performances flawlessly - so one SHOULD assume something else is in the game if a single instrument pops or klicks, right?

a single patch runs even on an old G4 1,25 (also somehow devasted softwarewise) without any problem.

so i really don't know what VSL had to admit - if you don't like to consider points from above, it is your decision, but then please don't blame VSL to be responsible for a certain state of your system.
christian

That's it, I give up...

Simon, the reason I double-checked and posted above is to establish that there's more to the story than just "something is wrong with the V.I. Player." I think that if my machine is working fine, there must be another factor causing people these problems.

Note that I was able to get my machine to click and pop as soon as I had the PCI-424 card receiving audio from a slave machine. It stopped doing that after I turned Altiverb off and back on again, but now I wonder if that couldn't have something to do with it.

It could just be a matter of breaking the camel's back too, and what makes it hard to track things like this down is that every machine will click and pop under a heavy enough load.

Nick, as we already have established, it is not a performance issue, since it can happen with any minor patch no matter the buffer size of your audio card and so forth. AND the fact that all other sample players don't exhibit this behaviour. And if a dual 2.66 Ghz machine with 5 GB RAM isn't enough for VI to play back one stereo stream, then something is seriously wrong[:)] There is something wrong with the VI engine - period. Just because this behaviour doesn't show on every single setup doesn't mean that there can't be something wrong with a piece of software. It may be a combination of software and hardware and drivers yes, but the thing still remains that this is a problem with the VSL engine only and not all the other streaming sample engines. I don't care if VSL coded the engine in the proper way, and that somehow all the other companies have found a workaround to make their engine work in OS X as it should, the fact is that there is a problem.

While I don't expect the VSL people to admit at once that there is something wrong, I DO expect a response more along the lines of "we will have our programmers look into it" instead of the response we are getting at the moment, which is so unlike VSL.

Simon, do you have Boot Camp with Windows on that machine? That would be an interesting test.

And I'm going to check the PCI-424 theory.

Nick, no BootCamp here. When I tried it back in september it didn't work very well with my bluetooth keyboard - ie. I ended up not being able to boot anything but Windows XP until I plugged in an USB keyboard to get into the Macs boot menu... So I am a bit anxious to do that again.

But why would that be interesting? The PC version of the engine may very well not exhibit these problems but that doesn't prove anything. Or it may have, and it wouldn't prove anything either, would it?

It wouldn't prove anything, other than that maybe you can run the PC version and not get clicks and pops on your machine. [:)]

By the way, the PCI-424 card isn't causing clicks and pops on my machine. Evidently it was just running out of horsepower that did it - which is understandable with all that stuff going on.

So the next question is why my machine isn't clicking and popping like the others in this thread. I know it's not because I'm smarter than anyone else, and Kays proves that it's not the California sun.

Hi all,

I posted all KNOWN reasons, why clicks and pops might occur on Mac, regarding unknown problems I already said:

@Another User said:

we are also investigating in order to find a solution

However this might take a while since the problems occur randomly.

Best,

Maya

@Nick Batzdorf said:

I know it's not because I'm smarter than anyone else, ...

Hmmmmmm, it seems you are... [;)]

Maya

Here is a word for those who have suffered from this problem with hopes that you will find relief as I did from JWL. Also I learned from my precious wife that any firewire device has to share the same built in firewire controller. Lesson-Only use one firewire device if it requires a large bandwidth. I am a very happy guy now.

Dear JWL:

We thank you for a suggestion that made sense. I did not know that because I had the Fireface 800 connected to the FW 400 port and the Rocstor HD with the VSL SE library connected to the FW 800 port that they shared the same bus and obviously VSL does not like to share. When I hooked the Rocstor up to the USB port and left the Fireface 800 alone on the FW 400 port, end of pops, and end of sound dropouts. Now I am kickin it. Many, many thanks. [:D] [[:|]] [H] [[;)]]

Power Mac dual 2.5 ghz with 4.5 gb RAM Rocstor ext HD USB port with VSL SE library and Fireface 800 on FW 400 port

Is that a USB 2 port for you external hard drive???

Tim

Yes. I also intend to look into buying a PCIx card for any other firewire devices I might need to use. I need to research this some with regards to compatibility with the Fireface. The USB 2.0 on the front of my Mac seems to work just fine.

just as a sidenote ... VSL as such does not care about the method you connect what and where ... it is the file access handled by the operating system which is affected, VSL *only* is requesting a huge amount of data most of the time.

doing some research regarding firewire 800 extension cards is a very good idea - there are some really crappy products on the market. unfortunately i could only find the german page explaining what some vendors have done ... http://www.rme-audio.de/techinfo/fw800alarm.htm
christian

I don't use any firewire harddrives. I use two WD 500 GB RE2 SATA drives internally for sample playback.

Another reason, why dropouts can happen is that Logic´s audio engine goes to a form of "sleep mode" sometimes. The result is that sample streaming from HDD doesn´t work anymore and only sample data which is already buffered in RAM will be played back properly.
In this case it helps to go into play mode in Logic and to play all tracks with Vienna Instruments instances for a few seconds. This will "restart" Logic´s audio engine.

Best

Maya

Can the Logic audio engine sleep mode be disabled while working or does this have disadvantages? [*-)]:

@Simon Ravn said:

I don't use any firewire harddrives. I use two WD 500 GB RE2 SATA drives internally for sample playback.

Good Morning, Simon. I have felt your pain. I am curious and you may have said this in previous posts - Does your problem persist with the use of built in audio? My problem was timed with the use of the FW 800 port-ie that was the act that caused my problem. Did you attach anything new when you loaded VSL SE? If built in audio works, then it would seem to point to how info is handled internally with more than one HDD. Resolution of this issue is important to all of us as I am contemplating a new system.

@Simon Ravn said:

I don't use any firewire harddrives. I use two WD 500 GB RE2 SATA drives internally for sample playback.

Good Morning, Simon. I have felt your pain. I am curious and you may have said this in previous posts - Does your problem persist with the use of built in audio? My problem was timed with the use of the FW 800 port-ie that was the act that caused my problem. Did you attach anything new when you loaded VSL SE? If built in audio works, then it would seem to point to how info is handled internally with more than one HDD. Resolution of this issue is important to all of us as I am contemplating a new system.

Hello.

I still haven't tried with built in audio, since I don't have that connected to anything, but I will test it with a MOTU PCIe solution soon and see if that changes anything.

And no, I haven't attached anything special. And it's not VSL SE, it's every VSL instrument that behaves like this. It is related to the VSL engine in some way. Maybe the engine needs to be coded in a slightly different way to work 100% on OS X - I don't know, but Native Instruments and others got it right.