Markers in gray with RED .r3d files!

Similar Questions

• workaround for the slowdown in performance and the low resolution of the RED R3D files after effects CC 2014 (13.0)

  ml http://blogs.adobe.com/AfterEffects/2014/06/Red-R3D-Problems-After-Effects-CC-2014-13-0.HT

  The After Effects team are investigating a bug in after effects CC 2104 (13.0) when RED (.) R3D files) are very slow and the resolution of the images is poor, all sampling of 1/8.

  
  

  The following workaround solution was reported to solve problems in some cases:

  1. Save the project.
  2. Choose Edition > purge > all memory and disk cache.

  
  

  Please post in this thread on whether or not this work around has helped you.

  Performance issues and resolution with the RED (.r3d) files have been fixed in the CC of effects after update to 2014.1.1 (13.1.1).

  Details: http://bit.ly/AE_1311_details

• AE 2014CC RED R3D files support broken - footages looks bad, slow everything down.

  Just got an update, first is great, but AE is dead. Cannot yet open files RED-incredibly slow. 100 times slower than the old version. Must be a bug. I have TITAN GPU on classic MAC PRO Tower. AE2013 works very well - what's wrong with the news? And it actually looks like the format supported completely broken RED cause when I go to 100% images looks like 1/8 high-end resolution.

  Performance issues and the low resolution of the RED (.r3d) files are set in the After Effects 2014.1.1 (13.1.1) implemented to date. Please install it to solve these problems.

  Details on the update: http://bit.ly/AE_1311_details

  Under the hood, here's what happened:

  Late in development after effects CC 2014 (13.0), a change was introduced to how After Effects and Premiere Pro to cache data frame when the decoding of .r3d files. This change caused bugs in After Effects only, because of the requests of the frame in a slightly different way than Premiere Pro.

  The fault was not apparent when we inspected the code, and he made several unexpected failures.

  The first problem, .r3d files had low resolution, caused when After Effects generated a thumbnail of the file to the project Panel. The miniature request is for a very small image, about 320 x 180 pixels, and the small image dimensions have been incorrectly be reused when After Effects requested the full large images for composition. (Workarounds I had suggested earlier, to open the dialog box settings of RED or purge the cache, worked because they cause frame requests be reset).

  This bug has been fixed in after effects CC 20141 (13.1). After Effects now correctly Initializes the dimensions in the frame cache requests.

  The second problem was that for some but not all .r3d files, any request for less than 1/8 resolution frame would result in After Effects to stall (beach ball) for 15 seconds. This included when the file is imported and the thumbnail has been generated, or if the resolution composition control was set at less than 1/8, or, if the Adaptive resolution has been activated and allowed to table the resolution less than 1/8.

  Not all .r3d files encountered this problem. The affected files have been of the newest cameras and sensors, including the RED Epic camera and the detector of Dragon. Files of the older cameras like the RED One, did not have this problem.

  This problem was caused by an incompatibility of the proportions of the framework cache when requests for image low resolution. During the generation of the frame cache, the proportions of the image is calculated, but the proportions of the image low resolution that result may not match the aspect ratio of the original frame. This calculation is indeed correct; bypassing the new dimensions of the whole pixels, the proportions frame moves less than 1%. In problematic cases, this caused lag After Effects to assume that cache framework did not provide the backstory, and he could wait 15 seconds (a preset timeout clock) for a better match, what has not happened, and then it should be the frame anyway.

  This bug has been fixed in After Effects CC 2014.1.1 (13.1.1). Now, After Effects ignores the small variances expected in the proportions between the original frame and the image cache low resolution.

  These two fixes solve known issues with .r3d file decoding after effects CC 2014. We apologize once again, that have occurred these bugs, and personally, I apologize for being silent on this thread for so long; We were busy investigating and fixing these and other bugs.

• "Not supported" RED R3D files after project save

  All of a sudden yesterday my our cam RED R3D files are unusable / not supported after the project folder except. Opening and existing project and before you save the RED files work fine. Importation of RED is also "not supported" after you save the file updated the project. Closed the project to test the import in an empty project, still no dice. Restarted AE and still impossible to import. The only thing I have not yet tried restart and import into an empty project.

  The only way I could work with my pictures RED so is to open the project file that haven't had them imported before this problem and do not save. Once I have save unhandled errors appear. None of the RED image is corrupt.

  I am currently one of the clips to a direct connected drive away our SIN. I'll update soon.

  

  I use RED CS6 and CC without problem for many, many months (maybe years, I lose track of time in my cage)

  RED footage comes from a Mysterium EPIC and in a format, we used many times

  29.97, 5K (5120 x 2700), REDcode 5:1, not HDR, Firmware 3.2.21. (48926)

  After Effects 12.2.1.5

  Mac 5.1 running 10.8.5

  NVIDIA k5000

  Synology NAS (RED slow work, but reliable and cheap)

  Update: SOLVED

  Editing the file of MDM by adjusting settings look in the REDCINE - X Pro caused After Effects in the impossibility to use the media.

  Version 22.31200

  Version 30.33198 fixes the MDM problem.

• Experiences with RED R3D: CS5 and in general?

  I'll post my first spot with images of a RED One next week. I've only played with a few clips and not tried anything 'real' with her yet.

  The film is made in 4K 16 x 9, I think of 23.976. Final delivery will be 720/30 p for broadcasting/cablecasting. Fortunately, no sound synchronization worry in this one. I get the RED drive full of pictures tomorrow afternoon, so I'll have some time to play with the equipment.

  My system seems to be OK with clips of 4.5 K I tested. I kick down to 1/4 and 1/2 resolution break, and things reading seems catchy. My system is a i7-930 @ 4 GHz, 24GO RAM, GTX 480, 4-drive RAID 5 off the coast of the mobo that serves as my main drive of edition.

  I looking for general advice dealing with this material in general at the OS level, just in case where there are best practices and pitfalls to the extent of the CS5 is concerned. I am trying to determine what would be the best configuration of the sequence to be used; I want to use a preset matching RED, or by mail to my destination size/frame rate? My usual approach with my own 1080 p material (DVCPRO HD, primarily) is to change in a sequence of 1080 p full raster and then export them directly to 720 p to deliver. I think I'll take the same approach here, working at 4K and export to the final, but I'm open to suggestions. Work at a lower frame size would obviously give me sliding options.

  I can do a little light AE work on this; nothing too things I flip that quite quickly. I hope to make it a shine - the producer is terrified of RED (of course, he's the one who usually shoots 35mm and there telecine to miniDV), and if all goes well I'll have much more regular tasks to do like this... and I'll get to raise rates!

  Thanks in advance you seasoned REDitors

  Hey Colin,.

  I have worked extensively with R3D in PPSC5 and REDCINE-X.

  First note - don't bother with Cine-X... Now that CS5 (starting from 5.0.3) supports the new science of the color in the build 30, there is no need to use movie-X as an intermediary. According to my experience it is both very slow and also VERY unstable. If you start to do too much, it crashes. And this isn't just my system, word on the street, it's that Cine-X is unstable both on the PC and the Mac, period.

  Then, use PPro CS5 for everything you do with R3D.

  If you go to crop, then Yes, go ahead and edit in 720. There are RED presets for down in the lower ranges, too, so I would use a RED 720p30 preset in order to paste in the RED presets for editing. It may not make a difference, but I just watch is as best practices... Either paste elsewhere, in a "Preset" RED.

  Œuvres RED beautifully in PProCS5... I have a 920 with three disk RAID-0 and the GTX285 and I put it on the ground 1/4 and full of break and it works beautifully up to four layers. I haven't worked beyond four layers, but it was still good when I hit four.

  Note for you with the clip for the RED settings dialog box... You can save preset settings, then go in your first shot of a specific configuration, it get the way you like it and then create a preset for that. Then choose the rest of the clips in the tray under the angle of the shot and apply this preset. Repeat for different configurations of shooting required.

  Adobe has done a great job, building of support really fluid and flawless for RED and with the 5.0.3 release, they got support for the science of colours 30 build as well.

  R3D Edition has been a great experience for me...

• How can I link to R3D files when they are multiple (long resumes 4Gbs).

  Hello guys,.

  I'm transcoding (SOUL) my red images to the H.264 format for easy/fast mounting in another machine slow (the film's Director). But he comes to files with multiple R3D files, long takes over from 4Gbs, it creates several mp4 files, and they are all exactly the same.

  -Can I actually use an mp4 for my editing file and replace with originals later?

  -I should only transcode the first R3D file?

  -How can I connect back once the editing is done? Ive tried but do not know what R3D file should link to and does not after trying it. The mp4 file is take it all, but the R3D are not taking it together since they are separated in different R3D files.

  I work with first CC 2015.

  Thank you so much, I have spent days watching the tutorials but can't find my answer, I would greatly appreciate your help.

  I'd probably transcode to prores proxy, or something that does not have the long form, GOP, as Mp4.   Then, a test and make sure your guard to transcode the original code term when you bind again, there is no problem.

  do a test run w / a clip as not to lose time and when you do a couple of edits in a timeline w / as a clip, click with the right button on the clip in the project bin and select 'replace the clip', point to the original file then who must fill out your edited clip w / new source footage.

  you will then need to change the codec of your timeline should match that of your source.    hope that helps.    Certainly test first to make sure that you have the workflow down before you begin your session.

  This also works when there are tons of clips in your tray of sequences that need to be replace.

  When we work w / R3D files, usually created proxies on the fly for this reason (I think).   I'm sure that simply point to the first R3D file in this order if you make your own proxies, although I have not tested.   the first R3D file will usually connect automatic for the rest.

  This isn't the way we usually work but seems it should work.      Good luck.

• Back to the first, Final Cut. Help editing native RED r3d

  I am one of the many new converts to first Pro CS5.5 of Final Cut after many years using the Apple software. I want to dive into the heart and start editing with Premiere, but I meet an immediate obstacle.

  First, I heard the discussion without end on ability Premiere Pro to edit RED raw images natively. Simply drag the files r3d and go. Yet, I could not even get the first get me this far in my editing workflow. I've been working with RED images, and in the past, I've been transcoding in Final Cut Pro Res (Proxy) and compliance/online to the end, using newspapers and transfer or RED alert. Naturally, I was very happy to be able to drop them into native files of RED and never have to online to the end. Here comes my problem: I drag in a recent session r3d files. 4 k 23,967 suddenly on RED. I double click the clip in my project to open it in the monitor source and all I get is black. I can't rub, I can't playback video or audio to make my cuts; all I get is timecode. HOWEVER, if I drag the file r3d directly in the timeline, I get image / its and all. Of course, it is not possible to change and I can't just be filing lots of clips in the sequence and try from there. Like any editor, I want power double click my clip, rub through it in the source monitor and find the particular plug, I want to use. THEN I add to my calendar.
  
  WHY am I not able to view/edit r3d believed in my monitor source files? Everyone knows about this problem? Frustrated and unable to start using this first highly touted (who all my heart, I want to believe in). Please ask me if I can get running with my RED images. In the meantime, it's to Final Cut 7...

  I should mention that I use a Quad-Core Intel Xeon 2.4 GHz Mac Pro with 15 GM of Ram and an ATI Radeon HD 5770 graphics card. I've heard talk about NVIDIA is the way to go, but we're not the upgrade/change cards in the immediate future. For now, it is what I use. I hope this isn't the only reason that I can not read/see anything in my monitor source with my r3d files.

  
  Thank you

  
  Daniel

  OK, the Blackmagic card and its drivers would have been a first mention, simply because this can change how things are set up in Premiere Pro.

  Just to clarify: you see anything in the Source monitor? It seems that your ProRes clips worked there...?

  In Premiere Pro preferences, go to player settings and check what drive module that you use (should be Adobe Player or BMD one); try changing it and see if something changes in the SM.

• Problems with CUDA acceleration and playback of sequences of RED R3D

  I came across several errors and crashes on my PC last night while trying to open the first. So, I decided to reformat my PC and reinstall all the drivers and what not. Now when I try to read the raw R3D files in Premiere Pro to use CUDA acceleration, all video files are just black. It simply does not appears in the window preview or the playback of the source window. Non-ROUGE images works fine and when I go to only software acceleration, RED cheek images very well as well. Advice as to why this is happening? I've updated all my drivers and made a few uninstall / reinstall.

  I work with a Titan GTX, RED Rocket-X, 2 Intel Core Xeon (12) processors, 128 GB ram.

  Thank you!

  I have the same problem.

  If you order acceleration of OpenCL, you'll be able to read and make, but it's very bad performance.

  Word on the street is it of the xx 368 nvidia driver. do, I have not yet tried to install an older one, but I thought it should work

• RED. R3D files are not supported in After Effects?

  When I try to import R3D files seem to be disabled in all supported formats.

  Also when I create a composition in After Effects from Adobe Premiere, he seems to be offline.

  Whats Happening?

  

  This bug is fixed in the update after effects CC 2015 (13.7.2): http://adobe.ly/1WaV0pP

  This only bug fixes Update corrections occurred after effects CC 2015 (13.7.1) on Mac OS x files: RED (.r3d) can still be imported and are not reported as missing in existing projects.

  This update is only for Mac OS X and is not available for Windows, because the bug with the RED files does not occur under Windows. The most recent update for After Effects on Windows is after effects CC 2015 (13.7.1).

• Gray screen flashes a file with? and a file with an icon.

  Gray screen flashes a file with? and a file with an icon.

  Click here and follow the instructions. If you get to the third series of steps, insert a Mac OS X installation disc.

  
  (136937)

• Icon "Are the selected markers to separate the export audio files" is grayed out outside in the markers window. The titles show starts but no end of times, and yet time is calculated.

  I have a large wav file to finish securities as a mixer and inserted the CD markers where I want the marked pistes. Icon "Are the selected markers to separate the export audio files" is grayed out outside in the markers window. The titles show starts but no end of times, and yet time is calculated. Why can't I export those items marked as separate files?

  You must make the markers of track in regions for the Export of work function. Make sure that you have placed a marker at the end of the file, as well as at the beginning of each track. Then select all the markers in the marker list by left clicking the first then shift left click on the last. You can then merge markers in the channels using the comb as icon (3rd from left) at the top of the list of markers. You will then be able to export the lines marked as separate files.

• Keyframing motion with .r3d files

  Hi, I have a strange problem in first work with the newest Dragon .r3d files to 5 k. I work with the most recent CC 2014 first.

  I want to set the framing in a sequence of 1080 p, where I must keyframe motion effects. But every time I have to add a bunch of key frames in succession each to perfectly fit a Dolly, it loses some of the query previously retouching in the same clip. The numbers in the effects still change, but it does not appear on the actual video.

  It is a very annoying problem that I fight with.

  If someone knows a solution to this, please let me know. Without nesting or convert the files to a different format, I need the RAW capabilities for the year.

  Thank you

  Dan

  Too bad. I thought about it. For future reference: this was caused by what is a clip of 50 frames per second. I had used the time-remapping to bump it up to 200% to get a 'normal' speed This is what caused my problems. Making the speed of rise in speed/duration by right clicking worked in association with the movement.

• As prelude does not work with red images, how can I add logging information to a file in Premiere Pro

  As prelude does not work with red images, how can I add logging information to a file in Premiere Pro CS6?

  RED footage has a restriction on the metadata.  We are looking into what it would take to get the metadata full support in our system, but you cannot mark red footage at this time.

• AE CC 2015.2 r3d files import does not (error: no file found at...)

  Hello!

  Import R3D footage in after effects CC 2015.2 does not work. It does not work in Premiere Pro CC 2015.

  Operating system is Yosemite (10.10.5). It also does not work when opening projects that were imported from r3d footage.

  Any help would be great!

  Thanks in advance.

  This bug is fixed in the update after effects CC 2015 (13.7.2): http://adobe.ly/1WaV0pP

  This only bug fixes Update corrections occurred after effects CC 2015 (13.7.1) on Mac OS x files: RED (.r3d) can still be imported and are not reported as missing in existing projects.

  This update is only for Mac OS X and is not available for Windows, because the bug with the RED files does not occur under Windows. The most recent update for After Effects on Windows is after effects CC 2015 (13.7.1).

• R3D files is no longer working or import into After Effects, after update.

  Just updated to the latest After Effects go about 30 min. All my. R3D files went offline. I can import them isn't over either. They worked with all versions up to this update.

  I reinstalled all the latest red codecs just to be sure. Can someone please check on that?

  Thank you

  John

  This bug is fixed in the update after effects CC 2015 (13.7.2): http://adobe.ly/1WaV0pP

  This only bug fixes Update corrections occurred after effects CC 2015 (13.7.1) on Mac OS x files: RED (.r3d) can still be imported and are not reported as missing in existing projects.

  This update is only for Mac OS X and is not available for Windows, because the bug with the RED files does not occur under Windows. The most recent update for After Effects on Windows is after effects CC 2015 (13.7.1).