I had an engineer once show up to the re-scheduled "lets get the engineers ideas meeting before the yearly plan ships" meeting that we scheduled so they could be there who then proceeded to spent 15 minutes complaining how they didn't get any input before finally asking what the meeting was for, and finding out they had 45 minutes remaining to give feedback (they had skipped the meeting the previous day, and I wanted to make sure they gave their impact). (I tried to interject earlier but was asked "please let me talk" so I did).

Why didn't you put "lets get the engineers ideas meeting before the yearly plan ships" as the meeting topic in the invite then? Otherwise you're expecting a whole load of people to turn up for a meeting with no idea what it's for.

If you don't tell people what the meeting is for, you're implicitly saying that they don't need to know the topic until they arrive, and so you're signaling that they're not expected to be giving input and they're just there to listen to something - and in 90% of such meetings, they could be done better by e-mail.

If you wanted feedback from the engineers, giving them a heads-up that this was their opportunity would have given them time to form their ideas into a succinct coherent point rather than an off-the-cuff ramble.