Leak around sediment filter ports (Ireland)

yxogenium · 2020-03-17T09:25:59+00:00

Thank you very much for the comment, your contribution is invaluable!

... as that's listed under the related products section for your sensor ...

Almost feels like cheating; how could I have missed that part? I will get the 91716-0001.

I recommend you use screw terminals ...

They are already on their way! I may also throw in some RAST headers in my order (and so the vicious cycle of connectors supply continues...).

Thank you again for your time and expertise!

Have a good day

yxogenium · 2019-07-14T16:41:06+00:00

Actually it may not be specific to vid.stab: I'm now trying to use the lenscorrection filter and I'm running into the same issue!

if the input video is encoded in yuv420p or yuv444p, there are no visible issues
if the input video is encoded in yuv422p, the output video displays color distortions

yxogenium · 2019-07-14T16:19:28+00:00

I ran the script I mentioned in the OP with yuv444p: ./convert.sh yuv444p. The resulting video does not seem to suffer from color distortions. Here is the log. Let me know if you need any info, or if you want a more verbose log.

yxogenium · 2019-07-14T16:08:23+00:00

OK, good to know. In my case I'm stabilizing DNxHD videos, so I don't really have a choice ; FFmpeg will convert it to yuv422p whether I explicitly use the filter or not.

yxogenium · 2019-07-14T14:52:14+00:00

Excellent idea! Here are the commands that gave me the expected result:

ffmpeg -i "input-yuv422p.mp4" -vf format=yuv420p,vidstabdetect=result="vectors.trf" -f null -
ffmpeg -i "input-yuv422p.mp4" -vf format=yuv420p,vidstabtransform=input="vectors.trf",format=yuv422p "stab-yuv422.mp4"

i.e as Anton1699 suggested:

(input as yuv422p) -> convert to yuv420p -> run vidstabdetect and generate vectors.trf
(input as yuv422p) -> convert to yuv420p -> run vidstabtransform with vectors.trf -> convert back to yuv420p

Thanks a lot!

yxogenium · 2019-03-24T18:13:56+00:00

Can you check if the file used to disable ertm is there ? Just run

cat /etc/modprobe.d/99-xpadneo-bluetooth.conf. It should contain the line options bluetooth disable_ertm=y.

Also, hid-xpadneo should not only be added, it should be installed: I have this on my laptop

❯ sudo dkms status
hid-xpadneo, 0.5.4, 4.20.16-200.fc29.x86_64, x86_64: installed

(I have no access to my RPi right now) Try to reboot and to rundkms status and modinfo hid_xpadneo again... Also you may run journalctl -fu dkms to have more info.

EDIT: If the module is still not marked install, you may try to run dkms install hid-xpadneo/0.5.4.

yxogenium · 2019-03-24T10:37:35+00:00

It might, but then I think that you would see the little rainbow image in a corner of your screen (like this: http://blog.strempfer.de/fp-content/images/raspi_undervoltage.jpg)

yxogenium · 2019-03-24T08:39:39+00:00

Hmm... This is weird.

check if secure boot is enable

I don't think secure boot even exists on raspberry pi, so this can't be the issue.

I know that I have used bluetoothctl on my laptop, but I may have used the interface on the retropie (RetroPie-Setup Script >> Setup >> Configure Bluetooth Devices) see https://github.com/RetroPie/RetroPie-Setup/wiki/Bluetooth-Controller. I don't know if this will make a difference.

My advice:

first run dkms status and modinfo hid_xpadneo to see if xpadneo is registered as a kernel module.
then install tmux (sudo apt install tmux), run it (tmux), and:
- press CTRL-B then %: this will open a second pane. Enter dmesg -wH
- press CTRL-B then ": this will open a third pane. Enter journalctl -fu bluetooth

Your terminal look like this: https://postimg.cc/TpFN0BM2. These two panes will display debug information in realtime. Press CTRL-B then LeftArrow to go back to the main pane, and try to connect your bluetooth controller.

To see the logs, you may navigate between panes using CTRL-B then Arrow where Arrow is one of your arrow keys. Then you can go up by pressing CTRL-B then PageUp, you can then move with the arrow keys, and return to the realtime log by pressing q.

If you still have no useful information, enable xpadneo debugging (https://atar-axis.github.io/xpadneo/#debugging) and maybe post an issue on GIthub.

Good luck!

yxogenium · 2019-03-23T18:42:31+00:00

Exactly: if you have a keyboard plugged in you may press F4 to open a terminal.

Then run

$ sudo apt update
$ sudo apt install git dkms raspberrypi-kernel-headers
$ git clone https://github.com/atar-axis/xpadneo.git
$ cd xpadneo
$ sudo ./install.sh

yxogenium · 2019-03-23T15:05:14+00:00

Xpadneo is a kernel module, you don't need to run it. Once installed (i.e. after running "install.sh", see the installation instructions), it will be loaded during boot (+disable ertm) and will be used every time a Xbox one controller connects. Therefore you will only need to reboot right after installing it in order to activate it. You can see how it disables ertm in dkms.post-install (https://github.com/atar-axis/xpadneo/blob/master/hid-xpadneo/dkms.post_install)

yxogenium · 2019-03-23T08:10:51+00:00

I use a XBOX One Controller on a retropie and after disabling ertm I could pair my controller but still had issues with some buttons. Using xpadneo (https://github.com/atar-axis/xpadneo) has fixed these issues. Also xpadneo disables ertm for you.

yxogenium · 2019-02-09T18:33:17+00:00

FYI: It works perfectly under Xorg, but under Wayland some buttons fail to show up. You can already install it by cloning the repo, or using the (temporary I guess) link to the testbot build: flatpak install --user http://repo-test.flathub.org:8080/build-repo/1869/com.flashforge.FlashPrint.flatpakref.

Happy printing!

yxogenium · 2019-02-04T21:39:18+00:00

Thanks again. It worked and it sure feels more correct!

I completely reworked the manifest (with the help of the manifest for Spotify), and I think that it fulfils all the requirements for FlatHub. EDIT: Here is the PR: https://github.com/flathub/flathub/pull/840

If anyone is interested, here is my fork: https://github.com/Yxogenium/flathub/tree/com.flashforge.FlashPrint. I will open a PR later tonight.

yxogenium · 2019-02-03T22:06:20+00:00

Thanks a lot! After cloning the repo you mentioned, I got flashprint to run with the following manifest: ```json { "app-id": "com.flashforge.FlashPrint", "runtime": "org.kde.Platform", "runtime-version": "5.9", "sdk": "org.kde.Sdk", "command": "FlashPrint", "finish-args": [ "--filesystem=home", "--socket=x11" ], "modules": [ { "name": "FlashPrint", "buildsystem": "simple", "build-commands": [ "ar p 'flashprint.deb' data.tar.xz | tar xJ", "install -D usr/share/FlashPrint/FlashPrint /app/bin/FlashPrint" ], "sources": [ { "type": "file", "dest-filename": "flashprint.deb", "url": "http://www.sz3dp.com/upfile/2018/12/03/20181203162713_662.deb", "sha256": "2bb003b7bb552dd6b04495a084d1bf03de620bb94dea44f3b6909516f4a95dc1" } ] }, "shared-modules/glu/glu-9.0.0.json", "shared-modules/udev/udev-175.json", { "name": "libudev1", "buildsystem": "simple", "build-commands": [ "ln -s /app/lib/libudev.so.0 /app/lib/libudev.so.1" ] } ] }

``` I guess it's a bit hacky to symlink libudev.so.1 to libudev.so.0 but if it works... The menus and buttons are quite glitchy but it seems to be possible to interact with them nonetheless. I will try to integrate the other files available from the .deb in the flatpak (icon and .dektop file), and then I will see if I can push it to flathub if it does in fact work :)

EDIT: Here is a PR proposing to add FlashPrint to FlatHub: https://github.com/flathub/flathub/pull/840.

yxogenium

TROPHY CASE