The Server Pack
The most powerful audio restoration system ever created
Have you ever wished that you could record audio onto a restoration system, generate and edit its embedded metadata while recording, while simultaneously processing numerous other files that exist elsewhere on your network? How about working in real-time on a particularly intractable piece of audio while the system processes a dozen other files in the background? Or maybe you currently work on another manufacturer's dedicated ingestion system, and you would like to access the power and quality of CEDAR from your own desktop without getting out of your chair or transferring files between computers...
CEDAR Cambridge Servers offer you all of this, and more.
Developed following extensive discussions with archivists, audio libraries, and post-production houses, a CEDAR Cambridge server system comprises four elements:
The CEDAR Cambridge CAM/SP Server Pack
CAM/SP provides the most efficient audio processing environment ever developed. Its capabilities fall into two principal areas:
- print-server style batch processing, locally and across a network
- background processing supporting multiple instances of CEDAR Cambridge simultaneously
The latest CEDAR Cambridge software core
CEDAR Cambridge Server is hosted by the latest CEDAR Cambridge software core, which includes an audio recorder with BEXT metadata editing, precise metering, M/S tools, sample rate conversion, a DC filter and more.
The Host System
The CAM/SP Server Pack is compatible with all CEDAR Cambridge systems, from the earliest dual-Xeon machines (with additional RAM) to the latest multi-core processors. This means that all owners can add server functionality to their systems if they wish.
Any combination of CEDAR Cambridge audio processes you desire
There is a growing family of CEDAR Cambridge processing modules. These are applicable in all areas of audio and all modules can be obtained and installed individually as required.
Convenience and efficiency
Imagine the scenario:
You switch on your CEDAR Cambridge system, access a file, load the processes you need, and determine the parameters that offer the best results. In the past, you then processed the audio in real-time or pressed Render and waited for processing to be completed before you could move on. But with the CAM/SP server pack, you simply 'click' the job into background mode, whereupon the system will render it as and when processing power is available to do so.
You are now free invoke a second instance of CEDAR Cambridge on the same host system. Having done so, you can load another file and, in the foreground, work out the parameters that offer the best results. You don't even have to use the same audio processes as before; you are free to create a completely new signal chain if you wish. When you have done so, you place job #2 into background mode, invoke a third instance of CEDAR Cambridge and move onto job #3...
At this point, you may be wondering whether the first job needs to be completed before the background processing mode will accept job #2. Of course it doesn't... CEDAR Cambridge allows you to launch multiple instances of the entire system so you can keep setting up jobs and placing them in the background, right up to the limit of the hardware to handle them. What's more, every instance of CEDAR Cambridge is independent of all the others, with separate processing chains and independent parameters for each.
Background processing is a remarkable leap forward in ease of use and productivity, and it will be a boon for every audio archivist and librarian, as well as for sound engineers handling large volumes of audio in post, broadcast, and audio forensic investigation.
An audio restoration system that works as quickly, effectively and simply as a print server... That's the concept that lies behind the CEDAR Cambridge batch processing system.
Imagine that you are working on a large network of ingestion systems, processors, RAID arrays, or even other workstations, and that you need to access the unsurpassed audio capabilities of CEDAR's audio restoration and other processes. No problem! You can be sitting on the other side of the studio facility to the CEDAR Cambridge server system, but if you can see the its input folder, you can simply drag-and-drop your audio into this, whereupon it will add the file to the queue (if there is one) and later place the processed audio in a chosen destination.
Think about how this could help you and your company. Every seat in every studio can have access to a set of pre-determined CEDAR setups, no matter where the CEDAR Cambridge Server is physically installed.
Combining background processing and batch processing
We knew the questions that you were going to ask next... "Is it possible to combine multiple instances of CEDAR Cambridge Server in background mode, each with its own batch processing input and output folder, and each with different processing chains and parameter sets? What's more, can I place the output folders on different servers around the network?"
So, rather than wait for you to ask for them, we took care of it. You can set up as many processing environments as you like - say, a declick and debuzz batch processor for old recordings, a mild dehissing batch processor for high quality tapes, and so on - and then you and your colleagues can drop your audio into the appropriate input folder, as you wish. CEDAR Cambridge Server will process the files according to each setup, and the results can be made available to anybody on the network who wants them.
Reporting from the Batch Processor
If the Report Generator is available on your system, the Batch Processor allows you to generate an individual report in either XML or HTML format for every track it processes. The reports are stored alongside the processed audio, so large quantities of audio and processing metadata can be added efficiently to users' databases and asset management systems.
CAM/XE: XML Extension
Integration with media asset management (and other) systems
Developed in response to requests from national sound archives and libraries, the XML extension extends the Batch Processing system and allows the processing applied to each audio file to be specified by a software file called a batch token. This contains information such as the location of the source audio and its file name, what processes you would like to apply to the audio, where you would like the results deposited, and whether you would like a processing report generated. In addition, an XML log file can be created for each batch job.