Search found 5 matches
- Sun Feb 28, 2010 6:40 pm
- Forum: Other Discussions
- Topic: Accurate editing AVCHD/MPEG without re-encoding
- Replies: 5
- Views: 27807
Re: Accurate editing AVCHD/MPEG without re-encoding
Thanks for your reply. If the GOPs are variable length and may be long there is an even greater need to know where they are. Jump to keyframe is a common function in many video tools, such as Virtualdub and Avidemux. The latter indicates the frame type when looking at a standard DVD MPEG-2 file whic...
- Fri Feb 26, 2010 10:53 am
- Forum: Other Discussions
- Topic: Accurate editing AVCHD/MPEG without re-encoding
- Replies: 5
- Views: 27807
Re: Accurate editing AVCHD/MPEG without re-encoding
Is there a way to see where the keyframes are and to move to the next keyframe? If not, then these functions would be a big improvement. Key frames could be indicated by placing a colored frame around the frame thumbnail, and the should be a forward and backward "jump to keyframe" button a...
- Thu Feb 25, 2010 7:48 am
- Forum: Smart products - support
- Topic: Bad Pool Caller
- Replies: 16
- Views: 10198
Re: Bad Pool Caller
More info: I tried to cut and join pieces from a VOB file and the same error occurred. So, the problem is probably not related to the M2TS files. Parameter 1 of 0x07 indicates that "The current thread attempted to free pool which was already freed" (see http://www.osronline.com/ddkx/ddtool...
- Wed Feb 24, 2010 7:09 am
- Forum: Smart products - support
- Topic: Bad Pool Caller
- Replies: 16
- Views: 10198
Re: Bad Pool Caller
This happens during Record List. My processor is an Intel Core Duo T8100.
The second file can be obtained at http://www.sendspace.com/file/cr48oe.
I will e-mail the first file.
The second file can be obtained at http://www.sendspace.com/file/cr48oe.
I will e-mail the first file.
- Tue Feb 23, 2010 8:56 pm
- Forum: Smart products - support
- Topic: Bad Pool Caller
- Replies: 16
- Views: 10198
Re: Bad Pool Caller
I get the same error when trying to join two M2TS files: A Windows crash with the blue screen displaying bad_pool_caller, STOP: 0x000000C2 (0x00000007, 0x00000CD4, 0xE359D008). I am using Windows XP Pro on a Lenovo Thinkpad R61 laptop. This is a really bad error as it requires power off and restart....