Casual Encounter
"Casual Encounter" is a song by Australian rock band Divinyls, released in August 1983. The song originally appeared on the Australian release of the band's debut album Desperate, but first appeared on the international release of their second album What a Life!. "Casual Encounter" did not meet with success when it was released as a single, only peaking at number ninety-one on the Australian Kent Music Report singles chart.
| "Casual Encounter" | ||||
|---|---|---|---|---|
 | ||||
| Single by Divinyls | ||||
| from the album What a Life! | ||||
| B-side | "Gonna Get You" | |||
| Released | August, 1983 | |||
| Genre | Rock, new wave | |||
| Length | 3:05 (single and What a Life! versions) 3:17 (original Desperate version) | |||
| Label | Chrysalis Records | |||
| Songwriter(s) | Christina Amphlett, Mark McEntee | |||
| Producer(s) | Mark Opitz | |||
| Divinyls singles chronology | ||||
| ||||
On the original Australian version of Desperate, "Casual Encounter" ran 3:17 and had a proper ending, but the single and What a Life versions just faded it out at the 3:05 mark, which was carried over to Greatest Hits in 2006.
Track listing
- Australian 7" Single[1]
- "Casual Encounter" - 3:05
- "Gonna Get You" (Re-recorded)
- "Only Lonely" (Live)
Charts
| Chart (1983) | Peak position |
|---|---|
| Australian Kent Music Report Singles Chart[2] | 91 |
gollark: I mean, if people actually want a server, I can host it on my stuff.
gollark: BigReactors is kind of boring, the reactors have weird rules and don't explode. There's Nuclearcraft, which is arguably more realistic, though.
gollark: https://www.archmission.org/spaceil ← interesting real-life implementation of pretty long-term storage
gollark: No, Intel stuff is affected by both, basically every modern one including ARM by spectre.
gollark: I'm pretty worried about the effects of Spectre/Meltdown. Apparently Spectre, at least, affects basically all modern/high-performance CPUs, and can't be patched without large performance drops. It probably wouldn't have been an awful vulnerability to have around probably a few decades ago, but now basically everything executes some untrusted code (JS in browsers, cloud providers running people's workloads, etc.) Which probably means a significant security/speed tradeoff, and there's not really any right way for that to go...
References
- http://notsorted.tripod.com/DIV.discog.html
- Kent, David (1993). Australian Chart Book 1970-1992. St Ives, N.S.W.: Australian Chart Book. p. 91. ISBN 0-646-11917-6.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.