Bug 394836 - K3B unable to handle the following files due to an unsupported format
Summary: K3B unable to handle the following files due to an unsupported format
Status: RESOLVED DUPLICATE of bug 399056
Alias: None
Product: k3b
Classification: Applications
Component: Audio Project (show other bugs)
Version: 2.0.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-29 18:25 UTC by Viktor
Modified: 2020-02-06 01:35 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
A wav file downloaded from landr.com and not accepted by k3b (1.50 MB, audio/x-wav)
2018-05-29 18:25 UTC, Viktor
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Viktor 2018-05-29 18:25:50 UTC
Created attachment 112952 [details]
A wav file downloaded from landr.com and not accepted by k3b

When creating an audio project, I try to import wav files (16b, 44.1khz) and get the error as in the title. Further I get this: 
"You may manually convert these audio files to wave using another application supporting the audio format and then add the wave files to the K3b project.
~/Downloads/LANDR-Fisarmonika[add.silence]orig.wav"

These wav files are downloaded from landr.com, an online mastering service. 

I contacted the LandR customer service and they told me that "...This suggests that your CD burning software does not like the metadata attached to LANDR masters downloaded from the cloud. Masters downloaded from the cloud include metadata related to it's origin server location."

On K3B, I can burn mp3 files downloaded from the same website, I can burn wav files from any other source.

I can also burn these downloaded wav files files with Brasero disk burning software. 

I attach a sample wav file downloaded from landr.com
Comment 1 Patrick Silva 2018-09-25 15:10:01 UTC
I can confirm on Arch Linux with K3b 18.08.1.
Bug 399056 seems related/duplicate.
Comment 2 Patrick Silva 2020-02-06 01:35:13 UTC

*** This bug has been marked as a duplicate of bug 399056 ***