IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
Errors when compressing WAV merged with GoldWave, [Specify WHICH errors—ie “WARNING: skipping unknown sub-chunk” at end]
xj220c
post Feb 3 2012, 20:24
Post #1





Group: Members
Posts: 4
Joined: 3-February 12
Member No.: 96917



Hello all,

New here, please forgive if this is a noob question but I think I've got a really weird problem.

I'm trying to combine individual tracks ripped from various SACD's into a single WAV file that can be compressed with FLAC. All of the tracks are 24bit/96K. Basically I'm making compilation SACD's off of my SACD collection and then archiving them as FLAC + cue sheet for when the CD-R goes bad and I need to regenerate it.

I'm using GoldWave to merge the tracks. This produces a perfectly good WAV and cue sheet that seem to work fine in a variety of other players.

FLAC will compress each of the individual track WAV's just fine. However, when I try to compress the merged WAV saved from GoldWave FLAC runs fine until about 99% completion when it starts to throw out thousands of errors. All of these errors are of the format "WARNING: skipping unknown sub-chunk (use --keep-foreign-metedata to keep)". I've let FLAC run for several minutes and it just generates a seemingly endless stream of these errors without completing.

And then it gets even weirder . . .

GoldWave has the ability to save in FLAC so I tried that and GoldWave compressed the merged WAV without generating any errors. HOWEVER, when I decompressed the FLAC file made with GoldWave using FLAC the input and output WAV's did not match. The output was about 0.5% smaller than the input and generated a different checksum. Even stranger, the smaller decompressed WAV will now compress with FLAC without error.

It seems that GoldWave is writing some non-standard data to the merged WAV and that this non-standard data (and hopefully ONLY the non-standard data) is then lost when GoldWave compresses the file to FLAC.

One way or another something goofy is going on here. GoldWave and FLAC don't seem to be playing nice with each other. I could just write out the FLAC from inside GoldWave but that produces a non-identical file on decompression so I'm a little scared of that process. I suspect that the issue is with GoldWave doing something weird when saving the merged WAV but it's impossible to be sure.

Any insight on this one? Anybody have an idea on what's happening?

Sorry if it's not all clear. I'll try to clarify if you folks can't make out what I mean.

Thanks!
XJ.

PS - it's FLAC 1.7.1 and GoldWave 5.66.

This post has been edited by xj220c: Feb 3 2012, 20:27
Go to the top of the page
+Quote Post
db1989
post Feb 3 2012, 21:10
Post #2





Group: Super Moderator
Posts: 5275
Joined: 23-June 06
Member No.: 32180



My uneducated guess would be that said “unknown sub-chunk[s]” are some tag that GoldWave is appending to the resulting WAV file. Does it have any options to configure this sort of thing, i.e. to turn it off?
Go to the top of the page
+Quote Post
lvqcl
post Feb 3 2012, 21:13
Post #3





Group: Developer
Posts: 3436
Joined: 2-December 07
Member No.: 49183



...And what's the size of the WAV file?
Go to the top of the page
+Quote Post
xj220c
post Feb 3 2012, 21:27
Post #4





Group: Members
Posts: 4
Joined: 3-February 12
Member No.: 96917



QUOTE (db1989 @ Feb 3 2012, 22:10) *
My uneducated guess would be that said "unknown sub-chunk[s]" are some tag that GoldWave is appending to the resulting WAV file. Does it have any options to configure this sort of thing, i.e. to turn it off?

AFAIK there's no way to control the metadata or header that GoldWave writes to a WAV. While I like it for it's editing capabilities, GoldWave is, unfortuantely, not very friendly towards file format tweaking.

QUOTE (lvqcl @ Feb 3 2012, 22:13) *
...And what's the size of the WAV file?

Individual tracks are between 60 and 120Mb.

The merged files are between 1.25 and 2.75Gb.

This post has been edited by db1989: Feb 3 2012, 21:36
Reason for edit: Please try to write everything, or edit, rather than double-posting.
Go to the top of the page
+Quote Post
xj220c
post Feb 3 2012, 22:39
Post #5





Group: Members
Posts: 4
Joined: 3-February 12
Member No.: 96917



An Update:

So I downloaded Audacity and manually merged the tracks with that program. The resulting WAV compressed in FLAC without errors. The FLAC file then decompressed to an exact copy of the original and I was able to master an SACD-R using the decompressed files that played properly in my SACD player.

So whatever the issue is it most definitely seems to be in GoldWave and not FLAC.

Audacity doesn't have an automatic file merge feature so it's not going to work well for me. I'll just have to abandon GoldWave and find another program that will automerge a set of high rate files.


Further Update:

A merged WAV created with GoldWave can be "fixed" by importing it into Audacity and re-exporting it as a new WAV file. The resulting WAV will compress and decompress perfectly with FLAC.

This clearly points to GoldWave writing some sort of extra data into WAV files that FLAC is choking on. At this point I don't think I'll be trusting GoldWave with my files anymore.


Cheers,
XJ.

This post has been edited by xj220c: Feb 3 2012, 23:02
Go to the top of the page
+Quote Post
hlloyge
post Feb 4 2012, 10:52
Post #6





Group: Members
Posts: 701
Joined: 10-January 06
From: Zagreb
Member No.: 27018



Just a quick off-topic question: with what are you mastering your SACD-R disk?
Go to the top of the page
+Quote Post
mjb2006
post Feb 4 2012, 10:53
Post #7





Group: Members
Posts: 848
Joined: 12-May 06
From: Colorado, USA
Member No.: 30694



I experimented with some 24-bit 96 KHz audio files and Goldwave's merge function, but didn't get any problems. I did have to be careful to select 96000 Hz in the merge dialog, and to select the right "attributes" (WAV 24-bit 96 KHz stereo) in the output file-save dialog. I noticed it had two different options for that, one being "obsolete". Maybe that makes a difference?
Go to the top of the page
+Quote Post
astroidmist
post Feb 5 2012, 02:07
Post #8





Group: Members
Posts: 34
Joined: 10-January 11
Member No.: 87208



Wavosaur also writes it's own metadata to WAV files, just to warn ya before you try that one too. Also a disappointment since Wavosaur can read/write some large files really quickly.


--------------------
opinion is not fact
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 26th November 2014 - 12:49