RPi Cam Web Interface

[btidey]

Minor change to simplify annotation settings. We now always use V3 style annotation as this allows better control. The annotation version selection control (V2/V3) is removed.

Note that V3 relies on having up to date base raspberry support so if you have been using V2 you may need to do a rpi-update if you haven't done one since about March 20th

[silvanmelchior]

This is really a nice addition! Good to have you back and glad to see you will be working on this together.
Since the movements were short in on my cam it always captured a bit to late. Now the video is actually showing the full movement.

What I did notice while reviewing the timestamps in motion started video is something like this :

Suppose a video started motion triggered with timestamp 16:30:01

16:30:01 good video
16:30:02 good video
16:30:00 blurry/still video
16:30:01 blurry/still video
16:30:02 blurry/still video
16:30:03 good video
16:30:04 good video
16:30:05 good video

It jumps back some seconds and shows blurry video those couple of seconds, after that video looks good again.
Any idea what that could be and how to fix it ? I could send you an example video if you would like to check it out.

Sorry, I'm not sure if I understand your observations: Whenever you record a video with buffer enabled, the first few seconds of that video are blurry?

[0lly]

Hi silvanmelchior
Buffer only works if Video_fps = 25 ?
if i set the Video_fps to 10 it crashes.
After reboot

Code: Select all

pi@raspberrypi ~/RPi_Cam_Web_Interface $ ./RPi_Cam_Web_Interface_Installer.sh start
Started
pi@raspberrypi ~/RPi_Cam_Web_Interface $ mmal: mmal_vc_component_enable: failed to enable component: ENOSPC

[piecam]

If I understand this then stopping restarting scheduler releases it from 'frozen state'. Is that right? When it is stuck in this state is it continuing to record to the h264 file or there is a h264 file that just hasn't been converted?

HI Robert,
Yes, that's correct.
The h264 file is not growing anymore and just stays there not being converted to MP3.

Thanks.

[piecam]

HI Robert,

It seems that I don't see any annotation title once I completely do it with new SD card with new distro gits.

However, if I just follow your instructions converting to new GITs, and use my backuped files, I am ok.

New files from completely new install:
uconfig:
annotation Driveway IR %Y.%M.%D_%h:%m:%s
anno_background 1
video_buffer 3000
raspimjpeg:
# annotation max length: 31 characters
annotation RPi Cam %Y.%M.%D_%h:%m:%s
anno_background false
anno3_custom_background_colour 0
anno3_custom_background_Y 0
anno3_custom_background_U 128
anno3_custom_background_V 128
anno3_custom_text_colour 0
anno3_custom_text_Y 255
anno3_custom_text_U 128
anno3_custom_text_V 128
anno_text_size 50

Files from upgrade pi:
uconfig:
annotation Front Door %Y.%M.%D_%h:%m:%s
anno_background true
video_buffer 3000
MP4Box 2

Raspimjpeg:
# annotation max length: 31 characters
annotation RPi Cam %Y.%M.%D_%h:%m:%s
anno_background false
anno_version 2
anno3_custom_background_colour 0
anno3_custom_background_Y 0
anno3_custom_background_U 128
anno3_custom_background_V 128
anno3_custom_text_colour 0
anno3_custom_text_Y 255
anno3_custom_text_U 128
anno3_custom_text_V 128
anno_text_size 50


Upgraded rpi-update as well. Adding anno_version 2 to new install doesn't help as well.
Any thoughts?
thanks

HI Robert,
No worries on this. I did AGAIN "rpi-update" on my completely new install and got annotation working; though, not knowing why.

thanks anyway.

[donster22]

Hi

I have been through 5 installs now trying to figure this out and making changes slowly.
In my install I changed the install directory so now instead of /var/www/ i'm in /var/www/BB/

everything is working fine and I have mounted my NAS as /var/www/BB/media.
manual snapshots and video are being saved properly in this linked directory.

BUT no matter what i do, motion will not work. I have ammended the netcam url in motion.conf to http://localhost/var/www/BB/cam_pic.php is that right?

motion starts but does not register any motion when i dance about infront of the camera.
is there another setting i've overlooked or have I done something else wrong.

any pointers appreciated.
thanks
don

[btidey]

HI Robert,

It seems that I don't see any annotation title once I completely do it with new SD card with new distro gits.
HI Robert,
No worries on this. I did AGAIN "rpi-update" on my completely new install and got annotation working; though, not knowing why.

thanks anyway.

up to date rpi-update is a requirement as wiki says. The new version has simplified annotation code and avoids possible confusion in the config by using v3 annotation only. V2 no longer supported or used.

I don't know why your first rpi-update didn't work unless it wasn't rebooted which is needed to activate the changes.

[btidey]

Hi

I have been through 5 installs now trying to figure this out and making changes slowly.
In my install I changed the install directory so now instead of /var/www/ i'm in /var/www/BB/

everything is working fine and I have mounted my NAS as /var/www/BB/media.
manual snapshots and video are being saved properly in this linked directory.

BUT no matter what i do, motion will not work. I have ammended the netcam url in motion.conf to http://localhost/var/www/BB/cam_pic.php is that right?

motion starts but does not register any motion when i dance about infront of the camera.
is there another setting i've overlooked or have I done something else wrong.

any pointers appreciated.
thanks
don

Personally I wouldn't have recommended relocating the /var/www directory as there may be other dependencies in the web code which may not have not been fully exercised. You should be able to achieve external mounts fine direct from the media folder under /var/www

However, if you have other web sites running under Apache, which could be in conflict then I can see it can be convenient to separate into different folders. In principle, most (or all) should work but it depends on what you are doing with the Apache Document root.

If you have left that at /var/www then all urls are relative to that. Previously the motion url was http://localhost/cam_pic.php because cam_pic.php was in the Document root. So with a Document root left at /var/www and an install folder of /var/www/BB then the url would be http://localhost/BB/cam_pic.php and I assume you browse to http://localhost/BB/index.php to get main page.

[btidey]

If I understand this then stopping restarting scheduler releases it from 'frozen state'. Is that right? When it is stuck in this state is it continuing to record to the h264 file or there is a h264 file that just hasn't been converted?

HI Robert,
Yes, that's correct.
The h264 file is not growing anymore and just stays there not being converted to MP3.

Thanks.

It sounds like the video capture has stopped, but boxing hasn't worked plus the status file that is used to communicate back to the web code has got out of step with reality. I'm not sure how that could happen at the moment.

Assuming you are using background MPBoxing then the buttons should return to an idle status as soon as the raw recording stops and this shouldn't depend on whether boxing succeeds or fails. If you are using inline boxing then the status will be boxing until this operation completes.

Basically raspimjpeg writes it as it goes through these different states (start video, motion detect on, boxing etc) . The web code then reads it to determine how to display the buttons.

The file in question is the status_mjpeg.txt file in the /var/www folder. It just has 1 line in with values like ready, md_ready, md_video, boxing in it. When nothing is happening it should have ready or md_ready in it depending on whether motion detection is on.

So if it appears to freeze check this file. If it says video or md_video then the web will think a capture is still in progress. Similarly if it says boxing and you know MP4Box has stopped then again that would be a real problem. If either case and you know it has stopped then as a test you could edit the file to say ready or md_ready, save it and see what happens to the web interface. Do not add a line feed onto the file, it should have just a single string with no line ending. E.g. a 'ready' file will be 5 bytes long.

[donster22]

Hi

I have been through 5 installs now trying to figure this out and making changes slowly.
In my install I changed the install directory so now instead of /var/www/ i'm in /var/www/BB/

everything is working fine and I have mounted my NAS as /var/www/BB/media.
manual snapshots and video are being saved properly in this linked directory.

BUT no matter what i do, motion will not work. I have ammended the netcam url in motion.conf to http://localhost/var/www/BB/cam_pic.php is that right?

motion starts but does not register any motion when i dance about infront of the camera.
is there another setting i've overlooked or have I done something else wrong.

any pointers appreciated.
thanks
don

Personally I wouldn't have recommended relocating the /var/www directory as there may be other dependencies in the web code which may not have not been fully exercised. You should be able to achieve external mounts fine direct from the media folder under /var/www

However, if you have other web sites running under Apache, which could be in conflict then I can see it can be convenient to separate into different folders. In principle, most (or all) should work but it depends on what you are doing with the Apache Document root.

If you have left that at /var/www then all urls are relative to that. Previously the motion url was http://localhost/cam_pic.php because cam_pic.php was in the Document root. So with a Document root left at /var/www and an install folder of /var/www/BB then the url would be http://localhost/BB/cam_pic.php and I assume you browse to http://localhost/BB/index.php to get main page.

---

Thanks, yes.I'm using the urls you mention but it's not working.
The http://localhost/BB/cam_pic.php is working when i view it in my browser but motion just won't pick up on movements so I'm still a bit stuck.

The reason I'm trying to do this is because I want my current website in /var/www/ It's index.html refreshes every 60 seconds and will pull a cam.jpg in each time it does and then everything else is "behind the scenes" in /var/www/BB/ for me to watch and share when necessary.

Are there any other ideas you think might help or will this not really work? I tried it because it references moving the install folder in the installation notes.

thanks
don

[jbeale]

Nice continued work on this program, silvanmelchior and btidey! Just installed it on a new RPi2 board. I notice when waving my hand in front of the camera and taking a still frame, either with the web button or on a command line with

Code: Select all

echo -n 'im' > /var/www/FIFO

that the resulting image on the download page has a "preview" thumbnail taken near the moment of the command, but the actual full-res image is different and is taken about 1/3 second later (perhaps shutter-speed dependent; this is indoor nightime eg. dim light). I suppose the thumbnail is from the running video preview before it switches into still-capture mode?

[donster22]

Hi

I have been through 5 installs now trying to figure this out and making changes slowly.
In my install I changed the install directory so now instead of /var/www/ i'm in /var/www/BB/

everything is working fine and I have mounted my NAS as /var/www/BB/media.
manual snapshots and video are being saved properly in this linked directory.

BUT no matter what i do, motion will not work. I have ammended the netcam url in motion.conf to http://localhost/var/www/BB/cam_pic.php is that right?

motion starts but does not register any motion when i dance about infront of the camera.
is there another setting i've overlooked or have I done something else wrong.

any pointers appreciated.
thanks
don

Personally I wouldn't have recommended relocating the /var/www directory as there may be other dependencies in the web code which may not have not been fully exercised. You should be able to achieve external mounts fine direct from the media folder under /var/www

However, if you have other web sites running under Apache, which could be in conflict then I can see it can be convenient to separate into different folders. In principle, most (or all) should work but it depends on what you are doing with the Apache Document root.

If you have left that at /var/www then all urls are relative to that. Previously the motion url was http://localhost/cam_pic.php because cam_pic.php was in the Document root. So with a Document root left at /var/www and an install folder of /var/www/BB then the url would be http://localhost/BB/cam_pic.php and I assume you browse to http://localhost/BB/index.php to get main page.

---

Thanks, yes.I'm using the urls you mention but it's not working.
The http://localhost/BB/cam_pic.php is working when i view it in my browser but motion just won't pick up on movements so I'm still a bit stuck.

The reason I'm trying to do this is because I want my current website in /var/www/ It's index.html refreshes every 60 seconds and will pull a cam.jpg in each time it does and then everything else is "behind the scenes" in /var/www/BB/ for me to watch and share when necessary.

Are there any other ideas you think might help or will this not really work? I tried it because it references moving the install folder in the installation notes.

thanks
don

Just to add on this, I have run through the troubleshooting tips here :
https://github.com/silvanmelchior/RPi_C ... RPiCam.pdf

Motion just doesn't trigger at all.
I've also change the destination to a local folder instead of my linked NAS in case it was a permissions issue.

Is there anywhere else to look? Thanks for any help.
Don

[btidey]

Nice continued work on this program, silvanmelchior and btidey! Just installed it on a new RPi2 board. I notice when waving my hand in front of the camera and taking a still frame, either with the web button or on a command line with

Code: Select all

echo -n 'im' > /var/www/FIFO

that the resulting image on the download page has a "preview" thumbnail taken near the moment of the command, but the actual full-res image is different and is taken about 1/3 second later (perhaps shutter-speed dependent; this is indoor nightime eg. dim light). I suppose the thumbnail is from the running video preview before it switches into still-capture mode?

Yes. The thumbnail is a grab of the latest cam.jpg (used for main preview and by motion) taken by raspimjpeg at the moment the capture command is received. raspimjpeg then immediately issues the real capture command to the MMAL camera interface so any lag is down to the delay there.

With video captures using the new circular buffer, the thumbnail is still at the point of processing the trigger command, but the stored video can now start earlier using the data already in the buffer.

[btidey]

[
Thanks, yes.I'm using the urls you mention but it's not working.
The http://localhost/BB/cam_pic.php is working when i view it in my browser but motion just won't pick up on movements so I'm still a bit stuck.

The reason I'm trying to do this is because I want my current website in /var/www/ It's index.html refreshes every 60 seconds and will pull a cam.jpg in each time it does and then everything else is "behind the scenes" in /var/www/BB/ for me to watch and share when necessary.

Are there any other ideas you think might help or will this not really work? I tried it because it references moving the install folder in the installation notes.

Just to add on this, I have run through the troubleshooting tips here :
https://github.com/silvanmelchior/RPi_C ... RPiCam.pdf

Motion just doesn't trigger at all.
I've also change the destination to a local folder instead of my linked NAS in case it was a permissions issue.

Is there anywhere else to look? Thanks for any help.
Don

If you are getting a cam.jpg with that url in the browser and motion is using the same url then file / folder permissions are not the issue. The only thing that would stop motion getting the data it needs then would be if you had put any user / password on the web site and not included that in motion.

From your trouble shooting it sounds like you don't get a trigger out from motion so one needs to check the motion settings. Are you using the defaults except for url changes?

The subfolder you are using should not be a factor here as we are just interested in 4 things; motion running, motion getting the feed of cam.jpg, motion detection settings, and motion action when triggered.

[TepidRPi]

Personally I wouldn't have recommended relocating the /var/www directory as there may be other dependencies in the web code which may not have not been fully exercised. You should be able to achieve external mounts fine direct from the media folder under /var/www

However, if you have other web sites running under Apache, which could be in conflict then I can see it can be convenient to separate into different folders. In principle, most (or all) should work but it depends on what you are doing with the Apache Document root.

If you have left that at /var/www then all urls are relative to that. Previously the motion url was http://localhost/cam_pic.php because cam_pic.php was in the Document root. So with a Document root left at /var/www and an install folder of /var/www/BB then the url would be http://localhost/BB/cam_pic.php and I assume you browse to http://localhost/BB/index.php to get main page.

---

Thanks, yes.I'm using the urls you mention but it's not working.
The http://localhost/BB/cam_pic.php is working when i view it in my browser but motion just won't pick up on movements so I'm still a bit stuck.

The reason I'm trying to do this is because I want my current website in /var/www/ It's index.html refreshes every 60 seconds and will pull a cam.jpg in each time it does and then everything else is "behind the scenes" in /var/www/BB/ for me to watch and share when necessary.

Are there any other ideas you think might help or will this not really work? I tried it because it references moving the install folder in the installation notes.

thanks
don

Just to add on this, I have run through the troubleshooting tips here :
https://github.com/silvanmelchior/RPi_C ... RPiCam.pdf

Motion just doesn't trigger at all.
I've also change the destination to a local folder instead of my linked NAS in case it was a permissions issue.

Is there anywhere else to look? Thanks for any help.
Don

Don't get me wrong. I think this is probably the best add-on created for the PICamera Module

But I also have an existing Apache Server running a site already
The install of this basically wiped it out, luckily It was just a couple of test pages.

I am also interested in this. This is a problem if you run more than one site on your Pi.
The alternative might be to run a Primary Server Pi and URL to that through a link.
I will have to test that, but it should work.
It's could create a band width problem though with WiFi, not sure.

Basically, the code needs fixed to run by default and install by default in a sub directory and not take over an existing install of Apache.

It should check if Apache is already installed and leave it's config files alone.
Add what it may need, but don't change settings that may already exist.
Ok,, it appears to do this.

this is great work so far on the Interface.

the installation and how it works in general needs heavy tweaking.
I just don't see the reason for the choices made in how this operates on the back end.
there is no reason for it to work the way it does.
Wiping out Apache plus everything else shouldn't be necessary
nor should it be necessary to reside solely in /var/www or break.

Thanks.

PS. I am not giving up on it just yet.
If some workarounds don't work, then I will I think. maybe. we'll see.

[donster22]

[

If you are getting a cam.jpg with that url in the browser and motion is using the same url then file / folder permissions are not the issue. The only thing that would stop motion getting the data it needs then would be if you had put any user / password on the web site and not included that in motion.

From your trouble shooting it sounds like you don't get a trigger out from motion so one needs to check the motion settings. Are you using the defaults except for url changes?

The subfolder you are using should not be a factor here as we are just interested in 4 things; motion running, motion getting the feed of cam.jpg, motion detection settings, and motion action when triggered.

Thanks for bearing with me!

Yes, after editing the installtion file so that it installs to /var/www/BB/ the motion url is the only thing i have changed.

Just as a control I have just reinstalled it on a fresh and updated raspian image to the standard installation folder and everything works fine so I'm puzzled.

If I can't get it fixed I will set up a second pi as my webserver and bring the images and videos in from the original pi running RPi Cam Web Interface but that's not ideal.

I do hope i'm not just being daft (it sometimes happens )

[TepidRPi]

[

If you are getting a cam.jpg with that url in the browser and motion is using the same url then file / folder permissions are not the issue. The only thing that would stop motion getting the data it needs then would be if you had put any user / password on the web site and not included that in motion.

From your trouble shooting it sounds like you don't get a trigger out from motion so one needs to check the motion settings. Are you using the defaults except for url changes?

The subfolder you are using should not be a factor here as we are just interested in 4 things; motion running, motion getting the feed of cam.jpg, motion detection settings, and motion action when triggered.

Thanks for bearing with me!

Yes, after editing the installtion file so that it installs to /var/www/BB/ the motion url is the only thing i have changed.

Just as a control I have just reinstalled it on a fresh and updated raspian image to the standard installation folder and everything works fine so I'm puzzled.

If I can't get it fixed I will set up a second pi as my webserver and bring the images and videos in from the original pi running RPi Cam Web Interface but that's not ideal.

I do hope i'm not just being daft (it sometimes happens )

I don't think you are being daft.
I just did it following the instructions and nothing worked at all.

But, I have a second Pi that I am installing it on now,, repairing my original server
and will use it as a remote camera if possible.

In retrospect, this would be it's primary intention.
Therefore, running it as a secondary tool on a Primary Apache Server is actually not ideal.
With that said, Options should be available, and work.
In this case, moving the interface from it's primary intended location, does not work.

[btidey]

Don't get me wrong. I think this is probably the best add-on created for the PICamera Module

But I also have an existing Apache Server running a site already
The install of this basically wiped it out, luckily It was just a couple of test pages.

I am also interested in this. This is a problem if you run more than one site on your Pi.
The alternative might be to run a Primary Server Pi and URL to that through a link.
I will have to test that, but it should work.
It's could create a band width problem though with WiFi, not sure.

Basically, the code needs fixed to run by default and install by default in a sub directory and not take over an existing install of Apache.

It should check if Apache is already installed and leave it's config files alone.
Add what it may need, but don't change settings that may already exist.

this is great work so far on the Interface.

the installation and how it works in general needs heavy tweaking.
I just don't see the reason for the choices made in how this operates on the back end.
there is no reason for it to work the way it does.
Wiping out Apache plus everything else shouldn't be necessary
nor should it be necessary to reside solely in /var/www or break.

Thanks.

PS. I am not giving up on it just yet.
If some workarounds don't work, then I will I think. maybe. we'll see.

Appreciate the comments. As I understand it the original install script was set up to be simple and easy to set up dedicated web site application. That I think was initially attractive to the first users as they didn't have to struggle with installing and configuring many bits and pieces to get going.

However, you are right that it does not sit comfortably with trying to co-exist with other web usage and even getting new versions with 'install' tended to wipe out any RPi Cam Interface config changes made by the user.

As a quick fix for the latter issue I added an update action to the script which does not change any base software or internal configs so is more benign in that respect.

I think use of the sub-folder installs should work. The only reason for being cautious there is that there has not been much testing of that facility. If people can not only test that but feedback any problems / fixes they have to apply then those can be incorporated.

On the initial install respecting existing material then it looks like that should work providing the rpicamdir variable is set up before running the script. I appreciate that it is too easy to run the install without realising that. That could be mentioned in the wiki or even better if someone want to contribute a tweak that asks for it first.

Another weakness here is the /etc/rc.local handling which is ensuring that boot starts are set up correctly for RPi Cam Interface usage but will wipe out other material.

As a general comment it would be good to enter issues like this on the github so they can be tracked better as they will tend to get lost here.

[TepidRPi]

Don't get me wrong. I think this is probably the best add-on created for the PICamera Module

But I also have an existing Apache Server running a site already
The install of this basically wiped it out, luckily It was just a couple of test pages.

I am also interested in this. This is a problem if you run more than one site on your Pi.
The alternative might be to run a Primary Server Pi and URL to that through a link.
I will have to test that, but it should work.
It's could create a band width problem though with WiFi, not sure.

Basically, the code needs fixed to run by default and install by default in a sub directory and not take over an existing install of Apache.

It should check if Apache is already installed and leave it's config files alone.
Add what it may need, but don't change settings that may already exist.

this is great work so far on the Interface.

the installation and how it works in general needs heavy tweaking.
I just don't see the reason for the choices made in how this operates on the back end.
there is no reason for it to work the way it does.
Wiping out Apache plus everything else shouldn't be necessary
nor should it be necessary to reside solely in /var/www or break.

Thanks.

PS. I am not giving up on it just yet.
If some workarounds don't work, then I will I think. maybe. we'll see.

Appreciate the comments. As I understand it the original install script was set up to be simple and easy to set up dedicated web site application. That I think was initially attractive to the first users as they didn't have to struggle with installing and configuring many bits and pieces to get going.

However, you are right that it does not sit comfortably with trying to co-exist with other web usage and even getting new versions with 'install' tended to wipe out any RPi Cam Interface config changes made by the user.

As a quick fix for the latter issue I added an update action to the script which does not change any base software or internal configs so is more benign in that respect.

I think use of the sub-folder installs should work. The only reason for being cautious there is that there has not been much testing of that facility. If people can not only test that but feedback any problems / fixes they have to apply then those can be incorporated.

On the initial install respecting existing material then it looks like that should work providing the rpicamdir variable is set up before running the script. I appreciate that it is too easy to run the install without realising that. That could be mentioned in the wiki or even better if someone want to contribute a tweak that asks for it first.

Another weakness here is the /etc/rc.local handling which is ensuring that boot starts are set up correctly for RPi Cam Interface usage but will wipe out other material.

As a general comment it would be good to enter issues like this on the github so they can be tracked better as they will tend to get lost here.

Thank you for the reply. I will try to do that.
I ahve too much going now to get to it though.

[xab]

How can I build raspimjpeg?

[mahjongg]

How can I build raspimjpeg?

I don't know, but maybe you could start by reading this: viewtopic.php?f=43&t=61771

[silvanmelchior]

How can I build raspimjpeg?

Clone Robert's fork of the userland and run the buildme-script in it, it will replace /opt/vc/bin/raspimjpeg with the new compiled version. The source is in the repo itself in "host_applications/linux/apps/raspicam/". At the moment there are 4 relevant files:

RaspiMJPEG.h
RaspiMJPEG.c
RaspiMUtils.c
RaspiMCmds.c
RaspiMCam.c

Silvan

[silvanmelchior]

Hello

I updated raspimjpeg:

- Now everytime a video capture is stopped, the circular buffer is reset. This prevents wrong video results if there is a delay between two videos that is smaller than the size of the buffer.
- Bugfix

[silvanmelchior]

Hi silvanmelchior
Buffer only works if Video_fps = 25 ?
if i set the Video_fps to 10 it crashes.
After reboot

Code: Select all

pi@raspberrypi ~/RPi_Cam_Web_Interface $ ./RPi_Cam_Web_Interface_Installer.sh start
Started
pi@raspberrypi ~/RPi_Cam_Web_Interface $ mmal: mmal_vc_component_enable: failed to enable component: ENOSPC

Thanks, this should be fixed in the new version

[silvanmelchior]

This is really a nice addition! Good to have you back and glad to see you will be working on this together.
Since the movements were short in on my cam it always captured a bit to late. Now the video is actually showing the full movement.

What I did notice while reviewing the timestamps in motion started video is something like this :

Suppose a video started motion triggered with timestamp 16:30:01

16:30:01 good video
16:30:02 good video
16:30:00 blurry/still video
16:30:01 blurry/still video
16:30:02 blurry/still video
16:30:03 good video
16:30:04 good video
16:30:05 good video

It jumps back some seconds and shows blurry video those couple of seconds, after that video looks good again.
Any idea what that could be and how to fix it ? I could send you an example video if you would like to check it out.

I made some bugfixes. Could you check wheter the error is still there? And if so, could you describe me an exact scenario where the bug occurs, so that I can reproduce and try to fix the problem?

Thanks