raynebc

It's probably a temporary outage on Mediafire's network.

A while ago, EOF and the RS toolkit started using a simplified XML formatting that allows any default values to be omitted (ie. don't have to define fretting or fingering for a string that isn't used in a note/chord). Make sure you're using the latest toolkit and EOF hotfix to avoid such issues.

It's more of an Allegro bug than anything else, as it doesn't handle drawing multiple submenus on top of each other well. There are some workarounds: 1. Use keyboard accelerators: When a menu item has an underline, you can activate it by pressing that key on the keyboard, ie. use ALT+T to open the track menu, then press R to select the Rocksmith submenu, then press H to select the "Fret hand positions" submenu and then press S to select the Set function. 2. Use keyboard shortcuts: Some menu functions have a function key or key sequence listed to the right edge of the menu to indicate a way you can use the function without even having to open the menu. The shortcut for the set fret hand position function is SHIFT+F. 3. Increase the width of the program window. You can make EOF's window larger by using File>Display>Display and picking a pre-set window size or setting a custom size. You can also simply enable the Notes panel (File>Display>Notes panel>Enable or simply CTRL+P) to make the window 50% wider than any of the pre-set sizes.

EOF doesn't write .chart files. You could try one of the converters that can translate between a chart and MIDI file. You could also try Moonscraper, which is a chart editor for the game Clone Hero that can import a MIDI and save in its native .chart format.

Very odd. The command prompt was completely broken? That would definitely break a few things in EOF.

If you're using the toolkit to add dynamic difficulties (DDC), it could be a problem involving that. If you create a version of the chart without DDC, do all notes appear in-game?

First, make sure you're using the 2-20-2019 hotfix, as the one before that had some audio file handling problems. Otherwise: What option are you picking for the location of the new chart? When I create a new project, select an MP3 and choose the source audio file's folder for the destination, it has me select a bitrate and then it creates an OGG as expected. If I instead opt to create a new folder, it creates a new folder named "[ARTIST] - [sONG TITLE]" in my configured song folder (defined with "File>Song folder"). If you have no song folder defined, it should default to EOF's program folder but then you can run into permissions or file name compatibility problems depending on where you've stored EOF, ie. if you put EOF within one of Windows's "Program Files" folders or if ANY folder in the path to the project folder includes any accented/Unicode characters. That said, you could still create customs even if that didn't work because you could prepare the OGG file in Audacity or something. Only certain tools used by EOF have limitations with accented/Unicode characters in file paths.

You might be able to kind of cheat and mark those chords with the "hi dens" status, but I'm not sure if that will work as well.

Hi, folks. The latest hotfix (2-20-2019) is in the first post. Changes are as follows: *Fixes bugs with audio handling introduced by the previous hotfix. *Improved Feedback import to allow the selected audio file to be named bass.ogg, keys.ogg or crowd.ogg instead of creating a copy named guitar.ogg. *Added an "Enable open strum by default" preference that will take effect for new projects. *Improved the new chart wizard so that if Rocksmith export is enabled, and neither FoF nor Rock Band exports are enabled, pro guitar tracks have their difficulty limits removed by default to suit Rocksmith authoring. *Fixed a bug where clicking the "Auto-Adjust sections/FHPs", "Auto-Adjust tech notes" or "EOF leaving focus stops playback" checkbox immediately after clicking the Default button in the Preferences dialog causes the dialog to be closed. *Improved the "Validate tempo map" function to correct the first beat's position if it doesn't match the delay value defined in Song>Properties.

EOF can output a "musical MIDI" (enabled in the import/export preferences) that is probably similar to what you'd get from Guitar Pro or TuxGuitar.

It looks like this only happens after using the Default button in the same dialog instance, but I'll be able to fix it.

The latest hotfix of EOF has some bugs with its audio file handling that result in the leading silence function not working correctly, but otherwise EOF will detect if the stream copy option failed and resulted in a short audio file and will offer to undo the operation. OggCat has some limitations with which OGG files it can append, so sometimes you have no choice but to use the re-encode option.

It seemed like for most people, real guitar is too hard for a party game. Rock Band 3 or Bandfuse would be the closest matches to your suggestion, but neither of those had dancing and both of those have reached their end. I'd like to see a subscription model, but it would probably cost more than people would want.

The latest hotfix is pretty buggy with waveform, spectrogram, load ogg and leading silence. Here's a Windows beta build that should generally fix those issues: http://ignition.customsforge.com/eof/download/304 I want to allow testers a day or two longer to test this beta out to make sure the problems are gone, and I can also add some more features until then.

For EOF to give that error, the XML file must resemble the expected Rocksmith arrangement at least a little bit (ie. has an "" tag near the beginning). Are you able to upload the XML file that wouldn't import so I could look at it?

Hi, folks. The latest hotfix (1-31-2019) is in the first post. Changes are as follows: *Re-assigned the A accelerator key from Note>Transpose to Note>Clear, since the functions in the former menu already have keyboard shortcuts. *Fixed a bug with the "Validate tempo map" function that wouldn't correctly take non #/4 time signatures into effect. *Added "End proximity" selection functions to select/deselect notes that end within a specified distance (or one grid snap length) of the note they precede. This will help in case you want to manually apply a specific note gap, by selecting notes that don't have at least a gap of the current grid snap length and then using [ or the scroll wheel once to shorten the selected notes. *Renamed the "Neighbor proximity" selection functions to "Start proximity" to better identify their purpose compared to the "End proximity" selection functions. *Added the ability to replace some of EOF's built-in graphics, fonts and sounds by saving PCX and WAV files with appropriate file names into the "resources" subfolder. A readme file is provided in that folder defining the names of some usable file names and the gem, font or sound effect the file pertains to. Allegro's "grabber" command line utility can be used on eof.dat to export any of EOF's built-in images or audio for reference/alteration. *Fixed a bug with MIDI import where the note length wasn't correctly read for GHL open notes. *Updated Feedback import to support Moonscraper's notation for non #/4 time signatures. *Improved Feedback import to allow the selected audio file to be named song.ogg, drums.ogg, rhythm.ogg or vocals.ogg instead of creating a copy named guitar.ogg.

Based on the screen capture and EOF's logging, it looks like the problems start with the open low E note after the first four sets of triplets. I'm guessing the low E note isn't supposed to be part of the triplets, but the screen capture may be saying that it is. You might be able to alter the tablature in a way that it will export a valid file, but ither way, Guitar Pro 7 is exporting the GP5 file incorrectly. Worst case scenario, you can author it in EOF manually by using the tablature as a reference.

Unfortunately, those problems never occur on my Macbook. I'm also not a Mac expert so I don't know how to troubleshoot that problem. Are any other Mac EOF users able to explain why this could happen? I think I remember somebody mention that Mac OS may interfere with EOF if EOF is within the Downloads folder. If it isn't already, it's probably worth moving EOF to a folder on your Desktop or something like that.

This will mostly happen if the active track isn't one of the guitar/bass tracks with "real" in the name, as those are the only tracks that can contain Rocksmith arrangements. Use CTRL+Tab functions or Song>Track to change the track and let me know if those functions are still unavailable.

That file does not open in Guitar Pro 5, which instead gives a cryptic "Erreur E/S 998" error message. So the file is corrupt, but I don't have enough information to determine what length the note is supposed to be. EOF's logging suggests this problematic note is in the first measure of the first track. If you can post a screen capture, it might let me see what that track is supposed to have in it. In case I can't add workarounds for this corrupted file, there may be no way to import it directly into EOF. It's probably worth contacting Arobas support and explaining that their program is exporting a broken GP5 file. If they fixed that already, they may suggest upgrading to a newer version of their program.

That file seems to be in GPX format and not in GP5 format, so EOF won't be able to import it and I can't open it in Guitar Pro 5 to examine it. Please send me the GP5 file that EOF wasn't able to import.

I suppose. Although if this originated in Guitar Pro 6 or newer, a buggy export is probably the reason it won't import. Sometimes, the broken GP5 exports won't even open in Guitar Pro 5.

It's an error in the Guitar Pro file. The smallest note length that is allowed in GP5 specification is a 1/64th note, which is written as length 4. GP6 has been known to occasionally write buggy GP5 files with features not actually supported in Guitar Pro 5. Check to make sure the tablature doesn't use anything shorter than 1/64.

There may be specific scenarios where this kind of thing could happen, ie.: 1. If you create the waveform graph, then use "File>Load OGG" to load a different one, the waveform isn't recreated until you hide and show the waveform again (ie. press F5 twice). This is intentional behavior in case somebody wanted to load a drum stem, display its waveform and then load a different audio file while keeping the drum waveform shown. 2. If you have the project open in EOF and edit the chart audio outside of EOF, the change isn't immediately reflected because EOF loaded the audio into memory already. Re-loading the project would fix it.

If you mean you want to import the Rocksmith XML file and remove everything except the (edit: highest) difficulty, this should do it: http://customsforge.com/index.php/topic/21280-how-do-delete-dd-sections/?do=findComment&comment=166356