| Summary: | k3b problems with flac 96k 24bit, created by libFLAC 1.2.1 (UTC 2007-09-17) | ||
|---|---|---|---|
| Product: | [Applications] k3b | Reporter: | Nikos Papadopoulos <231036448> |
| Component: | Audio Project | Assignee: | k3b developers <k3b> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aacid, krashrson, michalm, trueg |
| Priority: | NOR | ||
| Version: | 19.04 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | "___ File 2 ___ " as described in the bug | ||
|
Description
Nikos Papadopoulos
2020-02-24 19:06:17 UTC
Created attachment 126385 [details]
"___ File 2 ___ " as described in the bug
Attention!
This file is a silent file. But if you open it in Audacity, you will see a graph.
I see now. that the wav file, that gets created by k3b, out of "___ File 2 ___" flac, is too large to attach here. For this thing to make sense, you probably have to use the attached "___ File 2 ___" flac file, and try to make an Audio CD with k3b (export the sound only, no need to actually burn the CD ). Then you need to open the new wav file, in Audacity, as well as open the initial "___ File 2 ___" flac file in Audacity. Comparing the two, you should see that the initial graph has disappeared. But then again, this might be a result of the different "Sampling rates" between the two files, and this example might mean absolutely nothing. Sorry... but that is what I could find. ... Why is the flac file silent? See... https://people.xiph.org/~xiphmont/demo/neil-young.html --> Intermod Tests Alternatively, someone could try downloading the "___ File 1 ___" flac file. Please provide a non silent file, i can't rule out there's some magic optimization somewhere saying "this is silent anyway" Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |