Sponsored Content
Operating Systems OS X (Apple) I don't know how to put this, an Apple Audio HW bug? Post 302907232 by Corona688 on Thursday 26th of June 2014 05:01:38 PM
Old 06-26-2014
Quote:
Originally Posted by wisecracker
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.
It could be anything from the software implementation of the player and codecs, its DSP chipset, or the output amplifier which causes the inversion. It really doesn't matter for audio purposes, since it sounds the same. You're just seeing the relative popularity of different designs, not "right" or "wrong".

By which I mean, I don't think you can count on it always being the same, you'll need a way to invert it.

[edit] Actually, you could put a switch in your circuit to invert, couldn't you? To flip the secondary side of the transformer.

Last edited by Corona688; 06-26-2014 at 07:22 PM..
 

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 03:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy