Skip to content
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

Add tutorial: setting-up Bluetooth - PulseAudio #24

Open
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

BertLindeman
Copy link
Contributor

Probably needs more work, but this is a good stage to ask for comments.
On Windows the tutorials page did not look OK:
tutorial_on_win7

But that could well be a jekyll on win artefact.

Formatting still needs work
…-up-bluetooth-audio-with-pulseaudio.md

rename to conform with the existing tutorials
@dlech
Copy link
Member

dlech commented Nov 18, 2014

But that could well be a jekyll on win artifact.

If you have not recently, run bundle update. Also, it should be serving over http://, not file://

---

### Overview
Debian jessie is using BlueZ 5 and PluseAudio 5, which are fairly new.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leading spaces here are causing line break problems.

@dlech
Copy link
Member

dlech commented Nov 18, 2014

This is not very readable as-is, so I will let you clean it up a bit based on my comments and then have a look at it again.

First markdown cleanup round
Updated titles to conform to existing tutorials
Format of "pactl list cards" output is horrible.
@BertLindeman
Copy link
Contributor Author

I assUme commit 5565cd7 is included as the diffs above are marked "outdated"

The format of the output of 'pactl list cards' is horrible on windows
but in github OK, but the numbered list restarts after this output. It should not.
There is probably more formatting not completely correct.
Thanks David.

@dlech
Copy link
Member

dlech commented Nov 18, 2014

GitHub and GitHub pages use different markdown engines, so it is possible that there are some differences. If things are still looking horrible on windows, they probably will look horrible everywhere. Be sure you are following the instructions from here to preview on Windows. Also, you can create a gh-pages branch in your fork of this repo and see what it will actually look like on the web (should be the same as viewing locally if you are doing it right).

**This should all be done as root**

1. Install pulseaudio:
apt-get install --no-install-recommends pulseaudio pulseaudio-module-bluetooth
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, you need a blank line between the line that starts with 1. and the line with the "code".

@dlech
Copy link
Member

dlech commented Nov 18, 2014

This should help: http://kramdown.gettalong.org/syntax.html

[PulseAudio 5 only supports the A2DP profile and not Headset profile (HSP) or Hands-free profile (HFP)](http://www.freedesktop.org/wiki/Software/PulseAudio/Notes/5.0/),
although it is under development see [note 2].

The A2DP profile supports:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should say that running PulseAudio provides these two profiles and that the device we are connecting to needs to have at least one of these profiles.

@WasabiFan
Copy link
Member

@BertLindeman

But that could well be a jekyll on win artefact.

From your screenshot, it doesn't look like you are looking at it from the server. The path in the address bar is a "file://" URI, which will just retrieve raw page content (without styles). Open the server (usually http://localhost:4000/) and it should work better, assuming you have the server running.

formatting
Changed bluetoothctl into brickman
@BertLindeman
Copy link
Contributor Author

@dlech @WasabiFan Thanks for all the tutorial and guiding.
Updated formatting
Changed bluetoothctl into brickman

---

### Overview
Debian jessie is using BlueZ 5 and PluseAudio 5, which are fairly new.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Get rid of trailing spaces to prevent line breaks. This applies to the whole file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On some places it's a matter of taste, but you are right. will do.

Formatting (again)
add brickman images to images directory
images still need some color work
dim the images background

### Automatically load driver modules for Bluetooth hardware
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lines between .ifexists and .endif should be indented. Here and below.

@dlech
Copy link
Member

dlech commented Nov 19, 2014

I just learned something new. It appears that in kramdown, when using ordered lists the indent depends on where the text after the number starts, so it may not necessarily be a multiple of 4. I was noticing that under numbered items, the code blocks had one or 2 leading spaces.

I would like to keep the indents a multiple of 4, so the way to fix this is to add an extra space between the number and the text if the number is a single digit. Like so...

1.  Some text...
    If there more than one line, it is indented the same.
    ^
123456789
        v
        This is a code block

I added the numbers and "arrows" to make it easier to see how many spaces there are.

Scale images to 356x256 and adapt the markdown to that.
Extra space on numbered list items
Some less indent, some more indent.
@BertLindeman
Copy link
Contributor Author

At the moment I wonder if the BT-keyboard tutorial in ev3dev is indeed an enhancement.
A pointer to https://wiki.archlinux.org/index.php/bluetooth_keyboard may be enough.
What do you think?

@dlech
Copy link
Member

dlech commented Nov 21, 2014

The Arch wiki page is way too much info. You just set you keyboard to discoverable, then pair it and connect using brickman. That's it.

@BertLindeman
Copy link
Contributor Author

OK, Let me start on it. I do not have a BT-keyboard.
So I will re-use some Brickman screens.
It will probably take a few days as I need to do other things :-(

Add the BT keyboard tutorial
@BertLindeman
Copy link
Contributor Author

Please verify the BT keyboard procedure, I do not have one to test this with :-(

removed step 1 from keyboard procedure
screenshots scaled with interpolation "none"
Not longer wooly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants