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

new REDCINE-X feedback

Also guys - a warning when opening a project and you have automatically save RMD files set to on and option to turn it off, since any clips that are used in the project you are about to open will re-write their settings to the RMD files when you open the project - possibly overwriting all the work you just did creating looks and syncing audio to them in your session so far.

(this happened to me so I know now to check)
 
One final question, having overloaded you with feedback, requests and ideas:

Are RMD's supported in any third party apps yet so your initial grades carry through?

They seem to have no effect in the latest plugin for Color.

& when Quicktime proxies are exported there is no feedback to tell you it was successful - would be nice to have some though my trust in it is growing.
 
EDL

EDL

Hi all,
I think its great that the EDL option is available, but for some reason it seems not to be working for me. Has anyone else been having issues getting the EDL function to work properly?

Thanks
 
Quentin_B said:
One final question, having overloaded you with feedback, requests and ideas:

Are RMD's supported in any third party apps yet so your initial grades carry through?
Click to expand...
Yes, the Adobe CS5 suite (Premiere Pro, After Effects) support RMD input, writing and output in both directions. It's a great way to maximise both platforms.

HTH

Paul
 
For me, there seems to be a bug in Build 326 when rendering subclips using the new Redline (software) rendering option. Whenever there are multiple clips pulling from the same R3D file (i.e. subclips), RCX will only render one of those clips and simply skip rendering the other ones (it will write the file names, but it will do nothing else and go straight to "Finished").

I've been able to duplicate this problem in both the 32-bit and 64-bit versions of Build 326. I was really excited about having the Redline option, since it's significantly faster by not having to render just one clip at a time and leaving 70% of my remaining CPU power idle. :P
 
Tom Lowe said:
Can we please add an ability to delete R3D files to Red Cine X?

If you are worried that people might accidentally delete clips, then make some kind of redundant system asking, "Do you REALLY want to enable delete R3d files?" "Really?"

:)
Click to expand...

I'd like an option in settings to enable/disable that with an option to password protect it also ;-)
 
Black QTs

Black QTs

Rendering 1/3 colored dots and 2/3 black QT on a macbook pro with 326 and now 321. Does anyone has a work around? Thanks. I need to render prores clips on the 3rd.
 
Cannot render QT??

Cannot render QT??

Anyone? Why my QTs are black with a stripe of colored dots on the top? I am using REDCINEX 326 and 321 on a macbook pro. With both I cannot get to render the QTs.
 
Could we please have a more structured bug-report system for Redcine-X. It's a pain to write to an e-mail and get random feedback and it's a pain to "yell" things out here and not knowing if problems are being addressed.
 
If I export a TIFF there is an Alpha channel in it.... also have problems with software only transcoding to MXF - black screen on mediacomposer...
 
There are several utilities and wikie-type systems to log and follow up with software debugging. Usually this is used internally (probably Red is using one) but if this is something you guys would consider we could implement one at the community/user level.
 
Panos Bournias said:
Anyone? Why my QTs are black with a stripe of colored dots on the top? I am using REDCINEX 326 and 321 on a macbook pro. With both I cannot get to render the QTs.
Click to expand...

Rainer Fritz said:
problems with software only transcoding to MXF - black screen on mediacomposer...
Click to expand...

Please send me an RCX log file from these issues to redcinex at red dot com. I need to know exactly what your settings are to recreate the issue here.
 
Everyone having problems opening a clip: Try to delete any existing RMD file in the clip folder and see if that works. That is fixing a lot of problems for me... typically when having synced an audiofile to the clip. Works (almost) perfectly in 262, though.
 
The quicktime audio export settings do not work (I'm using RedCine-X 261 in Windows 7 64 bit). No matter which codec or settings I choose, the audio ends up always coming out as uncompressed - "Integer (Big Endian)".

This is a bit of a disappointment, as otherwise RedCine-X would be incredible for quickly making quicktime rushes that can be burned as data onto DVD-Rs (instead, the resulting quicktime files have uncompressed audio which is about 20 times the size of the video track in terms of space).
 
Same problem here with impossibility to export to QuickTime (tried all kinds of settings). Output is always black. It's a real bummer because in my workflow there's no other way to profit from the look settings that RedCine-X would provide. Please make sure that this feature works with the next release! Pretty please!

Another problem is non-ASCII characters in file paths: export either crashes or doesn't do a thing (depending on export settings). Please make sure that all your string handling is Unicode safe.

Thanks!

(sorry for cross posting in the recon thread)
 
Is XML and EDL feature working on the latest Redcine X 321 ? Its quitting on me !
 
black QTs

black QTs

Suddenly the 321 and 261 work on the Qts for me. The 326 cannot, renders black only. Is there a workaround this issue?
Cheers
Panos
 
You must log in or register to reply here.
Back
Top