[2.78 testbuild2] AL lib: (EE) ALCplaybackAlsa_mixerNoMMapProc: available update failed: Broken pipe #49208

New Issue

sn0w75-4 · 2016-08-31T00:22:24+02:00

sn0w75-4 commented

2016-08-31 00:22:24 +02:00

System Information
Ubuntu 14.04, 64-bit.
Graphics card is NVIDIA GTX 670, NVIDIA driver version is 370.23 (beta).

Blender Version
Broken: http://download.blender.org/release/Blender2.78/blender-2.78-testbuild2-linux-glibc219-x86_64.tar.bz2
Worked: 2.77a

Short description of error
Startup Blender from a console, this error message gets printed to the console.

I haven't tried to playback any audio within Blender after getting this error, let me know if I should do some testing in this regard.

Does not occur in 2.77a.

**System Information** Ubuntu 14.04, 64-bit. Graphics card is NVIDIA GTX 670, NVIDIA driver version is 370.23 (beta). **Blender Version** Broken: http://download.blender.org/release/Blender2.78/blender-2.78-testbuild2-linux-glibc219-x86_64.tar.bz2 Worked: 2.77a **Short description of error** Startup Blender from a console, this error message gets printed to the console. I haven't tried to playback any audio within Blender after getting this error, let me know if I should do some testing in this regard. Does not occur in 2.77a.

sn0w75-4 commented

2016-08-31 00:22:24 +02:00

Changed status to: 'Open'

sn0w75-4 commented

2016-08-31 00:22:24 +02:00

Added subscriber: @sn0w75-4

Sergey Sharybin commented

2016-08-31 11:28:13 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2016-08-31 11:28:13 +02:00

This is an error message printed by OpenAL library, so we can't really control this output. Things to check:

Check if the audio actually works. If it does work, then just ignore the message from the console ;)
Check if this happens with glibc211 builds.

This is an error message printed by OpenAL library, so we can't really control this output. Things to check: - Check if the audio actually works. If it does work, then just ignore the message from the console ;) - Check if this happens with glibc211 builds.

sn0w75-4 commented

2016-09-04 17:31:32 +02:00

OK, I did some testing with the new Release Candidate 1 builds.

The issue (error printed to console) still occurs in rc1-glibc219.
The issue does not occur in rc1-glibc211.

testbuild2 download links went down when rc1 went up, so I haven't tested testbuild2-gilbc211, but I would presume the issue does not occur in that build either.

Testing audio playback by loading an OGG file and playing it back in the Video Sequence Editor:

In rc1-glibc211, the OGG file played back normally.
In rc1-glibc219, while playing back the OGG file resulted in audible sound, on one attempt the playback was choppy, and on another attempt I got noise that didn't resemble the OGG at all.

I have a HDMI recorder I can use to record the audio playback in rc1-glibc211 vs. rc1-glibc219 if you'd like me to.

OK, I did some testing with the new Release Candidate 1 builds. * The issue (error printed to console) still occurs in rc1-glibc219. * The issue does **not** occur in rc1-glibc211. testbuild2 download links went down when rc1 went up, so I haven't tested testbuild2-gilbc211, but I would presume the issue does not occur in that build either. Testing audio playback by loading an OGG file and playing it back in the Video Sequence Editor: * In rc1-glibc211, the OGG file played back normally. * In rc1-glibc219, while playing back the OGG file resulted in audible sound, on one attempt the playback was choppy, and on another attempt I got noise that didn't resemble the OGG at all. I have a HDMI recorder I can use to record the audio playback in rc1-glibc211 vs. rc1-glibc219 if you'd like me to.

Sergey Sharybin commented

2016-09-04 17:51:05 +02:00

Does the issue happen with any sound? Any chance you can share ogg file which caused issue for you?

sn0w75-4 commented

2016-09-04 18:40:37 +02:00

It seems to occur with any sound (I tested 3 different OGG files and 2 different MP3 files, all were either choppy or noisy when played back).

Here's one of the OGG files I tested.

prep.ogg

It seems to occur with any sound (I tested 3 different OGG files and 2 different MP3 files, all were either choppy or noisy when played back). Here's one of the OGG files I tested. [prep.ogg](https://archive.blender.org/developer/F352783/prep.ogg)

Sergey Sharybin commented

2016-09-04 18:44:04 +02:00

Thanks, will have a closer look tomorrow.

Sergey Sharybin commented

2016-09-05 15:20:19 +02:00

Unfortunately, didn't manage to reproduce the issue with any glibc219 builds on neither own system (Debian stable) nor on Ubunto 15.04 system we've got around and nor on the LiveCD of Ubuntu 14.04.

Things to try:

Start blender with factory settings (blender --factory-startup)
Try latest builds from builder.blender.org (i did re-compile OpenAL making sure all proper environment flags are set)
See if the sound exists if you boot Ubuntu 16.04 LiveCD on your machine.
See if you can reproduce the error on another machine.

Unfortunately, didn't manage to reproduce the issue with any glibc219 builds on neither own system (Debian stable) nor on Ubunto 15.04 system we've got around and nor on the LiveCD of Ubuntu 14.04. Things to try: - Start blender with factory settings (`blender --factory-startup`) - Try latest builds from builder.blender.org (i did re-compile OpenAL making sure all proper environment flags are set) - See if the sound exists if you boot Ubuntu 16.04 LiveCD on your machine. - See if you can reproduce the error on another machine.

sn0w75-4 commented

2016-09-05 17:06:28 +02:00

The error message and choppy/glitched sound persists when starting blender 2.78-rc1 with factory settings (--factory-startup).

On the latest glibc219 build from builder.blender.org, the error message and choppy/glitched sound still occurs, although there was one instance where it randomly played back a sound normally despite the error message still being printed to console.

Fortunately this issue isn't critical since it seems to only occur on glibc19 builds.
I'll try to get around to some 16.04 LiveCD tests on my machine as well as another machine soon.

The error message and choppy/glitched sound persists when starting blender 2.78-rc1 with factory settings (--factory-startup). On the latest glibc219 build from builder.blender.org, the error message and choppy/glitched sound still occurs, although there was one instance where it randomly played back a sound normally despite the error message still being printed to console. Fortunately this issue isn't critical since it seems to only occur on glibc19 builds. I'll try to get around to some 16.04 LiveCD tests on my machine as well as another machine soon.

Sergey Sharybin commented

2016-09-05 17:21:51 +02:00

The thing is hat glibc211 environment is really tricky for maintenance now, and really difficult to add new dependencies we need (for example, HMD support thingies). So eventually we'll be retiring glibc211 sooner than later. So from this point of view we have to figure out what causes the problem.

I did another trick: just used OpenAL libraries from glibc211 environment now. Mind downloading fresh buildbot version again and give it a try? :)

The thing is hat glibc211 environment is really tricky for maintenance now, and really difficult to add new dependencies we need (for example, HMD support thingies). So eventually we'll be retiring glibc211 sooner than later. So from this point of view we have to figure out what causes the problem. I did another trick: just used OpenAL libraries from glibc211 environment now. Mind downloading fresh buildbot version again and give it a try? :)

sn0w75-4 commented

2016-09-05 18:14:16 +02:00

Ahhh, I see, I wasn't aware of those circumstances.

Glad to help :) I tried out 922aefb-glibc219, issue does not occur in this latest build (no error msg in console, sound seems to play normally)

Ahhh, I see, I wasn't aware of those circumstances. Glad to help :) I tried out 922aefb-glibc219, **issue does not occur in this latest build** (no error msg in console, sound seems to play normally)

Sergey Sharybin commented

2016-09-05 22:01:59 +02:00

That is interesting. Would be really curios to know why. Could be some compiler bug, or issue in OpenAL code which is visible when new compilers are used..

Would you mind doing some more tests in the coming days so we'll figure out the root of the issue? (just afraid at some point we'll have to update OpenAL and if we can't compile proper lib in a new environment it'll be a real bummer :S).

That is interesting. Would be really curios to know why. Could be some compiler bug, or issue in OpenAL code which is visible when new compilers are used.. Would you mind doing some more tests in the coming days so we'll figure out the root of the issue? (just afraid at some point we'll have to update OpenAL and if we can't compile proper lib in a new environment it'll be a real bummer :S).

sn0w75-4 commented

2016-09-06 13:18:26 +02:00

Yeah, I don't mind. Just make a comment on the ticket and I'll get on it as soon as I can.