# \[WS\] Qobuz (Available in 24 countries)
**URL:** https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860
**Category:** Web Sources Scripts
**Created:** [May 2, 2023, 4:31pm UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860 "2023-05-02T16:31:46Z")
**Posts on this page:** 10
**Page:** 2
### Author:  [@GMK](https://community.mp3tag.de/u/GMK)
#### Post date: [March 27, 2026, 2:47am UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860/24 "2026-03-27T02:47:35Z")
I’ll do some investigating. Thanks for letting me know.
---
### Author:  [@GMK](https://community.mp3tag.de/u/GMK)
#### Post date: [April 8, 2026, 1:43pm UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860/25 "2026-04-08T13:43:00Z")
Latest version has been uploaded, including some additional fields in the search index.
---
### Author:  [@aspnxl](https://community.mp3tag.de/u/aspnxl)
#### Post date: [July 2, 2026, 1:32pm UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860/26 "2026-07-02T13:32:22Z")
Hi. Does anyone know what this error means? It happens with every search.
---
### Author:  [@yorickausyps](https://community.mp3tag.de/u/yorickausyps)
#### Post date: [July 2, 2026, 7:55pm UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860/27 "2026-07-02T19:55:52Z")
This probably has it's cause in the **greedy** first part `.*` of the regexp `".*"albums":"({.*?})".*"`. In this form it searches the **last** appearance of the string`"albums"`. But this string appears only once and near to the beginning of the data, so that means we can search for the first one. For this to appear we should change the first part of the regexp to a **lazy** `.*?` one.
If you can edit the file `Qobuz.inc` yourself, the line 28 of it should read:
`RegExpReplace ".*?\"albums\":\"({.*?})\".*" "\[\1\]" `
If you can't edit the file yourself please let us know.
Are you using a Mac? Under windows I can't duplicate this issue, and AFAIK the regexp implementations are different between mp3tag for Mac and windows.
---
### Author:  [@GMK](https://community.mp3tag.de/u/GMK)
#### Post date: [July 2, 2026, 9:04pm UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860/28 "2026-07-02T21:04:06Z")
@yorickausyps, thanks for the suggestion. That worked for me, anyway.
@aspnxl, the newest version is available in the first post.
---
### Author:  [@GMK](https://community.mp3tag.de/u/GMK)
#### Post date: [July 2, 2026, 9:06pm UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860/29 "2026-07-02T21:06:33Z")
Although, I can't guarantee this will fix it on Mac. Not sure what the differences are in implementations. @Florian?
---
### Author:  [@aspnxl](https://community.mp3tag.de/u/aspnxl)
#### Post date: [July 3, 2026, 2:18am UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860/30 "2026-07-03T02:18:09Z")
Yes I am macOS. I downloaded the latest version but I am still getting the same error. I checked that the line @yorickausyps mentioned in the Qobuz.inc file matched what he suggested.
---
### Author:  [@yorickausyps](https://community.mp3tag.de/u/yorickausyps)
#### Post date: [July 3, 2026, 5:21am UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860/31 "2026-07-03T05:21:08Z")
My next wild guess is that the curly braces need to be quoted by a backslash. The [ICU regular expression doks](https://unicode-org.github.io/icu/userguide/strings/regexp.html) state: Characters that must be quoted to be treated as literals are \* ? + [ ( ) { } ^ $ | \ .
That means the line 28 should read:
`RegExpReplace ".*?\"albums\":\"(\{.*?\})\".*" "\[\1\]" `
Same in line 36
`RegExpReplace "\"(.*?)\"\:(\{\"id\"\:\"\1\",)" "\2" `
I hope this helps.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [July 3, 2026, 8:02am UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860/32 "2026-07-03T08:02:04Z")
Here is a fixed version that should also work on macOS. The main issue was using `\1` instead of `$1` in the replacement string. While `\1` is the standard syntax for backreferences in regex patterns, replacement syntax varies between regex flavors, and many engines expect `$1` instead.
[Qobuz.inc.zip](https://community.mp3tag.de/uploads/short-url/fy5WvD86JLVKv0MjD4HCBFjS4Dj.zip) (3.0 KB)
* * *
For your reference, here are the relevant parts from the [ICU Documentation](https://unicode-org.github.io/icu/userguide/strings/regexp.html):
| Character | Description |
| --- | --- |
| `\n` | Back Reference. Match whatever the nth capturing group matched. n must be a number \> 1 and \< total number of capture groups in the pattern. |
And in [Find and Replace](https://unicode-org.github.io/icu/userguide/strings/regexp.html#find-and-replace):
| Character | Descriptions |
| --- | --- |
| `$n` | The text of capture group ‘n’ will be substituted for `$n`. n must be \>= 0 and not greater than the number of capture groups. An unescaped $ in replacement text that is not followed by a capture group specification, either a number or name, is an error. |
| `\` | Treat the following character as a literal, suppressing any special meaning. Backslash escaping in substitution text is only required for `$` and `\`, but may be used on any other character without bad effects. |
---
### Author:  [@aspnxl](https://community.mp3tag.de/u/aspnxl)
#### Post date: [July 3, 2026, 3:05pm UTC](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860/33 "2026-07-03T15:05:58Z")
Awesome. Thanks for helping out @Florian @GMK @yorickausyps ! 🙂
[Previous page](https://community.mp3tag.de/t/ws-qobuz-available-in-24-countries/60860.md?page=1)