Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

HD-SDI output workflow possibilities

Lenny Manfred

Well-known member
Joined
Nov 20, 2007
Messages
825
Reaction score
0
Points
16
Location
Los Angeles
Not everyone wants to work in the new uncharted territory that is 4k files. i have a regular client that is all set up for dvcprohd, and is a lot more comfortable with that workflow. in tests with earlier builds, i had no problem shooting non-action footage (talking heads) coming out of the hd-sdi into a 1400 deck and plugging the sound straight to the deck. it looked good to my eye. there is a disconcerting delay when you do it this way, but, somehow, the sound and picture match.

so, feeling confident of my tests, i told the client i could do it, but, i did the update to build 16, and did not re-test. the day of the shoot i got a big surprise. now the hd-sdi output had some kind of 50% translucent frame around the picture, about 10% from the edges. supposedly, anything out of that frame is not recorded on the files, but, of course, it is recorded on the dvcprohd deck. even after talking to RED tech support, no one could figure out how to get rid of it, but they did suggest that if we recorded on the drive, we could play it back clean and it would not have that frame. we did a quick test, and it worked, so we shot most of the morning, and, when we broke for lunch, started to transfer the footage. guess what? no sound. they forgot to tell us that the hd-sdi would not have embedded sound. small detail. it is very disconcerting to me working with the RED at times, because things that you know to be truths, absolutes, are not always the case here. why would i even imagine that their hd-sdi would not have sound? isn't that one of the main things about hd-sdi? but with RED, you can't take anything for granted.

so we where forced at that point to finish recording everything onto the drive. luckily we had a laptop and a couple of hard drives there as back up, and we get the client the files and said good luck. the last i heard is that the sound is clipped, but they are finding a solution. they where happy with the pictures, and that goes a long way, so i hope i don't completely loose them. i keep getting burned with RED, but keep pushing forward. hopefully it won't put me completely out of business before it all comes together.

so i am very interested in finding a solution to this. i don't want to hear how i should find another editor (not an option) or transfer the files for the client (are you going to pay for this, because they are not), or other ideas on how i can make it work the RED way. too many folks here insist on trying to change ny reality, i really want to hear from people that have a solution that fits my reality, not theirs. if build 17 will play back with embedded sound, that might be enough. but i almost prefer a way of getting rid of that stupid frame that came out of nowhere, at least having the option of turning it on or off.

thanks you for reading my rant.
__________________
 
I would recommend always testing your workflow before going under fire. Changing anything like camera firmware right before shooting always involves a huge risk if you haven't tested it with your workflow no matter what sofware, camera, etc you use.
 
Build 17 does play back with embedded audio in HD-SDI. I'll bet in sync as well.

Certainly worth a try.
 
I would recommend always testing your workflow before going under fire. Changing anything like camera firmware right before shooting always involves a huge risk if you haven't tested it with your workflow no matter what sofware, camera, etc you use.

yeah, thanks for re-stating what i just said, but, really, this pretty much only applies to the RED. i have had many updates to software done on my varicam, my hdx900, my d600, etc., etc., without it ruining my workflow. so your theory does not apply to EVERY camera.
 
Firmware updates to other cameras tend to reveal fewer changes and fewer responses to customer requests so this has pluses and minuses. The big push from us to Red for 16 was to enable multiple monitor outputs. We got that but it meant changing things. Which would you rather have, very little change and ignoring your requests or constant improvement from listening to your feedback?
 
Back
Top