您好,欢迎光临琴界。登陆 | 注册
琴界商城 | 网站联盟 | 琴界博客
当前位置: 首页 > 品鉴 > 杰奎琳·杜普雷
品鉴:杰奎琳·杜普雷
【请大家来品鉴】
简介:
杰奎琳·杜普雷(1945-1987),英籍大提琴家,五岁初展过人禀赋,十六岁开始职业生涯,才华与年龄的落差倾倒众生;1973年,被确诊罹患多发性硬化症,遂作别舞台,缠绵病榻十余载,终卒于盛年。《狂恋大提琴》是她的姐姐希拉里与弟弟皮尔斯在1997年合著的传记,其中披露了许多鲜为人知、甚至可以说惊心动魄的舞台背后的故事。这里摘录的,是姐姐希拉里眼中的妹妹,一个被扭曲了人性的天才。

 

      杰奎琳·杜普雷(1945-1987),英籍大提琴家,五岁初展过人禀赋,十六岁开

始职业生涯,才华与年龄的落差倾倒众生;1973年,被确诊罹患多发性硬化症,

遂作别舞台,缠绵病榻十余载,终卒于盛年。《狂恋大提琴》是她的姐姐希拉里

与弟弟皮尔斯在1997年合著的传记,其中披露了许多鲜为人知、甚至可以说惊心

动魄的舞台背后的故事。这里摘录的,是姐姐希拉里眼中的妹妹,一个被扭曲了

人性的天才。

 五岁时,她开始在Herbert Walenn’s 伦敦学校学琴。一九五六年,十一岁时,嬴得the Suggia Award,成为全英国最受瞩目的演奏家,当年的评审还包括了巴比罗里爵士(Sir John Barbirolli)。

  一九六五年,由杜普蕾担任大提琴,巴毕罗里(Sir John Barbirolli)指挥伦敦交响管弦乐团,演出英国作曲家艾尔加(E. Elgar)的大提琴协奏曲(Cello Concerto in E minor, op.85)。这张录音对杜普蕾非常重要,因为它奠定了杜普蕾在演奏舞台上的地位。钢琴家顾尔德曾经说过,杜普蕾的艾尔加协奏曲,呈现了无限的悸动与热情。后来她第一次听到那张与巴毕罗里合作的录音时,曾令人吃惊的说道:「这并不是我想表达的!」只可惜,她无法再录下更好的Elgar,到底她想表达什麼?我们永远无法得知。

  杜普蕾演奏的Elgar没有人会错过,很多人都喜欢听她的协奏曲录音,在管弦乐衬托下,她全身投入,充满朝气,又不失女性的细腻,也不是完全没有节制的放纵自己的情感演出,从她手指尖的传递出来的琴音,让人完完全全地被她的热情与音乐诠释所感染。杜普蕾诠释艾尔加的E小调协奏曲无人能出其右,直到现在,据说只有马友友的演出稍许企及她的境界,但仍然有一段不小的差距。

  据说匈牙利大提琴家史塔克有次乘车,听见广播里正播放大提琴曲,便问旁人是谁演奏的。旁人说是杜普蕾。史塔克说:“像这样演奏,她肯定活不长久。”好厉害的史塔克,真是一语成谶啊!也许只有顶尖的艺术家才能理解自己顶尖同行的水准,史塔克听得出,杜普蕾是用生命在演奏,为了琴艺的完美,可以不惜一切。杜普蕾一直是许多古典音乐乐迷心中的一个叹息。

  一九六七年,她在耶路撒冷和以色列籍钢琴家巴伦波因(Daniel Barenboim)结婚(巴伦波因在一九七五年时,担任Orchestre of Paris的指挥)。杜普蕾和巴伦波因共谱恋曲,为古典乐坛留下佳话。他们不论在生活或是音乐上,彼此都是最佳的伴侣。

  他们合作演出,很多乐评人说是奇妙的一对。杜普蕾和她的先生巴伦波因也多次合作过艾尔加的大提琴协奏曲。他们合作过的版本,是一九七0年,由巴伦波因指挥费城交响乐团演出的录音。这份她与夫婿巴伦波因在一九六七年合作的录音是两人合作灌录的许多唱片中最常被人聆听与谈论的。主要原因是两人在浪漫派音乐上所采取的风格和手法,与布拉姆斯的严谨有很大的差别,杜普蕾在音乐中发挥了她自由的本性,完全挣脱出布拉姆斯音乐里给予大提琴角色的限制(乐曲中钢琴的地位较高),她捉住所有的机会展现她的魅力,而巴伦波因则体贴而充满爱意地予以扶衬。

经典作品

这套《杜普蕾EMI录音全集》为1961~1973年间杜普蕾在EMI唱片公司录制的全部作品,一直未见电驴上有,特发布出来与朋友们共享。其中CD1是著名的与巴比罗利及伦敦交响乐团合作的埃尔加大提琴协奏曲;CD2中的1970年录制的德沃夏克协奏曲也是名版。CD4是杜普蕾留下的最后录音,1971年12月10-11日杜普蕾在没有事先安排的情况下突然来到了EMI的录音棚,录制了弗兰克和肖邦的奏鸣曲。其余的曲目详见Booklet,有些重复的曲目是不同时期的各个录音。

这套CD虽然是一套环保包装的低价盘,音质与制作等未必最佳,但仍是欣赏、了解杜普蕾的较全面参考资料。得益于杜普蕾不管是在音乐会上还是在录音室麦克风前均全力投入的秉性,其琴声的魅力仍然扑面而来。

 

From which maybe you are perched as a Community Designer on Ning, foundation lets out are not quite see-thorugh. The Ning System and also your social support systems go along for several a long time, then give back up, and never considerably has changed.

With nothing observable for you, natural question is why performed we carry all along at all? And, in scarce events like this past weekend, the discharge is followed by a different discharge soon after web site, and maybe you are kept thinking what's transpiring.

So, this is just a little on which continued behind the curtain of Wednesday evening's discharge, and the replace to come on Sunday night…

Wednesday

We started with prep work sixty minutes before the discharge, at 8 in the evening Wednesday (other small products get carried out through the day). Prep work will involve numerous things: priming databases which contain the computer code we will set up towards the computers, which we at Ning contact “cores” (in most, more than 20 Gb of binaries get propagated along the Ning foundation to replace the cores to the next discharge), stopping some notifying solutions that might or else go haywire in the servicing, and undertaking build on life solutions that will have to be started up in the servicing.

The upkeep started on time at 9 in the evening Wednesday, and that we were ready to go. For foundation lets out, we have a program that parallelizes methods wherever possible, but also involves many sychronisation. On Wednesday, the complete discharge course of action was carried out after just one hour – Ning and also your social support systems were going once more regarding “closed doors” by 10:05 in the evening PDT.

Nonetheless, as with every foundation discharge, we all do a full Quality Control look at -mainly automatic – which we clocked at 35 min's to make sure all big efficiency along the foundation and systems. Naturally, we all do many Superior inspections in workplace set ups environments that copy additionally from the Ning System, but you have got constantly some potential from the compact neo-obvious disparities involving the environments which may develop refined challenges reside in production. So before going stay once more, we double check all we can easily.

In such cases, by 10:40 PM on Wednesday we got carried out the QA period properly with the exception of a single item from the “core” that takes care of text messaging from the foundation. We expended the following 25 min's solving small situation that induced this and Ning made a comeback on-line at 11:05 in the evening PDT.

Except for us that’s the starting point. After having a discharge is completed and the site is stay, the team constantly keeps “watch” across the process for as much as two hours, whatever time we carried out the discharge. That is to test and recheck items that could have been neglected. This “platform watch” will involve the business a variety of process wellbeing inspections, storage utilization, and assessing foundation habits under heap with formerly established guidelines, as well as the far more prosaic guide book testing. In such cases, our fear repaid, if we learned that one of the systems from the Ningbar (“My Sites on Ning”) was not replacing appropriately, but while doing so expressing no faults.

It had more than sixty minutes of head-itching and debugging ahead of we seen that we got erroneously impaired one of the bodily listing solutions which was involved with generating that facts. In a different 30 minutes we got checked and two times-checked the answer and through all around 1 am PDT all was normal. We persisted process view right up until 2 am and named it a single night.

Sunday

Sunday at 8 am PDT we have got warns when using internal system which was going to uses up capacity to provide needs. This was not observable to anyone utilizing the Ning System – we have now redundancy integrated at several degrees to circumvent that. We have quite hypersensitive notifying constantly in place to spot, wherever possible, challenges before they grow to be observable by you.

Just for this very first happening it seemed like an isolated function, so we kept it on it's own but persisted enjoying very carefully. At 9:30 am PDT the attentive was once more. These times, the team received on-line to get to the basis reason behind the condition. During this process, we observed other small problems (once more, very little that might impact you straight) we planned to get repaired before the problems became a actual dilemma, by way of example, sub-contract-optimum adjustments on some computers on how they connected to databases.

By 6 in the evening PDT, we got the modified discharge set and QA started. Our program initially ended up being to perform a discharge devoid of entering servicing, but at 7:20 in the evening it started to be clear that was likely to be doable, and that we were required to perform a small thinking time. We stimulated our result solutions but as a result of a entering miscalculation by me nobody received alerted on time. Were now reviewing how you would can prevent this from transpiring once more later on.

We started the discharge course of action lastly all around 7:30 in the evening PDT, and carried out all the methods for the discharge and inspections right after likely live and eat 10:00 in the evening PDT, using the genuine thinking time amongst.

In Conclusion…

All in all, it was not a terrific discharge, from a perspective, or mine. You can be positive we looks at what travelled perfect and what travelled incorrect and do the job to get it perfect the very next time. Meanwhile, we we appreciate you your tolerance, along with applying Ning!

用户评论(共0条评论)

    暂时还没有任何用户评论
总计 0 个记录,共 1 页。 第一页 上一页 下一页 最末页
用户名 匿名用户
内容
 
制作工艺小分类1
制作工艺小分类2
制作工艺小分类3
小提琴中提琴大提琴琴弓配件松香音乐会
商家推荐