Vienna Symphonic Library Forum
Forum Statistics

197,874 users have contributed to 43,083 threads and 258,678 posts.

In the past 24 hours, we have 0 new thread(s), 2 new post(s) and 51 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. vsl daemon

  • vsl daemon

    G
    G
    Hello, Anyone know what this is? I am seeing in my OSX Tiger Activity monitor as "vsldaemon (Not Responding). Is this something normal or is it not needed? The location of the file is in Library/Application Support/VSL on the HD. Thanks,
  • L
    L
    Do a force quit and reboot
  • L
    L
    Select the VSL deamon app, look at the red button upper left and click on force quit
  • cmC
    VSL Team
    cmC
    last edited
    last edited

    @Laurent said:

    Select the VSL deamon app, look at the red button upper left and click on force quit
    this is actually a very bad idea ... the vsldaemon (as most daemons in UNIX-like systems) does not interact with the GUI and appears therefore as *not responding* since it is not responding with something to the GUI

     

    please leave everything as it is for normal use - and be aware: OS X does not behave like OS 9, there is much more to consider.

     

    for the rare cases where it would make sense to force-quit the daemon (and then not only the daemon btw) we rather recommend to reboot the computer ... eg. before updating the ViennaInstruments softwar or a license control center.

     

    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • L
    L
    When the VI wouldn't work (spinning ball when accessing to the VI host), the only solution for me was to force quit the deamon applications and reboot, now I don't encounter these situationsanymore. I did that when I had this lovely spinning ball. So, of course, don't listen to me, and apply carrefully what Christian said. I meant it in case of problem, but even in that case I'm sure CM shoudl offer another solution.
  • cmC
    VSL Team
    cmC

    facing the *spinning ball* when trying to access the VI plugin has generally another reason (than vsldaemon not responding, which is - as mentioned - normal)

    in most cases it is an unsuccessful or incomplete AU validation, which again is mostly related to incorrect permissions.

     

    this is why we recommend to repair permissions (disk utility, or for the advanced users disk warrior) after every installation or update on OS X.

    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • L
    L
    Never use disk warrior, or maybe it's newest update 4.1, by the very Apple and drive repair specialist it's useless and could much tent to lead to some problems. cm when I get the spining ball, that's mainly because suddenly the VI seems not recognising the syncrosoft key. I always check repair the permissions after a new install.
  • S
    S

    Laurent:

    Have you had a bad experience with DiskWarrior?

    I have used it for a number of years and it has consistently fixed problems that no other utility could fix (and some problems that no other utility could detect). It has never caused any harm whatsoever. In one memorable case, every other utility declared that my startup disk was corrupted beyond repair, I ran DiskWarrior and, over a 14 hour period, it was able to rebuild the directory of that disk. (Since things were going so slowly, I worried that DiskWarrior had crashed and called Alsoft Technical Support. They told me that, as long as I could move the cursor, it had not crashed, but that it would take a very long time since DiskWarrior's behavior indicated that my startup disk was severely damaged as a result  of physical defect.) I lost no data in this process and was able to backup the disk completely before replacing it.  I have not yet tried DiskWarrior 4.1 since Alsoft has not yet released the download for updating DiskWarrior 4 to 4.1. 

    I would be most interested to learn what your negative experience was.  
  • L
    L
    Steve, I bought DiskWarrior a few years ago and it helped me quite a lot. But until recently, it never could repair a damaged disk with it, perhaps because it was too damaged for once, the 2 others I don't know. Each time i've go a problem with a disk, Diskwarrior could not SEE it like Disk Utility couldn't either. I live in Paris and went to the most sofisticated drive repair shop called http://www.13-17.fr/ The guy could analyse the source problem while I was putting the phone next to the running but unmounting drive. It could detect by the rythm that the reading head was broken and should have damaged the drive, When I went the to buy their one and only enclosure, we spook about diskwarrior, he prevented me from using it, telling it could lead to some problems. The conclusion was that it was safer not to run it. Agree or not, I prefer to follow his warning. BTW, reading your story you're a very lucky man "-) Quadri 2.6 Ghz MacPro / 9 Go ram Logic 7.23, Logic 8, Fission, Sibelius 5 OSX 10.5.2 Apogee Duet 2 To inside, ( 1 To + 2 x 500)