Bugs Premiere Pro - A qui le faire remonter ?

Bonjour,
je suis monteur permanent dans une société de production audiovisuelle spécialisée dans la captation de concert.
Nous sommes passés il y a peu à Première. Le soft est vraiment bien fait mais j'ai repéré quelques bugs et certaines fonctionnalités qui pourraient clairement être améliorées sur le soft.
A qui faire remonter ces remarques ? Est-ce que le forum de Premiere est suivi par les développeurs du logiciel, est-ce utile de poster une discussion ou je n'aurai que des retours d'utilisateurs ?
Merci pour tout.

Pour moi, le formulaire est en anglais et c'est impossible de le poster en français. (j'ai eu confirmation du SAV).
- Alors j'ai un sacré problème d'affichage lors des montages en multiplan, en voici un exemple : bug multi - YouTube . Je me mets en lecture, et voilà le problème. C'est très très contraignant, je suis obligé de passer par les réglages de la fenêtre programme, passer par un mode de forme d'onde et me remettre en lecture multiplan pour que tout fonctionne correctement. Assez fastidieux.
- Sinon je ne comprends pas comment il est possible d'aplatir un plan mutlicam et ensuite avoir la possibilité de le re-rendre multicam. Après avoir fait des recherches en anglais, il est impossible de le faire apparemment, ce qui est contraignant.
- Et sinon, voilà plusieurs projets que je monte, qui font plus d'une heure (dans les environs d'une heure trente) et la navigation dans la séquence se fait très mal (en voici un exemple : lenteur projet - YouTube , vous ne voyez malheureusement pas quand est-ce que j'appuie sur mes raccourcis de zoom et dézoom, mais il y a bien au moins 8 à 15 secondes d'attente entre le moment où j'appuie sur ma touche et le moment où ma timeline bouge). Et la vidéo n'est pas au ralenti ...

Similar Messages

Je n'arrive pas à lancer adope premiere pro, que dois je faire?

je n'arrive pas à lancer adope premiere pro, que dois je faire? J'ai pourtant installé quick times player 7 pour pc
Merci de prendre soin de ma requète

What error message do you see?
What is your exact brand/model graphics adapter (ATI or nVidia or ???)
What is your exact graphics adapter driver version?
Have you gone to the vendor web site to check for a newer driver?
For Windows, do NOT rely on Windows Update to have current driver information
-you need to go direct to the vendor web site and check updates for yourself
ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us
Do you have dual graphics adapters?
Go to the Windows Control Panel and select Hardware and Sound and then select Device Manager... In Device manager you click the + sign to the left of Display Adapters... and see if 2 are listed
IF YES, read below
-http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
-http://forums.adobe.com/thread/1001579
-Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
-link to why http://forums.adobe.com/message/4685328
-http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
-HP Fingerprint/Password conflict http://forums.adobe.com/thread/911575

Premiere Pro CC not playing fair with .mov files

I have a CC account and use Premiere Pro on my PC with no issues so far except that the RAM and Graphics card suck. So I decided to run on my laptop running windows 8 rather than 7.
AE runs with no issues (so far), but when I use Premiere Pro it does not like .mov files for some reason.
I imported files from my iPad and it gives me this message:
Error Message
"The FIle Has no Audio or Video Streams"
To work around it for now, I converted the file into mp4 and imported to edit from there. Now issue is that we need to place a lower third. I have an AE project as the .mov file imports into that no problem, but when I then export as quicktime file for the alpha channel it still will not import into Premiere Pro, same error message.
I can export as .avi but then the file screams 'MASSIVE' as it is over 1.5gb cpmpared to the 32mb as a .mov file.
Bottom line, cannot get any .mov to import into PP on my laptop even though it works fine on my PC. Also, .mov files play fine in AE??
Please HELP
Martin

Hi MartinSalteruk,
Thanks for contacting Adobe Forums,
As I understood you are only getting issues with .mov files, Please check if you Quicktime player installed on the system.
if not click here to download the Quicktime player
Regards,
Sandeep

Super annoying bug: Premiere Pro CC (and probably older versions) encoding/exporting window keeps stealing focus while working

This is something that has caused me to lose a lot of hair due to pulling it:
1. Open Premiere Pro on Windows (8.1, but that hardly matters, I think).
2. Open some video.
3. Export (encode) it to the desktop. The encoding/exporting child-window starts showing the progress bar as it works.
4. Click the bottom-right corner of the screen to show your desktop.
5. Now open any folder on the desktop, such as a dir called "test".
6. Does the Explorer window showing the "test" dir open, as expected? Nope! Instead, Premiere Pro goes: "HEY! What's up?! I'm gonna push myself in front of everything and show you this export/encoding child window as well as the main Premiere Pro window in front of everything! What do you think about that? Heh-heh! Whatever you tried to open is now in the background and I'm in the foreground!"
For the entire remainder of the encoding/exporting process, which can sometimes take hours, I am therefore crippled and cannot do any real work on my computer because Premiere Pro insists on force-showing itself against my will whenever I try to do anything else. This makes working with the computer while Premiere Pro is working (when I can't use the program anyway!) impossible. I'm left to Alt-tabbing around applications if I want to be able to do anything at all.
Without a doubt, I'm not the first person to be annoyed by this. In fact, I'm 99.99% sure that Adobe is well aware of this. Still, I have to make an attempt at reporting this, because it's crippled me every day for the last few years and made me really, really angry. I primarily associate Premiere Pro with frustration and anger at this point. I really hope there is a hidden preference to turn this madness off or something.
I predict that somebody will be tempted to respond with something along the lines of: "Use the Media Encoder!". Well, I don't like the Media Encoder. I want nothing to do with the Media Encoder. I just wanna use Premiere Pro and not have it steal focus against my explicit wishes.
Please tell me this is possible somehow. And please don't tell me to report this to Adobe with some form. I'm reporting it here and now, thanks. Plus, once again, I'm sure they know about this already. (If they don't, they aren't using their own software.)

I only asked two questions of you!!!
Both of them intended to get to a solution for you from understanding your workflow... .
Sheesh.
Don't understand why you put up with something that's made you go crazy"for years" and yet never mentioned by anyone else!
He's doing a Direct Export, not going through AME. That calls up a small dialog showing the progress of the export. Kind of like when you render.
I still don't know how that is done or how one even accesses a "direct export" option/menu.

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

Adobe premiere Pro Cs6 video saccadé

Bonjours à tous ! Débutant en la matière je solicite votre aide pour m'éclairer, donc voila, sur adobe premiere pro Cs6 je voudrais faire un montage a l'aide de videos (format MOV.) prise avec un Canon 650d mais il y a un hic lorsque je transfert mes videos et que je tente de les lire, elles lag, très saccadé que ce sois dans "source" ou dans l'outil qui permet la pré-visualisation ... donc le disque de travail a 85 go, et je voulais aussi savoir quel type de préconfiguration devrais-je choisir sachant que la largeur de la trame = 1920 et la hauteur = 1088, et que la frequence d'images est de 25 trames/s, Merci d'avance pour votre aide

D'accord je vois, et merci de ton aide,
mon processeur : Intel(R) Pentium(R) CPU B950 @ 2.10GHz
Mémoire installé (RAM) 4,00 Go
sous windows 7 et ma carte vidéo est Intel HD Graphics family
j'ai aussi tenté de convertir la video dans un autre format que MOV. car j'ai vu pas mal de problémes similaires avec ce format et en Mpeg sa ne saccade plus mais il y a une grande perte de qualité j'en ai deduis que c'est au niveau des paramètre de sortie de conversio, et le seul réglage qui me pose probleme est le Taux (Kb/s) en allant dans les propriétés des vidéos que je veux convertir il y a des taux variant de 48000 à 49000 je ne sais donc pas vraiment quoi mettre ...

Adobe Premiere Pro CC Timeline automatically zooms in when moving clips around

This is an issue that keeps happening. It has been an ongoing problem with Premiere Pro CC and now 2014.1. It would start after working for a while on a project and become more frequent as the project gets larger. The only way to rectify the problem is restarting the computer. I would be working and I go to drag a clip around on the timeline and the timeline will automatically zoom in and thus place the clip in the wrong location. This happens when I am not holding down any keys. It will continue to zoom in every time I move any clips on the timeline and once it starts it happens on all sequences. While restarting the computer seems to help I have to do that 5 or more times in a day which can be very frustrating. It doesn't seem to be related to any OS, computer, hard drive/storage. Deleting preview files, flushing PRAM, trashing preferences doesn't help either. I usually work with Quicktime files AppleProRes Codec or H.264. Any help or insight into this issue would be greatly appreciated.
Here is a video that demonstrates the bug:
Premiere Pro Version: Every version from 7.0.0 to 8.1
OS Version: Every version of Mavricks and Yosemite including version 10.10.1
The footage I most use is H.264 and ProRes 422
The problem occurs randomly throughout the day, nothing seems to trigger it. When it starts the only way to make it stop is to restart the computer
Other software running at this particular time is” Mail, Evernote, Safari, OmniFocus, On The Job, Text Expander, Messages, Preview
No third-party effects or codecs installed.
Hardware:
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon 5
32 GB 1866 MHz DDR3
AMD FirePro D700 6144 MB.
No third-party I/O hardware.
Mercury Playback Engine is turned ON

Hi Patrick,
Sorry, I've never seen that. What happens if you do not run any other software launched as you work? If you have time, please file a bug report: http://adobe.ly/ReportBug
Thanks,
Kevin

Premiere Pro CC Bug Fix Update (7.2.2)

Hi,
Today a bug fix update was released for Premeire Pro CC. Check out this link for full details: http://blogs.adobe.com/premierepro/2014/04/premiere-pro-cc-7-2-2.html?scid=social21455164
Thanks,
Kevin

Hi Richard,
rnaphoto wrote:
Hi Kevin-
I see on another thread that lots of folks are having this issue. Since a Plural Eyes workflow if very common, I would expect that your testers would check that out pretty thouroughly.
We have beta testers and QE engineering constantly testing out common workflows, including with third party applications like PluralEyes.
Regarding this issue: we tried to test those problems with PluralEyes in house after we heard about them, but have not been able to reproduce the problem. That's why we're collecting media and project files from users.
rnaphoto wrote:
In the meantime, is there any way that folks can go back to 7.2.1? I think it would be good if Adobe would give us the option to go back when things go wrong.
Sure, I wrote a blog post about that: http://blogs.adobe.com/kevinmonahan/2014/01/29/revert-to-a-previous-version-of-premiere-pr o-cc-or-any-creative-cloud-application/
Hope that helps you.
rnaphoto wrote:
One really gets tired of dealing with these issues since they seem to be happening much more now that the CC allows fairly constant updates. Although constant updates may seem like a good idea to some, for many of us it seems like a lot of risk for not much gain since we are usually under the gun to get stuff done...
Sorry you feel that way, and not sure what other problems you were having, but most folks are enjoying the updates and not experiencing issues like that. FWIW, you never have to update if you don't want to.
rnaphoto wrote:
But I can't emphasize enough that part of the updating MUST include extensive testing using common workflows. I could have told you you had a problem within 15 minutes of installing this update...
I'm sorry, Richard. Unfortunately, it's not that easy. We could not even reproduce the issue in-house. So, there must be something different with your system, media, workflow, that we have not found yet. We are investigating the issue thoroughly, and hope to have a fix as soon as we can.
Thanks for understanding,
Kevin

[Premiere Pro CS6] Bug, vidéo coupée en deux

Bonjour, j'ai un problème très embêtant sur première pro : mes vidéos importées (chutier, moniteur source) et celles dans la table de montage sont coupées en deux ! Je ne sais pas du tout à quoi cela est dû, d'autant plus que j'ai commencé mon projet sans aucun souci.
J'ai fait une capture d'écran : http://img819.imageshack.us/img819/269/zuil.png
Le plus bizarre, c'est que les vidéos ne sont pas toutes touchées (le bug s'arrête à la vidéo "SDV_936"). Je viens de remarquer que les vidéos de format mp4 ne sont pas atteintes mais les vidéos wmv oui. Comme vous pouvez le constater, cela est très ennuyant. Et cela me serait long de tout reconvertir en mp4. Le son en revanche marche nickel.
Quelqu'un sait comment réparer ce problème ? Merci d'avance.
Références :
Windows 7 64 bits
Adobe Premiere Pro CS6
Formats vidéo utilisés : .wmv (=format présentant le bug) ; .mp4
Note : j'ai effectué un premier rendu de mon projet juste avant le bug après réutilisation du logiciel. J'ai ensuite supprimé les fichiers de rendu et le bug s'est propagé sur ma table de montage.

Je n'ai pas Photoshop.
PP est dans sa version 6.0.0 , je devrais donc installer la maj 6.0.3 alors.
Ma configuration du projet est bonne. Ce qui est bizarre, c'est que ce problème est intervenu seulement il y a quelques jours alors que je procède de la même façon depuis des mois.
D'ici là, je fais la maj et je dis si ça règle les choses.

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

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

Bugs Premiere Pro - A qui le faire remonter ?

Similar Messages

Maybe you are looking for