Also, if someone provides you a sample file, it'll no longer be 'growing', right? You would need to start the ingest/capture to a file on a volume PPro can see, then import the file in PPro. You'll see the duration update, in the source monitor, every N seconds (you can change N in Preferences-->Media).
I'm currently evaluating Premiere Pro 6.0.3 on Windows 7 and am having difficulty importing a growing RDD9 file. I get the same "The importer reported a generic error" error message as reported by Aleksandra.
The import succeeds when the RDD9 file is complete.
When writing a growing file on Linux and exporting the directory to Windows 7 using CIFS the import succeeds and I see the duration incrementing!
However, when writing the file on the Windows 7 client I see several SHARING VIOLATIONS in the Process Monitor system tool when Premiere Pro tries to open the growing file. I think the issue is that it wants ShareMode=Read whilst the growing file was opened with Generic Read, Generic Write.
Does the growing file need to be opened in a special way?
Does growing files support maybe require an .xmp file?
I think the issue is that it wants ShareMode=Read whilst the growing file was opened with Generic Read, Generic Write.
You are correct! If the file has been opened with SHARED_WRITE on the local system, PPro will refuse to open it. No XMP required.
Still no luck I'm afraid.
I've tried every combination of desired access (GENERIC_READ, GENERIC_WRITE) and share mode (FILE_SHARE_READ, FILE_SHARE_WRITE and FILE_SHARE_DELETE) and none of them work. I either get a "This file is in use" error message when only using FILE_SHARE_WRITE (which is expected), and otherwise I get the "...generic error" error message.
The C call I use to open the file is this one (changing the 2nd and 3rd parameters):
CreateFile(filename, GENERIC_WRITE | GENERIC_READ, FILE_SHARE_READ, NULL, CREATE_ALWAYS, FILE_ATTRIBUTE_NORMAL, NULL);
My guess is that Premiere is trying to lock the file by opening a file handle with ShareMode=Read, and this share mode conflicts with the GENERIC_WRITE access of the existing file writing handle. I need GENERIC_WRITE to write to the file. The result is a SHARING_VIOLATION error.
It works through a CIFS share because Linux doesn't have file share modes and the requests are simply ignored.
If you have any suggestions then that would be greatly appreciated.
First suggestion: Use the CIFS share through Linux, which works.
What file system is in use, on the storage? Please send me (directly: email@example.com) details of your entire setup, and I'll see whether we can make some more useful recommendations.