Text searches persist across sequences and clips, causing unexpected jumps around timeline

I'm still getting this issue of a sometimes jumping CLI in 24.6.1 

Thx for the thorough testing, @Stan Jones.  I'm glad to see this issue is getting some attention.

I stayed confused over this "bug vs expected behavior" and the relevance of the "Follow active monitor setting." I tested again in Beta 24.6.0.37 and Release 24.5.0; Win10. Auto-scrolling is enabled. "Follow active" is on.

I now understand that turning "Follow active" off avoids switching transcript views, so the search does not have the same effect on the playhead. I tested with "Follow active" on because that is a better test for whether the bug has been fixed.

I believe this has been improved and appears the same in the Release and Beta versions. I created source media transcriptions of Clip 1 and Clip 2 and created sequences from each. I entered "the" as the search term. If I switch from Source monitor view to sequence view and from one sequence to another, the playhead does not jump. I do get odd behaviors - for example, when switching views the search may advance even if the playhead does not move. (If Sequence 1 is on search results 4/nn and playhead position 20:00 when I switch to Sequence 2, it has jumped two search steps and is on search results 6/nn and playhead 20:00 when I return.)

Unrelated: Is there a way to go to result x/nn directly? I don't see it. I can navigate through the transcript, switch to the Source Monitor and jump ahead, but as soon as I click next, it advances only one search result.

Stan

I'm glad this is recognized as a bug. Losing my cursor position on the timeline beacuse the search box is jumping to text in the search box is a very frustrating way to work. If you disable auto scrolling in the text window, then it is hard to find and follow the text.

This bug report shows no staff attention. If this is the expected behavior/by design, what is the proper workflow to avoid the problems? The only thing I see is deleting the search word.

For me a key question was @kit.kohler's here:

https://community.adobe.com/t5/premiere-pro-bugs/text-searches-persist-across-sequences-and-clips-causing-unexpected-jumps-around-timeline/idc-p/14191037#M16748

What is the "use case in which someone would want to be searching for the same word or phrase in both a source and the sequence in quick succession. It seems like a pretty extreme edge case. " In any event, he describes his workflow that makes the current behavior problematic.

If this behavior remains, one option would be a preference/Text-panel-search option to not automatically go to the next found item? I first think in terms of limiting the scope of the search to the transcript panel, but I think that is really about the syncing of location in panel and timeline?

@Kevin-Monahan @Kerstin Ebert @Alexander_DVA 

Stan

Don't worry about seeing things differently. I never expect anyone to work or view an app like I do. I sincerely enjoy discussing the differences as I do routinely learn from them.

And thanks, of course. I love to help almost as much as to learn.

Neil I have to continue to respectfully disagree - I am not complaining about any feature that someone else might want to use - eg being able to search a word and see it multiple times as you hit the down arrow (I myself use that feature). I am talking about a bug, where the search is happening when the user didn't initiate it. eg You have searched a word, maybe found it in a few places, then moved on. Then a while later the CTI can just jump to that word when you weren't expecting it.

It seems this doesn't happen to you which is great. You do amazing work here on the forum and have often helped me over the years, so I don't really appreciate how this is going, but I do understand that forums can be places where people act like how you think I am acting, but I can assure you I am not.

Good comments.

I was at a SMPTE class a year ago, and was with some people in major companies in an array of workflows. I think all in general vastly faster editors than me.

Yet they were so "siloed" in their practices that I actually knew a lot of production things they didn't. That was an eye opener for me, even after years of NAB shows.

Everyone's mileage always varies.