Click here to Skip to main content
15,917,610 members

Comments by onemorecoke (Top 14 by date)

onemorecoke 31-Aug-13 16:46pm View    
That is perfect! Thank you RedDK. Please put it in the solutions and I will accept.
onemorecoke 26-Aug-13 10:45am View    
The information you gave is more evidence that the timestamps in the original video are set at 5 seconds and the fast ffmpeg method will only be able to break at those positions. The only solution to use the faster ffmpeg command is to have more frequent timestamps in your source video. If you are not able to do that then you will only be able to use the second slower method.
onemorecoke 23-Aug-13 12:36pm View    
You can use the command ffmpeg -i "input.mp4" to get info on the file. It will show the timestamp rate. I am not sure where you are getting your source video, but when the video is rendered from editing you should be able to set the timestamp frequency, which is usually a timestamp per X amount of frames. I would get a new file with a timestamp every 1 second and see if the accuracy of your cropping with that first ffmpeg instruction you specified. Good luck!
onemorecoke 23-Aug-13 12:30pm View    
Ron, have you ever dealt with exposing the response, request, and session objects from classic ASP in the VB.NET environment? I tried using the ASP type library and the COM+ component which work in some ways but seemed like a duct-tape solution. I may have to abandon having those three objects available in the .NET environment, which I am thinking might be the case, and that I would just pass the webpage elements I need in the function calls to the new DLL. It would be more work but it might be what I need to avoid completely rewiring the classic ASP webpages right now.
onemorecoke 23-Aug-13 12:23pm View    
Thanks Ron, good stuff. I was able to convert the VB6 functions to vb.net 2012 at one point, and then make the DLL COM visible. There were two issues though: The problems I ran into was getting at the RESPONSE, REQUEST, and SESSION objects as I did in the VB6 ActiveX DLL. Though it did work it failed sometimes so I was thinking I was trying to use OLD technology in a new environment. The other was that I was not certain if the COM visible vb.net DLL was actually working in 64 bit mode. So at the time I abandoned it but now I have to deal with it hard so that is why I was asking if someone had a good path.