but that doesn't always work with audio interfaces. Not a big deal with a keyboard because using the keyboard will wake up the port. Windows by default disables unused (and inactive) USB ports. USB ports: I'm wondering if your USB port settings are the problem. The fix was a clean W10 installation and a single paid version of AV/AM. Had reinstalled W10 3 times before I sussed it out. Malwarebytes seemed to be the main culprit. Uninstallation was problematic and only added to the problem. Windows 10 and AV/AM: I had tons of problems with Windows 10 when using free versions of AV/AM. Regards, be helpful if you post your system specs. May be every version / release of win 10 is not the same as it evolves and is consequently released to vendors in different parts of the globe. Think windows 10 support via the OS, is being finished, remember media player capability was part of Just makes me ask if Reaper was installed in admin mode and is now running without any such privileges, if such is possible, or the driver in question could have a similar issue.Īre you running 32 bit Reaper, l read somewhere about 32 bit programs having issues on win 10, Admin mode is just that, I've spent two days fixing file permissions because of someone running in admin mode, they too were trying to get an application coaxed into running. USB port, FIREWIRE PORT, thousands of ports on a computer, and a good firewall blocks them unless the user opens them. All these things have nothing to do with an USB-interface.Īnd for complicated reasons explained in other longly threads Reaper should be used in admin mode. Ports a thing of internet connectivity and ports can be blocked by firewalls. but that signal isn't being routed to Reaper or my standalone apps. so I at least know there's a signal going into the interface, through the Firewire card and into the box. ![]() the Focusrite mixer does respond to input. so the dead behavior in not just with Reaper. ![]() Recall that I said this behavior is also happening in my standalone apps that depend on my audio interface as well even though their audio inputs are configured properly (just the same as they were in Vista). Enable synchronization to time code is unchecked. right click the play button > External Timecode Synchronization. no need to buy a new USB interface unless I'm sure my Firewire interface isn't gonna work. Nothing going on in the background like popups. the Firewire connection is fine (it's a Firewire interface not USB) and it's all synced up. when I tried to record the track was record armed and the record button was pressed. For me that's Direct Sound and Sound Blaster Recon. playback of sound files using Reaper works fine when the audio device is set to use the system driver. It's setup no different from when I was using Reaper in Vista. ![]() the correct driver for the interface is installed and the interface is correctly configured in Reaper. ![]() everything that doesn't depend on the Focusrite interface plays media fine. none of the track or master volume meters move. Windows 10 圆4 has been struggle from the get go. When I was using Reaper on Vista 32 with my Focusrite interface. Am talking to Focusrite Support but we just started. I've read this type of behavior could be an audio interface driver problem (the driver installation seems fine and it's the latest), Windows DPC or something preventing Reaper (and my other stuff) from accessing the audio interface driver. I can't get any signal what so ever into my stand alone amp sims or my Peterson Strobosoft. the counter is static but says it's playing and there's no movement of the play cursor. the counter is static but says it's recording and there's no movement of the record cursor. When I arm a track, select the input etc. setting everything up on it for the first time. This is a brand new Windows 10 圆4 computer build. Maybe someone can point me in the right direction here.
0 Comments
Leave a Reply. |