Berneer

1) I forgot to summarize in my last post that only one dummy <chordTemplate> need exist to be invoked by as many dummy <chordtime> tags as authored. 2) I had also confirmed that "dummy chordId dummy chords" will score per the single notes superimposed on them which is a flexibility not afforded by the "handshape chordId-1 dummy chords" which need to have identical superimposed single notes and vanished chordnotes in order to score properly in-game. Setting ignore = 1 on the "dummy chordId dummy chords" <chordtime> tag doesn't prevent the single notes at the same time stamp from scoring. So it seems there is no difference with setting ignore = 0 or 1. 3) if it is of any use, I can test if "dummy chordId dummy chords" with no single notes superimposed can be appear in-game without having to be played. Not sure if there's any use for that. 4) probably the only status of use for "dummy chordId dummy chords" is the "accent"status in the <chordTime> tag. Questions for @chlipouni: 1)"For specific usages in which there are no chord and only one note at the same time position, I can add this easily in DDC." Why do you specify "one note" instead of "one or more notes" 2) " these handShapes will appear in the game" I guess you mean in a difficulty where a single note is slated to appear that corresponds to a dummy chord box you will make sure the "handshape chordId =-1 dummy chord" appears in game? If so, I thought instead the dummy chordbox would appear in a difficulty level where at least two single notes appearing to be a chord or partial chord would appear in game. I probably misunderstood you here. Sorry, you know your DDC and I don't mean to question other than to help in case you were wanting feedback from us. No need to respond if you weren't needing feedback.

I suppose we'll scrap the -1 chord ID idea for now then. I guess the benefit to dummy chords is that it offers some possibilities like authoring a chord/handshape with no fingering or a single note that has a chord box? I'm a bit OCD so I had to continue the testing just a little to confirm a couple of things: 1. Those chordID=-1 dummy chords can have single notes superimposed upon them at the exact same time stamp. See below. http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/Handshape%20with%20-1%20chordid/Handshape%20-1%20Test%20Results%20-%20Example%202_zpse7qaocvr.png 2. To avoid the scoring problem (aka How-do-you-play-what-you-cannot-see) in-game I tried making a handshape with no notes (or equivalently, with ghost chords on the handshape, as shown in the picture below). It turns out that the chordID=-1 dummy chord box won't show up unless a real chord (or presumably a single note) is authored in the handshape at that same time stamp. So just the XML manually added single notes show up. http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/Handshape%20with%20-1%20chordid/Handshape%20-1%20Test%20Results%20-%20Example%203_zpsom6hqxnf.png So as long as the intended single notes (identical to the authored but vanished chordnotes) are superimposed over the chordId=-1 dummy chord, then this mechanism is viable, but then it causes problems with DDC so it seems unworthwhile to continue with this. So I'd like to make a distinction here before with decide to do without such as thing as 'dummy chordboxes'. There are two types of dummy chordboxes: "Handshape chordId=-1 Dummy Chords" which is what is shown in the 1st image at the top of this post."Dummy Chords associated with a Dummy Chord Template" (for short I will just call this one "Dummy Chords")The latter dummy chord, which has been the subject of very extensive testing in another thread (I link to a summary post, after which, extensive testing began) works by associating a <chordtime> tag containing no <chordnotes> with a dummy <chordTemplate> tag containing only blank names and -1's for fingerings and frets. (See code below the following image)It is currently only doable by tweaking the XML manually with the code shown in the image below.In fact is has reliably proven to be the *only known way* to author the sequence shown below of a chord played and followed with a HOPO on one of it's strings.The LinkNext Tech note splits up the chord into single notes as well as it's typical duty of removing the subsequent note head. Admittedly I wish I could find a way for this dummy chord to look like |_| as does the "Handshape chordid=-1 dummy chord". But it's not a deal-breaker in my opinion. http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Example%202k_zpsbsnxfaij.png Code that generates the dummy chordbox in the picture above: <chordTemplate displayName="" chordName="" fret0="-1" fret1="-1" fret2="-1" fret3="-1" fret4="-1" fret5="-1" finger0="-1" finger1="-1" finger2="-1" finger3="-1" finger4="-1" finger5="-1" /> ... <chord time="82.983" linkNext="0" accent="0" chordId="34" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down"/> I hope I am not being too pushy. If you guys don't want this then that's a legitimate choice I'll respect. But HOPO's on select strings of a chord has no way to be authored without this and it sounds pretty cool on the guitar (listen to Blaze intro in my sig for an example). I thought it might be good to summarize all this here since we are talking about discarding the idea of "Handshape chordId=-1 Dummy Chords" while "Dummy Chords associated with a Dummy Chord Template" are still a worthwhile consideration.

Hi guys, Test Results! Sexy dummy chord box, no fingering, no chord name. All as predicted by raynebc! http://i.imgur.com/B3PH1DG.png What I meant to say in the image is that the dummy chord will only register if I play the A5 power chord. No other power chord or note will score in-game. So we must put the right notes of E5/A7 in that box. I ran out of time. Hopefully tonight I can perform the follow-up example of manually adding note tags at the same time stamp as the dummy chord and then the dummy chord mechanism would work. Note that I unpacked every single on of my 200+ ODLC and the On-desk songs and after sifting through over 1900 XML's I have found no hits for the search string----> chordId="-1"

My pleasure. Yes. In fact I was planning to do this tomorrow morning. @@Chlipouni, can you provide the name of the Official song that uses the concept so I know what to mimic exactly.

Your first image Plum is something I don't seem to understand what is being shown on screen or have ever seen, though it looks cool and flashy .... :) I too do not understand what you are pointing out. So below I resume crash testing from my previous post 1462. Seems like everything is fine after all and the crashing was sopme sort of unexplained anomaly... Zoomable Link http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/High%20density/Hotfix%2001-16-2016%20-%20Determining%20cause%20of%20crashing_zpsbzqdxbnu.png

Sorry @@eezstreet, I just now remembered to add links to your contributions to the OP. It's done now. Thanks!!

It's possible that in some circumstances the game or the toolkit doesn't like high density chords? If you make those two high density chords normal, does it stop crashing? http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/High%20density/Testing%20No%20More%20Lies%20chorus%20with%20Hi%20Dens_zpsgrovxgb2.png Hmm you seemed to have predicted that, raynebc. :) I wonder what is going on. Have I corrupted something by authoring the above yesterday... take a look below for my follow-up tests as you suggested: I ran sequence 1 alone without any "high dens" on the 6th A5 power chord --> CRASHI ran sequence 2 alone without any "high dens" on the 6th A5 power chord --> CRASHI ran sequence 2 alone without any "high dens" on the 6th A5 power chord & just authored 1 G0 note randomly (thinking I had deleted all notes except the G0 note but having accidentally maintained the sequence 2, albeit sequence 2 authored at the 4s time stamp instead of 2 sec like in the picture above) --> NO CRASH! --> Perhaps crazy status + "Hi dens" status is a bad mix ...I ambitiously therefore retried running sequences 1 and 2, without any "high dens" on the 6th A5 power chord, with sequence 2 occurring at 4 sec and sequence 2 occurring, now at 6 sec --> CRASHI kept the two sequences without any "high dens" as in the previous bullet but removed the Crazy status from the 6th power chord --> CRASH ---> WTFI tried starting a new project in a new directory, and building up to the error by simply authoring 2 sequences of 5+5 A5 power chords, so essentially what you see in the image above but without any "hi-dens status or Crazy status or Handshape marking --> CRASH ---> WTF^2Erased all notes and authored a simple G0 sustained notes at 2sec mark lasting 2 second --> CRASH --> WorrisomeOK .... let's see if I can play my long ago authored CDLC No More Lies which basically contains Sequence 1 above but without the "HI Dens" status --> NO Crash --> Thank goodness!! (It was authored with a very old Hotfix)Tried running the latest Beta version of my Blaze custom authored with Hotfix 01-12-2016 --> --> NO Crash By CRASH, I mean Message that program stopped working and back to Desktop. I even rebooted yesterday before reporting the crash. So anything I author with the latest Hotfix is no longer authoring. Since something has seemingly corrupted should I: Erase and Reinstall the latest HotfixErase and Reinstall the whole EoF programErase and Reinstall the latest toolkitErase and Reinstall Rocksmith 2014I guess I'll start in the above order and probably do so tomorrow morning since I have to go to work soon... Edit: Somehow rebotting EoF and rebooting the RSToolkit allowed me to test the dummy chord boxes to see if manually changing the XML to High Density =1 in the dummy chord tag in the XML would author the desired |_| chord box instead of the square box. Here is what I found. http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Attempt%20at%20creating%20dummy%20half%20box%20-%20Attempt%201_zps0vw4xdvd.png Hopefully rebooting EoF and RSToolkit is all I needed to get the above crashes resolved. TBD tomorrow morning. Edit 2: After testing the dummy chord boxes in the Edit 1 above,, after having rebooted EoF and RSToolkit, I had just enough time to retry testing 10 chord sequence of A5 power chords with a bit of time between chords 5 and 6, (no hi dens statuses, no Crazy chords, no handshape marking) --> NO CRASH (contrary to the 4th last bullet above) I will proceed tomorrow adding 1 item at a time so as to return to the first image in the top of this post, the last one being crazy+hi-dens on chord 6. Hopefully we'll conclude then what's breaking the game.

Sorry, took a while to comment, but here goes, I don't mind changing this back, but in the interest of not overlooking anything, does anybody have any arguments against this? As long as the author has the feedback in the 3D pane to be alerted that he should set the chord to "hi-dens" when it is identical but different chordid, chlipouni's logic sounds fine. Like chlipouni, I initially didn't like the idea of a handshape's base chord showing up as a repeat line (high density) but then I remembered an instance where it would actually be warranted. In my custom, No More Lies, by Iron Maiden, the chorus portion shown below used crazy status on the 6th of 10 chord boxes to simulate a silence between the first 5 A5's and then next 5 A5 power chords. Now, with handshapes, I'd create a handshape for the first 5 and another for the last 5 and I would put a "high dens" status on the 6th chord to remove the gems inside it, which I couldn't remove below at the time. This would give the player that cue for a silence (in the case of this custom, a dramatic one) after the 5th chord instead of a "let ring" cue if it were one long handshape. And then the player quite obviously would resume the same chord for the next 5 chords all showing, nice and cleanly as repeat lines. However, apart from using the "high dens" for the purposes of authoring a silence between two handshapes, I see no other reason why an author should start a handshape with a repeat line. Perhaps firekorn is right that it's a concern only for people "nose-deep into EoF" and we likely won't see a bunch of new authors rendering their charts indecipherable with over-liberal use of high-dens... Either way is fine. ... I could live with my chorus 6th chords being a full chord box... LOL Unless we can avoid handshapes altogether and auhor as I did in the past with Crazy status on the 6th chord but then overrule that 6th chord with high dens status to eliminate the gems inside the 6th chordbox. Then I think handshapes could forcibly always start with a full chord box. (You can ignore the red text in the image below since the image was from Post #1382 when PC Plum wanted to see examples of High Density.) http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/High%20density/Highdensity%20insight%202_zpsk59knezy.png Edit: FYI, I tried testing some of these ideas but both currently crash the game.... despite the XML seeming logical enough....even when I author each deqeunce of 10 chords individually..... go figure... http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/High%20density/Testing%20No%20More%20Lies%20chorus%20with%20Hi%20Dens_zpsgrovxgb2.png Hmm, I wish we could avoid repeating chord names to keep charts elegant since this makes it harder to detect and time the strumming for changes in quick chord sequences on a busy screen. Ex: GGGGAGGGG ---> G---AG--- is cleaner But I see the importance of harmonizing our tools and it does seem to be "either/or" as raynebc said. Maybe it is a silly idea but maybe we could have our cake and eat it too by putting a "split" status on all chords in the handshape for whom we don't want to see repeat chord labels, and then add a "dummy chord box" around those notes per the discussion in this thread. However the dummy chord boxes I've been able to create are big square ones instead of the more elegant half boxes that seem more common as shown in Post 1450. Would love to know how to create dummies of those half chord boxes. So if this silly idea were to be used, the whole high density issue would be gone and the DDC issue would disappear, presumably. I understand this is laying it on a bit thick and should probably be dismissed as an idea but I wanted to offer food for thought. So, if for purposes of harmonization with DDC, the chord labels repeat on the side of the highway due to having only one instead of multiple chord templates in the handshape, one would still be able to remove all those repeat chord labels by selecting all but the first (base) chord and doing Note > Edit Name and setting it blank (1 space character)? I thought that very action in EoF would author a whole new chord-id? Thanks for all the hard work chlipouni and raynebc!!

Shouldn't behave like this if sections are defined in EoF. Rereading chlipouni's web site it seems the only way what you describe can happen is if your friend authored no sections in EoF and each measure is populated with notes (no empty measures apart from beginning and end), then chlipouni's web site implies that only one section will exist for the whole song. If I understood correctly then the solution to your friends problem is simply authoring sections in EoF and then using DDC again. I thought you meant you wanted DD on only part of the song, which currently would only work if you create DD for the whole song and then open the XML and remove all those things you don't desire but that would require meticulous effort and for you friend to understand XML really well to know what he should and shouldn't erase.

Well if we cannot go beyond 12 semi-tones for tuning, then maybe a combination of yours and RockZot's ideas would be combined for some degree of success: Multiplayer + mutiple strings used for 1 octave. I guess you're point 4 is similar to what I am about to say. If we want 6 octaves then it is 2 strings per octave (since we're assuming 12 strings total due to multiplayer). That means if RS cannot accomodate multiple simultaneous notes on one string then since a chord is a triad of notes we'd need 3 octaves per string. So Player 1 (bass clef) gets 2 octaves, Octaves 2 and 3 and Player 2 gets octaves 4 and 5. Then when a chord comes along such as C4-E4-G4 (C Major) it will span the red-yellow-blue strings with the C4 being on the red string, E4 being on the yellow string and the G4 being on the blue string, all neatly placed in a nice Rocksmith chord box to hammer home visiually the the notes are simultaneous. Perhaps, Player 1 can play with a multiple/fraction of the 440Hz frequency to get the tuning within +/- 12. Low E string --> -28 -3 = -31 --> Change frequency to reduce the magnitude of this number A string --> -20 -3 = -23 --> Ditto D string --> -14 -3 = -17 --> Ditto Player 2 can play with A440 since those tunings are within +/-12 semi tones G string --> -7 -3 = -10 B string --> +1 -3 = -2 High e string --> -8 -3 = -+5 I'm still curious if I mod an XML manually if the Toolkit and the game will allow simultaneous mutliple notes on a string..... probably not. I guess I'm curious how you confirmed that the Real Tone Cable goes from B0 to E6 :) Perhaps I'll test in out in the the coming months if nobody has done it yet. Looking forward to trying Hallelujah on violin.... I think you said she's on violin.... I agree that it is probably just simpler to defer to another software. I must admit Sythesia is pretty cool and that video compels me more than ever to try it, especially at $30, but I have to admit that though their design is elegant I find it to crowded to try to capture the entire keyboard. That's why I am excited to get it to work in RS since we could divide into Octaves requiring 12 frets. Probably you are are correct that it would be shoe-horned and not elegant, but I would still enjoy see what we could do, especially since many fun pieces don't span more than 4 octaves. For now I have to go back to my Blaze custom.... it's already taken me too long to complete. :)

So to my wife's delight I was eating supper at Pizza Hut with her and I was a conversational delight while envisioning in my head how Painosmith would operate. :) Here are a few thoughts regarding how we can try to go about using the piano in Rocksmith 2014. So given @@firekorn and @@RockZot there seems to be 3 interesting possibilities: 1. RockZot's clever idea of having the bass clef as one player and the treble clef as a 2nd player and then the microphone detecting both piano clefs being played by the player. 2. firekorn's idea of defining the two thickest strings as the bass clef and the two top strings as the treble clef 3. I wondered if we might as well not even consider getting the majority of the piano's 88-keys by using all six guitar strings in game as follows: e string, 3rd fret = C6 (C note of 6th concert pitch octave) ...... B6 (15th fret) B string, 3rd fret = C5 (C note of 6th concert pitch octave) ...... B5 (15th fret) G string, 3rd fret = C4 (C note of 6th concert pitch octave) ...... B4 (15th fret) D string, 3rd fret = C3 (C note of 6th concert pitch octave) ...... B3 (15th fret) A string, 3rd fret = C2 (C note of 6th concert pitch octave) ...... B2 (15th fret) E string, 3rd fret = C1 (C note of 6th concert pitch octave) ...... B1 (15th fret) We wouldn't used frets 0 to 2 since, those are custom inlay dead zones according to cozy1 upon which the inlay will not be able to show piano keys. Also we wouldn't need frets 15 and above since each octave (in western music) contains 12 notes in the chromatic scale (C, C#, D, D#, E, F, F#, G, G#, A, A#, B ) I used one of the template inlays to create this inlay: http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Pianosmith/Piano%20Inlay%201%20octave%20per%20guitar%20string_zpsn5wis4bk.png Sadly, in-game it doesn't align in my 1st attempt but I'll post the image anyway so you get the idea of what I'm envisioning: http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Pianosmith/In-game%201st%20iteration%20of%20a%20piano%20inlay_zpsujfzpz0w.png Yes I'd have to optimize the transparency of the keys so that we could see the notes properly just before they cross the strings. As firekorn said, using a funky but appropriate tuning we could define each string such that the 3rd fret is the C note of the octave being represted on that string. GUITAR and BASS GUITAR are what are known as OCTAVE TRANSPOSING INSTRUMENTS. This means that the written note is an octave below the note that they sound. Example: To play middle C (C4) on a guitar play 1st fret of the B string. When reading piano, the C4 appears on the first ledger line below the staff. On guitar the 1st ledger line below the staff is C3. So to play guitar with piano music sheets requires to play guitar an octave above what the piano music sheet says to play. Here is my special tuning math, please verify my calculations: So let me do this in steps to get to the final tuning in EoF. Step 1: Tuning if Guitar were not an octave transposing instrument & assuming piano C notes are played at guitar fret 0 (open string) So E Standard Guitar Tuning is: E2-A2-D3-G3-B3-E4 Therefore, E2 to C1 =-16 (red string in Rocksmith) A2 to C2 = - 8 (yellow string in Rocksmith) D3 to C3 = -2 (blue string in Rocksmith) G3 to C4 = +5 (orange string in Rocksmith) B3 to C5 = +13 (green string in Rocksmith) E4 to C6 = +20 (purple string in Rocksmith) Step 2: Tuning if Guitar is transposed to concert pitch (piano notation), yet still assuming piano C notes are played at guitar fret 0 Consider from the above example that Guitar C4 to piano C4 = -12 semi-tones (aka half-steps), then: Guitar E2 to piano C1 =-16 -12= -28 (amount of semi-tones between E3 and C1) Guitar A2 to piano C2 = - 8-12= -20 (amount of semi-tones between A3 and C2) Guitar D3 to pianoC3 = -2-12= -14 (amount of semi-tones between D4 and C3) Guitar G3 to piano C4 = +5-12 = -7 (amount of semi-tones between G4 and C4) Guitar B3 to piano C5 = +13-12 = +1 (amount of semi-tones between B4 and C5) Guitar E4 to piano C6 = +20-12 = +8 (amount of semi-tones between E5 and C6) Step 3: Tuning if Guitar is transposed to concert pitch (piano notation) & Piano C notes are played at fret 3 Consider that for the 3rd fret to be considered an 0th fret due to the inlay deadzones in frets 1 and 2, we'd need to reduce the tuning from step 2 by 3 semi-tones. Therefore the final tuning that would render the 3rd fret to have a C note, from each respective octave on each Rocksmith string would require the following tuning: Low E string --> -28 -3 = -31 A string --> -20 -3 = -23 D string --> -14 -3 = -17 G string --> -7 -3 = -10 B string --> +1 -3 = -2 High e string --> -8 -3 = -+5 Issues to overcome: Will Rocksmith allow tunings so many semi-tones away from the standard? Core frequency in the Rocksmith toolkit for piano as described here is A440, right? Probably, since tuning above is relative to guitar tuning. However if RS doesn't like the big numbers, perhaps halving (not doubling is it?) the frequency to A220 will fall within a tuning RS will accept. FHP = 3 and Width =12 in order to keep in-game camera in a fixed place. Will Rocksmith (and EoF, and the Toolkit) allow multiple notes on one string in order to simulate piano chords. Example C Major being C4-E4-G4, in the case of the chord being played in the 4th octave. If it won't accept multiple simultaneous notes on the same string, then we'd be limited with only single note piano pieces, which is far less attractive. For a given Real Tone Cable gain, will a microphone transmit all octaves equally well to the game?What do you guys think? I can't really take the time in the next few months to develop this but if no one does it, I may try to make it work in the future at some time. Honestly, if anyone wants to develop on these ideas, I'd be more than happy to see it developed since I would take forever to get this off the ground and operational.

Hi @@Chlipouni I tried authoring your sequence above out of curiosity and it looks like this in-game: http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/High%20density/Chlipouni%20Example%20of%20Crrossing%20Slides_zpslyayhd4i.png When I authored it, it forced me to specify the end fret of the pitched slide to the lower fretted string of the two simultaneous notes, so as you did, I set it to 2 based on the D-String end fret of 2, so EoF authored it in the XML such that both notes slide to fret 2 as can be seen in the XML, hence the crossing of the note tails in the game. It works fine without the split status, because EoF recognizes that the slide of the lowest fret by 1 fret is to be applied in relative terms for the higher fretted string chordnote as well, but that logic is either not yet available for EoF or maybe impossible, which i guess raynebc will confirm. If there is no easy fix in EoF, I got your desired look to work with a tech note on the A-string note tail as shown below. Admittedly I didn't get the handshape lane highlights to follow with the FHP to transition nicely. I look forward to seeing how you manage the FHP in your custom. What is the name of your custom so I can inspect when it comes out. http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/High%20density/Chlipouni%20Example%20of%20Crrossing%20Slides%20fixed%20with%20Tech%20Note_zps0puephl5.png Quick question: I noticed two different red piano roll symbols for Palm Mutes, as authored in your example in the above post chlipouni, "-" resulting from Edit Pro Guitar Note > Muting > Palm selected "PM" resulting from CTL+M Is there any difference making you select one over the other...

Still interested in this of course. Just busy with other stuff. I know we're a small subset of the community but I hope we'll see more customs. I even wanted to create a guitar inlay of a piano with each fret getting 1 key, so basically you only get two octaves in-game but it is probably good enough for some pieces. 1octave for the left hand and one for the right hand , or two for the right hand.

I still have to read the last half dozen posts here since I just got home from work, but the new Hotfix works like a charm! Here are multiple authorings all in one handshape. http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/High%20density/Test-Hotfix01-14-2016-Split_and_High%20Dens_zpslhiinijr.png

Hi guys, So I finally fell upon this thread that discusses chlipouni's new findings.... Silly me, I should check this section of the site more often. I read this thread but need to read it again to make sure I understand all the details. A couple of early questions come to mind: 1. @@Chlipouni, you went a slightly different direction than I thought you might have. I thought you were going to say the fingerings were taken care of by the "embedded handshapes", so that individual chords in the main hand-shape would show their unique fingerings instead of the fingering of the first chord in the main handshape. Would you know if it works when the "embedded handshapes" get the fingering assignments instead of the "main handshapes"? I guess I'll have to re-read the thread to better understand the need for the embedded handshapes as you propose, as it currently seems to me that the main handshape does all the "work". 2. Heart Shaped Box being an on-disk song, I am wondering where that psarc file is located so I can look inside too. It's not in the DLC folder, so where is it? 3. What does "-nop" stand for in the chord templates? Does it act any differently than setting that to nothing ( "") Thanks for your patience with my questions. This is all quite impressive work you did!!

Thanks for the new Hotfix! So I tested it and it works as expected now. Very cool indeed! So my understanding is that this new feature discovered by @@Chlipouni would also allow displaying various different chords within a handshape, not unlike the Ghost Handshapes concept inspired by @@SmellsLikeMonkey. In fact it seems like it can/will replace the concept of Ghost Handshape. So I decided to try it out. I have a couple of questions. Though I think it is all expected behaviour but I just wanted to make sure. Zoomable Link http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/High%20density/Hotfix%2001-12-2016%20Examples_zpsfaqonqua.png

Hi raynebc, I tested your new "Hi-Dens" status. Here are my findings: If you recall Post 1387 at the time of Hotfix 12-24-2015, where I responded to chlipouni about high density inside a hand shape and came up with this example. There was a little bit of an unexpected behaviour that now has a greater impact with your New Hotfix 01-09-2016. I am using the version of the toolkit b942ce6e released January 9, 2016 to pack the psarc that created the in-game images. You mentionned "pending this new capability from the Rocksmith Toolkit." in your Hotfix notes. I thought Toolkit b3e91eeb completed the implementation but is this feature still in progress? Zoomable Link http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/High%20density/Testing%20Hotfix%2001-09-2016_zpsoicfguqm.png Yup, I like this. :) So controlling the density, controlling the split up of chords into single notes and the ability to add a chord box at will and it seems like all possibilities are covered. Am I wrong? Question: Regarding your comment " unofficial "N 5 #" notation is applied to a note, that note's forced HOPO notation is inverted." what is "N 5 #". Sorry there will always be some noob in me... :) Yes I'm awake at 5am. I realized something. Why give the best hours of my day to my boss when I could give them to myself, RS, and the community. So I go to bed at 9pm, like my son, then wake up at 5am and do RS related stuff till 6:30am, then wake up my son and prepare for work. LOL.... Let's see how long this lasts. Headbanging at 5am is probably not what Gene Simmons meant by "Rock'n'Roll All Night".... :)

Thought I would try Rhythm for a change. For someone who thinks he wants to play lead guitar I sure have a lot of fun playing rhythm. Even when it gets repetitive, you get into a trance-like groove, almost like when you are approaching drunkenness..... Love that feeling! http://i920.photobucket.com/albums/ad41/Berneer/CustomsForge%20Championship/Week%20115%20-%20Ending%2009January2015/CF%20-%20Week%20115%20-%20Iron%20Maiden%20-%20Alexander%20The%20Great%20-%20Rhythm%20-%20Attempt%201_zpsxniaieqf.png

This is a very cool discovery. Nice job chlipouni!!! Question for @@raynebc or @@Chlipouni : So now the XML chord-density tag will not be over-ruled by something such as a handshape. But I suppose there is or will be a way soon in EoF to specify the chord density specifically? So cool!!!

Thanks for the info raynebc! I notice @@Chlipouni 's github issue 248 was closed yesterday via the latest daily commit to the toolkit. Any ideas how to use thIs new toolkit feature or how to use EoF to take advantage of it?

How exciting when the slightest amount of progress is made when playing one of your favorite songs from your favorite band. Monday morning after slamming my alarm shut with both fists I will have thoughts of playing this song at night to keep me sane. Strange that without DD my yellow score would go up to 84%..... anyway I know it's not the one that counts. http://i920.photobucket.com/albums/ad41/Berneer/CustomsForge%20Championship/Week%20115%20-%20Ending%2009January2015/CF%20-%20Week%20115%20-%20Iron%20Maiden%20-%20Alexander%20The%20Great%20-%20Lead%20-%20Attempt%202_zpsptbmw2a7.png

1. This sounds very promising from chlipouni.It does sound however that it is meant for chords, which is the thing my test above showed needs to be deleted in order to remove the lingering B12 sustain problem. But I guess we'll see what happens after chlipouni's and Toolkit devs finish working on it. 2. I've ammended the Random test to start the handshape at the HO B13/e0 time stamp instead of the beggining of the sequence and the lingering sustain problem returns. As the remarks in the image state now we know the two things that triggering the lingering sustain problem and luckily we also know what it takes to eliminate the problem. http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Example%202%20-%20Random%20Test%202%20Handshape%20marking%20starts%20at%20HO_zpslguu43ew.png I'll stay tuned with whatever new toolkit/EoF changes occur and once I finish my Blaze custom I'll make sure not to forget to update the Tech Notes tutorial accordingly, at which time, though I'll comb through the forums, I'll ask you @@raynebc, if anything sticks out in your mind in terms of changes you made to EoF since March 2014, that would require me to update the Tech Notes Tutorial..... all in good time :)

I must take time off from authoring to play this. As usual my first score is always cold with no practice. Which sadly is about 5% less than my best so far.... Freebird or Lostbird I think Lostbird is more accurate. But nonetheless, maturity means you are not afraid to display your ineptness to the world so here goes.... http://i920.photobucket.com/albums/ad41/Berneer/CustomsForge%20Championship/Week%20115%20-%20Ending%2009January2015/CF%20-%20Week%20115%20-%20Iron%20Maiden%20-%20Alexander%20The%20Great%20-%20Lead%20-%20Attempt%201_zpszgeaa5dm.png @@MaZtoR, everytime I see your avatar, it is tiny enough that there is a great resemblance and I always think I am reading a post from Gannichus from Spartacus (one of the main super protagonists). I love that show!

WE'RE ALMOST THERE! So here are some conclusions I have drawn from looking at the Example 2 codes of the images from the previous post. Example 3 and Example mrmaton behave like Example 2 and Example 4 is not the driver here so I haven't looked at it's code yet. So I figured that for Example 2 (the Tenacious D example) the way forward lies in comparing the desired reference case - Example 2k from Post 55 with what EoF Hotfix 12-31-2015 is exporting into the XML today. Here is what EoF Hotfix 12-31-2015 exports: (repeat of 1st case from previous post) http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Example%202%20-%20Crazy%20status%20and%20Handshape_zps6rto5u81.png <chordTemplate chordName=" " displayName=" " finger0="-1" finger1="-1" finger2="-1" finger3="-1" finger4="2" finger5="-1" fret0="-1" fret1="-1" fret2="-1" fret3="-1" fret4="12" fret5="0"/> ... <note time="2.000" linkNext="0" accent="0" bend="0" fret="12" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="4" sustain="0.500" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="2.000" linkNext="0" accent="0" bend="0" fret="0" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="5" sustain="1.997" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="2.500" linkNext="0" accent="0" bend="0" fret="13" hammerOn="1" harmonic="0" hopo="1" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="4" sustain="0.500" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="3.000" linkNext="0" accent="0" bend="0" fret="12" hammerOn="0" harmonic="0" hopo="1" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="1" slap="-1" slideTo="-1" string="4" sustain="0.500" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="3.500" linkNext="0" accent="0" bend="0" fret="10" hammerOn="0" harmonic="0" hopo="1" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="1" slap="-1" slideTo="-1" string="4" sustain="0.497" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> ... <chord time="2.000" linkNext="0" accent="0" chordId="0" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down"> <chordNote time="2.000" linkNext="0" accent="0" bend="0" fret="12" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="4" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chordNote time="2.000" linkNext="0" accent="0" bend="0" fret="0" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="5" sustain="1.997" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> </chord> ... <handShape chordId="0" endTime="4.001" startTime="2.000"/> Example 2k - Reference Case obtained from tweaking XML as described atop the following image http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Example%202k_zpsbsnxfaij.png ! Dummy chord template --> frets and fingers all set to -1 <chordTemplate displayName="" chordName="" fret0="-1" fret1="-1" fret2="-1" fret3="-1" fret4="-1" fret5="-1" finger0="-1" finger1="-1" finger2="-1" finger3="-1" finger4="-1" finger5="-1" /> ... ! Removed last 3 e0 notes, set linkNext=0 on the remaing e0 and made sustain attritube of first e0 note last duration of entire phrase <note time="82.983" linkNext="0" accent="0" bend="0" fret="12" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="4" sustain="0.471" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0" /> <note time="82.983" linkNext="0" accent="0" bend="0" fret="0" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="5" sustain="1.866" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0" /> <note time="83.454" linkNext="0" accent="0" bend="0" fret="13" hammerOn="1" harmonic="0" hopo="1" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="4" sustain="0.47" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0" /> <note time="83.924" linkNext="0" accent="0" bend="0" fret="12" hammerOn="0" harmonic="0" hopo="1" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="1" slap="-1" slideTo="-1" string="4" sustain="0.471" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0" /> <note time="84.395" linkNext="0" accent="0" bend="0" fret="10" hammerOn="0" harmonic="0" hopo="1" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="1" slap="-1" slideTo="-1" string="4" sustain="0.454" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0" /> ... !Dummy chord, notes wiped out by its chord template <chord time="82.983" linkNext="0" accent="0" chordId="34" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down"> <chordNote time="82.983" linkNext="0" accent="0" bend="0" fret="12" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="4" sustain="0" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0" /> <chordNote time="82.983" linkNext="0" accent="0" bend="0" fret="0" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="5" sustain="0" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0" /> </chord> ... <handShape chordId="32" endTime="84.853" startTime="82.983" />So the last two hotfixes have brought us far along onto the road to success by replacing the manual tweaking of the XML of removing single notes, with the new EoF combining logic using linknext tech notes. Now the difference between the two XML's is that for the identical authoring in EoF as seen in the images above, the Hotfix 12-31-2015 exported a chord in the XML which I didn't when making Example 2k, namely: <chord time="2.000" linkNext="0" accent="0" chordId="0" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down"> <chordNote time="2.000" linkNext="0" accent="0" bend="0" fret="12" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="4" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chordNote time="2.000" linkNext="0" accent="0" bend="0" fret="0" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="5" sustain="1.997" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> </chord> When I manually remove this above chord from the XML but keeping everything else EoF authored, it looked like this in-game: TADAA! the lingering B12 sustain issue sustaining beyond the B13 HO all the way till the end of the sequence NOW DISAPPEARS!! It seems what I was on about in Post 66's 1st paragraph came into play: a chord with differing sustains for each note seems to be interpreted by Rocksmith 2014 as giving the same longer (?) sustain to both chord notes of the chord. Anyway here is what it looks like after removing the chord: http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Example%202%20-%20Hotfix%2012-31-2015%20testing%20-%20CrazyHandshape_CHORD%20REMOVED_zpsqublqbt7.png Now if we could add that dummy chordbox directly using EoF then it looks exactly like the desired Example 2k. Note I removed the chord only and not thecorresponding chord template from the Hotfix 12-31-2015 authored XML since the handshape tag references the same chord template as the now deleted chord did (chordid = 0). It would seem the we need to ask ourselves a few questions: 1. Do we really need single note and chord note overlapping when a chord is set to crazy in a handshape? Problem is that it is the chordnote I'd want to remove, as I did above, but that seems to go against prevailing "full chordbox at start of handshape logic". Currently the overlapping single and chordnotes making that rotating cross shaped notehead is an outcome of the overlapping chord note and single note. 2. Is there a way to author this in EoF? I don't know Allegro or the EoF coding but would the current full chordbox logic at the beginning of a handshape be circumventable by a 2 step process: 1) creating a status on the initial B12/e0 chord, in handshape marking, called, say, "Delete Chord" & 2) creating a status on the initial B12/e0 chord called, say, "Dummy Chord box". Just an idea... I guess I'll stop here and wait to hear comments. Oh, actually I wanted to share a random test I did on Example 2 which offers some insight. http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Example%202%20-%20Hotfix%2012-31-2015%20testing%20-%20Random%20Test%20of%20CrazyHandshape%20with%201%20Linknext%20Tech%20Note%20missing_zpsgqh8gbne.png

Hi, Just to be thorough, I've tested each of examples 2 to 4 with the following method though probably once I have time to make for some conclusions it'll make a more compelling read: a) All crazy + handshape b ) No crazy + handshape c) All crazy + No handshape d) No crazy + no handshape I've run out of time and I will explore the the XML codes more closely tonight or tomorrow to see if I can find any explanation for unexpected behaviour. For now I thought I'd share the in-game screenshots I'm looking. Too much to paste all the code here so I link the XML and notes.eof used for my testing. Note I have not tweaked the XML at all. XML NOTES.EOF Example 2 - Tenacious D - The Metal (example from Firekorn of an ODLC) Zoomable Link http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Example%202%20-%20Hotfix%2012-31-2015%20testing_zpsmuknhufa.png Example 3 - Blaze - Stare At The Sun (2 string simplification since akin to Mr. Maton example) Zoomable Link http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Example%203%20-%20Hotfix%2012-31-2015%20testing_zpsw6rmm8gs.png Example 4 - Blaze - Stare At The Sun (full authoring on 3 strings) Zoomable Link http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Example%204%20-%20Hotfix%2012-31-2015%20testing_zpsrinaexdw.png Example mrmaton http://i920.photobucket.com/albums/ad41/Berneer/CustomsForgeStuff/Questions%20for%20CF/HOPOonSomeStringsOfChord-GitHubIssue153/Example%20mrmaton%20-%20Hotfix%2012-31-2015%20testing_zpsjg2bnjsc.png Conclusions Later.