Convert AU to WMA Online for Free

Convert AU to WMA by Decoding SND Samples and Writing a New ASF Stream

Convert AU to WMA when the receiving application expressly accepts Windows Media Audio rather than a Sun or NeXT AU/SND source. The converter reads the AU header and payload encoding, decodes the source to samples, encodes a new Windows Media Audio stream, and places it in an Advanced Systems Format (ASF) file commonly named .wma. It is neither a simple container move nor an extension change.

AU can contain linear PCM, floating-point samples, G.711 mu-law or A-law, ADPCM, and other coding types. WMA profile selection is a separate new delivery choice. If the AU holds clean PCM, it can be a suitable source for one WMA output; if it is already G.711 or another lossy source, WMA cannot restore prior detail. Preserve the AU or another suitable master and avoid making a new WMA from an old lossy copy.

A correct file must carry a supported WMA stream and coherent ASF objects. An output that happens to end with .wma but still contains AU data is not a valid conversion.

Use the Big-Endian AU Offset and Encoding Code to Locate and Decode Source Audio

AU/SND begins with .snd. Its six fixed 32-bit header fields are stored big-endian and identify the data offset, data size, encoding, sample rate, and channels after the magic. The data offset includes the fixed header and any variable information field. A parser must use the actual offset rather than assuming a fixed audio start; otherwise it can feed header text or the wrong bytes to a decoder.

Encoding codes define how the payload is interpreted. Common codes identify 8-bit G.711 mu-law, 8-, 16-, 24-, and 32-bit linear PCM, 32- or 64-bit IEEE floating point, and 8-bit G.711 A-law. AU fields and audio payload are big-endian in the Sun definition. G.711 requires expansion to linear sample values; linear multibyte PCM needs correct big-endian interpretation. A bad offset, wrong encoding, or swapped sample bytes must be fixed before WMA bitrate or profile settings can matter.

Verify source magic, offset, declared payload size, encoding, rate, channels, decoded duration, and audible content. An AU file can have the expected extension but still be malformed or use an unsupported encoding, in which case an honest workflow stops rather than labelling unrelated output WMA.

WMA Identifies the Audio Codec Family While ASF Supplies the Object Container

WMA and ASF are related but different layers. Windows Media Audio names audio codec choices; ASF is an extensible container that can carry WMA or other streams. An audio-only ASF containing WMA is commonly given the WMA extension, but the extension by itself does not identify profile, rate, channel layout, or actual source. The conversion must create the selected codec stream and the container that describes it to the receiver.

ASF objects use a 128-bit GUID, a 64-bit object size, and object data. At the top level, a Header Object and Data Object are mandatory; Index Objects are optional. The Header appears first and contains stream interpretation information. The Data Object follows it and carries media data organized as packets. File Properties can describe size, play duration, packet count, minimum and maximum packet sizes, and maximum bitrate. Stream Properties describe individual streams, and optional objects can carry metadata and codec information.

This object model is not compatible with the AU fixed header. AU description text and source encoding fields do not simply become ASF properties without deliberate mapping.

Match WMA Profile, Bitrate, Rate, and Channels to the Actual Destination

Select a WMA profile, bitrate, sample rate, and channel configuration from the real destination’s requirements. These are different controls. Profile determines the WMA decoder toolset; bitrate sets a compression budget; rate defines timing; and channels determine layout. A higher bitrate does not repair a wrong AU decode, restore G.711 detail, or undo clipping. Preserve AU rate and channels when the target supports them, and document a resample or downmix when it is required.

For a multichannel AU source, verify that the chosen WMA profile and receiver can handle the intended layout. If stereo is required, create an intentional mix and listen for dialogue loss, phase cancellation, and balance. Do not silently discard channels. For a narrowband mu-law AU, an increased WMA rate or bitrate changes the target representation but does not turn telephone-band speech into a wideband original.

Inspect ASF Packet and Header Consistency Instead of Treating WMA as Raw Audio

The ASF Data Object contains media data packets, each with parsing information followed by payload. Packets have presentation times and appear in received order. Header information records characteristics including packet size and count, so packet construction and the Header Object must agree. For a typical fixed-packet delivery, do not byte-copy arbitrary source ranges or alter packet boundaries without an ASF-aware workflow. A syntactically damaged packet sequence can play partially, fail seeking, or be rejected by the receiver.

The optional Index Object provides time-based random access into the Data Object. Its absence or presence is a container decision, not an AU-source fact. A successful WMA delivery should be inspected for its actual codec, stream properties, duration, bitrate, channels, and metadata; then transferred through the same route the final system uses. A partially copied file can look like a WMA codec failure even if the local encode was valid.

If a receiver cannot open the output, compare its accepted WMA profiles, ASF packet expectations, rate, channels, and DRM policy before producing another source-based file. Do not guess by changing extensions.

Keep AU Context Separately From ASF Metadata, Markers, and Optional Indexes

AU can contain a variable information area, while ASF Header Objects can store title, author, codec list, and other metadata. An ASF marker or index serves its own time-based container purpose. There is no guaranteed one-to-one mapping from AU information text, source encoding code, application-specific bytes, or production notes to WMA/ASF fields. Preserve essential source context in a manifest and map only known descriptive fields after inspection.

Treat audio and metadata acceptance separately. Confirm WMA audio first, then inspect title, author, artwork where supported, ordering, duration, and any marker behaviour in the final library. If only tags are incorrect, repair metadata without a new lossy WMA encoding whenever feasible. Keep the original AU when its header or source information carries archival value.

The output is a distribution derivative with a new packet and metadata system. It should not silently replace the AU as the only provenance record.

Approve AU-to-WMA Only After Source Decode, ASF Inspection, and Target Playback

Is AU to WMA a lossless conversion?
Not in the usual WMA delivery path. PCM AU can be decoded cleanly, but a new WMA encode is normally lossy. G.711 and other lossy AU sources cannot regain removed detail.

Why does my output sound like noise?
Check AU magic, big-endian offset, encoding code, source rate, and channels. A wrong source interpretation is encoded into WMA and cannot be repaired by increasing bitrate.

Is WMA the same as ASF?
No. WMA names audio codecs; ASF is the object-based container usually used for WMA files. Inspect both the stream and the container.

Can I choose any WMA profile or rate?
No. Use values documented by the final receiver, then verify the output’s actual codec/profile, rate, channels, duration, and playback.

Will AU notes become WMA tags and markers automatically?
Not reliably. AU information and ASF metadata/index models differ, so preserve source context separately and map only verified fields.

For batches, group AU sources by encoding, sample rate, and channel layout. Validate one file in each group from header inspection through WMA output and final receiver playback. Record source decode, profile, bitrate, packet/header checks, metadata mapping, and transfer result. This isolates AU parsing, WMA encoding, ASF structure, metadata, and compatibility problems while a clean source remains available for controlled re-encoding.

Also compare the first audible source sample and final event after the final copy. This small check catches an AU offset mistake or an incomplete ASF transfer that metadata inspection alone will not reveal.