BWV 1041, migrated from MS3 to Reaper.
Just spent some days, 'migrate' all the 3 movements of
BWV 1041 from MS3 to Reaper DAW.
MP3
https://www.violinhead.com/1041-1-2020.mp3
https://www.violinhead.com/1041-2-2020.mp3
https://www.violinhead.com/1041-3-2020.mp3
All 3 Movements in a single MP3.
https://www.violinhead.com/1041-123-2020.mp3
Total Length 13:36
00:00 - 03:37 1 Movement
03:40 - 09:50 2 Movement
09:53 - 13:35 3 Movement
BWV 1041, MS3 mscz Files that compressed.
https://www.violinhead.com/BWV-1041-2020.rar
Please leave any comments here, thanks.
P.S. the whole process use AirPods Pro as 'Monitor'
Comments
Since, presumably, the quality of the interpretation and performance are at issue here (thank you for providing the .mscz's), I feel it is appropriate to comment on those aspects. If there really is a piano in there (which should be harpsichord, anyway), I can’t hear either.
Referring only to the first movement, the phrasing decisions seem out of touch with Baroque performance practice. Taking mm 100-101 as an example, you shorten the note AFTER a tied group; the break belongs BEFORE that note (i.e., shortening the last of the slurred phrase), not before it (the next note is part of the downward scale in that phrase). You do this a lot. At very least, the MuseScore default staccato of 50% seems wildly inappropriate in Bach, almost always (I have found 75% right for Bach-marked staccati, e.g., https://musescore.com/bsg/scores/5148025 ). But the additional staccati you have introduced for phrasing, sound even worse — please check out the phrasing plugin — a cutback to 85 or 90% will sound much better - what you have sounds like people stereotyping Baroque music, esp the staccato bass notes where Bach indicates no such thing (and 90% would be just great - not legato, but not staccato). What is the additional slur in the solo of 170 etc which defeats Bach’s innate phrasing? Try singing the solo there, and see where you breathe. See my “meticulously phrased renditions” set ( https://musescore.com/user/1831606/sets/5099782 ) for examples of reasonably-phrased Bach.
Finally, I don’t understand the places where violino solo is colla parte with vn1 (e.g. 167) and you have staccato marks in one and not the other.
Leaving these interpretive issues aside, the sound is gorgeous. With such gorgeous sound available, I think there is even a greater responsibility to get the performance details right.
No question: the music you've created in Reaper is impressive. I basically do the same thing: create the core information (score) in Musescore, but rely on Reaper's superior sound reproduction ability to create the actual interpretation, my latest endeavour notwithstanding. I'm curious to see how many other artists have this workflow, particularly to Reaper, as it is a DAW unique in its flexibility, customisability and most definitely price,
In reply to No question: the music you… by robynsveil
OK, you've got me interested. Does Reaper include these beautiful soundfonts?
In reply to OK, you've got me interested… by [DELETED] 1831606
Actually, many find this is one of reaper's biggest downsides: no included soundfonts. There's included plugins, but no libraries as such. To offset that shortcoming is the price: a mere $60. So, you then buy libraries that suit your taste and budget. For example, for someone wanting to create music for films and doesn't need to have granular control over what each instrument does, you've got Spitfire's Discover:
https://www.spitfireaudio.com/shop/a-z/bbc-symphony-orchestra-discover/
which is free. Most composers - particularly one as accomplished as yourself - would want a library where you have more control over articulations. Articulation management also becomes a consideration: Reaper has a number of solutions, mostly no-cost, for this task.
Not sure if this is a case of you asking what time it was and I shared with you how to build a clock, but anyway... :)
In reply to Actually, many find this is… by robynsveil
Uh, are you aware of the articulation plugin I wrote and use every day? (Thanks for the compliment!).
These are exactly what I wanted to know, thanks.
In reply to Uh, are you aware of the… by [DELETED] 1831606
Now that you mention it: I remember you were working on this some time ago, but failed to follow it, unfortunately... your progress was detailed in some very interesting mscz you posted on your page. I have downloaded and will install your plugin... thank you for creating and sharing it, Bernard!
In reply to Now that you mention it: I… by robynsveil
Welcome! I worked on it in the Summer of 2019, ancient history now. I have an entire set of "Meticulously-phrased renditions" you can check out, although I use it with every score I create now, and have posted phrasing tutorials (see my "tutorials" set) as well. Enjoy!
Stunning sound quality!
How do you transfer the score to Reaper?
In reply to Stunning sound quality! by yonah_ag
Not to answer for dds, but the approach I take is to export as MIDI files - one instrument part as one file - and import that into Reaper. I prefer MIDI over xml or mxl but that's just me.
In reply to Not to answer for dds, but… by robynsveil
MIDI files are a blessing when preparing scores for other applications. I use them for driving Hauptwerk (or GrandOrgue), but had to engineer a significant suite of python tools (now public and documented at https://github.com/BernardGreenberg/VPOMIDITools ) for massaging them in transit, including registration and "note-collision" management.