Flatten multicam weirdness

I am finishing up a multicam project. Setup and editing of the multiple cameras went very smoothly. This was a 45 minute concert video. After getting all the camera cuts right I wanted to flatten the sequence and then trim out the dead areas.
When I flattened the sequence there were sections where the clips had diagonal bars and no video played in those sections. I undid the flatten and opened up the nested multicam sequence and found that in those areas there were some gaps on tracks that were not active tracks. (i.e. camera3 was active camera 1 had a small gap. I found if I put black video in the gap things seemed to work.
This happens on my work computer and home computer Both are mac pros, one is an 8 core 2008 machine running 10.8.4 the other is a 12 core running 10.9. Both are runing  Premiere 7.2.1
I ahve plugin on my project, so to verify that it wasn't the plugins I built a multicam sequence with just video and flattened that and got the same result.
One thing I also discovered is if I double click on the sections with diagonal lines and no video, they will open in the source monitor and play fine there. If I drag that clip back to a timeline it goes back to the diagonl line no video state.
Any ideas?

Can some other Premiere users or preferably someone in the Adobe staff please make this test:
- Make a sequence and put som black video in it, name the sequence seq1
- Put seq1 into a new sequence, name it seq2
- Right click and enable multicam for the seq1 clip inside seq2
- Flatten the seq1 clip and notice that everything works fine
- Undo the flatteing, go into seq1 and make multiple edits using the razor tool (not moving any clips, just making cuts)
- Go to seq2 and perform the flatten feature once again and see what happens
In previous versions of PRP you would end up with the exact same source clips and edits in seq2 as in seq1 after flatteing, which is what you really want. In PRP 7.2.1 you end up with one single clip with diagonal lines beacause of the timecode being misplaced. Somehow the flatten feature in Premiere 7.2.1 gets confused by edits inside of a multicam sequence.

Similar Messages

  • Audio problems when flattening multicam

    Discovered this bug when I tried to flatten a multicam sequence. When I flatten a selection of the multicam the audio seems to “import” the full audio track from the linked multicam sequence, not just the cuts I have made. As a result the audio on both sides of the cuts gets overridden by the “new” audio from the flatten multicam. When I tried to do it manually it seemd like the audio from the flattening stayed in the track. I discovered this when I selected different clips in the track. When I clicked in a presumably empty places in the track it selected the audio from the flatten multicam.
    To better describe the problem I screen recorded it.
    The machine is:
    OS: 10.9.4
    Modellnavn:Mac Pro
    Modellidentifikator:   MacPro6,1
    Prosessornavn: 6-Core Intel Xeon E5
    Prosessorhastighet:   3,5 GHz
    Antall prosessorer:   1
    Totalt antall kjerner:   6
    Nivå 2-buffer (per kjerne):256 kB
    Nivå 3-buffer: 12 MB
    Hukommelse: 32 GB
    Start-ROM-versjon:   MP61.0116.B05
    SMC-versjon (system):   2.20f18
    Illumination-versjon:   1.4a6
    Serienummer (system):   F5KN3023F694
    Maskinvare-UUID: 6CC0D7BE-4A3E-5ED0-B7E7-3EEC887552E8
    Adobe Premiere Pro CC 2014.0 - 8.0.0 (169) Build

    We tried flattening in the new 8.1 also, what happend there was some audio disappeared and the audio adjustment also disappeared.
    This was done on the same machine but with Adobe Premiere 2014.1 8.1.0 (81) build

  • Audio problem when flattening multicam

    To sum up:
    When flattening multicam sequences the audio is selected from audio track one, which is not the track with good audio. I have all bad audio muted in the source sequence, so prior to flattening it sounds right. Loading the multicam clip to the source monitor then right click switch camera audio makes no difference. The only way I find to fix this is to move the good audio to track 1. This would be very time consuming as I have a large number of multicam source clips. Any ideas on an efficient fix? Am I missing something?
    Here's a long detailed step by step explanation of what I'm doing if you want more information:
    I have a series CC2014 sequences (I'll call them "master sequences") composed of many multicam clips. These mulitcam clips were created by Premiere from the project panel. I have a total of 7 of these "master sequences". Within each master sequence, all mulitcam editing is done (camera cuts made within each multicam clip). I selected the proper audio for each mulitcam clip. All good so far. Now I want to flatten the master sequences to simplify the project. For the first 3 sequences I selected all clips/multicam/flatten. Everything worked normally, no problems. For the next 4, when I flatten, the audio source changes in every multicam clip to a bad camera audio track which cannot be used. This bad track is muted in the individual multicam sequences and was not heard prior to flattening. The difference between the sequences that worked right and the ones that didn't is that the order of the cameras on the tracks is reversed. When it worked properly, the camera with the good audio was on video/audio track 1, when it didn't work the camera with the bad audio was on track 1. I understand I can copy and paste the audio from the original sequence but each of my main sequences contains many individual multicam sequences as created by Premiere, so I would have to reveal in project each source multicam sequence, open in timeline, and select the audio to copy and paste. This would be very time consuming.
    Thanks in advance for wisdom proffered.

    We tried flattening in the new 8.1 also, what happend there was some audio disappeared and the audio adjustment also disappeared.
    This was done on the same machine but with Adobe Premiere 2014.1 8.1.0 (81) build

  • Multicam weirdness - Premiere CC Mac

    I've been loving the new multicam features but I just hit a problem.  I'm using Premiere CC on a Mac, all updated.  I cut a three camera multicam last week and I just wanted to look at a few parts again to see if I choose the best angle.  When I set the Program Monitor to Multi-Camera, the screen goes black, no angles at all are displayed.  When I set it to Composite, the single angle displayed looks fine.
    You can see from the timeline that all three angles are loaded and active (so nothing is turned off in the Nest).  I also double checked and the timeline and the Multicam is still active, not flattened.  Of the four multicam sequences I edited last week (all in the same project), two work as expected and two don't.
    Here is the sequence opened with the Program monitor set to Composite:
    Here it is with multicam selected:

    I just found out some more info.  I opened and older, auto-save of the project and the multicam sequence *was* working correcty.  I reviewed it and made a few corrections (all was going well).  Then I changed to the color-correcting workspace.  When I left that and went back to the editing-workspace two of my four sequences open in the Timeline were closed.  When I re-opened them, the multicam window was black.
    Looks like a bug to me.  I can't wait for the "October 15th" update!

  • More multicam weirdness - CC

    Okay... I have an unusual multicam with an even more unusual problem. 
    We are making short videos for a Spanish class.  These are mostly three cameras with additional, non-sync audio for each of the main actors.  Each video is shot in short takes with a little overlap that need to be put together in a multicam sequence.
    I used the new audio sync feature to (successfully!) sync up about 70 files.  They auto sorted into a dozen different multiclips and, for the most part, Premiere was close to perfect!  This is wonderful since my Spanish is "no muy buena"!
    I opened each of the multiclips in the timeline.  It is important that I include the audio from each of the actors so I turned all of the relevant audio tracks on.  I selected the best take from each multiclip and pasted these into a new sequence with the intent of making that into a multicam sequence the old fashioned way.  I suspect this is my problem.
    When I drag this new nest to the new item icon I get a single video and audio track and all of the audio tracks play at once (all very good).  BUT when I enable the Multi-Camera most of the audio tracks (all of the useful ones) go away even though they were happily playing muxed in the nest before I enabled Multi-Camera!
    Any ideas on why this is happening or how I could proceed differently?  I'd really like to use the multi-camera feature but it will be difficult to edit each little piece and then bring it into a finished sequence.
    Here are some screen grabs to help:
    My original, hand-made, nest called "ALL_techshop"
    The new item created when "ALL_techshop" is dragged onto the new item icon.  All of the audio channels that I have turned on paly simultaneously
    Enabling the Multi-Camera turns off all of the useful channels:

    There may be a new cool simple way or button to take care of this, but if I understand your post correctly...did you try option+selecting just the video tracks only and then right-clicking and selecting "nest" then right-click again and select multi-camera>enable. That is how I used to do it on CS6 and it worked recently on CC. That way your video is nested all on one track but your audio remains untouched. I don't know why when you did it some of the tracks turned off. Might be something simple that's not being toggled on or off, not sure. But you can try what I suggested for now and see if it helps.
    HOWEVER...please be aware before you start your multicam edit that there is a huge, giant, ugly, ridiculously unacceptable bug with multicam in Premiere Pro CC right now that has essentially broken the multicam experience. If you don't know about it, read about it below or you may be left losing hours of editing work:
    http://forums.adobe.com/thread/1236698?tstart=0
    Good luck!

  • Workflow for Green Screen Multicam, Color Correction. (CC 2014)

    Hi
    What is the best workflow to do a music video shot with 7 cameras (each with 4 takes) on a green screen which would also include green screen stills.
    All shot with Consumer Grade cameras at 1920/1080 at the highest resolution (I think 30 fps)
    The way I am going about is not efficient.
    My tasks are:
    Key each 20 minute clip (to get about 2 usable minutes)
    Rotate my DSLR video (shot in landscape so I could take stills as well)
    Color correct all clips
    Create a new cleaned up movie for each clip including: Proper format. Keyed with new background, Color Corrected, Re-encoded as a new movie, Re-imported as 7 new movies, begin to edit.
    I was watching some movies about pasting attributes which look helpful and also about nesting sequences which looks like it could save time.
    What is the best workflow steps to do all this? Am I going about it the right way by creating new movie clips which are keyed with a new background, color corrected, and reencoded including all the garbage footage? Then create a new multicam project to edit the cleaned up footage?
    HELP!

    Temporary solution for this was "export xml" after all. I had to disable all graphics and textlayers and delete colorcorrections, and flatten multicam, so i had to redo all grading ja graphics stuff in older premiere after importin FCP xml. But got the work done in time. Won't use cc 2014 in near future unless someone figures out what is wrong with green frames. (well actually now im exporting from older AME, will she if the green frames pops out there too, wouldn't be too much surprised....)

  • 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.

  • What's Fixed in Premiere Pro CC2014.2

    As noted in the blog post for the 2014.2 release, while this update includes a few new features, it is chiefly geared toward addressing known issues. The blog post lists the higher profile fixes. Below is is a more comprehensive list.
    Import
    Red frames in MXF clips from a particular model of camera.
    Cannot import ARRI Alexa Open Gate clips
    Import fails for IMX 30 MXF clips stored on certain proprietary media asset management systems. Error: Unsupported format or damaged file.
    Some XDCAM HD Proxy files show red frames
    Some .VOB clips play only audio or shows media pending indefinitely
    Premiere does not recognize timecode for audio-only MXF files written by some third-party programs.
    Only the first frame of video plays for AVC-Intra50 MXF files stored on certain third-party media asset management systems.
    Spanned DVCPRO clips have incomplete audio if an XMP file is present but no media cache/pek file are found.
    Some metadata from an Adobe Clip project does not get correctly logged on import.
    Exporting & Rendering
    Rendering fails for MXF media with Posterize Time effect applied
    ProRes exports can be very slow when smart rendering
    Encoded output can include black frames, corrupted frames, or frames from elsewhere in the sequence
    Canceling export to P2 can result in low-level exception if the sequence duration is greater than a few minutes
    Aspect ratio for IMX 30 widescreen anamorphic encodes is incorrect.
    Edit to Tape: Audio drops out while playing out to tape
    The Height setting for encodes to the GoPro Cineform codec is constrained to multiples of 8.
    Smart Rendering: GoPro 2.7K footage cannot be smart rendered
    AAF
    Distorted audio in AAF exports with 24 bit embed option selected.
    If a multichannel sequence has been nested into 2 channel sequence, then an AAF export yields the number of channels in the nest rather than the 2-channel mix-down
    Certain third-party programs have problems relinking to video with Premiere's AAF exports. (Windows only)
    If the first of two adjacent audio clips has a Fade Out applied, exporting as AAF converts it to a Fade In onthe second clip. (Mac only)
    When AAF exports are opened in some third party apps, audio crossfades are treated as cuts or fade-ins.
    Crash during AAF export if a video clip has multiple effects applied.
    When AAF exports are opened in some third party apps, some audio clips and tracks are incorrect.
    Crash upon exporting to AAF with disabled clips that have cross fades applied
    If a multicam sequence with mono audio is nested onto a stereo or adaptive track, then exporting to AAF yields a stereo clip with the audio panned fully to the left.
    When AAF exports are opened in some third party apps, rendered audio of is relinked automatically, but the video needs to be manually linked.
    Playback
    If a UHD ProRes clip is in an SD sequence an scaled to less than 50%, then scaling is ignored during playback at Full Resolution [GPU acceleration only]
    Poor playback performance with certain third-party I/O hardware on OS X 10.9.
    Crash during playback of R3D content [CUDA GPU acceleration only]
    Audio
    Audio sync is lost with some XDCAM content wrapped in QuickTime reference movie
    Audio sync is lost when user starts scrubbing during playback while using certain I/O hardware.
    When playing past an audio transition, the sound sometimes surges and has pops/clicks introduced
    Audio dropouts, and Events panel reports "audio dropouts detected." [Prefetch purge related]
    Audio dropouts in some scenarios after releasing memory (e.g., cycling focus to another app)[Prefetch-related]
    Shuttling for an extensive time can cause audio dropouts
    Project
    If current user does not have write access to certain folders, the crash error message is uninformative (Mac only)
    In Adobe Anywhere, crash when using keyboard shortcut to open Convert Project to Production dialog or the New Production dialog.
    If multiple clients on a network use the same media cache location, then upon importing a given asset each client writes its own accelerator files.
    The Find features in the Project panel and Timeline cannot search by Korean characters.
    In Search Bins, moving focus by keyboard from one clip to another can cause the tree view to expand to show the bin where the clip is stored.
    Project Manager/Consolidate & Transcode
    If the destination drive has insufficient space, Premiere throws an "unknown error" rather than an informative message.
    Project Manager writes some clips outside of folders
    Consolidate and Transcode does not warn the user if the destination drive has insufficient space.
    Unknown error can result from using Consolidate & Transcode with P2 content in the sequence.
    In some cases, Consolidate & Transcode copies and renames the component assets for merged clips.
    If Exclude Unused Clips is deselected, the components for merged clips sometimes still get copied; if the option is selected, the presence of merged clips can yield Unknown Error.
    If the sequence being transcoded contains overlapping "soft" subclips, then some clips may be missing from the sequence in the consolidated version, and In/Out points may be incorrect for the subclips.
    If Exclude Unused Clips is turned off and the project being transcoded contains "soft" subclips, then the consolidated version of the project does not have transcoded copies of the subclips.
    If a sequence contains only audio from an A/V clip, using Consolidate and Transcode to some presets will fail with unknown error
    If the sequences being transcoded contains two copies of a master clip, one of which was the product of Duplicating or Copying/Pasting in Project panel, the consolidated version of the project has only one instance of the master clip.
    If the project contains multiple master clips for the same asset and Interpret Footage is applied, then the consolidated version will have multiple transcoded copies of the source asset.
    If the transcoded sequence contains a hard subclip (i.e., "Restrict Trims to Subclip Boundaries" enabled), the resulting project item is a master clip rather than a subclip.
    Merged Clips
    Comment markers added to a merged clip get inserted to the component clips, but the Name & Comment entries are not saved.
    Hang on right-clicking the current marker in a merged clip in certain circumstances.
    Editing/Timeline
    Crash on clicking the very bottom of clip in the Timeline and dragging to move the clip. [SubViewImpl.cpp-724]
    Crash on Ripple Trim Previous Edit to Playhead for a clip group when that action completely deletes one of the component clips in the group. (TrackItemGroup.cpp-821)
    Indefinite hang if sequence contains a QuickTime .mov with an unusual framerate and a CEA-708 caption track
    Crash upon creating a sequence from a source with no frame rate specified (e.g., a title imported from a third-party-generated XML)
    If a rendered-and-replaced clip has been trimmed, then Restore Unrendered can result in content being out of sync
    Multicam
    Audio is lost when flattening multicam sequences that were created with dual stereo movies.
    If a multicam clip was created with Switch/mono and placed into stereo tracks, then flattening incorrectly maps the audio channels to stereo, with the right channel disabled.
    Playing a multicam sequence in the Source Monitor can result in an unacceptable ratio of dropped frames.
    Effects & Transitions
    With Warp Stabilizer applied, Program Monitor shows only upper left corner of the frame, sometimes with alternating whole frames [GPU acceleration only]
    Sub-pixel positioning is incorrect for non-linear alpha compositing [GPU acceleration only]
    GPU transitions that depend on other layers cannot access those layers
    Crash upon clicking outside the Direct Manipulation control for some effects.
    Memory leak with certain third-party effects
    Crash on clicking Setup button for some third-party transitions.
    Loudness Radar' Track FX Editor intercepts keystrokes intended for editing titles (e.g., spacebar)
    Crash (Pure Virtual Function Call) on adjusting parameters for some third-party effects.
    Some third-party effects get frames from the wrong time in the clip.
    UI/Workspaces
    All open Project panels get reset to root upon switching between projects that use the same workspace.
    The order of open Timelines sometimes gets jumbled upon closing and reopening the project.
    Bezier handles for keyframe can be nearly invisible at default brightness.
    Closing the Source Monitor when it's showing a scope (e.g., YC Waveform) crashes Premiere (error: CheckBoxControl.cpp-105)
    HTML5 panels do not receive Tab events.
    Redraw errors on maximizing an HTML5 panel.
    Performance (Note: Most of these fixes are also listed under a product area)
    In certain scenarios, performance is unacceptable when doing basic editing operations with waveforms displayed in the Timeline.
    Scrubbing a growing file on an Xsan can result in very high bandwidth usage with some network configurations.
    Playing a multicam sequence in the Source Monitor can result in an unacceptable ratio of dropped frames.
    ProRes exports can be very slow when smart rendering.
    Poor playback performance with certain third-party I/O hardware on OS X 10.9.

    Just in case anyone is interested:
    anyone else having PP crash after the 8.2 update? I keep getting the below error:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
    Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
    Exception code: 0xc0000005
    Fault offset: 0x0000000000052f86
    Faulting process id: 0x2168
    Faulting application start time: 0x01d019e6c12de352
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 8f518e38-85de-11e4-81e4-1cc1de338660
    I trashed my preferences; rolled back to earlier versions of NVIDIA drivers; cleared out my cache; reinstalled PP 8.2, and uninstalled all 3rd party plugins... I still get the above error. I've since rolled back to 8.1 with no issues. I'd love to get 8.2 to work, since scrubbing thru Gh4 4k files was a lot smoother with this update.
    Specs:
    HP Z800 MC 8.2, Adobe CC 2014, Windows 7 Ultimate 64-bit SP1, 2 Hex Core X5650 @ 2.67GHz, 48Gigs Ram, NVidia Quadro K4000, Sandisk Extreme 240 gig SSD System drive, SATA 4 Tb (Raid 0) media drive, Sata 2 TB export drive , SSD 120GN for cache, 1 G-Tech 2tb Raid export/backup,1 4tb G-drive backup, Matrox MXO2 mini, 850 WATT PSU
    in Premiere Pro • Reply • Like Show 0 Likes(0)

  • Premiere pro cc2014 bugs?

    Hello
    Has anyone updated Premier pro cc 2014 to the latest version. I havent touched it in ages because of all the bugs and constant  crashing but im eager to return to several  CC 2014 projects that I need to start using again.
    Have the bugs been fixed is it worth using again?
    Thanks
    Philip

    Here's a breakdown and he's the link to the original post. There's some feedback from other customers there: What's Fixed in Premiere Pro CC2014.2
    As noted in the blog post for the 2014.2 release, while this update includes a few new features, it is chiefly geared toward addressing known issues. The blog post lists the higher profile fixes. Below is is a more comprehensive list.
    Import
    Red frames in MXF clips from a particular model of camera.
    Cannot import ARRI Alexa Open Gate clips
    Import fails for IMX 30 MXF clips stored on certain proprietary media asset management systems. Error: Unsupported format or damaged file.
    Some XDCAM HD Proxy files show red frames
    Some .VOB clips play only audio or shows media pending indefinitely
    Premiere does not recognize timecode for audio-only MXF files written by some third-party programs.
    Only the first frame of video plays for AVC-Intra50 MXF files stored on certain third-party media asset management systems.
    Spanned DVCPRO clips have incomplete audio if an XMP file is present but no media cache/pek file are found.
    Some metadata from an Adobe Clip project does not get correctly logged on import.
    Exporting & Rendering
    Rendering fails for MXF media with Posterize Time effect applied
    ProRes exports can be very slow when smart rendering
    Encoded output can include black frames, corrupted frames, or frames from elsewhere in the sequence
    Canceling export to P2 can result in low-level exception if the sequence duration is greater than a few minutes
    Aspect ratio for IMX 30 widescreen anamorphic encodes is incorrect.
    Edit to Tape: Audio drops out while playing out to tape
    The Height setting for encodes to the GoPro Cineform codec is constrained to multiples of 8.
    Smart Rendering: GoPro 2.7K footage cannot be smart rendered
    AAF
    Distorted audio in AAF exports with 24 bit embed option selected.
    If a multichannel sequence has been nested into 2 channel sequence, then an AAF export yields the number of channels in the nest rather than the 2-channel mix-down
    Certain third-party programs have problems relinking to video with Premiere's AAF exports. (Windows only)
    If the first of two adjacent audio clips has a Fade Out applied, exporting as AAF converts it to a Fade In onthe second clip. (Mac only)
    When AAF exports are opened in some third party apps, audio crossfades are treated as cuts or fade-ins.
    Crash during AAF export if a video clip has multiple effects applied.
    When AAF exports are opened in some third party apps, some audio clips and tracks are incorrect.
    Crash upon exporting to AAF with disabled clips that have cross fades applied
    If a multicam sequence with mono audio is nested onto a stereo or adaptive track, then exporting to AAF yields a stereo clip with the audio panned fully to the left.
    When AAF exports are opened in some third party apps, rendered audio of is relinked automatically, but the video needs to be manually linked.
    Playback
    If a UHD ProRes clip is in an SD sequence an scaled to less than 50%, then scaling is ignored during playback at Full Resolution [GPU acceleration only]
    Poor playback performance with certain third-party I/O hardware on OS X 10.9.
    Crash during playback of R3D content [CUDA GPU acceleration only]
    Audio
    Audio sync is lost with some XDCAM content wrapped in QuickTime reference movie
    Audio sync is lost when user starts scrubbing during playback while using certain I/O hardware.
    When playing past an audio transition, the sound sometimes surges and has pops/clicks introduced
    Audio dropouts, and Events panel reports "audio dropouts detected." [Prefetch purge related]
    Audio dropouts in some scenarios after releasing memory (e.g., cycling focus to another app)[Prefetch-related]
    Shuttling for an extensive time can cause audio dropouts
    Project
    If current user does not have write access to certain folders, the crash error message is uninformative (Mac only)
    In Adobe Anywhere, crash when using keyboard shortcut to open Convert Project to Production dialog or the New Production dialog.
    If multiple clients on a network use the same media cache location, then upon importing a given asset each client writes its own accelerator files.
    The Find features in the Project panel and Timeline cannot search by Korean characters.
    In Search Bins, moving focus by keyboard from one clip to another can cause the tree view to expand to show the bin where the clip is stored.
    Project Manager/Consolidate & Transcode
    If the destination drive has insufficient space, Premiere throws an "unknown error" rather than an informative message.
    Project Manager writes some clips outside of folders
    Consolidate and Transcode does not warn the user if the destination drive has insufficient space.
    Unknown error can result from using Consolidate & Transcode with P2 content in the sequence.
    In some cases, Consolidate & Transcode copies and renames the component assets for merged clips.
    If Exclude Unused Clips is deselected, the components for merged clips sometimes still get copied; if the option is selected, the presence of merged clips can yield Unknown Error.
    If the sequence being transcoded contains overlapping "soft" subclips, then some clips may be missing from the sequence in the consolidated version, and In/Out points may be incorrect for the subclips.
    If Exclude Unused Clips is turned off and the project being transcoded contains "soft" subclips, then the consolidated version of the project does not have transcoded copies of the subclips.
    If a sequence contains only audio from an A/V clip, using Consolidate and Transcode to some presets will fail with unknown error
    If the sequences being transcoded contains two copies of a master clip, one of which was the product of Duplicating or Copying/Pasting in Project panel, the consolidated version of the project has only one instance of the master clip.
    If the project contains multiple master clips for the same asset and Interpret Footage is applied, then the consolidated version will have multiple transcoded copies of the source asset.
    If the transcoded sequence contains a hard subclip (i.e., "Restrict Trims to Subclip Boundaries" enabled), the resulting project item is a master clip rather than a subclip.
    Merged Clips
    Comment markers added to a merged clip get inserted to the component clips, but the Name & Comment entries are not saved.
    Hang on right-clicking the current marker in a merged clip in certain circumstances.
    Editing/Timeline
    Crash on clicking the very bottom of clip in the Timeline and dragging to move the clip. [SubViewImpl.cpp-724]
    Crash on Ripple Trim Previous Edit to Playhead for a clip group when that action completely deletes one of the component clips in the group. (TrackItemGroup.cpp-821)
    Indefinite hang if sequence contains a QuickTime .mov with an unusual framerate and a CEA-708 caption track
    Crash upon creating a sequence from a source with no frame rate specified (e.g., a title imported from a third-party-generated XML)
    If a rendered-and-replaced clip has been trimmed, then Restore Unrendered can result in content being out of sync
    Multicam
    Audio is lost when flattening multicam sequences that were created with dual stereo movies.
    If a multicam clip was created with Switch/mono and placed into stereo tracks, then flattening incorrectly maps the audio channels to stereo, with the right channel disabled.
    Playing a multicam sequence in the Source Monitor can result in an unacceptable ratio of dropped frames.
    Effects & Transitions
    With Warp Stabilizer applied, Program Monitor shows only upper left corner of the frame, sometimes with alternating whole frames [GPU acceleration only]
    Sub-pixel positioning is incorrect for non-linear alpha compositing [GPU acceleration only]
    GPU transitions that depend on other layers cannot access those layers
    Crash upon clicking outside the Direct Manipulation control for some effects.
    Memory leak with certain third-party effects
    Crash on clicking Setup button for some third-party transitions.
    Loudness Radar' Track FX Editor intercepts keystrokes intended for editing titles (e.g., spacebar)
    Crash (Pure Virtual Function Call) on adjusting parameters for some third-party effects.
    Some third-party effects get frames from the wrong time in the clip.
    UI/Workspaces
    All open Project panels get reset to root upon switching between projects that use the same workspace.
    The order of open Timelines sometimes gets jumbled upon closing and reopening the project.
    Bezier handles for keyframe can be nearly invisible at default brightness.
    Closing the Source Monitor when it's showing a scope (e.g., YC Waveform) crashes Premiere (error: CheckBoxControl.cpp-105)
    HTML5 panels do not receive Tab events.
    Redraw errors on maximizing an HTML5 panel.
    Performance (Note: Most of these fixes are also listed under a product area)
    In certain scenarios, performance is unacceptable when doing basic editing operations with waveforms displayed in the Timeline.
    Scrubbing a growing file on an Xsan can result in very high bandwidth usage with some network configurations.
    Playing a multicam sequence in the Source Monitor can result in an unacceptable ratio of dropped frames.
    ProRes exports can be very slow when smart rendering.
    Poor playback performance with certain third-party I/O hardware on OS X 10.9.

  • Green frames when exporting from CC 2014

    Hello. I just updateted to the newest edition of premiere pro(aswell as all the other CC software i have installed which includes phoshop,speedgrade,audition,ame, and after effects). So the versions of the software are the very latest.
    My computer is late2013 macbook pro with nvidia graphics card, and i have all the system updates installed, nothing special going on.
    Heres the issue:
    When exporting the project, i get random green frames, full green frames. Complitely randomly, no pattern whatsoever.
    My workflow have been this: Footage shot with two Sony cameras and i have encoded all the materials to mxf format with one step earlier AME version. I started the project with one step earlier premiere, and i have already done 19 out of 23 sequences that project contains, no problem at all with earlier version of ame&premiere. Now i updated to the latest 2014 cc and these green frames started to pop out randomly. I have not used any plugins or effects, only premieres own threeway colorcorrector and bightness&contrast. Parts of the clip have transparent black video as textbackground with crop effect applied and basic textlayer from premieres own text editor. I have exported few grpahics from aftereffects (both the lates and the one step earlier version) to proress 4444 format as RGP+alpha. And im exporting with using youtube SD widescreen 360p settings, nothing changed. Again, everything worked perfectly before update.
    things i have tried sofar:
    delete caches both manually and from each software
    normal boot
    pram reset
    safeboot
    update check
    export XML from 2014 cc and import to earlier premiere -> no luck, things got messed up somehow
    made a copy of both project files, i compared and changed some version number from 27 -> 26 so i could open the project in earlier premiere -> no luck (this worked back in cs6 time when i had to import cs6 project to cs5.5)
    Kinda running out of time, so rest of the night im going to spend re-editing those sequences i have done today with newer version of premiere. Will adobe pay for me for these extra hours, i think my client wont approve one extraediting day(night becaus of the schedule, these must be ready tomorrow with no green frames) because of software problem?
    Ask anything you want, i'm 100% sure this is not user error since everything was fine with one step earlier premiere version. I will copy&paste this to the bugreport too.
    Thanks

    Temporary solution for this was "export xml" after all. I had to disable all graphics and textlayers and delete colorcorrections, and flatten multicam, so i had to redo all grading ja graphics stuff in older premiere after importin FCP xml. But got the work done in time. Won't use cc 2014 in near future unless someone figures out what is wrong with green frames. (well actually now im exporting from older AME, will she if the green frames pops out there too, wouldn't be too much surprised....)

  • Final Cut 6 to Motion3 workflow

    Hi everyone?
    i am editing a multishoot sequence in Final Cut 6. I want to roundtrip to motion3 for effects work.
    whats the best workflow for this. I collapsed my multiclip in Finalcut and then i can either send separate clips to motion from timeline or i can send the whole sequence (but sending the whole sequence did not update my effects in Finalcut). Should i somtimes export as quicktime and then re-import to Motion3. Im not sure what is the best workflow, is there better workflow for different situations?
    Thanks
    Danny

    Sorry Dan, I use 'baking' a lot so I forget. It just means exporting a Quicktime of that clip at the native res / codec and then re-importing it. That way it's more stable than just a flattened multicam clip.
    With your multicam clip on the timeline, select it (with in's and out's) and choose file>export>quicktime movie. That will export it in a codec and at a resolution that it exists as on the timeline. When you import it back in, it shouldn't need a render. Then with the newly imported clip on the timeline, right click on it and choose 'send to' and choose Motion. It will ask you to save the motion project somewhere, and then ...you're off the the races. ^^ When you save your changes in Motion and go back to your final cut timeline, you will have a motion file where your 'baked' clip was.
    I would suggest for timeline organisation, that you leave your multicam clip in place and just place the baked / motion file clip over top on V2. This will allow you to go back to where you were before exporting / baking in case anything goes wrong.
    I guess I got a little long in the wind there, but I hope it helps,

  • Multicam flattening issue

    Hi !
    I'm experiencing a weird bug/behavior while flattening my multicam sequence.
    Here is my "workflow" :
    - I create a multicam sequence by selecting the angles and the audio in the project panel. At this step, the cameras are in the wrong order.
    - Instead of moving the tracks in the multicam sequence, i open it in the source view, and choose "change cameras" (I'm french, i don't konw the exact translation for this function)
    - I edit my sequence.
    When i try to flatten it, the order of the cameras set previously in the source view is skipped, and the "flatten function" uses the track number of the sequence to replace the edit.
    Before submitting a bug report, i want to know if somebody has experienced this problem yet. Is it a normal behavior ? (In my opinion, it shouldn't be) Is there a workaround ?
    Thanks.
    (I'm on the latest version of Premiere Pro CC (7.2.1), Mac os x 10.9.2)

    - Instead of moving the tracks in the multicam sequence, i open it in the source view, and choose "change cameras"
    Huh?

  • Multicam Frame Hold Issue in Premiere CC 8.0.1 - When Flattening

    Hi,
    I'm not sure if this has been addressed before, I couldn't find an answer:
    When I use frame hold for a segment in a multicam timeline, then flatten the timeline, the frame hold no longer holds the frame.
    The timeline is a 720x960 23.976p  P2 timeline with three cameras.
    Thanks!

    Me too with this one have it randomly when just opening the same project and begining to edit
    had it happen about 4 times now.
    Latest update
    Microsoft Visual C++ Runtime Library
    Program C:\Program Fi...
    R6025
    - pure virtual function call
    [ok]
    Adobe Premiere Pro CC 2014.1 has stopped working
    roblem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.1.0.81
      Application Timestamp: 5426694c
      Fault Module Name: MSVCR110.dll
      Fault Module Version: 11.0.51106.1
      Fault Module Timestamp: 5098826e
      Exception Code: 40000015
      Exception Offset: 00000000000740da
      OS Version: 6.1.7601.2.1.0.256.1
      Locale ID: 2057
      Additional Information 1: a22a
      Additional Information 2: a22a26525c716a6a7fdf0a84944bf385
      Additional Information 3: 9245
      Additional Information 4: 9245cf38809b383bd6a86e3f052c9114
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

  • One take folder is acting weird: flatten and merge deletes the take folder

    My other take folders are acting fine, but when I flatten and merge this particular one, it deletes the entire take folder from the track. The other take folders on the track are left alone.
    It also shows a blank comp when I click the disclosure triangle to close the take folder. When I am comping the track it is fine and acts normal. I can't get the audio out of the take folder without bouncing it, and that's not good because the waveform is so small in comparision to the rest of the tracks.

    you don't need to bounce
    Just unpack folder take
    or
    http://discussions.apple.com/thread.jspa?threadID=2003147&tstart=0
    Export as Audio should be easy
    (export track as Audio is not the same as Bounce... *it bypass all reverbes and delay on BUSSes...*
    of course you need to bypass manually the inserts plugins before export the whoòe audio track...
    it will be absolutely the same as original!!!
    G

  • "Flatten" option for multi-camera  is gone in new version of CC

    It has been a couple months since I have used this feature, but it is gone now. Now when I right click on a multi-camera clip, the only option is "Enable" (or disable by uncheking it). The option to "Flatten"was a huge benefit, and it was sorely lacking in CS6. Please tell me that this feature is coming back, or more importantly how to get it back. I am working on a whole bunch of multicamera projects this month.
    Thanks,
    John

    The flatten command remains for me on 7.2 running  OSX 10.8.5,  for multicam sequences created through the Project panel and by the old method of nesting a sequence in another sequence.
    As evidence that this is CC7.2, note that two instances of the Media Browser are open, which was not possible until the new update.
    I'm not suggesting that the command is missing in your case but only certifying that it has not been removed altogether. The more info you can provide about your case, the better the chance that we'll be able to figure out what's going on.

Maybe you are looking for