linuxworks

translation: you disagree with me. fine! can't be 'friends' with everyone. (btw, who the hell are you, again?)

ban me? for stating my views? you already threatened me over at headfi. now you want to threaten me here? what a dip-wad you are, grawk. seriously a dip-wad.

negatory. once the bit-squirting hardware has the byte (via dma) the cpu and rest of system has nothing to do with it. once I post a letter in the mail, whatever I do next, the post office is the ONLY one to affect letter speed.

mac people ARE more gullible. they want computing handed to them easily since pcs are 'so hard' (rolls eyes). mac hardware is not better (in any way) than pc hardware but the mac marketing machine has users thinking 'mac will take care of them'. nothing hard to believe about this. its what macs are invented for. computer-phobes, by and large. if the amarra people had 'beef' they'd also release a pc version. why is it they don't bring their 'super special sauce' to other platforms? pc users already know how TRIVIAL it is to squirt out spdif bits. extremely simple. like I said, since win98 pentium-1 days, digital audio has working just fine. but explain to the gullible high-end crowd that, oh my, there's PROBLEM with computer audio (there isn't, btw) then the pocket books open like a cheap whores legs.

prove it, oh clueless asswipe that you are.

the modern mac code is unix based. I have a hard time believing its not *already* bit-perfect and doing things properly. I'm not a mac fan but its incredulous to think that they 'messed up' something so simple as digital audio out to a sound card. folks, that's all it is - clocking bits out to a serial card; same as rs232 (at one level). read a byte, send to spdif hardware. THAT hardware does the proper bit timing and its all hardware these days, software simply does not (and should not!) enter into it. software simply keeps the buffers from being empty. a pentium 200 with win98 (old school) can do that.

disagree. you can explain what you are doing and not give away the shop. this is the same fallacy that hardware vendors use to NOT give you drivers in source form. anyone who does driver work knows that drivers will never let you reverse engineer the hardware or dsp algorithms! so, he could explain what he's doing - but I suspect that there's a ton of smoke and mirrors going on here. there is no other valid reason to hold back the tech info. the fact that 'serious professionals' have bought into this, blindly (no design details) makes me wonder who these so-called pros are and if they're worth anything or are just resting on some name-fame of some kind. in science, disclosure is king. all else is bullshit.

when I was reading up on the amarra website, it 'dissed' nfs and samba and said that remote file access was 'bad' somehow. they lost all cred, in my eyes, with that kind of statement. until they tell us what they are doing, its all just marketing hype to me. computers are quite easy to setup to output bit perfect audio. its not rocket science and does NOT need dsp! dongles only add insult to injury. I hate to say it, but mac people are more gullible and so maybe they are more easily shaken free of a kilobuck (?)

indeed! oops. wrong quote. uhh. yes. yes, it will be there. lol

just for fun....

I'm a heavy freebsd user. that said, I did NOT find freenas stable. but that was about a year ago when I tried it. neat idea, but it needed a newer kernel and bsd is just LOUSY on samba (not sure why!). linux is samba king. linux is a much better fileserver (even for nfs).

650? I'll pass. damn. the point, to me, was that it was semi-affordable. this is just too much. they need to go more large-scale to get the price down. WAY too much on a 'garage project' of sorts (and it looks like it, too).

is this cable worse than, say, the denon d2000 cable? THAT one sucks dead donky dick. so to speak

yes, glt has done some work on the TP dac kits. he seems very interested and motivated toward that I share the same viwe as AMB on this; the NDA stuff rubs me the wrong way and so I won't be spending any time on the ESS chip. it may be a nice chip (never heard one, myself) but locking up the specs (and parts) is not something I agree with.

lcd2? already? I want one!! I missed out on lcd1. gotta have the -2 version now (lol). the top headband isn't appealing but the rest look ok to me. I would change out the bare (sharp?) metal earcup supports or at least cover them somehow. it does not look 'touch friendly'. but the wood cups and leather (?) parts are a nice improvement over the lcd1.

yes, I have seen things like that. reminds me a lot of the square greenlee chassis punches I have (only a few; those are expensive!)

my square drill bits are broken. I can't find replacement square bearings! oh noes.

as long as you clean up your mess before you leave, I just don't care!

the hardest part is cutting the front hole. well, I think it is its just a 'controller' and a volume control board (in one config). vol control board will have inputs and outputs (like a pot). there will be some set of wires that goes to the controller board but it will be documented what goes where. if you like the default programming, then you simply build the boards, hook up the wires and give it power. the LCDuino-1 only need 5v (for itself). diff vol control (and relay boards) need diff other voltages, perhaps. also cut a round hole and some bezel for the IR sensor led thing. wire that to the board with 3 wires (ground, + and signal-out). no big deal. the pga board I use only need 3 cpu wires going to it. again, just a 3 wire bundle or ribbon cable of whatever you have lying around. this should be a pretty easy build. I'm on my 3rd board done, already (lol). I'm busy replacing all the perf-board versions with nice clean pc board ones. some kind of front bezel would be nice. this is an area that could use a little creativity and some help from you casework gurus out there.

no matter what volume level you dialed in, it would self-reset back to eleven. somehow. then you have to wire in one of these: just in case.

thanks I had thought about a multi-dmm (sort of) display to help set things like bias. after going thru a b22 setting, it would be nice to 'watch' a few things at once. even help with doing a delta between 2 things and showing when its 'low enough'. there are 4 unused analog-ins on this chip. send in a 0-5v dc signal and you get 10 bits (0..1023) scaled value. that may be enough. else, there's a really high (20 or 24bit) a/d that has been written up. its a $10 or $15 chip (not cheap) but its very high res. if you could switch that around (somehow; relays?) to the various test points, that would be a 'muxed dmm' of sorts. then just spray the diff voltages at uppper left, upper right, lower left, lower right of the display. like that. yup, thought about it. even a 'environmentals' page on an amp. place voltage sensors on the rails, temperature sensors near inlet,outlets, if you have fans, add rpm sensors and have the ard. keep track of that. bonus points if you have thresholds and want to alarm (or 'fix things') if an alarm is triggered. welcome to 'enterprise class' audio systems! (semi serious) add in a web-reachable ip presence and you have something really interesting. (make things read-only, though. imagine if someone broke in and set your bias TOO high on you? lol! time to reset my AMPs password. ha!)

well, a lot of the source is 'up there'. http://www.netstuff.org/audio - start there and (for now) click on the large text names of the projects and that will send you to the firmware source area. its a mess right now (org and code wise) but at least the code does run and once its integrated (more libraries, less inline stuff) it will be a lot more manageable. it has lots of comments in the code and that should help a lot, too, I hope. some of the projects use different levels of the lcd interface. initially, I was following the design of this: AI-1 ("All-in-one") Remote and he had the lcd on the analog pins (as a whole bank, for ease of use in simple 'write to whole port at once' methods). I lived with that for a while and life was good.... until I needed more pins so the lcd got moved around quite a bit as I added different devices that would hang off this chip (the x10 firecracker takes 3 pins, the PGA vol control chip takes 3, i2c 'bus' takes 2, IR takes 1, lcd backlight takes 1 (pwm) and so on. its a balancing act of pins vs functions. ultimately, the port-expander (chip to the right) was called into service to hide the lcd behind and let him do the work for a 'cost' of only 2 common i2c bus pins. deal! I left in the realtime clock from tom's design and even the supercap, as well. tom had so many good ideas, I have to throw a lot of credit his way. we both started some of this stuff in terms of camera remote control and then he took it and expanded on it a whole lot. years later, I stumbled on his web page and that finally pushed me enough to dive into the whole arduino thing. I plan to port his code over (to use the i2c port expander and IR for input) and so there will be a 'camera app' that runs on this platform, as well. so, if you want to start reading, check out tom's page. and his source. and the simplest of mine is probably the motor-pot source code: http://www.netstuff.org/mvc-master/firmware/arduino/ no lcd stuff; just reading the IR sensor for remote button presses (from a sony dvd player remote) and mapping the 4 arrow keys to 2 speeds of up and down, on the motor pot (a fast-up and a slow-up; and down, as well). mute is via a relay and you can enable input selection easily, as well (have discrete leds show the input that is selected).

cheers was nice meeting you at nor-cal meet. you probably saw early samples, there, of all this 'stuff'.

(cough) scuze me. I *am* working on some audio for that system. yes. some PID controllers have a piezo buzzer. I wonder if speech synth is possible? or even sensible (lol). seriously, when you start an espresso shot, its *supposed* to be 24 seconds and you can't watch the clock and also the quality of the shot. it would be nice to *hear* a count down. or something.

hey guys took me a while to find this place. it was under a bunch of socks. I think. anyway, yeah, amb and I have been working on this quite a while, now. I hope people like the software, as well. there's a lot it does right now, and there's still *plenty* of code space left in this chip I've had a web *server* running, web *client*, x10 firecracker (wireless powerline control) and like I said in my first post, some non-audio things, as well. we're hoping it becomes a platform for things that need integrated and common i/o, such as the lcd and an IR input. that, and sample code will get people up and running very fast, we think. we hope there just wasn't much out there that did this kind of thing. I went thru a bunch of closed-source hardware and software partial-solutions - mini boards that did this or that - and got tired of having to work it that way. the arduino 'way' is to release source and make it easy and affordable for anyone to get the source, modify things and push it back into the device. *they* now control what this thing does, not the manufacturer. I kind of like it, this way