File Specifications Sample Clauses

The File Specifications clause defines the technical and formatting requirements for files to be delivered or exchanged under an agreement. It typically outlines details such as acceptable file types, naming conventions, resolution, or compatibility standards that must be met. By clearly setting these parameters, the clause ensures that all parties provide files in a consistent and usable format, reducing the risk of errors, incompatibility, or delays due to improper file submissions.
File Specifications. Customer shall deliver an ACH file in the NACHA Standard format as specified in the NACHA manual ACH Rules. Said format may be derived from using software provided by the Bank.
View SourceView Similar (10)
File Specifications. The Customer may elect to transmit an ACH File directly to Bank. In such case, the Customer shall provide Bank with computer readable information and with an ACH file consistent with current NACHA file specifications. The file shall be delivered to Bank in accordance with an agreed upon processing schedule as defined in this Appendix II or use the Republic Treasury Direct software file specifications.
View Source
File Specifications. Format Container Video Audio HD 1920x1080 1280x720 MPEG-2 Transport Stream MPEG-2 Mbps, i-frame only 80 AES3 LPCM; PCM; MPEG Layer 1,2, One track – multi channel QuickTime MOV (iTunes package format) ProRes 422 HQ (~220 Mbps) LPCM, iTunes channel configuration SD 720x480/48 6 720x576 MPEG-2 Transport Stream MPEG-2 Mbps, i-frame only 50 AES3 LPCM; PCM; MPEG Layer 1,2, One track – multi channel QuickTime MOV (iTunes package format) ProRes 422 HQ (~50 Mbps) LPCM, iTunes channel configuration 3D 3840x1080 2560x720 Full-Res, Side by Side MPEG Stream Transport H.264/AVC 100 Mbps i-frame only AES3 LPCM; PCM; MPEG Layer 1,2, One track – multi channel • Match the original frame rate and aspect ratio of program as it was originally shot. • Contain a minimum of 1 frame and a maximum of 1 second of black at head and tail of the program. • If Source Material has commercial blacks, each commercial black segment must be trimmed down to 2 seconds or less before delivery. • Contain the non-subtitled version. Netflix defines “non-subtitled” as the presence of main titles, end credits, narrative text, location call-outs, and other supportive/creative text, but the absence of burned-in subtitled dialogue, regardless of the language in the primary video. • Have audio and video muxed into one file. • Have audio conform (sync) to video within the MPEG-TS or MOV container. • Have audio and video duration match within 1 second. Bars and Tone VITC (vit-see) Time Code Advertisements Production Slates Ratings Cards FBI Warning Cards Placards Overlay Branding Website Links • Encompass the spoken dialogue intended to be understood that differs in language from the subtitle file. • Translate any narrative burned-in text that is in a different language from the subtitle file. • Conform, within a half second, to the Primary Video Mezzanine that is delivered or to a Netflix-provided Proxy File. • 23.976 video must have subtitles / CC timed to 24.00 timecode, starting at 00. • 25.00 video must have subtitles / CC timed to 25.00 timecode, starting at 00. • 29.97 video must have subtitles / CC timed to 29.97 drop frame timecode, starting at 00. • STL (EBU) • DFXP (valid extensions are .dfxp and .xml) • SRT • SMI
View Source
File Specifications. Electronic files provided to Client or any of their carriers by BE will be provided in a format specification both parties have agreed upon. If Client requests changes to file format specifications after initial files have been sent, BE will charge time and expense based on the hourly rate in effect at the time. All work incurring additional charges will require Client approval before the work will begin.
View Source

Related to File Specifications

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Technical Specifications The purpose of the Technical Specifications (TS), is to define the technical characteristics of the Goods and Related Services required by the Procuring Entity. The Procuring Entity shall prepare the detailed TS consider that:

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.