Meet Kevin Stanley

[MichaelP]

Yes... but getting answers is slow. I am sure he is busy - but these questions are of interest to Avid users and the post industrty at large - such as the PC QT codec, etc.

Does Tony drive the priorities of the RedCine application feature requests or does RED? I can only do so much to keep Avid users up and running when control over the process in not in our hands.

Thanks!

Michael

 

[Kevin Stanley]

Kevin, could you test the sharpen slider please.
many people reported that it doesn't work or it get stuck at some single digit value.

Andrew,

I checked this with XP and OSX MAC PRO Quad and they both work fine. If you installed build 082 and did not remove the old Redcine file from your library then there could be old pref files confusing the new build. There is instructions to remove this in the text file that accompanies the new build.

As a general rule of thumb, if loss of functionality occurs, my starting point is to remove the old Redcine files and re-install the app. NOTE: always copy your old Redcine folder to a safe place as there are logs in it that contain project history.

Hope this helps. Also, If people let me know what systems they are using when issues occur it will help me trouble shoot.

Kevin

 

[Mark L. Pederson]

Welcome aboard Kevin!!

We're gonna have some fun!

 

[Mark L. Pederson]

Try creating a new Redcine project, save it, import your footage (using either "load all" or "load shot") once the footage is in the timeline try selecting each clip (one at a time) by swiping the timeline slider over it. Now change the Framerate in the Format Settings in the Project Tab to 25fps. You will have to do this for every shot just as you would to adjust the shot framing or color.
Kevin

Ridiculous to have to change the timebase in each and every clip one clip at a time. That's not workflow.

Redcine is reading the meta-data of each clip - so, there is ZERO reason I can think of why it doesn't use the framerate.

Am I missing something here?

 

[Mark L. Pederson]

3. I noticed a data field in the XML already being different from one generated in a previous version - will that format be finalized? I can understand additional metadata being added, but previously available metadata no longer being there is harder to deal with. Notably, the "/note/" tag.

Agreed. Clearly the dust has not settled REDCINE XML land - and NAB is tomorrow - and many workflows depend on this BIGTIME. I sincerely hope this gets nipped in the bud and I pray for color settings in the XML.

5. Automatically creating the XML when exporting files rather than a "save project as" and manually setting it to .xml

Michael

I asked for this as well. My request didn't seem well received - there was a concern over "aborted" renders etc, - which doesn't make sense to me - have the app write the XML at the END of a render. YES I want that feature. We use watch folders, etc.

 

[Teague Kennedy]

Andrew,

I checked this with XP and OSX MAC PRO Quad and they both work fine. If you installed build 082 and did not remove the old Redcine file from your library then there could be old pref files confusing the new build. There is instructions to remove this in the text file that accompanies the new build.

As a general rule of thumb, if loss of functionality occurs, my starting point is to remove the old Redcine files and re-install the app. NOTE: always copy your old Redcine folder to a safe place as there are logs in it that contain project history.

Hope this helps. Also, If people let me know what systems they are using when issues occur it will help me trouble shoot.

Kevin

Hey Kevin, welcome. I am having the same problem. I can change the OLPF settings all day in Redcine, and I can see no change in the footage at all. I just installed the most recent version today and had no old version installed before. I have the same issues with Red Alert. Up in one of the drop down menus you can change sharpness, but it doesn't seem to do a darn thing. I'm using an 8 core mac pro. Project is 2k. Any thoughts?
Thanks!

 

[Kevin Stanley]

Ridiculous to have to change the timebase in each and every clip one clip at a time. That's not workflow.

Redcine is reading the meta-data of each clip - so, there is ZERO reason I can think of why it doesn't use the framerate.

Am I missing something here?

I wasn't specific enough. I was not intending that to be a fix for workflow. Just a fix to get the footage to the desired fps while we run some tests.

Kevin

PS. thanks, I'm already having fun!

 

[Mark L. Pederson]

I wasn't specific enough. I was not intending that to be a fix for workflow. Just a fix to get the footage to the desired fps while we run some tests.

Kevin

PS. thanks, I'm already having fun!

Thank GOD!

I was actually sincerely scared for a moment.

I found some other broken stuff in build 82 - but I want to try to carefully recreate before I go crazy posting -

But yeah, glad to have a fresh name to start to drive nuts - I get worried that the RED team is sick of me.

 

[Kevin Stanley]

Hey Kevin, welcome. I am having the same problem. I can change the OLPF settings all day in Redcine, and I can see no change in the footage at all. I just installed the most recent version today and had no old version installed before. I have the same issues with Red Alert. Up in one of the drop down menus you can change sharpness, but it doesn't seem to do a darn thing. I'm using an 8 core mac pro. Project is 2k. Any thoughts?
Thanks!

Thanks Doc,

That's odd, I checked this on a mac 4core today and it worked. the NR was working very well actually. I'll run a test on the 8 core tomorrow and see if there's any difference. Do you have your viewport resolution at full when your making adjustments?

Kevin

 

[Dylan Reeve]

Yes... but getting answers is slow. I am sure he is busy - but these questions are of interest to Avid users and the post industrty at large - such as the PC QT codec, etc. [...] I can only do so much to keep Avid users up and running when control over the process in not in our hands.

Thanks Michael,

I think it is reassuring for those of us in the 'ugly stepsister' camp (Avid/Windows) to see some of this stuff discussed publicly. Means we know at least that these issues are out there and being dealt with.

I'm pleased that the DNxHD export actually works now (it didn't when I tried with build 70 something) - but the inability to choose the codec options is a big limitation.

As for XML, I'd like to see XML files generated by the camera at record time (like the P2 and XDCAM EX formats) - handy for supporting applications and things. But that's not really a post thing I guess.

Good luck Kevin - Us Avid users are a demanding lot (you think this is bad? Try being on the receiving end at Avid! They've been taking a fair bit of flack for quite a while now).

 

[BASSAM MSSALATIE]

kEVIN spent 9 hours onlin in his first day ..did you notice that.
i wonder how many will spend offline trying help us .thanks kevin

 

[Teague Kennedy]

Thanks Doc,

That's odd, I checked this on a mac 4core today and it worked. the NR was working very well actually. I'll run a test on the 8 core tomorrow and see if there's any difference. Do you have your viewport resolution at full when your making adjustments?

Kevin

yes, viewport res was at full.

Thanks.

 

[Andrew M.]

Andrew,

I checked this with XP and OSX MAC PRO Quad and they both work fine. If you installed build 082 and did not remove the old Redcine file from your library then there could be old pref files confusing the new build. There is instructions to remove this in the text file that accompanies the new build.

As a general rule of thumb, if loss of functionality occurs, my starting point is to remove the old Redcine files and re-install the app. NOTE: always copy your old Redcine folder to a safe place as there are logs in it that contain project history.

Hope this helps. Also, If people let me know what systems they are using when issues occur it will help me trouble shoot.

Kevin

Uninstalled, deleted old REDCINE data (all in Application Data\REDCINE) installed again and it works!

NR works great, visible difference.

Details - could be bit more pronounced, very small difference but noticeable.

Sharpen - slider works correct now from 0 to 100 but I can’t see any difference.

Highlight – works but still have to be kicked by changing Contrast or other sliders by .01 or any other value. Highlight slider doesn’t have (execute_value_after_change), implemented as all other sliders have.

I am using Jim’s race track clip A003_C007_071105_001.R3D and MARTIAL_ARTS_feet.R3D

from here:
http://www.redrelay.net/owners/0010/ (Jarred Land) post
http://www.redrelay.net/owners/0232/ (Jon Firestone, Chris Bagley) post

Hardware:
Dell XPS M1730 with NVIDIA Intel dual core XP 32bit

 

[Mark L. Pederson]

We REALLY need the ability to APPLY settings created to a shot in the SHOT PANE of REDCINE - to other shots - a "copy and paste" function - and an "apply to all" function - there are a million times you will find a "best light" for a set for example and want to put that look on all the shots in that set - etc.

Right now, REDCINE is very a much a one shot at a time situation without ease to handle lots of shots quickly -


Just a few more features (yeah audio pass through and XML spec, etc.) and we can get rockin with it -

 

[Cüneyt Kaya]

i can copy and pace color settings (including a created s-curve) to other shots,
is it possible to copy just the s-curve, and this to selected shots (like other takes ect.) or to all?

btw. you seem to answer questions like Data from Star Trek..means great to have you here.


_______@mark------automator is now a friend

 

[Mark L. Pederson]

i can copy and pace color settings (including a created s-curve) to other shots,
is it possible to copy just the s-curve, and this to selected shots (like other takes ect.) or to all?

btw. you seem to answer questions like Data from Star Trek..means great to have you here.


_______@mark------automator is now a friend

Exactly. What I meant is I want to be able to select ONLY what I want to copy - NOT copy everything (scaling, white balance, etc.)

 

[Cüneyt Kaya]

but also it would be cool to be able to copy certain settings to a certain number of selected shots...and the ability to load LUTs, ok this feature would be really cool.

 

[BASSAM MSSALATIE]

but also it would be cool to be able to copy certain settings to a certain number of selected shots...and the ability to load LUTs, ok this feature would be really cool.

and if you add the ability to save those settings for each different project
for later use either for same project preferences or for other projects with
similar settings.:devil:

 

[Cüneyt Kaya]

i didnt try it, but what you are wanting is possible now i think..

 

[Sean]

Hmmm.... thanks for the quick response. That is a bit high level. My questions are for file based workflows - not tape based. Avid will soon have a RED XML to ALE conversion for ingest of the QT based proxies - but the choice of data rate is based on REDCINE to which there is no control by the user. For now the questions are basic - there is a lot more metadata that is of interest to the post production workflow that is still not available -

For now:

1. When will a QT codec for PC be available?
2. When will the DNxHD data rates be available within RedCine (Mac or PC)?
3. I noticed a data field in the XML already being different from one generated in a previous version - will that format be finalized? I can understand additional metadata being added, but previously available metadata no longer being there is harder to deal with. Notably, the "/note/" tag.
4. Easy presets for output where a DPX export matches the QT file name and format.
5. Automatically creating the XML when exporting files rather than a "save project as" and manually setting it to .xml

Michael

Michael, aren't you already talking to Tony directly about these questions?

It's tremendously valuable to me to see some forum discussion on these topics rather than be left in the dark about offline discussions and negotiations. The openness of Red has been really impressive, and I continue to learn a lot from the questions that MichaelP is posting, since I will be tackling these workflow questions very soon. I'd rather know what I'm up against before the camera arrives!