raynebc

The toolkit should see when the XML file written by EOF indicates that a capo is used.

Doing that will break the detection of the bass note (ie. for slash chords). I authored that chord and while EOF didn't know the fingering for it, the program did not crash. Did you have to add a chord shape definition before the crash would occur? Can you paste that definition here? Are there any other needed conditions for causing this crash?

The two 9mm Parabellum Bullet songs were released a month and a half ago.

That is expected behavior. The capo position is treated as the nut, just as with guitar tablature. In EOF, you could transpose all notes down one fret, but that will only work if there are no open notes in the track (ie. you can't play the low E note in standard tuning if there is a capo on fret 1).

There are lots of good songs, but I'm curious about your last sentence. All of the Japanese DLC they announced has already been released, hasn't it?

I was trying to think of a way to do cstewart's example so that the note on the G string didn't need to be picked more than once until after it slide back down to fret 4. I realized I had to fix it so that tech notes with sustain status work correctly, but in the next hotfix, you'll be able to author it like this: http://i15.photobucket.com/albums/a354/raynebc/linknextchordswithsustaintechnotes_zpsb2ad3d68.jpg This is a tricky one, and it may or may not work since the chords aren't split up into single notes (because the technotes have linkNext status instead of the regular notes themselves), but here's how it would work in theory: 1. The first note at fret 4 links to the note on the G string in the chord that follows and slides into it. 2. The tech note on the G string in first chord causes that note only to export with its sustain and to link to the note on the G string in the chord that follows. There is no sustain status in effect for the open note on the A string, so it exports with no sustain because by default individual notes in a chord export with no sustain. 3. Pretty much the same thing as #2. The tech note on the G string in the second chord causes that note only to export with its sustain and to link to the single note that follows. There is no sustain status in effect for the open note on the A string, so it exports with no sustain. 4. The linkNext was applied with a tech note instead of to the normal note itself in order to prevent the chord that follows from being split up into single notes. The single note slides into the note on the G string in the next chord. 5. The tech note on the G string in this last chord causes that note to sustain after the slide has ended. There is no sustain status in effect for the open note on the A string, so it exports with no sustain. Here's what the XML looks like: <note time="1.963" linkNext="1" accent="0" bend="0" fret="4" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="6" string="3" sustain="0.277" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="3.084" linkNext="1" accent="0" bend="0" fret="6" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="4" string="3" sustain="0.277" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <note time="3.645" linkNext="0" accent="0" bend="0" fret="4" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="3" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chord time="2.243" linkNext="0" accent="0" chordId="0" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down"> <chordNote time="2.243" 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="1" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chordNote time="2.243" linkNext="1" accent="0" bend="0" fret="6" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="3" sustain="0.558" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> </chord> <chord time="2.804" linkNext="0" accent="0" chordId="0" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down"> <chordNote time="2.804" 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="1" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chordNote time="2.804" linkNext="1" accent="0" bend="0" fret="6" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="3" sustain="0.277" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> </chord> <chord time="3.364" linkNext="0" accent="0" chordId="1" fretHandMute="0" highDensity="0" ignore="0" palmMute="0" hopo="0" strum="down"> <chordNote time="3.364" 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="1" sustain="0.000" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> <chordNote time="3.364" linkNext="0" accent="0" bend="0" fret="4" hammerOn="0" harmonic="0" hopo="0" ignore="0" leftHand="-1" mute="0" palmMute="0" pluck="-1" pullOff="0" slap="-1" slideTo="-1" string="3" sustain="0.278" tremolo="0" harmonicPinch="0" pickDirection="0" rightHand="-1" slideUnpitchTo="-1" tap="0" vibrato="0"/> </chord>

By default, when you place a section on a beat marker, it applies to all tracks. You would have to check the "specific to ..." checkbox in order to make it apply only to the currently active track. If you imported sections from a Guitar Pro file and want to make it apply to all tracks, you can open Beat>Events, and for each of the desired sections, select it in the list, click Edit and then uncheck the box that makes it specific to only the one track.

If you want chords to display as repeat lines, you have to have the handshape tag long enough to cover multiple chords. Otherwise you can use the "crazy" status on a chord to force it to display as low density (a chord box) and the handshape tag (lane highlighting) won't extend from the first chord to the second. EOF puts two chords into the same handshape tag if they're the same chord and are close enough (10 seconds), but I could probably make that threshold user-configurable. When you can reproduce it on-demand, let me know. Until then there's no good way for me to identify the problem.

If you made it a single long note that slide from fret 7 to 9, Rocksmith would make the slide slow enough to take the entire duration of that note. If you want to author it to be more specific, ie. to bend from fret 7 to fret 9 and then sustain on fret 9 for a while, you could apply the linkNext status (available in the "edit pro guitar note" dialog) to the note that has the slide: http://i15.photobucket.com/albums/a354/raynebc/linknextslidewithsustain_zpsca357696.jpg The linkNext status will cause Rocksmith to combine the two notes as if they are one note, and you only have to pick the first one.

I'll need to be able to reproduce the error before I could easily fix it, so if you can provide a project file that reliably results in that error message with a specific list of steps (ie. open the project, enable tech view for a specific track, save the project), it will allow me to correct it.

When Go PlayAlong exports the synced song from your library (a feature of the paid version of the program), it should create a folder along with that GPAX file which contains the XML, Guitar Pro and audio files.

What you're wanting to author is extremely specific, and the more specific you get the more complicated it can be to author. I don't think you have any other option but to do it like this: http://i15.photobucket.com/albums/a354/raynebc/Linknextcrazyslides_zps67971c79.jpg If DDC has problems with it, make sure to let Chlipouni know so he can address them. Resnapping all notes is not something you should do out of habit, it should only be used if you've managed to get your notes out of grid snap. It's better to avoid that condition altogether, such as by not clicking+dragging notes across tempo changes. If you have to move several notes, copying them to the clipboard, deleting them, seeking (using per-beat or per-grid snap seek functions) to where the first copied note should go and pasting prevents the notes from getting out of grid snap.

It's not even a good protection against piracy, they just don't want to have to support a giant list of third party hardware.

The "Edit pro guitar note" allows you to set many Rocksmith features, but most techniques have a keyboard shortcut to toggle them on/off for selected notes. These shortcuts are listed in the menu system, ie. CTRL+Up/Down toggles slide technique, H toggles hammer on, P toggles pull off. Those features should import from the GP file without issue, if you find otherwise please provide me the offending GP file so I can troubleshoot. Grace notes, however, are not a technique supported in Rocksmith, and due to the problematic way they are defined in the GP file (they are not defined as standalone notes, but as an "effect" of another note), EOF does not import them. Ghost notes do not export to XML, their only usefulness is in authoring arpeggios. If you want to have a slide into a note, you would probalby need to author a note, make it slide up and then place the desired note at the end of that slide. If you apply the "ignore" status to the note serving as the slide in, I think that causes Rocksmith to not display the note's head so it would just appear as a sliding tail. So that won't require the slide for scoring purposes but it may be aesthetically useful to illustrate for the player that it's there.

Hi, folks. Another quick hotfix (r1298) is in the first post. This fixed a bug where linkNext status used with chords could cause RS2 export to fail.

Hi, folks. The latest hotfix (r1297) is in the first post. Changes are as follows:*Fixed a bug where changing tracks while tech view was enabled could cause some types of phrases to be removed from the track.*Fixed a bug where the "Note>Remove statuses" function didn't remove ignore or sustain pro guitar statuses.

No it isn't, I downloaded it twice, and both times it passed WinRar's validation. Your computer probably just broke the download part-way through so you'll have to try downloading it again.

I'd need the project file that causes this, if you are able to reproduce the error reliably. There is a bug with RC9 where if you leave tech view enabled for a track, change to another track and then change back to the first track, some phrases are removed because some clean up logic wasn't updated have handling for tech notes yet. This will be corrected in the next hotfix. That's not something I'm going to change, it would require far too many hours of programming and debugging to allow notes at the same position to not merge into a single chord. The non tech note slide for the purple note was probably removed because it can't slide down as far as the notes on fret 5. The slide on the orange note may appear to start later in-game, but that isn't something you can define in the XML with just tech notes. The game decides when a slide starts, and the only way to control that in the chart is to use additional notes and the linkNext authoring mechanic.

I mentioned the Program Files folders specifically because all versions of Windows newer than XP have a security mechanism that denies programs write access to anything in those folders unless the program prompts you to give it administrator access (an "allow program to make changes to the computer" prompt) or if you launch the program by right clicking on it and selecting the option to run it as administrator.

Hi, folks. The new release candidate (1.8RC9) is in the first post. Changes since the previous hotfix are as follows: *Changed the SHIFT+T shortcut that toggles MIDI tones so that it can be toggled on/off during chart playback. *Improved keyboard handling logic so that the numberpad enter key can be used in dialog functions. *Fixed a tech note RS2 export bug where the "bend" attribute of a note/chordNote tag didn't reflect the strongest bend within the note. *Fixed a bug where unpitched slide tech notes weren't displayed or exported to XML correctly. *Fixed a bug where a chord inside of an arpeggio phrase didn't preserve the "ignore" status when broken into single notes. *Improved the RS2 export of partially ghosted chords, which will now not use an arpeggio chord template unless the chord in question is also within an arpeggio phrase. *Fixed the key detection for spacebar, - and = related keyboard shortcuts. *Corrected RS export to write the hours in the lastConversionDateTime tag properly as a value from 0 to 23. *Changed RS2 export to write chordNote tags for all chords, since it's been determined Rocksmith 2014 requires this to avoid graphical glitches. *Updated auto-adjust logic to handle fret hand positions. *Updated auto-adjust logic to move tech notes as well as regular notes. *Updated the logic so that when the first beat marker is moved, the tech notes are moved accordingly. *Updated the "Insert new difficulty", "Paste from", "Erase track", "Erase track difficulty" and "Manage RS phrases" functions to handle tech notes. *Updated the color coding for the display of Rocksmith phrases to reflect the normal notes, not the tech notes. *Fixed a bug with RS import logic where some escape characters weren't read correctly, and improved Go PlayAlong import to support GP files with escape characters in their names. *Improved the "Beat>Reset BPM" function to allow you specify whether tempo changes after the selected beat are removed instead of all tempo changes after the first beat. And here's the customary wall of text changelog for RC9: http://www.fretsonfire.net/forums/viewtopic.php?p=625266#p625266 It's been a long time coming, but Rocksmith 2014 authoring should be pretty stable now even though some features are notably not complete yet (ie. Score Attack support). Lame has been updated to the latest version (3.99.5). Oggenc2 has been updated to the latest version (2.87). Oggcat has not been updated since the latest version (0.8a) always forces a re-encode instead of trying to concatenate the files as-is. The documentation probably needs more work, let me know if anything is particularly lacking. I'm planning on adding a built-in tutorial for Rocksmith 1 and 2 authoring, and that is something I really want to finish before the 1.8 stable release or the next release candidate, whichever is first. I'm working on an outline and I may post a working draft to get public comment on what's needed to flesh it out. The keyboard logic changes since RC8 may work better or worse for you depending on your keyboard layout, but if anything doesn't work as well as it used to when you are in English US layout, let me know.

Hi, folks. I'll be using this thread to maintain the latest versions of EOF in one place. To start, download and extract EOF 1.8RC12: http://www.mediafire.com/file/ih70h6p67iy77ka/eof1.8RC12.zip You can keep that zip file handy to avoid downloading it more than once. When I release a new hotfix, all you have to do is replace the files from the above zip file with the ones from the hotfix. The latest hotfix (9-26-2020) is here: https://www.mediafire.com/file/6xzg32k4a9gqwxs/eof_hotfix_%289-26-2020_4%29.zip/file *If you use a non QWERTY US English keyboard layout, and keyboard controls/shortcuts aren't working for you, please make a post describing what keyboard shortcuts aren't working, and what the Info panel says the "CODE" and "ASCII" values are after you use each of the keyboard controls in question. I can make Mac releases and will try to post one with each Windows release, but my ability to do so is sometimes limited. If I don't get around to releasing a Mac build you want, just remind me to do so. The latest Mac build (9-26-2020) is here: http://ignition.customsforge.com/eof/download/487 Unless you have oggenc and LAME installed (these don't come with the Mac build for licensing reasons), you won't be able to have EOF automatically convert from MP3 to OGG when you create a new chart. If you have trouble getting those set up on your system, here is a package that should get them installed and usable by EOF: http://www.t3-i.com/apps/eof/downloads/eof_utilities.pkg Please provide any and all feedback, including bugs and feature requests. If possible, also please review the included documentation (manual, tutorials) and let me know if you find any room for improvement there. Eventually I plan to add a Rocksmith authoring section to the pro guitar tutorial, but the community's knowledge of the Rocksmith songs' makeup changes pretty quickly so it's hard to know when particular features are considered fully known. For any features that ARE fully known (like anchors), please feel free to remind me if they aren't incorporated into EOF yet, in case I missed any information being passed around on this forum or the Google group. Note: If you are reporting a bug, please specify which hotfix (date) you're using. I release hotfixes on a somewhat random schedule, sometimes more than once per day, so the issue being reported may have been fixed in a release you haven't tried yet.

That would be easier than skimming hundreds of updated threads per day (it really was like that back in Smithy Anvil's prime).

EOF's log file should give the Operating System's reason for the error. Usually it's something like a permission issue (your project file is in a protected location such as within "Program Files" or "Program Files (x86)") or the folder is marked as hidden or something. Usually in a worst-case scenario, you can use "File>Save as" to save someplace else.

The easiest way to add multiple difficulty levels is to use the DDC (Dynamic Difficulty Creator) feature in the toolkit. It requires that you've placed section markers appropriate in the chart. You can add difficulties manually, but it is a much more complicated process.

I like Bandfuse a lot, I consider it an excellent complement to Rocksmith. The only reason it isn't a complete replacement is because there is no known way to hack customs into it. The songs use instrument stems so you can be certain they use a strong encryption. Sure, people could break it, but the people that can do it don't want to get sued (threat of legal action was why the latest RB3 songs' encryption was not publicly broken).