Camera Jitter, depending on the settings either the player or the environment jitters

Of course it's not there, as I said I've tried putting there with values 101, 401, 600, etc... and it was messing things, so I removed it.
I'll dig into the dependencies... but the script is the one I posted above.

 

Update... @Gregoryl you were right, but I needed a tweak.
Basically putting the ParallaxElement after the CinemaBrain was working, BUT at start of scene all my items weren't placed in their correct position (i.e. they were left as if the Parallax wasn't active, and then started to move later on). That's why I said everything was messy. Because since the Parallax Script was starting after the camera moved to the player, all the objects with Parallax were in the original camera position (the default one, 0,0,0, and not the one of the player at start, which can be in different points of my scene according from where the player is coming from).
I solved creating a new script called InitializeParallax, which call the "ProcessParallax" at Start of each ParallaxElement objectsOfType, so they are placed correctly, and then work smoothly!

 

It has to do with the "target look" at with cinemachine. For timeline, because nothing in this engine is ever easy, you'll just have to aim the camera manually. Has anybody had success with target look at using a prefab's object? I also tried looking at an unparented smooth follow object, and that had jitter issues as well.

 

Just a note for anyone else who didn't have their problem solved by any thread anywhere: If you are using the Input System Package, double check the update mode in the Project Settings > Input System (should be set to Dynamic Update).

This is the solution for you if, like me, you found that the mouse look was jittery, but gamepad was fine.

Solution from https://answers.unity.com/questions/1877166/unity-input-stutter-with-new-input-system-and-3rd.html

 

I fixed the jitter by updating the update method to late update on the cinemachine brain. fixed update caused the jitter for me.

I'll keep it in mind, but yeah, i assumed in a different thread the jitter had to do with looking back and forth at the base animation object position and the new object position from the overridden animator timeline. so setting the target at runtime makes sense, just kinda silly to not respect it at default.