AE CC 2017 - BIG Bug interpreting the FPS of the sequence of images

[albgel]

Hi everybody,
There's a big bug in the timeline that need to be solved really urgently: it doesn't remember the correct fps interpretation for a sequence of images.

Just to explain step by step
- create a timeline at 25 fps

- import a sequence of images (like a timelapse)

- by default, it assumes 30 fps for the sequence

- change the interpretation to 25 fps: the timeline refreshes immediately

- SAVE THE PROJECT and you'll immediately see that the timeline refreshes the footage interpretation to 30 fps. Also in the project panel, selecting the sequence, you'll see 30 fps instead of 25

- (you can also select "remember interpretation" option, under Interpret Footage Menu, but nothing change.)

- The bug doesn't annoy the footages (at least.. until now!!!!!)

Hope to be solved really quickly.

[Dave_LaRonde]

nugasm38692845 wrote:

Do you know any work around besides marking work area ?

There is no other way besides marking the work area.  That's why there's a work area in the first place.

[nugasm38692845]

Sorry if I didn't like your answer.

But it's definitely not smart enough to work with setting up your workarea every time you want to ram preview when you could use "play from current time" option and it used to work great in all the versions i have used all the way through 3.1 till cc 2015.

We all know how much we hit "0" and how often and how quick .. that's not possible to set workarea every little time we ram preview.

This needs to be fixed please .........

[Dave_LaRonde]

How tough and time-consuming is it to move the timeline cursor, hit the b key, move the cursor again, hit the n key and then hit the 0 key?  Do you want to do this telepathically or something?

Jeez, get a grip.

[nugasm38692845]

It's very difficult

It's about the workflow and I'm used to this from years now. I'm sure there are thousands of ppl who are used to work like i do.

May be it'll be easy later when my subconscious mind start to hit "b" automatically before i hit "0" .

But for now it's lot of pain.

[nugasm38692845]

Ok let's talk more about this. actually it's annoying if i forget to set workarea. because you are doing lots of ram preview and it's quite ppssible to forget someitme.

What cc 2017 does is it starts to cache from your current time and when it reaches end, it starts to cache again from begining, then we will run out of memory because it can't cache all the frame if i have long compositions. so it has become very important to remember to set work area and if you forget you are doomed. which is not in the case of earlier versions.

again I have been experiencing some ram preivew issues, like after i cached ram preview, sometimes, it recache again. i have no idea why .

[Roei Tzoref]

I want to start ram preview from current time till end and it should repeat from current time till end.

But in this new 2017 version, ram preview starts from current time but when it repeats it starts from all the way from frame 0.

nothing has been change in that regard in CC2017. make sure you preview panel settings look like this for Numpad 0 and you will get the expected (and much needed) behavior of previewing from current time

[nugasm38692845]

Thanks again Roei for trying to help but it's not working in my computer, Are you sure it's working in your computer ? may be it's some sort of deleting preference folders ?

[Roei Tzoref]

I am sure. Current time is my preferd way to work and if it would'nt work, I'd be very upset. check and see and report back.

[nugasm38692845]

Nope, mine is not working. it starts from current time but loops from workarea. are u sure you dont' loop from workarea but from current time to the end ?

[Roei Tzoref]

Nope, mine is not working. it starts from current time but loops from workarea. are u sure you dont' loop from workarea but from current time to the end ?

by end you mean end of workarea?

try this:

[nugasm38692845]

I'll get back to this issue later. sorry busy now. But i will have comparision video of cc2014 and cc2017 .

[nugasm38692845]

ok short reply

suppose i have 500 frames.

- i want to ram preview 450 till 500

- but i don't want to setup the workarea. so the workarea is from 0 to 500f

- i move the timline indicator to 450 and i do Pad0 for ram preivew

- ram preview starts to cache from 450 and when it finishes 500, why does it go to 0 and continue to cache ?

- In cc2014 , ram preview starts to cache from 450 till 500f and starts playing immediately. why not in cc2017 ?

[Roei Tzoref]

I now see what you mean. yes it behaves differently. no way around it. it doesn't bother me much because my work area is always shorter than my timeline duration. this way when I see it finished caching what I need, I just hit 0 again an preview from current time and don't let it finish the duration to start over. like this:

if it does start over by accident, I just purge the cache and start again. if you thing this behavior should be like CC2014, then ask for it here: Feature Request/Bug Report Form

[Tim Kurkoski]

You can emulate the old behavior by setting the Range option to Play Around Current Time, setting the Preroll value to 0, and the Postroll value to some large value (such as 10 seconds) that is long enough to cover the typical time between the CTI and the end of your comp or work area. Remember that the Range and other options in the Preview panel are customizable per-shortcut, so you could set, for example, Numpad-0 to one behavior, and Shift+Numpad-0 to another.

As to the reason behind the change, we debated this quite a bit. The reason why After Effects CC 2014 and earlier would loop only from the start of the cached frames is because it is unknown whether or not there would be enough memory available to cache the entire work area. If there isn't, it could create a gap in the cached range. The solution in those older versions was simply to avoid that happening, by not looping.

For After Effects CC 2015 and later, we considered this problem and possible solutions. Part of the equation was the addition of new options to allow you to customize all of the behaviors for each preview shortcut, including where playback started from. (In CC 2014 and earlier, you could only customize whether to start playback from the current time for Numpad-0 or Shift+Numbpad-0.) How and when to loop playback was a part of the discussions. We decided that the possibility of a gap in the cached range wasn't serious enough that we should prevent preview from looping to the start of the range. If you need to preview only a certain range, that is what the work area is for.

We could, potentially, add another option to loop only to the start of cached frames, if enough users request it. I will mention that this is the first time I have heard of such a request. Please do submit a feature request if this is something you want: adobe.com/go/wish

[nugasm38692845]

Thanks for you kind attention. BTW, I'm sorry. I think I saw the cache being erased because it was continuing to cache from 0 frame. But It didn't. !!

let's say I have 500 frame, I start from 400, it cached 400 to 500 and depending up left memory it cached another 0 to 200. so there is not cache erasing. I think I saw the cache being erased and that's what was bugging me

Because if i forget to set workarea, there was chances of erasing the cached frames.

I think this is very good option. I really do not need that feature now . Sorry again. !!

BTW, it would be really cool to have an option to "fit comp"in preview.  like i have Pad0 for normal ram preview and Num. for fullscreen.

So if I wan to preview in window, I hit Pad0 and Num. in full screen, but most of the time user wants to ram preview full screen with fit view options which is not on everyt ime.

Just an idea..

[Roei Tzoref]

About the last part, I just press shift+/ for zoom to fit to view if I need to. Even while it caches.

[nugasm38692845]

yes that tool is handy now since you can play when playing.

I have ctrl+space for ram preview and shift+space for fit to view as shortcuts my right hand is always on mouse

[R.Silva]

I have exactly the same problem. After Effects 2017 DOES NOT KEEP THE INTERPRETATION of the footage, even within the project open, it does revert to 30fps.

I am using a sequence of images as footage that needs to be interpreted as a 24fps sequence. The image sequence constantly reverts to 30fps and I am unable to render a decent movie.

Adobe needs to FIX THIS IMMEDIATELY!

[micheles71799324]

Incredible.. So we're Beta Tester of an official release????

[R.Silva]

Apparently so.

[R.Silva]

The workaround provided by the user Roei seems to work.

[Rick Gerard]

As I suggested in another thread on the same subject - try changing the default setting in Preferences.

Personally I'm not having any issues and I have run about 30 comps through CC 2017 since it was released that use a mixture of image sequences and footage from a Canon C-300...

The only issue I ran into was a mistake in using Mocha Pro's replace module when I choose the wrong frame rate for the original footage.

[Sevlom777]

I use large amounts of image sequences importing from stopmotion projects.  I need them at 15fps.

My work around for this is I created a preset in the render queue called "DragonFrame" and what I've been doing is (SAVE first), then manually change each seq to 15fps, then (WITHOUT SAVING), Select all the sequences in the bin and hit cnt+M to add them all to the render queue.  AE creates comps for them all, and you'll see the fps in the comps change back to 30, but the comps created stay at 15fps.  Then switch to the preset and render out .mov files.

So far it seems to keep the 15fps and it works fine so far.

[Roei Tzoref]

I use large amounts of image sequences importing from stopmotion projects.  I need them at 15fps.

My work around for this is I created a preset in the render queue called "DragonFrame" and what I've been doing is (SAVE first), then manually change each seq to 15fps, then (WITHOUT SAVING), Select all the sequences in the bin and hit cnt+M to add them all to the render queue.  AE creates comps for them all, and you'll see the fps in the comps change back to 30, but the comps created stay at 15fps.  Then switch to the preset and render out .mov files.

if you are working with 15fps, it seems that changing the default frame rate in the preferences to 15 would be a far easier workaround.

do that and you are done basically.

[Sevlom777]

YES! this problem needs to be fixed ASAP!!  It's killing my workflow in stop-motion which is heavy img sequence using.