-
Notifications
You must be signed in to change notification settings - Fork 7
CCSMB-5: PCM Audio Transmissions over modem #18
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
base: master
Are you sure you want to change the base?
Changes from 1 commit
a170d9f
01afc24
08e8161
b8fab17
a7a79e5
3445da9
8ca7b64
bccaf85
aa863e1
c5a8320
2f87bec
1b026dd
eb04510
5122823
70dba1f
779b4e9
2d2b02f
f6179e0
05e4960
953963f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,17 +7,17 @@ | |
| A client will only listen to packets while the audio is being transmitted from a server | ||
| The server will communicate to the client over modem | ||
|
|
||
|
|
||
| ## Packet | ||
| A packet consists of the following fields in a table: | ||
| - buffer: A table that contains Signed 8-bit PCM @ 48kHz audio | ||
| - station: A string that contains the name of the radio station | ||
| - title: A string that contains the song that is currently being played | ||
| - protocol: A string that contains the protocol used | ||
| - `buffer`: A table that contains Signed 8-bit PCM @ 48kHz audio | ||
| - `id`: The ID of the server sending the message | ||
| - `station`: A string that contains the name of the radio station | ||
| - `title`: A string that contains the song that is currently being played, or other relevant metadata | ||
|
piprett marked this conversation as resolved.
Outdated
|
||
| - `protocol`: A string that contains the protocol used | ||
|
|
||
| In order to be compliant the | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is worded a bit informally; I'd prefer it to use full sentences in bullet points or an ordered list. We should also mention RFC 2119 if using keywords like "MUST", "SHOULD", etc.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you write an example, I feel like writing the same |
||
| - protocol field must be "CCSMB-5" | ||
|
EmmaKnijn marked this conversation as resolved.
Outdated
|
||
| - client must be able to accept the buffer field | ||
| - client must be able to deal with crosstalk by allowing the user to select a station if there are multiple stations on a single channel | ||
|
EmmaKnijn marked this conversation as resolved.
Outdated
|
||
| - client must reject a packet with an invalid protocol field | ||
| - server must be able to transmit all of the fields | ||
| - client must reject a packet with an invalid `protocol` field | ||
| - server must time the packets appropriately in a way that the client is just able to play back the buffer | ||
|
EmmaKnijn marked this conversation as resolved.
Outdated
|
||
Uh oh!
There was an error while loading. Please reload this page.