Ardour 8.11 released

Blog
#21

The macOS and Linux packages were all updated within a couple of days. We did not do a new release because there were no code changes required to fix the issue, it was just a packaging problem. Unless you obtained 8.11 during the first 2-3 days of its release, the problem is already solved.

See earlier in this thread: Ardour 8.11 released - #16 by paul

#22

I just downloaded the new release this mornig but the issue remains
If you think I can send you a log file or something else to understand what happens, do ask.

But for now that’s okay. Hope the problem will miraculously disappear in next releases :slight_smile:

thanks

#23

Have you made sure that Edit → Preferences → Appearance/Translations has “Use translations” checked?

Also make sure you have some files in your Ardour8.app/Contents/Resources/locale/fr_FR(or similar)/LC_MESSAGES folder

#24

The problem was known to be fixed. It is more likely you have a more mundane issue, like the one Peder described above. Ardour does not translate by default.

#25

Yes “use translation” is checked :wink:
But I don’t have any “locale” folder!

    /Applications/Ardour8.app/Contents/Resources
    ├── ArdourMono.ttf
    ├── ArdourSans.ttf
    ├── InfoPlist.strings
    ├── appIcon.icns
    ├── ardour.keys
    ├── ardour.menus
    ├── clearlooks.rc
    ├── default_ui_config
    ├── export
    ├── fonts.conf
    ├── icons
    ├── mcp
    ├── media
    ├── midi_maps
    ├── mixer_settings
    ├── osc
    ├── patchfiles
    ├── plugin_metadata
    ├── rdf
    ├── resources
    ├── scripts
    ├── system_config
    ├── templates
    ├── themes
    ├── typeArdour.icns
    └── web_surfaces
#26

I just downloaded the 8.11 Demo for Mac and I can’t get the translations to work either.
The time stamp on the files and foldes says Feb 6 04:52.

If I read the osx build script correctly there should have been a Resorces/locale folder with all the language subfolders in it, but as pierx pointed out it’s nowhere to be found.

Maybe the demo doesn’t contain any translation files but I suppose pierx is using the paid-for version.

#27

Indeed it is AWOL. if you read the osx build script more closely you’ll notice that the find command which looks or translations used GNU extensions (not available on apple’s BSD find), so translation files were not copied.

Ardour - Log file: build_log.txt shows this…
find: *.mo: unknown primary or operator

now fixed since Fix translation bundling, use BSD*find syntax · Ardour/ardour@125fd41 · GitHub

2 Likes
#28

Nice.

So there should be a a new macOS package in a few days, I take it?