synthnassizer
commented
7 years ago Hi there, you'll need to add you user in audio group , and provide realtime scheduling access to the "audio" group. this may help https://askubuntu.com/questions/166126/unable-to-start-jack-cannot-allocate-memory this will solve the "ERROR: Cannot lock down 82274202 byte memory area (Cannot allocate memory)" "ERROR: Cannot use real-time scheduling (RR/10)(1: Operation not permitted" issue.
However you have a more important issue. Virtualbox is just one process of your main pc (where virtualbox is installed) and it may or may NOT be executed often and fast enough. This mean that even though you may use a preemptive kernel in Ubuntu VM, will cannot actually guarantee running the jack server in "real-time".
Unless someone has a solution for this , I suggest running you Ubuntu OS with jack server directly in some other hardware - even a very old PC will suffice. Also, to make your life easier you may want to use Ubuntu based distros that have already taken care of all the stuff that need tweaking such as the "realtime scheduling" of the audio group. Such distros are Ubuntustudio and KXstudio.
Best regards, Athanasios
On Wed, Nov 1, 2017 at 4:30 AM, Tres Finocchiaro notifications@github.com wrote:
For unit testing, I'm working from Ubuntu 14.04 and trying to setup jack. I want the simplest setup for the fastest unit test. The documentation suggests suspending PulseAudio and starting jackd are the way to go, so my server prefix is pasuspender -- /usr/bin/jackd, per instruction http://jackaudio.org/faq/pulseaudio_and_jack.html#option-4-suspend-pulseaudio-while-jack-is-running (Option 4 -- suspend pulseaudio).
The configuration is default with exception of that change. Screenshot here https://user-images.githubusercontent.com/6345473/32257035-fc184340-be88-11e7-9158-dae0f37125d1.png .
The error message is as follows:
22:03:59.640 Patchbay deactivated. 22:03:59.661 Statistics reset. 22:03:59.690 ALSA connection change. 22:04:00.130 D-BUS: Service is available (org.jackaudio.service aka jackdbus). Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started 22:04:00.163 ALSA connection graph change. 22:05:05.585 D-BUS: JACK server could not be started. Sorry Tue Oct 31 22:04:40 2017: Starting jack server... Tue Oct 31 22:04:40 2017: JACK server starting in realtime mode with priority 10 Tue Oct 31 22:04:40 2017: ERROR: Cannot lock down 82274202 byte memory area (Cannot allocate memory) Tue Oct 31 22:04:40 2017: Acquired audio card Audio0 Tue Oct 31 22:04:40 2017: creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit Tue Oct 31 22:04:40 2017: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods Tue Oct 31 22:04:40 2017: ALSA: final selected sample format for capture: 16bit little-endian Tue Oct 31 22:04:40 2017: ALSA: use 2 periods for capture Tue Oct 31 22:04:40 2017: ALSA: final selected sample format for playback: 16bit little-endian Tue Oct 31 22:04:40 2017: ALSA: use 2 periods for playback Tue Oct 31 22:04:41 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: Operation not permitted) Tue Oct 31 22:04:41 2017: ERROR: AcquireSelfRealTime error Tue Oct 31 22:04:46 2017: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out Tue Oct 31 22:04:46 2017: ERROR: Driver is not running Tue Oct 31 22:04:46 2017: ERROR: Cannot open client name = dbusapi Tue Oct 31 22:04:46 2017: ERROR: failed to create dbusapi jack client Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started 22:11:04.377 Could not connect to JACK server as client. - Overall operation failed. - Server communication error. Please check the messages window for more info. Cannot read socket fd = 25 err = Success CheckRes error JackSocketClientChannel read fail Cannot open qjackctl client Tue Oct 31 22:11:04 2017: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out Tue Oct 31 22:11:04 2017: ERROR: Driver is not running Tue Oct 31 22:11:04 2017: ERROR: Cannot create new client
I also tried disabling PA, no respawn (user and system), launching jackd from CLI, etc to no avail.
I feel obliged to admit the similarities with #116 https://github.com/jackaudio/jack2/issues/116 (comments deemed out of scope) https://github.com/jackaudio/jack2/issues/116#issuecomment-340901460.
In addition to this problem, I've tried some other combinations of VirtualBox + Linux OS to no success. The only Jack back-end I can get working is a dummy back-end.
Some additional information that may be relevant...
VirtualBox ships with three hardware emulations:
- Intel HD Audio
- ICH AC97
- SoundBlaster 16
By default, AC97 is selected, but I've also tried with SoundBlaster 16 to no avail.
I'd be happy to list the hardware setup, but this is an otherwise vanilla Ubuntu 14.04 install inside of VirtualBox, so the hardware is emulated and should be reproducible.
To rule out host hardware as the culprit, I've reproduced on three separate VM hosts (separate physical machines) including Windows and MacOS.
Finally, I've reproduced what I believe to be the same symptoms on Fedora Core 26 as well. The Fedora wiki steps https://fedoraproject.org/wiki/JACK_Audio_Connection_Kit didn't help fix the issue.
Sorry in advanced if this is a support issue. I feel I've done enough research and testing before filing.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jackaudio/jack2/issues/304, or mute the thread https://github.com/notifications/unsubscribe-auth/AGb0dSEBpYX-osvSeQlcaIJWL8578hp7ks5sx9fjgaJpZM4QNq0Z .
tresf
For unit testing, I'm working from Ubuntu 14.04 and trying to setup jack. I want the simplest setup for the fastest unit test. The documentation suggests suspending PulseAudio and starting jackd are the way to go, so my server prefix is
pasuspender -- /usr/bin/jackd, per instruction (Option 4 -- suspend pulseaudio).The configuration is default with exception of that change. Screenshot here. I do not have realtime enabled although
qjackctldoesn't seem to know that out of the box. Neither unchecking it nor checking it and doing theaudiogroup / logout method has helped.The error message is as follows:
I also tried disabling PA, no respawn (user and system), launching
jackdfrom CLI, etc to no avail.I feel obliged to admit the similarities with #116 (comments deemed out of scope).
In addition to this problem, I've tried some other combinations of VirtualBox + Linux OS to no success. The only Jack back-end I can get working is a dummy back-end.
Some additional information that may be relevant...
VirtualBox ships with three hardware emulations:
By default, AC97 is selected, but I've also tried with SoundBlaster 16 to no avail.
I'd be happy to list the hardware setup, but this is an otherwise vanilla Ubuntu 14.04 install inside of VirtualBox, so the hardware is emulated and should be reproducible.
To rule out host hardware as the culprit, I've reproduced on three separate VM hosts (separate physical machines) including Windows and MacOS.
Finally, I've reproduced what I believe to be the same symptoms on Fedora Core 26 as well. The Fedora wiki steps didn't help fix the issue.
Sorry in advanced if this is a support issue. I feel I've done enough research and testing before filing.