MovieMator Video Editor

MovieMator Video Editor

Kaito May 11, 2019 @ 11:50pm
Black Screen after exporting
when I installed it, I could enable 60 fps in any profile/preset (HDTV, Youtube, 4k, etc) even modifying the resolution without any problem.

I have used the program again after several days and no matter what profile/preset I use, when I change to 60 fps the video will be completely black after exporting the mp4 video.

Any ideas? I would also like to know how to return to the default configuration.

Thanks in advance.
< >
Showing 1-15 of 19 comments
radio_babylon May 14, 2019 @ 2:39pm 
i also reported this bug last week, and have been working with their support team to create a reproducible test-case. they have identified the issue and are working on fixing it... so, hopefully, soon...
76561198870672195 May 16, 2019 @ 3:54am 
Thank you for your feedback. We are working on the problem now.
Kaito May 21, 2019 @ 7:48pm 
Thanks for answering both.

When will it be ready?
76561198870672195 May 23, 2019 @ 2:06am 
Originally posted by Beker:
Thanks for answering both.

When will it be ready?
I will let you know once we have a beta version with that problem fixed.
The Crazy Gringo Jun 3, 2019 @ 3:27pm 
I'm also getting this bug and only bought the software today.
The video goes black about half way through the rendered video using the standard h.264 codec. Nothing fancy.
Please fix this or I'll have to ask for a refund.
76561198870672195 Jun 5, 2019 @ 11:53pm 
Originally posted by The Crazy ♥♥♥♥♥♥:
I'm also getting this bug and only bought the software today.
The video goes black about half way through the rendered video using the standard h.264 codec. Nothing fancy.
Please fix this or I'll have to ask for a refund.
Sorry about that. Did you also change the default frame rate before rendering?
The Crazy Gringo Jun 6, 2019 @ 5:13am 
Too late. I returned the software and was refunded.
76561198870672195 Jun 10, 2019 @ 3:27am 
Originally posted by The Crazy ♥♥♥♥♥♥:
Too late. I returned the software and was refunded.
Sorry about that. Thank you for your time.
radio_babylon Jun 16, 2019 @ 11:50am 
just received an update. this issue is STILL NOT FIXED.

im about to petition for a refund even though ive had it over the refund period because seriously, this is ridiculous. this is not a minor bug, its a serious issue that makes it effectively impossible to export anything unless youre willing to stick with 24fps...
cacaongu23 Jun 24, 2019 @ 3:55am 
yeah it still have the above prblem
76561198870672195 Jun 27, 2019 @ 1:45am 
Originally posted by radio_babylon:
just received an update. this issue is STILL NOT FIXED.

im about to petition for a refund even though ive had it over the refund period because seriously, this is ridiculous. this is not a minor bug, its a serious issue that makes it effectively impossible to export anything unless youre willing to stick with 24fps...
Hi, I'm sorry to hear that. Could you please send your project and the source files to us for testing? We are unable to locate the problem now. Did you change the video mode? Please drop us an email at support@effectmatrix.com. We'll fix the problem very soon.
radio_babylon Jun 27, 2019 @ 11:53am 
are you kidding me??

i can re-send you the exact same project and source files i sent you 6 weeks ago, because they STILL reproduce the problem. you guys have no excuse for this bug continuing to be unfixed at this point.
radio_babylon Jun 27, 2019 @ 12:46pm 
just so you guys cant try to make the excuse that you dont have a working, well-documented test case, and so anyone else can reproduce the test case if they want, i am reposting here the test case that was delivered to you May 5 2019, and confirmed as a valid test case by you on May 8 2019.

the files for reproducing the test case can be found at: https://www.dropbox.com/sh/umnfq7577iavozj/AAD38sCaD3TX3tZoa0uJhC_Ra?dl=0

to reproduce the sample output files exhibiting the problem follow these steps:

1) edit the xml in the last-9-seconds-slice.mmp to change the <property name="resource"></property> to reflect the path to the local source file for the test case.

2) open moviemator and load the mmp file

3) export the video with the following settings to reproduce the 3 individual test cases:

3a) video profile "HDTV 1080P" - default settings (24fps) - video exports as expected

3b) video profile "HDTV 1080P" - change frames/sec to 30 - exports with black frames beginning at 1.2 seconds and continuing until the end of export

3c) video profile "HDTV 1080P" - change frames/sec to 60 - exports with black frames through the entirety of the export video

Test Case Analysis:

the input video is 39 seconds long. the slice selected for export is the final 9 seconds of the video.

at 24 frames per second, the slice exports normally.

at 30 frames per second, the black frames begin at 1.2 seconds of the slice. this corresponds to the 31.2 second mark of the input source. 24 frames per second is 80% of 30 frames per second, and 31.2 seconds is EXACTLY 80% of 39 seconds.

at 60 frames per second, the entire export is comprised of black frames.

24 fps is 40% of 60 fps. if the entire input source (and not just the 9 second slice) is exported at 60 fps, the black frames begin at 15.6 seconds... which is, also, EXACTLY 40% of the length of the full input source.

clearly, the exporter is INCORRECTLY linking the output frames per second to the times on the input source, and once it hits what it THINKS is the end of source, it renders only black frames for the remainder of the output.

-------------

i sincerely doubt you are ever, ever going to get a better documented, more consistently repeatable test case than this. you have NO EXCUSE for not getting your devs on this test case, isolating the root cause, and fixing it.

i am an application developer myself, and manage a team of devs... getting a repeatable test case like this for a bug is like a wet dream because usually the biggest obstacle to fixing a bug is being able to reliably reproduce it. THIS occurs *every single time* and if i were to have handed my team this test case 6 weeks ago and they still didnt have a fix by now, somebody would be getting their ass fired for it, because this is about as much of a softball bug fix as a dev can ever get.
Last edited by radio_babylon; Jun 27, 2019 @ 12:53pm
76561198870672195 Jul 3, 2019 @ 11:33pm 
Originally posted by radio_babylon:
just so you guys cant try to make the excuse that you dont have a working, well-documented test case, and so anyone else can reproduce the test case if they want, i am reposting here the test case that was delivered to you May 5 2019, and confirmed as a valid test case by you on May 8 2019.

the files for reproducing the test case can be found at: {LINK REMOVED}

to reproduce the sample output files exhibiting the problem follow these steps:

1) edit the xml in the last-9-seconds-slice.mmp to change the <property name="resource"></property> to reflect the path to the local source file for the test case.

2) open moviemator and load the mmp file

3) export the video with the following settings to reproduce the 3 individual test cases:

3a) video profile "HDTV 1080P" - default settings (24fps) - video exports as expected

3b) video profile "HDTV 1080P" - change frames/sec to 30 - exports with black frames beginning at 1.2 seconds and continuing until the end of export

3c) video profile "HDTV 1080P" - change frames/sec to 60 - exports with black frames through the entirety of the export video

Test Case Analysis:

the input video is 39 seconds long. the slice selected for export is the final 9 seconds of the video.

at 24 frames per second, the slice exports normally.

at 30 frames per second, the black frames begin at 1.2 seconds of the slice. this corresponds to the 31.2 second mark of the input source. 24 frames per second is 80% of 30 frames per second, and 31.2 seconds is EXACTLY 80% of 39 seconds.

at 60 frames per second, the entire export is comprised of black frames.

24 fps is 40% of 60 fps. if the entire input source (and not just the 9 second slice) is exported at 60 fps, the black frames begin at 15.6 seconds... which is, also, EXACTLY 40% of the length of the full input source.

clearly, the exporter is INCORRECTLY linking the output frames per second to the times on the input source, and once it hits what it THINKS is the end of source, it renders only black frames for the remainder of the output.

-------------

i sincerely doubt you are ever, ever going to get a better documented, more consistently repeatable test case than this. you have NO EXCUSE for not getting your devs on this test case, isolating the root cause, and fixing it.

i am an application developer myself, and manage a team of devs... getting a repeatable test case like this for a bug is like a wet dream because usually the biggest obstacle to fixing a bug is being able to reliably reproduce it. THIS occurs *every single time* and if i were to have handed my team this test case 6 weeks ago and they still didnt have a fix by now, somebody would be getting their ass fired for it, because this is about as much of a softball bug fix as a dev can ever get.
Sorry for my late response. I had a few tests again and didn't find any problem with the exported video. The problem is that the Video Mode is set wrongly. Please customize a Video Mode as 1080P HD 60fps, then load your video and trim it, then export it as 30fps and 60fps. There will be no problem with the videos, no black screen.
Sorry again.
radio_babylon Jul 3, 2019 @ 11:42pm 
i have no idea what you are talking about. but if you dont think its a bug that when you change the fps in a profile to 30 or 60, and it wont export correctly... then you and i have different definitions of what constitutes a 'bug'
< >
Showing 1-15 of 19 comments
Per page: 1530 50