search

rncbc / qjackctl

QjackCtl - JACK Audio Connection Kit Qt GUI Interface
https://qjackctl.sourceforge.io
GNU General Public License v2.0
185 stars 41 forks source link

Issue with QjackCtl 0.5.2 #38

Closed sub26nico closed 6 years ago

sub26nico commented 6 years ago

I have issue with QjackCtl with preset having () in the name. Ardour doesn't have sound output if the name of preset in QjackCtl is (default), it's working if I erase the () in the preset name, it wors with 'default'. Reaper (native linux version) give error message too (if thre is () ). it was working fine with QjackCtl 5.0.0.

rncbc commented 6 years ago

are you with the French (fr) translation? this last one was indeed with a translation mistake (a string that should have never been translated).

if that's the case, to work around that please run v0.5.2 as follows:

LANG=C qjackctl

the fr translation has been fixed on git head already.

thanks

sub26nico commented 6 years ago

My system is translated in French (LibraZiK) but the name of preset (default) or default are in english. I have the same issue with the french name (défaut). défaut runs fine. Strange thing, it was working fine after the update with Ardour, but Reaper gives error message. Since I changed the name of preset ( name without () ), Ardour can't give sound in the output (the vu-meters showes sounds). I'll test with the command you gives above.

sub26nico commented 6 years ago

with QjackCtl in English, Ardour and Reaper works fine. Strange thing, I read error with reaper and Qjack in english forums (https://forum.cockos.com/showpost.php?p=1994484&postcount=523), and it was the same here. Maybe this reaper user have non english system). @rncbc : do you want I close here ?

rncbc commented 6 years ago

thanks. closing now.

trebmuh commented 6 years ago

@rncbc I added 2 translator's comment in the French translation file. See #39 . Then, it's not going to be forgotten that those strings need to NOT be translated.

If there is a way to add it to all the translation files, I'd suggest to do so.

rdoursenaud commented 1 year ago

@rncbc

are you with the French (fr) translation? this last one was indeed with a translation mistake (a string that should have never been translated).

If the string shall not be translated, the proper fix is to mark it as such in the Designer file by setting the string tag notr attribute to true. This way, it won't even appear in the translation file and fix the issue for all languages. Yes, I'm deflecting the blame :p