Jump to content

Riot Nrrrd

  • Posts

    32
  • Joined

  • Last visited

  • Country

    country-ZZ

Retained

  • Member Title
    Freshman Member
  1. Damien, This new release is nearly unusable for me. I get almost constant red "CPU over" interruptions with it. I'm on a wheezing old MacBook Pro (2006) with 2.16 GHz Core Duo and 2 GB. (Hooked up to Harmon Kardon SoundSticks® via USB.) I already had the settings set for the minimum (256 MB) buffering with Max I/O turned off as well. Luckily I still had a copy of the 0.8.2 "Test A" A/B binary lying around ... it does not have the same problem. No "CPU over" errors happening under the same conditions. :-( In case it helps: -- Audirvana rev. 0.8.2 debug information: Currently playing in standard 32bit float mode Mixable linear PCM Interleaved 0bits little endian Integer aligned low in 0bit, 0 bytes per frame @0.0kHz Hog Mode is on Devices found : 2 List of devices: Device #0: ID 0x11c Built-in Output UID:AppleHDAEngineOutput:1B,0,1,2:0 Device #1: ID 0x116 SoundSticks UID:AppleUSBAudioEngine:harman/kardon:SoundSticks:fd843000:1 Selected device: ID 0x116 SoundSticks UID:AppleUSBAudioEngine:harman/kardon:SoundSticks:fd843000:1 1 available sample rates up to 50000.0Hz 5000.0 to 50000.0 Audio buffer frame size : 14 to 6144 frames Current I/O buffer frame size : 512 Physical (analog) volume control: No Virtual (digital) volume control: Yes Preferred stereo channels L:1 R:2 Simple stereo device: yes Channel mapping: L:Stream 0 channel 0 R:Stream 0 channel 1 1 output streams: Stream ID 0x117 2 channels starting at 1 5 virtual formats: Mixable linear PCM Interleaved 32bits little endian Float @5.0 to 50.0kHz Mixable linear PCM Interleaved 32bits little endian Float @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 24bits little endian Signed Integer @5.0 to 50.0kHz 6 physical formats Mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Mixable linear PCM Interleaved 24bits little endian Signed Integer @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 24bits little endian Signed Integer @5.0 to 50.0kHz -- Audirvana rev. 0.9.3 debug information: Currently playing in standard 32bit float mode Mixable linear PCM Interleaved 32bits little endian Float, 8 bytes per frame @44.1kHz Hog Mode is on Devices found : 2 List of devices: Device #0: ID 0x11c Built-in Output UID:AppleHDAEngineOutput:1B,0,1,2:0 Device #1: ID 0x116 SoundSticks UID:AppleUSBAudioEngine:harman/kardon:SoundSticks:fd843000:1 Preferred device: SoundSticks UID:AppleUSBAudioEngine:harman/kardon:SoundSticks:fd843000:1 Selected device: ID 0x116 SoundSticks UID:AppleUSBAudioEngine:harman/kardon:SoundSticks:fd843000:1 1 available sample rates up to 50000.0Hz 5000.0 to 50000.0 Audio buffer frame size : 14 to 6144 frames Current I/O buffer frame size : 512 Physical (analog) volume control: No Virtual (digital) volume control: Yes Preferred stereo channels L:1 R:2 Simple stereo device: yes Channel mapping: L:Stream 0 channel 0 R:Stream 0 channel 1 1 output streams: Stream ID 0x117 2 channels starting at 1 5 virtual formats: Mixable linear PCM Interleaved 32bits little endian Float @5.0 to 50.0kHz Mixable linear PCM Interleaved 32bits little endian Float @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 24bits little endian Signed Integer @5.0 to 50.0kHz 6 physical formats Mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Mixable linear PCM Interleaved 24bits little endian Signed Integer @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 16bits little endian Signed Integer @5.0 to 50.0kHz Non-mixable linear PCM Interleaved 24bits little endian Signed Integer @5.0 to 50.0kHz -- Looks pretty much the same to me ... [EDIT: Update: After quitting 0.8.2 "Test A", I re-ran 0.9.3 ... now it's not getting the red CPU over errors anymore?!? WTF. Maybe it was just an out-of-memory/swapping problem ... ]
  2. @One and a half: Interesting. Good to know. Now that I think of it, I think my Onkyo has 2 different sets of Burr Brown DACs inside. One for multi-channel and one for 2-channel, perhaps? Maybe that would explain your 192 kHz HDMI-only explanation.
  3. @Jud: I was looking at the mouse-over specs 'behind' the photos, and it seemed to me like most of them (except the S/PDIF converter at the bottom, which elcorso just mentioned) only did 24/96, not 24/192. e.g. both the Brick Triode and Proton models say 24/96 when you mouse over.
  4. Thanks Bob (and elcorso). I was pretty sure that TOSlink was uni-directional but didn't want to guess wrong and look like a fool @elcorso: "You need an USB/SPDIF interface [that is] 24/192 capable, and to get Integer [Mode] you need on 24/192 the WaveLink or V-Link." I looked at http://www.usbdacs.com/Products/Products.html but didn't see any USB DAC on there that does 24/192 kHz. Am I being dumb?
  5. I've mentioned this before but I'll restate it a different way. I have an Onkyo TX-SR876 receiver with 24-bit/192 kHz Burr Brown PCM1796 DACs inside. But if I hook up my Mac Pro to it via TOSlink/SPIF optical out, Audnirvana's debug output only shows me values up to 96 kHz. Is this because Audnirvana can't detect the DACs inside the Onkyo over the optical link, or because the Mac Pro's optical link doesn't support over 96 kHz? In other words, is the only way to get 192 kHz via an outboard USB DAC? The Flat Earther
  6. "why do forums start with the first post, often years ago, rather than the latest. This is simply retarded." Besides the fact that it's easily changed, are you Jewish? Do you read normal text backwards? It's not "retarded" in the slightest. Most posts reference previous posts, why would I want to see the later post without seeing what it referenced? To me "Newest post first" is the "retarded" way. -- So as not to be content-free, I'm disappointed that Damien's A-B-C test didn't include a "placebo", i.e. one of the 3 only with a couple of code lines swapped, i.e. just enough to make the binaries be different but clearly not enough to make the sound change. You could predict that the number of people who would've chosen the original vs. the placebo would be exactly the same. It's harder to make generalizations about the results of the A-B-C test without a placebo in play - which would also help eliminate the "I could swear I hear a difference between them" responses.
  7. OK you two, outside on the railroad tracks behind the school at 3 o'clock! We'll settle this like men. lol -- Side tangent: I notice many of you have outboard DACs. Is it safe to say that you all use them because you use pre-amps and/or amps instead of receivers? (I have an Onkyo TX-SR876 receiver with Burr-Brown 192 kHz/24-bit audio DACs built-in, so I don't think I need an outboard DAC) The Flat Earther
  8. "In fact, the 0.8.2 build is made with gcc..." hahahahahahahahahahahahahahahahahahahahahaha .... I rest my case (I still think multiple A/B/x tests are good, Damien ... hope you will take the time to do them) - The Flat Earther
  9. @wgscott: "The point of the wine article is that expectations can actually lead to physiologically-based changes in perception. There are clear physiological reasons why the differently priced samples tasted different, and those physiological changes are triggered by mental states (expectations). If you substitute speaker cable pricing for wine pricing, you can see how your ears may genuinely hear a difference." Absolutely right - and for a very similar example, you should all watch Penn & Teller's "The Truth About Bottled Water" segment: http://www.youtube.com/watch?v=XfPAjUvvnIc I could produce similar links for posts by Audio/Videophiles who swore up and down that Lexicon's rebadged Oppo BDP-83 really did sound/look better than the Oppo, before it was exposed as being a fraud. The Flat Earther
  10. [The computer geek in me thinks this whole thing is hysterical. Algorithms are algorithms - if Damien's code has a function that returns a truth value, it better return the same value whether it's GCC or LLVM at any optimization level. While individual instructions can be different due to different compilers and/or optimization levels, at a function call level it all better work the same.] I would argue that the test should be made even simpler: (1) Plain GCC (2) Plain GCC but with a different level of optimization used (perhaps -O2 instead of -O, etc.) (3) Plain GCC but with a few lines of code that are execution-order independent switched around, so as to produce a slightly different but essentially the same binary (4) (Optional) LLVM padded to the same size as one of the other choices If you are going to argue that a GCC-built version sounds different than an LLVM-built version, then similarly a binary built with a different optimization level should sound different. Right? Signed, The Flat Earther
  11. I keep hearing people talking about using outboard DACs (like Musical Fidelity's V-DAC) in these posts. I have an Onkyo TX-SR876 receiver. It purports to have "Burr-Brown 192 kHz/24-bit audio DACs". Those are supposed to be pretty good, right? Should Audirvana be 'seeing' those internal Burr-Brown DACs on the receiver (when hooked up via the TOSlink Digital Optical Audio Out port on a Mac Pro) and correctly identify them? And enable whatever high-resolution (96? 192?) support the player has built in to it? [Disclaimer: I'm a computer geek, not an Audiophile™. You've probably already guessed that by now. lol]
  12. @church_mouse David, are you having the problems with Audirvana when you aren't running iTunes as well? I've got an old MacBook Pro with only 2 GB of RAM as well, and so far I've only seen Audirvana put up the red CPU overload indicator once - but I'm probably not using it anywhere near as much as you are. Also, I have never run Audirvana as the only program running - I usually have at least Mail.app and a Web browser and Terminal running. Can you identify your Mac mini from the list on this page? http://support.apple.com/kb/ht3476 If you could increase the RAM from 2 to 4 GB it would probably be a big help. Also, is this happening to you when Audirvana is the only program you have running? If that is the case, you might want to try running Activity Monitor (from your Applications -> Utilities folder) and experiment with sorting on the Real Mem and Virtual Mem columns. Watch the behavior over time as you play things. See whether or not you can see the numbers grow for whatever is at the top of the sorted lists. Also check out the System Memory tab at the very bottom of the window; see what you have for "Free" (in green) and "Inactive" (in cobalt blue). If you are only setting Audirvana to use 256 MB and have nothing else running, it's pretty surprising to hear that you are having CPU overload issues. The most common impact on running programs is when memory is exhausted and the system has to page memory pages in and out of memory to/from disk; if you can avoid that, it's far more likely that you can avoid the dreaded red indicator.
  13. @Jud: Well, most of the OS is 64-bit, but actually the kernel by default is 32-bit in order to run 32-bit compatibility kernel modules. If you don't need the modules, you can choose to run the kernel in pure 64-bit mode. I did some research, and it turns out we're both sort of right http://support.apple.com/kb/ht3770 says These Macs use the 64-bit kernel by default in Mac OS X v10.6: - Mac Pro (Mid 2010) - MacBook Pro (Early 2011) These Macs use the 64-bit kernel by default in Mac OS X Server v10.6 (they can also use the 64-bit kernel in Mac OS X v10.6, but do not use it by default): - Xserve (Early 2008) and later - Mac Pro (Early 2008) and later - Mac mini (Mid 2010) These Macs support the 64-bit kernel, but do not use it by default: - iMac (Early 2008) and later - MacBook Pro (Early 2008 through Mid 2010) That said, I still think your findings are trippy, but then we can't argue with our ears, can we?
  14. @Mercman "how about $695 for Amarra?" I could say something but I think PT Barnum beat me to it For $695 it should perform every feature that Pro Tools has, plus playback. "Thanks for letting us know that you never tried the program." I've owned/tried - MacAmp Lite X - Audion - SoundJam - iTunes - Vox - Songbird - Audirvana - Decibel How many more of them do I need to try/own to have an opinion on their pricing? All of these (save perhaps Decibel) were free or relatively low cost. But throw in 96/192 sampling and all of a sudden it's worth almost $700??? If you ask me, by providing a good "audiophile player" in Audirvana as DonationWare (so far), Damien has really thrown down the gauntlet to the other players in this space.
  15. @Mercman: "I think you should spend a little more time looking at this program before you trash it." Just to be clear - I'm not trashing the program (as I've never used it). It might be quite good at what it does. I *am* trashing the idea that a software playback-only program should be $129. I noticed that they have a program called Pure Vinyl® as well. It appears to be a "Pro" type of Audacity-like program. I think the case can be better made for programs like these costing a bit of money.
×
×
  • Create New...