Bentron

ok great ! I understant all of that before :P Just thought there was something more :P

(I know how to read tab :P )

Haha, sorry :lol:   I figured you knew how to read tab, but I wasn't sure what part you didn't understand from my earlier post, so I just decided to cover all the bases ;)  But no, that was all for me.  Other than the different playing position and that one spot with a missing note, I didn't notice anything else out of place.

@@Shiroo The stuff in code blocks is just tab notation, read basically the same way as EOF represents notes but with less granular timing and no representation of note length.  The lines from bottom to top are the EADG strings, and the numbers on the lines are the frets the notes should be played on, on that string.  The vertical lines are just measure dividers for readability.

I just used section number because I was lazy and didn't bother loading the xml into EOF, but "Section 3" starts about 00:14 in the audio, and it looks like is "verse 1" in EOF.  "Section 12" starts about 00:52, and EOF is calling it "verse 5", if that helps you find it.

As for the changes, what I'm doing is shifting position to where my index is on the 4th fret.  From there, anything that was A9 or E9 originally, I play as D4 or A4 respectively.  There are also the two notes that were originally D8, which I just stretch up and play as G3.  Same notes, just different positions on the fretboard.

Hopefully that clears it up?  If i had the project files I could make the changes and send the new xml over to you, but without them, I'm not sure if what EOF will spit out (without going through all the beatmap, hand position, and other setup stuff) will even be useful.  I also would have to make changes across all the difficulty levels without the original files, which I'd probably screw up :)

And today's progress.  Just three notes short...  And the bit at the end is still pretty sloppy, even if the game gives me a pass on it.

http://i.imgur.com/iQqNQO6.jpg

next is underwear

...

bass dl 5

tab 8, verses are slightly different, also another position maybe could be an improvement. Some parts are missing tiny fills.

tones 9

...

Agreed on the position and some missing notes.  I copied down how I've been playing it if anyone wants to try it or tweak the custom to match.

Numbers in square brackets are the RR sections.  The sections below are played from the 4th fret, everything else in the song I play as written (I think).  I found the stretch up to 3rd fret in bar 1 of section 6 to be more comfortable than shifting around (as written originally) or a stretch down to the 8th fret, but maybe others prefer the original.

If you do go with what's below, it's tempting to play sections 15-17 from the 4th fret like earlier in the song, but you need to shift to hit the Eb Db (8th and 6th fret) on the G string at the end of section 17 anyway, and the start of section 15 felt like a sensible place to do it.  I still forget sometimes though if I'm zoning out.

  [3 & 10]                          [4 & 11]
G|----------------|----------------|----------------|----------------|
D|----------------|44--------------|----------------|44--------------|
A|--------44------|--------66------|--------44------|--------66------|
E|66--------------|----------------|66--------------|----------------|

  [5 & 12]                          [6 & 13]
G|----------------|----------------|33--------------|----------------|
D|----------------|44---464------46|----------------|----------------|
A|------4-44----4-|--------66---6--|------4-44----44|6---------------|
E|66---6-6--------|----------------|-----6-6--------|----------------|

  [7]                          
G|----------------|----------------|----------------|----------------|
D|----------------|----------------|44444444--------|----------------|
A|----------------|----------------|--------66666666|444444446-------|
E|6666666666666666|6666666666666666|----------------|----------------|

  [14]                          
G|----------------|----------------|----------------|
D|----------------|----------------|44444444--------|
A|----------------|----------------|--------66666666|
E|6666666666666666|6666666666666666|----------------|

  [15]                          
G|----------------|----------------|----------------|
D|----------------|----------------|----------------|
A|----------------|----------------|9999999966666666|
E|6666666666666666|6666666666666666|----------------|

As for missing notes, I think sections 5 and 12 should probably be as follows:

  [5 & 12]                          
G|----------------|----------------|
D|----------------|44---464------46|
A|------4-44-----4|--------66---6--|
E|66---6-6------6-|----------------|

There could be other errors in the tab, but that's just the one spot I noticed earlier today.

Did a few runs through learn a song and then some time in RR.  There's nothing particularly hard in isolation, but it's pretty fast.  I still fumble the transition between some sections, and I'm definitely not playing that lick at the end cleanly when at full speed, but I think I'll get there.  Overall probably a little easier than last week's.

http://i.imgur.com/rwXJGb3.jpg

Update to v1.6 for Kuchibashi ni Cherry has been uploaded.  Just fixed a missing note toward the end of the bass track.  Still looking for feedback though.

I could be wrong, but I think alternate tunings that low generally require different strings.  Normal strings that you would use for E Standard just aren't going to have enough tension if you loosen them down to B.  

I only play bass (not sure if guitar strings normally have a wider range for playable tunings), but the one time I ran into a song with I think drop C tuning, it was a nightmare to get the game to recognize the string as in tune at all.  And then it was so loose I couldn't realistically play on it anyway.

This one may be my final score.  It's not quite as high as I'd like, but I'm getting a little tired of the song at this point.  I might  try a few more runs tomorrow before going back to E standard tuning, but this is it for today.

http://i.imgur.com/BhURCWl.jpg

Edit: Just noticed I only have a 532 streak instead of 533, but still 100% accuracy... Does an early/late note break the streak, but not count as a miss for the purpose of accuracy or something?  And wouldn't that have had to been on the first note of the song to still have a 532 streak (which I'm pretty sure didn't happen)?  So weird.

Progress, if a bit frustrating.  I think I was only maybe two missed notes short of 100% on this run.  My focus was already fading for today unfortunately, and I slipped up toward the end.  

http://i.imgur.com/Hfl0EiS.jpg

@@cholerae Not all customs are created with dynamic difficulty levels (the one in your video doesn't have DD).  If they don't have DD, they'll behave like the difficulty is locked at 100% even if it says 0% in Riff Repeater, just like you're experiencing.  

You should be able to use the custom toolkit to add it yourself if you really want DD though.  The subforum for the toolkit is located here with the download link and some guides on how to use it.  The specific tool is called DDC (Dynamic Difficulty Creator).

@albatross213 mentioned some of the riffs up around the 10th fret could be rewritten for ease of play, and I'll second that as well.  I'm fairly sure everything after the intro (maybe even including it) can be played on the first four frets if moved up a string or two, so I've just been transposing those parts on the fly as I work through sections in RR.  It'd probably be easier to just unpack the custom and tweak the arrangement, but I feel like I'm learning something useful doing it the hard way :)

@@missis sumner Thanks, the felt pick sounds interesting for sure.  I'll probably grab one of those and a normal sample pack with various thicknesses to try out.  It'd be nice to at least have the option for songs that really call for the picked sound.  And if I eventually have to replace a set of strings because the nylon got damaged (not the end of the world), then I'll know.

 

Your score depends very much on where your misses are (in terms of your score multiplier) while your % accuracy does not. Any miss sets you back to the last checkpoint (x1, x5, x10, x25, x50), so if you miss a note at x26, you pretty much only lose an x1 on the next several notes, whereas if you miss a note at x49, you lose x24 on the oncoming notes. So it's basically not at all a problem if you miss a note just after a checkpoint, but if you miss one just before it can be a huge deal. Chances are it's this and not that your timing became dramatically worse.

 

Huh, good to know.  I somehow never noticed the checkpoint system.  Usually my scores would correlate mostly with accuracy (or timing if I'm hitting 100% already), so I guess I never paid much attention to how the multiplier worked.  Thanks  :)

This run's probably the best I'm going to get for now (numb/tired fingers).  Oddly, it's not my highest score (only by 10k points or so), but almost double my next best streak and over a percent better on accuracy.  It's hard to tell what exactly it is, but I'm going to assume just bad timing.  I'm still not playing as fast or as cleanly as I'd like, but I'm not sure speed is something I can improve too much more on in the next couple days.

It would be nice if the game had a DDR style breakdown of perfect/good/early/late/missed notes at the end.  It's a bit hard to keep track of them popping up on the edges of the screen while playing.  Would also be nice if RR were as strict about timing as score attack is.

http://i.imgur.com/7IJVIQa.jpg

Small improvement on Arcarsenal after some time in RR.  My shifting is still super sloppy causing some pretty bad intonation (fretless), and I feel like I'm still not playing quite fast enough.  Continues to be a blast to play though.

http://i.imgur.com/BITj38F.jpg

I guess it could be?  I've never had a cable fail on me (standard instrument or the one that comes with the game), so I'm not sure what a bad cable actually sounds like, or if they can just fail due to age.  I would think a bad cable would give you a ton of noise all the time, or give no signal at all.

If you can, it's probably worth it to check your guitar through an amp with a normal cable (to rule out some issue with the guitar's electronics) before spending money on a new rocksmith cable.  But really, from what you described, it sounds like the cable volume is just set too high.  

Also, it's normal for strings adjacent to one you're playing to vibrate a bit.  The ringing you're hearing is probably a harmonic.  You just need to practice muting the strings you're not playing to prevent that.

So here's my best for Moonlight Shadow.  Countless runs missing only 1 or 2 notes (in random places) preceded this, along with much pain and agony, but I just couldn't let it go....

http://i.imgur.com/Fkp9ApL.jpg

Finally hitting 100% was really satisfying, even though I know I'm still sloppy at times.  The sync seemed perfect to me, but I felt the sustains were overly long or unneeded in places.  I know it's sort of personal preference whether chart to sustain as the full note length or what is actually heard in the audio, but there are a few places where I found the overly long sustains made it hard to read.  I also found the bass tone really loud and distracting, but that's probably just me and/or my setup.  Just nit picking a bit, don't mind me.

Overall (ignoring my consistency issues), I found this track much easier than Twist My Arm from last week.  Probably a 4 on difficulty?  Not sure I've got enough experience to accurately rate song difficulty yet though.

I also gave Arcarsenal a shot... Is this track really played without a pick originally?  I guess I'm lucky the game is so forgiving with the timing on fast rhythms.  It definitely didn't feel like I hit over 90% of the notes in this song.  

On a related note, can anyone recommend a pick that won't shred nylon wrapped strings?  Do I even need to worry about it, or will the nylon stand up to basically any amount of picking punishment?  I've actually never used a pick before, but this bass part is quite fun to play (even if I don't usually listen to this kind of music).  And it's probably a skill I should learn at some point anyway.

http://i.imgur.com/PSe0YKP.jpg

You may just need to turn the cable down.  It's unlikely latency or buffer settings are causing your input to be too loud.

There should be a setting in the game itself to turn it down manually (which is the same as turning down the volume on the windows recording device for the cable) , or there's a calibration routine somewhere in the settings that well help you get it set at the right value for good note detection without being too loud.

I've never worked with a tab imported from some other program, so I'm not sure I can give too much useful advice there.  I have seen many people recommend syncing the beatmap before you import a tab/add notes to avoid causing the notes (rather than beats) to be out of sync though.  I've only ever charted from print style sheet/tablature, but I've still always done the beatmap first since it makes placing notes a lot easier.

If by "too slow" you mean like half or quarter speed, it may be that the time signature (and average bpm) between the beatmap you generated from the audio and the imported tab don't match.  At least one of the tutorials @@Rockfirstlast linked further up the thread I think covered how to compensate for that.  If it's less drastically slowed down than that but still more than just out of sync, I'm not sure what the issue might be.

Yep.  It should be pretty intuitive after you play with it a bit, as far as where you need to anchor beats.

@@DeadlyPower I think you need to anchor the beats you manually sync (A key toggles, check under the Beat menu for other options).  

It's been a while since I've tried to sync a beatmap (someone please jump in if I'm misrepresenting how this all works), but I believe the general idea is that it won't ever move anchored beats from that specific  time stamp in the track.  All the beats that aren't anchored are sort of dynamic based on the time signature and tempo I believe.  If you have two anchored beats and you move the later beat around, it will compress or expand the unanchored beats, changing the tempo in that span between the two anchors.

In your case, assuming the breakdown comes before the chorus, and the chorus is already synced properly, if you were to anchor the first beat of the first measure of the chorus, you'd then be able to move beats around in the breakdown section without messing up the chorus sync.

That's odd.  Make sure you're using the default display resolution (640x480 I think) under the same menu.  I noticed that if I increase to 800x600 or 1024x768, and then use x2 zoom option, bad things happen.  I assume it has something to do with the zoomed window's size relative to your desktop resolution, but I'd never looked into it. 

I've run it on a monitor as low resolution as 1680x1050 without it crashing (assuming 640x480 display + x2 zoom).  If your monitor is lower resolution than , you might be stuck.  If I had to guess, It probably needs 960px + whatever window borders and title bar add in vertical pixels to avoid throwing a fit/crashing when you enable x2 zoom.

EOF obviously isn't using modern UI/rendering frameworks, so it tends to behave a bit oddly compared to more recently created programs.  I don't imagine something as messy as overhauling those systems is a particularly high priority either unfortunately.

Is there a way of working with eof on fullscreen it would be awesome to me since i have a 22' screen

The best I've found is  File > Display > x2 Zoom.  Not quite full screen, but large enough to be workable.

I decided to look into DDC today, and it turns out it's not nearly as complicated as I remembered/assumed.  I've uploaded a new version (v1.5), but only for PC, Mac, and Xbox.  I had some issues with DDC and was  hoping someone could explain what's going on.  

When I fed DDC the xml files for the arrangements, it spat them out just fine  The toolkit took them and made the various packages as expected, but once I load it into game (only PC to test with), it causes rocksmith to crash right after tuning.  I thought it might be an issue with the tone (as I'd had similar crashes caused by tones early on with this custom), but I didn't touch anything other than running the arrangements through DDC.  Recompiling with clean xmls from my eof project (no DD) still worked without crashing.

What's really odd is that if I instead gave DDC the .psarc files compiled from clean xmls, everything works fine.  The problem with this method is that DDC will accept the ps3 .edat as a valid package file, but doesn't actually create a new one with DD arrangements.  No errors or anything from DDC/Toolkit.

Is there a reason generating DD from the xmls fails that I can fix?  Something with the way my arrangements are authored maybe?  Or alternatively, is there a way to get DDC to actually process the .edat for ps3?  Is this even worth worrying about, or do people not really play customs on consoles anyway?

First time participant here, bass only.  I had assumed I'd be in the beginner's bracket for sure, but I think getting 100% accuracy on Fields of Gold would bump me up next week anyway (according to the rules sticky)?  So I grabbed Twist My Arm too and worked on it a bit.  If both songs are representative as far as difficulty, I guess I'm entering the intermediate bracket instead.  

Anyway, the screenshots....

http://i.imgur.com/HQaEdM5.jpg

http://i.imgur.com/84rqnhA.jpg

I'm definitely flubbing my way through parts Twist My Arm despite the 93% accuracy, so still tons of room to improve on that one.  Looking forward to the weekly competition keeping me honest with consistent practice at least.