Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in. Login to AccountCreate an Account
Learn & Play Rocksmith!
Want to play the songs you love? Registration and the use of this website is 100% free.
The only thing you need is a legal copy of Rocksmith 2014 w/ a cable. Click here to buy it.
Having trouble logging in or registering? Please click "Support" below.
I have spoken about this issue a long, long time ago, although I did not articulate the problem similarly.
I do not have "highlight non-grid snapped notes" option switched on in EoF because I would be looking at cyan graphs almost permanently.
It's not the grid moving, it's the notes. It comes because (I think, I am sure raynebc can correct me) of difficult maths i.e. sums that require rounding.
For example, you say that it never happens when you double the bpm. Because doubling something is mathematically easy and does not require rounding multiple decimal places.
But when you go from 120 (the defaut number) to something like 145 then the multiplier is 1.20833333 which cause some of the notes to come off grid ever so slightly.
I think it happens as soon as you change BPM, it's just that EoF seems to not be highlighting it straight away. There is possibly logic to why EoF takes a step or 3 before it realises notes are off grid and highlights them.
To reproduce what I mean
- Change BPM (with auto adjust notes)
- Press Ctrl+A to highlight all notes
- Hit Ctrl+Shift+R to re-snap all notes
- Hit Ctrl+Z to make EoF "undo"
- Notes will now be highlighted cyan
The moral of the story is that when you change BPM (especially when you are actually changing individual beats to beat map the song) then notes come off grid. It is good practice to selct all the notes and re-snap them again manually at regular intervals.
I always re-snap all arrangements (including tech notes) before saving an EoF project. Even if I plan to come back to the project and work some more on it later (i.e. it not "finished" yet), I always re-snap before saving.
To re-cap, the commands that will solve your issue
Go up, hits loads of repeated pre bends, then come down. You can sustain the first bend and hold if you want. You will probably have secondary questions when you try it. Best to take some screenies, post them and ask. I could be here all day with a million permutations, but the pic I showed you is how to begin.
As raynebc says it cannot be helped. I've got a pretty decent rig that can zip through modern games, and I have to stop/start every so often.
Trust the visuals when syncing. If you are making modern metal type music where the audio graph is basically a rectangle then using visuals can be difficult, but usually in most songs there are clear places on the audio graph where drums are hitting (usually snares), choruses are kicking in/ending, solos begin and lots of other visual cues.
Or, as raynebc also says, you will be hitting the space bar constantly anyway to drag beat markers about. Then the audio/visuals will stay in relatively good sync.
I'm so used to it now I hardly notice (or simply don't worry), but I always rely more on where the beat markers are in relation to the audio graph rather than the actual audio.
I thought that the quick save function eliminates all warnings?
Can this not be used instead of eliminating other warnings or making matters more complex with extra settings?
I'm not trying to be anal and I bearly read the warnings from EoF I just get used to (on a per project basis) the order in which they come up - it's kinda rhythmic tbh. It has saved my ass countless times when either a warning I was expecting does not appear, or a new warning does appear - I have a think about why its has appeared or went away, then amend anything I have changed by mistake or have not changed.
It's pointless trying to type out all possible examples but for the sake of argument I will produce 1
I have went through my newly imported GP and eliminated all the slides with no end position. EoF warnes me about a slide with no end position. I think "crap I missed one".
Whereas I have come across songs where its impossible not to cross a boundary with sustain or a phrase boundary with an arpeggio, it does not happen that often tbh. And the warning is a reminder to look out for possible glitches in game. Trouble shooting why there's a gfx glitch or missing notes in your DD is far easier if EoF has been warning you that you crossed boundaries. I don;t like crossing section boundaries at all, and most songs I have no intention of making DD. But, someone else might and it reduces the chances of glitched charts and/or hanging customs (omg I'm so old - hanging customs is so 2014 )
I know it's user preference and most EoF users will probably not want all warnings all the time, I'm just fighting the case for what I see as very minor inconvenience that can actually be extremely helpful and a great time saver in the long run.
And, if I've just invested an hour or more of my life into making a chart look nice, I damn well appreciate a robust saving system. If I've just popped in to change a note or two I still appreciate a robust saving system