Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #79601
    Profile photo of WLCC
    WLCC
    Participant

    I have been using this setup for recording rehearsals and services for the past two weeks and everything has been working without fail, thus far. When I called Waves regarding the problem that I was experiencing, one of their first questions was regarding my operating system. I was stopped right there and asked to use an operating system that they support. So to go any further with Waves in troubleshooting my issue, I had to revert to Sierra from High Sierra.

    After I had done so, I tested everything out things have been working perfectly.

    There was one additional change I made while troubleshooting this issue though. I had previously been trying to run the card at 48k. I figured that this was more than adequate for my recording purposes. However, I had the dLive system set to run at 96k. It was my experience that I could not select the “digital” clock source for the Waves card when the two are not running at the same rate though. To me this makes sense, the Waves card cannot be slaved to console clock if they are not running at the same rate. I believe for the sake of playback through virtual soundcheck that the clock rate and source need to be the same.

    My tracks recorded while running the card at 48K played back in a standalone DAW running at 48K without a problem. In other words, the tracks had been recorded cleanly. It is though playing them back through virtual soundcheck that they are mis-clocked and therefore full of digital artifacts.

    This has been my experience and the resolution that I had found. After reverting to Sierra from High Sierra, I never finished troubleshooting with Waves due to finding an apparent solution the problem I was experiencing.

    #79124
    Profile photo of WLCC
    WLCC
    Participant

    Hi all,

    I wanted to post a follow up and let you all know that the issue has been resolved. First of all, I reverted the iMac back to OS Sierra. The SoundGrid app is not supported on OS High Sierra. Secondly, it appears that I had the wrong settings with the Waves card driver. The driver is now set at 96k with its source selected as digital, in other words it is looking at the Dlive for its clocks source. I am also running TracksLive at 96k as well and all is now good. Thanks for your input on helping me resolve this issue.

    #78875
    Profile photo of WLCC
    WLCC
    Participant

    Yes Jay, I have let it go to sleep with Soundgrid running. After I setup the computer for use with the dLive, I never changed the settings beyond the factory default configuration. I will try this as well after I finish reverting the OS back to Sierra.

    #78870
    Profile photo of WLCC
    WLCC
    Participant

    It is a spinning drive operating at 7200 rpm. I am in the process of downgrading to Sierra and will try that out first thing.

    #78841
    Profile photo of WLCC
    WLCC
    Participant

    I thought it was most likely a clocking issue, I just don’t know what I am missing with the configuration though. A week ago today was the install and everything was working perfectly. If I open up my session from last week everything plays back perfectly right now. However, when I open up my session from yesterday, everything is distorted, popping, etc.

    I am recording to an i5 iMac with 12gig of ram with the latest os High Sierra installed. The waves V3 card is connected directly to the iMac via shielded cat6. I am recording to an external hard drive connected to the firewire 800 bus.

    I have not called Waves yet but am planning to do so if I cannot get this figured out soon.

    Thanks for your help.

Viewing 5 posts - 1 through 5 (of 5 total)