Watch out when doing multiple Load All's!

[sander kamp]

This bug in RedCine cost me a day of frustration and work.

When you import folders with the Load All function and then do another import with Load All the shots don't come after another in the timeline. If the playhead is somewhere in the middle of the timeline all your new footage gets ON TOP of the old footage. If the playhead is at the end of the timeline the FIRST NEW SHOT is set ON TOP of the last shot in the timeline.

I don't know what the reasoning is behind this but when rendering out multiple folders my client was complaining that footage was missing and I was wondering what went wrong.

I really like RedCine and I think it is one of the selling points of the RED camera. But all these bugs and annoyances need to be fixed. Please.

 

[Cüneyt Kaya]

did you set depth level to ten...

see under the library tab.

 

[sander kamp]

Depth level doesn't make a difference here, try for yourself.

 

[Jeff Brown]

The best thing to do is bring in all of your rushes in one import from the top level folder (setting the depth level appropriately). That way you'll get all your shots on the timeline OK.

Regards

Jeff brown
RED708

 

[Cüneyt Kaya]

will test it....but sander is right...this cant be so much of a problem to solve.

 

[Lucas Wilson]

This isn't a bug... REDCINE will load clips starting with the slot you have selected!

1) Go to the Library
2) Scroll to the end of the timeline
3) Right click after the last slot and say "Insert Slot"
4) Click under the empty slot - the place where there is timecode or other information under individual slots
5) Click Load All.

Now clips will load like you want.

Lucas

 

[sander kamp]

Why does it load new clips on top of others by default? I don't understand what the use of it is.

If you're not in the library you don't see what is happening and you miss the fact that some clips will not play or be put out because they are not in the timeline.

And if loading new clips CAN make new slots then why do I have to make just one new slot for the first clip. It doesn't make sense to me.

 

[M Most]

Why does it load new clips on top of others by default? I don't understand what the use of it is.

If you're not in the library you don't see what is happening and you miss the fact that some clips will not play or be put out because they are not in the timeline.

And if loading new clips CAN make new slots then why do I have to make just one new slot for the first clip. It doesn't make sense to me.

It all makes perfect sense if you understand that the basic interface was designed for a conforming/data management application (Scratch). If you're doing a conform, or creating changes to an existing timeline, you sometimes want to replace a group of clips with new ones, or replace from a certain point in the timeline to another. In Scratch, the Construct (the Library in Redcine) and the Edit module (which doesn't exist in Redcine) are tightly interwoven, and the ability to do what you're talking about is valuable.

Of course, Scratch and Redcine are two different programs with two very different purposes. And Redcine is not under Assimilate's direct control, it is a Red product. So it might make sense to have a different default behavior, or at least a user selection to control this (i.e., a choice between "add at end of construct" vs. "add at current slot selection").

 

[sander kamp]

Ah, now I understand.