Monday, January 9, 2017

Roseblood by A.G. Howard

ARC, 432 pages
Release Date: January 10, 2017
Published by: Amulet Books
Read from: January 6, 2017 
Stand-alone
Source: #BooksforTrade
For fans of: Retellings, Gothic, Dark, Fantasy, YA

     In this modern day spin on Leroux’s gothic tale of unrequited love turned to madness, seventeen-year-old Rune Germain has a mysterious affliction linked to her operatic talent, and a horrifying mistake she’s trying to hide. Hoping creative direction will help her, Rune’s mother sends her to a French arts conservatory for her senior year, located in an opera house rumored to have ties to The Phantom of the Opera.
     At RoseBlood, Rune secretly befriends the masked Thorn—an elusive violinist who not only guides her musical transformation through dreams that seem more real than reality itself, but somehow knows who she is behind her own masks. As the two discover an otherworldly connection and a soul-deep romance blossoms, Thorn’s dark agenda comes to light and he’s forced to make a deadly choice: lead Rune to her destruction, or face the wrath of the phantom who has haunted the opera house for a century, and is the only father he’s ever known.

*MY THOUGHTS*

     When I first heard of this book, I was all for it. And I knew it was something I needed in my life. And then the cover was released and I fell even harder for it. But unfortunately, that was where my love affair with this book ends. It pretty much broke my heart to do this, but I had to do DNF this. 
     Rune has a different type of connection to music. Her mom wants to get her help so she sends her to a school to help hone in on her talent. There she meets someone and their romance blooms. But is he a good person for her or is she doomed to destruction?
     While that description sounds all good, the excution is what I wasn't a fan of. The main thing was the fluff. I am a huge fan of fluff. I love overworked descriptions, to where I feel like I'm in the story. What I don't like, is when a story is ALL fluff. So much so that I have to re-read passages and make sure I didn't miss some important detail because I read over it in the midst of all the said fluff. *takes breah*  lol BUT, unfortunately, with this story, this is exactly what happened. I know many of you may want to read this for your own proof, but, really, a 35 page car ride was a bit ridiculous. I got bored reading the same things over and over. 
     Because the fluff was there, it also made it hard for me to be grabbed by the story. I just couldn't get into the story. It really hurt to not be pulled into it, but it was also monotonous trying to re-read passages and then try to jump back into the flow of reading. after a while I just couldn't do it anymore and gave up. 
     Over all, this wasn't for me, but I know this was a highly anticipated read for many different people. Just because it wasn't for me doesn't mean it won't be for you! Don't give up, still give it a shot! 
DNF @ page 75
However I DID skim the book in hopes that it would cut all the fluff (nope) and I know the climax and what happened. 

To be clear I classify fluff as being too wordy. 

3 comments:

  1. So the problem is that there is TOO MUCH romance? :p

    ReplyDelete
    Replies
    1. lol there's never too much romance. The problem was too much details. Like long drawn out sentences. Hell I hadn't even met the love interest yet in 60 pages lol Well them together lol

      Delete
  2. UGH! I was excited about this book because I am a huge fan of The Phantom of the Opera and I want more retellings but now I'm thinking I'll pass on this one. Not only am I not a big fan of romance heavy books but I do not like when they are wordy with their descriptions. Great review!
    Cassi @ My Thoughts Literally

    ReplyDelete