ISCA Archive Interspeech 2024 Sessions Search Website Booklet
  ISCA Archive Sessions Search Website Booklet
×

Click on column names to sort.

Searching uses the 'and' of terms e.g. Smith Interspeech matches all papers by Smith in any Interspeech. The order of terms is not significant.

Use double quotes for exact phrasal matches e.g. "acoustic features".

Case is ignored.

Diacritics are optional e.g. lefevre also matches lefèvre (but not vice versa).

It can be useful to turn off spell-checking for the search box in your browser preferences.

If you prefer to scroll rather than page, increase the number in the show entries dropdown.

top

Interspeech 2024

Kos, Greece
1-5 September 2024

Chairs: Itshak Lapidot, Sharon Gannot
doi: 10.21437/Interspeech.2024
ISSN: 2958-1796

# Re‑upload with metadata gsutil cp gs://src-bucket/file.txt - | \ gsutil -h "x-goog-meta-$CUSTOM" cp - gs://dest-bucket/file.txt Add a metadata filter to your sync profile:

Posted on April 17, 2026 • By ChatGPT TL;DR | Symptom | “Metadata transfer not supported” error (or similar) appears when you try to copy/move a file or object and the underlying service can’t preserve its extra attributes (timestamps, ACLs, tags, etc.). | |---|---| | Common culprits | Cloud storage SDKs (AWS S3, Azure Blob, Google Cloud Storage), on‑premise backup tools, FTP/SFTP clients, container image registries, data‑lake migration utilities. | | Why it happens | The source and destination have different metadata models, or the transfer protocol simply doesn’t expose a “metadata‑copy” operation. | | Quick fix | Explicitly tell the tool to skip metadata, or map it to a supported format; upgrade to a newer client/SDK; use a staging area that understands both sides. | | Long‑term fix | Align your data‑governance strategy with the capabilities of the storage platform, and automate metadata handling in your pipelines. | 1️⃣ What Is “Metadata” Anyway? When you hear “metadata” in the context of files, objects, or containers, think of the data about the data : metadata xfer not supported

# Extract user metadata (may be empty) CUSTOM=$(jq -r '.metadata' src-meta.json) # Re‑upload with metadata gsutil cp gs://src-bucket/file

Search papers
Article

Xfer Not Supported | Metadata

# Re‑upload with metadata gsutil cp gs://src-bucket/file.txt - | \ gsutil -h "x-goog-meta-$CUSTOM" cp - gs://dest-bucket/file.txt Add a metadata filter to your sync profile:

Posted on April 17, 2026 • By ChatGPT TL;DR | Symptom | “Metadata transfer not supported” error (or similar) appears when you try to copy/move a file or object and the underlying service can’t preserve its extra attributes (timestamps, ACLs, tags, etc.). | |---|---| | Common culprits | Cloud storage SDKs (AWS S3, Azure Blob, Google Cloud Storage), on‑premise backup tools, FTP/SFTP clients, container image registries, data‑lake migration utilities. | | Why it happens | The source and destination have different metadata models, or the transfer protocol simply doesn’t expose a “metadata‑copy” operation. | | Quick fix | Explicitly tell the tool to skip metadata, or map it to a supported format; upgrade to a newer client/SDK; use a staging area that understands both sides. | | Long‑term fix | Align your data‑governance strategy with the capabilities of the storage platform, and automate metadata handling in your pipelines. | 1️⃣ What Is “Metadata” Anyway? When you hear “metadata” in the context of files, objects, or containers, think of the data about the data :

# Extract user metadata (may be empty) CUSTOM=$(jq -r '.metadata' src-meta.json)