Hi There is no more development activity here in this repo since more than 2 years, and another repository has been created to continue TuxGuitar development. So, please go directly to this new repo if you need support. Note that the version 1.6.3 you are using has beed released by this new repo. Considering your specific problem, we have recently identified (and hopefully fixed) a very similar issue. So I recommend: - to download latest pre-release from the new repo, and to check if your problem...
I have a percussion track in solo mode composed in tuxguitar with more than 100 compasses. But when it's exported do audio file, the content does not reproduces the entire song, just the first 2min and 18seconds. Menu: File > Export > Audio File File Encoding: PCM_SIGNED File Type: WAVE TuxGuitarVersion: tuxguitar-1.6.3-linux-swt-amd64 How can I export the entire track?
Hi. All development activities have stopped here in sourceforge since about 2 years. Another repository has been created to continue TuxGuitar development, and new versions have been released there. So, I suggest creating a feature request in this new repository.
Currently played note highlight improvement
Bonjour. Le développement de TuxGuitar ici sur SourceForge s'est arrêté il y a bientôt 2 ans avec la version 1.5.6. Pour trouver du support, il faut maintenant (à partir de 1.6.0) aller sur le nouveau dépôt : https://github.com/helge17/tuxguitar/ Pour demander de l'aide ouvrir une "discussion", de préférence en anglais ;) En ce qui concerne les doigtés (de la main droite je suppose), non il n'est pas possible de les indiquer.
J'utilise la version 1.6 de tux guitar. Il me semblait que l'on pouvait indiquer les doigtés mais je ne retrouve pas cette option ? Merci de votre aide
Hi There is no more activity going on here in sourceforge, so if you have questions/problems with TuxGuitar I suggest to go to the new repo in github: https://github.com/helge17/tuxguitar. By the way, the latest available version (1.6.1) has made significant progress about triplets representation. A triplet is a "3 for 2" pattern, so if you want 3 notes in 1 beat, first select your beat and define its duration to 1/8th with edit toolbar or menu. Then, place cursor on the first 1/8th and click on...
PLEASE HELP I am completely lost. How do I make triplets (3 equal notes to 1 beat) in tux guitar?
Bit late to this, but how do you make triplets (3 equal notes to one beat) on Tux I am so lost someone please help.
Should be fixed in latest version on https://github.com/helge17/tuxguitar/releases
Hi feature is available at https://github.com/helge17/tuxguitar/releases, since there is no more development going on here. From pre-release 2023-10-26 you can configure shortcuts for "zoom in/out" actions. Note: it's also possible to zoom in/out with (Ctrl+mouse wheel) or (Ctrl+2 fingers touchpad)
Requesting shortcuts for zoom in (+) and zoom out (-)
Oh yes, I also imagine it should be "Angel" and not "Angle", definitely less poetic XD but it's no me the author of "geometric" horror. Thanks a lot anyway, I think I'll save the Guitar Pro files in TuxGuitar format if I want to work on lyrics. Thanks again and have a good day
OK, I looked at the example file. From what I understand, the .gp3 format (quite old) does not handle tracks with lyrics. There is some textual information coded in the file, but attached to specific beats. See measure 6: first beat of first track has a textual attribute "Angle came down from" (should have been "Angel" I guess!). So, for the example you mentioned above it seems the limitation comes from the .gp3 format, and TuxGuitar's behavior seems normal to me... Do you also have the same problem...
A fix has been implemented at https://github.com/helge17/tuxguitar, Fix is available in releases from pre-release 2023-10-11. Thank you very much for that very clear and precise description of the issue. Thanks to the detailed procedure and attached poc files I could reproduce the issue, and also test the fix. Note: this vulnerability corresponds to CVE-2020-14940
Hi I updated to version 1.6.0 last week, from version 1.5.6, but the problem persists. On guitar pro files (any version) saving the lyrics sometimes works and sometimes it doesn't, while the .tg format doesn't cause problems. They are files that I downloaded from gtptabs.com. For instance, the file linked below doesn't allow me to save the lyrics. http://gtptabs.com/tabs/8/hendrix-jimi/angel.html
Hi Just 2 questions, because I can't reproduce this issue: 1. Which version of TuxGuitar are you using, on which platform? 2. Can you reproduce this issue? I mean: do you have a file for which this issue can be systematically reproduced (or at least often)? If so, could you provide such a file so I can investigate?
back on my steps I noticed that sometimes, I mean for SOME FILES, LYRICS are NOT RECORDED Can you tell me why or when this happens? thanks
A new version is now available at https://github.com/helge17/tuxguitar/releases, where we try to continue maintenance and development of TuxGuitar, since all activities have stopped here (see this post). Since pre-release 2023-09-25-snapshot the display of triolets has been improved, it is now possible to write measures as described in this thread. See attached screenshot :
A new version is now available at https://github.com/helge17/tuxguitar/releases, where we try to continue maintenance and development of TuxGuitar, since all activities have stopped here (see this post). Since pre-release 2023-09-25-snapshot the display of triolets has been improved, it is now possible to write measures as described in this thread. See attached screenshot :
Version 1.6.0 is now available at https://github.com/helge17/tuxguitar/releases/
It took me some time but I finally found a way: 1) create a 1/4 measure bar 2) divide the measure in 2 eighteenth 3) select the first eighteenth 4) add the triplet 5) this adds 1/4: [8 8 8]. Then it's super easy to create your bar, even if with this workaround you divide the single bar in multiple ones... It kinda sucks having to do all of this, I'm used to MuseScore, where you can just press Ctrl+3 and the selected note is divided in a triplet of the same overall duration.
Awesome - I want to contribute. I will see you over in the Github repo :)
Okokok, made it works. Cheeers! :)
TuxGuitar itself does not require any account, it's a standalone app running on your machine. You can use it to create tabs, edit, import, export, .... An updated version is available there: https://github.com/helge17/tuxguitar/releases. Then if you want to export them to songsterr you need a songsterr account, but it's completely independent from TuxGuitar.
Since the repository here on SourceForge seems to be orphaned, we try to continue developing TuxGuitar on this Github repository, yes.
Helge, First thanks for stewarding this. Second, to be clear: does this mean development will be happening at github.com/helge17/tuxguitar going forward?
Thxs! So i don't need an acount to create tabs, export them and use them with songsterr?
TG community is no more maintained (similarly, historical TG's official web site also disappeared). Globally it seems all maintenance/development activities are discontinued here in SF since quite a while. As you can see in this discussion, a new fork has emerged a few months ago to continue maintenance and dev. However there is no plan (at least in short term) to restore TG Community feature.
Greets! Just installed TG on my mx linux, wantin to create tabs for songsterr, but the welcome wizard links to TG comunity and creatin an acount just lead me to random and dubious sites... Any help?
Julian seems to be no longer active in this repository and did not respond to our request a few months ago. Since the new repository https://github.com/helge17/tuxguitar has made a lot of progress and the code is now in a quite consistent state, we decided to release a new "official" version of TuxGuitar: 1.6.0. The changes since version 1.5.6 are: Add click & drag selection Copy/paste and repeat selection Apply actions and effects to selection Fix percussion channel issues in GP importer Improve...
You can try the version on this repo: https://github.com/helge17/tuxguitar Installable builds (pre-releases) are available here, including mobile version. With this version I can open .tg and .gp files. Practically, development of TuxGuitar seems discontinued here.
Mobile Version for Android Not Reading .tg Files
As you can see there is no more development activity in this repo since quite a long time. Practically it seems discontinued. A new fork has emerged a few months ago to continue TuxGuitar maintenance and development: https://github.com/helge17/tuxguitar. If you want to have a try, installable builds are available there for different platforms. I just initiated a discussion there about this feature request. It looks feasible, but I would appreciate if you can give some more precise details about how...
As you can see there is no more development activity in this repo since quite a long time. Practically it seems discontinued. A new fork has emerged a few months ago to continue TuxGuitar maintenance and development: https://github.com/helge17/tuxguitar. If you want to have a try, installable builds are available there for different platforms. I just initiated a discussion there about this feature request. It looks feasible, but I would appreciate if you can give some more precise details about how...
Save tuning preferences
True, it would be very useful and practical if it were added
Display note names in score
Don't hesitate to provide feedback, especially if you think of useful adjustment/improvement
Don't hesitate to provide feedback, especially if you think of usefull adjustment/improvement
That's great, might give it a chance. Thanks for doing the hard work of improving someone else's code.
Hello. It seems the same problem also mentioned in this ticket. If so, then I have implemented a fix in this fork, because it seems there is no more development activity going on here. You can find installable versions there
Feature is implemented in this fork, since it seems there is no more development going on here. Installable builds are available for Linux, windows, macOs and Android. Feature is available through menu "File/Set custom template"
Hello Helmar, Yes, it definately needs a new file format in order to keep the current format compatibility. It's probably better to wait for a new format. When this time comes, please tell me and I would gladly give you my help to integrate this patch :) Thanks, Kevin
Hi Helmar, You're welcome :) Yes I've noticed some quirks while playing with the repeat (adding it, removing it, remove bars, etc ...). I think it needs a general fix around the way repeats are managed. Cheers, Kevin
After having a look in the code, in fact there is already a way to do this, but it's definitely more a hack than a real solution. You can overwrite file tuxguitar_installation_path/share/templates/template-default.tg with a file containing 1 empty track with your bass, and it will open a copy of this file each time you launch TuxGuitar. Also when closing the last opened song, or with menu File/New. But not with 'Ctrl-N' shortcut. Note that it will impact all users on the machine. I'm currently working...
Hi yes this could be a workaround to start TuxGuitar in a more convinient way Best regards Le 28/05/2023 à 21:48, guiv a écrit : Hi. It seems to me a possible solution could be to configure which file to open by default when TuxGuitar starts. Not 100% sure but I would bet it could be easy to implement. This way you could just create once an empty song with 1 track for your bass, and TuxGuitar would automatically open it each time it starts. Do you think it would make sense? (note: no idea how to...
Hi. I would also consider this a bug: one can reasonably expect "pause" and "stop" buttons to behave differently. I've implemented a fix in this fork, since it seems there is no more dev activity here. Installable builds are available for Linux, Windows, MacOs and Android. Note: "pause" feature was already working fine in Android..
Hi. It seems to me a possible solution could be to configure which file to open by default when TuxGuitar starts. Not 100% sure but I would bet it could be easy to implement. This way you could just create once an empty song with 1 track for your bass, and TuxGuitar would automatically open it each time it starts. Do you think it would make sense? (note: no idea how to handle printer parameters)
Hi An implementation of that feature is available in this fork, since there is not much dev activity here. Binary builds (beta) are available for Linux, Windows, macOs and android there
It might be linked to this keyboard issue: digits typed with a combination or keys are not interpreted as digits by TuxGuitar (I tested with 1.5.6). E.g. on an AZERTY keyboard, typing "1" on first row of keys is interpreted by TuxGuitar as "shift+&" which is different from "1" typed with the numpad. A fix is available here, since there is not much dev activity here
The fork https://github.com/helge17/tuxguitar stores the tunings in the file /opt/tuxguitar/share/tunings/tunings.xml. The file already contains ukulele tunings, but you can also add different tunings manually.
In fact I don't have your Git experience, I really am an amateur. So I started by comparing the code (quite tough, as you said the 2 versions are very different), and now I am backporting the code manually. Not very practical, but it's not possible to just merge: - some modifications done in 2.0 are only compatible with SWT, and I had to modify the code to try to keep compatibility with JFX (feasible). Not yet considered Qt (see here why) - some modifications for "click & drag select", and "copy-paste"...
Thanks for the patch! I tested it on the fork https://github.com/helge17/tuxguitar. It worked quite well, but there are a few problems: - I am currently trying to keep the fork's file format compatible with TuxGuitar 1.5.6. 1.5.6 is not able to open .TG files with the pick strokes. - The fork shows more details about the bending (commit e982d11). This view clashes with the pick strokes. - When I open the .GP4/5 files exported from TuxGuitar with Guitar Pro 6, some strokes are missing. - The Android...
Great, glad to hear it :)
Thanks a lot for the patch! I have added it to my repository at https://github.com/helge17/tuxguitar .
Thanks! Added to https://github.com/helge17/tuxguitar .
In fact I don't have your Git experience, I really am an amateur. So I started by comparing the code (quite tough, as you said the 2 versions are very different), and now I am backporting the code manually. Not very practical, but it's not possible to just merge: - some modifications done in 2.0 are only compatible with SWT, and I had to modify the code to try to keep compatibility with JFX (seems feasible). Not yet considered Qt (see here why) - some modifications for "click & drag select", and...
I think at this point the two projects are so different that we just need to pick one and move on, so I guess I'll join you with backporting features from v2.0 to 1.x. v2.0 has a better git history to work with, so I guess it makes sense. @guiv I've been trying to use git bisect to find the working version with note selection, so I can help. I struggled with compiling, because there's different versions of SWT and Java used. Because of this, I've wrote a little script and guide to help us with compiling...
Thank you Simon for these details. Whatever we do, we can only succeed if the community follows. 1.x seems to me a smoother path for a transition, easier to follow for most users. These days new users are logging in 1.x branch, filing issues and feature requests. So, I suggest we try to take benefit from this momentum, and start to address these users' requests. Some of them can be addressed by backporting 2.0 features. Note: currently looking at the awesome "click & drag select" feature, from comments...
Thanks a lot for the patch! I have added it to my repository at https://github.com/helge17/tuxguitar.
Thanks a lot for the patch! I have added it to my repository at https://github.com/helge17/tuxguitar.
Thanks a lot for the patch! I have added it to my repository at https://github.com/helge17/tuxguitar. TuxGuitar handles repeats and endings a little differently than Guitar Pro, so it may be necessary to manually change the notation to get the intended behavior, but this is not due to the patch itself.
Yes, the commits without any comments in 1.x git log all say they're akdmia's. See below for the version history and commits. I was looking through the git log manually for any changes to TGVersion.java, then I found this really useful git command to just show me all the git commits and the changes to that file. git log --follow -p -- TuxGuitar-lib/src/org/herac/tuxguitar/util/TGVersion.java Note: v1.x and 2.0 last shared commit was on Mar 24 2019. For the v1.x fork Dates the version changed: v1.5.6...
Yes, the commits without any comments in 1.x git log all say they're akdmia's. See below for the version history and commits. I was looking through the git log manually for any changes to TGVersion.java, then I found this really useful git command to just show me all the git commits and the changes to that file. git log --follow -p -- TuxGuitar-lib/src/org/herac/tuxguitar/util/TGVersion.java Note: v1.x and 2.0 last shared commit was on Mar 24 2019. For the v1.x fork Dates the version changed: v1.5.6...
Thank you Simon for this detailed analysis of the history. Just 2 questions: - do the commits with no comment in 1.x correspond to akdmia's commits? - do you know where the 1.5.6 release is in these 2 branches?
I think I'm a bit torn between the versions. Personally, I'd vote for v2.0, because I can see the improvements, both in the GUI and from the git commits. 1.x has some missing git comments :(. That being said, the midi playback didn't work on 2.0 for me(ubuntu), but does in 1.x. I compiled both from the helge17 forks. I'm not too sure how hard it would be to backport the changes from 2.0, because there has been a lot of work on it(see below). I do however like the idea of TuxGuitar working on android,...
I think I'm a bit torn between the versions. Personally, I'd vote for v2.0, because I can see the improvements, both in the GUI and from the git commits. 1.x has some missing git comments :(. That being said, the midi playback didn't work on 2.0 for me(ubuntu), but does in 1.x. I compiled both from the helge17 forks. I'm not too sure how hard it would be to backport the changes from 2.0, because there has been a lot of work on it(see below). I do however like the idea of TuxGuitar working on android,...
A fix is available here: https://github.com/helge17/tuxguitar/releases
The binaries on https://github.com/helge17/tuxguitar/releases now contain all the Chinese translations from this patch. Thanks for your help!
Thanks a lot for the patch! I have added it to my repository slightly modified. You can download the patched binaries from https://github.com/helge17/tuxguitar/releases.
I guess it was the original motivation for this post: re-establish contact with Julian, yet without success. This is also a reason why I preferred to contribute to the "1.x" fork: as mentioned by Helmar, should Julian resume his work on TG one day, then it would be a lot easier to backport modifications implemented in direct continuity with 1.5.6.
The last SWT version with 32-bit support was 4.9 from 2018 (https://archive.eclipse.org/eclipse/downloads/drops4/). Many Linux distributions have completely discontinued 32-bit support or have dropped the 32-bit SWT version. In practice, it would still be possible to provide 32-bit binaries, but to save resources for more important things, I decided to remove 32-bit support. However, since we are trying to keep the file format of our new version compatible with 1.5.6, you can continue to use Julian's...
why remove 32bit? too hard to build for with new features? should keep em, i have old machines that i use in the jam room for this kinda thing. not to say it's a popular option but i'd keep as much compatibility as we can... if we can
@akdmia
can anyone get a hold of julian?
Hello all. Nice to see the TuxGuitar community still lives! Todo List so far: Vote on a TuxGuitar version to fork. I tried to understand the story behind this "2.0beta thing": helge17 repo is a fork of pterodactylus42 repo, which forked pcarmona79 repo, where it is stated "This repository was uploaded from a copy of the deleted https://github.com/cyclopsian/tuxguitar" A bit difficult to establish the link with the historical branch here in SF. The last reference I found is here, and it's almost 4...
Hello Simon, glad to hear you are willing to contribute! As you can see from the discussion above, I "voted" for the 1.x version and created a new repository at https://github.com/helge17/tuxguitar. I also try to integrate patches from the 2.0beta version (https://github.com/helge17/tuxguitar-2.0beta). Under "Releases" you can find binary packages for both versions. You can also start discussions and open issues for bugs or TODOs. 2.0beta has a lot of GUI improvements, you might want to have a look...
Hello, I'd like to help out with this a little as well :). I love TuxGuitar, but it's become a bit of a nuisance to keep up with where to grab the 'most recent version' from, because of the split in development. The way I use TuxGuitar is to learn a song and to play along with it at increasing speeds. Every time I use it, it feels clunky to practice a small section of a song, and I think "I should just write the code for this". I'd like to work on being able to select a section, set a loop, and easily...
Hello, I'd like to help out with this a little as well :). I love TuxGuitar, but it's become a bit of a nuisance to keep up with where to grab the 'most recent version' from, because of the split in development. The way I use TuxGuitar is to learn a song and to play along with it at increasing speeds. Every time I use it, it feels clunky to practice a small section of a song, and I think "I should just write the code for this". I'd like to work on being able to select a section, set a loop, and easily...
Same problem also, azerty keyboard, linux, version rebuilt from source. It seems clearly linked to the keyboard. I changed settings manually, tried to associate "0" key to "fret 0", and when typing the key it displays "shift+à" instead of "0" From source code: in the swt version, key events are identified by a UIKeyCombination object = a list of keys. So, two different key combinations corresponding to the same character are considered different events. Edit: issue is also present in the jfx version....
Same problem also, azerty keyboard, linux, version rebuilt from source. It seems clearly linked to the keyboard. I changed settings manually, tried to associate "0" key to "fret 0", and when typing the key it displays "shift+à" instead of "0" From source code: in the swt version, key events are identified by a UIKeyCombination object = a list of keys. So, two different key combinations corresponding to the same character are considered different events. Edit: issue is also present in the jfx version....
I could finally manage the horizontal spacing, when "compact mode" display is not enabled. Feedback welcome! Not much activity here, so you can find the code here, and installable builds here
I could finally manage the horizontal spacing, when "compact mode" display is not enabled. Feedback welcome! Not much activity here, so you can find the code here, and installable builds here
Same problem also, azerty keyboard, linux, version rebuilt from source. It seems clearly linked to the keyboard. I changed settings manually, tried to associate "0" key to "fret 0", and when typing the key it displays "shift+à" instead of "0" From source code: iIn the swt version, key events are identified by a UIKeyCombination object = a list of keys with "+" as a separator. So, two different key combinations corresponding to the same character are considered different events. Edit: issue is also...
Same problem also, azerty keyboard, linux, version rebuilt from source. It seems clearly linked to the keyboard. I changed settings manually, tried to associate "0" key to "fret 0", and when typing the key it displays "shift+à" instead of "0" Edit: issue is also present in the jfx version. Association of this key displays "Shift+undefined"
Same problem also, azerty keyboard, linux, version rebuilt from source. It seems clearly linked to the keyboard. I changed settings manually, tried to associate "0" key to "fret 0", and when typing the key it displays "shift+à" instead of "0"
I am having the same issue on linux (flatpak release). It seems you have to enter numbers using the numpad, using numbers on the normal row does not work. I am using AZERTY keyboard which might also be related.
Yep, got it. In fact there are 2 problems in the code for the plugins-related menu items in "Tools" menu. First, their labels are hardcoded (see example of batch converter above). Second, labels are only set when menu is created and are not refreshed if language is changed in the settings. A fix is available here.
"Action" indicates that the pop-up menu only displays the "File format batch converter" sub project, but in the "Java" file, it is not referenced in the language file. Translating these means that the project needs to be rebuilt, and modifying the language file alone is not possible.
I was also wondering why, in my French version, toolbar items "Tools/File format batch converter" and "Tools/Guitar Tuner" were not translated... Looking at the source code of TG1.5.6, in TGConverterPlugin.java I can see the name is hardcoded: protected String getItemName() { return "File format batch converter"; } In which version did you see this reference to action.file-format-batch-converter?
Sorry, I couldn't find these titles either. I forgot to delete them. But All sub projects have been translated. "file.new-song.template-1= and - file.new-song.template-2=" in the "tuxguitar-1.5.6 \share templates\templates. xml" file. -action.file-format-batch-converter in the "TGConverterPlugin.java" file; - action.guitar-tuner in the "TGTunerPlugin.java" file; - Share with the Community in the "TGShareSongExporter.java" file; - -action.jack-console in the "JackConsolePlugin.java" file. Because...
Sorry, I couldn't find these titles either. I forgot to delete them. But All sub projects have been translated. "file.new-song.template-1= and - file.new-song.template-2=" in the "tuxguitar-1.5.6 \share templates\templates. xml" file. -action.file-format-batch-converter in the "TGConverterPlugin.java" file; - action.guitar-tuner in the "TGTunerPlugin.java" file; - Share with the Community in the "TGShareSongExporter.java" file; - -action.jack-console in the "JackConsolePlugin.java" file. Because...
Sorry, have overlooked that. Now I have also added the translations of the plugins. I could not find the following names in the sources, so I did not include them: - action.file-format-batch-converter= - action.guitar-tuner= - action.jack-console= - browser.factory.fs.community-files= - file.new-song.template-1= - file.new-song.template-2= - tools.file-format-batch-converter= - tools.Instrument-tuner= - tools.jack-console-title= Not sure where they come from, maybe from older TuxGuitar versions?
Yet the slide effects are only displayed on a 'per-measure' basis, so the behavior you can see is the expected one. It might be a little tricky to display slides split over two measures, especially if this correspond to an end of line.
Hello, apart from the "share\templates\templates.xml" file, I have merged all the Chinese translations of other plugins into the "messages_ zh.properties" file.
Thanks! Added your translation to my repository https://github.com/helge17/tuxguitar If you would like to also translate some other dialogues (for plugins etc.) just search for the files named messages.properties in the TuxGuitar source tree.
Thanks! Added your translation to my repository https://github.com/helge17/tuxguitar
Possibility to have a parameter file to fix parameters
由于旧版汉语翻译作者已经很久没更新,新版本增加了比较多项目,我自己做了翻译,但是有3个句子,因为我找不到原文位置所以还是英文的,如果有那位大佬肯指点,或者有发现错误的请告诉我,谢谢! 邮箱:auase@outlook.com 网站:www.auase.com (Since the author of the old version of the Chinese translation has not been updated for a long time, the new version has added more items. I did the translation myself, but there are 3 sentences, because I can’t find the location of the original text, so it is still in English. If there is a big guy who is willing to point out , or if you find any mistakes, please tell...