Skip to content
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

Support change of resolution during grabbing. Usecase: UDP streaming … #769

Merged
merged 12 commits into from
Sep 15, 2017
Merged

Support change of resolution during grabbing. Usecase: UDP streaming … #769

merged 12 commits into from
Sep 15, 2017

Conversation

mifritscher
Copy link
Contributor

…with changing sources / qualities.

Test included.

Signed-off-by: Michael Fritscher michael.fritscher@telematik-zentrum.de

Michael Fritscher added 7 commits August 23, 2017 09:46
…with changing sources / qualities.

Test included.

Signed-off-by: Michael Fritscher <michael.fritscher@telematik-zentrum.de>
Signed-off-by: Michael Fritscher <michael.fritscher@telematik-zentrum.de>
Signed-off-by: Michael Fritscher <michael.fritscher@telematik-zentrum.de>
…with changing sources / qualities.

Test included.

Signed-off-by: Michael Fritscher <michael.fritscher@telematik-zentrum.de>
…with changing sources / qualities.

Test included.

Signed-off-by: Michael Fritscher <michael.fritscher@telematik-zentrum.de>
…avacv into dynamic_resolution

# Conflicts:
#	platform/src/test/java/org/bytedeco/javacv/FrameGrabberTestChangingResolution.java
@saudet
Copy link
Member

saudet commented Sep 3, 2017

Looks good, but for some reason, your tests are not getting run by Maven. Could you check out why this is the case? The same is happening with pull #770. Thanks!

@mifritscher
Copy link
Contributor Author

I think this is because I didn't registered them. I'll need to search the relevant file first ;-)

@saudet
Copy link
Member

saudet commented Sep 3, 2017 via email

@saudet
Copy link
Member

saudet commented Sep 9, 2017

Looks like we have an answer here:
https://stackoverflow.com/a/6178629
Any reason to not just put them in FrameGrabberTest?

@mifritscher
Copy link
Contributor Author

Aaaahhhhh - naming conventions :-) Thanks for this hint!

I can put the test into the already existing FrameGrabberTest file, no problem. I only thought that you prefer to put it into an extra file ;-)

@saudet
Copy link
Member

saudet commented Sep 10, 2017

Yes, FrameGrabberTest is fine, as long as they pass :)

Michael Fritscher added 4 commits September 14, 2017 09:33
# Conflicts:
#	src/main/java/org/bytedeco/javacv/FFmpegFrameGrabber.java
#	src/main/java/org/bytedeco/javacv/FFmpegFrameRecorder.java
…with changing sources / qualities.

Test included.

Signed-off-by: Michael Fritscher <michael.fritscher@telematik-zentrum.de>
Signed-off-by: Michael Fritscher <michael.fritscher@telematik-zentrum.de>
@mifritscher
Copy link
Contributor Author

Ok, seems to work now :-) I had to leave the test in an extra file - I have the feeling that else FrameGrabberTest would be overhelmed by this test (3 helper functions, 2 threads, 3 global variables)

@saudet
Copy link
Member

saudet commented Sep 14, 2017

Sure, that's fine, thanks! We just need to remove FFmpegFrameLock.java now :)

@saudet saudet merged commit 487c0a5 into bytedeco:master Sep 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants