• TalkBass has been independent since 1998. Add your voice.
    Create a free account to reply to discussions, view embedded media, and browse with fewer display ads.
    Join freeLog in
    Want zero display ads or expanded classifieds tools? Compare plans.

Cool rock n roll photos

Sam Cooke & the Soul Stirrers at Carver High 1956
1781749321606.png

1781749434081.png
 
Freddie Tavares, born in 1913 in Paia Hospital became a well respected steel guitar player who moved to Honolulu and played throughout the '30s and '40s in Waikiki. then moved to California as a session player for Dean Martin, Frank Sinatra, Henry Mancini, Elvis, and many others, then hired in 1953 at Fender Guitars where his first task was to help design a new guitar which was then named the Stratocaster. the wild glissando heard on the old Warner Bros. Looney Toons cartoons, that's Freddie on a Dobro steel.
1781779532245.png

 
on Oct. 5, 1968 after a concert at the Honolulu International Center, Jimi Hendrix walked across the street with his girlfriend, Mitch Mitchell and some gear to crash an Art Park music festival to give an impromptu jam session for the crowd who couldn't make the sold out concert, under a lunar eclipse.
From the archives: That time Jimi Hendrix played at the Museum
1781780726802.png
 
this ain't cool just like Bread were not rock n roll, but nobody and no gear deserves this.
BREAD played what would be their final concert on June 21, 1973, in Salt Lake City, a trucking accident earlier that day destroyed much of the band's equipment. Rather than cancel the show, the band took the stage using borrowed instruments and amplifiers, determined not to disappoint their fans.
1782083508908.png
 
this ain't cool just like Bread were not rock n roll, but nobody and no gear deserves this.
BREAD played what would be their final concert on June 21, 1973, in Salt Lake City, a trucking accident earlier that day destroyed much of the band's equipment. Rather than cancel the show, the band took the stage using borrowed instruments and amplifiers, determined not to disappoint their fans.
View attachment 7520376
I’m smelling AI with that one.
 
I don't know. There was the truck wreck that destroyed their equipment. It would be normal that people took pictures.
It has the visual texture of much of the confirmed AI that I’ve seen, and there’s so much about the composition of that shot that is hinky. Just what type of combo amps are those? In archival live photos, the only combo I ever saw was a Fender Twin, otherwise they had Showmans, Sound City, Marshall, and an Acoustic 360 or Fender Super Bassman for bass.
 
1782104274903.png


"Gemini is AI and can make mistakes."


ALSO:

I just asked Gemini "is Google AI under some server duress? Its been acting 'crazy' lately"...

(reply)
You aren't imagining things—Google’s AI infrastructure has actually been under some genuine duress recently.

If you've noticed it throwing connection timeouts, failing to complete requests, or just generally acting "crazy," it aligns perfectly with a few major backend strain points over the last few weeks:

  • The June 10th Global Outage: Just a couple of weeks ago, Gemini suffered a massive, unprecedented global blackout that lasted for over six hours. Users worldwide were hit hard by two specific errors: Error 1076 (connection timeouts) and Error 1099 (a server-side crash that locked out both free and Workspace accounts).
  • API and Caching Strains: Throughout late May and into June, Google AI Studio and the underlying Gemini API have been dealing with recurring, unacknowledged blips. Specifically, there have been documented issues with context caching (which makes the AI work harder and less efficiently) and intermittent spikes in API latency.
  • Massive Infrastructure Demand: The background reason for the strain is sheer load. Google has been aggressively rolling out deep browser integrations (like Gemini in Chrome across several international regions) right alongside scaling up major enterprise partnerships—like powering Apple’s Siri backend.
When a massive language model infrastructure scales that fast, the load balancers and token caches can get choked up, resulting in erratic behavior, dropped context, or flat-out error pages.

Things are largely stabilized right now, but if it starts acting up again on your end, it’s usually a transient server-side queue backup. A clean page refresh or hitting "re-submit" on your prompt often bypasses the choked node.