Jump to content

Search the Community

Showing results for tags 'sync'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CustomsForge
    • News & Announcements
    • Ignition4 Search
  • General
    • Rocksmith Remastered
    • Rocksmith Championship
    • Music Discussion
    • Off-Topic
  • Rocksmith CDLC
    • Workshop
    • Learning Guitar & Bass
  • Rocksmith 2014 Remastered Tools
    • CustomsForge Song Manager
    • Editor on Fire
    • DLC Builder
    • RSPlaylist / RockSniffer
    • Mods & Projects

Collections

  • Ignition4

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Member Title


Website URL


Steam


Twitter


Twitch


Discord


Location


Interests


Guitar


Bass


Favorite Bands


Rocksmith

Found 8 results

  1. Hi ! I was trying to make my first CDLC on the bass part for the song Reach on by George Duke and after the intro the tab is going completely out of sync but when i play it with Guitar pro it syncs with the song how can i manage to avoid that problem ? Otherwise is there a way to select multiple notes in EOF ? Thanks in advance for your responses ! :)
  2. This is my basic workflow for making the song. This is also good approach for quick check if it's worth to do the song (checking out the tab). Disclaimer: This is not the only one approach but it's the best practice for minimizing manual frustrating error-prone work and it allows you to actually go back and fix anything in the sync, tab, sections or phrases easily. (You can use this tutorial even if you later decide to maintain chart completely in EoF.) Note for tabbing: I have found GP/GPA combo to be great for creating tabs from scratch - I figure out the BPM, sync the measures and progressively fill them up with notes (hearing GP tab immediately or slowing down the GPA playback and playing along the song is great help). Repeat signs: I didn't have any issues in GPA so you can do this later, but you might need to replace repeats to avoid EoF import issues and I don't recommend to import GP3 format. Without repeats you also get more control over partitioning phrases/sections. Replacing repeats is trivial in TuxGuitar once you get hold of it: 1. remove start and end sign (note the number at the end sign = N) 2. copy those measures (all tracks, you want to copy all instruments) 3. go to the next measure and let TuxGuitar paste it in new measure N times (otherwise it will be overwritten) 4. if it is alternate ending, you need to do one additional paste at the last (alternate ending) measure Synchronization 1. You should have correct GP tab prepared and also MP3 file, it will be hard to sync if notes in tab are not in place. Make sure you have at least one empty measure at the start (otherwise you will need to do the sync again later). 2. Install Go PlayAlong and load GP and MP3 files into it. You might want to add few seconds of silence first if it starts too soon, you can use Audacity and its Generate -> Silence function. It is possible to add it later too and set EoF project Delay value but it always keeps bugging you to convert it to empty measures which you shouldn't do if you follow this approach. 3. Place some links on notes and peaks of the waveform, preferably only on measure boundaries, don't try to fix the tab by overriding the timing (especially if you are trying to sync both guitar and bass at once). Do this manually for the whole song to ensure high precision. Hardest point is the start, you should make sure you get it right, doing high frequency (guitar or loud drum beats) is easiest, but you need to check if both arrangements are in sync once you're done. Use zoom and slow down the playback to make this easier. If you place first link after the actual first note of arrangements you care about, go back and place a link before them too to avoid possible EoF import issue (measures up to first link will be shifted forward/backward depending on where the first measure fits). discussion 4. Check if the result is correct for all relevant arrangements. 5. Export. Licensed GPA is needed to do this but it's absolutely essential, you can calculate BPMs manually but there will be a lot of imprecisions this way and I don't recommend it. (If export fails, check artist/songbook name and remove any space in front of it.) 6. Now you can create EoF project and import XML file with Guitar Pro import. If you don't need to change timing you will never have to do this again, you can clear sections/phrases and notes and import them directly from GP file if you fix anything. 7. Now you are ready to save and create a package with toolkit. Be sure to save package template for future rebuilds (each arrangement has unique IDs which identify score and progress in Rocksmith). There is also fairly recent feature of slowing down playback in EoF which is a great help for checking note sync but everything should be the same as in GPA. Phrases and sections (Make sure you use EoF r1300 and later to prevent phrase import issues.) Note that you can manage section and phrase names directly in GP tab (section names and text markers), I use alternate EoF setting for importing phrases from section names and sections from text markers on first beat of measure. If you intend to split phrases and sections differently or name them differently you need to keep separate GP tabs and EoF project for each arrangement (I recommend it, having correctly labeled phrases and noguitar sections for both bass and guitar adds a lot to the chart quality). Sections (text markers) need to be on the first beat of measure and phrase name (measure marker) is required at the same position. Section is the part that is selectable in riff repeater. You can name phrases whatever you want but you should use the same name for this particular phrase throughout the tab, this will instruct Rocksmith to advance them at once. Section names are restricted to these Rocksmith names (use only the word in quotes, EoF accepts both forms but the first one is canonical): {"intro", "Intro"}, {"outro", "Outro"}, {"verse", "Verse"}, {"chorus", "Chorus"}, {"bridge", "Bridge"}, {"solo", "Solo"}, {"ambient", "Ambient"}, {"breakdown", "Breakdown"}, {"interlude", "Interlude"}, {"prechorus", "Pre Chorus"}, {"transition", "Transition"}, {"postchorus", "Post Chorus"}, {"hook", "Hook"}, {"riff", "Riff"}, {"fadein", "Fade In"}, {"fadeout", "Fade Out"}, {"buildup", "Buildup"}, {"preverse", "Pre Verse"}, {"modverse", "Modulated Verse"}, {"postvs", "Post Verse"}, {"variation", "Variation"}, {"modchorus", "Modulated Chorus"}, {"head", "Head"}, {"modbridge", "Modulated Bridge"}, {"melody", "Melody"}, {"postbrdg", "Post Bridge"}, {"prebrdg", "Pre Bridge"}, {"vamp", "Vamp"}, {"noguitar", "No Guitar"}, {"silence", "Silence"}"noguitar" section is used for silent parts and is excluded from Riff Repeater. If only one arrangement is silent then you should make a copy of GP tab and EoF project and do different version of section naming. If you want to see purple bars in the song chart you need to have more than one difficulty. I wouldn't do that manually in EoF, you can use either DDC or I use a script to do exact copy so I have 2 identical levels. Technique import (My notes about how EOF imports various techniques and known issues, if you know about some, let me know.) Should work (let me know if you notice issues): - Note/chord - Palm mute - Sustain - Accent - Slide to note/chord - Dead note/chord - Hammer on/pull off - Slap/pop - Vibrato (only single frequency, probably only visual effect) - Tremolo (see import issues) - Harmonic (& harmonic pinch?) - Tap - Bend - Chord notes techniques should be mostly supported Some issues: - Tremolo - EOF project needs to be set to remove difficulty limitations - Slide to no destination exports as 1 fret slide - Trill - according to @@raynebc it needs to be converted to hammer-on/pull-offs (discussion) - Arpeggio chord outline can be added if you add chord notes as ghost notes and then manually set Arpeggio mark with Ctrl+Shift+G in EoF at each arpeggio appearance Unsupported import to EOF: - Unpitched slides (no TuxGuitar support?) - Chord slides limited to same offset? Unsupported techniques in RS2 (ignored): - Ghost note (effect) - Grace note (effect) - Dotted (lenghtened duration) - Staccato (shortened duration) - swing/shuffle or Triplet? (duration) Additional tips I recommend starting off with official song and DLC tones (in manifest files), choose one that fits and improve it. You need to use toolkit to unpack game and DLC psarc files to access them and then import them to your toolkit template (you can import your new or modified tones from RS profile too). Some tones of interest: - punk distortion: Versus Them - 6AM Salvation - clean ska guitar: Weezer - Say It Ain't So - Filter Clean - tight punk bass: Clash - London Calling - deep bluesy bass: Albert King - Born Under A Bad Sign - dubby bass: Clash - Guns Of Brixton - reverb clean guitar: Disonaur - Space Ostrich - jazz clean: (couldn't find any official so I customized one for Le Chat) TuxGuitar is a free replacement for Guitar Pro, also supports PTB tabs. Latest SVN version can read GPX (GP6) but you need to build it yourself (run "mvn clean package" in "build-scripts/$PLATFORM" depending on your target operating system). (Update: here's a ZIP with Windows version https://www.dropbox.com/s/zcwzmptqxgrp9om/tuxguitar-1.3-SNAPSHOT-windows-x86.r1104.zip - requires Java)
  3. Apologies in advance if these things are already possible and I'm just too stupid to have found where the options are, but; Go Play Along is fairly convenient for getting a quick sync and importing into EOF - but GPA has an annoying habit of making mid measure anchored beats. Is there any way to easily select all beats that are not the first beat of a measure and un-anchor them? Alternatively - an option during GPA import to not have ANY of the beats as auto anchored? In the correct place / bpm changes are ok, but the anchors are not strictly necessary (please correct me if I'm wrong). Also; GPA has another habit of syncing to the spikes on a track(as shown on the GPA waveform - it doesn't display the same way as the waveform within EOF), not the start of the note/beat - meaning the entire sync can potentially be off by 60-80 ms. Is there any way to select an entire track once imported (with or without anchors) and move everything by X amount? I've been getting around it by adding a leading silence and not moving the notes/beats to match with it but being able to select everything and drag would be much more convenient. Dropbox link to an example of GPA sync files - https://www.dropbox.com/sh/3z4kb2vc70udoqy/AAADnEYc5tC9htI7KIWuHfCVa?dl=0
  4. Hey everyone! I've been wanting to create a tutorial like this for some time, and I finally got around to it :) Hopefully some of you will find it helpful, and feel free to leave any questions or comments you may have: For further insights into using the spectrogram, you can refer to @@albatross213 's post here (sorry for the numeric dyslexia when I mentioned your name in the video). Also, would anyone like to see any other EoF- based tutorials? If so, which topics would be the most helpful to you? Let me know here
  5. This will be spread across multiple posts for reasons of organization. For a while a lot of the posts will just be placeholders, but I'll eventually fill things out. This will be pretty comprehensive, and I hope touch on some things that aren't addressed in other tutorials, and also bring together a lot of accumulated knowledge that's now scattered across this site. It will also be in mostly text and pictures, simply because it's easier to update text and pictures than video, and probably less time-consuming overall for both me and you. I'll probably be skipping some of the more basic things that are contained in other tutorials. For example, the basics of what programs you'll need and how to arrange them are covered in @@Darjusz's tutorial. Some of the later material is outdated because of updates to the software from some of our hardworking developers (for example, you don't need to work directly with Wwise anymore, but can instead put guitar.ogg into the toolkit and it will produce the .wem from that), but it provides an excellent introduction to most of the tools you'll be using. Also, don't expect every CDLC of mine to perfectly implement everything that I mention here. Some things I've learned since making certain CDLC and haven't updated yet, others I might have decided weren't worth the time for the song, and so on and so forth. We do this as a hobby, so we can't really expect everything to make everything perfect. But if we find a flaw, we should notify the creator so it can be fixed - fixing this will not only improve the quality of that CDLC, but also likely will help improve subsequent output from that charter. I guess I'll start with my philosophy on making CDLC. First thing is to do what I can to make sure things are accurate. My sense of rhythm is pretty good, so it's pretty easy for me to tell if something is off rhythm or not once synced. My sense of pitch is pretty bad, but even so I can usually tell if something (like in a guitar solo) goes significantly higher or lower than the tab and the melody is completely off. If I see things like this that are off, I then have to decide whether to scrap the project, fix it myself, or release as is and try to get someone from the community to help with fixing it. Next is to make learning the song more approachable - you shouldn't (intentionally or unintentionally) make it harder to learn a song. There's a lot to do here, some of which may get noticed (RR sections and DD), but much of which probably won't (Fret Hand Positions/FHP, chord fingerings) but can still be very important, especially for songs that beginners will play or will prove popular. The rest of this guide will be spread throughout several replies to this post. The topics will include (they will be presented in this order, but probably won't be written in this order): The basics of spectrogram view (not started)Syncing a song in EoF (not started)Preparing tabs for import (in progress)Sectioning, and adding DD (Mostly done)Fixing up slides (Mostly done, but needs examples and images)Miscellaneous technique stuff (in progress)Fixing up FHP (Mostly done, but needs examples and images)Lyrics (mostly done)Miscellaneous Toolkit stuff (In progress)I'm almost certainly not the foremost expert in all of these subjects on here, so if anyone wants to assist in the writing on some of these subjects, or just present an alternative perspective on one, all help would be greatly appreciated. Also, if there are any other topics you think should be included, let me know! It's a little hard to judge the quality of a DLC without playing it, but here's a rough guide of what I'd consider important for a good DLC that I'll come back to often and enjoy playing. The exact order can depend on the content of the DLC (techniques, chords, arpeggios, etc.), so don't take the order too seriously. The essentials: Accurate tab, with good fretboard logicBeat synced, not note syncedHigh quality audioUseful RR sections. If there's something that's both new and hard (it could be a chord progression, a new idea in a solo, a fill, etc.), it should be towards the beginning of a section, and I shouldn't have to wait too long to practice it each time around.Well done slides. Too many bad slides (which often means slides left alone after import, as a lot of tabs manage slides incorrectly) can ruin the experience of an otherwise good custom. Pay attention to slide timing, whether it should be legato or not, whether it's a slide in or a slide out, and whether the slide should be pitched or unpitched.Tones. At the very least, have a tone. Even if you can't come up with tones that fit every part of the song exactly, it's better to have something (that people can switch away from if they choose) than to break the tone engine of everyone who ever plays your DLC.Of great utility (sometimes): FHP. This is especially important for tapped sections, or places where the index finger is rooted and one reaches over more than 4 frets (quite common in solos given the size of frets higher up the fretboard, but also possible lower down). If these aren't done manually it can create a lot of visual clutter and be quite confusing, which does not help anyone trying to learn these (generally tough) passages.Chord fingerings. It can sometimes be a bit of a chore to enter them all, but it's really frustrating trying to learn a new chord while actually playing the song (especially if its chord pane is partially obscured by other chord panes), and if you don't put in the chord fingering (and maybe a chord name), it won't appear in the chord book.Suitable scroll speed. The RSToolkit default of 2.0 is often way too slow. Most official DLC have a scroll speed of 1.3, and some are faster. More technical songs often benefit from higher scroll speeds, and rhythm and lead often benefit from faster scroll speeds than bass (so that chord panes get space out appropriately). It's down here because if people dislike your scroll speed, it's one of the easier changes to make.DD. It's also reasonably simple for the user to add if the charter doesn't, but more time consuming. I don't consider it essential since I'd usually rather play the full riff at a slow speed than a simplified version at full speed so I don't use it very much unless I absolutely can't sightread something. But I know many others will disagree with me and consider it essential.Good use of tech notes and techniques. Accurate bends can add a lot of nuance to a solo. Good use of handshapes and arpeggios can make it much easier to understand complicated passages. Using the wrong techniques in some places can be confusing (for example, harmonics shouldn't have slides, bends, or vibratos, but pinch harmonics can have these techniques. Also palm muting vs. fret hand muting, as sometimes tabbers get these wrong, or just leave out palm mutes).Nice to have: Alternative/bonus arrangements. If there are multiple guitarists that trade off solos, it might be nice to have arrangements for each individual guitarist in addition to a lead path that has all solos. If a custom uses a 5-string bass, it is nice to have an arrangement for 4-string bass so that most people can play it.Lyrics. And please, if you're going to go to the effort of making lyrics, make sure they're synced appropriately and have line breaks at natural places (I've seen a lot of CDLC with the entire song as one line, which means the game makes line breaks once enough text has accumulated, which only rarely coincides with actual lines).Most of the other posts will expand on the topics introduced in this post. Thanks for reading!
  6. Hey guys, Been enjoying my stay here and enjoying all the great customs, however I've reached a point where I want to tackle my own. I have watched the tutorials by Squid and PC Plum, and read the tutorial on how to create cdlcs by Darjusz. I have EOF, the RStoolkit, and have been using tablature and guitar pro for years. So.. I started with some very basic songs, set EOF up exactly as told with most recent hotfix, imported song, double and triple checked BPM including the second method that Squid uses via. Songbpm.com I imported tabs ~ trying Modest Mouse's 'Dramamine' bass line and the Arcade Fire's 'Rebellion (Lies)' bass line for practice. I can not get the notes to sync with the music. I have used the bpm as said on the tab file. It all seems extremely out of sync. What am I doing wrong? Also, I registered for Wwise and it keeps saying it can't finish installing. ?? Any tips, experience with this, links, etc. would be helpful. I don't want to give up before I've even begun. :( ~lilstrats.
  7. Hi, Just wondering if you might consider adding GPX for the import option in EoF I have been working on some songs that have double dotted rests and notes but when exporting from GP6 to GP5 format I loose the double dots which throws things out of sync here and there when I import the file into EoF. Or can anyone offer a workaround that I can use to substitute the double dots within GP6 so everything is in the right place when exported to GP5 format?
  8. Hi, I'm currently working on some songs in EOF. They seems perfect in sync in EOF but when I test it in RS they the first note is good, but after a while the notes become more and more out of sync. How is this possible when its perfect in EOF? Anyone an idea please? Thanks edit: I see now that I placed this in the wrong topic, can i still change 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