Donate to keep JJazzLab free for all
Help translate JJazzLab
Contribute to improve this documentation
Like the videos and subscribe the YouTube channel
Record a video of yourself playing along with JJazzLab: videos will be put on the JJazzLab YouTube channel
Spread the word ! Talk and add links to www.jjazzlab.com on social networks, blogs, websites, etc.
If you're a developer, contribute code
On MacOS the Options are accessed via the main menu JJazzLab/Preferences.
Select all the chord symbols (right-click menu Select all the chord symbols)
Use the mouse-wheel, or right-click menu Transpose
It's easy if you use VirtualMidiSynth with the JJazzLab SoundFont:
in JJazzLab, save the backing tracks as a .mid file using menu File/Export to Midi file
open VirtualMIDISynth (right-click from the icon in the Windows system tray) and select the MIDI converter. Select the .mid file and generate the audio file.
You can also use a screen recorder software: some of them directly capture the output of the computer sound card and save it to a .mp3 file.
Use the FluidSynth -F option to generate a .wav file.
Use the VST host (Cubase, Reaper, etc.) capabilities to record the output of the VST instruments.
You need to reset all JJazzLab user settings (uninstall/re-install is not enough).
The simple way: menu Tools/Options/Advanced, button Reset all user settings.
The hard way: find the location of your Netbeans user dir in menu Help/About/System Information, exit JJazzLab, then delete the Netbeans user dir.
Yes. When first prompted by the JJazzLab installer, select "Install only for me", then select an installation directory where you have write access (in My Documents for example).
You need a good synthesizer connected to the output of JJazzLab. But what means good synthesizer when we talk about backing track generation? There are 3 main factors to take into account:
Individual sound quality (sounds for drums, bass, piano, ...)
Overall sound mix (how the different instruments fit together)
Effects (overall and per-instrument effects)
2 other factors can also impact the backing track rendering :
Drums XG compatibility: many Yamaha styles use specific XG drum/percussion sounds, e.g. jazz brushes, etc.
Correct Output Synth configuration in JJazzLab: Yamaha styles define a preferred instrument (e.g. synth bass) for each channel. If the Output Synth configuration is wrong, JJazzLab can't select the optimal instrument for each channel (e.g. use a piano sound instead of a synth bass).
Below are some typical configurations.
Java Internal Synth with default bank
Works out of the box. Considering the super small size of the default sound bank, the overall sound balance is quite good actually.
Difficult to find a well-balanced SoundFont, e.g. you get a nice piano but the bass sucks, etc. No individual effect per instrument. No XG compatibility.
Tested on many Yamaha styles. XG compatible, plus a few additional sounds and drum kits. There is an Output Synth configuration preset for a quick setup. No individual effect per instrument.
In GM mode the mix between individual sounds is usually very good out of the box. Each individual sound can have its own effects (e.g. distortion for guitar, etc.), this has a big impact on the overall rendering. If you find a Cakewalk instrument definition file (.ins) on the web for your synth, you can control it directly from JJazzLab.
Usually no GM compatibility. Need some effort for the initial set up : virtual Midi device + VST host, select each instrument sound, adjust mix from VST host, ... Each individual sound can have its own effects (e.g. distortion for guitar, etc.), this has a big impact on the overall rendering. Unless you created your own Cakewalk instrument definition file (.ins), you'll need to adjust your setup when you change rhythm.
Also, when a rhythm does not sound good, you'd be surprised how you can improve things just by trying different instruments and adjusting the mix (volume, effect, panoramic, velocity shift).
If you want to fully customize a backing track, you may simply export to a Midi file, then import the Midi file into your preferred DAW for advanced customization.
For additional information visit the Midi configuration pages.
JJazzLab can drive your keyboard to benefit from its optimized sounds. Connect your keyboard via Midi and go to the Output synth editor and apply the Yamaha Tyros preset. This preset is based on Tyros5 which is backwards compatible with previous Tyros models and most of the PSR keyboards.
In the JJazzLab installation directory, edit the file etc/jjazzlab.conf and add --fontsize 16 (16 or any other value, default is 11) in the default_options variable, you should end up with something like this:
default_options="--branding jjazzlab -J-Djjazzlab.version=2.2.0 -J-Dplugin.manager.check.new.plugins=true -J-Dplugin.manager.check.interval=EVERY_DAY --fontsize 16"
Restart JJazzLab. All menus should look bigger now.
This won't solve everything though, as some editor fonts do not depend on this setting. But you can tweak some of them using menu Tools/Options/Theme. Check each item in the list and if there is a font defined, change it to make it bigger. The user settings are automatically saved, so you need to do this only once.
You can pass one or more .sng file names on the command line, JJazzLab will open them upon start.
# Example on Win10 (x64)"C:\Program Files\JJazzLab\bin\jjazzlab64.exe" "C:\my dir\MySong.sng" "D:\AnotherSong.sng"
We need the following information in order to help you:
Provide the content of the log file
Describe what does not work as expected
Describe the sequence of actions that caused the issue
To get the log file content:
Right after the problem has occured, go to menu Tools/Options/Advanced
Click on Show Log Window
Copy & paste the full content of this window in your bug report
If for some reason the above does not work:
Go to menu Help/About and find the location of your Netbeans user dir.
For ex. on Windows
For ex. on Linux
Open an explorer, go to this directory then to the var/log subdirectory
The last log file is messages.log, the previous one is messages.log.1, the before previous is messages.log.2, etc.
Find the relevant log file and send it with your bug report