By using our API integration with Bright River’s system Stream, we are able to send any type of file directly to their production system.
Generally speaking, there are two types of files that we will send to Post Production, the main image that is needing editing, and a type of resource file that is used to help support the editing of the main image. Whether that be for colour accuracy, stacking, ghost mannequin effects, or just additional files to help an editor in their retouching process.
Typically as a studio, you will not need these files returned back to Creative Force, but you do need to have them sent to the vendor to ensure the images are edited as expected. The logic is a bit nerdy but useful to know!
When sending these different files to Bright River’s system we will send them in slightly different URL strings so that Bright River will know the purpose of the respective files, and which ones to return.
Below is a breakdown of the variance of the URL strings based on the type of image that we are sending.
Image Type | Image Type Description | Format in the URL that is sent to Bright River |
Main Image | The main image that needs to be edited and sent back to Creative Force | URL will include the value “imageURL” in the string |
In-clip Files | Supporting files that are needed to help create “Ghost Mannequin” composite images. Learn more about the general setup here | URL will include one of the following values in the string: imageURL2, imageURL3, imageURL4, imageURL5 |
Colour Reference Files | Support files sent to help ensure the colour accuracy of a given product. Learn more here. | URL will include the value “imageURLGroup” in the string |
Resource Files | General supporting files that you may need to send from time to time to a vendor, but do not need to be in a set process. Learn more here | URL will include the value “additionalResourceFileURLGroup” in the string |
Based on the above logic Bright River will know which images need to be returned, and the purpose of the supporting files.