Haven't Met You Yet
Here's something I've been working on for a while. It's the hardest transcription I've done to date. I have a particular chord in there that I'm not quite sure about. If you're familiar with the song you'll catch it in measures 12 and 40. If it sounds ok to you then maybe my judgement is off. If you hear it too, I would appreciate any help in correcting the problem. As it stands, though, I'm still very pleased with my work. Comments are appreciated!
| Attachment | Size |
|---|---|
| Haven't Met You Yet.mscz | 17.45 KB |
Comments
My guess for the right hand in measure 12 is (starting from the top and going down) C-sharp, A-natural, F-natural, and the left hand as it is.
In reply to My guess for the right hand by David Bolton
Not quite, but it's a lot closer than it was, thanks!
Nice :)
Do you think the song is D♭ or C♯?
It's difficult to know for certain because of the other instruments. The right hand sounds more like a (top to bottom) Eb, A and F♯ chord (might not be all those notes, though). Not sure if the bass note is either Eb or D.
Not sure why, but it won't always let me play the score from the note I selected. Also, if a export a MusicXML and import it, it introduces page breaks.
In reply to Nice :) Do you think the by chen lung
C# and Db are basically the same key, so it would be nearly impossible to tell the difference. Personally, my mind translates sharps much better than flats so that's why I chose C#. :)
Yeah, I also have a similar problem during playback. It always starts four measures back from where you select, unless you make a change, in which case it will let you start playback where you selected. But after that initial playback, it falls back to the fourth preceding measure. I'm not sure if when I was getting familiar with the software I changed some playback setting somewhere or if it's a bug in 0.9.6.3 that just never got worked out? But if it was just changing a software setting on my end, then it shouldn't affect playback on your end, because you would have your own different software settings. That would lead me to believe that it's a score setting which *would* play back even on your end (although, it seems this happens on all my scores, making me think twice about it being a software setting). However, if, in fact, it happens t be a bug (which I would think would be fairly unlikely) it should only be present on your software if you are still using 0.9.6.3. which would mean something in my score brought it out in your software. So I'm not really sure what the issue is, as I'm not a software engineer or anything even close.
This is a fairly legitimate issue. I haven't reported it yet just because I could deal with it, but now we at least have two people with the same issue. Help anyone?
In reply to C# and Db are basically the by rj45
My mind does flats better ;)
Maybe doing the score from scratch on a new version would correct it. I've had to do that sometimes - the software is still under development really. If it still happens after that, we could do a bug report.
I used 1.0 and Mac 10.4.11 to load it.
In reply to My mind does flats better by chen lung
It might work on 1.0, but I know that at least on 0.9.6.3, it has done this on every score that I've done so far, so I'm really not sure why it happens but it seems a little odd that a bug would be present on two consecutive versions of MuseScore just because it's never been caught. I'd never really bothered reporting it, primarily just because it wasn't that big of an issue, but...
In reply to It might work on 1.0, but I by rj45
It appears to be no problem on the nightly builds (3996 - Mac 10.4.11), so we can just assume that it's fixed in the future version :).
In reply to It's no problem on the by chen lung
Well, that's good! No real need to report a bug. I can just work around it until I get around to downloading 1.0. I should probably get around to that anyway. O_o
In reply to Well, that's good! No real by rj45
When I export an XML from 1.0 and open it in the nightly build 3996, there's a crash. This suggests a possible inadequacy found in versions earlier than 1.0 - such as a corrupt timing bug (since fixed).
I'd recommend re-doing your score from scratch in 1.0 (via New. Don't work on the old one, or copy/paste from it - just output a PDF or something and use it as your reference) to fix things like this. Doing that may also fix the initial issue.
Perhaps there should be a warning somewhere incase there's such instances: Re-do your score every time there's a new version.
In reply to When I export an XML from 1.0 by chen lung
Redoing the score every time there's a new version should be necessary. The only time it might be necessary is if the old file is corrupted somehow.
In reply to Redoing the score every time by David Bolton
It does guarantee no corruption if you do it again though (something might have been changed, or implemented and perhaps cause a dysfunction, or contradiction).
In reply to Redoing the score every time by David Bolton
Redoing the file "should be" or "shouldn't be" necessary? You either missed a contraction or I'm totally misunderstanding what's being said.
In reply to Redoing the file "is" or by rj45
I think David's post was a typo and he meant "shouldn't".
I'd recommend doing this one again (just this time anyway), mainly because of the crash experienced (likely suggesting a timing bug) and we want to prove the playback issue is definitely fixed.
Usually the score should open in any versions, it's just when there's key, inadvertent or small (any kind really) changes, I'm wary.
In reply to Redoing the file "is" or by rj45
It's funny how a small typo can change the whole meaning! (I meant "shouldn't")
In reply to Correction by David Bolton
Thanks for the clarification, David!
In reply to Nice :) Do you think the by chen lung
Can someone confirm: "Also, if a export a MusicXML and import it, it introduces page breaks."
I can't check as there's a crash when I import a MusicXML score.
In reply to Can someone confirm: "Also, by chen lung
Yes export to MusicXML and import to MusicXML add page breaks. While exporting to MusicXML, MuseScore will save in file where a new system is created. It's a feature to keep the same formatting in MuseScore and another scorewriter.
In reply to Yes export to MusicXML and by [DELETED] 5
Sorry, I should have been more specific.
I think differing Page Setting sizes have made it so that one system (when opening the MusicXML of this score) receives a full page. Are Page Settings recorded in MusicXML?
Also see this .
In reply to Also see this. by chen lung
Lol! Now, why does that sound so familar?
In reply to Also see this. by chen lung
See #9367: [v1.0] Playback Selection error with repeats
I just performed this song as a part of my spring pops concert for choir. You arranged this really nicely, but you're missing some rests. Jazzier tunes usually have more breaths in the middle of a phrase for effect. for example, the line "i might have to wait, i'll never give up" should be sang as "i might have to wait (breath) i'll never give up" with slight staccato on each word. i'm not sure exactly how long the rest would be, but i think it would be either a 16th or 8th rest.
In reply to need more rests by choirgeek2013
You're right. It does need a little more articulation as far as that goes, some fine tuning. I find myself constantly editing the small bugs out of my work (or at least my transcriptions), the kinds of things you usually don't catch unless you're looking for it. Thanks for the suggestions, and I will do my best to incorporate them into the piece. :)
I really like that way you interpreted this song.
In reply to I really like that way you by Cookie Monster_
Thank you! I'm glad you enjoyed it!