FORK Overview

Notas del editor

3. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
4. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
5. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
6. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
7. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
8. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
9. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
10. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
11. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
12. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
13. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
14. - Mac/Win - Crossplatform - FORK Icon = One Source, multiple destinations. - Shared storage - Clients/Server Based
15. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
16. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
17. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
18. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
19. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
20. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
21. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
22. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
23. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
24. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
25. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
26. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
27. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
28. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
29. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
30. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
31. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
32. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
33. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
34. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
35. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
36. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
37. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
38. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
39. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
40. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
41. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
42. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
43. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
44. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
45. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
46. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
47. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
48. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
49. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
50. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
51. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
52. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
53. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
54. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
55. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
56. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
57. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
58. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
59. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
60. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
61. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
62. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
63. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
64. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
65. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
66. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
67. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
68. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
69. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
70. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
71. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
72. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
73. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
74. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
75. Workflow example: - Start an ingest - PDS is looking for available port - Two in use - Free port used - MPR is writing media to storage - Client can view media from storage through share/fyber - Others can view the same media
76. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
77. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
78. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
79. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
80. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
81. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
82. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
83. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
84. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
85. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
86. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
87. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
88. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
89. - Ingest, Edit, Playout - While ingesting, add markers and metadata. ANYWHERE! ANY client - After editing, export timeline: new clip add metadata, markers - PLAYOUT! - Why? Central storage!
109. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
110. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
111. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
112. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
113. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
114. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
115. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
116. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
117. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
118. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
119. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
120. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
121. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
122. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
123. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
124. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
125. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
126. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
127. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
128. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
129. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
130. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
131. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
132. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
133. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
134. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
135. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
136. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
137. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
138. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
139. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
140. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
141. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
142. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
143. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
144. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
145. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
146. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
147. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
148. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
149. FORK Prod Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
150. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
151. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
152. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
153. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
154. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
155. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
156. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
157. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
158. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
159. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
160. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
161. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
162. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
163. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
164. - A clip contains metadata - A smartbin is filtering on metadata - Based on this metadata the clip will be visible in multiple Smart Bins.
166. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
167. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
168. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
169. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
170. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
171. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
172. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
173. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
174. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
175. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
176. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
177. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
178. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
179. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
180. - Central storage: multiple users can work with the same material - FORK Production Server: rack room, 24/7 online, admin only. - FORK Mediaplayer: Ingest/Playout + highres/lowres at the same time! - FORK RFU: transcoding to other formats, QT codecs only. - FORK Production Clients: Same central storage - Connected via ethernet to FORK Production Server.
181. FORK Playout Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
182. FORK Playout Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
183. FORK Playout Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
184. FORK Playout Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
185. FORK Playout Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
186. FORK Playout Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
187. FORK Playout Client runs modules. Depending on user rights, you have access to these modules All modules are in the Client, based on login these modules are activated.
188. - 24/7 playlist - Control windows shows the actual part, including ON-AIR - Playlist moves throught Control Window - Playlist becomes History, short part is visible in the Control Window - Playlist can be editted via Playlist Editor, via a segment (timeframe) - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.
189. - 24/7 playlist - Control windows shows the actual part, including ON-AIR - Playlist moves throught Control Window - Playlist becomes History, short part is visible in the Control Window - Playlist can be editted via Playlist Editor, via a segment (timeframe) - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.
190. - 24/7 playlist - Control windows shows the actual part, including ON-AIR - Playlist moves throught Control Window - Playlist becomes History, short part is visible in the Control Window - Playlist can be editted via Playlist Editor, via a segment (timeframe) - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.
191. - 24/7 playlist - Control windows shows the actual part, including ON-AIR - Playlist moves throught Control Window - Playlist becomes History, short part is visible in the Control Window - Playlist can be editted via Playlist Editor, via a segment (timeframe) - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.
192. - 24/7 playlist - Control windows shows the actual part, including ON-AIR - Playlist moves throught Control Window - Playlist becomes History, short part is visible in the Control Window - Playlist can be editted via Playlist Editor, via a segment (timeframe) - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.
193. - 24/7 playlist - Control windows shows the actual part, including ON-AIR - Playlist moves throught Control Window - Playlist becomes History, short part is visible in the Control Window - Playlist can be editted via Playlist Editor, via a segment (timeframe) - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.
194. - 24/7 playlist - Control windows shows the actual part, including ON-AIR - Playlist moves throught Control Window - Playlist becomes History, short part is visible in the Control Window - Playlist can be editted via Playlist Editor, via a segment (timeframe) - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.
195. - 24/7 playlist - Control windows shows the actual part, including ON-AIR - Playlist moves throught Control Window - Playlist becomes History, short part is visible in the Control Window - Playlist can be editted via Playlist Editor, via a segment (timeframe) - Multiple Playlist Editors can be used, user will get a warning if others are working on the same segment/timeframe.
196. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
197. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
198. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
199. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
200. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
201. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
202. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
203. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
204. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
205. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
206. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
207. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
208. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
209. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
210. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
211. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
212. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
213. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
214. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
215. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
216. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
217. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
218. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
219. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.
220. - A clip contains Metadata + Markers - A clip refers tomnaerials: xxx.tape if it is from tape. Else it’s a xxx.file - A xxx.file is a reference to, for example, xxx.dv, xxxP.dat (lowres) and xxxY.air, where Y is the channel number. - A subclip is a new clips, has it’;s own metadata, but refers to the same Materials.