Jump to ContentJump to Main Navigation
Blood and Black Lace$
Users without a subscription are not able to see the full content.

Roberto Curti

Print publication date: 2020

Print ISBN-13: 9781911325932

Published to Liverpool Scholarship Online: January 2021

DOI: 10.3828/liverpool/9781911325932.001.0001

Show Summary Details
Page of

PRINTED FROM LIVERPOOL SCHOLARSHIP ONLINE (www.liverpool.universitypressscholarship.com). (c) Copyright Liverpool University Press, 2021. All Rights Reserved. An individual user may print out a PDF of a single chapter of a monograph in LSO for personal use.date: 02 December 2021

Prologue (and Epilogue)

Prologue (and Epilogue)

Chapter:
(p.7) Prologue (and Epilogue)
Source:
(p.3) Devil’s Advocates
Author(s):

Roberto Curti

Roberto Curti

Publisher:
Liverpool University Press
DOI:10.3828/liverpool/9781911325932.003.0001

This chapter provides an overview of Mario Bava's film Blood and Black Lace (6 donne per l'assassino) in 1964. It mentions critics and commentators of the Blood and Black Lace movie who were spellbound by its fascinating visual analogy that links the opening and final images. It also looks into analyzations of the film that proposes the most disparate interpretations. The chapter discusses Bava's demystifying explanation of his movie in an interview published in 1979, just one year before his death. It talks about the significance of the opening scene of Blood and Black Lace and interprets the connection between the signboard swinging at the beginning, during a rainstorm, and the telephone falling on the ground.

Keywords:   Mario Bava, Blood and Black Lace, visual analogy, signboard, rainstorm

Liverpool Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs, and if you can't find the answer there, please contact us.