Premiere Pro CC Mute / Solo bug

Mute and Solo seems to enable and disable by themselves when I save a project, ie if I save a timeline with three audio tracks and track one muted, then quit Premiere and re-open the project, all three audio tracks will be muted.
It happened on a small project converted from CS6, I'll see if it happen with a project started on CC too.

OK, everyone (i.e. Adobe).  I attempted to submit the feature request.  Unfortunately Adobe only wants to hear 2000 words from it's customers.  LOL
Here's the request (and please fix your feature request form to allow detailed feature requests):
*******Enhancement / FMR*********
Brief title for your desired feature:
CS6  had "Toggle Track Output" (I'll refer to this as "Enable Track").  CC has "Solo Track".  The name has changed, but the functionality seems identical.  I would like to see BOTH "Enable Track" and true "Soloing" of a SINGLE track.  Currently it's possible to  "Solo" more than one track.  In my mind this doesn't make sense (though I realize that for audio professionals they'll recognize this is how their physical mixing boards have always worked).  So I would propose a "Single Out Track" or "Isolate Track" function.  
How would you like the feature to work?
When I click the "Isolate Track" button, I will hear output from that track only.  When I click the "Isolate Track" button on another track, the previous track will be un-isolated and the current track will be isolated.  This would help in isolating audio issues.  This, in conjunction with "Toggle Track Output" would allow me to set up groups of tracks to be output, in order to check my mix on a group of tracks.  But Isolating a single track would help me quickly identify what's happening on the individual tracks.  Un-Isolating a track, I would then hear just the "Enabled" tracks again, until I Enable ALL tracks to hear the entire mix.
Why is this feature important to you?
I shoot reality-type footage.  I shoot 2 or 3 cameras, and I have 8 "actors" being recorded on 8 separate audio recorders.  I do the initial sync using PluralEyes (though I would love to ditch it when Premiere's Audio Sync is fixed).  So I have a multi-cam sequence with anywhere from 5 to 14 tracks of audio.  I ALWAYS have to perform slight adjustments to sync to account for WOW/Flutter effects of shooting on disparate devices.  First, I have to isolate a track (un-solo a track and then solo a new track) in order to A. identify which track is which, for renaming the tracks.  B.  Throughout the edit I am constantly riding the un-solo, solo feature while moving from one track to the next (a lot of clicking) so that I can hear exactly which take picked up the best recording of a particular line of dialog.  Perhaps actor A and actor B are standing close together.  Actor A yells something and his audio clips.  I solo Actor B's track to see if it picked up well enough to use as a substitute for Actor A's audio (un-solo Actor A, solo Actor B).  Sure enough it does.  I make the appropriate edit and then un-solo all tracks, then solo Actor A, Actor B and the ambient track.  I would rather just un-solo Actor B at this point and instantly be listening to the mix of A, B and ambient because I've previously set up "Toggle Track Output" on those three tracks, while moving my Isolated track from A to B to ambient and back off again (returning to whichever tracks have been enabled for track output).
The new interface for customizing which buttons I can see in my audio track header would allow those who use SOLO to use it as they expect it to work (as it currently works).  But I could delete the SOLO button and add "Toggle Track Output", "Mute" and "Isolate Track" buttons to my interface.
Great job on the new CC version.  You have a thankless job, it seems.  When something new releases, we end-users see even more potential for productiviy and the cycle begins again!  THANKS for what you've done already!  Resizing tracks (CTRL +/- and ALT +/-) is AWESOME!!

Similar Messages

  • Move Audio everything Mutes - Solo Bug?

    Move audio everything mutes ..... is this the dreaded Solo bug from a few years back? In Logic X?
    Please tell me I'm wrong

    i havent switched to 916 and 917 becuz i read about the bugs... im on 915, and 10.6.8 operating system
    right now my set of bugs are:
    THE MUTE BUG: where if you accidentaly clicked the SCORE window and hit M, there will be select midi notes though out your ENTIRE project that will muted, this doesn't discriminate on which note, nor velocity.. It is truly random, but for the same instrument, each region will have the same type of muted notes. THERE IS NO UNDO. you literally have to sit for about 30mins, to an hour to sort this.
    THE SOLO BUG: This thread.
    "THE TAB TO TRANSIENTS" BUG: Logic just doesn't recognize a transient on some audio! Incredible... I can clearly see it. I have to take into protools to do "Tab to transients" there. Then bring it back!
    FADE FILE ISSUE: when I save as, or save copy of project. There is a -36 error, where either fades arent updated. Also, some audio tracks regions, simply play of an on... as the play head hovers passed them! at this point my session is RUINED. because it will happen on multiple tracks.
    4 bugs are OKAY I guess.... I didn't feel like adding more to this arsenal LOL... now I see some of you understand my gripe. I have reinstalled my entire OS, gotten a NEW hard drive on my mac pro, still same issue.
    Oh, and my favorite bug!!! When I work at 88.2, and Time+pitch a region, the HARMONIC CORRECTION fails! lol
    I am going to update to 917 and tell u if the bug is there.

  • Premiere Pro CS6 - Warp Stabilizer BUG causes project to crash

    Hi!
    Sometimes Warp Stabilizer causes Premiere CS6 to crash. I found out what steps cause this so hopefully a fix can be made in an update soon:
    1) Add the WARP STABILIZER to a clip. It Analyzes and then is applied to the clip.
    2) TOGGLE OFF the effect in the effect controls window
    3) Adjust the clip duration and RE-ANALYZE while the effect is TOGGLED OFF still and Premiere crashes.
    Happens every time. BUG Report was filled out.
    (If the effect is toggled ON when you RE-ANALYZE it, everything works okay.)
    So why not just not do this? Well, I usually don't but sometimes in the middle of working with hundred of clips I toggle on/off the effect to check certain things and then leave it off. If the clip is adjusted later or I come back and try to click ANALYZE again while the effect is toggled off, everything crashes.
    That's the pop up. If Premiere doesn't allow for you to re-analyze a clip while the effect is toggled off, then the ANALYZE button should not be active or at least a popup saying "Cannot Analyze this clip while it is toggled off". Instead Premiere crashes and upon reopening the project you are forced to rename the project which fortunately is usually fully recovered.
    Running 6.0.2 on a suped up 2011 27" iMac with 16gb ram and AMD 6970M 2gb video card.

    I know I'm piggy-backing on an old post here, but I've just had real issues with a similar thing on Mac. Unfortunately, my Premiere CS6 is crashing and becoming totally unresponsive whenever I simply apply the Warp Stabilizer. The moment I drop it on my clip, BLAM! I get that same pop up you posted. I click 'OK,' and then nothing. Just beachbal of death until I force quit. What's more annoying is that, not only has the camera operator made the stabilizer essential, but I've been using it for the past week with no issues up till now.
    At first I thought I was overloading Premiere by dropping the effect onto two clips at the same time. But I tried it one at a time and had the same problem. My recovery project files seem to be ok, but that's not even nearly the point. I simply can not use a great and essential tool. Help?

  • Premiere Pro CC has a BUG (glitches) when playing XDCAM EX and XDCAM footage

    I work with XDCAM EX footage and since I upgraded to CC all the footage now plays with glitches.  Sometimes it just shows green.  In addition to it the audio goes out of sync if you continue playing.
    I did some research and other people are reporting the same issue but with XDCAM footage.
    Adobe, please fix this bug.  I can't edit anything like this.  Also in the mean while let us, creative cloud members reinstall CS6.  I can't just sit for days waiting for a fix.
    I'll try a doing a clean reinstall of everytjing in the computer but if issue this persists, by tomorrow I'll have to switch back to Final Cut X.

    Maybe Adobe needs to expand it's beta program before release.
    Adobe Premiere
    Multicam edits switch angles when relaunching a project in Premiere CC (probably best to do multicam edits in CS6 for now)
    More multicam quirks
    Update 7-1-13: Adobe has posted a candid response to the multicam bugs.
    Match frame may not match to the correct clip
    Keyboard Shortcut panel is blank
    Audio dropouts, possibly due to image sequences
    Pressing M twice in the source panel adds a second marker instead of editing the first
    Visual corruption when playing XDCAM media
    Several reports of Effects Panel lag
    Premiere CC still losing render files
    Timecode is not preserved when sending to SpeedGrade
    Labels can disappear in CS6
    Importing media files first and then importing an XML can prevent freezes for large XML files

  • Frustrating Mute/Solo button bug?!!!

    I have the most frustrating problem and i'm reaching my boiling point!!!
    I'm trying to sync audio (by hand, because sadly the new 'audio-sync feature' doesn't work right 90% of time).  I hit "mute" on one track and try to go one frame back/forward with the keyboard arrow keys to find my exact sync point, yet as soon as i click the arrow key either way, the Mute/Solo buttons toogle themselves back on/off.
    To be clearer: I mute track 1 and unmute track 2.  Then i press the arrow key on the keyboard to move one frame and as soon as I press that key, track 1 unmutes and track 2 mutes. 
    this doesn't happen always, but certainly happens most of the time i try to sync stuff.  I'm as frustrated as I can be and can't believe I haven't seen anyone else online mention this issue.  Is this some dumb new feature in premiere and if so please please tell me how to turn it off, and if it's a bug - is there any fix for it?
    If I hadn't already spent 2 weeks building this massive project (it's a big feature film), i'd go back to Premiere CS6, but now i don't want to have to re-organize everything again...
    Please help!

    There is a different mute/solo bug which only rears it's head after reopening a project.  You're the first I've seen report something similar while still working.
    You could try trashing preferences, and if that doesn't work, you may want to consider a reinstall.
    https://blogs.adobe.com/genesisproject/2011/02/premiere-pro-cs5-maintenance-two-great-tips .html

  • CS3 versus Premiere Pro 2.0

    I am thinking of upgrading to CS3 from 2.0
    Does CS3 use significantly more processor power and/or memory?
    Any gotchas?
    Will my Pro 2.0 project files open up fine in CS3?

    The general rule for any software upgrade is always the same: ignore the manufacturer's (or reviewer's) claim that the upgrade is a must and study the new features if any. Of course many upgrades may have some new convenience features which may be important for some users (on a deadline for example). In your case, getting Encore may be worth it.
    In the case of Premiere PRO CS3, the main effort by Adobe was to port it to MAC. They made changes to the Premiere PRO engine introducing new bugs and removing some features (short-cuts, etc..) as well as making some 3rd party plug-ins inoperable.
    It is always hazardous to carry a project to a new version. While possible it is never perfect and almost always requires hours of work to remedy. It is always better to finish a project in the version where started.

  • Adobe Premiere Pro CS6 HDV Capture error

    Since the latest update, i'm not able anymore to capture HDV with firewire link from my Canon XHA1.
    MAC OSX Intel 10.7.5
    When it should start capturing I get an error and Premiere CS6 goes on 'freeze'.
    In CS5.5 (wich I kept installed), I don't have this error! But in CS5.5 there was no live view available.. what can be causing this error?
    Help me please!!!

    A cautionary tale:- I too fell foul of the Premiere Pro CS 6.0.5 update bug and kept losing my Firewire Capture. So I followed the advice here and uninstalled Premiere Pro and reinstalled it from the Production Premium disc and then updated to version 6.0.2.
    However, my Mac Pro has now lost all system audio - no Quicktime (”an unknown error -101”), no CD/DVD sound and the iTunes progress bar does nothing when I press play. This bug is detailed by others in Apple Discussion page https://discussions.apple.com/message/18657051#18657051. Thankfully I am still able to hear sound in Premiere through my line out so I can still edit.
    I’m not sure if this bug was fixed as the last submission to the Apple discussion was dated 20 June 2012 and the ‘Branched to a New Discussion’ link at the top of the page goes to a removed page.
    If an update to Premiere Pro could fix this bug (it only appears to happen when Premiere CS6 is installed) as well the loss of Capture, I would be happy.
    Premiere Pro Cs6
    Mac Pro 5,1
    Mac OS X 10.7.4

  • FAQ: How do I submit a bug report or feature request or otherwise give feedback about Premiere Pro?

    The best way to submit a bug report or feature request is to use the bug-report/feature-request form.
    The Premiere Pro team doesn’t  necessarily see and record every post on every forum and social network, but we do see, record, and track every entry  through the the official feature-request/bug-report form.
    It also helps a lot if you opt into the Product Improvement Program.
    Also, be sure to use the crash reporter.
    We really do read all of the bug reports and feature  requests, and the software really does get a lot of benefit from  detailed crash reports.
    Don’t forget about contacting Adobe Technical Support or Customer  Service, too. For information on how to contact Adobe Technical Support,  see this page. (Note that you must register your product before you can open a technical support case for it.)
    If you have tried to get help from our support staff, but the service  was inadequate, I can help you to escalate your issue if you send me  your case number at kopriva at adobe dot com. You must provide me  a case number. I am not offering to solve your problem myself; rather, I  am willing to forward your information to someone if you have already  hit a dead end with our Technical Support or Customer Service.
    If you have feedback about the content of the Premiere Pro Help document,  then please add a comment at the bottom of the relevant page. You can  add comments to add information, to add links, to make corrections, or  to ask for clarification.
    If you want to keep up with the Premiere Pro team, then you can follow our blogs, Facebook page, and Twitter feed and so on.
    Oh, and I can’t resist this opportunity to remind you to update to  the most recent version of the application. Don’t be surprised when the  first thing that you hear back from us is that you need to install the  latest updates. We fix a lot of things in updates, and we don’t want to go chasing bugs that we’ve already fixed. We’ll keep you posted on our blogs, Facebook page, and Twitter feed about updates as they become available.

    Hi qwerty,
    Dun tink that creative customer support sucks cos I had been dealing with them in the past and I can say that their service are quite gd and fast. If you wanted a refund, I tink you need to contact the store that sells you the product. Dun tink creative will refund you though.

  • Flicker footage in Premiere Pro CC 2014.2. Tested on different computers. When waiting for fixes this bug?

    Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different. Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
    It can occur even in the parts without filters !!! But no all time.
    ver 2014.2 - win 7 - intel i7-4770 - gtx 770 - flicker!
    ver 2014.2 - win 7 - intel i7-4770 - Intel HD Graphics 4600 - flicker!
    ver 2014.2 - win 7 - intel i7-2700K - quadro 2000 - flicker!
    MERCURY PLAYBACK ENGINE work fine! But still flickering in preview and render.
    When waiting for fixes this bug?

    Hi Aleksey,
    Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different.
    Have you tried with the Mercury Playback Engine set to "Software Only?" More info please: FAQ: What information should I provide when asking a question on this forum?
    Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
    Is this a brand new project or one you updated from an earlier version? What kind of footage are you exporting? Which preset are you using?
    When waiting for fixes this bug?
    If I can repeat the case here with the same hardware, GPU, and drivers, that would be easier to fix the bug. Currently, I cannot recreate the bug.  If you or anyone else can provide me with steps to recreate the bug, that would help immensely. It sounds like this will be the difficult thing.
    Thanks,
    Kevin

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

  • Premiere Pro CC's Warp Stabilizer BUGS...see for yourself. (7.0.1 & 7.1)

    I'd love to hear from Adobe Staff on this one. Hopefully they can focus on fixes over features for the next update, especially for one it's most touted effects.
    Warp Stabilizer works great at stabilizing clips in Premiere Pro CC...but I'm beginning to learn that it's quite buggy. The two bugs below simply cripple the user experience when you use the effect a lot like we do. Here's a link to a sample project with just 2 clips (around 1 minute in length each) on two separate timelines with each clip stabilized using the Warp Stabilizer effect. It's only a sample/test project meant to show the issue which can be MUCH larger in a longer/bigger project. Relink to any longer media and you'll quickly see what happens when you have multiple warp stabilizers applied to a Premiere Pro CC project and how problematic it can be.
    https://dl.dropboxusercontent.com/u/105331144/Warp_Stabilizer_SAMPLE_Project.prproj
    See for yourself.
    Two VERY Annoying BUGS and One Unfortunate Feature:
    BUG #1: (It affects 7.0.1 and the new 7.1 Release/Update)
    1) With GPU Acceleration Enabled and both sequences open, once the timeline render bar has turned yellow, hit save.
    2) Now toggle to the 2nd sequence and you'll notice a delay/freeze as the render bar switches back to red and then yellow again.
    3) Now toggle back to the other sequence and you have the same thing occur. Then, you can toggle back and forth with no delay...until...the project saves (or auto-saves) again...and then the delay/freeze will happen all over again.
    4) Side Note: Even when you right-click on the sequence in the Project window, there's a delay. Right-click on a sequence with no Warp Stabilizers and the drop down list pops up immediately.
    What's the Big Deal?: When you have tons more warp stabilizer effects applied to multiple sequences, not only does it take a while to save, but when it does, you are forced to wait while Premiere Pro freezes momentarily. This affects AUTO-SAVE too!!! The more warp stabilizers, the longer the wait. Our sequences have delayed up to 30-40 seconds depending on how much we've used warp stabilizer in each sequence. Imagine if you have Auto-Save set to every 30 minutes or less, well that means that every 30 minutes or less you'll be forced to stop while premiere freezes up for 30-40 seconds or so (depending on how much this effect is used). Other effects do NOT have this issue.
    BUG #2: (It affects only the new October Release/Update of Premiere 7.1...this issue is NEW and does NOT occur in 7.0.1!!!)
    1) Take the above project into Premiere Pro CC 7.1 (again, this does NOT occur in the previous 7.0.1 release) and hit FILE>EXPORT>Media.
    2) You'll notice a delay while the EXPORT SETTINGS popup opens.
    3) Toggle to different "FORMATS" in the export settings window and there's more delays every time the format is switched.
    What's the Big Deal?: Again, this is a small sample project. When you have a much bigger project with lots more Warp Stabilizers applied to many more clips this "delay" can extend up to several minutes!!! Yes, on a recent project over an hour with MANY warp stabilizers applied to lots of clips, it took 7 minutes for the Export Settings window to pop up after hitting EXPORT>Media. And there was about a one minute delay now when switching formats. This occurs whether GPU Accleration is enabled or not. It ONLY occurs on Premiere Pro CC 7.1
    UNFORTUNATE FEATURE #1:
    We obviously use Warp Stabilizer A LOT. It's a great effect. The above bugs cripple the user experience. This last issue isn't a bug, but rather a default setting on Premiere Pro's warp stabilizer that should be changed. Within the settings of Warp Stabilizer there's a section called "Method". The default setting is "Subspace Warp". That sounds pretty cool. But in practice, and we have had lots of practice (eg. THOUSANDS of clips stabilized in just the last few months alone (no exaggeration)), we've found that switching the default method to "Position, Scale, Rotation" is a MUCH more effective way to stabilize a clip. Most of the time it cuts down on that "wobble" that you might see in complex moving clips...but more importantly, 9 out of 10 times it crops the video either the same or less than when you use the default method. By "crops less" I mean that the "Auto-Scale %" is less. Of those 9 times, I'd guess 7 or 8 of them would crop in on the video less while the other 1 or 2 times there would be no change to the Auto-Scale %. Less scaling = better.
    What's the Big Deal?: Well, as cool as Subspace Warp sounds, our numbers don't lie. Again, we use this effect on HUNDREDS of clips every week. When you have to go into hundreds and hundreds of clips every week and keep switching the setting so the effect will work better, it gets old real fast. We end up wasting so much time doing this but it's worth it because the results are undeniable. Why not create a CUSTOM PRESET???! Well, that'd be nice if it worked...but it doesn't. The problem with a custom preset like that is that when you drop it on a clip, it doesn't activate/analyze the clip automatically so you have to manually go into the settings and hit analyze which negates any time saved. It's be great if the default "method" was simply changed to Position, Scale, and Rotation. Or at the very least, it'd be great if one could create a custom preset that would automatically activate/analyze the clip it's dropped on (just like the original effect does). 
    (BONUS FEATURE: It'd also be nice to have the ability to set a "max scaling %" too so you never crop in more than a preselected amount...but first things first...fixes over features.)
    NOTE: I'm on a 2011 suped up iMac running OSX 10.8.5

    [r]Evolution wrote:
    Would it help to  Render these Warp Stabaliized clips instead of leaving them in the sequence w/ the Effect applied?
    Any way to "Batch" Warp Stabalize your media before editing so the effect is not needed during the edit?
    Sounds like you guys could benefit from having your shooters use a "Stabalizer".
    Thanks for the rendering tip rEvolution. Rendering the clips does help with BUG#1, however, I'm not sure if it would truly save us any time because of the constant need to render and rerender tons of very short clips with this effect as we make adjustments to the edit. Warp Stabilizer is GPU Accelerated so playback is really smooth which is great but why does saving a project have any effect on this and cause it to freeze up? And then it works great...until the next time the project is saved. Using any other effect, there is no issue (that I've found) when a project is saved or auto-saved.
    Rendering unfortunately has no effect on BUG#2 in Premiere 7.1 (again, this bug/issue did not occur in Premiere 7.0.1)
    Regarding "batch" stabilizing...I'm not entirely sure what you mean. We do stabilize dozens of clips at a time before editing because it's imperative for us to know which clips (the sections we've pulled) will stabilize effectively. And then once the longer edit is complete we end up pulling all the best shots from that long sequence and copy/paste it to another sequence to make a 2nd shorter edit.
    To say we've gone back and forth about the use of stabilizers would be an understatement. The fact is that we've spent almost 4 years creating a unique way to shoot based almost entirely around the effectiveness of warp stabilizer. It's taken years of trial and error but our style of shooting effectively allows us to mimick and thus replace the need for stabilizers, sliders and cranes. The extra freedom allows us to get MUCH more varied coverage of live events. It's different, I know, but it's fun and rewarding having a unique style. Granted the extra work is passed on to the editing side, but it's worth it IMO especially if these issues were addressed/fixed.
    Regarding the "unfortunate feature" I mentioned, I would be satisfied knowing the default method works great for others if one were simply able to apply a custom preset of the clip with the adjusted method and it activated automatically and began analyzing the clip without the need to manually go into settings and hit analyze. That would be nice.
    Thanks again for your input.

  • Bug list and wish list premiere pro cs4

    Iam realy interesting someone, sometime work with Premiere pro cs4 from Adobe team ? I gues not!! Some bug might not seen only people who not work on premiere !!! 2 russian video editing forum named premiere cs4 most worst of version premiere. Old bugs not fixed on premiere cs3 adobe make premiere cs4 with new most worst bugs and some options was remove(Fast export to frame\movie) What for ????!!!!! Cuting the clip i must press 2 button - what for ? Cut it most usful operation and adobe make 2 button press to cut. And domenation effects then adding to clip, please try add some effect to clip then add someone again. Why new effects adds not to last posotion ?
    And time warp, posterize time work only with neast sequence!!! What for !!!Its make work with premiere faster ????
    ADOBE PLEASE WORK YOUR SELF ON PREMIERE PRO CS4 SOMETIME !!!

    FAQ:How/Where do I report a bug?
    Cheers
    Eddie
    PremiereProPedia   (
    RSS feed)
    - Over 300 frequently answered questions
    - Over 250 free tutorials
    - Maintained by editors like
    you
    Forum FAQ

  • Huge Bugs with Many Legs Still Living in Premiere Pro - (Border from Sharpening & Flickering from Adjustment Layer)

    I haven't edited video in awhile.  While working on a new project I've run into a bunch of what I suppose are well known issues in Premiere Pro CC 2014.  It seems Adobe has know about these issues for some time, but that for some reason, nothing is being done about them.  Here is my most recent experience with editing a video using PP:
    1. Found that color correction tools in Premiere Pro for setting White Balance Suck for folks who don't edit video 8 hours a day.
    Searched on web to find solution find that Adobe has no fix but random humans have found hack solution: White Balance in Premiere Pro CC on Vimeo
    The dude shows you how to use the Cyroce Color Neutralizer plugin from After Effects - but sure enough the current version of the plugin that ships with AE CC 2014 doesn't work with premiere any more so you have to download the old version from dude's website here:  http://www.sternfx.com/tutorials/136
    Thanks to the DUDE!
    2. Found out that adding an Adjustment layer can cause flickering in footage.
    Searched on web to find solution find that Adobe has no fix but random humans have found hack solution: PP CC 2014 - adjustment layers flickering problem : Adobe Premiere Pro  AND  Re: image flickering from adjustment layer
    Added mask to control flickering.  More specifically, I turned each effect in the adjustment layer on and off until I found the particular effect that was causing the flickering.  Then I created a mask in that effect which covered the entire frame.  Mystically the flickering disappeared.  Learned that if you make any changes to adjustment layer effects, flickering will return and you have to delete/recreate the mask once again. Ridiculous.
    3. Thought all was good and that I could now peacefully continue to finish my project.  I was wrong.  Found that adding sharpening in adjustment layer causes a small border to form around the entire frame.  The pixels seem faded or translucent or something.
    Searched on web to find solution find that Adobe has no fix but random humans have found hack solution:  Sharpening bug Premiere Pro - - Fourmedia
    So now I've learned that the sharpening effect needs to go on it's own adjustment layer.  Awesome.
    Flickering returns because I made a change to adjustment layer 1.  Re-mask.  Sweet.
    That's it.  Pretty sure this post will help folks out, but man I am going to run out and give another NLE a shot.  None of these operations should be this difficult.  Makes me wonder if Adobe even attempts to use their own programs.  I don't see how anyone could possibly let a huge tool like Premiere Pro suffer from these issues -- and for so long a period of time.  Absolutely ridiculous.  Adobe truly seems to be asleep at the wheel.  This is some amateur crap here.

    Thanks for this post. It would be cool (since Adobe doesn't seem to use their products) if there were more posts like this that I could read before I upgrade. I'm having the flickering w adjustment layer problem you mentioned in #2 - and this post is over month old! Aghh

  • Weird hissing bug in Premiere Pro CS6

    I'm having a very strange problem with audio in Adobe Premiere Pro CS6.
    Whenever I make a cut in an audio clip, a few seconds of broadband hiss is introduced into it after the cut. The hiss is only there in the exported video. It does not appear after every cut but about 10% of them.
    The hiss is equally there when I export into different video/audio formats. It is there when I used different editing codecs. It might only be there for clips I recorded using some not so good microphones on a Canon 5D II, but the hiss only shows up after I make an audio edit and export the video/audio or just the audio. Sometimes though it shows up right away in PP before export. If I clean up the hiss in Audition for a given clip I no longer hear it in PP but again it reappears after export.
    It seems like the problem shows up when editing video shot on a Canon 5D MII with the in camera mic or several shotgun mics, but not with a decent lavalier mic. Changing the edit and export codecs doesn't help the problem.
    (i7 960 3.3 GHz, Win 7 sp1 12GB, Nvidia GeForce GTX 470 1280MB, PP 6.02)

    I have not encountered the "hissing bug"
    But have encountered something similar to what you describe - but with differences.
    When Audio is Cut at a point, that is not a Zero-Crossing, depending on the point on the Waveform, that the Cut was made, there can be a "pop," at that spot. Adobe Audition has the ability to set Cut at Zero-Crossing, but I do not think that PrPro has that capability.
    Now, all of my encounters with a non-Zero-Crossing Cut has been the formation of a Transient, which does sound just like a pop (not a hiss) sound. I have never heard a hiss, and I do not think that what you are hearing, is what I am, with non-Zero-Crossing Cuts - they just happen to appear AT an Audio Cut.
    Still, you might want to look at the Waveform very closely, just to rule out non-Zero-Crossing Cuts, in case that IS causing what you observe, but just producing a different sound, due to the difference in your Audio material.
    Also, have you done a side-by-side comparison in Audition between one of the files with the hiss, and the original sourse file? What differences do you see, where the Cut was made, if so?
    Wish that I had more to offer than a slightly similar problem, with a different sound.
    Good luck,
    Hunt

  • Serious show-stopping bugs in Premiere Pro when exporting

    OK, so first of all, I get that making a video editor is not an easy task. In fact, it's a nightmarish task. One I would never even attempt. However, Premiere Pro CS6 has been worked on since 1992 or so, by one of the biggest and wealthiest software companies in the world, with well paid experts on this very thing. It's supposed to be professional-grade, but bugs like this makes me wonder if it's some sort of a joke. It simply does not do what you tell it to when exporting. I come back to this problem (and similar ones) again and again. It's not me doing anything wrong. It's not me having misunderstood something. It's serious bugs in this software. There is no other explanation. Please look at these images:
    To the left: the video file as it appears in Premiere Pro.
    To the right: the video file as it appears once exported using the "Match Sequence Settings" option.
    What you cannot see well in the images is that the quality is also significantly lower, and it stutters in an insane fashion.
    It does NOT match the sequence settings. I repeat: it does NOT match.
    I know some people on this board are eager to reply quickly, but I would rather have you think this over before. It gets very tiresome to have people shout out the first (incorrect) thought that pops up in their minds. Thank you for respecting that. Please only respond if you know what is going on for sure.

    The "Match Sequence Settings" settings forces Pr to use rendered preview files as a source, instead of the actual source video.  If no rendered preview files are present, it defaults the export settings to the same settings that are used in the sequence to generate the preview files.  Check your sequence settings - you'll see what export settings Pr is using when MSS is selected.  Most likely, it's not what you want or expect.
    I've been told that the Match Sequence Settings check box is working as designed.  I personally think it's confusing and misleading.
    Jeff

Maybe you are looking for