Workflow from Render to Editing & Export?

[secundar]

I recommend using the File-->Open Image Sequence... import feature of QuickTime Pro. You can choose to save it as a reference movie so that it acts as a pointer to the TGA sequence but still can be played as a movie and dropped in an FCP timeline.

[scrimski]

Do your edit before the comp work.

The gamma problem has been discussed and solved before, use the search funtion.

[ciclopez]

Thank you for the answers :)

I recommend using the File-->Open Image Sequence... import feature of QuickTime Pro. You can choose to save it as a reference movie so that it acts as a pointer to the TGA sequence but still can be played as a movie and dropped in an FCP timeline.

I tried it but when I drop the QT renference into a secuence it gives me a "General Error" and another "Error: Out of memory" And it's only a 50 frame image secuence. Is that normal? Maybe if I try with tif secuence instead of tga?


Do your edit before the comp work.

The gamma problem has been discussed and solved before, use the search funtion.

I can't do my edit before the comp because I have many layers and I think it's not an appropriate workflow.
Anyway, I still have the same problem. I used the search funtion (when it worked) and I can't find a solution. There are many threads but no one have a solution for me.


I have also searched high and low for a solution to the "washed out" look. After an almost sleepless night I came across the fix without having to mess around with color profiles. I'm working from a PC so some of the commands might be slightly different.

After you create the QuickTime/h.264 file, open it up in QuickTime and select "Show Movie Properties." Highlight the video track then click on the "Visual Settings" tab. Towards the bottom left you should see "Transparency" with a drop-down box next to it. Select "Blend" from the menu then move the "Transparency Level" slider to 100%. Right after that, choose "Straight Alpha" from the same drop-down and close the properties window. AND finally, "Save."
This did'n work for me


http://forums.cgsociety.org/showthread.php?f=2&t=573790&page=1&pp=15
Gamma Stripper did'n work too... There was no embedded gamma tags inside the quicktime file :(

[scrimski]

I have many layers and I think it's not an appropriate workflow.
Actually it is the common workflow. Edit one layer before your comp to set the pace, determine which parts you don't use aka you don't have to comp later on. Picture quality isn't essential in editing.

http://forums.cgsociety.org/showthread.php?f=2&t=573790&page=1&pp=15

#6 works great here.

If it fails, consider a different codec, sorensen3 or mpeg 4.

[ciclopez]

Actually it is the common workflow. Edit one layer before your comp to set the pace, determine which parts you don't use aka you don't have to comp later on. Picture quality isn't essential in editing.
But to determine which parts aren't used I have made an Animatic before. Do you mean that I have to Edit my 45 CG shots with 5 layers per shot and then send them to comp, instead of making the comp per shot and then editing all composed shots? I don't understand the method you are using. How I'm suposed to edit with only a foreground or background layer of CG? And if need to retouch any cut or add sounds?

#6 works great here.
Not here :(
I'm using a macbook pro and I tried it under mac and under win with no results

[scrimski]

But to determine which parts aren't used I have made an Animatic before.
An information you missed to provide before. If you are happy with your timing, go ahead.
Do you mean that I have to Edit my 45 CG shots with 5 layers per shot and then send them to comp, instead of making the comp per shot and then editing all composed shots?
Basically yes. I wouldn't start to comp before the picture lock(the point where the edit is done and set, hammered into stone and won't change anymore). Comping all the material I might use for an edit usually ends up in more work as you have to comp the trims too.
If you don't have any trims- good for you, do as you like.
How I'm suposed to edit with only a foreground or background layer of CG?
The same way like you animated your animatic.
And if need to retouch any cut or add sounds?
You are going to explode. What's the point in this question?

[ciclopez]

You are going to explode. What's the point in this question?
sorry, let me explain. I'm planning to send the edited short to a friend who is going to make the sound and the music, so I need to send him the final composited shots edited. He is going to give me back some sound tracks that I'm going to add to de edition and then export all of this to whatever format I use finally. Anyway, I don't understand why to edit all my 40 shadow pass shots in sequence, then edit all my 40 foreground pass shots in sequence, then... If I touch any cut because it convinced me in the animatic but not in the final render, I have to touch that cuts exactly the same in each pass. Is not much easier to make the edition with composited shots? I think that's the way to work in a CG film production. Imagine the same process with 500 shots or more instead of 40.

Thanks for the answers again :)

[scrimski]

Anyway, I don't understand why to edit all my 40 shadow pass shots in sequence, then edit all my 40 foreground pass shots in sequence, then...Me neither. And I have no idea why anyone would come up with something like this nor why you blame me for your completely wrong thoughts about this process.

You do one edit, with as rough as possible comp or even one single pass in which you determine your start and end frame for each and every clip/picture/scene in that edit(this part is called offline edit)
ie: clip 1 starts with frame 1 and ends with frame 100. In the offline edit you decide you only need frames 8 to 80, so you comp everything together within these frames AFTER the offline edit(in which you determined the exact length).
You don't edit every pass, this would be just plain stupid.

The advantage of this is extremely obvious: If you have trims like 2 or 3 frames on 500 houndred shots (very hypotetical numbers, just for the math) this will add up to 1000 or 1500 frames of trims, multiplied with the number of passes(basic setup - diffuse, shadow, AO, light, reflection, specular) = 6000 to 9000 frames you do not need to process, render out of comp, encode and so on.

[ciclopez]

I finally made a QT export in a PC with an earlier version of QT (v7.3 instead of v7.4.1) and it worked fine... what's the problem with QT 7.4? I can't use this other PC cause it's not mine... what I'm suposed to do? I can't belive it... maybe is a problem with the integrated hardware function to accelerate H.264 compressions coming with macbook pro's nvidia card... or it's really a bug of this version of QT... or both... :(

[ciclopez]

You do one edit, with as rough as possible comp or even one single pass in which you determine your start and end frame for each and every clip/picture/scene in that edit(this part is called offline edit)

I know what offline edit means and what is for. Sorry, I think that we are agree and everything has been a misunderstanding.

[ciclopez]

CG-talk is not running well. Sorry, duplicated post.

[scrimski]

Finally sorted out.

what's the problem with QT 7.4?QT 7.4 is the problem. Incompatible with a variety of software, including After effects.

[ciclopez]

Witch version of QT should I use? I just tried 7.3.1 on mac and makes the same as 7.4.1.
I can't find v7.3 for mac and it wasn't easy to install a prev version of QT.
I still have the same problem of "Out of memory" on FCP, but it's imposible cause I'm monitoring the memory and I have more than a Gb when it happens.

[ciclopez]

Just found 7.3 for mac, installed it with pacifist (I didn't find any other way to install it cause it's a downgrade install) and same problem. I'm tired of this s**t.
I'm going to try the same thing in windows

[ciclopez]

Finally I resolved the gamma problem by reinstalling to QT v7.3(.0) in windows (in mac did'n work as you can read before) So next thing I'm going to try is to reinstall leopard and don't upgrade QT. This all is s**t but I don't have any other ways if I want to use Final Cut. I hope this solves the memory error problem too.

I will post any news.

[ciclopez]

Definitely I can't use H.264 QT on macOS. After the reinstalation of Leopard (QuickTime 7.2.1) I tried to compress obtaining the same creepy result, and Final Cut continues giving the Memory error with any type of image secuence preloaded on QT and made a QT-reference ¿Anyone with the same error?

since anybody seems to know a solution for any of my problems I decided to change the workflow to the following that seems to work:

-XSI Final Renders
[TGA sequence]>
-Shake
[QT-Animation codec]>
-Final Cut Pro
[QT-Animation codec]>
-QT v.7.3.0 windows
>[QT-H.264]

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.