Jump to content

albatross213

Member
  • Posts

    2,700
  • Joined

  • Last visited

  • Days Won

    25

Everything posted by albatross213

  1. @@Zooropa_Station - Thanks. Will check them out and try to get updates out soon!
  2. @@SedentarySeal - I'd like to do them eventually, but it's kind of hard to justify focusing on them in the near future when they're songs that will take many hours to complete and aren't super popular. I do have the beatmaps done and GP files set up, though, so if you think you can offer any help with the transcribing I can send the files your way.
  3. So, I've been away for a while. Sorry about that. Anyway, for CDLC creation purposes I'm probably going to transition to mostly (but not entirely) doing my own bass transcriptions for some bands I'd like to see. So, my apologies to guitarists who might like to play those songs, but most of the songs will have pretty interesting basslines and should be pretty enjoyable when played using emulated bass.
  4. https://github.com/kokolihapihvi/RockSniffer
  5. @@firekorn - Yeah, I don't think it technically does add sections, but I think that doesn't matter anymore (since ~Remastered). I think when they did the update they changed how sections/phrases work, so that phrases became the smallest selectable portions in riff repeater. I think this allowed them to fix silly things (like in The Thrill is Gone where the entire outro was one section but many phrases and so couldn't be broken into pieces for riff repeater) without having to actually change the file for it. But anyway, don't take my word for it. Try adding DD to a file with no sections (broken camera) or a file with long sections and no dynamic difficulty and see what happens. I'm pretty sure you'll find that you can use riff repeater on every phrase that DDC creates afterward. It's not as good as having the sections/phrases selected manually by an author that can figure out what will most likely trouble players, but it's a hell of a lot better than the broken crap it would be otherwise.
  6. @@alaslipknot - I believe that if you add dynamic difficulty to the song it will create new sections for you to select in riff repeater. I don't think that song has a ton of measures, so a phrase length of 2 should work fine and break everything into manageable pieces (though for most songs you'd probably want a longer phrase length).
  7. @@Lilumina - Thanks for the reminder. Been a while since I updated this (and similar threads), and it's hard to motivate yourself to keep up to date on something like this when it's not clear that anyone cares. Anyway, I still need to update a bunch of the numbers on this (this is easy to do for bands already on the list via the Artist search page), and likely add a few more bands, so let me know if there's anything else you think should be added!
  8. @@okewlie - I've heard of the band, but I don't think I've checked them out substantially. I'll see if there's something I like amongst the things that have been tabbed out so far... (none of the tabs I can find have bass, but hopefully that won't be a huge obstacle).
  9. I played Skyreach on bass, and it seemed like after the break the sync went off. Maybe off by an eighth note? It definitely didn't seem right to me. The first fill after the break also sounded like it should be an octave higher than charted, I think (there might have been other parts in the wrong octave, but can't remember off the top of my head).
  10. Not sure if this will solve it, but in the .ini file try setting "RealToneCableOnly=1" if it isn't that already. Otherwise I think Rocksmith will try to grab hold of all microphones when it launches (under the assumption you might want to use them for microphone mode or something).
  11. @@cozy1 - Since I've learned that the toolkit could handle the conversions I've always let the toolkit handle it. But it looks like that is the answer. Both songs have Terror in the titles (and thus the file names), and when the file name is changed, things work fine! Edit: Kind of funny since I was thinking it might be something in the metadata of the songs. I'd noticed that they were both Kreator songs, but clearly wasn't paying attention to the song titles or else we might have figured it out a bit faster!
  12. I don't think I've seen anyone specifically answer this question yet, but hyphens definitely occur in the lyrics of some ODLC (e.g. in My Generation for the stuttering parts).
  13. @@iminashi - Regarding the wait time when playing not equaling the amount of leading silence, I've noticed that in some customs I've made that if I start the beatmap fairly far into the song (which sometimes happens if there's a piano intro that's totally untabbed) that when playing it in game it will skip to just a few seconds before the beatmap starts. I haven't tried checking to see exactly how much of the "unmapped" audio gets skipped, though, so I can't tell you anything more specific regarding that.
  14. @@cozy1 - I've already tried remaking the .wem, and used different .oggs produced from different .mp3 files to make them, and still haven't had any success with it. As for using the 32 bit version instead, is there any particular file that I'd want to point the toolkit to, or would I need to reinstall it without installing the 64 bit component?
  15. I get this error when I try to unpack or add DD to the .psarc. The initial conversion using the toolkit (most recent beta) works fine, and the NDD version works fine in game. The download folder here has the .psarc and the EoF file I used to make it. Having this problem again also reminded me of a previous time I'd had this problem (also on a Kreator track, weirdly...) a few months back that I forgot to report. Files for that can be found here, including the original .ogg and the .wem produced by the toolkit if that helps figure out anything. Let me know if there's anything else I could provide that would help. Thanks!
  16. @@DiversantBivnev - Uh, you've lost me with the mention of "red" and "blue" notes, if those are referring to the strings in Rocksmith. This would be on the Orange and Green strings (in standard coloring. Not 100% sure how the colorblind setting changes things). Also, if it's indeed in B minor, then you could play at least the intro and outro (the stuff on Guitar 1 in the songsterr tab) in standard tuning pretty easily using the open B string and fretting notes on the e string (starting with the 3rd fret for the G4).
  17. Sounds to me like it might be the case that the tab is in a different key than the song. From what I can see online, though, even the artist has confirmed the tuning (though I think they use something slightly different in DADF#BD) and capo. Which I then guess makes me question the audio: Is there any chance that it was pitch shifted from the original somehow? You can download the TONART demo which can detect the key of the audio (and also whether it's tuned to something other than A440, which is another possibility), and see whether that's compatible with what's tabbed. Edit: With the audio in the file you included in the original post, I find that it's in B minor (and maybe around A444, though that difference shouldn't be too unbearable), with the first notes alternating between B3 and G4. The tab you posted seems to be in A#/Bb minor (the note that's the bass for the intro and outro riffs is four semi-tones up from F#, so F# -> G -> G# -> A - > A#). So, either the audio you have was shifted up a semi-tone somehow or the capo should be on the 5th fret.
  18. @@raynebc - So, I was working on a big song and some subparts of it for which I used the "Export time range" function and noticed a few flaws with how it works (I was using 4-17-2017 version at the time). The first one is pretty major, the others are less important and fairly easy to work around. 1) The exported EoF file seems to "forget" most of the track information. The tuning, number of strings, and arrangement type seem to reset to default for those tracks, and "Ignore tuning/capo" seems to get set to on (I haven't tested on a track with a capo to see if that gets reset or not, and I may have missed other variables that get changed). Tone changes (though defaults and stuff may need to be changed due to how the track is chopped up), track fret number, and all of the visible chart information (gems, FHP, sections, and so on.) seems to export as you'd expect, though. Anyway, the big annoyance is that for me, a six-string bass track that I have set on "Part Real_Bass_22" only remembers the lowest 4 strings when I export. I was able to work around this by cloning it to the bonus track and then exporting, then cloning the bonus track back to the bass part. 2) (This is more of an FYI than a bug, I guess) If you export from an off-beat time-stamp then it seems that EoF will shift the beats in the exported file so the first beat happens at the start of the song, which moves all of the beats so it basically becomes a note-synced and not beat-synced map. And if you don't start on the beginning of a measure, it shifts things so that the measures don't start at the appropriate place. So you need to be careful to use the exact timestamps of the beginning of a measure. But there might be a better way of doing the "padding" so that the beatsync stays in place. 3) Until the first measure that has a time signature explicitly defined (rather than no change), the exported file has the time signature undefined. I was able to get it to export the time signature as well by manually defining the time signature on the measures where I chose to start the exports (if they weren't already new time signatures). So again, this isn't a major deal, but there might be a better way to deal with it so that it doesn't have to be entered manually (whether in the original file or in the export). If you have trouble reproducing any of these I can send some of the files I was using along. On another topic, I updated the toolkit to the latest beta (the one released yesterday) and it wasn't accepting lyrics files (that I was producing with the 4-17-2017 release of EoF) that older versions of the toolkit did when I reverted. Anyone else having a problem with this, and know if it's an incompatibility issue or a problem with the toolkit?
  19. @@cozy1 - Fixed the picture link (I think I copied it before imgur was ready and got the gobbledygood rather than the actual link). Regarding the files in the folder, I added the album info to the EoF files and updated them, added the FLead_RS2.xml generated directly from that, and the ELead_RS2.xml from that after generating a .psarc with it using the toolkit. But I have to admit I don't really see why this would be particularly relevant, as the only difference between the EoF generated XMLs should have been the tuning. If this were the root of the problem, it seems to me like the toolkit should have rejected either neither or both, not accept one and reject the other.
  20. Not sure where the right place to post this is (so ccing @@cozy1 and @@Alex360, but I'm having problem with adding an arrangement to the toolkit for a Vektor song (where they record in high F standard). If I try to add an arrangement in F tuning, it fails to load, giving this result. However, for the E standard version (I make a pitch shifted version of Vektor songs to make them more accessible for most people) everything works, and the only change made between the two is changing the tuning in EoF from all +1 to all 0 (no transposing done). I also tested this on another song. XML loads fine in Eb, fails if I change the tuning to F (without transposing). Haven't tried editing the XML directly, so not sure if that will give a different result. I haven't tested yet either if this happens for most tunings including notes higher than 0 or maybe just this one. Anyway, this folder contains the relevant stuff (if anything more is needed, let me know and I'll add it). Latest EoF Hotfix and latest beta release of the toolkit are used.
  21. @@Cat With A Mustach - Grid lines display as yellow lines when you have the "Display Grid Lines" setting (Shift+G) turned on. So it sounds to me like you have that turned on with a grid snap setting of 1/4. That seems like it would explain everything you're seeing in the picture you posted (the yellow beat lines, the red ticks for notes that aren't on beat lines, the weird selectability of notes).
  22. @@iminashi - Would you expect this to be relevant for the toolkit develepors as well (regarding what can and can't be put into the Artist, Song title, and other similar slots)? If so, it might be worth bringing this to their attention.
  23. So, a few questions that might help diagnose the problem: 1) Exactly how does it crash? Does it freeze after tuning before the note highway shows up, or in some other way? If so, please describe how. 2) Are you creating the .wem by interacting directly with Wwise, or by using the toolkit to encode it from a .ogg or .wav? (The toolkit is safer since it's possible to enter the wrong settings in Wwise) 3) Do any of your notes have a ton of associated tech notes? (I once had a custom crash on a particular path because the GP file tried to simulate a wide vibrato with bends and the note had a bajillion tech notes. I can't remember exactly how it crashed, though. I remember someone else having a similar problem a few months ago. Maybe @@Brooklyn_Sounds?) And yeah, there might be other things that could cause problems. Conflicts with another custom's DLC key, arrangement number (extremely unlikely) or something like that, but it seems like things like those wouldn't affect everyone like it sounds the problems you're having do.
  24. @@raynebc - I remember doing something similar on one of my lyrics charts once (which I then fixed manually by finding something like that example and changing the later timestamp). I think it happened when I used x to go back a second (probably multiple times in a row) then pressed spacebar to place a new lyric while in the midst of previously placed lyrics due to losing my place in the song. Since then I've been careful to make sure that doesn't happen, so it was just the once for me.
  25. @@D4n - Without any more info, my guess based on what I've seen recently would be that you are using a recent version of EoF (since the abridged output was introduced) and a version of the toolkit that isn't up to date (amongst the betas. Forget exactly when it starts, but I think 2.8.2.0 versions deal with it correctly). To fix that you can either do 1) in EoF go to File -> Preferences -> Import/Export and uncheck "Abridged Rocksmith 2 export" 2) Update your toolkit to the latest beta (which seems pretty stable from the somewhat limited stuff I've done with it)
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy