Participant

Answered

New Speedgrade CC 2015 reverts all layers back to default when opened again.

Forum|Forum|10 years ago
June 17, 2015
36 replies
20010 views

Hi Guys I have just downloaded the new versions for work and already cant seem to get past the bugs.

I've had several Prem Jobs passed down the pipeline for colour grading and speedgrade has been fine for the initial grading looks. However If i open the same project a second time to make changes to my grades they are removed and reset to default again undoing all the grading I have spent time on and returning the look to un edited scopes etc.

I notice that when I open it a second time there is a lumetri layer that I can not delete and any attempt to adjust any settings forces a revert.

Am I missing some new process or setting in CC2015?

cc2015

This topic has been closed for replies.

Correct answer Animotion.nl

Guys. This a know issue :-(, this bug slipped in at the eleventh hour and is MAC CC2015 ONLY. Windows CC2015 version is fine.

Dennis Weinmann assured me his team is working on a fix. Until then, I'm sorry to say that my advise as an Adobe Certified Trainer is: DON'T use DIRECT LINK on MAC with CC2015 until this it fixed.

I'm sure they will come with a fix really soon, and then we can all forget about it. :-).

C

Canikickit917

Participant

It looks like they fixed this issue in the latest version of SpeedGrade CC (2015.1). I completed stopped using Sg due to this issue and I've just been using the Lumetri color effects in premiere, however with this bug worked out, I think I will give SpeedGrade another chance. Here is the version that I'm currently running on Yosemite.

R Neil Haugen

Legend

Sg 2015.1 fixed a bunch of problems ... I wasn't using if for much Direct Link work as well, it didn't Di-L nearly as well as say 2014.2. So I was still doing some new projects in that. It seems to be working fine in most respects now.

Neil

Everyone's mileage always varies ...

K

kbjohnson1

Inspiring

Thanks J_Harwood for your report!

I also find that my SG work done via DirectLink in CC 2014 is now visible in CC 2015 July update. Thank goodness.

To Blabberlicious -- Unfortunately, I still find that masks applied to scaled/translated clips (4k OR HD) in SG are in the wrong place.

So I still have to use the workaround of doing the scaling on one sequence, then nesting that in another at filnal delievery dimension to which masking grades can be applied.

In my case, the original scaled clips are in a Multicam sequence that gets nested in the final sequence anyway. So its not so inconvenient.

Any masking gets applied there, and there does not seem to be any truncation problems.. I can pull back detail in a masked area from skies that were blown out after the initial overall grade on the master clips.

Maybe off topic in this thread, but since you brought it up...

Late 2013 MacPro, D700's, Os X 10.10.3

Widget is not in the same place as the masked area.

B

Blabberlicious

Known Participant

Scaled masks are as you describe. It seem to be beyond them to fix. Funnily enough, I was using 4k in nested Multicam clips too. My problem with that is that you can't apply a grade to a Master Clip, as it gets applied to the whole Multicam sequence. To do that, you need to flatten the multicam tracks, and then SG be applied correctly to master clips. Swings and roundabouts.

I have a feeling I'll be using PP to to technicals on scaled 4K footage, using internal Lumteri. Given the new controls, I think 90% of what I do can happen without the pain of going to SG. It's realtime and decent scopes make a big difference.

To match shot to shot, I'm just loading my current Sequence into the Source Monitor then grading in the Program Window. Quite efficient.

R Neil Haugen

Legend

Glad that's working for you. Masking has been at times a frustrating part of Sg ... and I had the hopes when the Color workspace was announced that we could use the much more relable masking in PrPro ... though I still wish Sg's masking could become totally accurate always.

Neil

Everyone's mileage always varies ...

J

J_Harwood

Participant

Everybody seeing this fixed in the latest update?

Just tried going back and forth, initially just ungraded in premiere to graded in speedgrade, then went back and forth to premiere to see if the changes remained and didn't reset.

Then started mixing and matching the lumetri controls (only allowed in premiere) and speedgrade layers over the top.

All seems to work for me.

MacPro(2013) w/ D700s, working from a NAS, Yosemite, CC version updates 27/07/2015

B

Blabberlicious

Known Participant

Good to hear. I have a ten foot pole and have begun prodding

B

Blabberlicious

Known Participant

Adobe. You have got to be Kidding me. After 10 minutes testing.... Showstopper. (at least for me)

Speedgrade 2015 Direct Link
GPU acceleration DOES NOT WORK - MAKING IT (STILL) USELESS
2015, iMac

GTX 780M

10.10.4

32gb RAM

Mercury Playback Engine Claims to be on - and functions fine in native mode.

But in Direct Link Mode - it is obvious that is it not functioning. GUI takes minutes to update. Unusable.

If I open same Media (5D3 footage) in 2014 via direct link. It works.

Speechless.

No one uses iMacs to edit footage, do they? So I guess it missed your rigorous testing procedures.

K

kbjohnson1

Inspiring

Just found this post after discovering that none of my Speedgrade DirectctLink work done in 2014 is accessible in 2015.

Have to revert to 2014.

The Creative Cloud program's "Previous Versions" section doesn't include Premiere or Speedgrade.

Turns out, its in the bottom section labelled "Find Additional Apps". To the right is a blue text that said "Flters and Versions".

Clicking that and selecting "Previous Versions" from the dropdown allowed me to see Premiere and SpeedGrade.

Selecting "Install" next to Premiere allowed choosing which version.

Hope this helps someone find it more quickly.

P

phil_woodall

Participant

Just found this thread. Wish I had found it before I started grading a project with 2015. Back to 2014 for me as well.

The fact that this got by Adobe is disturbing.

ohanafilms

Inspiring

Many things about this concern me.

The fact that a "glitch" of this magnitude was allowed out the door. Did Adobe literally never do a round trip between PP and SG before they released this to us, their "beta testers"?

A problem that renders the software 95% useless should not ever make it to the end user, especially a problem like this that is so easy to find and replicate with the most basic testing.

The fact that Adobe took a company-wide vacation after a major release is mind-boggling.

And now we just sit and wait.

R Neil Haugen

Legend

No, there were many round-trips between programs before these programs were released. But realize that the total number of people working on these as members of the design/engineering team is probably fewer than you think ... and though they almost all work both Mac & PC machines regularly, it's still only a (relatively) few machines.

From what I know from chatting with people involved, they do get a lot of issues that come up within the private & internal user-testing program work. And they work at solving those as the come up. It's been fascinating to find how the same software runs totally fine on say the group doing X with it, and then someone else uses the same tools/effects with just a different codec or with a slightly different hardware config ... and everything that seemed totally stable and locked down crashes. Abysmally. And the engineers are sitting there going wth ... I tested with that, what happened? Implementations of various mobo parts drivers ... OS changes & options ... let alone 3rd party things such as AJA or BM cards/devices ... all of these things can work perfectly through a bunch of testing and crap on this other slightly different rig. A bug that lasted through two "generations" that they finally nailed to the wall forever ... resurfaces suddenly. Why? Oh ... maybe it was nVidia releasing a new driver that went around their earlier fix of this effect ... but ... this only affects people on say Mac with these nVidia chipped cards running this precise driver update. Realistically, a very few people. But maybe this completely shuts down professional work for those affected by it.

And along the way, judgements have to be made. There are only X team members, working Y hours/week. These are the list of problems, from some that do a slight bit of "hurt" (very annoying but you can work around it) but for a LOT of people, down to some that affect say less than 3% of the user-base, but HAMMER those folks. Now ... where do you put your time resources? That's a decision that will always be wrong for someone. Going in.

And at some point, Management decrees "We're going LIVE on Tuesday, with whatever you've got."

So ... you end up with making further judgements of the above paragraph, after the fact of Release. It's very public there are some problems ... but how widespread any one problem is will never be openly discussed ... and there's no communication giving a listing of exactly what's been acknowledged & when the fix will be in.

Which is where we are. And why some users have a very big bone to pic with management style & practices. And yet, there are some long-time users here who work many hours a week professionally delivering to major "outlets" all the time ... who've never been shut down by anything. Wish I were one of them, but ... I also listen to them when they suggest possibles for people to troubleshoot their machines over this or that issue. They've had some luck, sure ... but also made some (clearly) wise choices.

So says the guy who's writing on his laptop as his desktop ... a month old machine ... is going through hours of testing of EVERY part/driver on the mobo from CPU cores on down, to figure why this new machine has completely crashed in two different ways in it's short life. When it's run it's been an awesome machine ... but it's been ill more than healthy. My builder is ragging out with stress tests to find out what's the issue.

I hope to be working again by Friday mid-day. Been down since late last Thursday. I've got disagreements with the ways some of the new 'tools' within PrPr/Sg work/interact, but at least, my machine's internal drama can't be blamed on Adobe.

Neil

Everyone's mileage always varies ...

B

Blabberlicious

Known Participant

A very considered post.

I've been producing digital content since 1995, and seen the evolution of Photoshop from v1.

I think the work that's been done on Premiere, in particular, has been nothing short of a miracle. The speed and flexibility that real time editing has given cannot be understated. I am a big advocate for the platform. It was a brave decision to do a tear down when they did, and I applaud them for doing so.

I've spent a working lifetime merrily tripping through the various roadblocks, gotchas, platform/hardware performance disparities that inevitably arise developing so complex a product. That's life, in its infinite complexity. I can deal with that. I've poured many hours of my life into testing and evaluating software, in the hope I can help improve things , rather than just point and shout.

But when something like this happens, Adobe really have to understand that the timely communication of release issues should be bound into the Product, and always be 'F1' away, not buried in threads or web pages with broken URLS.

So rather than going through this again, I hope they set up a framework that gives up a heads up, so that we can roll with the punches - rather than being floored with a sucker punch!

Best

ColinB03

Participant

Does "in place for next update" mean 2015.1? Cause going by last year, that would be about Oct.

S

Seneca_lives

Participant

October is starting to be my concern as well. In addition to my general frustration at how this release of Sg has been handled, comes Adobe's infurating (non-)communication surrounding its many issues:

- The lack of acknowledgement that there are in fact many, many application-breaking issues (on Mac AND Windows), including massive memory leaks, permanent breaking of file references to After Effects dynamic links, layers resetting using DirectLink and a ridiculous amount of instability. Communications to date make it sound like "There's just this one bug which affects some people" (even so, that would be "people using DirectLink on Mac... probably 70-80% of Speedgrade users?).

- I found my own ticket (regarding the AE issue) to have been closed/resolved with no motivation after waiting a week for a response from the support crew. I then re-opened the ticket, but haven't been able to get a meaningful response since. Now, this could mean "We know about the bug and are fixing it as fast as we can", and I hope it does, but, if so, please let us know. (Not blaming the support crew here, I don't expect Adobe would let them formally communicate upcoming releases.)

- The lack of any kind of ETA for the bugfix. I'd understand if the patch were planned for a certain date and the deadline slipped, but the silence fuels the hopefully unreasonable suspicion that Adobe is basically taking July-October to get Speedgrade ready for its June release.

EDIT: I just noticed the Illustrator/InDesign group has been getting 2015.0.1 updates, so let's hope that's what Sg is getting as well...

R Neil Haugen

Legend

Hmmm ... I've seen staff comments acknowledging the Sg scopes memory leak, the Lumetri issues of PrPro/Sg on a couple different issues (including layer resetting) when in Direct Link, Dynamic Link issues betwixt PrPro & AE, problems with certain effects in PrPro, and several instability issues some of which concern particular Mac OS versions. And that there's work going on in all three programs to get a bug release update out as soon as they have the issues fixed.

They don't communicate even potential release dates ... you can complain all you want (I certainly have!) about this, but it isn't changing. Yes, guaranteed, there will be fixes posted long before October. When? No clue.

And the frustrating thing is many people are operating just fine, some folks are operating but with pains, and some are just plain hammered. Sorting out why one system is doing fine but another nearly identical one is hammered can be complex & frustrating. I've been on both sides as have many users. Some releases just flew for me while others were nailed, sometimes I've been one of a few nailed by a glitch that most didn't have.

Neil

Everyone's mileage always varies ...

benfth

Known Participant

Still waiting on this, are we?

What is this monthly subscription for, anyway?

Fix our programs, Adobe.

A

AraTheCoach

Participant

It's amazing to think that so many loyal Adobe users who pay for the products, depend on them and are 1st to install updates have basically been left out to dry. This update has rendered this application unusable and useless, it's been almost 3 weeks since it was highlighted and still no fix or firm notification from Adobe of a possible solution. Kevin-Monahan‌ I appreciate this isn't all on you but this is beyond a joke. If Adobe don't care about SpeedGrade‌ then why release an update? We've now been forced to look for alternative grading solutions which means we'll probably have to stop using Premiere too. So distressing.

Joost van der Hoeven

Community Expert

I think we all agree that of this version of SpeedGrade CC 2015.0 should never have been released. I've been informed that the Sg has a fix in the making. Until then, lets try to be constructive, believe it or not, even the Adobe employees are just ordinary people. ;-)

Manniac

Known Participant

I don't understand why people say, this is only a MAC issue? I have Windows 8.1 and suffer from the same problem: looks once created are lost, when I reopen the file in SG (directly or via direct link).

I still don't understand why this happens, but it seems to have to do with the inbuilt-lumetri-effect in premiere, because the problems started after i tweaked those settings in premiere

also i don't understand why there still is not fix! adobe, you leave us with a crippled program here! do something

Kevin-Monahan

Community Manager

Hi Manniac,

I don't understand why people say, this is only a MAC issue? I have Windows 8.1 and suffer from the same problem: looks once created are lost, when I reopen the file in SG (directly or via direct link).

I still don't understand why this happens, but it seems to have to do with the inbuilt-lumetri-effect in premiere, because the problems started after i tweaked those settings in premiere

The bug logged is related to Mac only. Could you file a bug report with details of your experience? It would be great to have some kind of repeatable steps to make sure we can fix the issue.

also i don't understand why there still is not fix! adobe, you leave us with a crippled program here! do something

A patch is planned to fix this issue. I'm sorry for the issue and ask for your patience while we work on a fix.

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Laurent Chesneau

Participating Frequently

Hi Kevin,

Could you also speak to the team about the issue of graduations in Parade window? I can't see it on 2015 version of Sg...

Thanks.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded