Skip to content

Commit 16c1438

Browse files
authored
Merge pull request #51 from membraneframework/code_snippets_colors_fix
code snippets colors fix
2 parents 18d372f + a7a045b commit 16c1438

File tree

12 files changed

+23
-23
lines changed

12 files changed

+23
-23
lines changed

basic_pipeline/01_Introduction.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ In order to be able to proceed with the tutorial, you need to have Elixir instal
99
We assume, that you are at least slightly familiar with that language - if that is not true, we would like to strongly encourage you to take a look at the [official Elixir tutorial](https://elixir-lang.org/getting-started/introduction.html).
1010
Once you are ready with the Elixir, you can get the project template we have prepared for you:
1111

12-
```
12+
```console
1313
git clone https://github.com/membraneframework/membrane_basic_pipeline_tutorial
1414
cd membrane_basic_pipeline_tutorial
1515
git checkout template/start
@@ -35,7 +35,7 @@ Below you can see an exemplary frame sent by one peer to the other. It gets frag
3535

3636
Here is how each packet looks like:
3737

38-
```
38+
```Elixir
3939
[seq:<sequence_id>][frameid:<frame_id>][timestamp:<timestamp>]<text>
4040
```
4141

@@ -50,7 +50,7 @@ where:
5050

5151
We have equipped you with the tool which produces the packets in the format described previously, based on the input conversation. You can use it as a [mix](../glossary/glossary.md#mix) task, by typing:
5252

53-
```
53+
```console
5454
mix generate_input --packetsPerFrame <packets_per_frame> <input_file_path>
5555
```
5656

basic_pipeline/05_Formats.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ That's it! Format modules are really simple - the more complicated thing is to m
3636

3737
Before advancing you can test the `Source` [element](../glossary/glossary.md/#source), using the tests provided in `/test` directory.
3838

39-
```
39+
```console
4040
mix test test/elements/source_test.exs
4141
```
4242

basic_pipeline/06_OrderingBuffer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -180,7 +180,7 @@ Once we have a consistent batch of packets, we can update the state (both the`:o
180180

181181
Test the `OrderingBuffer`:
182182

183-
```
183+
```console
184184
mix test test/elements/ordering_buffer_test.exs
185185
```
186186

basic_pipeline/08_Depayloader.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ Otherwise, if the packet is not of the 'ending' type (that is - it can be both t
157157

158158
Test the `Depayloader`:
159159

160-
```
160+
```console
161161
mix test test/elements/depayloader_test.exs
162162
```
163163

basic_pipeline/09_Mixer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -229,7 +229,7 @@ For all the tracks which are not yet `:finished`, do not have the buffer and the
229229

230230
Test the `Mixer`:
231231

232-
```
232+
```console
233233
mix test test/elements/mixer_test.exs
234234
```
235235

basic_pipeline_extension/03_DynamicPads.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,6 @@ The next thing we need to do is to implement the `handle_pad_added/3` callback,
7272
**_`lib/elements/Mixer.ex`_**
7373

7474
```Elixir
75-
7675
...
7776
@impl true
7877
def handle_pad_added(pad, _context, state) do

basic_pipeline_extension/04_Tests.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -156,7 +156,7 @@ With the Membrane's testing framework you can do it in one line only!
156156

157157
Now we can run the tests with a simple [mix](../glossary/glossary.md#mix) task, by typing:
158158

159-
```
159+
```console
160160
mix test
161161
```
162162

broadcasting/03_RTMP_RunningTheDemo.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,20 +8,20 @@ use cases of Membrane in real-life scenarios.
88

99
In order to run the demo, you need to clone the Membrane demos repository first:
1010

11-
```
11+
```console
1212
git clone https://github.com/membraneframework/membrane_demo
1313
cd membrane_demo/rtmp_to_hls
1414
```
1515

1616
Once in the project directory, you need to get the dependencies of the project:
1717

18-
```
18+
```console
1919
mix deps.get
2020
```
2121

2222
Finally, you can run the application with the following command:
2323

24-
```
24+
```console
2525
mix phx.server
2626
```
2727

broadcasting/04_RTMP_Pipeline.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,7 @@ scope "/", RtmpToHlsWeb do
108108
get "/", PageController, :index
109109
get "/video/:filename", HlsController, :index
110110
end
111+
```
111112

112113
We are directing HTTP requests on `/video/:filename` to the HlsController, whose implementation is shown below:
113114
**_`lib/rtmp_to_hls_web/controllers/hls_controller.ex`_**

broadcasting/H264_codec.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,13 +17,13 @@ There are different types of both VCL and Non-VCL units - for more information o
1717
>
1818
> With the use of Membrane Framework, you can inspect the types of NALus in your h264 file. To do so, you need to clone the H264 parser repository with:
1919
>
20-
> ```
20+
> ```console
2121
> git clone https://github.com/membraneframework/membrane_h264_ffmepg_plugin
2222
> ```
2323
>
2424
> Later on, inside the repository's directory, you can launch the Elixir's interactive shell, with compiled modules from the repository's mix project, by typing:
2525
>
26-
> ```
26+
> ```console
2727
> iex -S mix
2828
> ```
2929
>

0 commit comments

Comments
 (0)