Jump to content

mikec137

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by mikec137

  1. WDM/KS defaults to the Apollo but not compatible as main interface
  2. Yes, but when I hit "apply" it changes back to Realtek
  3. Thanks Outrage. I disabled Realtek but it still defaults back to it
  4. Hi everyone, I posted here about this issue a while ago with no resolution but I'm hoping someone here can help. I replaced my 10-year-old Creation Station PC with a new one a couple months ago and have been dealing with skips or hiccups during playback. My old PC ran flawlessly at 128 buffer size, but I have to set the new one at 1024 and still get skips. it's not the usual popping and clicking associated with buffer size, it's more of a hesitation. I noticed that the performance window on my control bar usually spikes to the red when this happens. The new Creation Station came with a basic version of Presonus studio one which runs flawlessly with lower buffer setting. One other issue I noticed is that my record latency adjustment device is set to Realtek ASIO. When I change it to the Apollo it reverts right back to the Realtek. I was able to uninstall the Realtek, but it reappeared after a while, and I still had the issue with the Apollo selected I'm using an Apollo quad firewire interface with a M-Audio Profire 2626 as ADAT slave
  5. Thanks Glenn, the Record Latency Adjustment device is now my Apollo, but I still have pops and clicks. My old machine ran at 128 buffers without a hiccup. I'm at 1024 and it's almost unusable. I think it may be an issue with the newer motherboards not handling firewire well
  6. Thanks David. ASIO 4all is gone but now it defaults to Realtek ASIO
  7. Hi all, I recently replaced my 10-year-old Sweetwater Creation Station with a new one. I'm having serious latency issues and clicks and pops even at high buffer settings. (1024) I noticed that in preferences>sync and caching>record latency device is set to ASIO 4all even though I'm using my Apollo Quad firewire as my interface. When I use the drop down to select the Apollo, it defaults back to the ASIO 4all. I tried uninstalling ASIO 4all and it then defaulted to the Realtek driver. I'm not sure if this is my problem, but it seems like I should be using the Apollo for latency adjustment. FYI... I tried the PreSonus studio one DAW that was included with the new PC and there doesn't seem to be any latency issue
  8. SLOVED... Thanks! You nailed it Bristol Jonesey. It was not in the scan path
  9. Hi, Long time... I recently replaced my studio computer and went through the process of reinstalling sonar and downloading all my legacy items with command center. I was able to get the stand alone D-pro 64bit but not the soft synth. Any help is greatly appreciated Cakewalk band lab, Sweetwater Creation Station, win 11, Apollo quad with ADAT M-Audio 2626
  10. Thanks, I have a bandlab account and Cakewalk by bandlab installed. I tried system restore and it seemed to work until this morning when I got the error again. When I try to launch Cakewalk I get this: "Cakewalk Application has stopped working" "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available" If I hit "open" on the bandlab assistant, I get this: "ACCESS ERROR" "Bandland Assistant can not open C:\Cakewalk Core\Cakewalk exe. Try to run app as administrator If I try to access my Cakewalk projects through my D drive, I get this: "D\Cakewalk Projects is not available" The request could not be performed because if an I/O device error
  11. I recently upgraded to Win 10 and had some bugs in cakewalk. it was recommended that I reinstall. Where do I go? do I still use command center? Thanks,
×
×
  • Create New...