ice9

heh - I just noticed your name in the commit logs for EOF :) LIke I said - no disrespect - EOF obviously has a lot of work put into it.. just curious if any thought had been done.... here's what I was thinking: 1) Chords: -Yes, you can manually enter chords in TuxGuitar. In this case, it would be directly used by the exporter -This can be doubly used as a fret anchor (if there's a single note, but it has a chord with all X's, use the position as the anchor) - not sure about arpeggio support - for any chord not explicity defined in the tab, it guesses the right one during export (like EOF) - TuxGuitar already has the code to guess the right chord name for a given chord - fingering choices, seem relatively straightforward - would have to figure out exceptions to this rule 2) section/phrase markers - exactly - use markers for sections, text for phrases 3) lyrics - haven't tried much, but it does seem to rely on putting 'notes' in, rather than a time, or at least putting the lyrics on known notes - was thinking of supporting a ultrastar import - you could then tweak as necessary 4) fret anchors - see #1 - but also curious how EOF determines it - haven't looked at that code yet - I know in some places, while it might be easier to play with fingers 1/3, if it's a major scale, you're better off fingering with 2/4, as the start of the major scale. Honestly, I'm doing this for 2 reasons... 1) I'm a java dev 2) I always like to have a side project going.... so I was just playing around and was thinking "what if I could do all this from TuxGuitar?", and decided to find out :) wow... didn't mean to write that much :D

I've been looking at what is available vs what rocksmith is looking for, and I think it can be done. There would probably be things that wouldn't be possible to notate in GPA itself, so it might not allow for all features to be accounted for. It would be interesting to see what people could come up with though. Like what? I've been looking at the generated files, and the techniques available in RS2014, and I think it's all doable. What things do you think are not notable? fret anchors, chord fingerings, there is a way (or at least a workaround) ..

oh cool - didn't know about that site... yeah - if I screw something up really big in Ultrastar, I'll tweak it in EOF. Main issue with using preexisting Ultrastar files is the sync against the particular mp3 file. Hopefully it won't change, but just like GPA files, there's always a chance it'll be a "little" off.... Would you find a direct TuxGuitar + GPA -> Rocksmith XML exporter useful? (not to step on EOF's toes - just trying to make it easier)

yeah - I hear ya on #1.... tabs are usually never "quite" right - I end up doing a lot of comparing of tabs, gp files and video..... but I like to have a good gp5 file as a basis when I am done. I even had a video of Dave Ellefson on Five Magics that I was slowing down to 50% so I could see what the hell he was doing :D

I've talked to several people, and I was curious what different people use to create CDLC. Obvious EOF and RSTK are a given, but there are a lot of different paths: Personally, I do: GP5/tab file-> TuxGuitar -> GoPlayAlong (to get sync file), editing in TG as necessary for accuracylyrics -> UltraStarCombine using EOF, and tweak as necessary for bend strength, unpitched slides, etc.RSTK->DDC->finished PSARC. EOF is great, but I have a lot of issues with note placement/time sync, so I tend to import from TG/GPA. I do have an ulterior motive here... a direct TuxGuitar->Rocksmith file export. No EOF needed (but GPA would be). Would this be of interest to the community?

First Album: Kiss - Double Platinum (I was like 7 I think - but even then, was into Gene Simmons and the bass) First Concert: Not including the various local "can't remember" bands, the first big stadium one was Jethro Tull on Halloween night, but more importantly, the second one was Megadeth, of course!

another thing... would it be possible to add something to reflect the "slightly flat/sharp" tunings... a lot of the CDLC I did are all in A427, and it would be nice to have that really obvious in the search.

I've found that if you add the silence to the mp3 right at the start, before doing ANY other work, everything else down the line works much better. I've run into issues re-importing GPA-sync'd files and lyric files if I don't.

no... when I build it, I generally do the "max" build first, including all parts, DD w/phrase length=2, RR, tones, etc - if there's an issue, then I start removing things until it works - this is even before I try to play it :) so I don't have any stored scores.

odd - that one is fine, and I can't get it to crash now.... figures

actually... try this: http://www.mediafire.com/download/upfljh6pvmx6o7o/Megadeth_Devils-Island_v1_FAIL_DD_p.psarc - I think this one is the build that is failing for DDC/RR if not, I'll get the failing one up later

I know the song starts right off with a chord - I even tried narrowing it down to a specific arr (bass, in my case) - tried different phrase lengths... the one thing that fixed it was reducing the number of sections. in the mean time, here's the list of sections: <sections count="18"> <section name="intro" number="1" startTime="3.352"/> <section name="solo" number="1" startTime="16.223"/> <section name="transition" number="1" startTime="41.536"/> <section name="verse" number="1" startTime="52.568"/> <section name="chorus" number="1" startTime="75.555"/> <section name="verse" number="2" startTime="87.815"/> <section name="chorus" number="2" startTime="99.354"/> <section name="preverse" number="1" startTime="111.635"/> <section name="verse" number="3" startTime="122.954"/> <section name="riff" number="1" startTime="145.591"/> <section name="solo" number="2" startTime="167.177"/> <section name="solo" number="3" startTime="189.395"/> <section name="verse" number="4" startTime="200.638"/> <section name="chorus" number="3" startTime="211.733"/> <section name="riff" number="2" startTime="234.846"/> <section name="solo" number="4" startTime="257.155"/> <section name="outro" number="1" startTime="279.335"/> <section name="noguitar" number="1" startTime="303.420"/> </sections> it worked after I removed the transition, preverse, solo @ 189.395 and the 2 riff sections I'll have to recreate the CDLC, but will post the link here when I get it built later today

Was working on a song and I noticed something odd: Had a song with 13 sections. DDC generated just fine, but song would crash in Rocksmith. Looking at the DDC output, I noticed it only had 12 phrases generated (it's a fairly repetitive song). When I deleted 2 of the sections from EOF and repacked, it worked (it now had fewer sections). Is this a bug with DDC or Rocksmith?

what about a way to rate the CDLC for accuracy/completeness/etc?

I know - that's why I said "in a perfect world" :D In a perfect world, all the artists/record companies would also say "have you seen this site? this is the coolest thing ever! we should give them money!"

now, in a perfect world, I would download the digital version from iTunes/Amazon, or buy the CD, then my stored digital rights could be used to verify me, and therefore can download the CDLC. I personally never download anything that I do not own the CD/iTunes/etc for, but a lot aren't so honest.

Yeah, I know - that's the dilemma... I guess you could say "ripped from this cd with these settings, song length is whatever, 3s silence added to beginning"... that would get to close enough to not matter

Would it be possible to have an option to upload the xml file that RSTK uses to save the package to parse out the artist/album/song/parts/etc etc? That way you could avoid typos and time, and it would accurately know what's contained inside the cdlc. Then the submitter could just put in the video and cdlc links and be done.

unfortunately a solution to the debate is to get people more technical and not include the .WEM files in the CDLC, and force users to repack the psarc. That way all the hard work of tabbing/syncing/etc has been done, but the user needs to have the original mp3 file to create the end product.