Welcome to our community

Be a part of something great, join today!

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

REDCINE-X Build 348...

OK found the snapshot problem. RCX preferences were not retained (obviously) with the new version. The cropping issue remains though....
 
Hi Peter,

Can you please send me your framing settings? You can find them in the following location:


/Users/{You User Name}/Library/Application Support/red/RedCineX/Framings

Send to redcinex at red dot com.

Thanks!
David
 
Things really seem to be coming along with the 300 build series. I'm really appreciating the improvements, thanks guys.

I can report that it is now playing nice with spaces on my system. Before if you had RCX active and switched spaces (I did this using hot corners) then RCX minus the background workspace window would pop up over the top of everything else in whichever space you had moved into. Previously the only way to avoid this was by making sure that RCX was not the active app before switching. It all works fine now though.

Looks now get included when using the use RedLine option on export but you have to remember to uninstall previous versions first.


A few bug reports to help keep things moving along..

I'm also seeing the metadata window endless spawning problem reported by others & can send a log file if needed.

When rendering a batch job (any more than one clip in the list) RCX goes through the whole rendering process at usual speed and eventually reports completion on all clips but no rendered clips are written to disk except a small unplayable .mov for the first clip. This is with QT ProRes export using the RedLine option.

Also when using RedLine audio tracks are not included even though set to be and the same clip with externally synced audio outputs fine with the audio embedded if not using the Use REDline option.



... and a short wish list (for once the bugs are fixed)

Audio when exported with a clip seems to default to 32bit Integer (Big Endian)even though the source is 24 bit Integer (little Endian). 32 Bit Integer when paired with ProRes in FCP seems to need rendering to playback no matter what sequence settings I use, causing a pain in the butt when editing and partially defeating the point of transcoding the footage for editing fluidity. Please add an option to output at a lower bitrate or with different settings so it can playback nice in FCP & elsewhere.

I really love the CSV metadata export function - or at least the idea of it doing what I hoped it would do -export all the metadata I entered in the list fields. Currently it only exports the data that used to appear in the metadata window (now more fields like Scene, Take etc appear there which is nice) I would love to have it export all this in the CSV then I would be able to log shots in RCX, have the data travel with the files in the RMD's and export a CSV to put on a spreadsheet or in a database at handover time. Currently I have to enter the data twice which is a pain in the butt. Sometimes there isn't time to do it in RCX as well as on the spreadsheet and I really like it to be there in the RMD's although currently not much other than RCX reads those fields I'm sure they could be very useful in the future.

It would also be great to see the RedCode setting a clip was recorded at and if varispeed was used and the varispeed framerate shot at in the list view and metadata window.

I'm currently testing the various Redline rendering options to find the best settings to use on my system, tests like this would be helped tremendously if the batch monitor had a column reporting the time taken for a each clip rendered (allowing starting and stopping if the render job is paused for a while). A further column with the export preset name would be handy too, then I could send a list of jobs using different presets and leave them rendering whilst I'm away from the computer and come back and compare how long each setting took.

Autosave RMD seems to now create a hell of a mess of .bak versions of the RMD in the clip folder. perhaps these could be put in a subfolder for tidyness sake and an option to delete them be added within RCX?




Phew. That enough for you in one go?

I will try and post things as I find them rather than a big splurge all at once if possible from now on.

Let me know if you want log files for any of the above.
 
I love how you can have a problem, one week later it's gone! Awesome!
 
Okay so I can get my look applied when using a computer that didn't have RedLine installed before and using the Use REdline render option but not on my MBP which had Redline installed before.
I know I need to uninstall it somehow but have lost the thread where instructions were given for doing so, can't find it for a lot of searching, can anyone point me in the right direction?
 
Quentin_B said:
Okay so I can get my look applied when using a computer that didn't have RedLine installed before and using the Use REdline render option but not on my MBP which had Redline installed before.
I know I need to uninstall it somehow but have lost the thread where instructions were given for doing so, can't find it for a lot of searching, can anyone point me in the right direction?
Click to expand...

In the recent REDcineX builds REDline is within the REDcineX application package. When you choose "install REDline" from the help menu, it adds a shortcut to /usr/sbin, which I imagine you remove to un-install.
 
I cant get edl or xml import working. Redcine-x just crashes when I put orginal r3d data location to root of my all material of project and load xml. Is there limitation in projects lenght or ammount of clip? When Im trying to load edl program gives file importer parse error "file importer error: invalid edit number at line 5067".
 
Quentin_B said:
I'm also seeing the metadata window endless spawning problem reported by others & can send a log file if needed.

Also when using RedLine audio tracks are not included even though set to be and the same clip with externally synced audio outputs fine with the audio embedded if not using the Use REDline option.
Click to expand...
These issues will be fixed in the next build. Thank you for reporting them.

Quentin_B said:
When rendering a batch job (any more than one clip in the list) RCX goes through the whole rendering process at usual speed and eventually reports completion on all clips but no rendered clips are written to disk except a small unplayable .mov for the first clip. This is with QT ProRes export using the RedLine option.
Click to expand...
Could you send log files for this particular issue to redcinex at red dot com?
 
Reproducible Bug: RCX B348 Avid MXF audio Export Broken :-(

Reproducible Bug: RCX B348 Avid MXF audio Export Broken :-(

Just discovered this bug with in camera audio. Reproducible on two different machines and on 32bit and 64bit versions of RCX b348.

We are recording audio onto channels 1 and 2 on the RED one b30. I can hear the audio in RCX and can hear the audio in exported QT prores files. Unfortunately processed Avid MXF files are mute (pictures look fine) once relinked in Media Composer v5.0.3 even though the audio files exist.

If I process Avid MXF in RCX b321 audio relinks fine in MCv5.0.3.

Please can someone verify they see this problem. Also can they confirm they have success conforming b321 processed Avid files back to R3D for grading.

Looks like I will have to reprocess todays footage with b321.
 
Nick Shaw said:
In the recent REDcineX builds REDline is within the REDcineX application package. When you choose "install REDline" from the help menu, it adds a shortcut to /usr/sbin, which I imagine you remove to un-install.
Click to expand...

I think the installed REDline was build 256 which ran a proper installer rather than just putting in a link. I tried installing the new one over the top using the Install RedLine option in the help menu but it has not changed anything. I need to find out how to get at & remove the old RedLine me thinks. Thanks for trying to help.
 
Grant Yoshida said:
Could you send log files for this particular issue to redcinex at red dot com?
Click to expand...
Great news on the forthcoming bug fixes.

Will try and recreate this then send logs but I'm in the middle of a big batch render right now.

One other bug I noticed is that when I change debayer settings in the viewer with center crop enabled it changes to the framing control to custom crop & moves my crop region to the top of frame.


Also another nice new timesaver feature would be a batch/ multiselect in bin function to reset all in & out points to original so that if I've set in & outs to demonstrate how some clips cut I can quickly remove them from all clips prior to transcoding proxies (which need to be full clip length for later reconfirms to work).
 
Last edited:
Quentin_B said:
need to find out how to get at & remove the old RedLine me thinks
Click to expand...

The old version is just a file (or a couple of files depending on version) in /user/sbin. You should be able to just go there (use "go to folder" in Finder) and remove it.
 
Grant Yoshida said:
These issues will be fixed in the next build. Thank you for reporting them.


Could you send log files for this particular issue to redcinex at red dot com?
Click to expand...

I just tried but it was a big batch render with RedCineX running for days and my mail program won't let me upload the 88MB log file!

I will have to try a small sample again using the export using Redline option next week and post you the file from that.

One thing I have discovered is that some of the files are being saved when I thought they weren't, just all in one place, usually the in folder belonging to the last clip in the batch list though this changes if I add more clips to the batch list later. I have Output Location set to Output with Clip Filename to Clip Folder. Almost all except the first few clips in the batch render out ok but they do so all to one folder. It seems to be the first few that produce bad truncated .mov clips and these are the ones that it says it's processing in parallel whilst later it shows it's working on the clips one by one.
 
Quentin_B said:
T
When rendering a batch job (any more than one clip in the list) RCX goes through the whole rendering process at usual speed and eventually reports completion on all clips but no rendered clips are written to disk except a small unplayable .mov for the first clip. This is with QT ProRes export using the RedLine option.
Click to expand...

Quentin,

Thanks for the report.

The problem seems to be exporting the same clip to Quicktime via multiple simultaneous REDLine's. What you have is possibly multiple REDLine's trying to write to same filename on disk at exactly the same time, and Quicktime does not like this. Unfortunately there is no quick or easy solution to this, but we are working on one.

In the mean time you can:

1. Use only one REDLine at a time.
2. Ensure that you do not have the same clip exporting within the same batch of currently running REDLines.
3. If you do need the same clip, use two different export preset's, for which you can uniquely name the output file.

David
 
any chance we will get ipad friendly export settings? I've been getting asked for ipad dailies pretty often, would love to harness the power of the red rocket to make them.
 
You must log in or register to reply here.
Back
Top