NG
A good point about the editing demands, but the idea of an essential function like recording being soley on the same network as the desktops is a bit silly. Systems I know of (and have used) have their full-res system on a broadcast network and the low-res (for editing) accessible via the IT network. They should be able to use the record ports independently of the desktop interfaces which will only use a proxy copy of the material. On the system i use for example the interface for the record ports is on a PC but is on the broadcast network. even if this software goes down you can just do the same function manually direct on the server itself
Although this isn't perfect (the high and low res databases will become unsynced) it does allow you to continue if the IT side gets compromised.
The problem with that is that it ends up centralising feed recording doesn't it. The Jupiter system allows ANY desktop to record - not just those designated for media management.
The method you propose is fine for small scale operations - but is based on a specific staffing model.
Perhaps a better solution would be dual networks - with PCs having two network connections?
I guess the other issue is that if the main IT network dies, it takes ENPS with it, so you're basically screwed anyway with an automated gallery...
noggin
Founding member
Most feeds are recorded at TVC using Jupiter - which is controlled by BBC Desktop PCs... over the network. If you can't use your BBC Desktop PC - you can't use Jupiter and thus can't make a recording, or view existing recordings outside edit suites. In those cases you have to use edit suites and editors to make recordings, view them and edit them... Not as many of them as there used to be.
A lot of editing is also done in Jupiter, which stops if the network stops - so the amount of editing required in the suites that also now need to record feeds goes up.
A lot of editing is also done in Jupiter, which stops if the network stops - so the amount of editing required in the suites that also now need to record feeds goes up.
A good point about the editing demands, but the idea of an essential function like recording being soley on the same network as the desktops is a bit silly. Systems I know of (and have used) have their full-res system on a broadcast network and the low-res (for editing) accessible via the IT network. They should be able to use the record ports independently of the desktop interfaces which will only use a proxy copy of the material. On the system i use for example the interface for the record ports is on a PC but is on the broadcast network. even if this software goes down you can just do the same function manually direct on the server itself
Although this isn't perfect (the high and low res databases will become unsynced) it does allow you to continue if the IT side gets compromised.
The problem with that is that it ends up centralising feed recording doesn't it. The Jupiter system allows ANY desktop to record - not just those designated for media management.
The method you propose is fine for small scale operations - but is based on a specific staffing model.
Perhaps a better solution would be dual networks - with PCs having two network connections?
I guess the other issue is that if the main IT network dies, it takes ENPS with it, so you're basically screwed anyway with an automated gallery...