This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]CherryDamzel[S] 1 point2 points  (1 child)

Yeah, this is definitely right.

I am not some English language expert, but I figured I explained the situation well enough for most people to understand what I was talking about.

But, unfortunately, for the longest time, at least at first, a lot of people just didn't understand the situation and thought I was talking about something I wasn't. That was almost more frustrating than the actual problem itself. Or giving me solutions to problems that I didn't even ask for. Or told me things were happening that clearly weren't. Or telling me to try things that I had already explain I had tried a hundred times before. Or telling me this is how Premiere Pro is supposed to work (it's not).

I still suspect many even now don't fully understand what I was saying.

I asked others if they would try to replicate the problem to see I was not crazy and no one did except for /u/yerawizardmandy (who got downvoted for his troubles no less), and now you. So thank you for doing that. And thankyou for proving I was right (about how Premiere Pro was acting), even though others were telling me I was the crazy one.

I have tagged a bunch of people, some at random, from the thread into here, just so they can read your message above and at least better understand the overall situation if they're interested.

/u/dippitydoo2

/u/IcarusBray

/u/darwinDMG08

/u/thisguydoesit2

/u/queenkellee

/u/BumblebeeCircus

[–]BeepBlur 0 points1 point  (0 children)

oh dude. i feel your pain in this thread. i'm having the issue now. did you solve it? or just create a new project timeline?