Compiling on Raspberry Pi

[Kriegbaum]

Hi!
I'm trying to get this up and running on a raspberry pi as the title suggests.
I've gone through a lot of dependencies, and at this point I've hit two issues with compiling. One I could fix and one I could not.

error[E0308]: mismatched types
--> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/ffmpeg-next-4.4.0/src/util/error.rs:205:7
|
205 | [[0_i8; AV_ERROR_MAX_STRING_SIZE]; 27];
| ^^^^ expected u8, found i8
|
help: change the type of the numeric literal from i8 to u8
|
205 | [[0_u8; AV_ERROR_MAX_STRING_SIZE]; 27];
| ^^^^

error: aborting due to previous error

For more information about this error, try rustc --explain E0308.
error: failed to compile blissify v0.2.2, intermediate artifacts can be found at /tmp/cargo-installmbmEs8

Caused by:
could not compile ffmpeg-next

To learn more, run the command again with --verbose.

Taking the compiler's suggestion of changing i8 to u8 cleared that one

now I've hit this:

error[E0004]: non-exhaustive patterns: AV_PIX_FMT_SAND64_16, AV_PIX_FMT_RPI4_8 and AV_PIX_FMT_RPI4_10 not covered
--> /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/ffmpeg-next-4.4.0/src/util/format/pixel.rs:413:15
|
413 | match value {
| ^^^^^ patterns AV_PIX_FMT_SAND64_16, AV_PIX_FMT_RPI4_8 and AV_PIX_FMT_RPI4_10 not covered
|
::: /tmp/cargo-installN6hIRT/release/build/ffmpeg-sys-next-85cb1efc39cad5e2/out/bindings.rs:5653:5
|
5653 | AV_PIX_FMT_SAND64_16 = 190,
| -------------------- not covered
5654 | AV_PIX_FMT_RPI4_8 = 191,
| ----------------- not covered
5655 | AV_PIX_FMT_RPI4_10 = 192,
| ------------------ not covered
|
= help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms
= note: the matched value is of type sys::AVPixelFormat

error: aborting due to previous error

For more information about this error, try rustc --explain E0004.
error: failed to compile blissify v0.2.2, intermediate artifacts can be found at /tmp/cargo-installN6hIRT/

Caused by:
could not compile ffmpeg-next

Any idea where to look to fix this?

[Polochon-street]

Hi,
It seems that these AVPixelFomat are specific for ffmpeg on rasperry pi (https://github.com/shantigilbert/Embylogic/blob/master/packages/multimedia/ffmpeg/patches/rpi4-hevc/ffmpeg-001-pfcd_hevc_optimisations.patch here apparently).
Does it work if you change the pixel.rs file and add the values in the enum, a bit like this PR does https://github.com/zmwangx/rust-ffmpeg/pull/60/files#diff-f9150192df441c0071988ac35697c7739854b75cbbd46bc884a36394830b7874R102 ?

On a side-note, bliss' analysis is pretty heavy on the CPU, so depending on the number of songs you have in your library, you might want to analyze them on a tougher CPU, then transfer ~/.local/share/bliss-rs/songs.db to your raspberry pi and use blissify without analyzing everything again. (though the song's paths must match)

[Kriegbaum]

I got it! Looks like there was an 'rpi' compile flag that needed to be set somewhere. I've done a little bit of rust coding but its been a while since I've touched the environments so I just removed the check haha.
Definitely not pretty but got me the binary I was looking for.
Analyzing 11799 songs, this might take some time…
We shall see how the RPI handles this

[Kriegbaum]

Surprisingly, MPD and Snapcast can run uninterrupted in the background while this churns away! Those services often lock and stutter when I'm doing heavy lifting with this little machine

[Polochon-street]

Hi,
I've taken a deeper look, and turns out there's actually a flag for compiling ffmpeg on raspberry pis, as you said 😄

I've made some adjustments so you can actually use it while installing blissify - it should be as simple as running cargo install blissify --features=ffmpeg-next/rpi.

Hope that works for you!

[Polochon-street]

closing this - feel free to reopen if your issue hasn't been solved :)

[kbridger]

I'm hitting the same problem while trying to compile on an rpi. Same error E0004.

Your workaround doesn't seem to be working either. Anything else I can try out?

pi@cookie:~/.cargo/bin $ cargo install blissify --features=ffmpeg-next/rpi
Updating crates.io index
Installing blissify v0.3.5
error: failed to compile blissify v0.3.5, intermediate artifacts can be found at /tmp/cargo-installOS5GmL

Caused by:
none of the selected packages contains these features: ffmpeg-next/rpi

[Polochon-street]

Hi, thanks for reporting :)

I updated bliss / blissify, and you should now be able to do cargo install blissify --features=bliss-audio/rpi. Hope that fixes it!

[Phil-BKK]

Hi, I am very much looking forward to using this however am running into problems compiling on my RPi4. Error data from build below:

error[E0425]: cannot find value AV_PIX_FMT_RPI in this scope
--> /home/pi/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ffmpeg-next-6.0.0/src/util/format/pixel.rs:1213:27
|
1213 | Pixel::RPI => AV_PIX_FMT_RPI,
| ^^^^^^^^^^^^^^ help: a unit variant with a similar name exists: AV_PIX_FMT_0RGB
|
::: /tmp/cargo-installPWnJQZ/release/build/ffmpeg-sys-next-720654b8f40ecd85/out/bindings.rs:5730:5
|
5730 | AV_PIX_FMT_0RGB = 120,
| --------------- similarly named unit variant AV_PIX_FMT_0RGB defined here

Can anyone assist to resolve ?

Thanks in advance

[altesockensuppe]

Hi

$ cargo install --features=ffmpeg-next/rpi
error: none of the selected packages contains these features: ffmpeg-next/rpi

so that I could install blissify-rs I had to add ffmpeg-next with the command cargo add ffmpeg-next.
After that everything worked as desired.

Best
AlteSocke

[Polochon-street]

Hi,

I've just updated some of blissify's dependencies - does cargo install blissify --features=bliss-audio/rpi work out of the box?
I don't have a raspberry pi, so I can't test myself, but it should work 🤞

[altesockensuppe]

Hi @Polochon-street

sadly it fails on ffmpeg-next

Here the procedure on a fresh raspi 3 debian bullseye

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
source "$HOME/.cargo/env"
apt install -y clang libavcodec-dev libavformat-dev libavutil-dev pkg-config
cargo install blissify --features=bliss-audio/rpi
    failed because of missing `libavfilter`
apt install libavfilter-dev
cargo install blissify --features=bliss-audio/rpi
   failed because of missing `libavdevice`
apt install libavdevice-dev
cargo install blissify --features=bliss-audio/rpi
    failed because of missing `ffmpeg-next`

cargo error output

[...]
   Compiling tempdir v0.3.7
   Compiling ndarray-stats v0.5.1
error[E0425]: cannot find value `AV_PIX_FMT_RPI` in this scope
    --> /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ffmpeg-next-6.1.0/src/util/format/pixel.rs:1252:27
     |
1252 |             Pixel::RPI => AV_PIX_FMT_RPI,
     |                           ^^^^^^^^^^^^^^ help: a unit variant with a similar name exists: `AV_PIX_FMT_0RGB`
     |
    ::: /tmp/cargo-installm5PIL6/release/build/ffmpeg-sys-next-86a89553036e5246/out/bindings.rs:3:174597
     |
3    | ...MT_CUDA = 119 , AV_PIX_FMT_0RGB = 120 , AV_PIX_FMT_RGB0 = 121 , AV_PIX_FMT_0BGR = 122 , AV_PIX_FMT_BGR0 = 1...
     |                    --------------- similarly named unit variant `AV_PIX_FMT_0RGB` defined here

For more information about this error, try `rustc --explain E0425`.
error: could not compile `ffmpeg-next` (lib) due to previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile `blissify v0.3.7`, intermediate artifacts can be found at `/tmp/cargo-installm5PIL6`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

try a other way...

git clone https://github.com/Polochon-street/blissify-rs.git
cd blissify-rs
~/.cargo/bin/cargo build --features=bliss-audio/rpi
    error: could not compile `ffmpeg-next` (lib) due to previous error

~/.cargo/bin/cargo add ffmpeg-next
~/.cargo/bin/cargo build --features=bliss-audio/rpi
    same error:
[...]
   Compiling rcue v0.1.3
   Compiling humantime v2.1.0
error[E0425]: cannot find value `AV_PIX_FMT_RPI` in this scope
    --> /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ffmpeg-next-6.1.0/src/util/format/pixel.rs:1252:27
     |
1252 |             Pixel::RPI => AV_PIX_FMT_RPI,
     |                           ^^^^^^^^^^^^^^ help: a unit variant with a similar name exists: `AV_PIX_FMT_0RGB`
     |
    ::: /root/blissify-rs/target/debug/build/ffmpeg-sys-next-a3e9d3125c441cbb/out/bindings.rs:3:174597
     |
3    | ...MT_CUDA = 119 , AV_PIX_FMT_0RGB = 120 , AV_PIX_FMT_RGB0 = 121 , AV_PIX_FMT_0BGR = 122 , AV_PIX_FMT_BGR0 = 1...
     |                    --------------- similarly named unit variant `AV_PIX_FMT_0RGB` defined here
[...]
error: could not compile `ffmpeg-next` (lib) due to previous error

~/.cargo/bin/cargo clean
~/.cargo/bin/cargo build --features=bliss-audio/rpi --features=ffmpeg-next/rpi
    same `ffmpeg-next` error

~.cargo/bin/cargo install blissify --features=bliss-audio/rpi --features=ffmpeg-next/rpi
    again a `ffmpeg-next` error
error: failed to compile `blissify v0.3.7`, intermediate artifacts can be found at `/tmp/cargo-installSYrFS6`.
To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.

Caused by:
  none of the selected packages contains these features: ffmpeg-next/rpi

Best
AlteSocke

[Phil-BKK]

Greetings!

There is a ticket open against rust-ffmpeg related to this:

115 - Handle unsupported pixel formats properly

zmwangx/rust-ffmpeg#114

Cheers

Phil...

[Polochon-street]

Hi,

Thanks for the heads-up. I managed to find a Raspberry Pi 4B and try it out, and it seems that doing cargo install blissify (without the feature) works - I could do blissify init and blissify playlist just fine.

Could you try it out? Otherwise I'll see what I can do to reproduce.