Sponsored Content
Operating Systems OS X (Apple) I don't know how to put this, an Apple Audio HW bug? Post 302907224 by wisecracker on Thursday 26th of June 2014 03:40:32 PM
Old 06-26-2014
I don't know how to put this, an Apple Audio HW bug?

Hi guys and gals...

Apologies for any typos...

Well I have a major problem and I don't know how to take it further so I need your advice AND help...
Found from the AudioScope.sh calibration method(s)...

I think I have found a HW bug in Apple gear...

This has been checked so far on a new iPhone 5S,
a 3 month old iPad Air and my Macbook Pro...

As a confirmation I have tried it on my old Blackberry Phone, Windows Vista and XP on various machines
Debian Linux and PCLinuxOS 2009 on an HP laptop and an Acer Aspire One netbook these work perfectly as
the sound _card_ should...
It has even been checked as a RAW file in /dev/dsp too and is correct.
(Will check CygWin tomorrow.)

Consider the code below:-
It was written to set up the vertical amplifier polarity and works as designed BUT........
Code:
#!/bin/bash --posix
> /tmp/pulse.wav
printf "\x52\x49\x46\x46\x24\x00\x01\x00\x57\x41\x56\x45\x66\x6d\x74\x20\x10\x00\x00\x00\x01\x00\x01\x00\x40\x1f\x00\x00\x40\x1f\x00\x00\x01\x00\x08\x00\x64\x61\x74\x61\x00\x00\x01\x00" >> /tmp/pulse.wav
for n in {0..8191}
do
	printf "\xFF\xFF\x00\x00\x00\x00\x00\x00" >> /tmp/pulse.wav
done
afplay /tmp/pulse.wav
exit 0

This works perfectly on the RANDOM gear as it should; a NEGATIVE going pulse NOT a POSITIVE one.
When pulse.wav is transferred to run on the Apple gear above the waveform is inverted, I.E. it is a
POSITIVE going pilse. AFAIK this is wrong.

What I would dearly like is for the interested on here to check the waveform from the earphone socket
against a known Oscilloscope and reply to this thread.

You can test on anything that plays a .WAV file. The quality of the wave is NOT important the polarity
IS however...

It should look something like this:-

Code:
 =-+  +-----------+  +-------  <- 0x00 Unsigned 8 bit.
   |  |           |  |
   |  |           |  |
   |  |           |  |
   |  |           |  |
   +--+           +--+  <- 0xFF Unsigned 8 bit.

Remember quality is NOT important, polarity IS...

I will be checking on other machines and phones myself over the WE...

Many thanks in advance...

NOTE:- I have not yet posted anywhere else and hope I am wrong. thanks guys and gals...

If this is consitent throughout Apple gear then I don't know how to take it further...

Barry.

EDIT:
Many thanks to my workmate Richard Carter for letting me test on his iPhone 5S and
his iPad Air...

Last edited by wisecracker; 06-26-2014 at 04:47 PM.. Reason: See above...
 

2 More Discussions You Might Find Interesting

1. Solaris

Solaris 10,audio don't work and unrar needed

Hi, I'm here again for newbie questions :) I've installed Solaris 10 but audio don't work.I've a Realtek integrated peripheral,listed in Sun Hcl.The volume control is ok also.But nothing came from speakers. I need to install unrar also,I've download it from here Freeware for Solaris with... (1 Reply)
Discussion started by: bgf0
1 Replies

2. Slackware

Problems with audio recording in Audacity 2.0.5. Slackware64 14.1; Intel HD Audio.

I'm trying to record audio using Audacity 2.0.5 installed from SlackBuilds. My system is 64-bit Slackware 14.1 and a sound card is Intel HD Audio. I didn't change my sound system to OSS. (Default sound system in Slackware 14.1 is ALSA, isn't it?) First, I set Internal Microphone slider in KMix... (2 Replies)
Discussion started by: qzxcvbnm
2 Replies
allegro_exit(3alleg4)						  Allegro manual					     allegro_exit(3alleg4)

NAME
allegro_exit - Closes down the Allegro system. SYNOPSIS
#include <allegro.h> void allegro_exit(); DESCRIPTION
Closes down the Allegro system. This includes returning the system to text mode and removing whatever mouse, keyboard, and timer routines have been installed. You don't normally need to bother making an explicit call to this function, because allegro_init() installs it as an atexit() routine so it will be called automatically when your program exits. Note that after you call this function, other functions like destroy_bitmap() will most likely crash. This is a problem for C++ global destructors, which usually get called after atexit(), so don't put Allegro calls in them. You can write the destructor code in another method which you can manually call before your program exits, avoiding this problem. SEE ALSO
install_allegro(3alleg4), allegro_init(3alleg4), destroy_bitmap(3alleg4), ex3d(3alleg4), exscn3d(3alleg4), exswitch(3alleg4), exxfade(3alleg4), exzbuf(3alleg4) Allegro version 4.4.2 allegro_exit(3alleg4)
All times are GMT -4. The time now is 01:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy