RED Anamorphic playback

I'm wondering if there's a way for FCPX to recognize and properly playback RED Epic footage shot anamorphically. I know I can always transform/distort clips in the timeline, but it'd awesome if they automatically displayed in the proper aspect ratio.
I noticed there's a metadata field for "RED clip aspect ratio" and "RED pixel aspect ratio" etc, so it seems all the info is there but it still plays back squeezed.
Anyone have ideas on this? If not I'm hoping Apple will fix this in the next version.

Thanks Paul, but I'd like this to work with the native r3d files. So QT Edit won't help there, although maybe it'd work with the QT proxies.
It's really not a big issue, it's just that the workflow is so close to perfect and the auto-desqueeze seems like something FCPX can handle.

Similar Messages

Red/Green Playback Monitor

I asked this question in the CS5 forum yesterday and while a lot of people read it, there were no ideas presented. I don't know if this problem might be related to hardware, so I will try here.
I have just upgraded from CS4 to CS5. I also just purchased a new Sony NEX-VG10. I'm finding with the new camera that I occasionally get a clip that will not play properly in the monitor and it displays a solid green or red screen. Sometime a clip with this problem will play the associated audio, others will not. But I have found that it is very consistent in how each bad clip plays. In other words the same clip will always display the same symptoms.
In a few cases a clip of say 30 seconds duration may play for 5-10 seconds normally, then it goes to red screen with no audio. If I edit out the bad part and keep the rest, there is no indication during playback that there was ever a problem with the remaining portion of the original clip. But nothing I have tried will work to save the bad portion of the clip.
These are AVCHD files with .m2ts file extension. I've tried a test project with some older .mts files shot on a Cannon and I'm not finding any of the green or red screen problems. And I don't recall ever seeing that problem with CS4 either. When I place 10 clips into the same sequence on the timeline there will be a solid yellow render bar, including above the bad clips. I can tell right away which clips are bad because the thumbnail picture at the start of the clip will be solid red rather than showing the first frame. I've tried rendering the timeline but that makes no difference. I have tried opening just the bad clip in a new project and get the same result. I've tried dragging the questionable clip into the New Item folder in the project area in order to open a new sequence that is assured to match the clip properties, but no joy.
If anyone has any ideas for what I might try to reveal the root cause of this problem I would really appreciate hearing them. Could this possibly be a memory card problem?? When I play the video back in the camea all the clips play fine. Perhaps something is being corrupted in the process of getting the video onto the computer?? I have found these bad clips in files there were moved to the computer via USB cable using software that came with the camera, and also by inserting the memory card into a USB slot on the computer for direct copy to the HDD.
Thanks

When I use the software that came with the camera to copy files from the memory card it will automatically place all the metadata files in the same folder as the video files. Of course, when I choose to import those files into PPRO the import dialog box only shows me the video files, so I'm not sure what PPRO does with the metadata??
When I remove the memory card from the camera and plug it into the card reader on the computer then when I open the folder I can only see the video files to copy. No metadata.
I've tried importing files that have been saved both ways and both have had the problem, so apparently it's not related to the presence of the metadata files. Although, this is the first I've read about the need for those files to be present and I will take that under advisement with future projects.
Plus, it's not ALL of the clips in a project that end up with this problem. So far it appears to be random, although I haven't seen it enough yet to be real scientific about keeping exact track of which clips, clip duration, etc. to see if I can find a constant.
All I know for sure right now is that every clip plays perfect when previewed in the camera and not so much by the time it gets into PPRO. I'm thinking perhaps some corruption in the process of getting the files from the camera to the HDD?? But how/why?? Something happening in the computer during the file transfer that bothers the clip being transferred at the time??
Very strange........

RED footage playback / paused resolution

Hey there,
Here's the situation: I have my playback and paused resolution set at 1/16 in order to work comfortably with RED footage. It works perfectly.
However, when I drag a clip in the timeline, and go near another clip, the PROGRAM window converts into a 2-screened edit-type display. And in this mode, the resolution pumps up to FULL res, making the program slow, and hampering all that nice flow that low resolution affords.
Is this a bug, or have I forgotten to click something somewhere?
Thanks!

I'm not seeing that here. With all the media I have, it stays at the resolution where I put it. I do not have any RED media for testing, though.

Red Rocket playback issues using transitions

Hi,
the title says it all.
Playback is smooth when I use the Red Rocket with Full Res. though when I use any kind of transition on the clips, playback stutters and is no longer in realtime.
When I deactivate the Rocket and just use my 4GB 670GTX at half res I've no problems.
I'm using CS6 and wonder if this problem is still in CC.
If this problem stays with CC I'm thinking of selling the rocket and invest in some better GrapicCard like the Titan.
System is:
Core i7
16BG RAM
OS on SSD
RAID 0 for Data
Nvidia 670GTX 4GB RAM
Regards
Manfred

First question is what dedicated internal SATA media drive you are playing the footage from?
Also, still pretty windy in Spokane.

Anamorphic playback on a consumer monitor?

I'm cutting a video from a hotel room and will not have access to a professional client monitor. The footage is all 16:9 anamorphic. Is there a way to set the playback from my anamorphic sequence to squeeze the footage into a letter-boxed format on the consumer monitor? My final deliverable will be anamorphic so I would rather not squeeze all the footage in my timeline. I'm getting my playback footage to the monitor via an AJA Io LA. Thanks.

Or just use the FCP canvas. It's rare to need an external monitor for a quick offline edit, which is what I'd imagine you're doing on the road?
PS Are there still 4:3 monitors in use in the USofA? Can't remember the last time I saw one this side of the water (except maybe in grandma's house)
Message was edited by: Denis Murphy

Canvas flashes red on playback, resart needed

has anyone else encountered the following FCP bug since the last round of apple updates:
FCP works fine for hours then every playback n the canvas flashes red; as if there is a frame of video then a frame of pure red, then a frame of video etc. It's red strobing effect. I need to restart my mac to get the problem to disappear.
Is this a known issue?
It's only happened since I last updated the OS, pro apps etc
thanks

I just had this issue too.. and solved it.
red flashes with jpeg-codec.mov / prores422.mov and I'm running a bunch of apps and have nvidia card.
I realised that I was playing a youtube video in the background through safari.
When it stopped, which was the only change I made, the flashes went...
THEREFORE.. the problem was that there is not enough memory/power/whatever is needed to refresh the fcp canvas at a suitable framerate so it was lowered automatically to suit the memory - red possibly just being a default colour to warn.
simples.

Editing 4k RED files in CS6, does SLI help in playback and editing? (GeForce GTX-760 vcard)

I just bought a GeForce GTX-760 card and noticed great improvements to video playback over my old card.
I want to start editing RED 4k files and be able to play them back in 4k, currently I can achieve smooth playback in 1/2 resolution, but thought if I bought a 2nd card and used the SLI I'd be able to get 4k to playback on my system... would this work?
I've been doing searches for this, but can't find much on using SLI in Premiere CS6...
Short of getting a RED Rocket, how could I achieve smooth RED 4k playback and editing in CS6?
Thanks all!
Aza

WIth CS6 you are limited to ONE video card.
With CC, SLI does not help. See Tweakers Page - What video card to use?
A second video card can help marginally with CC only, but the one thing that really helps is more cores, more L3 cache and higher clock speed.
See Tweakers Page - Exporting Style

My apple tv stalls during playback. How can I fix this?

My Apple TV stalls during playback. I am hooked up through ethernet so I'm certain that it is not a network issue. What happens is that after a few minutes of normal playback the movie that I'm watching simply stalls. It looks like AppleTV is trying to reboot it. if I rewind it briefly and restart the movie by pushing play it seems to be fine. But it it stalls again after a few minutes. I have to do this very often and it becomes quite distracting when you're trying to watch a show.
One thing I have noticed is that if I pause the program before it stalls and leave it for about 15 minutes I can watch a large portion of the show uninterrupted.
The files are in my iTunes library. I don't seem to have this issue if I'm playing the files from my iPad via AirPlay. I have restarted, reset, and rebooted AppleTV several times and it still keeps doing it. Any suggestions out there?

640 x 480
Widescreen 16:9
These settings are contradictory. Please post a screen capture image of the QT "Inspector" window to confirm what encode matrix setting, PAR display setting, and Scale display settings are actually embedded in your file. Also please confirm whether or not the source material was widescreen and it is 4:3 aspect you wish to correct at this point. If not, then please state the height at which the transcoded file was encoded and the target aspect ratio at which you want files to play in all media players.
Once compressed it plays back in Windows Media Player as 16:9 video.
When played back with Quicktime it is squished into a 4:3 format.
Different players dispay content aspect differently.
Why is this happening and how can I fix it?
QT 7, for instance, displays the file using specific Scale dimensions and if these dimensions are not equivalent to PAR/anamorphic playback settings, then the file can display differently in differently media players. As to fixing the problem, that depends on which setting you are trying to fix and what platform/software is available.

Why when done rendering do my clips turn fully red?

I just started using mts files. When I render clips with fast color corrector and color balance they turn fully red in playback, and I can no longer preview them, even paused. What the hell...

Jim's suggestion is also the first thing that I recommend, when there is a display issue. Even if it is not the cause, getting it out of the way first, is a good move - PrPro interfaces very heavily with the video driver.
Follow Jim's suggestion to go to the mfgr's. Web site, and do not trust your OS to tell you if you have the latest - check for yourself.
BTW - what OS are you running, and what is the make and model of your video card?
Good luck,
Hunt

Where is the grey bar? I see the red bar only.

Hi friends,
Vista32 sp2, FF 3.6.21, flash 10.3.183.7.
Today I did update Firefox from 3.6.20 to 3.6.21 (a normal update, I make this since years ;): at this point and for the first time since two years I see an odd thing that happens:
Youtube: I see the red bar (playback bar), ok, but after upgrading I dont see the grey bar (video loading bar) ever!
How to do to get the grey bar working again, so as it did work until yesterday? very strange.
thanks a lot in advance. best regards.

without the grey bar :-(
and now with the grey bar (as it appeared over the years until yesterday :-)

What's New and What's Fixed in 2014.1

First, here are links to the two main documents about new features in the 2014.1 release:
Product Manager Al Mooney's blog: Premiere Pro CC 2014.1 Release
The What's New page in the Help: Adobe Premiere Pro Help | New features summary
(I'll review both of those documents ASAP to see if any little goodies got skipped.)
And now, the bugs that were fixed in this release:
Import
Import of CinemaDNG clip fails if the file has been renamed.
Gamma shift in some re-imported QuickTime IMX clips
Some QuickTime Reference files import without timecode.
Indexing of XDCAM clips can take an excessively long time, footage shows Media Pending until indexing completes.
XAVC-S files import without Timecode
Unable to import certain XDCAMHD 422 Long-GOP clips with Pixel Aspect Ratio of 0.7500 MXF
Spanned XDCAM HD422 clips not handled correctly if the clip names do not follow the normal convention
When a sequence is loaded from Media Browser to the Source Monitor and then inserted to a sequence without explicitly importing, two copies of the sequence are added to project.
Scaling values are not properly handled for clips/sequences imported via an XML file written by some shot management and conforming programs
If the reported duration of an XDCAM HD MXF clip shorter than the actual length in the file, then frames outside the stated duration can be accessed.
Some XAVC and XDCAM-IMX-MXF clips have audio noise introduced on playback
Some .mp4 have green frames and 'static' garbage when played in Source Monitor
Canon XF300 Footage has unacceptable performance for playback
.mp4 clips generated by certain transcoding programs exhibit poor playback performance
PPro no longer recognizes timecode from a .qtc file, referenced from within a QuickTime reference movie.
Some XDCAM422 clips fail to import with generic error
Occasional crash on opening Source Settings for DNG footage, with 2nd monitor enabled
Overexposed white areas in some CinemaDNG footage display magenta artifacts.
When scrubbing C300 clips in Project panel’s Icon view, red frames sometimes show and Event panel reports error decoding frame.
If SpeedGrade was installed before Premiere, then double-clicking a prproj file launches SpeedGrade (Mac Only)
Growing Files
The last frames of some growing file are green. Must relaunch Premiere to correct the problem.
Importing a growing file can take an exceedingly long time, with footage showing as Media Pending
When a growing file refreshes, it stops voiceover recording
The incorrect timecode is shown in the Timecode Panel for growing files.
Timeline playback of growing files drops audio for about 1 second each time the growing file refreshes.
QuickTime reference files for growing files fail to import.
Export
When source is 120fps, export fails if Match Sequence Settings enabled
The Advanced XDCAM Settings section in Export Settings is blank for imported XDCAM presets
In QuickTime encodes, audio exported as uncompressed stereo imports into FCP as dual mono.
When you export to 5.1 AAC with the “Import into Project” option enabled, the resulting clip fails to import, throwing
“File import failure”
Image flicker is introduced in some constant-bitrate MPEG2 encodes
When the only variable blocking smart rendering is an adjustment layer, the effect(s) thereon are ignored and the segment is smart rendered.
ProRes media encoded by Premiere causes are not compatible with certain video QC programs.
AAF export: 88.2kHz and 96kHz audio clips exported to AAF do not appear in some audio production programs.
Audio EDL gets wrong source timecode if clip is nested or part of a multicam source sequence
EDL does not give correct Source In and Out for clips with speed reversed.
EDL does not give correct source in and out on reversed clips.
OMF export fails with some multicam sequences, reporting Audio Export Failure.
Hang during OMF export when the sequence contains a 5.1 audio track/clip.
Smart rendering can introduce black and red frames
Playback
Playback of IMX 50 clip freezes after 12 seconds.
With XDCAMHD and DVCProHD footage, frames are sometimes dropped though the render bar is green.
Audio for some mp4 files plays back at double speed
When pre-roll is set to 1 frame, timecode and video of XDCAM .mxf files are out of sync
Some DNxHD do not decode properly, resulting in frames being played out of order
Performance of playback for some QuickTime is poor because they are unnecessarily falling back to QT32
Dropped frames when playing R3D clips with RocketX enabled and Playback Resolution at ¼
Audio
With Maintain Pitch enabled, no audio when playing at slower than real-time
Solo buttons in Audio Meters do not work for clips loaded into the Source Monitor
Mono and Standard track puck and tray panner routing for Ls, Rs, C and LFE channels do not adhere to ITU-R BR.1384 standard.
Occasional crash on switching a clip from mono to stereo via Modify>Audio Channels
5.1 channels are not properly mapped for some Dolby content.
5.1 clip changes to a 6 mono channel clip when “Extract Audio” or “Edit in Adobe Audition>Clip” is performed on a project item or track item.
Changes to Frame Rate via Interpret Footage are sometimes not applied to saved for all audio streams, causing most audio channels to be out of sync after closing/reloading project.
Constant Power audio transitions introduce buzz if either track item has zero channels (generally limited to multicam clips)
Crash on applying changes in Modify Audio Channels dialog [Mac Only]
Project Panel
Sorting by Duration is broken if the column has been moved during the current session
If the Project panel is filtered via Rapid Find when a bin is created, the edit control for naming the new bin does not become active automatically, and it cannot be activated manually until Rapid Find is cleared.
Project items cannot be deleted or renamed if the list view is scrolled to the right.
Project panel does not autoscroll to the left when a column is dragged to the right side of the Name column
When a timecode value is typed in the Video Out control for a clip in the Project panel, the value gets reduced by 2 frames upon committing the change
Subclip
When a soft subclip with only an Out Point set is edited into a sequence, the Subclip Start is ignored; the resulting track item extends all the way to Media Start.
The Media Start/End and Subclip Start/End times for subclips from a merged clip are incorrect
Editing/Timeline
3-Point edit: If the source is a sequence and only an Out Point is set for the source, the wrong segment gets inserted when KEM Roll is set to Insert as Individual Clips
Keyboard trim commands do not affect clips on targeted tracks that are outside of visible area of in the Timeline
Switching between sequences can turn the render bar red.
Frame Hold option doesn't generate the freeze frame when speed change is in effect
In the Timeline, the FX badge gets hidden when the clip is not wide enough to show the full clip name.
If the Left/Right Balance control is displayed in Timeline header, the balance will change if the mouse strays over the Header region during click-and-drag operations in the Timeline (such as trimming out)
'Select In to Out' selects clips on locked tracks.
Multicam
If time-remapping is used on a Multicam Source Sequence, the Program Monitor's multicam view continues to play at 100%; if source sequence was slowed, the Composite view goes black after the original end point.
When a multicam source sequence has been slowed down via speed change or time remapping, the extended of the clip goes black—no video
If the audio in a multicam sequence is selected when it is flattened, the audio is sometimes deleted.
Disabled multicam source clips are sometimes rendered to the composite output
The camera can be changed for a multicam clip on a locked track.
The overlay displays timecode in audio time units for part of a multicam sequence if the source clips are stereo and the MC sequence is mapped to mono
If a nested multicam sequence's duration has been increased via Time Remapping, then upon reaching the original end point during an editing pass, the composite view restarts from beginning
Flattening
If a multicam sequence’s audio is 5.1 or adaptive, then flattening deletes the audio.
Crash on flattening multicam clip with keyframed scale when using a camera angle that does not start at time zero.
Flattening multicam can remove some audio clips from the sequence.
Flattening a multicam sequence with reverse speed applied results in incorrect frames being used
Effects
AE Text Template] When text fields are active for editing, they’re not being visually highlighted
Adding mask points very close to each can result in the ordering of the points being incorrect
Incorrect scaling of 1920x1080 adjustment layers in 720 sequences
Unexpected behavior with Cross Dissolves between Adjustments Layers.
Applying both Echo & Levels effects to an adjustment layer causes video playback to freeze
Crash on rendering previews for a Lumetri filter in Software-Only mode.
Crash on deleting a clip from a sequence after pasting an effect mask to the clip.
JPG frame sequence gets scaled down if an adjustment layers is in effect above it [OpenCL only]
Rename GoPro lens distortion presets to include the camera name
Clip name effect doesn't work correctly if Source Track is set to a different track.
Crash on using Clip effect or Timecode effect on a transparent video.
Crash on loading or applying VST Effects (Mac only)
Intermittent Crash with Warp Stabilizer applied (AEVideoFilter)
The Clip Name effect does not work when applied to a transparent video track item, with Source Track set to a video clip.
Crash on applying audio transition to clips with overlapping timecode
Previewing fails when an adjustment layer has an animated mask applied to Opacity and any other video effect.
In Software-Only mode, rendering previews of the new Cross Dissolve is slower than the old one.
Masking and Tracking
Shift-dragging a control point for an effect mask sometimes yields unexpected results
If a clip has an effect with a mask applied, moving the clip in the Timeline cause rendered preview files to be lost.
Previews rendered to a P2 codec are incorrect for the first 10-30 frames of an Opacity effect with mask applied
If a mask is applied to a GPU accelerated effect on an adjustment layer, the Program Monitor shows a cropped frame with Playback Resolution at Half and goes completely black at Quarter.
Opacity effect on Adjustment Layers fails to render within the mask with tracking.
After rendering an adjustment layer with multiple effects with masks applied, some of the effects are no longer confined within the mask [Mac only]
Crash on opening some projects with masking and tracking applied to effects
Direct Manipulation control fails to switch between multiple masks that are applied to the Opacity intrinsic effect.
3rd Party
Certain audio filters cannot be applied to a clip in a sequence that is imported via XML
PPro reports audio filter missing when opening a saved project with certain audio filters applied to the clips in a sequence that was imported via XML
Artifacts are introduced when using certain 3rd party transitions.
Certain 3rd party stabilizer plug-in are not working
Markers
On mouse-up after adjusting the Out point of a marker with duration, the playhead jumps to the marker's In point.
Video in Program Monitor strobes when dragging the In or Out point of a sequence marker
GPU
With GPU acceleration enabled, Gamma is being applied to some RAW media when it shouldn’t be.
Basic 3D effect can result in Program Monitor’s video overlay to become corrupted on some GPUs
Performance (Note: Most of these fixes are also listed under a product area)
Locking all Audio Tracks can significantly impair performance.
Performance of playback for some QuickTime is poor because they are unnecessarily falling back to QT32
Dropped frames when playing R3D clips with RocketX enabled and Playback Resolution at ¼
Navigating through projects in multiple Media Browser panels impairs performance and can culminate in a crash
In Software-Only mode, rendering previews of the new Cross Dissolve is slower than the old one.
Canon XF300 Footage has unacceptable performance for playback
.mp4 clips generated by certain transcoding programs exhibit poor playback performance
Interop
Crash on selecting Edit>Edit in Adobe Audition>Sequence...
When a 5.1 clip is sent to Audition via Edit Clip In Adobe Audition, the first channel is used for all channels.
Exporting from Audition to Premiere Pro opens Premiere, but the file fails to import
After grading a sequence in SpeedGrade, Premiere regenerates index & pek files
Miscellaneous
With some capture card hardware, captured uncompressed clips have the wrong field order
In the Overlay Settings dialog, the Track control is not properly constrained by the Property control.
A single preference flag is used for the "Import into Project" setting in the Export Settings dialog and the Export Frame dialog; they should be managed independently.
Custom scratch disk location for Video and Audio Preview folders get’s reset to default, “Same as Project File"
Changes to the label color cannot be undone.
In the Usage lists, all instance are ordered by track item start time; should sort by Sequence Name first, then by track item start
Automatic relinking fails in certain cases when the name of a folder in the relative paths are too similar. [Mac only]
With OpenCL GPU acceleration and Transmit enabled with some 3rd party I/O cards, the video on the output monitor is corrupted
Newly created projects sometimes have multiple Project Panels open.
And in closing, a request: If this post prompts you to think "Great, but what about..." or "Thanks, but I just found this new bug in 2014.1," please start a new thread--after, of course searching to see if there's already a topic on that issue.
[And Shooter, I apologize in advance if the foregoing contains any typos ;-)]

Lots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
Sadly, the following issue is NOT fixed for me. Is it with new projects only? I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
On the list above...
Switching between sequences can turn the render bar red.
This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
1) Create two sequences with multiple short clips (the more clips the better)
2) Make sure GPU acceleration is enabled.
3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
4) Hit SAVE.
5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
6) Toggle back to the original sequence and the delay occurs again.
7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
Sigh.

CS5 custom build with GTX 285 for long-form 4k projects

I've been researching nonstop for several days, and it's time to ask for your expert opinions. I would appreciate any help.
I'm ordering a new system for Production Premium CS5, and mostly I will use Premiere Pro CS5 to edit long-form projects (huge timelines with thousands of clips) of Red 4k footage. It's a feature film with only a few F/X shots, but we'd like to do as much F/X, sound mixing, and color correction in CS5 as possible.
Here is what I'm considering:
CUSTOM BUILD from CYBERPOWERPC (about $1950 including items not listed):
OS: Windows 7 Professional x64
CPU: Intel® Core™ i7-930 2.80 GHz 8M Intel Smart Cache LGA1366
HDD: 1TB SATA-II 3.0Gb/s 16MB Cache 7200RPM HDD (Single Hard Drive)
MOTHERBOARD: * (3-Way SLI Support) GigaByte GA-X58A-UD5 Intel X58 Chipset SLI/CrossFireX Ultra Durable™3 Mainboard DDR3/1600 ATX Mainboard w/7.1 Dobly Audio,eSATA,Dual GbLAN, USB3.0, 2 x SATA-III RAID,IEEE1394a,4 Gen2 PCIe,2 PCIe X1 &1 PCI [+132]
MEMORY: 12GB (2GBx6) DDR3/1600MHz Triple Channel Memory Module [+219] (Kingston HyperX)
SOUND: Creative Labs SB X-Fi Xtreme Audio 24-BIT PCI Sound Card [+48]
VIDEO: Nvidia GeForce GTX 285 (I will have to take out their card and install this myself for GPU acceleration)
1. Do you see any poor or strange decisions?
2. I liked that mobo because of the chipset's possibilities and because it has 1394 for old-style DV capture. Plus it has 8 SATA 2.0's, 2 SATA 3.0's, 2. eSATA 2.0's, and 2 USB 3.0's for huge/fast storage options in the future. Is there some better alternative if I'm keen to have at least one of each of these formats?
3. I'll clone their 1TB OS drive onto a smaller 250GB drive to use as the OS drive, then use their 1TB drive as part of a 2TB RAID 0 video storage. Will using the mobo's raid controller or some type of virtual RAID (like I did in Xp64) be fine, or do I need a separate RAID controller (like I had in the late 90's).
4. What do you think about that processor and RAM for what I'm doing? Any reason to prefer 2 Quad-Core's (if dual processors are even compatible with CS5)? Please let me know if the current configuration will lag with huge timelines with thousands of 4k clips.
5. Maybe I don't need the Creative sound card and could just use the mobo's sound?
6. Will it be simple for me to remove their graphics card and install an Nvidia GeForce GTX 285 myself?
7. The Nvidia GeForce GTX 285 seems like a good fit for GPU acceleration for me since I'm not expecting to have 4+ layers of videos, though I will be doing multiple effects on 1 or 2 layers. Would having a Quadro FX give any advantage over the GTX 285 for huge timelines with thousands of 4k clips? Or any advantages for any other use?
8. The GTX 285 has 2 DVI's as its only connectors (plus something that looks like S-video). Can I use one DVI for my workstation and one DVI for monitoring video in realtime on an HDMI/DVI-equipped LCD TV or professional HD video monitor. Any problems with viewing/outputting my 4k video in HD in realtime? What is the best setup to view your video on an external monitor? Back in the CS2 days I used a 1394 through a camcorder into an analog professional monitor, but that's not going to be HD, plus I heard there's a sync problem these days.
Thanks for your advice.

Thanks for your advice, everyone!
I'm gaining a lot of knowledge, but I have some followups so I'll break it down into subcategories and hopefully you can chime in on one or more topics.
To give more info about my daily use and purpose:
--smoothly edit huge amounts of RED 4k footage/clips and view the video externally in as high a resolution as possible (2k or minimum of 1k).
---no reason to have more than 3 layers visible at a time.
--the vast majority of the time only 1 video layer (with video effects) will be visible, with perhaps a handful of fades/dissolves during the entire 2-hour feature.
--I don't mind if it takes slightly more time rendering DPX files at the end, but I don't want any hiccups and never want to render during day-to-day editing and monitoring.
GRAPHICS CARD and VIDEO MONITORS
1. I'm pretty much set on the GTX 285, but I wondered if for my purposes I'd get any significant benefit from the Quadro FX 5800 (+$2000-$2600) or the GTX 480 (+$100)? Either in speed of playback or in output to external video monitors. The 5800 has 4GB RAM versus the GTX 285's 1GB, and the GTX 480 has 1.5 GB. Does this RAM matter for what I'm doing or are the cores much more important? Also, if I chose the GTX 480 then I'd have to pray that everything would be stable with a MPE/CUDA/GPU-acceleration hack, or hope Adobe comes through with full support of that card.
2. What is the 3rd output on the GTX 285? There are two DVI outputs and then something that looks like S-Video. Is it S-video out? Or an HD audio out that travels alongside the DVI output to an external video monitor?
3. Does it slow down the system to send the video at 1k or 2k to an external video monitor since you'd be using both DVI outputs simultaneously?
RED 4k PLAYBACK and RAM vs CPU
1. For day-to-day editing, I'm fine scaling to 1/4 resolution if necessary and monitoring video externally at 1k or 2k. Would my current system already achieve that smoothly?
2. From what I've gathered here and elsewhere, for better 2k or 4k playback it might be better to spend extra on CPU rather than RAM. I could spend
--$1000 more for 24GB RAM (instead of 12GB)
--$290 more for an i7 975 Extreme 3.33 GHz 8M Cache
--$686 more for an i7 980x Extreme 3.33 GHz 12M cache.
Given my needs and the current total system cost of $1950, which of these 3 would you choose? Or should I stay with the cheaper i7 930 2.8 GHz and overclock (which I've never done before).
ECBowen:
It sounds like you've used a system similar to what I'm buying to playback RED 4k on a timeline in full, 1/2, and 1/4 scale. I'd greatly appreciate if you could clarify YES/NO for which are possible to have SMOOTH PLAYBACK with your 980x/12GB RAM/GTX 285 system. I know it's a lot to ask, but it would make me feel so much better about this big purchase:
-full scale 4k of 1 layer with 0 video effects
-full scale 4k of 3 layers with 0 video effects
-full scale 4k of 1 layer with 3 video effects
-full scale 4k of 3 layers with 3 video effects (NO, right?)
-1/2 scale of 1 layer with 0 video effects
-1/2 scale of 3 layers with 0 video effects
-1/2 scale of 1 layer with 3 video effects
-1/2 scale of 3 layers with 3 video effects
-1/4 scale of 3 layers with 3 video effects
RAID CONTROLLER
1. I won't use the virtual/software controller. The GigaByte UD5 says it has RAID 0, 1, 5, 10. Does that mean it has an onboard hardware controller that I can configure in Windows 7 or using some software supplied with the mobo?

Quicktime player quietly quits: how fix/replace?

Hi,
QuickTime Player application (running on Snow Leopard) is quietly quitting whenever I try to run it (and without playing anything).
It doesn't matter if I double-click it in Applications, or drag a .mp3 or .mov file onto the app in a Finder window, or if I right-click a .mp3 or .mov file and choose "QuickTime Player" ... in all cases, there's no visible sign that QuickTime actually started.
I confirmed, by checking the access date on the program file (well within the .app structure, of course), that attempts to run it *do* touch that file ...
If I use the Terminal and navigate down to /Applications/QuickTime Player.app/Contents/MacOS
and then try to run "QuickTime Player" program, I get:
2012-04-13 16:55:01.348 QuickTime Player[4911:903] Unable to load nib file: MainMenu, exiting
(see below)
The "QuickTime Player" folder app is dated Feb, 2012.
BTW, file "QuickTime Player" shows:
   QuickTime Player: Mach-O universal binary with 2 architectures
   QuickTime Player (for architecture x86_64):          Mach-O 64-bit executable x86_64
   QuickTime Player (for architecture i386):          Mach-O executable i386
which looks fine.
It used to work (a month or two ago?)
I've rebooted.
I've run "Software Update" ... it won't find it or update it.
I've deleted it, then run Software Update ...ditto. (I then restored it via Time Machine.)
I went to the QT download page ... reading between the lines, it appears that QT download is available only Leopard and earlier.
I tried it anyway ... the app won't install, saying "QuickTime X" is already present.
I looked around, and found a version of QuickTime Player in a sub-folder ("Video Stuff") in my Applications folder ...
when run, it reports it's: QuickTime Player 10.0 (128), and the .app folder is dated June 27, 2011.
But it does seem to work, overall!
BTW, if I run this old QT from Terminal (from within the .app folder), I get:
2012-04-13 17:08:34.442 QuickTime Player[5157:903] .sdef warning for argument 'FileType' of command 'save' in suite 'Standard Suite': 'saveable file format' is not a valid type name.
...but it does work.
thanks,
Stan

640 x 480
Widescreen 16:9
These settings are contradictory. Please post a screen capture image of the QT "Inspector" window to confirm what encode matrix setting, PAR display setting, and Scale display settings are actually embedded in your file. Also please confirm whether or not the source material was widescreen and it is 4:3 aspect you wish to correct at this point. If not, then please state the height at which the transcoded file was encoded and the target aspect ratio at which you want files to play in all media players.
Once compressed it plays back in Windows Media Player as 16:9 video.
When played back with Quicktime it is squished into a 4:3 format.
Different players dispay content aspect differently.
Why is this happening and how can I fix it?
QT 7, for instance, displays the file using specific Scale dimensions and if these dimensions are not equivalent to PAR/anamorphic playback settings, then the file can display differently in differently media players. As to fixing the problem, that depends on which setting you are trying to fix and what platform/software is available.

Output is redlining while track inputs are fine??

I have four microphones hooked up to an Apogee Quartet and I am using Garageband to record. All of the input levels are fine when I record (all within the green). For some reason during playback, the mastertrack redlines and distorts the recording with loud passages.
I am not over powering the microphones as the gain levels are set appropriately for each track. All output levels on Garageband are set to 0db including the mastertrack. Not sure why the mastertrack goes into the red during playback. Please advise!! Thank you!

Your JOIN is not correct, many fields are missing, so there multiplication of pseudo-records may arise
SELECT *
FROM imrg
INNER JOIN mkpf ON mkpf~bldat = imrg~idate " You can select each and every
                                             " movement of the whole day ?
INNER JOIN mseg ON mseg~mblnr = mkpf~mblnr
                    mseg~mjahr = mkpf~mjahr " add the whole key
INNER JOIN equi ON equi~erdat = imrg~erdat. " You can select each and every
                                             " Equipment created this day ?
Try to analyze the standard tcode via [SE30|http://www.sdn.sap.com/irj/scn/advancedsearch?query=se30] or [ST05|http://www.sdn.sap.com/irj/scn/advancedsearch?query=st05].
Regards,
Raymond

Premiere CC 7.1 - Red frames in playback and export

Having some problems after the 7.1 update.
In a variety of projects, on a variety of footage, we're experiencing random fully red frames (#ff000). Sometimes there are 1-2 frames in a clip, and occaisionally it's 80%-90% of the frames in a clip (this is less frequent). It has never been all of the frames of a clip.
This happens:
- On an undrendered timeline (you'll be watching an edit and you'll see a red frame - if you scrub back to it it'll still be there)
- On a rendered timeline
- In exports
Red frames that are visible on a timeline, are sometimes carried through to the export and sometimes not. Sometimes an exported file will display red frames that were not present on the timeline.
Red frames seem to be based on clips, not sequence frames. For example, in one of my exports, I had video footage with a lower third graphic over it. In one frame of the export, a red box appeared over the graphic, but the main shot was not affected.
This has happened to the following types of footage:
- .MTS (from C100)
- .MXF (from C300)
- ProRes 422 MOV
- ProRes 4444 MOV with alpha channel
Fixes that seem to work:
- If an export has red frames, re-export. Watch the new one like a hawk. Repeat until you get lucky.
- If a clip on a timeline has red frames, force a re-render via a Crop filter or similar
- Quit Premiere and reopen it
System/environment details:
- OSX 10.8.5
- Premiere Pro CC 7.1
- Mercury Playback Engine Software Only
- Often (always?) I-Frame Only MPEG sequence settings
- Much (all?) of the footage we've been working with has been on AFP shares via GigE with MTU of 9000
I haven't been able to confirm yet:
- Whether this ever happens with locally stored footage
- Whether this ever happens when Queueing to media encoder (rather than Exporting from Premiere)
- Whether changing to a QuickTime Desktop based sequence setting resolves the issue
Is anyone else experiencing this issue? It's frutstratingly un-testable, since it seems to happen at random. We'll continue to gather data points though and see if we notice any other trends.
Edit: Added additional system context

the error also appears with PRORES 422 files, but only after a certain amount of source data from prores 422 clips is processed / read
i made a test comp in AE with only one gigantic prores 422 source clip (8000 pixels x 1000 pixels @25fps) and the error first appeared at around 1500 frames read from the source file (equalling a few GB of source read and processed). after the red frames error appears once, the erroneous red frames appear more often but never in the same place when rendering the same comp several times)
i also made a test comp containing only a few full HD prores 422 clips (1920 x 1080, @25fps), there the error appeared only seldom (but still randomly). so it can be that a broader user base never experiences this erroneous behaviour at all.
i also made a testcomp containing about 40 full HD prores 422 clips (each 1920 x 1080, scaled down to 10% in size and distributed all over the comp so i can see them all at once). the erroneous red frames appeared within the first rendered frames!! obviously, many qt files had to be open and read in parallel, and so the error appeared from the very beginning of the rendering / export.
i suspect that the AE / PR applications open a RAM buffer for each open prores source file they need to read, and that this buffers somehow becomes compromised when it overflows and when buffer resize / buffer clear / flush operations take place.
of course i tested all sorts of RAM assignents for MP rendering (1GB per core, 2GB, 4GB, 6GB) and i rendered with several different settings of how many cores and ram should be available to other tasks. but the error always appeared. randomly.
--> fact in AE is, that nearly all MP renders / exports using prores clips as source files contained the bad red frames. when rendering without the MP option on (but of course up to 20x slower) so far i never experienced this error (of course always after fresh restarts once the error appeared)
PLEASE FIX THIS ASAP
mac pro 2011, 12 cores, osx 10.8.5, 64 GB ram, angelbird SSD, ati hd radeon 5770 1GB

RED Anamorphic playback

Similar Messages

Maybe you are looking for