Jump to content

weff

  • Posts

    11
  • Joined

  • Last visited

  • Country

    country-ZZ

Retained

  • Member Title
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. There is also an error regarding the Mytek Digital Brooklyn ADC actual capabilities not the marketing spec of planned capabilities some time in the future. As of the 21st October 2017 the Brooklyn ADC : "From analog inputs XLR and TRS ... PCM 32 / 384 kHz can be recorded but DSD recording will be activated (firmware update) within a short period of time". (as advised by Mytek Digital recently.) This has been the state since July 2017 and unfortunately there is as yet no DSD support at all. It is being worked on is the only message I have received since March 2017 when I first asked and was about to place an order for a Brooklyn ADC. It might be the world's best PCM recorder - but when you want to purchase a DSD256 recorder if DSD functionality is not working then I don't wish to purchase a DSD256 recorder that cannot yet record DSD at all. After this length of time, since the Brooklyn ADC was first released around a year ago, it is quite discouraging that there is still no indication of when DSD support will be enabled with a new firmware update. There is no indication either that this is tied to MQA support for the ADC and they possibly won't release one without the other - I don't especially want (or need) MQA in the Brooklyn ADC - and I would have DSD support over MQA any day but clearly there is some intractable issue that is preventing the Brooklyn ADC from recording in DSD.
  2. Correction to the above - As a non-subscriber I can see technical data up until Feb 2014. Despite not being able to purchase the Aug 2014 Hi Fi News edition by itself - I did come across a pdf in Google - although not having access to the full data report it is hard to make proper sense of what the limited test data in their review copy means.
  3. It's a case of pay to read either the download copy from Apple Store - or a hardcopy of the magazine. As a non-subscriber the available review data is only from 2012 and earlier. I'm surprised that a detailed test review could even be prepared by this point - what with magazine lead times being 1-2 months. They certainly can't have tested with the latest DAC firmware - and I would have to wonder what burn in they did prior to the review ? Though what difference either of those factors would make to the measurements ?
  4. PS Audio website extract: " Unlike other processors available today, DirectStream unifies all inputs (PCM or DSD) at 10 x DSD, then uses a true single-bit double-rate DSD core engine." PS Audio basic description of the DirectStream states: "The DirectStream is a remarkable DAC that is pure DSD in operation"
  5. As far as the documentation on the PS Audio website shows DSD is upsampled to 10xDSD then back down to DSD128 as a core engine in the DirectStream. It is a purely DSD path with PCM inputs being converted to DSD as well.
  6. Hi Michal, I have mailed at mytek email 'Michal Jurewicz' <[email protected]> - and as described there, and confirmed by Miska at Signalyst the problem is that in Windows 7 64bit HQPLayer in ASIO mode the RigiSystems driver sees zero DSD channels and hence cannot playback DSD128 or DSD64 content. In WASAPI mode driver I am able to playback DSD64 with added staticy horrible noise. In WASAPI mode am able to playback PCM and actually have some music. Primarily doing this with firewire currently as that is more reliable. Have tested basic PCM functionality with USB1, USB2 as well - but DSD128 has always been my target application. I also tested Windows 7 32 bit mode with HQPLayer ASIO driver and was able to playback DSD64 and DSD128 - so just have to wait for corrected drivers for Windows 7 64 bit. So no, does not appear to be a hardware issue other than with the driver/firmware. I look forward to the next version that may resolve some of the issues. Regards Geoff
  7. Hi Michal, Thanks for the feedback - am appreciative of the time you are able to spend updating us on the forum with Mytek happenings. I was curious about the process of building the Weiss driver for Mytek driver compatibility - not so much in doing it myself as the only useful solution is the real Mytek driver as that alone will get the DAC working as intended. As to my system - currently trying to integrate a Windows 7 x64 system with the DAC with the intention of using that to playback DSD128 content recorded on a Korg MR2000S - the incompatibility with Windows 7 x64 and the ASIO driver being the main sticking point currently. Using HQPlayer (from signalyst); also have Jriver but HQPlayer the main output player currently. I appreciate that the development is going to take time - so perhaps periodic releases (every month or 2) of interim drivers/firmware (bringing new options online, or fixing some of the more serious bugs) could be a way of easing the pain - provided that doing such doesn't unduly impede ongoing development work and that accepting users take the driver/firmware on an as-is basis. (With "official" drivers to fall-back to as needed.) Similarly a short bulletin (every few weeks) indicating current driver/firmware version and planned interim driver(&change) will keep everyone informed without being too onerous. Something to consider at least. Regards Geoff
  8. Hi all, Being a Windows 7 (64bit) user I am curious to find out more details of the weiss 7_64 driver - as there are so many directories at the dice site - none of the multiple I found lined up with the expected contents. Which actual directories on that site contain the relevant code and some more detail of the actual build process would be appreciated. What I would really prefer of course is the Mytek version of the version 4.0.0 Dice driver - or (better) a version of the ASIO firewire/USB2 driver that recognises the Mytek under Windows 7 64bit so that DSD128 works. I can't run under Windows 7 32bit environment where I've tested and it works so I'm really hanging out for the proper drivers. I know I should be patient and just wait for the Mytek driver - but the sparsity of progress messages these days makes it seem as if no progress is happening. Even another interim driver/firmware from Mytek would be welcome if it progresses functionality even with known bugs. Thanks have to go to ted_b and others assisting with the driver testing - but any little tid bits of Mytek happenings now that Mytek has gone quiet would really be appreciated. Regards Geoff
  9. I checked my circuit board for the cut trace needed for version 1.32 firmware and the mod had already been made. I also tried out the 1.38 firmware - with dsf files from my Korg MR-2000s (capturing some vinyl) and for the first time I noticed the static noise interference moving across the sound stage. Reverting back to 1.32 firmware eliminated the problem. I've currently only got around 15-20 SACD discs - so have not attempted the ripping via a PS3 (not really cost-effective for me) - so the dsf files I've been previously listening to on the Mytek are from the Korg vinyl captures - or else downloads from sites like 2L. So far, via firewire HQPLayer 2.7.5.2 (WASAPI) has played them ok with 1.32 firmware. I have to wonder whether the problems being reported currently are endemic to the PS3 rips - and not to native dsf files - or are across the board? The PS3 rips, being so new, may yet have a structural defect in them that induces this static noise and that in attempting to counteract it Mytek are introducing errors that prevent correctly structured dsf files from being played back. What I am also waiting for is for the ASIO driver to be fixed so that I can listen to the captured vinyl DSD128 files from the Korg.
  10. Thanks ted_b, That explains why I never found the drawing - as my Mytek came delivered with 1.32 firmware - I never expanded the 1.32 firmware package to discover the "missing" mod info. Hopefully, already having 1.32 firmware on delivery (late 2011) - this may mean the mod may have already been applied. I will see if I can see the mod already applied and report back. Thanks again. Geoff
  11. Hi Ivan, This is about the 4th time someone has mentioned the hardware mod for the Mytek Stereo DSD - but without explaining what is needed. My unit shipped with 1.32 firmware - does this mean the hardware mod has already been performed ? Is there an easy way to check whether the mod has already been made or not ? If it involves cutting a track on the circuit board - then I would expect there should be a document with pictures of before and after on the Mytek Digital website - but haven't seen anything like that there yet. Thanks for any help you can provide. Geoff
×
×
  • Create New...