> It looks like it only supports compression code 1. > Whatever the hell that means.
I'm not sure why "compression code" - I think this is just the WAV format subtype where 1 is 16-bit PCM and 3 is IEEE floating point. But that's from my usually unreliable memory. > Is there some way to write files with compression > code 1 instead of 3? I think that's just what a 16-bit WAV file is. (The complaint here is about the input file to FLAC, which is uncompressed WAV - hence why "compression code" is weird and confusing.) > I guess this is pretty much a show-stopper though. Sounds like the packager will either need an intermediate step of converting to 16-bit (tedious and would need a warning dialog) or will need to not use FLAC on 32-bit files... or will need a 32-bit capable FLAC encoder, assuming the format supports it internally. What a pain. I'm not in a position to research this at the moment though, there may be a simple fix besides switching RG back to 16-bit output. > The brilliant idea to use /tmp as a dumping ground, > and then package up the good files Well, I can understand why you wanted to do that, but to be honest I don't think saving your work in a directory guaranteed to be lost on a crash is a very good idea whatever. (If you don't actually want the particular properties of /tmp, why save there? You could always create ~/scratch/ or something.) I don't think RG can be blamed for that part. It does make the packager really useless though. Chris ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
