These files handle the actions to take and notices to display when limits are reached:
...TIZEN\project\NX2000\packages\webkit-efl\Source\WebCore\platform\graphics\efl\CameraManagerPrivateMMFW.cpp
...TIZEN\project\NX2000\imagedev\usr\include\mmf\SLP_MultimediaFW_PG.h
Includes sample code.
Applicable variables contained within these files:
MM_MESSAGE_CAMCORDER_TIME_LIMIT
Time limit (Second) of recording file. If the elapsed time of recording reaches this value, camcorder will send 'MM_MESSAGE_CAMCORDER_TIME_LIMIT' message.
MM_MESSAGE_CAMCORDER_MAX_SIZE
Maximum size (Kbyte) of recording file. If the size of file reaches this value, camcorder will send 'MM_MESSAGE_CAMCORDER_MAX_SIZE' message.
----------------------------------------------------------------
This file set the limits:
...TIZEN\project\NX2000\imagedev\usr\include\mmf\mm_camcorder.h
#define MMCAM_TARGET_TIME_LIMIT "target-time-limit"
Time limit (seconds) of recording file. If the elapsed time of recording reaches this value, camcorder will send 'MM_MESSAGE_CAMCORDER_TIME_LIMIT' message.
#define MMCAM_TARGET_MAX_SIZE "target-max-size"
Maximum size(Kbytes) of recording file. If the size of file reaches this value, camcorder will send 'MM_MESSAGE_CAMCORDER_MAX_SIZE' message.
Note that these limits are defined by yet another set of variables "target-time-limit" and "target-max-size". These are likely the final variables which ultimately determine the limits.
----------------------------------------------------------------
...TIZEN\project\NX2000\packages\webkit-efl\Source\WebCore\platform\graphics\efl\CameraManagerPrivateMMFW.cpp
Contains a function called "setCameraVideoCaptureAttr(capturePath,maxTimeInSeconds)" which initializes the running attributes of camcorder video. Within this function, the variable MMCAM_TARGET_TIME_LIMIT is initialized by the variable maxTimeInSeconds, which is the second (and last) parameter passed to the "setCameraVideoCaptureAttr" function when called. When calling the function, the time limit will likely either be a variable or the number of seconds as an integer passed to that second parameter.
----------------------------------------------------------------
So now I'm left with the limits being set with "target-time-limit" and "target-max-size", as well as the function setCameraVideoCaptureAttr(capturePath,maxTimeInSeconds), so the next step is to locate where there are being initialized...
----------------------------------------------------------------
The following files contain the variables "target-time-limit" and "target-max-size":
...TIZEN\project\NX2000\imagedev\usr\lib\libewebkit.so.0.12.23
Contained within 5th parameter of function "mm_camcorder_capture_start", but this function is for still image capture and multishot, not for camcorder video, so not at all concerned with this function.
Unable to easily determine association within following files, may not be directly affected:
...TIZEN\project\NX2000\image\rootfs\usr\bin\di-camera-app-nx2000
...TIZEN\project\NX2000\imagedev\usr\lib\libmmfcamcorder.so.0.0.0
...TIZEN\project\NX2000\image\rootfs\usr\lib\libmmfcamcorder.so.0.0.0
...TIZEN\project\NX2000\imagedev\usr\bin\mm_camcorder_testsuite
...TIZEN\project\NX2000\image\rootfs\usr\bin\mm_camcorder_testsuite
Result: I'm unable to easily determine where "target-time-limit" and "target-max-size" are ultimately initiated.
----------------------------------------------------------------
The following files contain the function "setCameraVideoCaptureAttr":
...TIZEN\project\NX2000\packages\webkit-efl\Source\WebCore\platform\graphics\efl\CameraManagerPrivateMMFW.h
Defines function "setCameraVideoCaptureAttr".
...TIZEN\project\NX2000\packages\webkit-efl\Source\WebCore\platform\graphics\efl\CameraManagerPrivateMMFW.cpp
Passes "maxTimeInSeconds" to function "setCameraVideoCaptureAttr".
Function "startVideoCapture" calls function "setCameraVideoCaptureAttr" with time limit of 180 (3 Minutes), not sure why 3 minutes here.
Unable to easily determine association within following files, may not be directly affected:
...TIZEN\project\NX2000\imagedev\usr\lib\libewebkit.so.0.12.23
Result: I'm unable to determine where "maxTimeInSeconds" is ultimately initiated.
----------------------------------------------------------------
Other methods of locating where limits are ultimately the time limit is initialized is by searching for time in seconds. For instance, a 30 minute limit would be 1800, but possibly set at 1799. At 1080p30, the time limit is 20 minutes, which is 1200, or possibly 1199. Same deduction method could be used for known file size limits. I was unable to locate time limits by instances of 1799 and 1199, and there are too many instance of 1800 and 1200 for me to dig through.
I've given up on my initial search for where the limits are ultimately initialized.
Some possible alternative solutions:
...TIZEN\project\NX2000\imagedev\usr\include\mmf\mm_camcorder.h
Change Line 1029 from:
#define MMCAM_TARGET_TIME_LIMIT "target-time-limit"
To:
#define MMCAM_TARGET_TIME_LIMIT 86400
...TIZEN\project\NX2000\packages\webkit-efl\Source\WebCore\platform\graphics\efl\CameraManagerPrivateMMFW.cpp
Change Line 703 from:
MMCAM_TARGET_TIME_LIMIT, maxTimeInSeconds,
To:
MMCAM_TARGET_TIME_LIMIT, 86400,
Still I'd prefer to find find out where the limit variables are ultimately initialized rather than changing the functions. I also don't really have the time to learn the compilation process on my own. At least this is a start for others who want to give it a shot.
