But anyway, can you try to fix the bad part from video B and let me see just that couple of seconds of thanks for sharing the codes which I believe "scripts"? can you please give me a sample result of just a few I used to try mix 2 videos together like you said but it didn't turn out good as I don't know how to fix it first, could you please try if you got time or suggest anyone else who seems to play with these a lot so I could ask for help?
add some "light" to make it easier to look at. This is why I'm having the impossible dream as you said because I just simply think we can "smooth" out the pixels to make the whole frame looks "cleaner" and then. If you resize the window while playing it, it looks quite similar to video A except less "noise" and brighter. Also, if anyone has any more insight into the Clarion DB structure (important files, easy ways to determine linked fields from table to table, etc.Hi all, thank you for all your replies and discussions, now I know there's a thing called "frame interpolation" as manono it is my fault not to mention that the original B video was taken from a VCD too as I asked the uploader, what different are the video is retouched some time long ago by someone and it was "upscaled" to 720p. Thanks again to everyone, this has got me started, which was the first big hurdle. I believe this to be an error due to the size of the field or type of data. I tried importing from dBase III, but got the same results.
When I bring this field into Excel, it looks fine, but when I import to Access from Excel, it looks like this - 1.5010960E+11. Any suggestions?Ģ) One of the pieces of data is a float in the dBase III files. So I added columns in the Excel for these fields, but really feel unsure about whether they should be there at all. What this highlighted is that some fields which were in the *.dat files apparently were blank and therefore were not transferred to the dBase III files. I could then import into Access with no field name issues. in the conversion, the field names were changed to first three letters of the table name and then some characters from the field name not all, some) - I corrected this by viewing the *.dat files field names then converting the dBase III files to Excel and editing the field names there. ġ) the field names came over a bit scrambled (i.e. I found another program CCVT.exe that allowed me to convert the Clarion *.dat files to dBase III files, which could be viewed in Excel or imported into Access. Since the application is a shareware item, I was able to only view/export 100 files. OK, I tried the viewer that was suggested by OlafDoshke and was able to open the files.
0 kommentar(er)
