-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.2.2 Sound drops out during recording (ubuntu 18.04) #9732
Comments
Commented by: uklotzde The issue is unrelated to recording. How many decks and samplers are you using at once? We should consider increasing the hard-coded limits of CachingReader to prevent such a shortage of resources. |
Commented by: uklotzde Do you have the complete log from that session? We have never seen this error before. It's difficult to reason about what exactly blocked the processing and recycling of cached sample data chunks. As a consequence incoming read requests have been dropped. |
Commented by: eberlin 2 decks, no samplers. ivy bridge, 8gb ram, nvidia sound (now running latest nvidia driver) I don't know how much ram was in use as I did have Chrome open, but the case in May (unfortunately no log available) was only running mixxx. In March I successfully made a few recordings, browser open and all. Due to partitioning, my main library is the same partition as my primary, but I have a physically separate internal HDD (neither are solid state) where I somehow still have other library titles. I sometimes forget to mount the drive, as I did in this case, but cannot remember if that was the case in May. |
Commented by: uklotzde Strange. It really looks like that recording has somehow interfered with the processing of audio decoding and the CachingReader ran out of resources. |
Commented by: eberlin I tried another session this evening, just throwing in tracks to get some stuff recorded. It did hiccup again, but eventually powered through. I don't know if it matters, but just before the session with the problem in May, Mixxx was ready to go when I had a power outage (didn't know I was on battery power and that ran out) and I had to manually reset the journal indexing in Ubuntu/grub2 or whatever that process is called |
Commented by: eberlin ok, changing the recording directory to another hard drive worked. I use 320k mp3s and flacs of mostly 6-7 minute long songs and save to 320k mp3 for a sense of how big the file sizes are |
Issue closed with status Fix Released. |
Reported by: eberlin
Date: 2019-09-04T14:36:07Z
Status: Fix Released
Importance: Critical
Launchpad Issue: lp1842679
Attachments: mixxxdebug.log, mixxxdebug2.log
i had the same issue during the previous release at a gig last May and it happened again while trying to record today.
The problem developed after mixing a few tracks and the above is the repeated serious of error messages and once I stopped the recording. Performance went back to normal once I stopped the recording. REcording format was set to MP3
If it matters, I currently have the recording directory the same as my music library, on the same HDD partition, and will experiment tomorrow to see if recording to a separate physical drive makes a difference
The text was updated successfully, but these errors were encountered: