Welcome to our community

Be a part of something great, join today!

Register Log in
  • 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 :)

My Build 15 Experiences

D

Dylan Reeve

Well-known member
Joined
Oct 29, 2007
Messages
1,151
Reaction score
0
Points
0
Website
www.shotwrangler.com
We shot a music video on Build 15 today (yeah, I know... Beta...)

Went very well, aside from two issues - once clearly specific to Build 15 and one perhaps not so much?

1) Boot up hang. I've posted about that in the thread on the subject.

More concerning to me (as DIT and Post Supervisor) was this however:

2) Duplicate Reels. On power down the reel counted seemed to reset to A001, so we ended up recording two A001 reels, and one shot on a second A002 reel. The naming convention of the files clearly clashes (but I noticed before offload so put them in another directory). From then on we had to Force the reel number of each card (even after forcing the number, the next card formats by default as the next sequential number from the last full power down (so A002, which we had to force to A009 for example).

Then, when we switched to the RED Drive we formatted it as B001 for identification purposes. Which was fine, we shot a dozen clips or so as that. But after shooting on CF for a while longer we then went back to the RED Drive for the last shots (time-critical during sunset, no time for reel changes).. On mount it identified as B001_C-whatever, but then it proceeded to record as A001_C001 (and A001_C002). The CF remained labeled as B001_080314, and the directory is B001_080314, but in that root directory there is A001 and B001 clips.

So, I not have three separate A001 reels, and two A002s (although only one shot on the second).

What the hell do I do to fix these dupe reels? I've left numerical gaps for them in the proper reel sequence, but the REEL name is written in to the file name, the metadata, and in the header of the file - can I fix it? Deanan? Jarred?... HELP?!

My advice here, is be very very mindful of your reel sequencing - because not only are duplicate reels a pain in the ass for editing, the file naming will actually clash, so files will overwrite one another if you're not careful. For example, building all the QT ref files into a single directory is impossible, as the latter duplicate reels clobber the earlier ones.

It's 11:30pm here, and I started on set at 7am, so I think I'll go to bed now, but I'm quietly confident that I'll come back to a wealth of knowledge tomorrow morning.

In the meantime, build 15 was excellent. The all-active outputs was a huge huge help today. And, while I'm only speculating, it seemed like the sensor protect (black sun) might have been improved, because we had some really bright spots today (sun reflecting in chrome, etc) and no scary purple blobs turned up where I was suspecting they might.

Tomorrow, I will post some on-set shots of the rigs we used today. There was some insane set ups.
 
Interestingly I came up with the same dupe clip numbers when changing magazines or powering down, even when putting on a drive that was on before and hadn't been reformatted. The numbers clash but instead of an overwrite, the camera appears to record the new clip but since the number clashes nothing is written to the drive. This was an earlier build mind.

But then it was a Music Video too. What is it with those? ;)
 
Build 15 quirk?

Build 15 quirk?

So we upgraded to build 15 and it all does what was anticipated.

I did find a quirk though. When we have the camera set to, ie 29.97, 59.94, or any other frame rate, the LCD will display in the upper left corner the correct FPS as well as the display on the back of the camera. But in the bottom left corner which display the magazine info, the display ALWAYS reads 23.98.

The resolution is correct but the frame rate ALWAYS reads 23.08

We have re-formatted CF cards and the Red Drive to frame rates other than 23.98 and like I said, the camera display on the back of the camera and the upper left corner on the LCD read out correctly but the bottom left information on the LCD still states 23.98.

We have powered down between each change as well. Still the same issue.

Looking at recorded material in playback, they look like they are recording at the proper frame rates that we have set on the camera, so we are confident that the camera is recording properly but its just that display thing.

Anyone else have this or noticed this?

Thanks
 
Yes our guys notice the incorrect frame display as well. Seems to record fine however.
 
Not Build 15 Related

Not Build 15 Related

The duplicate reel thing is not Build 15 related. We have test footage that we shot and recorded to our hard drive with two A001 reels and we haven't upgraded yet.
 
fps indication

fps indication

We have re-formatted CF cards and the Red Drive to frame rates other than 23.98 and like I said, the camera display on the back of the camera and the upper left corner on the LCD read out correctly but the bottom left information on the LCD still states 23.98.
Click to expand...

Agreed, it seems to do this when you select a Project Frame Rate of 29.97, 50.00 or 59.94, but works for me when the Project Frame Rate is 23.98, 24.00 or 25.00. Recording and playback are not affected its just a GUI feedback issue, thanks for the feedback.
 
Dylan, thanks for the report. We have a shoot today where the client has opted for build 15 and are flying solo. They are going Red Drives which we have pre-formatted on build 15. They all formatted as A001, A002, A003

I'll try and get Matt to set today to check that is carrying through.

Our own brief tests showed the camera to be picky on boot up depending on what was plugged in at the time. This seemed to link with the LCD as we always got picture on the EVF, but sometimes not the LCD.

Had another instance of LCD stutter but this was cleared with a re-boot.

Edit:Oh yes. On one Red CF card 'media too slow' for 4k RC28! did not have time to check other cards or if a format under build 15 would of cleared that.
 
we had some funkiness in menu settings where it would not allow us to change the shutter speed. We could adjust the dial (twist the knob) and get a different speed, but when we selected that speed (pushing in on knob) it would not change the speed in the small window in upper right corner.

A reboot corrected the problem temporarily, but it has come back again.
 
Rocketeer said:
Dylan, thanks for the report. We have a shoot today where the client has opted for build 15 and are flying solo. They are going Red Drives which we have pre-formatted on build 15. They all formatted as A001, A002, A003
Click to expand...

Hey Scott, we only had one RED Drive, and it was only mounted twice (on two separate power ups) the first time we formatted as B001 to avoid any confusion, so later when it recorded as A001 onto that drive (when mounted again hours later at a different location) there was no clip conflict on the drive specifically, but other reels from the shoot were also A001.

As mentioned above, apparently if the drive had already had A001 clips on it, the second lot would have just not recorded? I'm pleased that didn't happen, because there was a 10 minute window for the last two takes, and no do-overs :)

As it requires a format to force the REEL or CAM number to change, I'm not sure how you'd avoid this?[/QUOTE]
 
You must log in or register to reply here.
Back
Top