Upgrade from Local Mode to Network Mode database

mattauckland · December 10, 2015, 12:25am

Hi,

This is a preparation thread for me, as I’m planning to move from a mAirListDB Local mode, to a network mode database shortly.

Is is possible to upgrade/port my existing database over, so I don’t have to start from scratch? I’ve been reading the 3.1 manual as reference.
When working from a networked computer using mAirList, do I need to map the storage drive of the system that hosts the audio files and PostgreSQL database?

Thanks

Torben · December 10, 2015, 8:31am

Use the new “clone database” feature found in the “Database -> Export” menu inside the mAirListDB app. The destination DB must be an existing but empty PostgreSQL database (do not create the schema before you clone!).
No, you can also use UNC paths.

mattauckland · December 10, 2015, 12:07pm

Thanks Torben, I’ll give that a go.

The audio drive is local to the other machine that runs mAirList, but obviously not to mine. I only asked because on other Playout systems I’ve used you normally either have to invoke virtual paths, or map the drives.

Torben · December 10, 2015, 12:39pm

Using the same drive letter on all computers is often a good idea, but not at all necessary.

The “default path” of all storages is stored in the DB configuration. That’s what you enter in the DB Administration dialog on the “Storages” tab.

In the playlist item records (“items” table in the SQL database), only relative filenames are stored, without the storage path at the beginning.

If, for any reason, the audio path is different on a particular computer, you can go to mAirListConfig -> Databases -> Properties -> Storage Redirection, and enter the local path which will override the default path on that machine.

mattauckland · December 10, 2015, 12:53pm

Gotcha, just what I expected. Thanks!

mattauckland · December 13, 2015, 11:07pm

Hi Torben,

I’ve received the following error when running Clone Database to my PostreSQL server:

If you Ok it, it doesn’t say its completed the task correctly, so I’m not sure if it is safe to use.

Torben · December 14, 2015, 6:47am

Hm, not sure at which stage this happens.

Can you please try again (into another empty database perhaps), and when the error message occurs, click Details and send a bug report.

Another tip: You can just press Ctrl+C on these error dialogs, and the message will be copied to the clipboard as text, much easier than a screenshot

mattauckland · December 14, 2015, 12:59pm

Did the same the second time around, so I’ve sent you the bug report as requested.

Torben · December 14, 2015, 1:56pm

Turned out that there is an extra column in database files that have been converted from an earlier schema version (22).

Easiest fix is to edit the *.mldb file with “DB Browser for SQLite”: http://sqlitebrowser.org/

Edit the table “playlist” (select table from list, then click “Modify table”), and remove the field “starttime”. See attachment.

mattauckland · December 14, 2015, 3:10pm

Thanks Torben, that fixed it!

Now the database server is up and running, I just want to quickly check the Storage stuff.

Because I was previously running a local db, the storage locations under the Storage tab in Database Configuration, have been set locally.

So for example I have Music storage, which Default location is set to D:\Music being the local drive of the studio/automation computer.

But, as I’m going to install a client on my desktop using the database server, do I need to change the storage locations on the studio machine to use network paths (UNC) instead?

Torben · December 14, 2015, 3:35pm

Doesn’t matter actually. Just make sure that the files are available on all clients under the same path. So you might for example share the D: drive on the network and map it as D: on the client. Or use UNC paths. Or even use storage redirection on the client to override the path.

bulldogdave · December 15, 2015, 11:18am

Hi, ive been having a similar problem for a while but have taken no notice. I have sent a bug report to see if it is the same problem.

mattauckland · December 31, 2015, 3:43pm

As an update, I opted to map the storage drive on the Playout, to the same drive letter on the Production (desktop) machine.

It’s a simpler option, and my internal network consists of cat6 cabling and a 1Gbps D-Link switch, so there’s no lag on the network.

Also for voice track it makes sense, as the recorded voice track files (which I do on Production) will need to be saved on the Playout storage drive, otherwise I would guess the VO would fail. But that’s an assumption.

Needless to say the setup is working fine. Thanks Torben!

I’m planning on producing short mAirList English tutorial videos for YouTube in 2016, starting in February. Covering things like initial set-up, configuration, tips, and so on.

I’m still learning the software myself, but I hope that these videos will help other users too.