News on Premiere Next at Adobe Max

[lasvideo]

Join us today at our #AdobeMAX keynote, live at 9:30 a.m. PT with CEO Shantanu Narayen and SVP @DWadhwani: http://adobe.ly/AdobeNext

[Undot]

... not people "racing to the Forum"

with the only intent of hearing themselves rant.

well, that racing one would be me.

Adobes creative move was indeed the reason for me to stop by and voice my concern. I'd rather have written  an email but it seems that isn't an option. Albeit I did not come here to hear myself rant, but add my voice to the chorus.

If that is of any use I can but hope...

[7marcin]

http://www.toolfarm.com/blog/entry/poll_how_do_you_feel_about_adobe_software_moving_into_the_cloud1

[joe_bloe_premiere]

Thanks for the link, 7marcin.

Current poll stats:

[Evil Edison]

Interesting that they didn't include the option "I'm so freaking angry I'm going to switch to something else altogether!"

[ExactImage]

Yeah.... between the AVCHD bug (now almost a year old) and now this, it seems Adobe had decided they didn't want me as a customer after all.

Still, never mind, they'll get nice and fat off all the people who can't afford to buy the suites but can afford the rental fee each month (for now at least) and all the large organisations that can afford the hardward for Adobe Anywhere, something that sounded great but was too good to be true for the vast majority of us.

Oh well..... it was nice while it lasted, but they'll have to really pull something out of the fire now.

[John T Smith]

>the AVCHD bug (now almost a year old)

Since Adobe says they will still provide bug fixes for CS6, I wonder how long it will for that particular bug to be fixed?

[joe_bloe_premiere]

No telling...   literally.

http://forums.adobe.com/message/5298537#5298537

[Kevin-Monahan]

joe bloe premiere wrote:

No telling...   literally.

http://forums.adobe.com/message/5298537#5298537

Right. That's why it's even more important to let the team know how you feel with a bug report: http://www.adobe.com/go/wish

[joe_bloe_premiere]

Thanks, Kevin.

Is it worth it for a single user to file more than one report?

EDIT:

One hour later, I am going to assume this might be

something that you can not officially confirrm or deny.

So...  I plan to submit daily Feature Requests:

"Fix the spanned AVCHD bug in CS6"

http://www.adobe.com/go/wish

[Kevin-Monahan]

joe bloe premiere wrote:

Thanks, Kevin.

Is it worth it for a single user to file more than one report?

EDIT:

One hour later, I am going to assume this might be

something that you can not officially confirrm or deny.

HI JB,

Right, we have no news regarding that bug fix right now.

joe bloe premiere wrote:

So...  I plan to submit daily Feature Requests:

"Fix the spanned AVCHD bug in CS6"

http://www.adobe.com/go/wish

Please don't do that. Feel free to encourage others to file a bug report, though.

[joe_bloe_premiere]

Got it.

[Kevin-Monahan]

joe bloe premiere wrote:

Got it.

Can say one thing, though, "No news is good news."

I won't give up. I'll keep pushing!

[Kevin-Monahan]

John T Smith wrote:

>the AVCHD bug (now almost a year old)

Since Adobe says they will still provide bug fixes for CS6, I wonder how long it will for that particular bug to be fixed?

The AVCHD spanning bug is an isidious one. I also believe it should be fixed. Therefore, everyone should file a bug report. Do so here: http://www.adobe.com/go/wish

[joe_bloe_premiere]

Interesting that they didn't include the option "I'm so freaking angry I'm going to switch to something else altogether!"

[Evil Edison]

Nice.  I wonder if someone has made an "Angry Hitler" video yet.

[joe_bloe_premiere]

[Kopy-Rite]

Better Still, from Adobe's Facebook page.  I'd post here, but wonder if I'd be banned for some terms of service violation!  🙂

https://www.facebook.com/photo.php?fbid=10201247168206191&set=o.305115773870&type=1&theater

https://www.facebook.com/photo.php?fbid=10201247168206191&set=o.305115773870&type=1

[lasvideo]

KR, I love it.  Do it, do it do it.

[Guest]

Guess what... try opening a project from CC into CS6 or CS5?  Not backward compatible.  Of course your old projects will open in newer versions.  That's not what I was talking about.  The problem with CC is eventually when you're sick of paying for it you can't edit your CC projects on old versions.  Guess what?  You're stuck!

From this thread in AE Forum:

Todd-Kopriva wrote:

Our intent is to have a Save As CS6 feature in each of the next several versions.

[ExactImage]

The road to hell is paved with good intentions     I hope they find a way to make that work.

[tclark513]

Fuzzy Barsik wrote:

Guess what... try opening a project from CC into CS6 or CS5?  Not backward compatible.  Of course your old projects will open in newer versions.  That's not what I was talking about.  The problem with CC is eventually when you're sick of paying for it you can't edit your CC projects on old versions.  Guess what?  You're stuck!

From this thread in AE Forum:

Todd-Kopriva wrote:

Our intent is to have a Save As CS6 feature in each of the next several versions.

No offence but having AE (only one video App BTW) "save as" to CS6 isn't really going to solve anything.  He said only a few new versions "MIGHT" have that feature included.  Eventually you will be stuck with projects that won't open on older versions not to mention all the other video Apps.  I'm not going to trust a company (Adobe) on someone mentioning that something "MIGHT" be implemented after what they announced yesterday!

[Guest]

No offence but having AE (only one video App BTW) "save as" to CS6 isn't really going to solve anything. He said only a few new versions "MIGHT" have that feature included. Eventually you will be stuck with projects that won't open on older versions not to mention all the other video Apps. I'm not going to trust a company (Adobe) on someone mentioning that something "MIGHT" be implemented after what they announced yesterday!

Being honest, XML structure of a PrPro project file makes it easier to revert it to an older version. The trick of replacing the Version="XX" expression in the fourth line with appropriate number has been working for a long time.

That's not to say Adobe mustn't provide official backward compatibility right on the decision to abandon releasing boxed versions. That's to say, 'It's at least something'. And you can test whether the mentioned by Todd feature of a backward compatibility really exists and works and whether the known tricks also work prior to moving your real life projects into a new release...

[Evil Edison]

tclark513 wrote:

Media Composer is 999.00 for a new license and 299-399 for upgrades.  Not as bad as I thought and you get to "keep" your software.  Something to think about.

I can't speak for Media Composer as I haven't used it extensively (although I'm sure it's a perfectly credible editing system).  However, I will say my experience with Avid as a company has been less than stellar.  I've used Avid|DS since it was Softimage|DS (back in 1998).  You probably haven't heard much about it (since Avid doesn't really market it) but everything people are thrilled about in the new version of Smoke pretty much existed in DS back in 2001. That said, Avid bought the product and then let it dwindle away while offering it's long time users lip service about future updates and Avid's undying commitment to its customers.  They still haven't officially EOL'ed it but the last sales person I talked to suggested that was the unofficial position.  So believe the marketing hype if you must but trust me, when it comes to making future business decisions, Avid won't love you any more than Adobe does.

[tclark513]

Seriously, I think you guys are running on paranoia here, 'inventing' reasons to dislike the Cloud which, to my eye at least, have little basis for genuine concern.

Are you serious???  I think you should read back a few pages.  It's very obvious the real legitimate concerns of this move by Adobe!

[Felix Dames]

Jim Simon schrieb:

But what if...an older project of mine relies on one of the removed features

I don't believe that's ever actually happened.  New versions might add features that old versions can't deal with, but not the other way around.

It happens all the time! "Vector Paint" was removed from After Effects CS5 because of the switch to 64bit, Reactor Dynamic Simulation Engine was removed from Autodesk 3ds Max because of licens fees just to mention some here. It's common practice if software moves on to better or newer technology thinks get phased out.