Skip to content
BS4U FretVector
AccountBuy $69.99
USER MANUAL

Manual

Every major FretVector feature explained.

USER MANUAL
COMPLETE OPERATING MANUAL

Step-by-step instructions for using FretVector.

Search the manual, open a chapter, follow the numbered procedure and use the matching video tutorial when you want to watch the same workflow.

01
Welcome to BS4U FretVectorUnderstand the purpose of FretVector and the order of the connected guitar workflow.

Before you start

  • Have the current FretVector desktop build installed.
  • Use a project folder where you can save songs, tabs and recordings.

Procedure

  1. Launch FretVector and open the Command Center.
  2. Read the workspace navigation from left to right: Import Song, Forge Analyze, Forge Stems, RockWheel, Tab Studio/FretSync/Guitar Coach, Tone Match, Jam Mode and Recording Studio.
  3. Treat the current project as the center of the workflow. Information such as song sections, chords, tab targets and practice notes should remain attached to that project.
  4. Use online features only when needed: account activation, the AI Guitar Assistant and YouTube Learning references require internet access.
  5. Save the project before changing songs or closing the application.
Expected result

You should understand where each major FretVector workspace fits and what information is meant to follow you from one workspace to the next.

Tips / common mistakes

  • Do not start by changing audio or tone settings randomly. Complete Audio Setup first.
  • Use the Tutorials page in the same order as the manual when learning the product.
Watch Related Tutorial 01
02
System Requirements and Recommended HardwareConfirm the Windows computer and guitar audio hardware are appropriate before installation.

Before you start

  • Review the current release notes for supported Windows versions.

Procedure

  1. Use a 64-bit Windows 10 or Windows 11 computer supported by the current release.
  2. Use at least a modern four-core CPU; six or more cores are recommended for larger projects, stem work and low-latency operation.
  3. Provide at least 8 GB RAM; 16 GB is recommended.
  4. Use 1920×1080 minimum display resolution; 2560×1440 or 4K gives more room for the complete workspace.
  5. For serious guitar work, connect a dedicated USB/Thunderbolt audio interface with a stable manufacturer ASIO driver.
  6. Keep enough free storage for the application, factory content, imported songs, stems and recorded WAV files.
Expected result

The computer should be ready to run the desktop application without relying on a browser-based front end.

Tips / common mistakes

  • Do not use a generic ASIO wrapper if the audio-interface manufacturer provides a native ASIO driver.
  • Keep the interface firmware and driver current before troubleshooting FretVector.
Watch Related Tutorial 02
03
Install FretVector on WindowsInstall the Windows x64 application and verify first launch.

Before you start

  • Download the current installer from My Account or the Download Center.
  • Close older FretVector installers before beginning.

Procedure

  1. Double-click the FretVector Windows x64 installer.
  2. Review the installer identity and version shown by Windows.
  3. Choose the default installation folder unless you have a specific reason to change it.
  4. Complete installation, then launch FretVector from the Start menu or desktop shortcut.
  5. Confirm the main FretVector window opens and the version displayed matches the release you downloaded.
Expected result

FretVector should open as a native Windows desktop application.

Tips / common mistakes

  • If Windows blocks the installer, verify you downloaded it from the official customer account/download page.
  • If first launch fails, note the exact error and use Support Center → Installation & Updates.
Watch Related Tutorial 02
04
First Launch and UpdatesComplete the first-run checks and know where to get later releases.

Before you start

  • FretVector must already be installed.

Procedure

  1. Launch FretVector and allow the main window to finish loading before clicking between workspaces.
  2. Confirm the displayed desktop version.
  3. Open the Download Center or My Account whenever a new release is announced.
  4. Read Release Notes before replacing a working build.
  5. Back up important project folders before installing a major update.
Expected result

You should know your installed version and have a safe update process.

Tips / common mistakes

  • Do not keep multiple old installers in the same working project folder.
  • If an update changes audio behavior, recheck the audio-device and buffer settings before changing tone presets.
Watch Related Tutorial 02
05
Account and License ActivationActivate a computer using the FretVector customer account or a license key.

Before you start

  • Internet access is required for online activation.
  • Use the same customer email/account used for purchase.

Procedure

  1. Open the FretVector activation/account area.
  2. For account activation, choose CONNECT FRETVECTOR ACCOUNT.
  3. When the browser opens, sign in using the purchasing account and approve the current computer.
  4. Return to FretVector and allow activation to complete.
  5. For a key-enabled build, copy the full FretVector license key, paste it into the license-key field and activate the current computer.
  6. If the device limit is reached, deactivate an old computer when possible or request a device reset through Support.
Expected result

The computer should show an active FretVector entitlement and licensed online features should become available.

Tips / common mistakes

  • Do not create a second customer account just to work around a device limit.
  • Keep the license key private. Revoked or rotated keys can deactivate computers that were activated with that key.
Watch Related Tutorial 03
06
Audio Interface and ASIO SetupSelect the correct guitar input and low-latency output path.

Before you start

  • Connect and power on the audio interface before launching FretVector.
  • Install the manufacturer ASIO driver when available.

Procedure

  1. Open the FretVector audio/setup area.
  2. Select the audio interface or its native ASIO driver.
  3. Choose the physical guitar input channel that matches the socket used on the interface, such as INPUT 1 or INPUT 2.
  4. Choose the correct stereo output pair feeding headphones, studio monitors or the mixer.
  5. Start with a buffer around 128 or 256 samples.
  6. Play the guitar and confirm the input meter responds before changing amp, cab or tone settings.
  7. If audio is stable, lower the buffer gradually only if you need less latency.
Expected result

Guitar input should reach FretVector and output should return through the intended interface outputs without excessive delay.

Tips / common mistakes

  • A very small buffer can cause clicks/dropouts; a very large buffer can feel delayed.
  • Use one sample rate consistently across FretVector and the interface driver.
Watch Related Tutorial 04
07
Input Calibration, Noise Suppression and Safe LevelsSet a clean input level before evaluating tone.

Before you start

  • Audio interface/ASIO setup must already be working.

Procedure

  1. Select the correct guitar input channel.
  2. Use the guitar and pickup you expect to practice or record with.
  3. Play your hardest normal attack and adjust the hardware input gain so peaks remain below clipping.
  4. Use NAM CALIBRATION or the available input-calibration control when the current build provides it.
  5. Enable NOISE SUPPRESSOR only as much as needed to control idle noise.
  6. Check sustained notes to make sure noise suppression is not cutting off the end of the note.
  7. Recheck the meter after changing guitars, active pickups, boosts or interface input modes.
Expected result

The signal should be strong, clean and free from digital clipping while normal sustain remains natural.

Tips / common mistakes

  • Do not fix clipping by turning down the final master after the input has already clipped.
  • Tone Match is much more reliable when the incoming guitar level is correct.
Watch Related Tutorial 05
08
Workspace and NavigationMove through FretVector without losing the active song context.

Before you start

  • Open or create a project.

Procedure

  1. Use the primary workspace navigation to open the tool you need.
  2. Watch the current project/song title so you know which project is active.
  3. When moving from Tab Studio to FretSync or Guitar Coach, confirm the same section/chord target is still active.
  4. Use the Command Center as the return point when you are unsure which stage of the workflow you are in.
  5. Save before switching to another project.
Expected result

You should be able to move between workspaces while keeping the same song/project context.

Tips / common mistakes

  • Avoid treating each tab as a separate application. The strength of FretVector is the connected handoff between tools.
Watch Related Tutorial 06
09
Create, Open and Save ProjectsUse projects to keep song analysis, tab, tone, practice and recording material together.

Before you start

  • Choose a folder with enough space for audio and recordings.

Procedure

  1. Create a new FretVector project and give it a clear song/project name.
  2. Save the project before doing detailed analysis or tab work.
  3. Keep imported source files and generated stems in the project structure when possible.
  4. Use Save after correcting chords, sections, tabs or practice notes.
  5. Use a separate project for a different song instead of overwriting the current one.
  6. Back up important project folders to another drive before major updates or moving computers.
Expected result

All major learning assets for a song should have a predictable home.

Tips / common mistakes

  • Include version or take notes in filenames when exporting recordings.
Watch Related Tutorial 07
10
Import SongBring a song or learning reference into the current project.

Before you start

  • Create and save a project first.

Procedure

  1. Open Import Song.
  2. Choose the supported local song/audio reference or the project source you want to learn.
  3. Confirm the correct file/title is attached to the active project.
  4. Play a short section to confirm the source opens correctly.
  5. Save the project before starting analysis.
Expected result

The project should now contain the source/reference used by analysis, learning and practice tools.

Tips / common mistakes

  • Keep an original copy of important source files outside the project as a backup.
Watch Related Tutorial 07
11
Forge Analyze: BPM, Key, Chords and SectionsCreate the first musical map of the song.

Before you start

  • Import a source and save the project.

Procedure

  1. Open Forge Analyze from the active project.
  2. Run the analysis process.
  3. Review the detected BPM and compare it with the musical feel of the song.
  4. Review the detected key and do not accept it blindly if the song modulates or uses borrowed chords.
  5. Inspect the chord timeline through the verse, chorus and other important sections.
  6. Review the detected song sections and rename/correct them when needed.
  7. Save the corrected song map.
Expected result

You should have a usable BPM/key/chord/section map that the other FretVector tools can reference.

Tips / common mistakes

  • Automatic analysis is a starting point. Correct questionable measures before building tab or practice plans around them.
Watch Related Tutorial 08
12
Correct Analysis ResultsFix chords and sections before they propagate through the rest of the project.

Before you start

  • Forge Analyze has already produced a song map.

Procedure

  1. Choose a section that sounds or looks incorrect.
  2. Play or inspect a small window around the questionable measure.
  3. Correct the chord label or section name using the available project editing control.
  4. Check the measures immediately before and after the correction for context.
  5. Save, then return to FretSync/Coach/Tab and confirm the corrected project information is used.
Expected result

Downstream tools should use the corrected musical map rather than the original detection.

Tips / common mistakes

  • Fix the map first; do not compensate for a wrong chord by forcing a wrong scale or fretboard target later.
Watch Related Tutorial 09
13
Forge StemsPrepare supported guitar-isolated or guitar-reduced material for practice.

Before you start

  • The current project should already contain the song reference.
  • Allow enough storage for generated audio files.

Procedure

  1. Open Forge Stems.
  2. Choose the supported separation goal, such as isolating guitar or creating a no-guitar practice reference.
  3. Run the installed stem engine and allow it to complete.
  4. Confirm the expected output files are present, such as guitar and no-guitar practice material when supported by the current build.
  5. Audition the outputs before practicing to make sure the separation is useful.
  6. Save the project after the stem references are connected.
Expected result

You should have practice material that makes it easier to hear or replace the original guitar part.

Tips / common mistakes

  • Stem separation is not perfect on every recording. Use the result as a practice tool, not as proof of the exact original multitrack.
Watch Related Tutorial 10
14
RockWheelUse the circular theory view to understand harmonic relationships.

Before you start

  • Confirm the project key/chords are reasonably accurate.

Procedure

  1. Open RockWheel from the active song.
  2. Set or confirm the current key.
  3. Locate the current chord and neighboring chords used by the progression.
  4. Use the wheel to see common harmonic relationships and likely movement.
  5. Compare the theory view with what you actually hear in the song.
  6. Send the musical understanding back into FretSync or your practice plan.
Expected result

You should understand why the current chords relate to the key and which note/scale targets are likely to be useful.

Tips / common mistakes

  • RockWheel explains relationships; it does not replace listening when a song uses modal mixture, chromatic movement or modulation.
Watch Related Tutorial 11
15
Tab Studio: Create and Edit Guitar TabBuild project-connected tablature for the part you are learning.

Before you start

  • Open the correct song project and section.

Procedure

  1. Open Tab Studio.
  2. Create a new tab sheet or select the current project tab.
  3. Work section by section rather than attempting the entire song at once.
  4. Enter string and fret information by bar/beat using the available editor controls.
  5. Use AUTO TRANSCRIBE only as an assistant when available; review the musical result before accepting it.
  6. Save the tab and confirm it remains connected to the current song/project.
Expected result

The project should contain editable guitar tab that can be used by the learning workflow.

Tips / common mistakes

  • Keep tab readable. Prefer practical positions and clear rhythm over filling every possible note.
Watch Related Tutorial 13
16
Tab Playback, Rewind, Print and ExportPractice the tab with transport controls and export it when needed.

Before you start

  • A tab sheet exists in the active project.

Procedure

  1. Use PLAY/PAUSE to follow the tab with the project transport.
  2. Use REWIND to return to the beginning or target section.
  3. Watch the current bar, section and chord context while practicing.
  4. Use FRETSYNC to send the current tab target to the fretboard view.
  5. Use GUITAR COACH to create practice steps for the difficult tab section.
  6. Use ASK AI ABOUT TAB for a specific fingering/harmony question when online AI is available.
  7. Use PRINT TAB, EXPORT TAB or EXPORT MUSICXML when you need a printable or compatible interchange version.
Expected result

You should be able to practice, hand off and export the same tab without re-entering the part in another tool.

Tips / common mistakes

  • MusicXML compatibility depends on the receiving notation software. Always verify exported notation.
Watch Related Tutorial 14
17
FretSyncMap the current musical target onto playable fretboard positions.

Before you start

  • Use the correct project chord, scale, tab or section target.

Procedure

  1. Open FretSync from the current song/tab context.
  2. Confirm the current chord or scale target.
  3. Review the highlighted fretboard positions.
  4. Choose one practical neck position for the current phrase instead of trying to use every highlighted note.
  5. Practice moving between the target positions slowly and cleanly.
  6. Return to Tab Studio or Guitar Coach without changing projects.
Expected result

You should be able to see where the current harmony or scale lies on the guitar neck.

Tips / common mistakes

  • Use fretboard targets as a map, then listen for phrasing and articulation.
Watch Related Tutorial 16
18
Guitar CoachTurn the current song and problem areas into a structured practice session.

Before you start

  • Have a clear current project and, ideally, a defined section or tab target.

Procedure

  1. Open Guitar Coach from the active project.
  2. Choose the song or difficult section you want to improve.
  3. Start below full tempo when accuracy is not stable.
  4. Separate the job into rhythm, notes, transitions, articulation and then tone.
  5. Use repeated clean passes as the reason to increase tempo.
  6. Save practice notes or project changes before leaving the session.
Expected result

You should have a repeatable plan instead of randomly replaying the whole song.

Tips / common mistakes

  • Five clean slow repetitions are more useful than one lucky full-speed pass.
Watch Related Tutorial 17
19
AI Guitar AssistantAsk useful project-aware questions about harmony, tab, practice and tone.

Before you start

  • Activate FretVector and confirm internet access.

Procedure

  1. Open the AI Guitar Assistant from the current project.
  2. Ask a specific question that includes the section, chord, tab measure or tone problem.
  3. When asking about tab, use ASK AI ABOUT TAB so the current tab context is included when supported.
  4. When asking about tone, describe the real guitar, pickup and interface instead of requesting a vague famous tone.
  5. Read the answer as guidance and play/test the suggestion.
  6. Do not assume the AI has heard audio unless the application explicitly supplied that audio information.
Expected result

AI responses should be more useful because they refer to the active FretVector project rather than a generic guitar question.

Tips / common mistakes

  • Ask for one change at a time when troubleshooting tone or practice problems.
Watch Related Tutorial 29
20
YouTube LearningUse a YouTube video as an online learning reference while keeping the FretVector workflow connected.

Before you start

  • Internet access is required.
  • Use a legal public/authorized YouTube video as the reference.

Procedure

  1. Open YouTube Learning.
  2. Paste or open the YouTube video URL using the reference field.
  3. Save the reference with the current project.
  4. Use SAVE FAVORITE when you want the reference easy to find again.
  5. Use OPEN IN BROWSER when you need the full YouTube page.
  6. Hand the learning target to FretSync, Guitar Coach, Tone Match, Jam Mode or Recording Studio as appropriate.
Expected result

The project should remember the YouTube reference while the actual learning work continues in FretVector.

Tips / common mistakes

  • FretVector is not a YouTube downloader. Keep marketing and customer instructions clear about that distinction.
Watch Related Tutorial 27
21
Tone MatchBuild a usable guitar sound for the current part.

Before you start

  • Input calibration should already be correct.
  • Use the guitar/pickup you will actually play.

Procedure

  1. Open Tone Match from the current project.
  2. Start from a clean input and a sensible factory tone or neutral starting point.
  3. Choose or describe the target sound/style.
  4. Adjust gain before EQ; excessive gain can hide articulation and add noise.
  5. Refine bass, mids, treble/presence and cab/IR choices while comparing at similar loudness.
  6. Add ambience/effects only after the core amp/cab tone works.
  7. Carry the finished tone into Jam Mode and Recording Studio.
Expected result

The tone should fit the part at realistic playing level and remain stable when recorded.

Tips / common mistakes

  • Louder almost always sounds more exciting; level-match before deciding one tone is better.
Watch Related Tutorial 20
22
Factory TonesUse the included tone categories as starting points instead of final rules.

Before you start

  • Calibrate the input first.

Procedure

  1. Open the factory tone/preset list.
  2. Audition StudioClean for a clean reference.
  3. Use TexasBlues when you want edge-of-breakup/blues response.
  4. Use BritishCrunch for more driven rhythm work.
  5. Use SingingLead for sustained lead work, ModernRock or HighGain for heavier sounds, and WarmAmbient for spacious clean/edge tones when available.
  6. Adjust the preset to your guitar/pickup and monitor level instead of assuming the preset is exact for every rig.
Expected result

You should have a useful starting tone category that can be refined in Tone Match.

Tips / common mistakes

  • A preset designed with humbuckers may need gain/EQ changes for single coils and vice versa.
Watch Related Tutorial 21
23
Jam ModePractice a section, progression or full song without losing project context.

Before you start

  • The song map should be saved and the guitar input/tone should be working.

Procedure

  1. Open Jam Mode from the active project.
  2. Choose the section, progression or complete-song target.
  3. Set a practical practice tempo.
  4. Enable count-in or metronome when timing needs work.
  5. Practice the part while watching the current chord/section context.
  6. Return to Guitar Coach or Tab Studio when a specific problem needs isolated work.
Expected result

You should be able to practice in context without rebuilding the song information.

Tips / common mistakes

  • Slow the difficult section down instead of repeatedly failing at full speed.
Watch Related Tutorial 22
24
Count-In and MetronomeUse timing tools to make practice and recording more repeatable.

Before you start

  • Confirm the project tempo is correct or choose a deliberate practice tempo.

Procedure

  1. Enable the metronome and set a level that is audible without masking the guitar.
  2. Use count-in before recording or difficult entries so your first note is prepared.
  3. Practice subdivisions at slow tempo if the riff rushes or drags.
  4. Increase tempo in small steps only after timing is stable.
  5. Disable the click for a final musical check only after the part holds time without it.
Expected result

Entries and internal timing should become more consistent.

Tips / common mistakes

  • If the detected BPM is wrong, correct the song map before relying on the metronome.
Watch Related Tutorial 23
25
Recording StudioPrepare the input, arm the correct path and capture a test before recording the full take.

Before you start

  • Audio/ASIO, input calibration and the desired tone must already work.

Procedure

  1. Open Recording Studio.
  2. Select/confirm the guitar input and monitoring path.
  3. Arm the appropriate guitar track or recording path.
  4. Enable dry and wet recording when you want both safety and processed signals.
  5. Use count-in/metronome if needed.
  6. Record a short test, stop, play it back and verify there is no clipping, wrong input or excessive noise.
  7. Only then record the full section or song take.
Expected result

The recording setup should be verified before committing to a long take.

Tips / common mistakes

  • Always test playback as well as record input; a meter moving does not prove the recorded file is correct.
Watch Related Tutorial 24
26
Dry and Wet RecordingCapture an unprocessed safety track and the processed guitar sound when available.

Before you start

  • Recording Studio must already be configured.

Procedure

  1. Enable the dry/unprocessed capture path.
  2. Enable the wet/processed Tone Match/amp path.
  3. Confirm both meters respond to the same performance.
  4. Record a short test.
  5. Solo/check the dry track to make sure it is clean and not accidentally processed.
  6. Check the wet track for the intended tone and level.
  7. Record the performance only after both paths pass the test.
Expected result

You should have a safety DI-style track for later processing plus the tone used during the performance.

Tips / common mistakes

  • Do not clip the dry track. A clean safety track is most valuable when it preserves headroom.
Watch Related Tutorial 24
27
Takes and Punch In/OutKeep good performances and repair only the section that needs another pass.

Before you start

  • A base recording already exists.

Procedure

  1. Record multiple takes without deleting the best previous take.
  2. Label or organize takes so you can compare them later.
  3. Choose a safe punch-in point before the mistake and a punch-out point after it.
  4. Leave enough lead-in for natural timing and pick attack.
  5. Record the replacement section.
  6. Compare the new punch/take at matched playback level and choose the most musical performance.
Expected result

You can improve a recording without sacrificing a good earlier take.

Tips / common mistakes

  • Avoid punching exactly on a noisy chord attack when a slightly earlier clean entry is possible.
Watch Related Tutorial 25
28
Export Finished AudioCreate a final file and verify it outside FretVector.

Before you start

  • Choose the final take/mix.

Procedure

  1. Open the Recording Studio export controls.
  2. Choose WAV when you want an uncompressed master.
  3. Choose a clear filename containing the song/project and version.
  4. Export to a known folder.
  5. Play the exported file in another audio player to confirm the file opens, the beginning/end are present and the level is appropriate.
  6. Keep the FretVector project after export in case you need another version.
Expected result

You should have a verified finished audio file plus the original project.

Tips / common mistakes

  • Do not judge export success only by the progress bar—always play the finished file.
Watch Related Tutorial 26
29
Complete Song-to-Play WorkflowUse the complete product in the intended order.

Before you start

  • Audio and activation should already be working.

Procedure

  1. Create/save a project and Import Song.
  2. Run Forge Analyze and correct BPM, key, chords and sections.
  3. Use Forge Stems if isolation/reduction will help practice.
  4. Use RockWheel to understand the harmony.
  5. Build/check tab in Tab Studio.
  6. Use FretSync to choose fretboard targets and Guitar Coach to structure practice.
  7. Use AI only for focused project-aware questions.
  8. Build the sound in Tone Match.
  9. Practice in Jam Mode.
  10. Open Recording Studio, capture dry + wet where useful, manage takes and export the final performance.
Expected result

The entire learning cycle should remain connected inside one project.

Tips / common mistakes

  • If a later step seems wrong, go back and correct the earliest bad information instead of compensating downstream.
Watch Related Tutorial 31
30
Troubleshooting, Support, Logs and BackupsCollect useful information and use the correct support path.

Before you start

  • Do not uninstall or delete projects before collecting the error details.

Procedure

  1. Write down the exact FretVector version and Windows version.
  2. For audio problems, record the interface model, ASIO driver name, sample rate, buffer size and selected input/output.
  3. For licensing problems, note whether you used account activation or a license key and whether the device limit is reached.
  4. For AI/YouTube problems, confirm normal internet access and check whether other online FretVector services work.
  5. Take a screenshot of the error or wrong screen when possible.
  6. Describe the last action that worked and the first action that failed.
  7. Back up the project folder before reinstalling or making major changes.
  8. Submit the structured Support Center form with the information above.
Expected result

Support should receive enough information to reproduce or isolate the issue without repeated basic questions.

Tips / common mistakes

  • Do not send passwords, full payment-card numbers or private API keys in a support request.
Watch Related Tutorial 36
Need help with BS4U FretVector? Support Center  |  support@bs4ufretvector.com