CS6 trimming

What does everyone think of the new trimming tools in CS6?  When I first heard about it, I thought I would love it.  After putting it to the test, though, it kind of drives me nuts.  I use regularly use ripple edits, which used to be done just by holding control while trimming.  When I made my edit and let go of control, that was the end of the edit.  In CS6, the ripple edit tool stays active after you make your cut.  This requires a de-click off the clip.
Now, if you decide to ripple edit Clip A to your liking, and decide Clip B needs a ripple edit, too, you have to click empty space and then make your ripple edit.  The same applies if you make a regular trim and want to switch to a ripple trim.  The original trim type you used stays active.  If the trim tool would simply deactivate after use, I think that would solve this issue.  Is there a way to make that happen by default?
I'm also not wild about accidentally triggering the rolling edit cursor - isn't that what the rolling edit tool is for?
Is there a way to make it behave like it did in CS5?  One of my editing gigs requires cranking out a ton of clips, which relies heavily on ripple editing.  I suspect this is going to slow that process down.
Other than trimming, CS6 has been a huge speedboost in my workflow.

You don't have to de-click selected edit point, just Shift or Alt+Click to change current Edit Mode. To switch between Rolling/Trimming mode use Ctrl+Shift or Ctrl+Alt+Click. Another easy solution is if you have a 4-5-button mouse, you can set a button to perform a "Ctrl+Shift+A" Deselect All operation as I did.
So there are no problems with this really.
Another inconvenience introduced is that when a single clip is trimmed - resulting clip duration not appears in the Info palette because an edit point is now considered as an object and the clip is deselected. Only a tooltip and timecode overlay with trim duration appears. To check resulting clip duration the clip should be clicked after every trim operation.
Other problem that doesn't have an easy workaround is to select a single clip from multiple selected clips.
In past versions - CS5.5 and older - when grouped/linked or simply multiple clips was selected, you could select a single clip with Alt+Click. They broken it and now the only way to select is by making a selection with Alt+Drag and if there are multiple stacked clips on the surrounding Tracks, you have to Lock the tracks just to select the necessary Linked/Grouped single clip. Other inappropriate solution is to Unlink/Ungroup or Shift+Alt+click every clip in the selection to finally select the single clip. Now that's really disappointing.

Similar Messages

  • Re: Adobe Premiere Pro Help | Trimming clips (CS6)

    How do we access just the P Pro CS6 Help Reference instead of all this community content?

    Regarding changes to Help, please read this document first: http://helpx.adobe.com/x-productkb/global/community-help.html
    [Jeff Sengstack]
    How do we access just the P Pro CS6 Help Reference instead of all this community content? When will Help arrive?
    Jeff, this is the Help reference. It arrived the moment we shipped CS6. There is tons of new writing here for the CS6 trimming features here on this page. The documentation covers all the new features. I also have some tutorials plugged in. What is your specific complaint about the page for trimming in CS6? If there is a problem with the content being incorrect, or missing info, I can fix it. I cannot fix the way that the new Help system is designed, however, I can provide feedback to my superiors.
    Also, we've been plugging in supporting community content into Help along with reference content for quite some time so that should be no surprise. We hope it is a help, rather than a hindrance. These articles and tutorials are from authors I worked with during prerelease, so tutorials are vetted, and the content is valid.
    [Jim Simon]
    Can't yet.
    You can access the entire Help system for Premiere Pro here: http://helpx.adobe.com/premiere-pro/topics.html or just press F1. This page (called the "Topics Page"), although different in appearance, has very similar chapter topics that were found in the CS5/CS5.5 Help table of contents.
    The only thing you cannot yet do is download the entire Help system as a PDF. That feature is coming next month: http://helpx.adobe.com/content/help/en/x-productkb/global/cs6-help-pdf-available-june.html
    [shooternz]
    I am kind of staggered that Adobe launched and released without Help Files for these CS6 products. Particularly in the case of SpeedGrade where I needed most Help.  New and unfamiliar applications need Help Files for Users to get up to speed! Adobe are now relying on the cool Tutorial Videos (which have great value) but are hopeless in terms of such basics as "Setting Up"  and trouble shooting.  "RTFM"...What FM? I have put SpeedGrade on the backburner because of this.  (I simply can not resolve some set up issues due to lack of available goto info.)  May not get back to it for sometime actually.
    That's not true, shooternz. Help files are available for every Adobe product. Just press F1. For Premiere Pro, the list of topics (table of contents) is here: http://helpx.adobe.com/premiere-pro/topics.html Keep in mind that this is a brand new Help system, and it took extra effort to complete the content and make sure that the system functioned properly. If there are any problems with the system, please let me know. For example, search needs to be improved and that is something we know about and are working on.
    SpeedGrade Help is sparse because we just got the product 6 months ago. Given our time constraints, there simply was not enough time to develop a full Help system. On behalf of Adobe, I apologize for not being able to provide full documentation for SpeedGrade. I assure you, though, that a full set of Help documentation for SpeedGrade will be available later this year. In the mean time, if you have questions about SpeedGrade, check out the user-to-user forum here: http://forums.adobe.com/community/speedgrade    
    [Jeff Sengstack]
    The issue is not how to access Help (pressing F1), it's how to access the old Help reference. The new Help system is community-oriented and does not include access to the old Help reference file.
    Do you mean you want the CS5/CS5.5 Help without the CS6 content? It's available here on PDF: http://helpx.adobe.com/premiere-pro/archive.html
    The "new community-oriented" Help is not new. We've been adding community content along with the reference content for some time now. If you mean to say the Help is only created by the community, that is totally incorrect. I am the writer for Premiere Pro, I include all the details of the new features, and I cull content to support the writing.
    If one noodles around in community help, one will find bits and pieces of the old Help reference but no single source.
    The previous Help content is included verbatim into current Help. It just has CS6 content added to it. It also "looks different" and is more search based. Again, search the PDF if you need to see the CS5/CS5.5 Help without CS6 content.
    That is unfortunate, because Community Help is a cobbled-together, clumsy means to find solutions. Wheras, when using the old Help reference, it was a lot easier to quickly track down answers to basic questions.
    I would really like to pinpoint what you are missing from CS5/CS5.5 Help. Why is it harder now to find what you need? The main differences I see is that there are no "next page" buttons, or hierarchy links. Is this what is bothering you? By the way, you can return to the topics page by clicking "Adobe Premere Pro Help" in the upper left of the page.
    [Wodehouse]
    I thought something had gone wrong with Master Collection installation because not a single product has any HELP guide!!!!
    Help systems are no longer managed by the Community Help Client and are now handled by the Adobe Help Manager. There may be edge cases where Help might not appear in previous systems. Check the Adobe Help Manager and see if you can have access to the Help that you want. More on the Adobe Help Manager in this thread: http://forums.adobe.com/thread/1000134

  • Audition CS6 deleting/trimming issues

    Hi All,
    I'm experimenting with CS6 in an effort to replace Audition 3.0 which crashes all the time lately. I noticed that several features work different and I can't find the way to make them work correctly.
    - In waveform mode, if I trim a recorded audio file (e.g. cut the first few and the last few seconds of silence), CS6 deletes this time frame in the multitrack session also ("pulls" the file left), thus messing up the file's timing totally. Is there a solution to solve this? Audition 3.0 didn't work like this, and it is very annoying, completely makes impossible to fine-trimming the files. I tried to split the file in multitrack mode and then save it, but CS6 ignores this and leaves the file unchanged. I'm stuck with this problem and no matter what I flag or de-flag in the options, it won't go away. I simply want the program to delete the selected part in the editor mode and leave the rest of the file as it was and where it was timewise. Is it possible?
    - Also in waveform mode, if I save a recorded file on a different name, the program doesn't renames and changes the file in the multitrack session. In the file list the name changes, but I have to manually delete the old file and replace it with the new one in the session, which is simply ridiculous (again something that Audition 3.0 did well and CS6 does a stupid, illogical way). is there a chance to make the program do it as it should work?

    All the information you need about gathering the crash information is in the two FAQs I've linked below, and I'd be inclined to do what it says here before running the cleaner tool. The cleaner tool often clears up installation issues, but as the last line of the introduction says, 'It does not affect existing installations of previous versions of Creative Cloud or Creative Suite applications.' Which means that it won't help you with specific crash situations. The information in the FAQs will, though:
    Audition Crashed.  Now what?
    steps to troubleshoot and get past common problems with Audition

  • FAQ: How do I trim in the Timeline using keyboard shortcuts in Premiere Pro CS6 and CC?

    You can now trim with a lot more keyboard shortcuts in the Timeline in Premiere Pro CS6 and CC. See this article for details: Timeline trimming using keyboard shortcuts in Premiere Pro CS6.

    I'm relieved (if a little frustrated!) that others have the same issues, it makes me feel at least it's not just me! :-)
    I am running Windows 7 64 bit Intel quad core processor 8Gb RAM if that helps Jim?
    Another quick test shows I have exactly the same issues as shooternz and Ann Bens above at 7 & 8 respectively. An audio only or audio/video clip from Bin to SM and I can add markers on the fly perfectly. Audio/video from the timeline to SM works just the same. Audio only from the timeline will not work however.
    I tried linking a video clip to my audio clip to see if that would allow me to add markers then unlink and remove the video... but when I opened that in SM the add marker button was greyed out and the keyboard shortcut (M) didn't work either!
    Curiouser and curiouser...

  • Timeline trimming using keyboard shortcuts in Premiere Pro CS6

    Just wrote a new blog post about Timeline trimming using keyboard shortcuts in Premiere Pro CS6.
    It's in the FAQ now, as well.
    Check it out.

    Good question.  If/when it does it again, I'll check.  However, until you asked that, I never noticed the keyboard layout options and that one of them is CS5.5.  That's an easier fix for me than re-customizing everything, as I was just wanting the CS5 layout. 
    Something else I noticed is that my workspace is set for "Import from Project" and I'm supposing it's possible that the keyboard layout is connected to the workspace and might be either resetting it to CS6 or custom, which may or may not have had those customizations.   About 25% of the projects I'm working on currently are pre-CS6, so every time I load one of those up, it might be making everything else go wonky. 
    In any event, I have a better idea what to look out for now.  Thanks

  • Adobe Premiere CS6 'Create new Trimmed Project' Crash with .MXF files

    Yesterday I started to back up all our students work, and found that the "Create New Trimmed Project" no longer works in CS6 with .MFX files.
    Adobe Premiere CS6.0.3,  crashes when I try to "Create New Trimmed Project" under "Project Manager"
    This only happens when there are .MXF files in the Sequence.
    As we use Panasonic P2 cameras at this university, this is a problem, as this is the format that they shoot in.
    As a test I have made a Project with only one .MXF file placed on the sequence, and it crashes.
    This happens on my Macs and Windows machines with Adobe Premiere CS6 .
    Adobe Premiere CS5.5 works fine, and does not crash.
    Unfortunately I cant save a CS6 project as a CS5.5
    If you don't have any .MXF files to test this,
    You can make your own .MXF files by exporting any video file as "MXF OP1a" or "P2 Movie" Format, (the Preset setting is irrelevant - any preset will cause it)
    P.S.
    Using "Collect files and Copy to new Location" under "Project Manager" works fine, but does not reduce project size as much.

    I also discovered this behavior last summer.  Unfortunately the best (lame) answer I could find was that "Some formats, such as Long GOP based media files, cannot trim media, or add handles."  Source:  http://help.adobe.com/en_US/premierepro/cs/using/WS1c9bc5c2e465a58a91cf0b1038518aef7-7c72a .html
    That's not very specific, but in my case at least (and it sounds like in your case, too) .MXF may be another file type that cannot be trimmed.  If I remember correctly, the answers I got from others was that they were able to export fine.  My machine (and maybe yours) has an issue that nobody else seems to have encountered.  So none of the prescribed remedies allowed me to move forward in this regard.
    After much searching, asking and several suggestions from various Premiere communities, I gave up and moved on. 
    Use Remove Unused and then Collect Files and Copy to New Location.  At least that can help you if you have a lot of clips.  In my case, it didn't help much, because my very short clips were edited from very long takes, so as Premiere sees it, not much was "unused".
    Be aware that "Project Manager does not copy and collect After Effects compositions that are dynamically linked to an Adobe Premiere Pro project. Project Manager does save the Dynamic Link clip in the trimmed project as an offline clip, however."
    Wish I could offer you more.

  • Trimming Clips (CS6)

    This question was posted in response to the following article: http://helpx.adobe.com/premiere-pro/using/trimming-clips1.html

    Apart from this feature issue, to back up the original Help topic, we've put up a free tutorial on using the trim tool in Premiere Pro CS6, by MVP Jeff Sengstack (raise your hand!). The tutorial offers a quick tip on avoiding confusion with the rubber band tool, and then shows a few different ways that trims can be applied:
    http://infiniteskills.com/blog/2012/08/adobe-premiere-pro-cs6-tutorial-trim-edits/

  • CS6 Project Manager is not trimming R3D media.

    Hello,
    I am experiencing another problem with CS6 and R3D media.
    I am trying to move a PPCS6 project to an external hard drive in order to send it out for DI work.
    From Project Manager I select "create new trimmed project" with 24 frames handels.
    Once all the files are processed the resulting new project is huge and none of the clips have been trimmed.
    I tried to create a test sequence, with only 2 minutes of editing to see if the problem could have been solved with a fresh new sequence.
    Unfortunatelly I get the same rusults.
    CS6 is giving me several headackes with r3d media. I have been having several Unkown Errors while rendering or exporting different projects.
    Now I realize that CS6 cannot properly archive or copy trimmed projects.
    This is one of Andrew Davis's links that explains the archival process. Unfortunatelly it won't work woth r3d media:
    http://library.creativecow.net/devis_andrew/Archiving-Projects/1
    Pease let me know If you ever ecountered a solution to this problem.
    If of any help, here is my setup:
    MacPro 12cores
    64GB ram
    RedRocket
    nVidia Quadro
    Media is stored in an Internal raid
    Project Manager is set to export the trimmed project on a regula G-Raid drive with sufficient space and speed
    Thanks!
    Message was edited by: Neonhigh - Tutorial link added

    Not all media types can be trimmed.  In this case, Adobe cant write to the proprietary RED codec.  (You notice there's no RED export options.)

  • No project trimming in Premiere Pro CS6 with MXF files

    as described in http://forums.adobe.com/message/5540575 it works with CS5.5.
    It´s time for a solution in CS6!

    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

  • QuickJog 1.0 - Shuttle/Jog Replacement for Premiere CS6... almost

    quickJog 1.0 - "fixing what Adobe broke in CS6"
    a shuttle/jog replacement for Premiere/Prelude CS6
    * see below for download links and instructions *
    Introduction
    I'll waste no time in expressing my opinion on this one: I loved the jog control in previous versions of Premiere, and a small part of my heart died when I realised that those beloved controls couldn't be reinstated in CS6 (though an ever larger chunk died when I realised that Q and W don't work by default in Prelude... ).
    JKL is great as a concept, but in practice, not very responsive - it's difficult to make precise jumps in speed quickly, and I'd hate to log footage in CS6 using the JKL keys alone.
    It was whilst reading through a different thread on the forums that I had an idea. Why not just jog with the middle mouse button? REAPER uses a similar idea to great effect for scrubbing.
    And so the journey began.
    Installing/using quickJog
    Pre-requisites
    Glovepie is only available for Windows. The script, therefore, only works on Windows.
    Sorry Mac users.
    To use quickJog, you'll need to download the following:
    GlovePie, from glovepie.org. Doesn't matter whether you grab the version with or without emotiv support, as long as it's a recent version
    The quickJog script, from bit.ly/getQuickJog (unreserved thanks go to Creative Inlet Films for hosting this)
    A mouse with a middle-mouse button/clickable scroll wheel
    You'll also need to ensure:
    The JKL keys have not been re-mapped in Premiere. This is essential, as quickJog 'presses' the JKL keys to alter the jog speed in Premiere.
    Installation/usage
    Is currently as simple as...
    Start Glovepie
    From the File menu, select Open...
    Navigate to wherever you unzipped the quickJog script. Open it.
    Click the Run button
    Click the [ .] button at the end of the menu bar to minimise Glovepie to the system tray
    To shuttle, click on the program monitor, source monitor or trim monitor, and scroll the mouse wheel. This functionality is built-into Premiere. You can hold Shift for bigger jumps.
    To jog, click and hold the middle-mouse button over the source monitor, program monitor, or timeline, and move left or right to increase/decrese the jog speed (just like the old jog slider).
    QuickJog tracks the position of the mouse itself, not the position of your mouse cursor, so don't worry about the cursor touching the edge of your screen.
    Keep your eyes on the video, not the mouse!
    To exit, right-click the glovePie icon, and select Exit.
    quickJog works in Prelude too, which is pretty cool.
    Links/Misc
    HOW AWESOME WOULD SOME EXTRA BITS OF INFORMATION BE FOR THE WORLD? Like information on how to tweak the configuration variables??
    Pretty awesome, I'd say James. Have you thought about actually writing this section, then?
    Paha! Don't be crass.
    Aww.

    I stand humbly informed!
    In hindsight, I'm not surprised that the JKL keys are a popular choice amongst editors (especially for those who've moved across from other NLEs), but it does rest somewhat uncomfortably in my heart. It feels like Adobe have replaced the pedals and gearstick in my car with a keyboard: not great for those moments when a child runs into the road.
    The Shuttle Pro (and Bella to my knowledge?) controllers emulate left/right arrow keypresses to do their work, making the playback 'glitchy' during shuttle operations - I don't like that. I didn't particularly like the feel of the Shuttle Pro when I tried it either. I do like controllers like this (I have one), but have been working for some time on interfacing between the Sony 9-pin protocol and Premiere.
    As such, my intermediate preference has been to use a graphics tablet (with a keyboard) for NLE work - hence why having the jog/shuttle controls on screen was so darn useful! Now that I have quickJog mapped to the stylus eraser, edits are much faster.
    Quick aside: Huge commendations on just how much can be mapped to keyboard shortcuts in Premiere, huzzah!

  • CS5.5 Gripes/CS6 Wish List (from the perspective of an FCP switcher)

    I have been a Final Cut Pro user for more than 10 years (starting with version 1.2 on a 500 MHz G4).  Final Cut Pro X is a disaster, but that’s a well-covered topic for a different forum.  After experimenting with Premiere Pro CS5.5 for a few months, I am ready to make the switch for all of my future projects.
    I make a living editing video.  I don’t, however, work for a big company, and I don’t have a lot of money to spend on third-party software or hardware.  Much of my work is shot on DSLRs and delivered online.  That may put me in the category of “pro-sumer” to some, but I wouldn’t be making the switch if I didn’t require a more professional alternative to FCPX to do my job.
    I also don’t think “pro” has to be synonymous with clunky and ugly.  (I’m looking at you, Avid.)  When Final Cut was young, it was fun, intuitive, and sturdy.  It became a robust, professional NLE over time.  I think Premiere Pro is on that path now.
    I like the look, the feel, and the functionality of CS5.5.  It’s not quite Apple-slick, but it’s very much at home on a Mac.  Overall, it’s an upgrade to FCP7 and a very strong alternative to FCPX.  I have high hopes for CS6.
    But this is not a comprehensive review.  It is just a list of negatives:  my gripes, wishes, and personal preferences.  My list of positives would be much longer, but my concern right now is with CS6 and the improvements that I hope it delivers.  As I am new to Premiere, it's quite possible that I am mistaken about certain functionalities or lack thereof, but I thoroughly researched each point in the help docs and forums before posting this.
    My primary system is a 3.2 GHz iMac 21” (2010) with 8 GB RAM, 512MB VRAM (ATI Radeon HD), running Mac OS X 10.7 with external Firewire 800 drives and a DisplayPort-to-HDMI external display.
    MAJOR ISSUES
    Hardware acceleration support for ATI GPUs
    There are rumors that Apple will be switching back to nVidia, but all recent iMacs have ATI and only ATI cards.
    Background rendering (or at least improved rendering options)
    Background rendering is probably FCPX’s most impressive feature and Adobe needs to catch up.  However, even if true background rending can’t be achieved, there should be an auto-render option (after a set idle time), partial rendering (if you cancel a render, keep everything that has been rendered up until that point), and more render options (e.g. render all and render selected). Regarding that last point, I think the whole work area concept should be dropped.  It makes sense for other apps, particularly for animation, but it just gets in the way of more important timeline functions while offering little functionality beyond being a clumsy way to control the area to be rendered.  At the very least, have a way to hide it.
    Full-screen preview
    Maximizing the program frame just isn’t the same (although the grave accent key function may be reason enough to switch to Premiere).  Full-screen preview isn’t just a nifty function for demo-ing sequences.  It’s a big part of the way I work.
    DisplayPort/Thunderbolt out to HDMI
    It may be that a third-party card is required for proper color correction on an external display, but there’s no reason this feature shouldn’t exist.
    Thumbnail images/show frames bug
    This one drives me crazy. I’ve tested this on 3 different Mac systems with various hardware configurations. Thumbnail images in the bins and frame images in the timeline seem to be recreated every time a project is opened, even though the thumbnail image files in the media cache folder don’t actually appear to get rewritten. It’s as if there is no cache at all (even for the most recently viewed bins and timelines segments).  It can’t be an intentional functionality for saving hard drive space because the cache files continue to take up more and more space.
    Open multiple projects simultaneously
    I know that you can cut and paste between projects but being able to open multiple projects at the same time is a very useful feature of FCP7.
    Magic Mouse/Magic Trackpad scrolling
    Premiere Pro is a cross-platform system and impressively so, but there need to be a few Mac-specific interface adjustments, the most important of which is support for the Magic Mouse and Magic Trackpad scrolling.  I use a Magic Mouse.  (It’s an irritating device sometimes, but once you get used to it, it’s hard to live without it.)  When I’m in a window, I expect a flick up or down to scroll up or down -- in every situation, every time, including the timeline.  Unless I stop using all other Mac apps, I will never get accustomed to the timeline suddenly flying left or right when I want to scroll up or down. Also, here’s a chance for Adobe to fix a problem that FCP7 shared:  When you scroll up or down in the effect control window using the mouse, the drop-down effect controls sometimes twirl all over the place if the mouse happens to float over them. As it is, it very easy to throw settings into random disarray without even realizing it just by scrolling through the pane.
    The timeline:  selection indication, icons, and general improvements
    It is very difficult to discern at a glance what, if anything, is selected in the timeline. Transitions always look selected!  Audio tracks should be a different color or otherwise more distinct. There should be an option to show frames only without any text. The icons for track options are small, crowded, and ugly.  Some of the editing icons are too similar, namely edit and ripple edit, although the excellent status bar at the bottom of the application goes a long way towards making up for this.  Simply put, the timeline could use some polish.  Don’t be afraid to steal from Apple on this one.  Keep the tracks; just make it easier on the eyes!
    Conforming audio
    The ability of CS5.5 to work natively with DSLR footage is awesome, but it’s not fully DSLR native if it has to pre-render a major component of the footage before it can play, even if it’s just the audio.
    Media loading
    When launching a project, it can take a long time for all the media in the project to “load” as tracked in the status bar.  I’m sure there’s a reason for this, but since the program is able to determine which source media files are missing before this step (and gives you the option to reconnect them), what is it doing and why must it load every clip in the project, even those not in use by any sequences?
    Page up/page down and arrow key commands
    For starters, the current page up/page down key functions should take the CTI to the next cut in the sequence, not the next cut in the track that happens to be targeted, which can be way down timeline.  In FCP7, I frequently navigated cut to cut with the up and down arrow keys.  I’ve avoided customizing the keyboard commands to match FCP7 --  I would rather endure some hardship and learn the proper Adobe commands -- but this one is flat-out backwards.  The page up/down keys should page through the timeline (left to right and right to left), while the up and down arrow keys should take over the clip to clip function (assuming the targeted track issue is fixed).  Currently, the down arrow takes you to the very end of the timeline, a function already duplicated by and better suited for the “end” key.
    Bin management and clip relationships
    Deleting an item from a bin should not delete it from the timeline, but this is part of a bigger problem, which is the whole master file versus instance versus subclip versus dup clip thing. There aren’t any good indicators regarding the relationships of these clips, and there are few ways to adjust them.  If clips are going to be connected, then they should be fully connected.  For instance, changing the name of a clip in the bin should change it in the timeline.  Adding an effect or trimming should affect the corresponding clips between bin and timeline.  Otherwise, the clips should just be completely separate instances.  I haven’t been able to find an option to turn a clip into an independent instance, although I have to think it exists.  Also, editing an instance of a title does change every other instance of that title throughout the sequence.  I would prefer to be able to edit them separately without having to duplicate them in the title editor.
    Bin effects
    Related to the above, it should be possible to add effects to clips in bins or keep effects on clips added to bin from timeline.  It would also be nice to be able to group effects together in bins for a specific project.  The effects window is better suited for global collections.
    Clearer visual indicators that a clip has been adjusted in the effect controls panel
    Even with the effects panel visible, you have to take a close look to see if there have been any adjustments to the standard settings. An indicator on the clip in the timeline itself would be useful.
    Snapping should include the CTI
    It should also include the blade tool, although the Cmd-K option to cut at the CTI position does make this less of an issue.
    Smoother scrubbing
    Scrubbing is pretty awful.  While this is understandable with native footage, FCPX somehow manages to make this silky smooth at full resolution.
    Color correction shape mask and better color correction in general
    Simplify the primary functions of the 3-way color correction effect.  Keep all the rarely used adjustments out of the way.  I use Magic Bullet for some purpose, but I’ve always done most of my color correction within FCP.  Put the most common adjustments front and center (or up top, as it may be).  The highlights/mid-tone/shadows drop-down is inconsistent in what controls it pertains to.
    FCPX’s color correction is actually one of its more underrated features.  The way it allows you to layer corrections is dead-simple yet as powerful as anything in FCP7 or Premiere.  Stick with the 3 wheels, but rely less on hard to control tonal ranges and add simple keyframe-able shape masks for secondary color correction.
    Better support for shared media access
    AVID is king in this arena and Adobe needs to improve.  It should be possible for multiple editors to safely work on the same project files and share media over a server.
    MINOR ISSUES
    More vertically compact playback/edit control area in source and program panes
    Make room for either a taller timeline or bigger previews.  The virtual scrubber and shuttle controls are the nifty things you drag with the mouse the first time you ever use an NLE and never touch again.
    Larger icons in icon view
    Remember size and position of bin windows
    Playback resolution setting indicator
    There should be an always-visible indicator of the playback res setting in the preview pane that’s easy to adjust without right-clicking.
    Better markers for sequences and clips
    Include colors and more keyboard shortcut control.
    Clip sliding with keyboard commands
    “Opt-,” (that’s Option-comma) should cause a clip collision, not overwrite.  Either that, or “,” and “.” should slide, while “Opt-,” should overwrite.  Opt-arrow should only extend an adjoining clip if in the middle of two clips.  Basically, this whole arrangement should be re-thought.
    Project browser should auto refresh/sort.
    Option-drag on a Mac should always be copy, not move.
    Copy is currently command-drag in the project browser.
    Stop auto-save from interrupting adjustments in timeline.
    Ideally, the auto-save should just be a background function, but it should at least wait until you’re not in the middle of dragging something.
    Add ability to select a cut directly and add default transition.
    CTI control
    If you move the CTI while it’s in play mode, it should continue to play from that spot after you release the mouse, not stop there.
    Show number of frames being adjusted during keyframe adjustments.
    Enable/disable specific effect parameters/keyframes.
    Clearing an effect should clear keyframes as well.
    Or have an option to clear both.
    Position controls
    There should be a preference to make the default position 0.0 x 0.0 (as opposed to 50% of whatever the resolution happens to be), and include a reset button.
    Through-edit indicator in timeline
    And a quick way to join clips, such as a right-click menu option.
    Border controls for images
    Auto save location preference and functionality
    In FCP7 I set the number of auto saves to keep to the maximum of 100 and Premiere can go even higher.  I have always used this feature as an additional backup and archive system, which has come in very handy.  Those files add up, however.  So, I prefer to auto-save to an external drive.  Also, auto saves in Premiere continue to occur whenever there are unsaved changes.  This means that if you make a small adjustment and then leave Premiere for a while, it will keep auto saving the same iteration, which is not only inefficient but leads to my next point….
    Tame the bouncing dock icon on auto save
    While using other apps, there’s no need for the dock icon to bounce every time Premiere performs an auto save.
    More/clearer control over cache locations
    There should also be an option to reset the cache/render file locations to their defaults.
    Export source range
    When exporting, remember the last-used setting of the export source range (or just dump the whole work area thing as I previously suggested).  It’s too easy to cut off a portion of the video when the export defaults back to the work area every time.
    Larger timecode display
    After spending hours and hours editing, the current timecode for clips and sequences is something you want to be able to track without squinting.  Use the letters h,m,s and f instead of colons.
    Simple slug
    Creating a black matte works okay, but it involves a few extra steps.
    Snapping toggle
    FCP allows you to quickly toggle snapping while dragging a clip.  Upon releasing the clip, the snap toggle returns to its original state.  Premiere could use this fucntion, but I suggest something simpler.  Holding down the “S” key should always turn snapping on regardless of toggle state, while releasing it returns it to however it was set before.
    Ability to dock the audio meters along top
    I like to give my timeline as much horizontal space as possible.  I’ve noticed a lot of users keep the toolbar up there, myself included.  I think it would be a good place horizontally aligned audio meters as well.
    More detailed tool tips or hover explanations in preferences
    For example:  The options regarding XMP data should make it clear that the original files will be modified by Premiere.  This caused me problems in other applications.  (After researching these settings, I understand that various Adobe applications use this information to share resources, but it’s still very unclear what the specific benefits are or what functions are lost without this option.)
    More detailed support documents
    The online support documents on the Adobe site very good.  They are nicely arranged and easy to search, but they could be more detailed and offer fuller explanations.  (Peruse the support forums and you will discover all kinds of debates that could have been easily cleared up with one concise line in a help document.)
    Icons and button design
    Icons and buttons are often too small, too similar, and too crowded throughout the interface.  Take some style tips from Apple on this one.
    NEW FEATURE WISH LIST
    Footage auto-analysis:  shot recognition, color correction, and color match
    If only Apple had just added these features and others to the FCP7 framework.  Adobe can do it better though, by using smart folders in addition to the traditional bins that we know and trust (anything besides those dreadful iMovie-style “events”).
    Effect previews
    In the 64-bit era, there has to be a quicker way to preview effects.
    Ability to render in alternate formats
    Namely ProRes or DNxHD.  This would save me considerable time on exports by allowing me to select the “use preview files” option.
    PluralEyes functionality
    Okay, I suppose I should just purchase PluralEyes...again.
    Many, many more effects!
    How about starting with the missing vignette effect?  Just because an app is “pro” doesn’t mean you should have to custom build every effect.
    Many, many more looks!
    Will most of them be cheesy looks I would never touch?  Sure...but give me some templates to play with before I tweak the look down to my exact specifications.
    More speed!
    FCPX, for all its flaws, blazes on any modern Mac.  This probably comes back to hardware acceleration, but while Premiere Pro on a Mac isn’t slow, it doesn’t blow you away.

    You hit the nail on the head, Peter.
    I recently started giving Premiere Pro CS5 a try, and was shocked by the amount of bugs and usability issues. I'm not even going as deep as you in the features, but the most glaring evidence of the lousy interface is that timecode offset bubble that appears everytime you move a clip in the timeline... the bugger appears just under your mouse pointer and won't go away, so if you try to just move a clip down a track quickly, and let go of the button ONTO the bubble, it acts as an obstacle and your drag/drop fails ! seriously, Adobe... don't tell me nobody has stumbled upon this one during beta-testing ?
    Ditto on the autosave that basicly interrupts anything you're doing. No background saving in 2011 ? At first it bothered me to no end so I disabled the autosave. And then a few hours later, Premiere crashed, and didn't even try to recover my work. I lost 2 hours of intricate work. I put autosave back on, and learned to endure the constant, annoying save dialog. And it's not like the save process is instant... even the simplest of projects takes 5 to 10 seconds to save... on an SSD... come on... let me work already...
    Of course, a headache-inducing implementation wouldn't be complete if the autosave didn't trigger even 30 seconds after a manual save. If I choose an interval of 5 minutes, just autosave 5 minutes after a manual save !
    In thumbnail view, you can reorder the clips manually. It's all fine, but you can't reorder them by name or date or length, unless you switch to list view and of course, lose the thumbnails.
    Dragging and dropping a clip in thumbnail view is a chore, because the palette doesn't scroll when the mouse reaches the edge. You know, when you want to move something at the top all the way to the bottom... so you have to drag, let go, scroll one screen, drag, let go, scroll one screen... it's a joke. Even the timeline can do it. Heck, it's a software standard, nowadays.
    Renaming a clip and pressing ENTER takes you back to... the top of the folder !?! How many times I've renamed files that were at the end of the thumbnail view, and for each clip, I had to scroll back down. Time waster.
    Want to locate a clip from the timeline, in the project ? the locate function takes you to the folder. But not to the file, you have to navigate towards it manually.
    Ditto on the up/down arrows. I haven't found a way to jump from cut to cut like in FCP7. How often do I need to jump to the starting/ending points ? much less often than jumping to a nearby cut.
    How come I can't reorder filters in the effects pane ? sorry, I can actually reorder the filters... provided I take them from the bottom and move them up. Moving effects down doesn't work. It's driving me crazy.
    Conforming happens more or less anytime. Without reason. And even if the Media Cache is already full of conformed files.
    When moving the boundaries of the work area, no timecode/offset appears. You need to let go of the button and THEN hover, then you'll know the exact time/duration.
    Try scrolling up in the timeline, it scrolls to the left (which is stupid, it should scroll up). Now scroll up on the tabs of a palette : they scroll to the right !?!
    Can't select an active track. Direct consequence : copy-pasting a clip overlaps anything that's on track 1. Say I want to duplicate clips on the same track... I can't do it.
    Copy-pasting between projects doesn't keep the transitions, only the order of the clips.
    Have you tried doing a frame freeze on a reversed clip and setting proper in/out points for the freeze ? Good luck.
    "Duplicate" command, when you right click on a thumbnail, is way too far from the cut/copy/paste commands at the top, even though they're quite related.
    The other day I transcoded footage with different audio parameters. Just the audio had changed. Upon opening the project, Premiere wanted me to locate the files, which I did. And it failed miserably. Instead, I opened the project ignoring the missing files, and then re-linked them. I pointed Premiere at the first missing file, and had to confirm the replacement. Premiere saw all the other missing files in that folder, and began prompting me FOR EACH SINGLE FILE !!! two hundred and forty three of them, precisely. Can't I have a "yes to all" button in 2012 ? and why does the relinking work inside the project and not when you open a project ?
    That was just from 3 days with Premiere Pro CS5. I still can't believe it. Just to think people bashed Final Cut Pro X, praising Premiere in comparison... Sorry, but they both have serious issues. And Premiere doesn't even have the excuse of novelty.

  • Premiere CS6 Still Has a Long Way To Go

    I'm in commercial editing and work as offline editor, assistant editor and compositor.  I've been using Premiere Pro ever since FCPX came out, but not in the workplace as an offline tool because of certain major missing features:
    - a good EDL exporter (absolutely essential in a commercial pipeline where we're bouncing sequences to grading suites and Flame all the time)
    - dupe detection (essential for prepping sequences for grading)
    - timecode overlays in the monitors
    - colored markers
    - marker overlays (to quickly see what the content of a marker is when scrubbing in the timeline)
    - searchable markers (great when needing to find one line you know you had marked)
    - a visual keyboard settings editor (FCP and Avid got it right, Premiere is a mess, although improved from CS5 which didn't have the ability to search for commands)
    - the ability to rename clips to match file names (can't tell you how many times I use this in FCP)
    - use of CMD X, C and V for cutting, copying and pasting marked selections in the timeline without adding in/out points
    - match frame edit indicators
    - heal match frame edit function
    - timeline to timeline editing.  Not expecting what Avid offers, which is enhanced by the ability to toggle your timeline between source and record, but to be able to do what FCP7 does by letting you edit with clip data, i.e. edit your track layout and edit points from a sequence in the viewer into the timeline.
    I'm super disappointed that not a single one of the above features has been addressed in Premiere Pro CS6.  I think the dupe detection, timecode overlays, and EDL export are the biggest disappointments. 
    For a little clarity on the EDL issue, every editor and assistant I know renames clips after they're imported into the project.  They don't use the "Scene" and "Take" metadata tags, because they want the clip name on the far left of the project window.  This isn't so much of an issue in Avid, but that software is on a different level.  Anyways, in Premiere, once you rename a clip, that's the way the clip name is going to come out out in the EDL.  This is a massive problem for Alexa and RED jobs, which is most of what I work with, because timecode isn't going to be unique to a clip on a multi-day, multi-cam shoot.  In FCP7, you have the option to export your EDL with either clip or file names.  Alternatively, you can select all the clips from your edit and choose "Rename Clip to Match File Name."  Premiere has none of these options.  The only workaround is to go through every clip in your edit, reveal in project, bring up the properties, copy the file name that's there, then paste into the clip name.  This is not a workable solution for a 60 second commercial with an edit every 12-48 frames.
    While Speedgrade is lovely, no one is going to convince Company 3, The Mill, MPC, Light Iron, or New Hat to switch from Resolve, Scratch, Baselight or Pablo.  And to get stuff into those systems, EDLs are still the preferred method when you talk to the assistants who are loading the projects.
    On the good side, it's great to see improved playback stability and scrubbing, the new audio meters are great, adjustment layers are a big help, the marker tab in the project pane has a lot of potential (why not make it searchable?), and the new trim tool is GREAT and right on par with Avid.
    With the exception of the playback control, though, I would trade all of the above improvements to have the hit list above taken care of.  Adobe seems to have added some very good big picture, high profile improvements.  It's the little things that you encounter every day in a long edit that really need some attention now.  PLEASE give a look to this stuff.
    I had really hoped I'd be able to use PP CS6 as an offline tool in my pipeline, but that's not going to happen.  Nor do I know any editors or assistants in commercial post in LA who will want to work without the above features.
    If anyone has some insights into the above features and maybe making these things work in CS6 as currently released, I'm open to hearing them and hopeful that there are workarounds. 
    Thanks and have a blessed day!

    The command copy, cut paste don't work unless you add edits to create a
    discreet clip.  You can't simply copy from an in to an out point.  The
    workaround is to add your markers, use lift or extract, undo to clear the
    damage you just did to your sequence, then paste the clipboard contents
    that you still have from the lift or extract operation.
    Regarding Speedgrade, it appears to be in its infancy and has a promising
    future, but what you get for free from Davinci Resolve Lite is wildly
    awesome.  It does everything the $1000 version of DaVinci does except
    stereoscopic color, network rendering, shared projects, and shared memories
    between projects (i.e. power mastering).  So, for free, you have a blazing
    fast color grade suite with the identical toolset actively in use by
    Company 3 and The Mill.  Add a panel or two and you're really rockin and
    rolling.  We use it at the shop I'm freelancing at now and it can burn
    through dailies transcodes (still essential for Red and Alexa), at about
    40fps.  Awesome.
    I think choosing between Avid MC and Premiere is strictly a "what do you
    need it for" question.  The main problem with Avid is now and always has
    been the hard import aspect.  AMA works kinda ok, but I know no one who
    starts and finishes a project strictly with AMA.  Plus it doesn't work on
    an average laptop without a lot of herky jerky playback, even at 10:1, and
    at some point on a long edit, you're likely going to be working off a
    laptop.
    The ability of Premiere to ingest ANYTHING immediately, including DPX
    sequences, is phenomenal.  If you don't want to wait for AJA, Blackmagic
    has some excellent and more affordable video I/O solutions that work with
    CS6 right now.  The playback is so much better than CS5.5.  I think the
    reason why it was a problem before was because it's trying to play nice
    with anything as it is.  FCP needed everything to be a quicktime.  Avid
    needs everything to be MXF.  Premiere says "come one come all!" and that's
    a tall, tall order.  Now it's working great and the Adobe folks should be
    lauded for whatever engineering magic they used to make this happen.  Huge
    timesaver, especially in finishing when I need to bounce more complex comp
    work to Nuke and back.
    The second thing that Premiere kills at is effects work, even though it's
    not so much Premiere as it is After Effects.  Avid has nothing there close
    to this.  Animatte?  Spectramatte?  Give me After Effects any day.  So, you
    can offline AND online a project with the Premiere and After Effects combo.
    Awesome!
    The biggest shortcoming Premiere has, I think, is it's audio filter suite.
    It's a huge liability and something I hope they devote a lot of attention
    to.  The way Avid can't match the Premiere/After Effects duo,
    Premiere/Soundbooth cannot match what Avid has built in.  The Audiosuite
    effects seemed to be designed to give you a bit of ProTools within your
    NLE.
    I think the best solution, at least until Smoke 2013 comes out this fall,
    seems to be to choose the app that is best suited for your project.  I
    don't think the conversation should be about one program wiping out another
    one, which it seemed to often be the tone of Avid vs. FCP debates.
    The more I play with Premiere CS6, the more I like it.  I used 5 and 5.5 on
    commercials a few times and felt like the software was getting in the way,
    particularly toward the end when I needed to generate EDLs and OMFs (I
    haven't tried the OMF export out of Premiere CS6 yet, but it can't be worse
    than 5.5 - my guess is it's no better though, based on what did and did not
    get improved).  It was fine for finishing, but you'd have to work around
    playback issues all the time, which got a bit embarrassing with clients in
    the room.
    I think CS6, for it's numerous shortcomings - none of which are
    catastrophic or deal-breakers - provides an excellent foundation on which
    to build something that could definitely one day pick where FCP7 left off.
    Smoke 2013 is the storm on the horizon, though, if you ask me.  But
    competition is GREAT and I actually hope Blackmagic joins the game as well.
    The more the merrier!

  • Premiere CS6 Unknown Error in Rendering & Export

    Hello,
    this is an ongoing problem that persisted on any version of Adobe Premiere Pro I worked with, including CS5,5.5 and the latest 6.
    I am stuck with a feature film on a CS6 Timeline, getting an Unkown Error during rendering and Media Encoder exports. 
    I get the same error if I attampt to create a new trimmed project with Project Manager.
    I am aware that this is one of the most common problems in this forum, and before opening a discussion I tried everithing I could:
    - Replace the media at the point of the error/crash (even though the error seems to happen randomly in dirrerent portions of the timeline)
    - Disable MPE
    - Reset Secutity and permission on files
    - change hard drive
    - Create a new sequence
    - Disable second monitor
    I have to bring an export of my film and a new trimmed project by tomorrow to a color house and I am currently stuck.
    I managed to render the entire timeline before exporting. Redering would stop randomly, generating the same "Unkown Error in Copiling Movie".
    Although I rendered the entire timeline by creating different IN-OUT with the work area selection.
    After a long and tetious rendering process I managed to have the entire timeline "green" and ready to go.
    I figured that this way the exporting process would have been successful. Unfortunatelly not.
    I switched to Premiere Pro for its ability to edit R3D media, but what's the point if we cannot export the project? And neither trimm it to a file that I can give to a colorist?
    Here some details of my workstation and source media:
    - MacPro 12cores 64Gb ram
    - Internal 6Tb raid for source media
    - 4Tb Dulce Scratch drive
    - Editing 4K and 5K R3D Media natively
    If anyone found a solution to this problem, please help.
    Thanks

    Hi Neonhigh,
    If you are going to color correction, why do you need an output? Aren't they color correcting the native files?
    I need an output as reference for the VFX department, I need an output for the sound designer, I need an output for the producer, I need an output for myself and to send to my girlfriend. The question I should ask you is, why shouldn't I need an output?
    What's wrong by exporting my timeline in a format that is not r3d files for reference and production management?
    I was talking about color correction only, as they usually only need the native files. Of course, an output would be necessary for all the other things you mentioned. Nothing wrong with that.
    Neonhigh wrote:
    If you need an output for some reason, why are you rendering at all?
    As I explained I simply rendered because the software was having several random "Unkown" problems in exporting. I though rendering and exporting a file matching the timeline settings would have solved those annoying Unkown Errors, giving me at list an export based on the render sttings.
    Problem is that PPro CS6 fails also to render the timeline, and I needed to break the process in 30-40 segments in order to achieve a complete rendering.
    Rendering in Premiere Pro is primarily for playback, and not necessary for output. In fact, it's a waste of time in most cases. Render files are typically not used for an output unless you explicitly want to do so. Typically they are lower resolution "preview" files that you don't want to use.
    Regardless, you should have no trouble rendering sections of your Timeline. Are you updated to Premiere Pro CS6 (6.0.2)?
    Can you try an export without rendering?
    I wish PPro CS6 was reliable enough to allow me to simply export.
    I still did not solve the problem. Several people from the redusers forum are trying to help me as and they all ran into the same issue.
    Currently this are the issues:
    - PPro does not render the entire timeline
    I'm trying a test project right now and so far it is rendering OK. Can you point me to the reduser forum post where people were giving you assistance?
    - does not output the entire timeline (if not chopping it in 12-15 parts)
    I'll test that, as well. You should not have to segment the sequence in order to get an export.
    - Project Manager does not trim the project to pass it to over post prod facilities.
    Sorry, the Project Manager will not consolidate every media type. It will copy, however. This would be a feature request or bug report: http://www.adobe.com/go/wish
    Beside questioning me with why I want to render or export my project,
    Not questioning your capabilities or talents, I just wanted to know what you wanted to do, and why. Typically, most people don't render as much in Premiere Pro as they do in other NLEs and I was wondering why you needed an export to go to color correction. That's all.
    Many users in this forum (as well as on the entire internet) experienced th same Unkown Problem:
    http://forums.adobe.com/message/4661398
    There could be many different variables which can cause that error. The troubleshooting doc you found addresses many of those. I will add the "Unknown Error" warning to the document.
    There is no "single fix" for this problem, I'm afraid, and these are our opinions and solutions on the matter.
    A legitimate gripe would be that the error is too generic, and I would agree with you there. The error should contain more details about how to remedy your issue. Please make a feature request for more descriptive error dialog boxes: http://www.adobe.com/go/wish
    I will also mention it to the product team.
    I understand that, being an "Unkown Errror" Adobe does not have a iniversal fix, but please don't ask me why I want to output my timeline.
    Again, I was only asking in the context of color correction. Of course, you want an output for various reasons.
    I've written up your bad experience in my case notes and I'll do my best to get you some better answers to your questions. You definitely should not have to jump through hoops to render or export a .R3D sequence.
    Neonhigh wrote:
    Here is a temporary fix for who runs into this problem:
    Yesterday, after trying everything I could think of I simply exported an XML, opened it in Final Cut Pro and exported all the files and formats that I needed. No Unknown Errors.
    Thanks for the workaround. I'll add it to my notes.

  • Cannot edit MPEG-2 in Windows Photoshop CS6

    Just upgraded to Photoshop CS6 and am attempting (unsuccessfully) to edit some MGEG2 content. The video content has been extracted from Windows DVRMS files using DVRMStoMPEGGUI. I can work with H264 content in Photoshop without a problem.
    All MGEP2 videos play fine with both Quicktime and Windows Media Player.
    Here  is what happens when I try to edit the file in Photoshop
    File is read by photoshop and all looks fine. First frame is shown as expected.  (see screenshot below)
    If I try to play the video in photoshop, the elapsed time counters at the bottom give the impression that all is well, but the video does not play.
    Attempting to trim the video does update the overall timings of the video, but the first frame is still displayed.
    Rendering the video as H264 appears to work - the export dialog appears and a file does get created. THe H264 file export is playable, but consists of the first frame  displayed continually for the duration of the video..
    I've checked through other discussions regarding editing MPEG-2 video content in Photoshop and another thread suggested checking that the video content is playable via Bridge. Like with Photoshop, Bridge displays the first frame of the MPEG2 in the thumbnail, but attempting to play it locks up Bridge completely.  Doing a "Reset Settings" with Bridge made no difference.
    Any suggestions about how to troubleshoot this further?
    Here is my setup
    Adobe Photoshop Version: 13.0.1 (13.0.1 20120808.r.519 2012/08/08:21:00:00) x64
    Operating System: Windows 7 64-bit
    Version: 6.1 Service Pack 1
    System architecture: Intel CPU Family:6, Model:10, Stepping:4 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
    Physical processor count: 4
    Logical processor count: 8
    Processor speed: 2660 MHz
    Built-in memory: 24567 MB
    Quicktime 7.72.80.56 + Quicktime MPEG2 7.60.92.0
    Bridge 5.0.1.21 (x32)

    Thanks for the quick response guys - I appreciate you taking the time to respond.
    Whilst I understand that there are complexities in dealing with MPEG2 content, and using another media format is certainly an option to work around my issue, MPEG2 is listed as a supported file format.
    To dig deeper intop the issue, I thought I'd see if I could read any MPEG2 content at all. I've tried downloading a random sample of MPEG2 content from the net - those that Photoshop read exhibited the same issue. That means that I'm either very unlucky with the MPEG2 samples I've picked, or there is a problem with my setup. 
    Do you happen to know of some MPEG2 content on the net that will work with Photoshop CS6? If I try that and it doesn't work for me, it means there is an issue with my setup. If it does work, the problem lies with the files I'm trying to edit.
    Bill - you suggested I post thew output from MediaInfo. I've included it below
    General
    CompleteName                     : C:\Users\Public\Recorded TV\As You Like It.MPG
    Format                           : MPEG-PS
    FileSize/String                  : 2.46 GiB
    Duration/String                  : 1h 59mn
    OverallBitRate_Mode/String       : Variable
    OverallBitRate/String            : 2 948 Kbps
    Video
    ID/String                        : 224 (0xE0)
    Format                           : MPEG Video
    Format_Version                   : Version 2
    Format_Profile                   : Main@Main
    Format_Settings_BVOP/String      : Yes
    Format_Settings_Matrix/String    : Custom
    Format_Settings_GOP              : M=3, N=24
    Duration/String                  : 1h 59mn
    BitRate_Mode/String              : Variable
    BitRate/String                   : 2 633 Kbps
    BitRate_Maximum/String           : 15.0 Mbps
    Width/String                     : 720 pixels
    Height/String                    : 576 pixels
    DisplayAspectRatio/String        : 16:9
    ActiveFormatDescription/String   : Letterbox 16:9 image
    FrameRate/String                 : 25.000 fps
    Standard                         : PAL
    ColorSpace                       : YUV
    ChromaSubsampling                : 4:2:0
    BitDepth/String                  : 8 bits
    ScanType/String                  : Interlaced
    ScanOrder/String                 : Top Field First
    Compression_Mode/String          : Lossy
    Bits-(Pixel*Frame)               : 0.254
    StreamSize/String                : 2.20 GiB (89%)
    Audio
    ID/String                        : 192 (0xC0)
    Format                           : MPEG Audio
    Format_Version                   : Version 1
    Format_Profile                   : Layer 2
    Duration/String                  : 1h 59mn
    BitRate_Mode/String              : Constant
    BitRate/String                   : 256 Kbps
    Channel(s)/String                : 2 channels
    SamplingRate/String              : 48.0 KHz
    Compression_Mode/String          : Lossy
    Video_Delay/String               : -14ms
    StreamSize/String                : 219 MiB (9%)

  • Make a simple "cut" edit in a singular video in CS6 (one video file as opposed to multiple clips).

    I want to be able to do simple editing in CS6. I just spent three hours watching tutorial videos and reading help articles and this forum. I have never used an Adobe video editing program before. I normally use Windows Movie Maker, but it's too simple for my current needs. (Eventually I will learn effects.)
    My problem is that the tutorial videos show examples where there is more than one "clip" being placed on the timeline. That seems to pre-set editing points. I only need to import one longer video file and then cut out frames that I no longer want in the video.
    I have figured out how to set start and end points on the clip, as in at the actual beginning and actual end. But following every single method described (JKL, etc), I still cannot seem to edit frames out of the middle of my videos. I assume this is because I'm missing some very simple method for setting edit points. This is what I need to know.
    I am an extreme novice with this program though I'm somewhat computer savvy. So please no jargon. I know nothing of this program. I did all I could to find my own answers before asking here, but if this is answered somewhere else, please direct me there. Thanks.

    I'm in a similar boat -- editing family video recorded on Hi8 and captured into DV with a Canopus ADVC-300. I typically have a 2 hour clip in the timeline.  I'm separating these into clips with the razor tool, but sometimes I want to remove a garbled few seconds from within a clip.
    Today I discovered something nifty: in Keyboard options, there are two items that don't have a key assigned:
    Application->Ripple Delete->Ripple Trim Next Edit to Playhead
    Application->Ripple Delete->Ripple Trim Previous Edit to Playhead
    I assigned these to the Shift+] and Shift+[ keys.   Premiere didn't warn me about these keys being assigned already, so I guess it's ok.  At first, I used '}' and '{' but I'm afraid that it is too easy to accidently hit them.
    When I play back in the timeline, at the start of the garbled area I want to remove, I hit Ctrl+K to add an edit point (the "out point", I suppose). Then I continue playing.   When I reach where I want the video to resume, I just press Shift+[ and Premiere ripple-deletes to the edit point.
    This does leave me with an edit point, though.  I have yet to figure out how to splice the two clips together again.
    I'm sure the pros won't like this, but I find it makes things easier.

Maybe you are looking for

  • Firefox will not update for my MAC 10.6.8. I've tried and tried! I still have Firefox 16.0 and my bank requires an update. Please help.

    I see other people have this problem and hope there is a solution. My Firefox browser is stuck on 16.0 and nothing happens when I try to update. It seems to download, but I'm still on 16.0. I have tried every which way to update my browser. Now my ba

  • SOAP to SOAP scenario without using ccBPM(PI 7.3)

    Hi experts, We have a requirement. SOAP1-> SAP PI->SOAP2 (Synchronous), and after getting the response from SOAP2 we need to do a lookup in SOAP3(Using values from both SOAP1 request and SOAP2 response). We don't have ABAP stack in PI 7.3 Any idea, h

  • How to get refund?

    Dear Whom it may concerns, My skype account was hacked on 2012, JAN. Skype officer said that they will refund money to me and send email to contact me several times but I didn't receieve refund from skype. So, I want to know that when I will recieve

  • EJB newbie -- do i need to create the database?

    I know this may seem an odd question but do i need to create a database and create all the tables with commands such as: CREATE TABLE (...)? or will the deployment descriptor do that for me? clarkie

  • Uncaught exception error message

    Upon reboot the following error message appears: application registry. wait for timeout (Oxbfca09409ffe99e5) Once the alert message has cleared nothing is working correctly. The BB Platform is there to stay and won't let me exit it.