Azrael

By that definition it is probably a hang. In Windows 8 a "hanging program window" becomes greyish after a couple of seconds and if you click into it a popup appears, telling you the "program is not reacting" and giving you the option to terminate it or keep waiting for a response of the program. This is what happens with EOF. While hanging, the task manager shows EOF as "inactive", with a extremely high CPU load (35%).

Wow, looks like some awesome improvements, gonna check it out! In the meantime, here is another ALT-Tab crash log. The behaviour is still the same. And to be more precise, for me it only seems when using ALT-Tab while EOF is in the foreground. ALT-Tabbing back to EOF (when highlighted another window with the mouse before) does not cause crashes!

Nice to see you working on this one again! This is not a bug but rather a new feature request: Maybe you have been aware of the new feature "Create Metronome Bonus Arrangements" in the "Edit Arrangement" window of the Toolkit. @@Alex360 has added it a while ago, and it produces a copy of the original arrangement, exept for adding metronome tick events to the xml. (The benefit is that you can play the song completely on your own and hear nothing but your guitar and a metronome to keep up with the beat.) Now when those psarcs are converted with your program, all the arrangements will appear dublicated. I have been wondering whether you were able to detect those identical arrangements and ignore them in the conversion. Maybe Alex could even sneak some special "flag" or boolean or whatever into the arrangement, telling you that it is a Metronome Bonus Arrangement and that you should ignore it? Here you can find some example CDLC: http://customsforge.com/tags/ccs/Metronome%2BBonus%2BArrangement/?search_app_filters%5Bccs%5D%5BsearchInKey%5D=database_3 I hope you two could look into that. This is not high priority of course, but rather nice to have (if it is relatively easy). Regards, Azrael

Even though I love the song, at first I thought I was going to hate playing Juular. After taking note of all the different finger positions though, it was starting to become fun :-) In order to play this, I have to sit (which I normally don't do), put my left foot on a (really high) stand, the guitar on my left leg and bend down towards my guitar, so that I could basically play with my teeth.^^ Only this way I feel like I can get my arm and hand in a position where I can strech this far... how do you guys do it? :D Here is my score for Advanced Lead: 97.14 % http://steamcommunity.com/sharedfiles/filedetails/?id=386858735

Why do you use two accounts for this discussion? (and alternate between them?^^) Did you try installing Rocksmith on a different PC, maybe a friend's? I don't think there are any (important in this regard) differences between Win 8 and Win 8.1... But if the game and the cable both work on other computers and you already tried verifying the game within Steam (or even reinstalled it), then completely reinstalling Windows MIGHT be the last option to check out. Also: Some punctuation would help us better understand your sentences ;-) Is the volume on your guitar set to maximum? Since it was working fine at some point, did you change anything afterwards?

No, if I understood Alex correctly, you have to insert "0" in EOF. But ingame it is indeed displayed with a "T".

Nice! Feels like I have a new body part strapped to my hand! :wub:

Hey everyone, check out the video of "Love Song" by Tesla http://youtu.be/m-HTGwKFjT8?t=1m3s There is a finger on the low E-String with the label "T" (instead of a number). Also the fingerprint is tilted slightly. It seems to be the thumb! Is this a new feature, or has this been present in the game all the time? It is the first time I noticed it.

@@DevXen Your poll doesn't have enough options. I went with "Yes", but I meant "admins are allowed to edit posts for any useful reason" (not simply "any" reason). In your specific case, I feel like the edit was justified. "You shouldn't quote the post directly above yours" (unless it is very long and you want to answer to one specific point) - this doesn't have to be a board rule, but I feel like it is one of the "unwritten" rules we should all stick to. To notify the person instead of quoting, you can always use the @feature. I think ForgeOn left a note "**Edited by ForgeOn, removed large unnecessary quote". So this is all the explanation necessary. The only problem here is that you were the one person on whom this unwritten rule was actually forced upon, while we see hundreds of wrong examples every day. Anyway I do apreciate beeing active in a community where such things are looked after - even if it is only from time to time. While I can somehow understand your anger, I honestly feel like you are overreacting a little bit with this discussion. Regards and peace everyone Azrael

@@ForgeOn thanks for bringing up this topic. But if you were consequent about it, you could keep removing quotes all day long^^ (You better never visit the Championship - people quote each other all the time, including lots of screenshots. It's horrible and makes loading the pages take ages) But back to topic: @@Lovroman, your plans sound VERY promising. I wish you good luck and hope you can work as part of the Customsforge team. This project will be appreciated by LOTS of people :-) Please give us something to beta-test as soon as you are ready :-)

Guys, you should post your ideas in the official feedback thread (instead, or at least in addition to) posting them here^^ http://forums.ubi.com/showthread.php/439984-Rocksmith-2014-Official-Gameplay-Feedback-Thread?s=abba3bae062ba2dac88064893044ee7c Dan actually reads those from time to time, it seems.

Sure, here are two screenshots: 1. This is the automatic result: 2. And this is how it is supposed to look: My suggestion is that the fret hand position should not be allowed to change within a single handshape - since, obviously, the finger positions don't change. But in this extreme cas with wide stretches, there are different fret positions within a single handshape.

Oh sorry, another try with the links: Original project: https://www.dropbox.com/sh/mgwuz2rroc6sb8h/AACRD1_TqpqvwM0cSihDkr5Za?dl=0 Unpack test: https://www.dropbox.com/sh/enm3ltljoe0lsz9/AAD3k1JHJ53dgz-7ESQR8dhEa?dl=0 Thanks for your answers. Now that I know about the expected behaviour, I'm fine with removing DD first. About the other features: You'll have to ask yourself whether it is worth the effort to go for a full unpack compatability in the long run. It would come in handy to improve bad CDLCs - but well, you've got to set your priorities (you're doing great work already!).

Hi @@raynebc I think the best way is by looking at an example: Here is one of my own customs: regular project folder: https://www.dropbox.com/sh/mgwuz2rroc6sb8h/AACRD1_TqpqvwM0cSihDkr5Za?dl=0 psarc unpacked with toolkit and lead xml imported into new EOF project: https://www.dropbox.com/sh/mgwuz2rroc6sb8h/AACRD1_TqpqvwM0cSihDkr5Za?dl=0 Some things to notice: time signature does not get importedtone changes do not get importedtech notes seem to be gone completely (e.g. pre-bends in bar #80) exept for tremolovibrato doesn't get imported (e.g. in bar #78)palm mutes get lost after (higher than) difficulty level 4 (not in all phrases, though)notes seem to build up in difficulty (as expected) until difficulty level 7 BUT only until bar #5: Level 7 has no notes in bars #6 - #9.It seems like once the maximum difficulty has been reached (within one phrase!) the notes disappear in the next higher difficulty level (yes, now I am really certain that this is what's happening. It depends on the phrases and each phrase's maximum difficulty level - and now I realize this is exacly what @@manchot66 has been saying^^) In another test where I used the original psarc (without DD) and imported it, all the notes showed up. But all the other problems above remain the same. Interestingly, P.M. were gone in most phrases, but not in all of them. To be precise: In those phrases, where P.M. "survived" until the highest difficulty in the DD test case, P.M. is also present in the NDD test case - and vice versa. Regards, Azrael

What I think might be another tiny bug: When I apply a handshape to a set of notes that are positioned on different frets, the function that generates the frethand positions ignores the handshape ghost chord and creates different positions for all the notes within the handshape. Regards, Azrael

Btw. will there ever be an update that removes (or lets us turn off) the following behaviour? A input box is selected just by hovering over it with the mouse. Quite often I find myself clicking on one box and then letting go of my mouse. But because it is wired and there is sometimes tension on the cable, the mouse itself slightly moves sometimes. Because of that, now a different box is selected, for example in the edit chord fingerings dialog. Or I simply move the mouse myself after clicking in the box to be able to view its content. I just realized that this has been bugging me for a very long time, but I never actually mentioned it :)

Hmm... I assumed this was common knowledge: When you use the "import package" function of the Toolkit to unpack a psarc file, and load up the generated xml files of the arrangements in EOF, the difficulty levels would in most cases be completely messed up: The highest difficulty would not contain all the notes, but instead the notes would be "spread" over the various difficulties - overall random notes would be missing. All in all you just couldn't unpack a psarc, edit it in EOF and generate a new psarc without risking the loss of information. I also assumed that this was exactly the problem we talked about in the Resynchronizer thread and that you fixed it in order to improve the Resynchronizer. I have no idea if the problem is the Toolkit, the DDC or the EOF... Anyway I just tested it with one of my customs with DDC 2.5 and 2.6 and the results in EOF are messed up in the same way. Do you need more information to maybe work on that problem?

Thanks again for your awesome work for this community! Just to be clear, does v2.6 now allow us to "import" psarcs into the Toolkit and load up the xml files in EOF withough loosing any notes or techniques (since that is what you needed for your Resynchronizer)? :) Regards, Azrael

EOF takes some patience to learn, but once you know all your techniques it is a very powerful tool :-) Didn't test it ingame, but looked at the EOF project. Arpeggios: Seem to be fine now. As long as the finger positions remain the same, you can include all the nodes in one Arpeggio. When the chord changes, you start the next Arpeggio. About the fingering: EOF will ask you to fill in the fingering automatically for known chords. For the rest, well, use your imagination what seems most comfortable. A tiny thing about sustains: Sustains should not last until the beginning of the next note, because this might block the view ingame when notes are ontop of each other. Choose "Grid Snap" = 1/32 or 1/16 and shorten the sustains one grid step. Only those notes that have a sustain and are then repeated should have a full sustain. You have a lot of tech notes in the chart that will not work ingame as expected. Tech notes are created automatically on import of the gp5 file to make complex bends and such things possible. You should have a look at this tutorial: http://customsforge.com/topic/890-tech-notes-tutorial-authoring-complex-bends-and-more/ Press F4 to view the tech notes. When you spot red notes, they won't have any effect, most likely because they are at a wrong position. Maybe you used "snap to grid" at some point? The tech notes are not effected by this and might become unsynced. Maybe it isn't your fault though - sometimes there are rounding errors in the position setting in milliseconds. So remember: Not all tech notes have to be grid snapped, but you have to check all of them to see what effect they are supposed to have. Moreover, you can delete a couple of the tech notes - the less tech notes, the better (more "flexible" or forgiving) the note regognition. In bar #116, you could delete most of them, because we simply want a bend and then a bend + release. On the first note, delete all the tech notes and use a "regular" bend instead with CRTL+B - enter 2 half steps and you're done. The visual representation ingame should be nearly the same, but the regonition would be better.One the second note, delete all but the tech note for starting the bend [/2] and the last tech note [/0] on its sustain tail (this is for the release). This way Rocksmith will be less strict about the timing of the releaseMoreover, in the gp5 file at this point the author wrote a annotation "bend & bull-off" but made the note on the 5th fret a ghost note for some reason. by selecting the note and hitting "n" you have to remove the ghost status and set "PO" for pull-off instead.I saved the changed I did in this bar so you can have a look as an example!It will take some time until you see those details and will be even harder if you don't even play the arrangement. About the bass track. I don't completely understand your question, but it does look fucked up^^ But I was able to simply import the bass from the gp5 file again and then everything was synced perfectly. On saving there are a lot of errors and warnings. Idealy all will be gone exept the one "mark unpitched vocals as playable freestyle" Set fingering positions correctlySet fret hand positions correctly (this can be automated by clicking Track-Rocksmith-Fret Hand Positions-Generate all diffs (you might want to improve it manually afterwards, but it should be ok)You have slides without ending positions. Those are unpitched slides, because gp5 doesn't store the info where to end a unpitched slide. you will have to remove the "regular" slide under note-pro guitar and then define the unpitched slide under note-rocksmith. The exact ending position is not very important, but the direction (up or down the neck) is! so choose at least 3 frets up or down the neck - whatever sounds best.On bends with tech notes you can remove the regular bend to prevent another warning Last but not least your vocals are fucked up :P You have to mark those vocals that are supposed to show up in one line by selecting them all (hold SHIFT and click on first and last word) and hitting CTRL+M (it generates a blue bar above them) - now the vocal preview will actually show your vocals!Please (!) use sustains in your vocals. Usually you can just close all the gaps between the words in one line by maxing the sustains. This will make the vocals look much nicer ingame (instead of having each of them flash a split second)I improved the first two lines as an example.Also I added count-in metronome tick-events into the bar #2 by pressing SHIFT+E. Wow... there is a lot to do here... and there maybe even more, but I stop at this point^^ Your folder with my changes: (bar 116, bar 2, vocals, reimported bass) https://www.dropbox.com/sh/9q5ja3h3i860bry/AABCtzsa22M01mGOz1Do193Ta?dl=0 But please only look at those as an example and continue working with your own files - I might have messed up some other stuff! Good luck!

Advanced Rhythm: 96.22 % http://steamcommunity.com/sharedfiles/filedetails/?id=383372245 Surprisingly high score, but I bet it sounded shit! Also the nonexistant tremolos help with high scores, and the very forgiving note regognition in the intro parts. Lead: 94.68 % http://steamcommunity.com/sharedfiles/filedetails/?id=383373557 Also nice score, all things considered. But I don't think I would rate this song 8 (7 instead). The overall tempo is quite high, but there are no super difficult parts, no solo. When there are solos that I am simply not fast enough for, I consider it a high difficulty. But in this case the problem is (only) to keep up the tempo for such a long time. By the way, do you agree with the sync problems I posted on the song page?

Well... I recorded my western acoustic guitar by using the output of my amp. it is a dedicated acoustic amp though that makes it sound exactly like the original - no distortion at all. But buying a new amp just for this might not be the best option, right?^^ Shouldn't you be able to record with a microphone, provided it is a very good one? - might be less expensive than the amp :-)

+1 Happens while chart is stopped. In fact I don't even need to load any project to make the crash happen (simply start eof.exe then alt-Tab one time = crash now 5 times in a row). Recovery usually does work, but sometimes it (seems to...) misses a couple of last changes. eof_log.txt: 480: Logging started during program initialization at 01/29/15 08:48:04 480: EOF v1.8RC10 (r1369) 480: eof_load_config() entered 480: set_default_config() entered 480: eof_controller_read_button_names() entered 480: eof_controller_read_button_names() entered 480: eof_controller_load_config() entered 480: eof_controller_read_button_names() entered 480: eof_controller_load_config() entered 480: eof_controller_read_button_names() entered 480: Importing chord shape definitions 480: eof_load_chord_shape_definitions() entered 480: Processing line #1 480: Processing line #2 480: Chord shape definition loaded 480: Processing line #3 480: Chord shape definition loaded 480: Processing line #4 480: Chord shape definition loaded 480: Processing line #5 480: Chord shape definition loaded 480: Processing line #6 480: Chord shape definition loaded 480: Processing line #7 480: Chord shape definition loaded 480: Processing line #8 480: Chord shape definition loaded 480: Processing line #9 480: Processing line #10 480: Processing line #11 480: Chord shape definition loaded 480: Processing line #12 480: Chord shape definition loaded 480: Processing line #13 480: Chord shape definition loaded 480: Processing line #14 480: Chord shape definition loaded 480: Processing line #15 480: Chord shape definition loaded 480: Processing line #16 480: Chord shape definition loaded 480: Processing line #17 480: Chord shape definition loaded 480: Processing line #18 480: Chord shape definition loaded 480: Processing line #19 480: Chord shape definition loaded 480: Processing line #20 480: Chord shape definition loaded 480: Processing line #21 480: Chord shape definition loaded 480: Processing line #22 480: Processing line #23 480: Processing line #24 480: Chord shape definition loaded 480: Processing line #25 480: Chord shape definition loaded 480: Processing line #26 480: Processing line #27 480: Processing line #28 480: Chord shape definition loaded 480: Processing line #29 480: Chord shape definition loaded 480: Processing line #30 480: Chord shape definition loaded 480: Processing line #31 480: Chord shape definition loaded 480: Processing line #32 480: Chord shape definition loaded 480: Processing line #33 480: Chord shape definition loaded 480: Processing line #34 480: Chord shape definition loaded 480: Processing line #35 480: Chord shape definition loaded 480: Processing line #36 480: Chord shape definition loaded 480: Processing line #37 480: Chord shape definition loaded 480: Processing line #38 480: Chord shape definition loaded 480: Processing line #39 480: Chord shape definition loaded 480: Processing line #40 480: Chord shape definition loaded 480: Processing line #41 480: Chord shape definition loaded 480: Processing line #42 480: Chord shape definition loaded 480: Processing line #43 480: Chord shape definition loaded 480: Processing line #44 480: Chord shape definition loaded 480: Processing line #45 480: Chord shape definition loaded 480: Processing line #46 480: Chord shape definition loaded 480: Processing line #47 480: Chord shape definition loaded 480: Processing line #48 480: Chord shape definition loaded 480: Processing line #49 480: Chord shape definition loaded 480: Processing line #50 480: Chord shape definition loaded 480: Processing line #51 480: Chord shape definition loaded 480: Processing line #52 480: Chord shape definition loaded 480: Processing line #53 480: Chord shape definition loaded 480: eof_set_display_mode() entered 480: eof_window_create() entered 480: eof_window_create() entered 480: eof_window_create() entered 480: eof_window_create() entered 480: eof_window_create() entered 480: eof_scale_fretboard() entered 480: eof_load_data() entered 480: eof_init_colors() entered 480: eof_undo_reset() entered 480: Initializing audio 480: eof_mix_init() entered 480: Checking for crash recovery files 480: Entering main program loop

The timing of the tone changes is not affected by the beats. Many (me included) make the wrong first assumption that you have to select a beat and then add the tone change marker. Instead the tone change is placed where the green vertical line in the left part of the screen (the current position of the song playback) is located. Press the buttons pageup or pagedown on your keyboard to seek to the correct beat. (ideally you would place the tone change just slightly before the first note with the new tone, not exactly on it). If you go for perfection and want your song really close to official quality, you might also be interested to have the metronome/drummstick ticks a count-in bar before your first note that you can hear in official songs. Check out this tutorial if you want to: http://customsforge.com/topic/13688-how-to-add-a-metronome-to-any-song-metronome-bonus-arrangement/ It will tell you how to best design your leading silence, have the measures in sync with the music (what firekorn mentioned) and add the count-in ticks inside EOF. The folder you shared doesn't contain the .ogg, so loading up the eof file doesn't include the song itself - no sound! Anyway, thanks for seeking advice! Too many people just release their stuff and develop bad habbits. It would be great to tell the name of the song you are charting and e.g. the tuning ;-) Won't tune to D standard now, but I would look at the eof file again, if you load up a new version and include the .ogg. Adding Arpeggios (shows the name of the chord ingame next to the note highway) or Handshapes (no chord name, somewhat "cleaner" look) is super easy: Select the notes that should be affectedSelect "Note"->"Pro Guitar"->"Arpegio"->"Mark" for Arpegios ORSelect "Note"->"Rocksmith"->"Handshape"->"Mark" for HandshapesThis will produce "ghost" chords. they don't actually show up ingame, but you can define the finger positions for the chord.

Have you downloaded the latest release AND hotfix from this thread? http://customsforge.com/topic/1529-latest-eof-releases-r1369/ I am running EOF on Windows 8.1 just fine... I suggest you ask for help in this forum, since the dev might see your post there: http://customsforge.com/forum/54-editor-on-fire/ Good luck!

Tested Vultures again - now it is perfect! Very good job, your tool is going to be awesome!