Welcome, Guest
Username: Password: Remember me

NOTE: This is a "Community" forum. Please be mindful that community members are here to help as part of a community effort. We therefore appreciate your effort in keeping this forum a happy place!

If you have a specific issue (e.g. hardware, failure) and want help from our support team, please use our tech support portal (Support menu - > Contact Us).
Thanks a lot of your help in making a better community.

TOPIC: Please, please, please.....

Please, please, please..... 2 years 1 month ago #33346

  • captgnarly
  • captgnarly's Avatar
  • Offline
  • Senior Boarder
  • Posts: 60
  • Thank you received: 15
  • Karma: 5
Dear miniDSP, I know it's been said FIR filenames display would get added into the openDRCs, like in the DA-8 (or ICE amps.)

This would make such a difference in usability for me.
The lack of filenames is driving me nuts !!!!

I just bought my 4th openDRC.......I experiment a lot, on a number of different 4 way speaker systems.
I love the sound I can get with the openDRCs, but it's getting to be as hard to associate/keeep track of, files that work together,.........
as it is to take measurements, and build FIR files !

Please help miniDSP,
Thanks ! Mark
The administrator has disabled public write access.
The following user(s) said Thank You: neatlyfolded

Please, please, please..... 2 years 1 month ago #33389

  • devteam
  • devteam's Avatar
  • Offline
  • Administrator
  • Posts: 8533
  • Thank you received: 1052
  • Karma: 157
@ Mark

It's a valid idea/requirement. We can see in the future how to make this happen.
The problem is that we don't sync data from BOX back to software.. So that would be an issue as you loose your XML file as you switch from one box to the other. Do you see what we mean?
MiniDSP, building a DIY DSP community one board at a time.
The administrator has disabled public write access.

Please, please, please..... 2 years 4 weeks ago #33406

  • captgnarly
  • captgnarly's Avatar
  • Offline
  • Senior Boarder
  • Posts: 60
  • Thank you received: 15
  • Karma: 5
Hi Devteam, thank you for a quick reply.

I understand that the data cannot be synced from the BOX back to software.
But it appears the software, when first connected with the BOX via the green button, checks to see if any changes have been made between the chosen Config slot and the box.
My experience is that if no changes are found, a connection is made without any need for further synchronization, and then changes made in software also change the box in real time.
If changes are found, a Synchronize Config is necessary to load the software into the box.
Correct so far ??

So in either case, whether no changes are found, or Synchronize Config is necessary, whatever the FIR filename is in the software,
IS or BECOMES the FIR filename that's in the BOX.

It seems all that's needed practically , is for the FIR filename to stay present in the software, like when it's first loaded into the software.
Am I missing something?

BTW, the best method I've found to help keep things straight so far is to keep BOX 1 using Config 1, BOX 2 using Config 2, ......3 to 3, and 4 to 4. (So I only use 1 Config slot per box.)
This way if I only make changes when connected real time, whatever box I plug into the laptop simply connects without needing to go through Sync Config.
Once again, if the FIR filename simply stayed visible in software, all is good.. :)
The administrator has disabled public write access.
The following user(s) said Thank You: devteam, pos, neatlyfolded

Please, please, please..... 2 years 4 weeks ago #33408

  • pos
  • pos's Avatar
  • Offline
  • Platinum Boarder
  • Posts: 346
  • Thank you received: 196
  • Karma: 39
captgnarly wrote:
BTW, the best method I've found to help keep things straight so far is to keep BOX 1 using Config 1, BOX 2 using Config 2, ......3 to 3, and 4 to 4. (So I only use 1 Config slot per box.)
That is a nice tips, will definitely use it :)
download the last version of rephase here: rephase.org
The administrator has disabled public write access.
Moderators: devteam