"Set default timecode for future sequences" checkbox is gone?

I just upgraded to the latest version of 2017 and now am hoping to get back to 2017.0.2 just so I can have this feature back. I work with hundreds of multicam sequences and need to be able to set by first clip. Was this feature removed? And if so will it be reinstated?

That's fantastic news Steve, I appreciate your interest in this issue we're having. I'll await further news before rolling back to 2015.5.

I was hoping that the answer would be that this option was renamed or relocated somewhere else in the preferences. Unfortunately making a template sequence and duplicating is not a viable option. Here's why:

I work at a post production facility that specializes in 'versioning' retail commercials. We are provided commercial elements and graphics and create multiple versions for different markets, using different prices, product shots, VO, etc. We have a team of 4 editors to produce on average over 75 unique retail commercials per week for several different clients. We produce commercials for Canada, the US and Latin American markets in frame rates of 23.976, 25 and 29.97 fps; and frame sizes of 720, 1080 and even some SD-only markets. (From this information you can understand that making one template to duplicate does not work in this environment.) However, the one common specification of every single commercial we produce is that each master and submaster file we export for delivery needs a start time of 59:53:00. Clicking the 'set as default for future sequences' checkbox was a one-time, one-step process that ensured that no matter what workstation, editor, frame size or frame rate of the elements provided, the default timecode for every new sequence matched our delivery standard every time. It is then up to the editor to ensure that the slate, two beep, audio, and picture all align with the timecode of the sequence from the very beginning. It also ensures that NESTING a sequence, no matter the source timecode, forces the nested sequence to also have a start time of 59:53:00.

I hope this sheds some light on the situation. It's been very frustrating this past month, enough so that we will likely roll back Premiere Pro on all our workstations to 2015.5 by the end of the month if another solution isn't found. Thanks for any other ideas you may have.

Me too.