- 31st December 2016 at 20:13 #27744
I am using the LR-16 as a 2×16 interface with Reaper. All works fine except that Reaper and the LR-16 will lose their connection after some apparently variable time (typically about 1/2-1 hour). When the connection is lost I get an [audio device closed] warning in Reaper. Both Reaper and the LR-16 have to be shut down and restarted to reestablish the connection.
The about screen in the LR-16 mixer says that the driver is 6.19.0 and the Firmware version is 18323. The LR-16 itself shows the firmware version to be 83859.
My system is a Dell pc with an i7 processor, 8MB Ram, and 256G SSD. It is less than a month old. I am using a 16′ USB 2.0 cable from Amazon Basic.
I’ve been running a dedicated power option for recording which a) never puts the system to sleep b) turns off the hard drive only if idle for more than 5 hours c) disables “usb selective suspend”.
I am recording directly to my 256G hard drive. This has obviously not been formatted via the LR-16. Do I need to attach a separate drive to a USB slot on my computer that has been formatted by the LR-16 and use that drive as my recording media or is that only a concern when recording directly from LR-16 to a drive and not using the LR-16 as an interface?
Any suggestions as to what else I might look at to resolve this issue.
Thanks,3rd January 2017 at 19:11 #27759
Those this issue present in any other application as well or only with Reaper?
Where you have this “audio device closed” error message, what do you see in the LR-16 control panel it still say connected?
If yes then you start any other (ASIO) application do you able to connect to your LR-16?
BTW is there any special reason why you want to record with the PC instead recoding with the LR-16 directly?3rd January 2017 at 20:30 #27761
Reaper is the only DAW that I use so I can’t compare with other DAW’s. I do use Amazing Slow Downer and of course a myriad of other windows apps and have no problem with them. I have used other audio interfaces with the LR-16 such as my Fractal Audio Guitar processor which can function as a 2×4 ASIO interface and a simple WAVE OUT or DIRECT SOUND internal audio device with a simple microphone. Have not experienced any Reaper “audio device closed” issues with these.
When Reaper says that the audio device is closed, the LR-16 still indicates that it has an active PC USB connection. When Reaper says that the audio device is closed, the LR-16 inputs and outputs no longer appear on the setup screen within Reaper.
I will re-check to see if I can switch to another ASIO application after REAPER tells me that the device is closed but I think I was not able to.
And the reason for recording with the PC is one of convenience. I am able to get much better control over the recording levels, can pause and resume the recording session with a single key-stroke, can set markers on the recording session for quick playback ( I use during the LR-16 for band practice to record and playback our practice sessions which may last 3 hours and include many songs), can have multiple takes of instrument parts, and can punch-in/out to overdub parts for more serious recordings.
This problem may be unique to my pc but I was thinking you might have some insight as to where I might look to resolve the issue. I have not ( to date ) had disconnects when the device was active but it seems to drop out after its idled for a period of time. I’ve just started using it with this new pc so the data is still coming in. Not an easy problem to nail down.
Thanks …4th January 2017 at 01:45 #27762
Suggest we put this issue on the side for awhile. The problem seems too variable and hard to reproduce. I tested it again this morning to try to answer the question as to whether I can connect with another ASIO system after the disconnect occurs and the system stayed connected in an idle state for more than an hour. At that point, I shut it down. I think I just need to watch the system a bit longer to see if any reproducible pattern shows up.
Thanks for the quick response and willingness to help. I’ll let you know if anything definitive turns up.
Joseph4th January 2017 at 10:45 #27764
Thank you for your detailed feedback.
I’ll keep my eyes on this Reaper related issue with LR-16.8th January 2017 at 23:23 #27800
I hope I am not premature on this, but I think the problem is solved. Unfortunately, I don’t know exactly what the detailed fix was!
I came across the following 2 articles:
and implemented most of the suggestions that they had for optimizing Windows 10 for audio. I did not implement them in a controlled fashion so I don’t know if there was a single fix or a combination of fixes that appear to have worked. (Maybe someday I’ll explore that further).
After the optimizations, the system has remained stable and connected for up to six hours before I shut it down. It had never been able to get anywhere close to that time before. So I am keeping my fingers crossed and calling it good.
I’ve included links to the articles which may prove useful to other LR-16 users.
Don’t know if there is anything in the articles that could be “built into” the drivers that would increase stability but you might want to take a look just as a matter of interest.
Joseph9th January 2017 at 10:46 #27804
Many thanks for your feedback.21st June 2017 at 01:29 #28535MartinParticipant21st June 2017 at 10:02 #28537
Do you have this issue with Reaper only?
- You must be logged in to reply to this topic.