Subject:ACID PRO 1.0d update

Posted by: DavidE

Date:4/23/1999 10:34:22 AM

I'm a bit puzzled by the 'packed' and 'unpacked' 24-bit
record options. Can you explain what these mean? My system
at the moment is a combination of 16-bit (Yamaha SW1000XG)
and 24-bit (CreamWare's Pulsar). Unpacked 24-bit seems to
work with the 16-bit SW1000XG drivers but recording to the
same format leads to strange things happening, e.g. only 16-
bit being available on record and the metering being
inoperative.

Something I've observed (heard) with version 1.0a is a
glitching of audio when 'don't transpose' is selected for a
particular track when key change markers apply to other
tracks. Is this recognised as a bug that needs fixing? Have
any bugs been fixed in 1.0d?

Apart from that, I think ACID is a brilliant piece of
software and remarkably stable given its largely un-updated
state!

Regards,

David

Subject:Re: ACID PRO 1.0d update

Reply by: pwppch

Date:4/23/1999 11:39:03 AM

This is the story...

24 bit packed is a format that contains the 24 bits of data in 3 bytes
per
channel. This is the native format for wave devices as defined by the
Microsoft wave API spec.

24 bit unpacked puts 24 bits of data in a 32 bit container. The lower
8 bits
of the container are zero. 24 bit unpacked sends data in 4 bytes per
channel. Many apps and drivers do this, though technically it is an
illegal
format.

The reason for the two is that some 24 bit audio cards do not support
24 bit
packed or are more efficient using 24 bit unpacked. What these cards
do is
have thier driver "unpack" the 24 bit packed format into the 24 bit
packed
format. While this gives them support for 24 bit packed, it does add
another
conversion in software - which means touching the data one more time
before
it is actually sent to the hardware.

Peter







DavidE wrote in message ...
>I'm a bit puzzled by the 'packed' and 'unpacked' 24-bit
>record options. Can you explain what these mean? My system
>at the moment is a combination of 16-bit (Yamaha SW1000XG)
>and 24-bit (CreamWare's Pulsar). Unpacked 24-bit seems to
>work with the 16-bit SW1000XG drivers but recording to the
>same format leads to strange things happening, e.g. only 16-
>bit being available on record and the metering being
>inoperative.
>
>Something I've observed (heard) with version 1.0a is a
>glitching of audio when 'don't transpose' is selected for a
>particular track when key change markers apply to other
>tracks. Is this recognised as a bug that needs fixing? Have
>any bugs been fixed in 1.0d?
>
>Apart from that, I think ACID is a brilliant piece of
>software and remarkably stable given its largely un-updated
>state!
>
>Regards,
>
>David

Subject:Re: ACID PRO 1.0d update

Reply by: DavidE

Date:4/23/1999 9:25:11 PM

Peter, thanks for the explanation. I'm not sure why I was
experiencing the problem with recording in ACID, though,
i.e., no signals on the meters and the 24-bit options
disappearing. Also, any thought on the glitching I
reported? This only occurs as the key change marker is
being passed on playback. It doesn't always happen and I
can't say whether it's affecting disk-based tracks more
than RAM-loaded loop ones.

Regards,

David

Peter Haller wrote:
>>This is the story...
>>
>>24 bit packed is a format that contains the 24 bits of
data in 3 bytes
>>per
>>channel. This is the native format for wave devices as
defined by the
>>Microsoft wave API spec.
>>
>>24 bit unpacked puts 24 bits of data in a 32 bit
container. The lower
>>8 bits
>>of the container are zero. 24 bit unpacked sends data in
4 bytes per
>>channel. Many apps and drivers do this, though
technically it is an
>>illegal
>>format.
>>
>>The reason for the two is that some 24 bit audio cards do
not support
>>24 bit
>>packed or are more efficient using 24 bit unpacked. What
these cards
>>do is
>>have thier driver "unpack" the 24 bit packed format into
the 24 bit
>>packed
>>format. While this gives them support for 24 bit packed,
it does add
>>another
>>conversion in software - which means touching the data
one more time
>>before
>>it is actually sent to the hardware.
>>
>>Peter
>>
>>
>>
>>
>>
>>
>>
>>DavidE wrote in message ...
>>>I'm a bit puzzled by the 'packed' and 'unpacked' 24-bit
>>>record options. Can you explain what these mean? My
system
>>>at the moment is a combination of 16-bit (Yamaha
SW1000XG)
>>>and 24-bit (CreamWare's Pulsar). Unpacked 24-bit seems to
>>>work with the 16-bit SW1000XG drivers but recording to
the
>>>same format leads to strange things happening, e.g. only
16-
>>>bit being available on record and the metering being
>>>inoperative.
>>>
>>>Something I've observed (heard) with version 1.0a is a
>>>glitching of audio when 'don't transpose' is selected
for a
>>>particular track when key change markers apply to other
>>>tracks. Is this recognised as a bug that needs fixing?
Have
>>>any bugs been fixed in 1.0d?
>>>
>>>Apart from that, I think ACID is a brilliant piece of
>>>software and remarkably stable given its largely un-
updated
>>>state!
>>>
>>>Regards,
>>>
>>>David
>>
>>
>>

Subject:Re: ACID PRO 1.0d update

Reply by: tonepad

Date:4/24/1999 5:50:48 PM

David,
Try zooming out full. Tho' I use Acid Music I have
experienced ticks when the cursor has to go to the next
zoomed in screen. Also this problem seemed to be reduced
when I upped my RAM to 128 (actually 160 since I kept a 32
stick in the box)...RAM is so cheap now even cheaper than
when I bought my 128 stick a month ago @$150. I feel the
ticks I've had could be a video/ram related deal hence the
zoom full fix. Don't know if this will help with your
system, but I'm trying to contribute to this forum since
there aren't many Acid boards on the web.

Wilson

David Ellis wrote:
>>Peter, thanks for the explanation. I'm not sure why I was
>>experiencing the problem with recording in ACID, though,
>>i.e., no signals on the meters and the 24-bit options
>>disappearing. Also, any thought on the glitching I
>>reported? This only occurs as the key change marker is
>>being passed on playback. It doesn't always happen and I
>>can't say whether it's affecting disk-based tracks more
>>than RAM-loaded loop ones.
>>
>>Regards,
>>
>>David
>>
>>Peter Haller wrote:
>>>>This is the story...
>>>>
>>>>24 bit packed is a format that contains the 24 bits of
>>data in 3 bytes
>>>>per
>>>>channel. This is the native format for wave devices as
>>defined by the
>>>>Microsoft wave API spec.
>>>>
>>>>24 bit unpacked puts 24 bits of data in a 32 bit
>>container. The lower
>>>>8 bits
>>>>of the container are zero. 24 bit unpacked sends data in
>>4 bytes per
>>>>channel. Many apps and drivers do this, though
>>technically it is an
>>>>illegal
>>>>format.
>>>>
>>>>The reason for the two is that some 24 bit audio cards
do
>>not support
>>>>24 bit
>>>>packed or are more efficient using 24 bit unpacked. What
>>these cards
>>>>do is
>>>>have thier driver "unpack" the 24 bit packed format into
>>the 24 bit
>>>>packed
>>>>format. While this gives them support for 24 bit packed,
>>it does add
>>>>another
>>>>conversion in software - which means touching the data
>>one more time
>>>>before
>>>>it is actually sent to the hardware.
>>>>
>>>>Peter
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>DavidE wrote in message ...
>>>>>I'm a bit puzzled by the 'packed' and 'unpacked' 24-bit
>>>>>record options. Can you explain what these mean? My
>>system
>>>>>at the moment is a combination of 16-bit (Yamaha
>>SW1000XG)
>>>>>and 24-bit (CreamWare's Pulsar). Unpacked 24-bit seems
to
>>>>>work with the 16-bit SW1000XG drivers but recording to
>>the
>>>>>same format leads to strange things happening, e.g.
only
>>16-
>>>>>bit being available on record and the metering being
>>>>>inoperative.
>>>>>
>>>>>Something I've observed (heard) with version 1.0a is a
>>>>>glitching of audio when 'don't transpose' is selected
>>for a
>>>>>particular track when key change markers apply to other
>>>>>tracks. Is this recognised as a bug that needs fixing?
>>Have
>>>>>any bugs been fixed in 1.0d?
>>>>>
>>>>>Apart from that, I think ACID is a brilliant piece of
>>>>>software and remarkably stable given its largely un-
>>updated
>>>>>state!
>>>>>
>>>>>Regards,
>>>>>
>>>>>David
>>>>
>>>>
>>>>
>>