There is a big difference in editing multi-camera sequences in the newest version of Premiere. I edit a 2 camera podcast and have always edited it using premiere using proxies and even with proxy editing I am noticing a delay the amount of time to even get play back to initiate and then often times the audio is delayed which makes cutting between cameras in accurate. I always have to go back and readjust the clips because the cut was never where the actual audio was playing faster than the video. I've tried adjusting settings, downgrading playback resolution, etc to fix this and its still an issue only in the newest version.

I do not have this issue whenever it's not a multi-camera sequence.

I find using period/full stop for seconds very useful.

It is only partially supported in Premiere. If . meant 00 always it would save a lot of time.

I find it can work for any number of seconds
"10." jumps to 10s

or minutes,

"2.." jumps to 2mins

but not at all for minutes and seconds
"105." jumps to 1m45
"320." jumps to 5m20

I find this to be the case for either moving a clip or jumping to a spot in the timeline. Would be interested to know if others see this or am I missing a setting somewhere.

This is what's written on the help page https://helpx.adobe.com/premiere-pro/using/timecode.html

"Use shorthand substitutes while entering timecode
When entering timecode, you can use shorthand substitutes affixed with period (..).For example, timecode value of 4.. jumps to the position 00:04:00:00. Premiere Pro interprets the numbers you type as hours, minutes, seconds, and frames.

Examples of shorthand substitutes:
1. moves the CTI to position 00:00:01:00
2.. moves the CTI to position 00:01:00:00 (should be 2)
.1 moves the CTI to position 00:00:00:01
.24 moves the CTI to position 00:00:01:00 for a 23.976 fps sequence
.1234 moves the CTI to position 00:00:51:10 for a 23.976 fps sequence"

So it's
.frames
1. is 1:00
2.. is 2:00:00

But I guess 2..15 to get to 2:00:00:15 is not supported
Nor is 215. to get to 00:02:15:00

Thanks for the new speech-to-text feature! I'd also really love to see the option for synching the already existing transcript (from the .txt file, for example) with the video.

Most of the time, I already have the text of what is said in the video, so using speech-to-text and correct it where needed is kind of not the most rational way of doing things. If you introduce this function, that'd be a life-changer for me, so much time would be saved.

When I tried to use "Import transcript" feature, it only allows .prtranscript files, but I have plain text.

Thank you! Looking forward to your response and hopefully that feature too. I actually bought Premiere Pro with the primary goal to make captions for my videos

HELP! Multicam - freezes - for 8-30 seconds after any edit in timeline

Professional video editor - missing deadlines - please help

This is happening now to multiple projects - this did not happen in the past. if I 'touch' timeline a freeze of the premiere app occurs for 8-30 secoids

windows,32gigs ram (24 allocated) no other software running - NVME for os and app, seperate NVME for cache, external SSD for project file and media together (tride using 2 different ssd to ensure the ssd was not the problem) using low res default proxies and 1/4 res & lumetri panel closed, fx button turned toggled to off - multicam window closed to just make timeline edits

I have:

-uninstlled reinstalled 3 different versions of 15.0 - none work

-reset preferences - used adobe cleaner tool

-reinstalled and reset preferences and cache

-at the dirrection of adobe support - moved cache files from my cahce only NVME to default system folder (that obviously didn't help)

-turned audio hardware to (no imput)

-reset editing workspaces to default not custom and reset to saved layout

additonal specs - updated driver for rtx2070 super, i7 1075h processor, monitoring system tempatures controlled by msi fans

update: (this did not work)

wiped computer - clean instal of windows 10

tried using v14.9 tried using 15.4.1

update: (this did work)

made zero 'rough cut' edits in the source sequence of the multicam

made zero edits that effected the time of multicam

added zero clips to the multicam that were not synced to the main audio reffernce clip

Did Not - switch audio units to millisecond in order to correct for lav to hardline latency syncing and then revert back to frame units

The multi cam now works perfectly - My assesment is that at least on windows - the sofware appears to be fragile when it comes to working with multicam edits at the source level - (when you open source in timeline and make initial edits.)

Not touching any of that - and its butter - but this is not great when your whole interview or project doesn't sync as one multicam - I'd suggest engineers look into multicam source for windows

Update: after a few hours of edits - the multicam is lagging again.

no additional edits were made inside the source timeline.

shortly afyer i did an eddit using the N hotkey to slide the edit point insted of Q and W edits to ripple tail and head it started to lag by about 1 second - now its up to 4 seconds after any edit - all I have done to the multicam besides simple Q W edits is add markers with notes on sequence, and markers w/o notes on the clip/multi-cam sequence.

Clean install of OS, system exceeds required specs, updated drivers, fast ssd's, brand new project started from scratch - What the heck is going on with lagging Multi cams - it's untenable! - Advice? suggestions - anyone?

the only edits in the source are lumetri adjustment and scale, position and rotation adjustments - 2 4k cams and 1 1080p cam - in 1080p multicam sequence