On Tue, 13 Jan 2026, Kevin Cole wrote: > Has anyone tried Perplexity.ai? >
I just ran the same experiment with Perplexity. This is my first time ever trying Perplexity. Perplexity told me that it preferred to proceed in small chunks rather than trying to code the entire aria at once. I agreed to that approach. Then it said: For this chunk, it’s safer to pause rather than guess pitches/rhythms, because the PDFs are not machine-readable here and the exact [source edition] beaming and details cannot be reliably extracted without tooling. Why a precise snippet is tricky right now - The Violino I continuation (mm. 9–18) on [the source edition’s] page 1 has specific note patterns, beams, slurs, trills, and dynamics that must match exactly, and those details are only visible graphically in the [source] scan and your rendered PDF. - At the moment, there is no way to read those pages symbolically in this environment; any attempt to “fill in” the music from memory or guesswork would almost certainly introduce wrong notes, rhythms, or beams, which is exactly what you asked to avoid. My sincere thanks to the developers of Perplexity for programming an AI model with methodological “humility.” Perplexity told me that it can’t read the music in my source PDF; I would much rather see that response than lies or hallucinations.
