When I switch computers and 'log out, and sign off of computer X' so I can use CC on computer B..., A: We should only have to do that once, and not each time I open another CC app, i.e. render with M.E..
and B:... when I do sign in (again), it shouldn't force me to save AE changes and quit the app. just so I can relaunch it. I haven't noticed this with PS and AI, but happens every day with DVA apps: AE, M.E. and I think premier. Even signing in and logging out from the CC control panel app, before I start any apps, doesn't fix it. Logged in 5 times this morning.

Layers provide a very inflexible two-dimensional editing paradigm and isn't very conducive to sharing data within a project. Instead of simply allowing node-based editing, Adobe appear to invite their own hacks such as Smart Objects for Photoshop, for example, but these still feel clunky to work with and still don't offer the flexibility that nodes do.

What is needed is an alternative view that is node-based an allows data to flow any way a user wants and without data duplication. This should be optional workflow within all Adobe tools, but at least in Photoshop, After Effects, Premiere Pro, and even audition.

If done right, the layer-based approach would simply be a view on top of the node-based network with added visual clues to highlight interconnectivity where layers are unable to display the data flow. For example, a layer that may be inherited from another part of the tree could be colour-coded or, better still, have an icon to highlight this relationship. The icon could the be used to toggle views and/or jump to the related output that influences or generates the layer. In Photoshop, for example, it may be that the alpha channel for the current layer is sourced from another layer that is in a group below the current layer. An icon could then indicate that such a link exist. Clicking the icon then jumps to that layer to allow it to be manipulated. The source layer icon could then display a drop-down of all the related destination allowing the user to pick one and jump to it. Either way, flattening a node-based tree to a layer-based on is possible. It just takes some thought. Users just need the option to have node-based editing if their workflow demands it. In fact, I can see no professional who would not welcome such a powerful workflow and paradigm to be part of their toolchain.

A lot of us just stick to basic dissolves, but if you watch any show on TLC, you'll notice lots of custom video transitions. Lens flares, complex animations, and more. You could argue that these transitions are tacky and garrish, but sometimes, if used correctly, can really add to a production.

The current way to do transitions like these is to send the head and tail of each video clip to After Effects and do the transition there. The only problem is that this isn't flexible, and if you want to roll the edit or trim some frames, you have to go over the whole process again. If the transition is just an overlay with blending modes, then you're using up an entire layer for video transitions, which seems unnecessary.

Imagine creating a custom transition template within After Effects that you could apply to video in Premiere Pro the same way you'd apply a video transition.

You could create (or download creations) of transitions that use motion blur, flares, blending modes, and more, and skip having to jump into After Effects every time you want to apply the transition.

It may be too ambitious of a feature to request, but that's what votes are for. Also, transitions and it's respective interface in Premiere Pro is showing it's age. So maybe it's not so far-fetched.

After Effects has great options for realizing a non destructive workflow, but when you have many layers, it is difficult for you to maintain a certain order. The new master properties are great for resolving that and for having a even more non destructive workflow.

On the other hand master properties should improve a lot if they want to be as useful as node based workflow.

ADOBE, you could use both layer based and node based workflows. Cinema 4D has this kind of combination. I think the best workflow is use the bests of both two worlds....

Or maybe not, ADOBE, maybe you are developing a new and revolutionary workflow by yourself...;)

Having worked with Nuke, I have often thought that it would be great if one could incorporate and automate Photoshop in Nuke projects as an OFX plugin. While in Nuke, I often think that, would it not be great, if I could simply drop a Photoshop node into my Nuke script to then chose one of its many powerful tools which I know could get the job done quicker and more elegantly. For example, imagine dropping a Photoshop node into a Nuke script and choosing the quick select tool, and then animate not only the location of the selection across time but also within a frame. Now that's powerful. It would also mean that Photoshop as a tool could become a standard tool in the VFX workflow, not only for textures and stills, but for video as well.