This appears to be similar to what brought ME here. I make a multicam source using the auto sync tool (sync on audio tracks), make global edits to the source tracks and select New sequence from clip. Presto change-o, there are NO AUDIO WAVEFORMS SHOWING. A workaround I've used is to export a WAV and attach it at the bottom (if concerned about the slight deterioration innate in that export/import process mute the WAV track and just use it for guidance - it should snap into place with no sync problems). This shouldn't be necessary. Nor should deleting all cache and peak files and asking them all to re-create. ADOBE - FIX THIS! ... View more

UPDATE: My Creative Cloud indicated a new version and I (fingers crossed!) attempted to install. SUCCESS! I now have v15 like everyone else. Not sure what the problem was with Error 160 but I somehow don't think it was on my end or anything I could have cleared (on the other hand, I don't see a spate of others with similar complaint...) go figure.  Anyway, this bug (or whatever it was) seems to have righted itself. ... View more

Since we can't get aid from tech support on a beta version, the last bastion of support is the staff here. Is there some reason no one's come to my assistance on this issue which persists (and on which I posted a later request for assistance)... ... View more

Quick update to above: Currently Creative Cloud says that I'm up to date; however, I'm running 14.9.0 (9[R]), not 14.9.0.9 which is where the error was in the install process. Not sure why the discrepancy. ... View more

First of all...no need for an apology! Second: This morning, Version 14.9 Build 6[R] arrived this morning, and it solved absolutely the "flickering" issue.  The only remaining issues that affect my own work are: that odd character I (and others) have posted about that occurs when I attempt to edit in the captions window; while the issue can be worked around by doing all editing in the program monitor, that character, similar to Unicode character U+2612 (ballot box "X") needs to be banished from the program.  Export of SRT (from File|Export|Captions) with timeline or caption window active, without having to export the entire timeline, and Carry captions into subsequences. I really appreciate the work that's gone into this. It will likely be found to be the #1 way to create and use captions in the industry, far more convenient than so many. If the Transcript section is robust it will cement this and likely make Premiere Pro the go-to captioning program.   ... View more

I guess the promise of 035 "tomorrow" was a bit optimistic (since I'm writing on 12/14 and the "tomorrow" fix to these entry difficulties was indicated on 12/10...) While I have found ways to work around the caption-entry issues in Windows, this version can't come too soon; OTOH delayed is better than release before it's ready... ... View more

I note that when creating a sub-sequence the captions do NOT follow.  This should be an easy fix and should happen! I needed to make a clip demoing the new captions - I had to do it directly from the timeline and thus couldn't engineer in a dissolve in or out...would have to import and re-export the clip, not the best practice. Thanks... ... View more

Very good news; to quote Scarlett O'Hara (GONE WITH THE WIND): "Tomorrow is another day!" ... View more

 Then we could export JUST the captions without having to set up an entire project, and turn off the Captions window to avoid doing a burn-in? Thanks for considering... Didn't mean Captions WINDOW - translate that to Captions TRACK. Turn THAT off to avoid burning in captions after SRT export. Sorry for the confusion... ... View more

I forgot to answer an important question: I'm in Windows 10 Pro, updated to 20H2, the latest. My self-built machine has an i9 processor, 64G RAM. OS and programs are on an M.2 drive. This does appear to be the "tomorrow" build you promised. It is WORSE than the last one (32[R])- at least with it, I could eventually get the box to respond EVENTUALLY. This one AT NO TIME allows entry of text. Some improvement. I'm very disappointed and frustrated. I expected better from your post. ... View more

I just downloaded the latest Beta build which is 34[R]. I am now COMPLETELY unable to enter text into the Captions|Text window. Double-clicking just brings up a flicker and return to the unenterable state. Which begs the question why IS there an unenterable state? Why is that box not simply open to typing or pasting without doing a double-click (better yet...a keyboard shortcut!)  The only workaround available at the moment seems to be copying the last caption on the timeline and pasting, then editing in the Program Monitor. Otherwise, no text is getting added to the project.  While I'm at it...thanks for making SRT export available. How about making it available from the Edit|Export menu so that when the Captions window is active Captions livens up as an export option? Then we could export JUST the captions without having to set up an entire project, and turn off the Captions window to avoid doing a burn-in? Thanks for considering... ... View more

For some reason in the current Beta (14.8.0 Build #32[R]) I'm having difficulty adding captions. I have a play script from which I'm copying, and double-clicking with the prior version opened the box and it was easy to add the new caption. This version it takes numerous times double-clicking to get the gray box to turn black which is the sign it's ready for text to be added.  Additionally, this annoying object (at red arrows): seems to like to interpose when I do any editing whatever to the text I've copied in. The only way to remove it is to get in front of it and press <Backspace>; <delete> doesn't have its usual effect. It only seems to occur when editing in the Text|Captions window, not in the Program Monitor (I note that this wasn't previously possible and apparently now is because I'm doing it...) That one is an annoyance but the lack of ease of getting the Caption box in the Captions window ready to edit is doubly so. Please if anyone knows a way to work around this let me know or PLEASE fix it, this wasn't a problem with the prior beta version.    ... View more

Hi, Stan, and thanks for the candid answer. My ultimate goal is to get a good SRT and be able to upload to YouTube or send the two files for users to apply as they wish (i.e. with VLC or 5KPlayer). I don't use AME for burn-ins, finding Handbrake a better solution for my needs.  Do you not, though, see the suggested shortcut (copy CTI position) as possible, as perhaps a feature request? I can't imagine it's insurmountable although it's clearly not there now (was just checking in case it was my occasional blindness to the obvious that was in the way); if you think it would be impracticable for Adobe to adopt such a shortcut option let me know and I won't bother. I didn't have SubtitleEdit until you mentioned it, but have now downloaded and will try it! I keep seeing that Adobe is improving the Captions tool; I have asked for better documentation and I wonder if the team developing the tools might consider this shortcut key (not asking it be assigned to anything, just that it become available). I've been in the current iteration of the feature request area and note that a member of that team is frequently present and answering questions... ... View more

Hi, Stan...strange times, and I'm just getting back to work on this project. So I have the script (of course not always followed onstage!) and need to efficiently place it in captions and get the start/end timings in the caption tool. Something that I would have figured would be obvious seems to be impossible and requires extra steps that take valuable time: There appears to be no way to quickly copy the position of the CTI in the timeline. I seem to need to highlight the time press Ctrl-C and then go to the caption and paste it in. I could save a bunch of steps and TIME if I could just get this data QUICKLY. It really adds a lot of time to the process. I've searched up and down the available keyboard shortcuts and this one eludes me. Any ideas (or am I missing something obvious?) Thanks... Jay ... View more

YAY!!!! It DOES work! It ignores the original in/out points and replaces them with the ones on the timeline. This was even true when I copied all of Act 2 and the subtitle work I had already done in a SEPARATE caption "clip". Heeding your warning (but would have done this anyway), the two clips, each synced to the act in which they were created, are both on V2 track. I had but to open them in SubRip to see that the timings are correct. This will save me doing a bunch of repeat work I was SERIOUSLY not looking forward to. Thanks so much. NOW how do we get Adobe to document this somewhere? Jay ... View more

Thanks, Stan, that's encouraging.  I still want a detailed description (I'm sure you would have shared if you had it) of what they did. It SOUNDS like they may have made the caption timings responsive to the timeline as it exists, not as it was at the moment the title was created. That would be huge for me.  Obviously, the intention there would be to make it so that every timing didn't have to be re-adjusted when an edit was made on the timeline (i.e. no such changes should be made until the timeline is LOCKED DOWN for other editing but we have these pesky things called clients who sometimes insist on us doing the impossible...) Anyway, you've encouraged me to try dealing with what I have and see what happens. I recognize that there even might be an issue with captions made in an earlier version of PPro not being able to conform to new standards. I'm basically just trying to do as little as possible by trial and error, and as much by going from what I KNOW the program is supposed to do. The project is a retelling of A CHRISTMAS CAROL, with music by Gilbert & Sullivan (and new lyrics by a G&S enthusiast). The author/director suddenly wanted a couple of numbers captioned for better understanding. When he saw the results, he then asked for the ENTIRE video to be captioned (the musical numbers, not the dialogue thank goodness!!!) SO I haven't even dared open the project because I dread having to re-write or re-time the captions I already did. Doing the work song-by-song would not be what's needed; the request is to have the entire video subtitled. As far as output, my best results in the past have been by exporting the .srt and sending as a sidecar file (recommending to users that they open in VLC or 5KPlayer) or posting to YouTube and then adding the .srt there. I would not consider burning in using Media Encoder (have had GREAT results burning in with Handbrake).  Again thanks for answering and for your encouraging words! I do hope someone from Adobe comes in with the actual list of what's new with captions but your obvious experience with this workflow is most helpful. Thanks and stay healthy in this difficult time. Jay ... View more

Jennifer, I had this happen on TWO concerts I recorded in January, and it was a bear to fix.  The feature is GREAT when it works (I never had it fail before and I've probably recorded 100 or more multi-cam theatrical/opera productions, mostly amateur and tiny pro companies here in NYC).  Adobe tech support turned me on to a Red Giant plugin called PluralEyes. You can download an unconditional (I think 14-day) trial and it will dig deeper into your audio clips than Adobe's generally marvelous solution.  If you try this out (and I do recommend it - it costs nothing to try and even USE the result), it will NOT set up the sequence the way you're used to it, but it WILL yield a result you can use to get your multi-camera source synced. I hope this helps. Jay ... View more

When you press "Export frame" you have several choices; which one are you using? I recommend either Tiff or PNG. They shouldn't degrade but BMP and JPG are older and less likely to satisfy. Hope it helps... Jay from the Bronx ... View more

Neil, I've since writing the above recorded the actual concert (on January 26) and another (January 24) in a different venue with similar results. At the suggestion of Adobe Customer Care technicians who are apparently taking this quite seriously, I used as a troubleshooting method downloading Red Giant's PluralEyes software which without any issue or problem synced the files perfectly and quickly. I would be very upset if the result is that I have to pay $300 for software to do what the Adobe suite advertises it does as part of that subscription. The Adobe techs and I are in agreement that the final footage - somewhat unlike the Dress Rehearsal versions - is extremely well-defined and relatively easy to match by eye on the audio tracks (but when I was able to use PluralEyes it showed that I was off by a frame or two).  ... View more

I just had some issues with sync, where some footage wouldn't sync on audio so tried to use in points in created sequences. It seems PPro doesn't like to do that. I made it work in the following way: put CLIP MARKS where I want my in points (select video and add a marker puts it on the clip, not the sequence timeline). Open ORIGINAL FOOTAGE (only opens in source monitor) and add my in points THERE. Do with all clips you want to sync and it should work. For some reason PPro doesn't seem to like the in points we mark in a sequence derived from a clip, wants them on the original clip. Problem: because they're only on the source monitor, if you want to sync on the audio track visually you need to mark rather than add an in point. Hope this helps someone... ... View more

I just had what I initially THOUGHT was the same bug in 2019...and in fact it was a color-mode issue as so many above have mentioned. CLASSIC problem - I opened a document that was made for print (i.e. in CMYK mode) and I need it in a Premiere project. I applied some effects (primarily bevel/emboss and shadow) and the colors did look weird, was going to fix in Premiere...but it wouldn't import into Premiere (generic error!) Tried to save as PNG and no dice, no option. Changed to RGB and problem solved. BOTH problems - the file imported as PSD, would save as PNG...AND the color issue solved itself. Apparently a file in CMYK mode won't save as PNG. No problem, just change to RGB. ... View more

Hi, Jim, and thanks for chiming in so quickly. I've checked the logs for further information. Here's the log for a 10mbps transcode of the file: 03/01/2019 04:39:24 PM : Queue Started - Source File: C:\Users\Jay\AppData\Local\Temp\CONSUL 2.prproj - Output File: O:\SCROOGE 2018 Media\0118 CONSUL COMPLETE.mp4 - Preset Used: Match Source - High bitrate - Video: 3840x2160 (1.0), 29.97 fps, Progressive, Hardware Encoding, 02;11;44;19 - Audio: AAC, 320 kbps, 48 kHz, Stereo - Bitrate: VBR, 1 pass, Target 10.00 Mbps - Encoding Time: 03:14:40 03/01/2019 07:54:04 PM : File Successfully Encoded Here's the same info for the one encoded - same folder, same drive - at 40mbps: 03/02/2019 10:47:09 AM : Queue Started - Source File: C:\Users\Jay\AppData\Local\Temp\CONSUL 2_1.prproj - Output File: O:\SCROOGE 2018 Media\0118819 CONSUL COMPLETE.mp4 - Preset Used: YouTube 2160p 4K Ultra HD - Video: 3840x2160 (1.0), 29.97 fps, Progressive, Hardware Encoding, 02;11;44;19 - Audio: AAC, 320 kbps, 48 kHz, Stereo - Bitrate: VBR, 1 pass, Target 40.00 Mbps - Encoding Time: 05:50:03 03/02/2019 04:05:04 PM : File Successfully Encoded The drive in question is an external 3.1 USB (Gen-1) connected directly to my new Asus Prime Z390-A motherboard (rear connector). The primary system drive is a 500GB Samsung SSD. The original footage comes from my two camcorders, both Sony, one an FDR-AX100 and the other an HXR-NX80, and results from a multi-camera rendering of the opera THE CONSUL by Menotti. The original footage is around 55-58mbps. The quality of the later (and much larger) file is obviously better. Sharper, better color rendition. What doesn't make sense is the muxing process taking so long! In each case, the actual encoding of the video file was within 30 minutes of the actual length of the project (2h11m44s19f). So the 40mbps took 3 1/2 hours longer...and it was all muxing. I'll experiment with different drive usage. I can also write to a RAID connected via eSATA; I can try that with the next performance of the show that I'm editing now. If the log info strikes you as informative, do let me know. Again, thanks for your input which will inform further testing. Jay ... View more

I've added proxy creation (ProRes in current recommended format) to my workflow on ingest and it seems to make all the difference. I recently upgraded my system to i7-8700/32GB DDR4/RTX 2070. This last (an upgrade from GTX 1050Ti) has made a huge difference in my standard workflow which involves multiple streams of h264 4K (Sony XAVC-S). Even with this firepower, it won't scrub well when all cameras are exposed in a multi-camera array. I have that button to use proxies available and I use it when I need it (i.e. to scrub), it takes less than a second to press or use a shortcut to toggle proxies on or off. I can't imagine investing in even more firepower to scrub better when I have the proxy option available. Even if I have to buy more hard drive space, I'm better off than trying to even further enhance my computing environment (or so I think). I'd be happy to hear anyone else's take on this... Taking the devil's advocate position in direct answer to your question: I think the only clear downside to using proxies is the drive space they take up. Of course, they can go as soon as you've finished editing the project. ... View more

Hi, Neil, and thanks for chiming in! I upgraded my CPU to i7-8700 (from i7-4770K). Decided not to pay the extra shekels for the 8700K because as a non-gamer I don't see any reason to push my system by overclocking. 32G DDR4 RAM. ASUS Prime Z390-A M/B. I agree that either would be significant, and beyond Premiere current specs (they don't do anything with the ray-tracing and other aspects that differentiate GTX from RTX - yet) but given the pricing of the GTX 10 series beyond my 2016-vintage 1050 Ti and the RTX 1060 and 1070 series...it makes no sense to me to stay in the 10-series space. The question is whether there's enough significance between the two cards in question to venture up to the higher-priced (and admittedly more powerful) card. Thanks! Jay ... View more