To them, those might be real reasons based on facts.I don’t understand why people are making excuses for MiniDSP.
After thinking about it since we had the time with the delay, when the Tide16 gets native 2.1, I’ll reconsider.
To them, those might be real reasons based on facts.I don’t understand why people are making excuses for MiniDSP.
After thinking about it since we had the time with the delay, when the Tide16 gets native 2.1, I’ll reconsider.
Yes. The channel config in Dirac is fixed at the calibration step and it will reject any modifications one tries to enable before it in the signal path.I believe the matrix mixer isn’t locked until Dirac filters are loaded. So these could be set up in advance of running ART but would not be editable after. That’s how I read the manual anyways. We won’t know for sure until it ships.
Maybe one day, in theory. MeantimeDo you need Dolby / DTS / immersive audio decoding?
Does the Tide 16 (due to Dirac) sample everything to 48khz or is it extended to 192khz?Maybe one day, in theory. Meantime upsampling
Its all done at 48kHz.Does the Tide 16 (due to Dirac) sample everything to 48khz or is it extended to 192khz?
Yes using Dirac requires all DSP to run at 48kHz.Does the Tide 16 (due to Dirac) sample everything to 48khz or is it extended to 192khz?
Does the Tide 16 (due to Dirac) sample everything to 48khz or is it extended to 192khz?
Note my use of that last word was mistaken.Maybe one day, in theory. Meantime upsampling
I have a PS5. What I’m doing now with the XMC2 (G3P) is that I need to connect the PS5 directly to my 83G4 and eARC to the XMC2.What in your use case requires 2.1, I don't believe that I have need of it?
Well, I do have recording that are in 96khz and 192khz (straight from the producer) and it's nice to play them at their native sample rates.Yes using Dirac requires all DSP to run at 48kHz.
This allows for the exponentially higher taps count / processing power required by its automated phase correction and complex time-domain corrections, especially at lower frequencies.
If you want higher resolution - why?
or to use other less automated more precise FIR filter creation tools, then you must disable Dirac.
Dear All, Great news is coming up.. Testing all finalized and the positive feedback we were waiting for from one of our partner just came in.
Just some minor tidying up, some clearing of some log files, and we're planning to release access to the shopping cart early next week. Units are already in QC stage. :love:
Thanks again for all your patience! An exciting page turning.
DevTeam
PS: Tmr is National holidays for us so we'll be back on Monday with more feedback.![]()
The only three inputs will simply be the switch chip is cheaper exactly the same applies to the Lyngdorf MP 40, which incidentally does have HDMI 2.1 but has a list price of 10k87 pages, time to summarize some of the repeated/repeating points made?
Note: "Reasons" to some might mean excuses, though imo, in some cases, when it comes to cost and time it is hard to distinguish between the two.
Reasons why miniDSP Tide did not offer the latest HDMI:
![]()
Understanding HDMI 2.1 vs 2.0 on Tide16
This is a great topic—and one that really deserves a deeper explanation, which is why we put together this FAQ. Since the launch of Tide16, one of the most common questions has been: “Why didn’t you include an 8K HDMI 2.1 module? You already had...support.minidsp.com
Reasons why only 48 kHz sampling rate:
![]()
Why is Tide16 only 48k? Why not 192kHz?
As much as we’d love to crank the sample rate as high as possible, it’s just not that simple. Most decoding and upmixing stages run at 48 kHz because that’s what the decoding libraries expect. It’s also the standard rate used by studios when th...support.minidsp.com
The links are for the FAQ's by miniDSP.
Note that their FAQ hinted (my interpretation) there might be hope? It said "Does this mean there will never be higher sample rate on Tide16? That's not what we said.. ;-)",
Also mentioned may times:
- only 3 HDMI inputs (have not seen any official reasons given, but I guess no need because at least the main reason is obvious..) Also, their forum admin said: "For your second request about HDMI. We do have a plan for linking up a Vroom but it's not yet ready. It will allow you a)have lot more inputs b)have a seemless switching c) have 8k for all those of you who need 8k. No timeline but it's coming. In the mean time, the feature of using one button changing source/settings/presets is already there. Please check out the scene selection."
- no Asychronus USB input for multichannel audio (https://www.minidsp.com/community/threads/tide16.24083/page-8#post-76667)
- HDMI does not do DSD, forum admin said: "DSD is planned but for V2. Right now we only accept PCM"
There are a few more Q&A that might help some deciding, but it takes time to search them out so I will update this post in the next few days.
I am doing this now because it is getting close, they finally seem to have committed to a date for "access to the shopping cart", whatever that means!
Tide16
Good eye, we'll edit that typo in the manual. Thanks for warning! DD+ is the lossy version and can indeed support ATMOS. With all the talk of everybody that complains that we're not supporting HDMI 8k, we're now talking of a support for ATMOS + ARC, on a very old standard by now.. Hard to please...www.minidsp.com
Pretty much anyone using room correction with any AVP/AVR is having their source content resampled. It's a non-issue as the benefits of room correction and sub integration far outweigh the benefit of sample rate preservation in most cases.Well, I do have recording that are in 96khz and 192khz (straight from the producer) and it's nice to play them at their native sample rates.
I get it, it feels like you’re throwing away something you paid for when you down sample to 48khz. That said, if you’re using a high quality SRC, it really should be not audible for us humans. Roon has a great SRC. If you have something like Roon, just set it to convert everything to 48khz, including RedBook CDs. Back in the early days of digital it did matter because by using a higher sampling rate the digital noise was shifted to a much higher frequency and the DAC output stage could use filters that were less steep and arguably better sounding. Today most DACs deal with this internally so it’s not an issue. The benefits of Dirac far outweigh any damage from the SRC and it’s much more beneficial to let Dirac run at a lower sampling rate if it’s implemented on a processor with limited throughput, like we find in most any AVP or AVR. Some of my best sounding recordings are RedBook CDs. The higher sampling rate versions of many recordings do sound better, but I would speculate this is more because of careful mastering using the best possible original material and not because the version is at a higher sampling rate. The 24 bit words do make a bigger difference, but that’s not an issue with Dirac.Well, I do have recording that are in 96khz and 192khz (straight from the producer) and it's nice to play them at their native sample rates.
Only psychologically, there will not be any audible difference downsampling even if you didn't need to do so in order to manipulate the signals via DSPWell, I do have recording that are in 96khz and 192khz (straight from the producer) and it's nice to play them at their native sample rates.
It's a non-issue as the benefits of room correction and sub integration far outweigh the benefit of sample rate preservation in most cases.
The benefits of Dirac far outweigh any damage from the SRC and it’s much more beneficial to let Dirac run at a lower sampling rate if it’s implemented on a processor with limited throughput, like we find in most any AVP or AVR.
It's difficult to argue with any of that, but I'm going to have a go anyway (again), even if it's only dogmatic philosophy.Only psychologically, there will not be any audible difference downsampling even if you didn't need to do so in order to manipulate the signals via DSP
Even though a few of my favorite-sounding albums are 16/44.1, I'm with you.It's difficult to argue with any of that, but I'm going to have a go anyway (again), even if it's only dogmatic philosophy ........................................................................ I know I won't win this argument, but I don't care.
Who exactly is "we", and why do you require PEQ on inputs and FIR on outputs? Please specify your output requirements in more detail.No PEQ on inputs to start with is very disappointing. If there's no possibility for FIR for crossover either, it's not the product we're looking for unfortunately.