Welcome to our community

Be a part of something great, join today!

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

Beta REDCINE for Build 16...

Still can't get QuickTimes to render across a network (even with v108). Regardless of file size. I keep getting random frame writing errors.

I've tried several different Macs, trashed prefs, etc. The problems are consistent.

Obviously, I can render TIFF for now, but I really need the QT solution.

Any help?

Thanks,
Phil

http://www.artbeats.com
 
What about rendering to the computer REDCINE is on?
When you say network - you mean ethernet, wireless or
networked drives??
 
Rendering to the same computer Redcine is on works fine. However, the storage servers (connected by ethernet) is where the work really needs to go. I can't imagine I'm the only one using this method to facilitate a production cycle (but then, I've been wrong before).

Thanks for responding :)

Phil
http://www.artbeats.com
 
What kind of storage servers?
 
I have never had success rendering over ethernet.
But then I was never an IT guru either!!
I usually have projects on separate G-raid drives.
We are moving away from the PC and now I finally
have a MAC with FCS2 and the Adobe Suite on it.
Makes life loads easier!
 
Mike Prevette said:
What kind of storage servers?
Click to expand...

Hi Mike,

We use OSX server. Hardware is six Apple XServes with other storage including XServe raids and SataBeast. We have been rendering After Effects projects to these servers for years (constantly updating of course) without problems. Even file sizes over 2gb.

Thanks,
Phil
 
Phil:

I will try to replicate your network-rendering problem in the morning. We too will be using our network storage a great deal in the near future. Currently, however, we are rendering to 1080proresHQ and our network is simply not fast enough to serve these files up, so we render locally. I will post results later in day.

Best Regards,

Nick.
 
Phil Bates said:
Hi Mike,

We use OSX server. Hardware is six Apple XServes with other storage including XServe raids and SataBeast. We have been rendering After Effects projects to these servers for years (constantly updating of course) without problems. Even file sizes over 2gb.

Thanks,
Phil
Click to expand...

I have similar hardware to you. We use XSAN however to access our XServe Raids.

No problems this end.
 
Record failure on #340 tonight Build 16

Record failure on #340 tonight Build 16

I was testing for a recording I will be doing starting tomorrow through Sunday of a new musical.
I was strangly enough testing the camera sync performance. I will be recording some of the music on one camera and some on the other as there are more than 4 channels to record.

I set up both cameras for 29.97 FPS, 4K 16:9, Redcode 28, shutter 1/96 sec.
jam sync with both cams fed from a single low impedence timecode source. (29.97 non drop frame).
Camera #340 had one audio connection enabled, (channel 2) as microphone at -20db with phantom power turned on. (Shotgun mic).

Camera 1538 was the same except that it's mic was plugged into it's channel 1.
At approximately 1h7min camera #340 stopped recording and displayed a red message which I should have written down but it said something like record error audio. I pressed record again a couple of times and got the same error.
(The camera did save the files though).

Since that is about a normal clip length for me, I am concerned. I have repeated the test and am now at 1h18m without any known problem. The cameras have not been powered down, but I did reformat the drives on both machines after looking at them briefly in Redcine.

(I am going to use the time slate again and then stop recording and check to see if the audio stayed in sync. On b15 it drifted, which would make what I need to do this weekend unworkble.)

Dave
 
neathedo said:
I was testing for a recording I will be doing starting tomorrow through Sunday of a new musical.
I was strangly enough testing the camera sync performance. I will be recording some of the music on one camera and some on the other as there are more than 4 channels to record.

I set up both cameras for 29.97 FPS, 4K 16:9, Redcode 28, shutter 1/96 sec.
jam sync with both cams fed from a single low impedence timecode source. (29.97 non drop frame).
Camera #340 had one audio connection enabled, (channel 2) as microphone at -20db with phantom power turned on. (Shotgun mic).

Camera 1538 was the same except that it's mic was plugged into it's channel 1.
At approximately 1h7min camera #340 stopped recording and displayed a red message which I should have written down but it said something like record error audio. I pressed record again a couple of times and got the same error.
(The camera did save the files though).

Since that is about a normal clip length for me, I am concerned. I have repeated the test and am now at 1h18m without any known problem. The cameras have not been powered down, but I did reformat the drives on both machines after looking at them briefly in Redcine.

(I am going to use the time slate again and then stop recording and check to see if the audio stayed in sync. On b15 it drifted, which would make what I need to do this weekend unworkble.)

Dave
Click to expand...


a short term solution might be to get a tri level sync running into the camera and a time code box running into both cameras.
 
Thank you. I am trying to get the equipment locally today, but having no success so far. I do think though that I would have to run timecode and tri level to both cameras. Red appears to only jam sync on the time code when you begin recording then free run from there. Also it doesn't appear to sync the wordclock for audio to the time code accurately (when not using external tri level). I'm assuming that running tri level to both machines will put and keep them both in sync (as long as the tri level is from the same source as the timecode).

Dave
 
Another audio error

Another audio error

I had another audio error this morning. This time it was the other camera (#1538) and was during in camera playback of a short clip.

Dave
 
One thing missing in the Windows version is the root directory drives don't show their drive names, only the drive letters. Mac version sees drive names fine (it has to I guess, given that Macs don't use letters). Subfolders show names properly on both OS's. Could we get drive names showing in the next build if possible?

Cheers!

Paul
 
Possible Bug

Possible Bug

After opening Redcine with clips already in it, I cannot play the timeline from the Player. I have to switch to Library and then back to Player in order for the timeline to playback.

Best Regards!

7/16/08 - downloaded and ran the latest build and everything that I spotted as an issue has been resolved. clips playback after opening RedCine a second time and ISO works.
 
You must log in or register to reply here.
Back
Top