-
Notifications
You must be signed in to change notification settings - Fork 2
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
Individual stripes in motion videos and motiongrams #20
Comments
I am running the analysis on both OSX and Windows next to each other here, on the same file, and this line can only be seen on OSX. Strange! |
So this line in the motion videos, motiongram and video preview window is only an issue on OSX? |
Yes, as far as I can tell. |
It is really strange that it happens randomly throughout the video and not at the start or the end. Hmm, hmm, will test this. |
Yes, I tested exporting all with 7 different videos and this line/color-artifact is only present on the "dance.mp4" video in the test_videos folder. This seems to be consistent, at least on my OS 10.13.6. I also tried with other .mp4 videos with h264 and AAC codecs but was unable to recreate the same artifacts.. Wierd. |
If we cannot reproduce it with any other videos, I don't think it is worth spending a lot of time on it. Strange, though. This dance video has been my standard test video since 2005... |
Indeed. But let's keep this issue open a little longer in case we experience it, or related bugging, while doing more tests |
Oi! That looks very mysterious... it looks like as if there were a lot of dropped frames during the render, but I don't exactly see how that could be possible with the framedump method.. |
I suspect my early-2011 macbook computing power and low battery.. But need to test some more to be sure. |
But that should only be a factor if the framedumping is happening in the scheduler thread, but it is not. Hmm, hmm... |
So found out that the culprit here is most likely the CPU load of running through high res videos. When exporting (or viewing a demanding movie in real-time), there seems to be something that the MacOS is doing which results in a great deal of lagging frames to compensate for something.. Therefore, we get these glitches because the patch is designed to do just this(!) when the same frame is pushed through over a longer period of time then expected. And also, this is a new problem! This was fairly fine until very recently so maybe were pushing the programs capabilities to the max (pun intended), at least for my 2 older macs for 2011. It seems to work fine on Balints windows machine. And also, it seems to work just fine on not too demanding videos. I guess this just speaks to the need for issue #13 in a future installment of the app. There might be other things we can do to make it more resource-friendly. What do you guys think about this, @balintlaczko and @alexarje ? On the other hand, there might other reasons. I will at least continue to look for this some more. |
Aah, I think I spoke too soon last night and was a little pessimistic. Im on to something now. Will update momentarily. |
I still see the stripes on OSX (10.11), but only in the dance example video. Haven't been able to see it in others. Can keep this thread open, and see if we can reproduce on other systems and with other files. |
Yes, absolutely. Let's keep this open. |
There are some occasional stripes in the exported motion video images. It may be related to #18.
This also shows up as stripes in the motiongrams.
Strange. Will test some more.
The text was updated successfully, but these errors were encountered: