It would be helpful to know exactly what you don't like about the new workflow so we can improve and move forward.  We will not be going back to the old designs.  One tip I'd like to share is that you are not required to import media when you create a project.  You can just enter a name and location and hit create.  This will create an empty project like before and then you can import in all the ways you are used to (drag from finder, media browser, File>import).  This is exactly the same number of clicks as the old method.       

You can enable this option in the workspace dropdown "show workspace tabs".  This puts the workspaces across the top again.  This provides a way to change workspaces with one click like before.  We are sympathetic to changes in muscle memory, but we won't be going back to the old UI.

Hello everyone,

after looking into both technical viability and current market needs, it’s unfortunately become obvious that we’re not going to be able to act on this request in the near future.

I wanted thank everyone for the considerate and passionate discussion on this thread. This has been a great example of a meaningful conversation over a controversial subject that I don’t take for granted.

Cheers,
Patrick

[my team created Productions]

We understand that things get crowded on a single screen.

The Project panel has special powers, unavailable in the Productions panel. Since those special powers are already available to users, the engineering effort to turn the Productions panel into a superset of the Project panel’s feature set, will be better spent improving Productions workflows.

Potentially helpful: Soon after introducing Productions, we also added to a “Close all other Projects” item to the Project panel context menu.

We know (and love) the Knights, thanks!

For consistency, PPro maintains control of its keyboard shortcuts, letting panels override them only when active; this is unlikely to change.

We have no plans to go back.

Happily, Newtek already provides the ability to stream PPro’s output, via their Transmit plugin.

https://www.newtek.com/software/adobe-creative-cloud/

While capturing from such streams isn’t in our near-term plans, PPro’s APIs make it possible for third parties to write Record plugins to capture streamed output, into media files.

Apple’s guidelines for application behavior require that we request access to all three locations.

We’re glad you’re using Productions!

We understand why that sounds like a good idea; here’s why we don’t do that:

Ingest settings are disabled in the Production Settings dialog because they are designed to apply to a single computer at a time. To use Ingest Settings first close your Production and create a standalone project that is saved outside of the Production folder. Set your desired Ingest Settings and import your media. After all ingest operations have finished, save your project and close it. Open your Production and use the Add Project command to bring the project file into your Production. From there you can use the ingested clips normally.

It’s a lovely idea, but the work necessary to get media onto another platform, process it, and get it back, would obviate any performance “gains” made by enabling rendering on other devices.

We are pursuing other ways to distribute renders…

We’re glad you’ve been using PPro so long!

That behavior was changed because of multiple requests, and is unlikely to change back.

As you rightly describe, if you paused and pressed a camera number, you’d get an edit. If you selected the wrong camera (a frequent occurrence, based on the feedback we received), you’d need to undo the edit.

The “new” (vintage 2013) behavior provides more “audition several cameras” flexibility, before the user intentionally makes the edit.

[I wonder whether creative re-designation of keyboard shortcuts, might not let you put together behavior closer to what you’re looking for…]

PPro’s ExtendScript API operates outside the Undo stack, so it’s very unlikely that we’ll be able to make this improvement, before PPro moves to UXP extensibility (Sometime Soon™).

Good idea, but…

Not every operation can be accelerated by GPUs, and these are (currently) among them. The gains available are more than offset by the costs of moving the necessary data to the GPU, for processing.

While infinite videos may indeed be in our future, for now PPro timelines are limited to 24hrs.

The best way for Adobe to understand and eliminate crashes is to get a crash report, containing all available information.

Your work has already been interrupted, by the crash. I don’t see how we’re breeching any trust, as we respect your choice of whether or not to send us that information; you’re also provided the option of not being asked again, to avoid further interruptions.

While we understand the desire, and plan to provide this functionality once PPro moves to UXP-based extensibility, It’s unlikely that this feature will make it into ExtendScript extensibility.