Fast playback (multicam) won't stop until end of timeline reached

Any ideas from Adobe? Only way I can get multicam to work right is to put all panels on one monitor and then fullscreen the Program monitor with the ~ key. Functional but inconvenient.

Thanks a lot guys. I have a slow machine so it still lags a little, but the interface freezing I had doesn't happen anymore, as long as I don't have an audio file selected while playing. For your info, I'm Running win 7 x64, and intel i3 2100 CPU @ 3.1GHz, 8 GBytes DDR3 Memory, and a NVIDIA GeForce 210 Graphics card with 1024 MBytes of memory. Adobe Premiere Pro CC 2014.1 8.1.0 (81) Build. I have 3 cameras on a multicam sequence that i made by creating a new sequence from a sequence. Two are MTS format with AVCHD Video, 1920 by 1080, 29 fps and 256kbps. One is MOV Format with Quick Time Movie, 1920 by 1080, 59 fps and 17915 kbps. I edit in 1/4 quality due to lagging. I work on two screens by dragging my project monitor onto my second monitor.

Thaks for the help, now I just dont select an audio if i want to play the sequence.

Just find out that when this problem occurs (even on 1 monitor display mode now...), each time I resize a PPro panel (no matter which panel : timeline, project, etc.) the problem dissapear temporaly. Hope this helps Adobe engineers... It's really anoying to work in multicam mode.

Here are my answers to above questions:

1. Does this happen regardless of playback speed or only when the MC sequence is playing at greater than real time (via JKL)

Only JKL

1. Does this occur regardless of the zoom level in the Timeline and the Program Monitor? If it happens only when you’re zoomed way in—or at least it seems more likely to happen in that case—please report how exactly you adjust the zoom level [in case you’re not aware, there are at least four ways to do this…]

Cannot reproduce issue zoomed all the way out on timeline. Issue occurs on all other zoom levels (changed with +/- key or Alt + scroll wheel)

1. What is your exact workflow for starting and stopping playback? Do you do this entirely by keyboard, entirely by clicking buttons, or a combination?

Only keyboard

1. In the Program Monitor, is the Show Multi-Camera Preview Monitor option enabled?

Issue happens regardless

1. When the app is in the state where playback will not stop, does it help to toggle focus to another program and then back to Premiere?

No

1. Is Mercury Transmit enabled? If so, with what hardware? Does the problem persist if you disable Transmit? [Note that with some configurations, Transmit is known to impact performance and responsiveness.]

Issue happens regardless

1. Where is your content stored? Internal hard drive? External drive? SAN? …

Internal Raid 0 (4 HDDs)

1. If you experience both the case where playback cannot be stopped at all and the one where playback continues for several seconds after the Stop command, are there any patterns in the occurrence of these two behaviors?

Issue happens each time I hit J or L more than two times in either direction. Sometimes it stops after many seconds, sometimes it doesn't stop at all. I have not detected a pattern. Info about your multicam sequence(s)

1. How exactly do you create your multicam sequences? By nesting one sequence in another and enabling multicam (old school)? By selecting clips in the Project panel and using the Create Multi-Camera Source Sequence command (the New Coke)? In PluralEyes?

New coke

1. If you use multiple workflows, do you have problems stopping playback regardless of how a given sequence was created?

Only one workflow

1. If you use the Create Multi-Camera Source Sequence workflow, exactly what settings do you select in the dialog by the same name?

All default settings except for "clip marker." One marker in each clip.

1. Is “Multi-Camera Audio Follows Video” enabled? Using audio follow video on "switch cameras" MC clip?

No, it is not enabled, but enabling does not solve issue.

1. Have you used the Edit Cameras feature in the Source or Program Monitor?

No

1. Have you changed the camera for an edited sequence by right-clicking the segment and selecting from the Multi-Camera submenu?

No

1. What effects, if any, are applied to the multicam source sequence? To its constituent clips? In particular, have you toyed with Time Remapping, Speed/Duration, or any other effects that affect playback speed? Have you used Interpret Footage to change the frame rate of any clips in the multicam source sequence?

Rotation, scale, position and Lumetri. Applied to constituent clips. One clip of multicam sequence has had Speed/Duration changed. Audio and video fades applied to multicam.

1. Does it matter how many cameras the multicam sequence contains? That is, can you repro with only two cameras, or does this happen only when you’re working with, say, 8 or more?

Only tried it with 2 cams.

1. Does the duration of the multicam sequence matter? That is, can you repro with sequences that are only couple minutes long, or only with those longer than, say 15 minutes?

Restarted PP and now cannot repro. Can't answer this question but original sequence was 36 mins long when repro was possible.

1. Do you have more than one multicam sequence in the master sequence where you’re editing multicam cuts?

No

1. What format(s) of clips are used?

MXF

Not sure if Adobe is still hunting after this bug but I have the same issue as the above poster, and the same solution. I can reproduce the results anytime I shuttle (JKL) backward or forward. The only way to stop the playhead is by changing the monitor displays within windows to anything different. Anything that gets the monitors to shut off momentarily stops the playhead.

I am running Premiere Pro 2014.1 (8.1.0). The issue only occurs with a multicam sequence when the program monitor is set to "Multi-Camera" display. I can post more details about my system and project if that would be helpful.

Just to share my own experience on this problem. I've also experienced this non-stop play in multicam mode on PPRO CC 2014 8.1 on Windows 8.1

My project :

8 cams (5 MPEG-2 422 Long Gop in 1080i50

1 ProRes 422

2 H264 DSLR

all these cams in multicam mode on Video 1 track

and 1 ProRes 422HQ 1080i50 in Video 2 track as PGM for reference

Timeline in 1080p25

Machine :

2x Intel Xeon E5 2630 @ 2.3 GHz

64 GB RAM

GeForce GTX 680 4 GB RAM

Windows 8.1 Pro x64

3 displays in 1920x1080@60Hz

1 Blackmagic Mini Monitor as... monitor

Medias of this project are equitally dispatched on 2 sets of HD (Raid 0) @ 280-300 MB/S read.

PPro interface is dispatched on my 3 monitors.

So I seems that my machine has got enough ressources to handle this kind of project.

THE PROBLEM :

When I hit play, then stop, my playhead keeps moving few seconds (between 2 and sometimes more than 10 seconds)

WHAT I DID

Try to disable mercury on the blackmagic

Disable antivirus, and all useless resident softs

Try to reboot

Update the NVidia drivers

Update the Blackmagic drivers

Disable Cuda acceleration

and so many others things...

MY "SOLUTION"

After the reading of this thread, I tried to disable 2 of my 3 graphic card outputs and set PPro interface on 1 monitor only. The playback continues to play after I hit stop but less longer.

Hope this will help some of you guys...

noar

I would like to follow this thread: having same issue.

• Multi-cam sequence
• Sony PMW 200 footage - MXF format
• Dual monitors.
• Nvidia GTX 285 Card

Not sure that this has been mentioned, but the problem on my system seems to occur more specifically when I have the multi-cam clip selected.  Then playback will continue until either several seconds after being stopped or the end of clip.

Looking forward to resolution.  Many thanks to Adobe Team.

Yes, several others have reported this issue in other threads on this forum. I actually hit the problem myself a few times in 7.1, and a fix went into that release. But apparently we did not nail all the cases, and we have not been able to isolate a consistent repro case--which makes it very difficult for a developer to investigate further.

Please start by double-checking that you're on the current version--7.2.2 (Several customer have reported being up-to-date, but upon further review found they were on 7.0...) If you are on 7.2.2 and can reproduce the problem consistently, I'd like to either get a copy of the project or confer with you about troubleshooting it to isolate the key variables.