TOPIC:

The words "synchronize" and "restore" confuse me, because I presume that there is a source configuration that we get our data from, and a destination that this data is written to, but neither word lets you know which location is which, only that one word means that the information flows the reverse direction of the other, I guess.

What I'm trying to do is to pull the configuration off my minidsp and load it back into the software. I do not want to overwrite the currently-running configuration, nor do I want to restore it to factory. My minidsp is already configured and I want it to stay that way, and I also want to be able to view that configuration after I've had to reformat my PC and reload everything on it.

How do I get the settings off of the minidsp and back into the software?

Sorry to have to say that you cannot extract a configuration from a MiniDSP. It is one way traffic only.

I'm late to the party but I feel like I have to say that.. sorry...
How stupid is it that a can't read the settings from my minidsp..
What if a did a 2.0 2way setup with filters for every tweeter and woofer and forget to save the settings befor disconnect?
Do all that measurement und setup shit AGAIN? Seriously?

ener85 wrote:

How stupid is it that a can't read the settings from my minidsp..
What if a did a 2.0 2way setup with filters for every tweeter and woofer and forget to save the settings befor disconnect?
Do all that measurement and setup shit AGAIN? Seriously?

Sorry, I don't see your problem?
You create the filter setup you want in the miniDSP plug-in, on your computer.
Then you save it (to your computer). Frequent 'Saves' is standard practice when using a computer IMO.
Then you upload the plug-in to the miniDSP unit (ie. 'Synchronise).
If you then make changes to the plug-in while the miniDSP is still connected - sure, you have to remember to save the plug-in. But as I said - this is 'good practice'.

What would be very useful AFAIAC is if the name of the plug-in file that was loaded into the miniDSP unit (or a particular Config) was displayed when you connect the computer to the miniDSP unit (or Config).

Andy

my problem is, i changed my media pc and i wasn't thinking i have to save the settings because i used a dsp in my car in the past and there i didn't have to worry about something like that.
That dsp ask, write to dsp or read from dsp.
I was thinks thats standard for dsp's...

#metoo
Syncronize? Restore? What? Restore from what to what? Syncronize which way? 
Press help and you get a wall of text that does not clear things up.
It should STATE CLEARLY that it is not possible to recover any settings/data from a 2x4HD. 
How hard is this. 

Quite agree with the original poster - the lack of the ability to find what configuration is stored on an active Mini-DSP system by being able to download the configuration back to the software is very very poor. I know it's likely part of the reverse engineering protection and licencing, but because this limits the ability to manage several devices with different settings in a pool, it's one of the reasons I've only bought one kit to use. Sticking Dymo labels on multiple boxes with the filename last loaded is not a professional way of working.

Synchronisation implies a two-way handshake/comparison process, what is happening here is uploading or firmware flashing in most peoples minds - synchronising it is not.

so If I save the xlm file from file export ,then  I am able to reload settings in case of minidsp breakdown or new pc?

This caught me out on my ddrc88a the other week. I wanted to check something on the config and because there was a mismatch between the plugin and the hardware I ended up loosing my previously good set-up. Painful as it included an MSO config of the subs. 

Anyway lesson learnt. Once set-up again I've saved the final config on my drive along with the dirac and MSO projects, all more clearly labelled and with notes on how I got there for an easier recovery. 

At the end of the day, the thing you have in your hand is the DSP device. Trying to work your way back to the original PC used to programme the device with the correct DSP parameters is a nightmare. Why could the designers not incorporate a bit of extra EPROM to store a readable configuration stored on the device?

My original idea was to provide a pre-programmed pool of 2x4 units with the sort of parameters that would provide a useful starting point for the EQ and delays needed for a simple live sound gig at a particular venue. I'm UK based so imagine small village hall with a visiting folk band. A simple setup providing Front of House or floor wedges, Back Line and audience sound reinforcement with delays as needed, all matched to the individual venue (or as near as possible) based on the experience gained from previous gigs. This would give a starting point before final tweaking on the desk so saving time or aiding an inexperienced operator.

Alas, with the way MiniDSP chooses to operate their software this would probably be unmanageable.