0.1.8-alpha for 2.0.4
Trammell Hudson
This is way below alpha at this point -- I have booted it a few
times on my camera running 2.0.4, but have not verified ANY of the
features beyond simple behaviour of the audio meters and zebras.
Please report any problems to the list and I'll see what we can fix.
Please do not distribute this release or use it for production.
Be sure to remove your battery after filming to ensure full
uninstall.
It will only work with Canon's 2.0.4 firmware. 1.1.0 and 2.0.3 are
no longer supported.
Jon -- if you want to give the audio settings a spin I believe the
old settings will work exactly the same. It will over-write the
Canon settings 1 second after recording begins, similar to the way
it did before.
--
Trammell
Chris Barcellos
yet, but I have not been successful with this version. I turned
auto boot on, then tried to write MBR, camera essentially locks up.
If my recollection serves me right, that is the way we are supposed
to try to construct the autoboot .bin file ?
I was able to write to the config file, and it save. Every thing
seems to work as we was in .0.1.6. I also try changing frame rates
while in ML, 0.1.8 and it worked fine. I checked out zebras
briefly, and that was okay. I have not tested sound yet.
Chris Barcellos
> magiclantern-0.1.8.zip
> 88KViewDownload
Jon Fairhurst
I haven't had a chance to load the new alpha code, but here are my noise
test results for various combinations. All the tests used a juicedLink
CX231 preamp. To calibrate, I switched the preamp input to line level,
inserted a 1kHz -12dBFS tone and adjusted the JL to produce a -12dBFS
(or so) recording. The mic/line switch makes a 40dB difference, so one
can calibrate for mic level using a -52dBFS tone.
I ended up using FW1.1.0 and ML0.1.6 with m_gain at +17dB and d_gain at
0dB as the target in-camera gain. (I normally use m_gain at +10dB, but
the 2.0.4 manual adjustment won't go that low.) To match the level, I
set the 2.0.4 firmware manual gain to six ticks above the minimum. The
JL ends up being set at 2:00 on the high setting.
Interestingly, when running auto gain and using the juicedLink DN101, I
hit the same calibration within a dB or so. Blind luck.
ML on 1.1.0 is still the cleanest solution around. My statistical
analysis tool showed the noise at -85dB. Let's use that as the baseline.
Here are the noise results in order...
FW1.1.0 ML m_gain+17 => 0dB
Tascam DR100 => +7.5dB (similar ballpark as the H4n, which wasn't
available for this test)
FW2.0.4 (Tick #6) => +9dB
DN101 on either firmware in auto mode => +15dB
Full auto => +39dB; the calibration sine wave is over boosted and is
heavily distorted.
Tomorrow, I should be able to do a test with the alpha code.
Best,
-Jon Fairhurst
Curt von Badinski
--
http://magiclantern.wikia.com/
To post to this group, send email to ml-d...@googlegroups.com
To unsubscribe from this group, send email to ml-devel+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en
To unsubscribe from this group, send email to ml-devel+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
--
Curt von Badinski
Maker of Things
Moira O'Brien LIPF
Moira
http://www.youtube.com/watch?v=OECUW5-J-ok
http://www.youtube.com/watch?v=ciExcdv4RFI
www.moiraobrien.com | www.youtube.com/moirajane | http://moiraobrien.wordpress.com/
Trammell Hudson
> Not sure if we are supposed to be able to write in order to autoboot,
> yet, but I have not been successful with this version. I turned
> auto boot on, then tried to write MBR, camera essentially locks up.
I found the bug -- I had violated my own "best practices" and had
hard-coded addresses of AllocateUncacheableMemory() and
FreeUncacheableMemory() in bootflag_write_bootblock() for the
locations in 1.1.0 rather than putting them in the stubs.S file.
This means that it didn't come up in the list of symbols to locate.
I'll send out an improved beta tomorrow once I find them.
> If my recollection serves me right, that is the way we are supposed
> to try to construct the autoboot .bin file ? [...]
You will need the autoexec.bin file from the zip file on the card
along with the .cfg and .fir file. The "Write MBR" functions (not
actually the MBR, as B. Cole pointed out) writes specifical labels
into the partition table.
--
Trammell
Howard Sheldon
Will the beta you post tomorrow have a different name so we can be sure we
get it? And then will it work with the new canon firmware?
Howard Sheldon
Thanks again for all your hard work, You are appreciated more than you can
imagine.
--
Trammell
--
Trammell Hudson
> Will the beta you post tomorrow have a different name so we can be sure we
> get it?
It will likely still be named 0.1.8 until the "official" version is
posted to the website.
> And then will it work with the new canon firmware?
Yes, the current alpha/beta version works with 2.0.4. That is the
only version that we're targetting now.
--
Trammell
Howard Sheldon
-----Original Message-----
From: ml-d...@googlegroups.com [mailto:ml-d...@googlegroups.com] On Behalf
Of Trammell Hudson
Sent: Tuesday, March 23, 2010 5:47 PM
To: ml-d...@googlegroups.com
Subject: Re: [ML] Re: 0.1.8-alpha for 2.0.4
--
Trammell
--
Ba...@aol.com
On Sun, Mar 21, 2010 at 10:43:54PM -0700, Chris Barcellos wrote:
> Not sure if we are supposed to be able to write in order to autoboot,
> yet, but I have not been successful with this version. I turned
> auto boot on, then tried to write MBR, camera essentially locks up.
I found the bug -- I had violated my own "best practices" and had
hard-coded addresses of AllocateUncacheableMemory() and
FreeUncacheableMemory() in bootflag_write_bootblock() for the
locations in 1.1.0 rather than putting them in the stubs.S file.
This means that it didn't come up in the list of symbols to locate.
I'll send out an improved beta tomorrow once I find them.
> If my recollection serves me right, that is the way we are supposed
> to try to construct the autoboot .bin file ? [...]
You will need the autoexec.bin file from the zip file on the card
along with the .cfg and .fir file. The "Write MBR" functions (not
actually the MBR, as B. Cole pointed out) writes specifical labels
into the partition table.
Trammell Hudson
> With Canons 2.0.4's histogram, are you thinking about streamlining ML
> to remove that feature ?
The official RGB histograms shut off when recording, which is a bit
of a problem. If you don't have the ML histograms displayed there is
no overhead to having them there.
--
Trammell
aj_newman
Jon,
When you compared the 48Khz noise - are you able to quantify the
frequency pattern of the noise?
If we low pass filtered in the 48Khz recorded signal with at 22.05Khz
brick wall - how does it compare with ML 0.1.6?
Regards,
Antony
Jon Fairhurst
The new alpha code is also less noisy than the stock 2.0.4 firmware.
With the ML m_gain at +17dB and the d_gain at 0dB, the levels are nearly
identical to the 2.0.4 firmware on Tick #3. It's a couple dB quieter
than ML 0.1.6, though I have no idea why.
In any case, my calibration is within 0.1 dB when comparing Tick #3 with
m_gain @ 17dB.
The bottom line is that the noise measures at 9dB quieter with
0.1.8alpha, compared to 2.0.4, based on statistical analysis. If you
look at the noiseprints we're even quieter. Perceptually, we're
definitely more than 9dB quieter.
Here's some good news: The new Canon firmware solves the DC offset
problem with and without ML.
On the other hand, from the noiseprint, the Canon firmware is flatter.
ML falls off at high frequencies. This implies that Canon has a flatter
frequency response, but I need to do more testing to know for sure.
I've attached the noiseprints for your enjoyment. :)
All the best,
-Jon Fairhurst
Jon Fairhurst
I've posted some noiseprints. I need to do more testing before I know if
the 48kHx rate has reduced aliasing, or if an external analog filter at
the camera input would help improve things...
Best,
-JF
Howard Sheldon
running with the new firmware is now quieter?
Howard
-----Original Message-----
From: ml-d...@googlegroups.com [mailto:ml-d...@googlegroups.com] On Behalf
Of Jon Fairhurst
Sent: Wednesday, March 24, 2010 12:17 AM
To: ml-d...@googlegroups.com
Subject: Re: [ML] Re: 0.1.8-alpha for 2.0.4
Anthony,
Best,
-JF
--
Trammell Hudson
> I'll send out an improved beta tomorrow once I find them.
Chris -- The attached update fixes the autoboot functionality so
that you can write the bootflag to the CF card.
Curt -- the PTP code is oddly broken. The camera goes into PTP
mode, but the unlock command is not releasing the camera controls to
function as well. I'll spend some time on it this weekend to see
what is going on.
Jon -- I haven't had a chance to write the code to slurp the Canon
registers from the AK4646 before audio.c re-writes them. Hopefully
this weekend. Thanks for running the analysis with the stock 2.0.4
firmware!
Matthias -- the histogram is showing the last pixel now. I think
this is the bug that you were describing in issue #148, but if not
please elaborate. I haven't had any time to try out new color
combinations for the waveform; hopefully this weekend, too!
Also new in this beta is a menu to turn the spotmeter on and off, as
well as a clear-screen option in the video menu to clear the active
16x9 region (a frequently requested feature).
If I've missed a bug report, please bump it on the issue site or
resend it to the list. Thanks!
A word of warning to beta testers: if your camera locks up, be sure
to remove the battery promptly. Apparently there is something going
on with the LCD, even when the backlight is off, and it can cause a
temporary "burn-in" along with a flickering border. Mine did it
when the reboot shim hung for several minutes and a user on dvinfo
reported it happened after a few hours of shooting with an external
composite display.
--
Trammell
Ba...@aol.com
Jon Fairhurst
ML on 2.0.4 and ML on 1.1.0 show very similar noise profiles.
Unfortunately, I tested them at different times. I'll make a point to
get the two cameras together soon. ML on 2.0.4 seems slightly cleaner,
but I'm not convinced that this isn't within the margin of error.
One thing for sure, Canon 2.0.4 has no DC offset. Canon 1.1.0 had a DC
offset on the left channel. I always figured that it was in the preamp
or my particular camera. I've now seen DC offset on two different
cameras with 1.1.0. The new 2.0.4 firmware fixes that on my personal
cam. The DC offset is also fixed for ML 0.1.8 on Canon 2.0.4.
There is also no doubt that ML on 2.0.4 is significantly cleaner than
2.0.4 alone. I pretty much expected this. Canon's gain control is purely
digital. Canon runs a hot analog gain that is fine when you plug a mic
directly into the camera. It's not so great when we try to turn down the
gain and noise in the camera for use with the juicedLink.
In order of increasing goodness (in terms of low noise)...
* juicedLink DN101 into 5D with auto gain. (It's a HUGE improvement over
ALC. It's not bad, but it can't fix Canon's high native analog gain.)
* juicedLink into Canon 2.0.4 stock firmware in manual mode.
* Tascam DR-100 (only a couple dB better than JL/2.0.4)
* juicedLink into ML (still the king!)
All the best,
-JF
Howard Sheldon
being able to get the ok to download it when it's finished.
Howard
Hi Howard,
All the best,
-JF
--
Moira O'Brien LIPF
Second 0.1.8:
There appears to be an issue with the HDMI output as well as with the internal screen display.
Firstly, after the camera goes into sleep mode, the screen fails to come back when brought back to life. This applies to both internal and external screens.
Secondly, the HMDI output seems to get out of sync. The top line of the display carrying the left audio channel disappears, and the ML info line at the bottom now overlays the screen about 1/4 up from the bottom. Also the crop marks go askew, shifted to the left and repeated on the right and the histogram is also shifted to the left and carries on flashing even when the 5D info display is switched off.
On autoboot the shutter used to go up on booting but that does not do so now.
That's about all I have found so far. I haven't been able to shoot in a live situation due to the screen problems but I might try on tomorrow's shoot if I can determine if the screen problems occur under all circumstances.
Keep up the excellent work Tram, you are a genius.
Moira
--
Trammell
Trammell Hudson
I haven't done any analysis on these AK4646 registers yet. This is
a dump showing the values of the registers listed in audio.h:
http://bitbucket.org/hudson/magic-lantern/src/tip/audio.h#cl-157
The upper byte is the register ID, the lower byte is the value read
from the register. The values were output once per second if at
least one had changed from the previous reading.
The camera started in auto audio gain in liveview (and I saw the
drive access light pulsing every second, indicating that something
was changed each time). I switched to the Canon menu, selected
manual gain and then went to max gain, then down to minimum and then
up to mid gain.
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2d49 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2dd2 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2d82 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2db4 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2dc8 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2dca 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2dd2 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2dcb 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2dca 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2dcb 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2206 2340 2704 28d2 29e8 2ce8 2a49 3500 2de8 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2dd2 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2dcf 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2724 28d2 29d2 2cd2 2a49 3500 2dcc 2e91 2f08 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2206 2340 2704 28d2 29e8 2ce8 2a49 3500 2de8 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2206 2340 2704 28d2 29ee 2cee 2a49 3500 2dee 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2704 28d2 29f1 2cf1 2a49 3500 2df1 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2704 28d2 29ef 2cef 2a49 3500 2def 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2205 2340 2704 28d2 29f1 2cf1 2a49 3500 2df1 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2040 2103 2207 2340 2704 28d2 29eb 2ceb 2a49 3500 2d49 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2204 2340 2704 28d2 29ad 2cad 2a49 3500 2dad 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2040 2103 2204 2340 2704 28d2 2900 2c00 2a49 3500 2d49 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2204 2340 2704 28d2 2999 2c99 2a49 3500 2d99 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2204 2340 2704 28d2 2900 2c00 2a49 3500 2d00 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2040 2103 2204 2340 2704 28d2 29a4 2ca4 2a49 3500 2d49 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2040 2103 2204 2340 2704 28d2 29d4 2cd4 2a49 3500 2d49 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2040 2103 2204 2340 2704 28d2 29e0 2ce0 2a49 3500 2d49 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2204 2340 2704 28d2 29e0 2ce0 2a49 3500 2de0 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2204 2340 2704 28d2 29dd 2cdd 2a49 3500 2ddd 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2204 2340 2704 28d2 29e0 2ce0 2a49 3500 2de0 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
2041 2103 2206 2340 2704 28d2 29e8 2ce8 2a49 3500 2de8 2e91 2f00 3000 3131 3c00 3d00 3e00 3f00 6c00 6d00 6e00 6f00
--
Trammell
Trammell Hudson
> [...] The upper byte is the register ID, the lower byte is the
> value read from the register. The values were output once per
> second if at least one had changed from the previous reading.
Why make it hard when the computer can do this for us? I modified
the code to print only the registers that changed and then did a
slow ramp from minimum gain to maximum gain. The newlines separate
each output block.
AUDIO_IC_PM1 41
AUDIO_IC_PM2 03
AUDIO_IC_SIG1 05
AUDIO_IC_SIG2 40
AUDIO_IC_ALC1 24
AUDIO_IC_ALC2 d2
AUDIO_IC_IVL d2
AUDIO_IC_IVR d2
AUDIO_IC_OVL 49
AUDIO_IC_OVR 00
AUDIO_IC_ALCVOL 49
AUDIO_IC_MODE3 91
AUDIO_IC_MODE4 08
AUDIO_IC_PM3 00
AUDIO_IC_FIL1 31
AUDIO_IC_HPF0 00
AUDIO_IC_HPF1 00
AUDIO_IC_HPF2 00
AUDIO_IC_HPF3 00
AUDIO_IC_LPF0 00
AUDIO_IC_LPF1 00
AUDIO_IC_LPF2 00
AUDIO_IC_LPF3 00
AUDIO_IC_PM1 41
AUDIO_IC_PM2 03
AUDIO_IC_SIG1 05
AUDIO_IC_SIG2 40
AUDIO_IC_ALC1 24
AUDIO_IC_ALC2 d2
AUDIO_IC_IVL d2
AUDIO_IC_IVR d2
AUDIO_IC_OVL 49
AUDIO_IC_OVR 00
AUDIO_IC_ALCVOL c8
AUDIO_IC_MODE3 91
AUDIO_IC_MODE4 08
AUDIO_IC_PM3 00
AUDIO_IC_FIL1 31
AUDIO_IC_HPF0 00
AUDIO_IC_HPF1 00
AUDIO_IC_HPF2 00
AUDIO_IC_HPF3 00
AUDIO_IC_LPF0 00
AUDIO_IC_LPF1 00
AUDIO_IC_LPF2 00
AUDIO_IC_LPF3 00
AUDIO_IC_ALCVOL a1
AUDIO_IC_ALCVOL c3
AUDIO_IC_ALCVOL ba
AUDIO_IC_PM1 41
AUDIO_IC_PM2 03
AUDIO_IC_SIG1 05
AUDIO_IC_SIG2 40
AUDIO_IC_ALC1 24
AUDIO_IC_ALC2 d2
AUDIO_IC_IVL d2
AUDIO_IC_IVR d2
AUDIO_IC_OVL 49
AUDIO_IC_OVR 00
AUDIO_IC_ALCVOL bf
AUDIO_IC_MODE3 91
AUDIO_IC_MODE4 08
AUDIO_IC_PM3 00
AUDIO_IC_FIL1 31
AUDIO_IC_HPF0 00
AUDIO_IC_HPF1 00
AUDIO_IC_HPF2 00
AUDIO_IC_HPF3 00
AUDIO_IC_LPF0 00
AUDIO_IC_LPF1 00
AUDIO_IC_LPF2 00
AUDIO_IC_LPF3 00
AUDIO_IC_ALCVOL be
AUDIO_IC_ALCVOL bc
AUDIO_IC_SIG1 06
AUDIO_IC_ALC1 04
AUDIO_IC_IVL e8
AUDIO_IC_IVR e8
AUDIO_IC_ALCVOL e8
AUDIO_IC_MODE4 00
AUDIO_IC_SIG1 05
AUDIO_IC_ALC1 24
AUDIO_IC_IVL d2
AUDIO_IC_IVR d2
AUDIO_IC_ALCVOL c6
AUDIO_IC_MODE4 08
AUDIO_IC_ALCVOL cc
AUDIO_IC_ALCVOL b3
AUDIO_IC_ALCVOL be
AUDIO_IC_ALCVOL bd
AUDIO_IC_SIG1 06
AUDIO_IC_ALC1 04
AUDIO_IC_IVL e8
AUDIO_IC_IVR e8
AUDIO_IC_ALCVOL e8
AUDIO_IC_MODE4 00
AUDIO_IC_PM1 40
AUDIO_IC_SIG1 04
AUDIO_IC_IVL e0
AUDIO_IC_IVR e0
AUDIO_IC_ALCVOL 49
AUDIO_IC_IVL b0
AUDIO_IC_IVR b0
AUDIO_IC_PM1 41
AUDIO_IC_IVL 00
AUDIO_IC_IVR 00
AUDIO_IC_ALCVOL 00
AUDIO_IC_IVL 99
AUDIO_IC_IVR 99
AUDIO_IC_ALCVOL 99
AUDIO_IC_IVL 9b
AUDIO_IC_IVR 9b
AUDIO_IC_ALCVOL 9b
AUDIO_IC_IVL 9e
AUDIO_IC_IVR 9e
AUDIO_IC_ALCVOL 9e
AUDIO_IC_IVL a0
AUDIO_IC_IVR a0
AUDIO_IC_ALCVOL a0
AUDIO_IC_IVL a2
AUDIO_IC_IVR a2
AUDIO_IC_ALCVOL a2
AUDIO_IC_IVL a4
AUDIO_IC_IVR a4
AUDIO_IC_ALCVOL a4
AUDIO_IC_IVL a7
AUDIO_IC_IVR a7
AUDIO_IC_ALCVOL a7
AUDIO_IC_IVL a9
AUDIO_IC_IVR a9
AUDIO_IC_ALCVOL a9
AUDIO_IC_IVL ab
AUDIO_IC_IVR ab
AUDIO_IC_ALCVOL ab
AUDIO_IC_IVL ad
AUDIO_IC_IVR ad
AUDIO_IC_ALCVOL ad
AUDIO_IC_IVL b0
AUDIO_IC_IVR b0
AUDIO_IC_ALCVOL b0
AUDIO_IC_IVL b2
AUDIO_IC_IVR b2
AUDIO_IC_ALCVOL b2
AUDIO_IC_IVL b4
AUDIO_IC_IVR b4
AUDIO_IC_ALCVOL b4
AUDIO_IC_IVL b7
AUDIO_IC_IVR b7
AUDIO_IC_ALCVOL b7
AUDIO_IC_IVL b9
AUDIO_IC_IVR b9
AUDIO_IC_ALCVOL b9
AUDIO_IC_IVL bb
AUDIO_IC_IVR bb
AUDIO_IC_ALCVOL bb
AUDIO_IC_IVL bd
AUDIO_IC_IVR bd
AUDIO_IC_ALCVOL bd
AUDIO_IC_IVL c0
AUDIO_IC_IVR c0
AUDIO_IC_ALCVOL c0
AUDIO_IC_IVL c2
AUDIO_IC_IVR c2
AUDIO_IC_ALCVOL c2
AUDIO_IC_PM1 40
AUDIO_IC_IVL c4
AUDIO_IC_IVR c4
AUDIO_IC_ALCVOL 49
AUDIO_IC_IVL c6
AUDIO_IC_IVR c6
AUDIO_IC_IVL c9
AUDIO_IC_IVR c9
AUDIO_IC_PM1 41
AUDIO_IC_ALCVOL c9
AUDIO_IC_IVL cb
AUDIO_IC_IVR cb
AUDIO_IC_ALCVOL cb
AUDIO_IC_IVL cd
AUDIO_IC_IVR cd
AUDIO_IC_ALCVOL cd
AUDIO_IC_IVL d0
AUDIO_IC_IVR d0
AUDIO_IC_ALCVOL d0
AUDIO_IC_IVL d2
AUDIO_IC_IVR d2
AUDIO_IC_ALCVOL d2
AUDIO_IC_PM1 40
AUDIO_IC_IVL d4
AUDIO_IC_IVR d4
AUDIO_IC_ALCVOL 49
AUDIO_IC_PM1 41
AUDIO_IC_ALCVOL d4
AUDIO_IC_IVL d6
AUDIO_IC_IVR d6
AUDIO_IC_ALCVOL d6
AUDIO_IC_IVL d9
AUDIO_IC_IVR d9
AUDIO_IC_ALCVOL d9
AUDIO_IC_IVL db
AUDIO_IC_IVR db
AUDIO_IC_ALCVOL db
AUDIO_IC_IVL dd
AUDIO_IC_IVR dd
AUDIO_IC_ALCVOL dd
AUDIO_IC_IVL e0
AUDIO_IC_IVR e0
AUDIO_IC_ALCVOL e0
AUDIO_IC_IVL e2
AUDIO_IC_IVR e2
AUDIO_IC_ALCVOL e2
AUDIO_IC_IVL e4
AUDIO_IC_IVR e4
AUDIO_IC_ALCVOL e4
AUDIO_IC_IVL e6
AUDIO_IC_IVR e6
AUDIO_IC_ALCVOL e6
AUDIO_IC_IVL e9
AUDIO_IC_IVR e9
AUDIO_IC_ALCVOL e9
AUDIO_IC_IVL eb
AUDIO_IC_IVR eb
AUDIO_IC_ALCVOL eb
AUDIO_IC_IVL ed
AUDIO_IC_IVR ed
AUDIO_IC_ALCVOL ed
AUDIO_IC_IVL ef
AUDIO_IC_IVR ef
AUDIO_IC_ALCVOL ef
AUDIO_IC_SIG1 06
AUDIO_IC_IVL d8
AUDIO_IC_IVR d8
AUDIO_IC_ALCVOL d8
AUDIO_IC_IVL da
AUDIO_IC_IVR da
AUDIO_IC_ALCVOL da
AUDIO_IC_IVL dc
AUDIO_IC_IVR dc
AUDIO_IC_ALCVOL dc
AUDIO_IC_IVL df
AUDIO_IC_IVR df
AUDIO_IC_ALCVOL df
AUDIO_IC_IVL e1
AUDIO_IC_IVR e1
AUDIO_IC_ALCVOL e1
AUDIO_IC_IVL e3
AUDIO_IC_IVR e3
AUDIO_IC_ALCVOL e3
AUDIO_IC_IVL e5
AUDIO_IC_IVR e5
AUDIO_IC_ALCVOL e5
AUDIO_IC_IVL e8
AUDIO_IC_IVR e8
AUDIO_IC_ALCVOL e8
AUDIO_IC_IVL ea
AUDIO_IC_IVR ea
AUDIO_IC_ALCVOL ea
AUDIO_IC_IVL ec
AUDIO_IC_IVR ec
AUDIO_IC_ALCVOL ec
AUDIO_IC_IVL ee
AUDIO_IC_IVR ee
AUDIO_IC_ALCVOL ee
AUDIO_IC_IVL f1
AUDIO_IC_IVR f1
AUDIO_IC_ALCVOL f1
AUDIO_IC_SIG1 07
AUDIO_IC_IVL e0
AUDIO_IC_IVR e0
AUDIO_IC_ALCVOL e0
AUDIO_IC_IVL e2
AUDIO_IC_IVR e2
AUDIO_IC_ALCVOL e2
AUDIO_IC_IVL e5
AUDIO_IC_IVR e5
AUDIO_IC_ALCVOL e5
AUDIO_IC_IVL e7
AUDIO_IC_IVR e7
AUDIO_IC_ALCVOL e7
AUDIO_IC_IVL e9
AUDIO_IC_IVR e9
AUDIO_IC_ALCVOL e9
AUDIO_IC_IVL eb
AUDIO_IC_IVR eb
AUDIO_IC_ALCVOL eb
AUDIO_IC_IVL ee
AUDIO_IC_IVR ee
AUDIO_IC_ALCVOL ee
AUDIO_IC_PM1 40
AUDIO_IC_IVL f0
AUDIO_IC_IVR f0
AUDIO_IC_ALCVOL 49
AUDIO_IC_PM1 41
AUDIO_IC_ALCVOL f0
AUDIO_IC_SIG1 05
AUDIO_IC_IVL ea
AUDIO_IC_IVR ea
AUDIO_IC_ALCVOL ea
AUDIO_IC_IVL ec
AUDIO_IC_IVR ec
AUDIO_IC_ALCVOL ec
AUDIO_IC_IVL ef
AUDIO_IC_IVR ef
AUDIO_IC_ALCVOL ef
AUDIO_IC_PM1 40
AUDIO_IC_IVL f1
AUDIO_IC_IVR f1
AUDIO_IC_ALCVOL f1
AUDIO_IC_PM1 41
Jon Fairhurst
I'm printing it now and will analyze it shortly.
Best,
-JF