2006-08-21, 09:03 PM
I've corrected the issue for the next release. It's now able to use a couple of other techniques to determine the FPS.
The new approach works fine with the sample files you supplied.
The new approach works fine with the sample files you supplied.
Quote:There is however a bit more. I had the UNC path defined as //server/... this gave 30 fps. I now redefined it as \\server\... (the way it should be) and get first 0 and the second time 25 fps (I have reported this before). However when viewing the file from the recordings screen it says the file does not exist after transcoding when using the correct UNC path (I set to not autodelete in the config.xml since when the router reboots GBPVR was clearing the full database).The //server/... format is invalid, so probably resulted in the mediadet not being able to open the file. \\server\... is the correct format for a UNC path format. 30 fps was the default if it wasnt able to open the file.
Quote:Further when I map the network path to a windows driveletter the recording service does not record anything (which is maybe normal).Yeah, this is normal. The recording service runs under a different user account, so isnt able to see your drive mappings.
