Major bug with search filters AND with Search bins!

[lflegg]

Augh. When even the workaround has a bug, it gets pretty tiring.

Any ideas why Prem is failing to filter results in the bin window correctly,

or why my Search bins aren't populating with relevant files either

would be greatly appreciated, thank you! I'm tearing my hair out over this.

I made a screencast:

Premiere bug with Search bin AND filters.webm - Google Drive

btw, this is after I've just deleted ALL media cache

and imported the project into a new project.

Latest version of Prem.

[edwinl76571172]

Update: Hope I don't jinx it , but I want to cautiously mention that with today's update (13.1.0 build 193), it seems this bug may be squashed. I'm still testing, but so far, in both new and old (converted to 13.1) projects, the bin-search function seems to be working again.

I hope you all have the same experience! Thank you devs. Crossing my fingers.

[Jeff Bugbee]

Very good news, it appears the latest update (13.1.0 build 193) has resolved this issue, and retroactively. I was able to open an old project that exhibited this issue and everything is now searchable and filterable.

As of today, the Fixed Issues page has not been updated with this patch but I'm sure this issue will make an appearance.

Bugs fixed in versions 13.x releases of Premiere Pro

If anyone is still experiencing this issue on the latest version, please report it here.

[johncsorensen]

The latest update 13.1.0 (build 193) definitely appears to be working just fine! The Search tool is back in business and do am I. Thanks Adobe!

[blakeb72859779]

Not for me. I can search the meta-data that was already written, but have you tried writing new metadata? That doesn't work for me. And when I downloaded the update, it made my footage playback incredibly slow and jittery in my sequence. On top of that, the LUT had on my adjustment layer was, for whatever reason, causing vastly different results than it was in the previous version. So strange!

[Jeff Bugbee]

I added something to Tape Name and it is searchable. What specifically is not working?

Let's keep the discussion related to Search in this thread. If you have issues with footage or LUTs, please make a new post.

[blakeb72859779]

I added info in Description and it wasn't searchable. And this morning, I even had someone with Adobe gain access to my computer, and go through a variety of steps to see if they could get it to work, but they couldn't. They said they're taking the problem to their director.

[Andy Adkins]

Just upgraded to 13.1.0/193 and so far so good in terms of search bins. Didn't have to re-import to new project or shenanigans.  One thing to note is that it took a sec for the search bins to populate after the project loaded, so at first I thought they still weren't working.

Also tested adding some new metadata (description) and that appeared to work. I was able to create a search bin that found it correctly. Was happy to see it populate super fast in list view w/ no thumbnails.

The inconsistent nature of this bug makes me not want to get my hopes up too much until I've tested it out more, but for now it's looking good and fingers crossed! A few other things feel snappier too including GH5 10 bit playback which always choked before. Is this the update I've been waiting a year-and-a-half for? Will be loading up a few big projects in the next few days and will keeping an eye on all things search, hoping for the best.

Also how do you get somebody from Adobe to assist!!??

[Kevin-Monahan]

Also how do you get somebody from Adobe to assist!!??

Here you go: Adobe Help Center

Link to "contact us" on in the lower left.

Thanks,

Kevin

[blakeb72859779]

Ah! Why won't this work for me!! I feel cursed. And yeah, haha. I was surprised too. I went through their Live chat. He was actually pretty attentive, but also confused by my problem.

[Jeff Bugbee]

Can you try making a brand new project in the new version of Premiere, then import your old project and see if search works?

[Andy Adkins]

Thanks Kevin!

Blakeb: Here is a good place to continue the LUT conversation. Could help you figure out your situation. Bottom line: beware the lut folders. Very weirdly implemented. Be careful changing anything in there unless you test it, understand how it works, and use a consistent workflow.

Linking LUTs by name rather than by position on LUTs list – Adobe video & audio apps

[anthonybarkdoll]

Just updated and search function works!!!

[SpearRanch]

I'm using 13.1.0 (Build 193) and the search folder function provides inconsistent results for me. For example, when I create a search folder seeking 'Media Type' then type "Sequence" in the search field, Premiere correctly creates a new folder with all four sequences located throughout the project. However, when I create a search folder seeking 'Label' and then select 'Forest', Premiere creates a new search folder and incorrectly shows only one sequence - the only sequence in the same folder I'm currently viewing (instead of finding all Forest labels throughout the project. Forest is the label color of all of my sequences. In other words, the search scope using media type was global whereas the scope by label was only in the currently viewed folder.

[charlotte@dynamic]

This issue was fixed in version 13.0.1 (build 13) and every update since the bug is back...

We have 6 machines in our office, every one of them have this bug.

We rolled all our machines back to 13.0.1 (build 13).

It was crippling our production since April 2018, until the 13.0.1 update came out.

we update one machine (mac) every release, test it for a day and then rollback to previous because the search function still not fixed.

Very frustrating.....

[Andy Adkins]

Yea... Not exactly fixed in the 2020 version. Who's testing this stuff? Kevin! Help us! It's hard to come up with the right right adjective for how ridiculous this is. Screenshot kinda says it all so I'll let it do the talking.

HUH?

[laurap443440500]

Maybe it's having a hard time distinguishing between 0 and 6?  After all, they look a little the same. Maybe it needs reading glasses. I was so hoping this problem would be fixed. Time to swtich to another editing system? This is beyond ridiculous. Apparently the idea of having a reliable search function is too basic and boring for the designers of Premiere who'd rather ignore this and introduce "exciting new features!"

[laurap443440500]

Mine is not.

[ETorr]

This post is a year old, the issue goes back almost two years (there's a uservoice entry with 121 replies and 145 votes stretching back to April of 2018), and I remember searching being a problem going on longer than that.

Pinned to that uservoice entry is a July 17,  2018 response from Patrick Palmer, principle product manager of Adobe stating "this issue has been addressed with 12.1.2", and the issue being marked "Completed"), and yet here's lflegg in January of 2019, effectively claiming the opposite, followed by countless posts in this thread, on Facebook and elsewhere.

Searching for footage is, in fact, i.e. finding that shot, is among the most important thing editors do on a daily, hourly, minute-by-minute basis.

Here's another post from 2019 further communcating the issue was not addressed

Would love to hear back from Mr. Palmer about this.  Why not only the lack of a fix but not even a progress resport?

[Andy Adkins]

So.... Search bins still totally untrustworthy eh? Like 5+ years on? Have we just given up and moved on to software that can perform a basic search? I mostly have but still need to use Premiere sometimes and today it's reminding me why I left.

Here I have at least 9 sequences with INTV in the description. A search bin based on that finds.... One.

[laurap443440500]

You have got to be kidding! It's as basic blah tools such as this (that a simple word program could do 20+ years ago) are somehow not important to Adobe.

[ninose11]

It's now April 2024, and the search bin function is still broken! It doesn't even work properly in the Beta version. How many decades do we need to wait for Adobe to get Premiere to properly perform the most basic task - filter and search for an asset in the project window. I don't understand how this is still not working after so many years of people reporting this issue. Why is it that any other program can filter and search instantly and flawlessly, and Premiere can't get this right? I've moved on from Final Cut Pro, but one feature I dearly miss is how any asset you search for in FCP's project window turns up instantly (that asset and only that asset), and you don't need to double click it to see it in the monitor window. Why can't Premiere get this most basic feature right??? 

[Andy Adkins]

Yep - FIVE YEARS and no fix for a broken search. One of the most basic and critical feature for editors. It works ok for small/fresh projets with only a handful of assets which is probably why the massses of youtubers aren't screaming about this. But as a project grows it will eventually fail to provide any search results, or give incorrect results. This has been my experience for many years. Summing it up: search is untrustworthy when you need it most... In projects with thousands of assets.

These are the other reports of the same thing - some go back more like EIGHT YEARS. And I'll add that I have a large project which now straight up crashes every time I attempt to open a search bin (one that used to work). That's a new twist. Zero steps forward two steps back I guess! Nice one Adobe.

https://community.adobe.com/t5/premiere-pro-discussions/premiere-project-and-search-bins-not-searchi...

https://community.adobe.com/t5/premiere-pro-bugs/premiere-pro-cc-2019-13-0-2-search-find-bin-filter-...

https://community.adobe.com/t5/premiere-pro-discussions/search-in-project-not-working-correctly/td-p...

@Kevin-Monahan , can you help us get any tracktion on this? I have seen no indication that anybody is taking this for what it is, which is a serious deal-breaker for large projects (I literally cannot trust search results and I steer fellow editors away from Premiere for this reason) and massive embarrasment of a bug going back nearly a decade.  My hunch is that there has been something fundamentally broken about the core logic of text searching a large dataset since the code was written. Not introduced introduced at some point but just never designed right. Even when it does work it's very weak in the sense that you can't do anything remotely advanced (stringing together several and/or/not operators etc). Really seems like it needs a re-write from the ground up.

[Kevin-Monahan]

Hi @Andy Adkins,

I am on personal leave, and the team is at NAB this week. I hope to respond to you when I return to work. I appreciate your comments, and I'm sorry for the frustration.

Thanks,
Kevin

[Andy Adkins]

Hi @Kevin-Monahan  - We would all appreciate some attention to this. The search bar and search bins (which both seem to be fed from the same faulty search algorithm) just don't work consistently and never really have. (see my previous post/rant)

An umpteenth recent example...

We have a realitvely new and small project with some clips that contain the word "focus" in the comment metadata field. 

Find (cmd-f) finds 3.

The search bar finds 1

A search bin finds 1

See the attached screencap.

PLEASE HELP. This is beyond rediculous at this point. I'm up to date, and I'm happy to provide more information but trust me this has happned on all manner of different OS's, premiere versions, system specs, reboots, trash prefs and everything else. 

[Kevin-Monahan]

Hi @Andy Adkins,

I'll move this to Bug Reports.

Thanks,
Kevin