Jump to content

Search the Community

Showing results for tags 'Vocals'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CustomsForge
    • News & Announcements
    • Ignition4 Search
  • General
    • Rocksmith Remastered
    • Rocksmith Championship
    • Music Discussion
    • Off-Topic
  • Rocksmith CDLC
    • Workshop
    • Learning Guitar & Bass
  • Rocksmith 2014 Remastered Tools
    • CustomsForge Song Manager
    • Editor on Fire
    • DLC Builder
    • RSPlaylist / RockSniffer
    • Mods & Projects

Collections

  • Ignition4

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Member Title


Website URL


Steam


Twitter


Twitch


Discord


Location


Interests


Guitar


Bass


Favorite Bands


Rocksmith

Found 8 results

  1. SEALS & CROFTS Hummingbird https://youtu.be/3WT2Tz6SV68 download Summer Breeze https://youtu.be/ywL6tMQdG4c download Yellow Dirt https://youtu.be/Q1nMDCvxePw download Wisdom https://youtu.be/CP7K6B6cE8o download Ledges https://youtu.be/5y88R7iTy0A download Thunderfoot https://youtu.be/p5jHDCChU0c download ---------------------------------------------------------------------------------------------------------------------- Bert Jansch Avocet https://youtu.be/laROagHBwbs download Kingfisher http://youtu.be/__Bdkzy1f5I download Osprey https://youtu.be/npB8RylB2zQ download
  2. Hi all, I was updating a track with all the latest tools, and I encountered an error when trying to load my vocals track into RST: Here is the xml. RST v 2.8.2.0-3ee97055 EoF v 5-3-2017 Please let me know what other data may help debug the issue. Thank you very much, Tysylio
  3. https://www.dropbox.com/s/mbezltz3irn3lkc/Captura.PNG?dl=0 I got this error adding and editing vocals on the template, for all the song that I try to make. What's the problem? Another question: Why is not posible to put spanish characters like á or ñ in vocals? In other versions before works fine. Examples in Maná songs.
  4. Download: LRCconverter.xlsm v.2.7 (2017-02) ---------------------------------------------------- Instructions: 1. Get lyrics file in .LRC format. (see LRC wiki) 2. Convert .LRC file content in LRCconverter.xlsm 4. Import new .LRC to EOF ---------------------------------------------------- LRCconverter.xlsm is Excel(required) Macro-Enabled Spreadsheet. http://killeroyo.webatu.com/RS24_CDLC/Screenshot27.jpg Example LRC line (text is too long and 3 time signatures causing import error in EOF): [03:59.76][04:16.13][06:35.17]Something to save me from myselfAfter converting (sentence is splitted to single words and time + leading silence time is added): [04:02.76]Something [04:03.66]to [04:03.86]save [04:04.26]me [04:04.46]from [04:04.86]myself [04:05.46] [04:19.13]Something [04:20.03]to [04:20.23]save [04:20.63]me [04:20.83]from [04:21.23]myself [04:21.83] [06:38.17]Something [06:39.07]to [06:39.27]save [06:39.67]me [06:39.87]from [06:40.27]myself [06:40.87]
  5. So I've been using Ultrastar creator all the time for my lyrics and then importing in EoF and adjusting them. Now most of the time the last ~2 sentences of the lyrics aren't shown in Rocksmith when playing. I have no idea why this happens and just accepted it, as it is only a few sentences. But latest songs I made have ~half of the lyrics missing. Does anyone have an idea why this occurs? Maximum word count? Error with some characters? To much sections?
  6. I want / need to display the minus sign "-" in my vocals. In EOF, it looks like the way it is supposed to be: Ih-ah! Ih-ah! Now the following is from the generated XML: <vocal time="67.810" note="254" length="0.997" lyric="Ih-"/> <vocal time="68.810" note="254" length="1.247" lyric="ah!"/> <vocal time="70.060" note="254" length="0.747" lyric="Ih-"/> <vocal time="70.810" note="254" length="0.997" lyric="ah!+"/> And in Rocksmith this becomes: Ihah! Ihah! Is there a way to "protect" a minus sign from beeing interpreted as a separator of syllables? Edit: I tried including a "dash" instead... First I tried –, but this gives an error in the toolkit. Then I tried ‒, but this gives only an empty space in Rocksmith Now there are many more codes for dashes, if noone has an idea I will probably end up testing them all...
  7. Hi, I'm trying to make CDLC for RS 2014 and I have found theese problems so far. I searched for a solution in the forums but I haven't found anything. 1. I don't get an .xml archive for the vocals when I save my Eof project. I get this error message: http://s22.postimg.org/5nh4ysg7l/lyric_export.jpg 2. When i put my bass line (part real_bass or part real_bass_22, i tried both) it says it's not valid for RS 2014. It works if I make the DLC for RS 2012 : http://s28.postimg.org/wgtntk3dp/Valid_arrangement.jpg 3. I tried to "fool" the Tool Kit by uploading the bass for RS2012 and then change the dlc to make it for RS2014, but then I got this other problem and then it crashes. I followed the tutorial to get the .wem, so that shouldnt be the problem http://s27.postimg.org/9ds29ozeb/wem_not_found.png I hope you can help me, especially with the second problem because i think that's the main reason I cant get my cdlc to work
  8. Hi all, with the help of tips from BHMath, pgboyd and raynebc, I was able to conduct some tests to help me verify how lyrics work in Rocksmith. First my conclusions and if you are interested I substantiate those conclusions with screenshots below. Each conclusion made has a corresponding number in the Substantiation section. Perhaps it is worthwhile specifying here that I only tested Rocksmith 2014. CONCLUSIONS 1. pgboyd's suggestion to me of keeping a pitch-adjusted or sustained lyric as one word but sustained with the ] button or mousewheel in EoF works and imo is elegant in its authoring and in its presentation. 2. So a dash at the end of a text note, in EoF, attaches that word with the next. The intent of adding a dash at the end of a word is to separate a word into separate text notes for each syllable, and the game concatenates them into one word without a dash, but highlights the word in blue 1 syllable at a time as the lyric text is sung. 3. So a dash inside a single text note, in EoF, puts a dash inside the word in-game. 4. i) The existence of + symbols in the EoF interface, no matter the number of them, do not seem to be responsible for line-wrapping in the case of a lyric line resembling the format "No more li + + + + + + es" ii) As raynebc stated, the + signs after a text note, in this case "Li", serve to adjust the amount of time the text note stays blue (i.e. should be sung). iii) The + signs in EoF simply indicate a duration that the text note need be sung, without any distinction between pitch changes or constant pitch vocal sustains. 5. i) Reducing the blue-marked lyric line length in EoF, using the CTRL+M shortkey, has no effect on the undesired text wrapping problem, no matter how long or short the blue-marked lyric line is. ii) Blue-marked lyric line length has no effect on how quickly the lyric lines scroll from one lyric line the the next. What does affect the lyric line scrolling speed is how imminent the next lyric note of the next lyric line is. Interesting that the triggering lyric note on the next line can be a + sign which will be invisible in-game, therefore cannot turn blue to indicate player to sing. iii) Blue-marked lyric length in EoF does, if possible, fit the lyrics in the marked area in one line in game. iv) If a lyric line is short enough, and an adjacent lyric line is not blue-marked as a lyric line in EoF, Rocksmith 2014 will put both the short blue-marked lyric line and as much of the non-blue-marked lyric line possible on the same line in-game. 6. i) Undesired lyric line wrapping onto a next line in game is independent of + signs in the EoF lyrics. Rocksmith seems to simply want the duration of lyric lines space between text notes, be they syllables or entire words to be less than approx. 3 seconds, or perhaps approximately less than 1.5 measures. This number is by no means exact but reflect findings for one CDLC. Perhaps these guidelines will apply to other CDLC, but that is uncertain until more tests are conducted. Not currently planning to test further, unless you guys compel me to. ii) This issue of undesired text wrapping came about due do the use of + signs to sustain the text note. If a text note was not split up in Ultrastar Creator and EoF, then presumably this issue would not arise. Though it is expected that there is a limit to a lyric line character length that will display on one line in-game. This limit is unknown to me at this point. I did witness very long lyric lines in Nirvana-SmellsLikeTeenSpirit-ex5-v.1.1-ForRS14PC-RR-Lead,Rhythm,Bass,Vocals-Estd-ACESHIGH_p.psarc that may be worth observing. 7. All this long-winded post to recommend that you simply follow BHMath's & pgboyd's 2-line recommendation posted above summarized in Conclusion 1. Otherwise as per Conclusion 6, you can keep the + signs you imported from Ultrastar into EoF, but must be careful to avoid the end of the intended lyric line being too far from the beginning. How far is too far exactly would require more testing, but maybe a lyric line shouldn't exceed approx. 3 seconds or approx. 1 or 1.5 measures. Maybe this changes with a different BPM song. 8. You can biff me in the head for being such a nerd. I just hate having worked so hard on a CDLC for it not to be perfect. Any way, I hope some of this can help you demystify lyrics in Ultrastar/EoF/Rocksmith 2014. CONCLUSIONS ADDENDUM 6. i) It is not the duration of lyric lines that must be less than approximately 3 seconds in order to prevent wrapping, as originally concluded, but rather the time between adjacent text notes that must be less than approx. 3 seconds to avoid text-wrapping to the next line in-game. See test screenshot in the corresponding substantiation numbered section below. 9. Building on Conclusion 2, the only way to concatenate text notes that are more than approx. 3 seconds apart is to author in EoF, all but the last text note intended for concatenation with a dash at its end (Example: In- doc- trin- a- tion). See test screenshot in the corresponding substantiation numbered section below. 10. The "+" signs exported from Ultrastar Creator into EoF simply add sustain (text blue longer than nominal time) to the text note preceding it and as soon as an adjacent text note (be it a syllable or a word) occurs more than approximately 3 seconds later, the text will wrap to the next line. A "+" sign in EoF is therefore not a concatenation character string as implied in UltraStar Creator's help tips. Note that although the use of the "[" and "]" are better suited to add sustain to a text note, the use of a "+" text note will override whatever sustain is defined in the bottom of the piano roll for that note. See test screenshot in the corresponding substantiation numbered section below. 11. If two text notes are far enough apart in time, whether both marked together as being part of a super long lyric line or not, the first part of the lyric will eventually disappear after 3 or 4 seconds, and then, when the song approaches the end of the lyric, a new line will appear. See test screenshot in the corresponding substantiation numbered section below. 12. Marking a lyric line in EoF by selecting the text notes in question and pressing CTRL+M places a "+" sign in the EoF-outputted-Vocals-XML file at the end of the last text note of the marked lyric line. This "+" sign serves in the XML file (we're not talking about the "+" sign in EoF anymore but rather in the XML!) to indicate to the game that a carriage return is required after the last text note marked. If the marked lyric line exceeds a certain maximum, then it will simply wrap the remainder to it's own next line of text. 13. In the absence of a lyric line being marked with CTRL+M, no "+" carriage return sign will be exported to the output vocal XML file and Rocksmith will choose how best to split up a sequence of unmarked lyrics, such as concatenating as many text notes as it can to fit in one long line of text or wrapping text notes (possibly just syllables if notes were broken down into syllables) to the next line of lyrics shown in-game that it may have to share with the next lyric notes, whether marked as a lyric line or not. See test screenshot in the corresponding substantiation numbered section below. VERY NERDY SUBSTANTIATION OF CONCLUSIONS Test 0 - Original Problem: Here is a look at what I did. In Ultrastar I entered the following" No more li+~+~+~+~+~+~+es No more li+~+~+~+~+~+es The Ultrastar output file looks as follows for the two lyric lines in question: : 8168 2 0 No : 8175 2 0 more : 8183 2 0 li : 8194 3 0 ~ : 8209 2 0 ~ : 8220 3 0 ~ : 8234 2 0 ~ : 8245 2 0 ~ : 8252 2 0 ~ : 8269 2 0 es - 8281 : 8292 2 0 No : 8303 2 0 more : 8310 2 0 li : 8324 2 0 ~ : 8337 3 0 ~ : 8369 3 0 ~ : 8378 3 0 ~ : 8387 2 0 ~ : 8395 2 0 es - 9265 Which PART VOCALS_RS2 imported as: <vocal time="395.888" note="254" length="0.079" lyric="No"/> <vocal time="396.163" note="254" length="0.079" lyric="more"/> <vocal time="396.478" note="254" length="2.794" lyric="li"/> <vocal time="399.862" note="254" length="0.079" lyric="es+"/> <vocal time="400.768" note="254" length="0.079" lyric="No"/> <vocal time="401.200" note="254" length="0.079" lyric="more"/> <vocal time="401.476" note="254" length="3.109" lyric="li"/> <vocal time="404.821" note="254" length="0.079" lyric="es+"/> Which surprised me a bit since there is only a line-break information (+ sign) and not pitch change information as I had intended in Ultrastar with the addition of +~ symbols. In EoF it appears as follows: http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/EoFView_zps5b7ffdce.png?t=1389931384 In game it appears as follows. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/LyricLineUndesiredSplit_zpsca46e8af.png?t=1389930534 "No more li + + + + + + es" as displayed in EoF wraps "es" alone to the next line in-game as per above posted screenshot. "Li" part becomes and stays blue until the singer sings "es" of the word "lies", then "es" on the next line quickly becomes blue then quickly becomes dark again as the next line is sung. Test 1 - pgboyd's and BHMath's elegant suggestion: Removed +'s imported into EoF Interface from Ultrastar; erase "es" of "Lies"; Change "Li" to "Lies. Use "]" key to increase sustain of "Lies" note and see bar just below the piano roll increase in size. RESULT --> "Lies" stays blue in game for duration of the time that word is sung out by the singer. Test 2 - Effect of dashes at the end of the word as per raynebc's and BHMath's posts : Removed +'s imported into EoF Interface from Ultrastar; erase "es" of "Lies"; Change "Li" to "Lies". Then add dashes after each word: "No- More- Lies- " RESULT --> Appears in game as "Nomorelies-" Test 3 - Effect of Dash in the middle of a word as per aludog's post: Remove +'s imported into EoF interface from Ultrastar; erase "es" of "Lies"; Change "Li" to "Lies". Then add only a dash in "Li-es" RESULT --> Appears in game as "No more li-es" Test 4a - Try to make lyrics work with + signs to corroborate raynebc's assertion. Remove 1 + sign between "li" and "es" in "No more li + + + + + + es": RESULT --> If remove 1st + sign --> The word "Lies" is still split over two lines. If remove last + sign --> The word "Lies" is still split over two lines. Test 4b - Remove 2 + signs between "li" and "es" in "No more li + + + + + + es": RESULT --> If remove first 2 + signs --> The word "Lies" is still split over two lines. If remove last 2 + signs --> The word "Lies" is still split over two lines. The "Li" half-word loses it's blue shading earlier since the removal of the last plus sign ends the sustain earlier. Presumably same thing happened in Test 4a but was less perceptible since only 1 + sign was removed (less curtailed sustain) Test 4c - Remove 3 + signs between "li" and "es" in "No more li + + + + + + es": RESULT --> If remove first 3 + signs --> No change If remove last 3 + signs --> No change. Sustain even shorter on "Li" Test 4d - Remove 4 + signs between "li" and "es" in "No more li + + + + + + es": RESULT --> If remove first 4 + signs --> No change If remove last 4 + signs --> No change. Sustain even shorter on "Li" Test 4e - Remove all 6 + signs between "li" and "es" in "No more li + + + + + + es": RESULT --> No change!!!! STRANGE, no plus signs and "Li" and "es" are still split!!!!! Looks like text wrapping is a lyric-line marking or duration related problem as raynebc thought it might. Test 5a - Play with marked blue area length in EoF: Mark the lyric line (CTRL+M) from "Li" to last + sign. RESULT --> See screen shots in EoF and in-game. Very interesting, the reduced lyric line blue area didn't solve the word wrapping problem, but the following "es" seems to be short enough that the game chooses to put the following lyric line on the same line as "es". This is unexpected because, presumably the lyric line "No more li + + + + + + es" may be too long to fit on one line but the game suddenly has enough space to fit it all if the "es" is placed in front of "No more li" .... hypocrite :) http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/ReduningBlueMarkedArea-tilllastplussign-EOFview_zps194077e0.png http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/ReducingBlueMarkedArea-tilllastplussign-Gameview_zps1fd43ad2.png Test 5b - Mark the lyric line (CTRL+M) from "Li" to 2nd last + sign.: RESULT --> See screen shots in EoF and in-game. --> Line wrapping problem not solved. In-game the lyric lines look the same as Test 5a. --> Note that with the shortening of the blue marked area in EoF, the result in-game was to carriage return more quickly than when the blue marked area was longer. Perhaps the blue marked areas really do have an effect in game after all. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/ReduningBlueMarkedArea-till2ndlastplussign-EOFview_zps47413ccd.png http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/ReducingBlueMarkedArea-till2ndlastplussign-Gameview_zps1678a25a.png Test 5c - Mark the lyric line (CTRL+M) from "Li" to 3rd last + sign.: RESULT --> See screen shots in EoF and in-game. --> Line wrapping problem not solved. In-game the lyric lines look the same as Test 5a. --> Again, lyric line in-game scrolled faster to the next line. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/ReduningBlueMarkedArea-till3rdlastplussign-EOFview_zps48ad0404.png http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/ReducingBlueMarkedArea-till3rdlastplussign-Gameview_zps1238f891.png Test 5d - Let's jump a couple of steps and see what happens when we mark the lyric line with CTRL+M in blue from "No" to "Li" with no plus signs in the marked area.: RESULT --> See screen shots in EoF and in-game --> Line wrapping problem not solved. In-game the lyric lines look the same as Test 5a. --> Again, lyric line in-game scrolled faster to the next line. Very fast this time, almost immediately after the "Li" text note was started. You can sort of get proof of this in the screenshots of Tests 5a,b,c,d because I had to gradually, with each successive test, take the screenshot with the F5 power chord further away in the distance or else the lyric line would scroll to the next line. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/ReduningBlueMarkedArea-tillendofLiinLies-EOFview_zps599d0e09.png http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/ReducingBlueMarkedArea-tillendofLiinLies-Gameview_zps0949e57b.png Test 5e - Keep "No more li" as one blue-marked lyric line like Test 5d, but now mark the " + + + + + + es" as another lyric line.: PURPOSE --> See by careful selection of blue-marked lyric line, if can disrupt the in-game pattern of displaying: "No more li" "es No more li" RESULT --> See screen shots in EoF and in-game --> Interesting, this time the blue-marked choice had an impact. Defining a lyric line for " + + + + + + es" forced "es" to have an in-game line to itself. --> Again the "No more li" scrolled to the next line very rapidly as in the previous case. --> Since "+ + + + + + es" in game appears as "es", it is short enough that in previous tests 5a,b,c,d, Rocksmith allowed the next line "No more li" to fit on the same line since I didn't impose any constraints. Now that I imposed a constraint, " + + + + + + es" becoming an independent lyric line, the game respected the new blue-marked lyric line and gave " + + + + + + es" a line to itself and appeared as "es" on a line by itself. --> My theory as to the reason for the faster scroll with shorter blue-marked area is not that the blue-marked area tells the game when to scroll to the next line, but rather I noticed from examining several lyrics throughout the song, that an in-game lyric line stays put, even if the blue words turned dark already, until the next lyric of the next lyric line starts. In our case, in Tests 5a,b,c,d, we simply blue-marked one less + sign at a time. So the reason the in-game lyric line "No more li" was sung and increasingly quickly (with successive tests) scrolled to the next line was that 1) there were less + signs in the lyric line to sustain the "Li" text note and 2) the next + sign, the first of the next lyric line (whether marked as a blue lyric line or not) triggered the lyric line scroll. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/ReducingBlueMarkedArea-Blue1tillLiBlue2es-EoFview_zps041f0243.png http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/ReducingBlueMarkedArea-Blue1tillLiBlue2es-Gameview_zps0f69d943.png OK, so the wrapping text problem could only be a lyric line length/duration issue. Let's check below. Test 6a - Shorten the duration of the intended lyric line to gauge how long the game will accept: Shorten the lyric line to the last + sign, replacing the + sign with "es" RESULT --> See screen shots in EoF and in-game. --> Lyric line not short enough, "es" in "Lies" still wraps to next line. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/Removelastplusandreplaceswitheserasingfartheres-EoFview_zpsb0872415.png http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/Removelastplusandreplaceswitheserasingfartheres-Gameview_zps13ad1d0e.png Test 6b - Shorten the lyric line to the 2nd last + sign, replacing the + sign with "es": RESULT --> See screen shots in EoF and in-game --> Ta-da!!!! The intended lyric line. No text wrapping to next line. Small forgivable space appears in-game between "Li" and "es". The "Li" becomes blue during the sustain, then the "es" in "Lies" becomes blue as intended. --> This works perfectly, except that it's not a solution for this song since reducing the duration of this lyric line in EoF, means the singer is still singing the word "Lies" after the word "Lies" goes dark, while we wait for the game to scroll the lyrics to the next lyric line. --> This test shows that the game is designed to display lyric lines that last too long --> My guess is that it is a time duration problem that cause the wrapping since the words "No More Lies" don't really constitute a long lyric line, given that + signs in EoF disappear in game and are instead transmitted from EoF to the game via the PART VOCAL_RS2.XML file which simply knows text note length via variable "length" --> The PART VOCAL_RS2.XML file lines in question that yield success in Test 6b was as follows: <vocal time="395.888" note="254" length="0.079" lyric="No"/> <vocal time="396.163" note="254" length="0.079" lyric="more"/> <vocal time="396.478" note="254" length="2.086" lyric="li"/> <vocal time="398.930" note="254" length="0.100" lyric="es+"/> <vocal time="400.768" note="254" length="0.079" lyric="No"/> <vocal time="401.200" note="254" length="0.079" lyric="more"/> <vocal time="401.476" note="254" length="2.440" lyric="li"/> <vocal time="404.170" note="254" length="0.100" lyric="es+"/> First of the two problematic lyric lines: Total duration: 2.344 seconds. (approx: 1 3/16 measures) Second of the two problematic lyric lines: Total duration: 2.698 seconds. (approx: 1 3/8 measures) http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/Removelast2plusandreplacewitheserasingfartherplusandes-EoFview_zps6479a594.png http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/Removelast2plusandreplacewitheserasingfartherplusandes-Gameview_zps4306dc73.png TESTS ADDENDUM (Results appear in Conclusions above) Test 6a (Take 2) - Time between adjacent text notes must be less than approximately 3 seconds to avoid wrapping: RESULT --> See screen shot. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/TEST6iAddendum-INDOCTRINATIONNODASHESNOPLUSSES-InEoF_zpsa73b1243.png Test 9 - Using dashes to keep syllables of a same word from wrapping to two different lines in game: RESULT --> See screen shot. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/TEST9-INDOCTRINATIONWITHDASHES-InEoF_zps3cba53a9.png Test 10 - Using "+" signs in EoF as a an alternative way to control text note sustains: RESULT --> See screen shot. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/TEST10-INDOCTRINATIONWITHPLUSSES-InEoF_zpsf2fef88e.png Test 11 - How a long marked lyric line with distant text notes behaves: RESULT --> See screen shot. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/Test11-LongLyricLinewithMarkinganddistanttextnotes-Notsyllables-InEoF_zps26a190ef.png Test 13 - How unmarked lyric lines behave: RESULT --> See screen shot. http://i920.photobucket.com/albums/ad41/Berneer/SmithyAnvilStuff/Lyrics%20Questions/Test13-LongLyricLinewithoutMarkinganddistanttextnotes-Notsyllables-InEoF_zpsed8acc65.png
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy