You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Video library not working when exporting the application (Windows) #172
I am using the Video library, update 2.0, and whenever I open the application that I exported, the program just freezes. Tested it with multiple different videos, but none of them work.
Code that I tested with.
importprocessing.video.*;
MoviemyMovie;
voidsetup() {
size(1360, 768);
myMovie = newMovie(this, "test.mp4");
myMovie.loop();
}
voiddraw() {
tint(255, 20);
image(myMovie, 0, 0);
}
// Called every time a new frame is available to readvoidmovieEvent(Moviem) {
m.read();
}
changed the title [-]Video library not working when exporting the application[/-][+]Video library not working when exporting the application (Windows)[/+]on Jan 17, 2021
we are now at.. "2.0-beta5" this one use GStreamer (1.16.2)
not sure how this works, but as far as I checked, my local gstreamer lib was different than the one that processing wanted to use.
Then that error about "loading the library".
Activity
oldguan commentedon Dec 29, 2020
I got the same issue when run application and catch this exception
Microsoft Visual C++ Runtime Library
Runtime Error!
Program: E:\proces...
R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.
lynch-if commentedon Jan 16, 2021
got the same problem
[-]Video library not working when exporting the application[/-][+]Video library not working when exporting the application (Windows)[/+]lynch-if commentedon Jan 21, 2021
it work when use the video library-2.0-beta1, @benfry
carlesgutierrez commentedon Apr 7, 2021
Good to know! Thanks This one works
we are now at.. "2.0-beta5" this one use GStreamer (1.16.2)
not sure how this works, but as far as I checked, my local gstreamer lib was different than the one that processing wanted to use.
Then that error about "loading the library".
"library-2.0-beta1" is more open mind. ^^
SeongJongKwak commentedon Apr 17, 2023
@carlesgutierrez / @lynch-if / @oldguan / @LukasGadeMEA20
By any chance, has that bug been fixed?
By any chance, has it been resolved?