No, I understand them completely.
A library will do the hard work for a limited section of what you need, like a XML parser library will give you functions you can use to manipulate your own XML, or a SSL library that will manage the hard work of encryption. Nice and easy, neatly compartmentalized to do 1 thing (hopefully well).
A framework bundles a load of these in, and then also provides you with a load of "boilerplate" that helps you do things the framework is designed to do - eg a web site framework that adds routes and templates for you - so all you need to do is put application logic in the spaces marked "todo".
The problem is that most frameworks do far more than I like, so if you want to step outside what they do, or the way they do it, you're SOL. Similarly, I find that I can more easily create the same functionality using libraries.