Page 2 of 11
Posted: Mon Jun 02, 2008 9:06 am
by nynaevelan
MoDementia wrote:If you fluked that the new tracks have the same Songs IDs in both libraries yes it will continue to work
Ok, I'm a little confused. Although the tracks are located on the drive they are not "put" into the library until I complete the Import Sync, so they should always have the correct SondID right??
Nyn
Posted: Mon Jun 02, 2008 9:32 am
by MoDementia
New tracks aren't imported, just logged that there are new songs that should be added.
Posted: Mon Jun 02, 2008 9:51 am
by nynaevelan
Ok, that's what I needed to know, as long as the SongID is being imported with the IS, then my current practice should be sufficient. With the creation of this script, I prefer using the Export Sync/Import Sync as my daily/weekly processes, I would like to avoid using the Export Complete DB as much as possible because my db is getting large and it is time consuming to download it from my networked drive.
Nyn
Posted: Mon Jun 02, 2008 10:07 am
by MoDementia
New Version
' 03-06-08 Version 1.5
' Optional Export/Copy New Tracks for complete exports.
Posted: Tue Jun 03, 2008 6:33 am
by MoDementia
New Version
' 03-06-08 Version 1.6
' Clear Last Imported Tracks (Need Synchronisation) once synchronised.
I have left the version 1.5 link there just in case the node isn't always 100% accurate with this version
Posted: Thu Jun 05, 2008 9:41 pm
by MoDementia
New Version
' 06-06-08 Version 1.7
' Supports Month, Day and Original Month, Day (Requires 1183 or Greater)
Posted: Tue Jun 10, 2008 5:13 pm
by nynaevelan
MoD:
Keep in mind I gave you a whole 5 days off
Would it be possible to have a report of what is going to be exported before the export is actually started??
Nyn
Posted: Tue Jun 10, 2008 5:20 pm
by MoDementia
A node of tracks changed since the last export?
or
How much detail do you need in the report?
Posted: Tue Jun 10, 2008 5:27 pm
by nynaevelan
The same info that is in the log now. I am getting some large numbers on my work computer and I am trying to figure out if this is because of the timestamps or something else. All I do on my work computer is play songs so the only differences should be the today's songs. But I did a lot of editing on my home computer over the weekend so I am trying to research to see if that is what is causing the large exports at work.
Nyn
Posted: Tue Jun 10, 2008 5:34 pm
by MoDementia
If you have done a complete export from home, yes all the changed dates will be > than the last export at work
Umm I won't be able to look at it until tomorrow.
in the mean time, you can do a dummy export (complete one is quicker) at work after a complete export overwrite
or
change the mediamonkey.ini section DEISync lastexportdate (I think thats what its called)
[EDIT] Yes there will be more exported tracks but they won't change anything at home. The import log should only have the tracks that have been played.
[EDIT]Ah I think I see, the import is changing the dates making them match criteria for the next export. Interesting
Posted: Tue Jun 10, 2008 5:44 pm
by nynaevelan
MoDementia wrote:
in the mean time, you can do a dummy export (complete one is quicker) at work after a complete export overwrite
I'll give this one a try in the morning after I import the file, that should ensure it is working as I need. Don't start working on this until I get back to you, a pre-log might not be necessary if this works as I think it should.
Nyn
EDIT: Ok I will not need a log report, I will just export a full db on my work computer after each time I import a full database to ensure I am only getting the days changes.
Posted: Wed Jun 11, 2008 10:53 pm
by MoDementia
New Version
' 12-06-08 Version 1.8
' Check for outstanding exports before importing (Cancel will just Reset Last Export Date. Use when overwriting with Complete Export)
' Reset Last Export Date After an Import (Import changes are't included in next export)
@ Nyn
You should no longer get large numbers when exporting sync at work
If you overwrite the database at work with a complete export run Import Sync at work (after overwrite) and click cancel to reset the export date.
Posted: Thu Jun 12, 2008 12:40 am
by nynaevelan
MoDementia wrote:
@ Nyn
You should no longer get large numbers when exporting sync at work
If you overwrite the database at work with a complete export run Import Sync at work (after overwrite) and click cancel to reset the export date.
Worked perfectly but when I try to import the exportsync to my home computer, I get this message, both are running 1183:
Nyn
Posted: Thu Jun 12, 2008 12:54 am
by MoDementia
Line 1181 isnt a line that would produce this error
The code around there is
Code: Select all
If objSongData.PreGap <> Clng(iter.ValueByName("Pregap")) Then
ImportLogStringList.Add(ImportLogInfo & "Pre Gap" & Chr(9) & objSongData.PreGap & Chr(9) & Clng(iter.ValueByName("Pregap")))
Update = True
objSongData.PreGap = Clng(iter.ValueByName("Pregap"))
End If
If objSongData.PostGap <> Clng(iter.ValueByName("Postgap")) Then
ImportLogStringList.Add(ImportLogInfo & "Post Gap" & Chr(9) & objSongData.PostGap & Chr(9) & Clng(iter.ValueByName("Postgap")))
Update = True
objSongData.PostGap = Clng(iter.ValueByName("Postgap"))
End If
I don't know what PostGap and PreGap are
But they are always Numbers not strings or "" null. -1 seems to be a default missing value.
Posted: Thu Jun 12, 2008 6:28 am
by nynaevelan
I don't know why but it was getting stuck on the OrigYear of one of the files. When I opened the import db in Sqlite spy I changed the 0 to a -1 and the import imported correctly.
Nyn