Hi,

not sure if this is a bug. Don't wanna noobishly spam to the devs' bug reports pile but this needs to be clarified. Is it a deken issue or on the repository or what?

Some searches for externals in the 64-bit version of PD vanilla for windows (I'm on windows 10) the deken search (in the menu: Help -> Find externals) don't return results while the same externals (in some cases) can found on the 32-bit version. Some externals are neither found in the 32- nor 64-bit version. Additionally - as a marker that something is wrong here - PD does not output the line

[deken]: No matching externals found. Try using the full name e.g. 'freeverb'.

which is the case for truly non-existing names (like searching "sdfsdfsdf").

Example of external found as expected on 32- and 64-version:
cyclone

Example of external found as expected on 32- but NOT on 64-bit version:
moonlib

Example of external found neither on 32- or 64-bit version:
apple

What I'm most eager to find out is whether, say, the moonlib external is just not compiled for 64-bit windows and therefore is not found or whether it should be found and just isn't (which hints more towards a bug).

Does anyone have an idea? I'm not completely new to PD but not up to date at all with its development. It seems the current version 0.49 vanilla is the first to have a 64-bit windows version.

kind regards

@oystersauce You are looking for freeverb~ ...... which has been compiled for 64-bit windows and is available on Deken.
I am pretty certain that your recent posts are all about the same problem.
If nobody has recompiled an external for 64-bit for the OS that you are running (and added a link to Deken) then Deken will not find it.
Some externals might have been compiled but not added, some have not been compiled, and maybe some cannot be compiled.
You might find repositories for the C code on github that will allow you to compile for your system.
Please share them afterwards as it will help others with the same problem.
64-bit Vanilla is starting to have some useful tools, but if you don't need them or the higher precision of 64-bit then Extended or Deken for 32-bit Vanilla are still a better bet at the moment.
Of course on a 64-bit OSX that is not an option.
If you are willing to try a fork like Purr Data then the developers are often more active and willing to help rebuild old (or even new) externals for their version.
A lot of people have been looking for [knob] and @yoichi_tbbb recently made a great one here........ https://forum.pdpatchrepo.info/topic/10938/new-knob-gui-object which I am surprised no-one has compiled for 64-bit.
David.

@whale-av thank you for that extensive answer! I will finally have a look at Purr Data and check out @yoichi_tbbb's awesome looking knob.
I'm not looking for freeverb~ though. It's only what deken outputs in case it finds nothing for a search.

By the time I posted this question I was already suspecting what you said about the various externals and the 64-bit versions.

One thing is still irritating. When I enter a random search term in deken, it returns a proper "nothing-found-message" as you would expect. Try it. Type "sdjfhskdjfh" in the search box and deken will return almost immediately:

[deken]: No matching externals found. Try using the full name e.g. 'freeverb'.

But when I search an existing external's name, like "moonlib" for example then deken will not show a result but also never tell me it found nothing. That's confusing. It makes users wonder if something is broken with the search or if there's really nothing adequate in the repository. Don't you agree?