After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 784872 - osxaudio: Audio fails to upmix mono channel to stereo
osxaudio: Audio fails to upmix mono channel to stereo
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
1.12.1
Other Mac OS
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-07-12 19:50 UTC by Jacob Adamson
Modified: 2018-05-07 15:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Full log (7.06 KB, application/gzip)
2017-07-13 16:04 UTC, Jacob Adamson
Details

Description Jacob Adamson 2017-07-12 19:50:52 UTC
When completing one of the tutorials for gstreamer, [Basic Tutorial 8](https://gstreamer.freedesktop.org/documentation/tutorials/basic/short-cutting-the-pipeline.html), the pipeline failed to play content with a not-negotiated message.

After a bit of debugging, it turns out the reason was because the appsrc was being configured as a single channel source, and the audiosink only supported 2 channel playback. Changing the caps on the appsrc to 2 channels worked around the problem, but I would have expected the single channel source to be upmixed to 2 channels.

[log](https://pastebin.com/mAHtLsQh)
Comment 1 Tim-Philipp Müller 2017-07-13 08:24:07 UTC
Could you dump the full log into a file, gzip it and attach it here please?

The paste only has the last 50 lines before not-negotiated.
Comment 2 Jacob Adamson 2017-07-13 16:04:56 UTC
Created attachment 355531 [details]
Full log

Ah, here's the full log
Comment 3 Tim-Philipp Müller 2017-07-13 16:23:44 UTC
I meant a log where the not-negotiated error happens, before you worked around it :)
Comment 4 Sebastian Dröge (slomo) 2018-05-07 15:58:52 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!