![]() It didn't work on 6D till I did it that way. Gop is probably going to have to be done from video parameters property. Once you have decent settings its usually good to go on startup at least from my experience with 6D. I may have to patch a few more errors for 5D3 too, thought I got all the asserts. Go in and out of the menu and check that loaded says yes. Give it a second to load up at startup, don't hit record right away. There is also probably a better way to handle all of this. An in camera text editor would take care of it too. I'm a bit of a shitty coder but there may be a way to change the parameters on the fly. Using the below ini, push record, LV and ML overlays all keep working fine, you can't stop recording, nothing it written to card and ML says error writing, restart, and restarts. Here is a small file with GOP 3 to check. Tried changing the GOP, mediainfo reports standard GOP, but I don't really trust it, and I can't think of any other way I have to check. Same crash logs as before, not sure if the log000 are the same. Restart camera still in override mode and crash on record, remove battery and try again err 70. Using vbr config, switch to override, load config and all works good. Using vbr config and switching to override mode without loading the config again, crash. All timecodes will be adjusted by 00:00:00.125 so that none is negative anymore.īitrate viewer still complained trying to open the file and I have no access to streameye :-( Code: Warning: 'O:\DCIM\100EOS5D\D46A6713.MOV': This file contains at least one frame with a negative timecode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |