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 :)

Forcing Reel number back to 001 on new day

Vladimir Eugene

Well-known member
Joined
Dec 29, 2006
Messages
1,083
Reaction score
0
Points
0
Location
Los Angeles, CA
On Build 9. I'm loving build 9, but am having a bit of a problem with this one, and I left my cell at the hotel.

Vladimir
 
Hey Vlad :-)

Hey Vlad :-)

Are you near the set or location of a shoot, not able to go get your phone, and in need of assistance? If that's the case, and you can't place a call from a pay phone for some reason, specify the problem and I'm sure in a few minutes or seconds someone will answer your problem from here. Good luck. Good to see you're out there doing your thing.

Cheers!
 
Hi Jaadgy,

Thanks, it is such a minor thing, I hisitated to mention it. I realized later that I could email support. It's on the manual, but I must be doing something wrong. I'm sure Red will send me an email soon.

How are you doing? I'm right outside of Chicago at the moment and realized, most of the bugs the camera was giving me was Operator error. Mark #41 cleared the problem I was having. The camera is wonderful, and support is great, with even greater network
 
Hope the last day goes well, guys, and I hope that crazy CA doesn't mess up your shoot. I had a great time in Rockford with y'all. Sorry I'll miss the toasted martinis. Sounds kinda dangerous, though.

-Chris
 
vlad
did you find a solutionfor this ? It was driving me crazy all day long! Especilly when the first card of the day reset to A-001 and the second card got named A-023 LOL
 
vlad
did you find a solutionfor this ? It was driving me crazy all day long! Especilly when the first card of the day reset to A-001 and the second card got named A-023 LOL

I don't know if the fault is still present in 1.3.6 but in 1.3.5 it was worked around by changing project frame rate and then back to your original.
I.E if your base fps, is 24 change to 25 and then back to 24.
 
Back
Top