onbase and large audio and video files

[Thomas_Reu]

Does anyone have any experience with how OnBase handles really large audio or video files?  We have some clients thinking about meeting minutes that could be 2-2.5 hrs of audio and other clients thinking about video over the same time frame (basically a full length movie).  I'm sure we are talking about 5-10GB or more for 1 file.

[Kevin_Ledgiste1]

Just for clarification, the video and camera devices that are capturing information are all compressed. None of it is uncompressed video and very unlikely are photos as well. A JPEG by definition is compressed, as is a Windows Media or MPEG video file. A true RAW, uncompressed video at 8 bits and 30 frames per second would be in the terabytes for an hour of video.

The real question is chain of custody. It's the same process the courts had to go through to accept a scanned document when the original is no longer available. How does the court know that a scanned document was unaltered from the original? How does the court know that a video file is unaltered if it is no longer residing in the source? 

Time coding should be stamped on the original video or you need a process that can compress the video and maintain the original time codes and operational metadata properties of the video. These are things that can help to forensically identify that a video is a true representation of the original. However, in these matters, it is always best to consult with the jurisdictional courts for an opinion or ruling before altering video files.

[Ciaran_Coulter]

The storage of media files is one part of a larger scope of media management. Other aspects include how media files are accessed, retrieved, consumed, and management and application needs around those.

 If there are specific scenarios or business uses that involve media retrieval and management, we would be interested in connecting on those to understand further. As mentioned in a previous post, the typical scenario may involve the ability to stream live or archived media.

 A contact via email to ciaran.coulter@onbase.com and\or scott.anderson@onbase.com for this purpose would work.

 Thanks

[Joe_Pineda]

Hi:

So for OB14, what is the latest info on this thread: large file support-number of docs in db?

1. Is there still a limitation on the I/O method to a limit of 2GB?

2. Does the DB support file size greater than 2 GB (BIGINT) for the column discussed above?  If so, is this "out-of-the-box", or a customization?

I just re-read Ansley's post about the size limitation in the db being removed.

3. What's the latest on SCR 166753?

4. How many documents can the db in OB 14 store? I saw Ansley's post, but is there a more precise number than "more than 2.14 billion?"

[AdamShaneHyland]

Hi Jose,

To answer your questions, as of OnBase 14, there is still the 2 GB limit for files stored in the OnBase Disk Groups.  There are active development projects in place to be able to support larger file size, but it hasn't been implemented and there is no ETA on when this will be completed. SCR: #166753 falls in line with the active development projects with no ETA on completion dates.

As for 64-bit integers (ie BIGINT), this is available in OnBase 13 and higher versions of the software.  Any new installation of OnBase 13 or higher would inherently support 64-bit integers.  Current installations do not out of the box support 64-bit integers simply by using the new version of the software.  This would require an engagement with Hyland Software to update the database.  A database configured for 64-bit integers can store 1 quadrillion documents in the system.

Take care,

[Joe_Pineda]

Thanks Adam. Exacty what I was looking for.