TMSArchive - die Fileralternative für den TMS

[tango]

Hello Everyone,

I'm Tango. I've been asked to drop by the forum and would like to say Hi.
I don't speak German, so unfortunately, my posts will need to be in English. I apologise in advance if this isn't etiquette on this forum.

In the past, Ricki and Longtom have passed on feedback and provided numerous translations to help develop TMSArchive. Thanks guys, your help has been (and is) invaluable!


I've been working recently with Ricki on some updates to TMSArchive:
1) Modify "delete non-empty folder" config parameter to allow permanent use
2) Cater for LittleClock TAP by reducing screen area check for OSD
3) Modify TAPManager: Play = Close TMSArchive then start selected TAP
4) BackgroundCopy TAP integration
5) Recycle bin autoclean to exclude external drives/mounts
6) Optional force delete with long-press of Blue key

The new version is almost ready for beta testing, but there is an issue with how the bgc integration has been implemented which will hold up its release.
How many people would use bgc integration and how would you want it implemented?

Here is how I've implemented it:
4) BackgroundCopy TAP integration
If bgc has been installed, then there will be 2 new options on the Move window: Green = Copy via bgc Jobile, Yellow = Move via bgc Jobfile. Both options will create a bgc Jobfile with the destination directory taken from the bgc ini file. TMSArchive will then start the bgc TAP.
<translated>
4) BackgroundCopy TAP Integration
Wenn bgc installiert ist, gibt es zwei neue Optionen im Move Fenster: Grün = „Copy“ Kopieren über bgc Jobfile, Gelb = „Move“ verschieben über bgc Jobfile. Beide Optionen werden einen bgc Jobfile mit dem Zielverzeichnis aus der bgc ini erstellen. TMSArchive startet dann selbständig das bgc TAP.

I've implemented it this way, because I understood that NASMounted folders weren't appearing in TMSArchive and so the background copy function built into TMSA wouldn't work. Therefore, to do a background copy, bgc was needed to copy the file to the detsination in its ini file.
I now understand that the requirement is to select a destination folder from the list and create bgc Jobfile to move/copy the file to that folder. This would seem to duplicate the background copy functionality that is already in TMSA.

Can someone shed some light on what is desired, and I'll see what can be accommodated.

Regards,
Tango.

[Ricki]

Welcome Tango to the forum. Glad you are here.

[Twilight]

Welcome Tango to the forum. Glad you are here.

wellcome in my living room

twilight

[macfan]

Hello Everyone,

I'm Tango. I've been asked to drop by the forum and would like to say Hi.

Welcome! It's very kind from you to help us here at the opposite pole of our world.

In the past, Ricki and Longtom have passed on feedback and provided numerous translations to help develop TMSArchive. Thanks guys, your help has been (and is) invaluable!

from me too!

I've been working recently with Ricki on some updates to TMSArchive:
1) Modify "delete non-empty folder" config parameter to allow permanent use
2) Cater for LittleClock TAP by reducing screen area check for OSD
4) BackgroundCopy TAP integration

These were wishes from me. Thank you for realizing them.

I've implemented it this way, because I understood that NASMounted folders weren't appearing in TMSArchive

They appear correctly.

and so the background copy function built into TMSA wouldn't work.

That's my fault. I didn't know that this function was already built in. ops: ops: ops:
But the function doesn't work for me. The Topfield hangs when I use it.

I now understand that the requirement is to select a destination folder from the list and create bgc Jobfile to move/copy the file to that folder.

That would be fine.

This would seem to duplicate the background copy functionality that is already in TMSA.

This seems to be true, sorry!

Gruß, Horst

[Twilight]

in SmartFiler we have done it that way:

if a file is moved into a directory it checks if the directory is mounted or not. if yes it creates a job file for bgc.

twilight

[tango]

Hi All,

Thanks for the welcome :-)

I'm working on fixing the inbuilt TMSA background copy to NAS. It isn't working, but I may have a fix.
Once that is resolved we can look at how the final bgc integration should look.

Cheers,
Tango.

[db1]

Welcome Tango, we already had contact by email and I am pleased that you are now also here.

Dieter

[tango]

Hi Everyone,

It's taken a while, but the new beta version of TMSArchive will be released shortly on TAPtoDate.

I have rewritten the bgc integration and it will no longer be limited to the destination directory in the bgc ini file. Instead there will be a new config option to choose between the using TMSArchive Background Copy and using bgc.

The main changes included in the new version are listed below (in English and German).
Please note this is a beta version and still needs more testing. Please use with caution and report any issue back here.

Regards,
Tango.


Main Changes:

(In English)
1) Modify "delete non-empty folder" config parameter to allow permanent use
The config parameter will have an extra option that will allow a non-empty folder to be deleted. Currently there is an option to delete a non-empty folder once. This option is reset after you close the TMSArchvie window. The new option will remember this setting.
Please use with caution. Folder deletion does NOT use the recycle bin and can not be undone.

2) Cater for LittleClock TAP by reducing screen area check for OSD
The On Screen Display (OSD) is checked by TMSArchive and if anything is displayed in specific regions, TMSArchive will not open. The default position of LittleClock is ok, but if you move it higher on the screen it will prevent TMSA from opening. I've reduced the screen area that is checked in the next version and nothing left of column 150 will be checked.

3) Modify TAPManager: Play = Close TMSArchive then start selected TAP
Currently in TAPManager mode both OK and Play buttons will start a TAP and leaves the TMSArchive window open.
I have now changed the Play button to close the TMSAchive window before starting the selected TAP. The OK button still works as it did before.

4) BackgroundCopy (bgc) TAP integration
There are 4 new config option on the General Settings screen. The main one is to choose between the TMSArchive Background Copy or creation of bgc jobfiles. If a file is moved to a folder that is on a different mount, then a background copy is triggered - either a TMSArchive Background Copy or a bgc jobfile, depending on the setting.
If Background Copy: then TMSArchive will attempt to copy (not move) the file in the background. There are some issues with NFS mounts, so a warning is displayed preventing copying by this method. The 2nd new config option can be set to bypass this warning and attempt to copy the file anyway.
If bgc: then a bgc jobfile is created and the bgc tap will be started. Whether a file is copied or moved by bgc is decided by the 3rd new config option. When creating a bgc jobile, TMSArchive will prompt for a confirmation before creating the jobile. The 4th new config option can be set to bypass this confirmation popup.

5) Recycle bin autoclean
The threshold value only applies to the internal HDD. ie. if autoclean enabled, then every hour the freespace on the internal HDD is checked and if it is less than the threshold the recycle bin cleanup will be triggered. There is no check of external HDD freespace.
Recycled files on external drives were being deleted when an autoclean ran. This has been changed now, and only recycled files on the internal drive will be auto cleaned (deleted). Recycled files on external drives will remain until they are manually deleted.

6) Optional force delete
A long press of the Blue key has been introduced and this will force a delete of the selected files instead of sending them to the recycle bin. If you don't use the recycle bin, then the long press of Blue will be the same as the normal press of Blue (ie. it does a delete with a confirmation screen).


(In German)
1) "Löschen nicht leerer Ordner" Konfigurationsparameter geändert um die Einstellung permanent zur Verfügung zu haben.
In den Einstellungen gibt es nun eine zusätzliche Option, mit der ein nicht-leerer Ordner gelöscht werden kann. Derzeit gibt es eine Option, um einen nicht-leeren Ordner einmalig zu löschen. Diese Option wurde zurückgesetzt, nachdem TMSA geschlossen wird.
Die neue Option merkt sich nun diese Einstellung.
Bitte mit Vorsicht nutzen. Das Löschen eines Ordners verläuft nicht über den Papierkorb und kann nicht rückgängig gemacht werden.

2) TMSA kann jetzt mit LittleClock betreiben werden.
Das On Screen Display (OSD) wird von TMSArchive überprüft und wenn etwas in bestimmten Bereichen angezeigt wird, konnte TMSA nicht gestartet werden. Die Standardposition von LittleClock ist OK, aber wenn es höher auf dem Bildschirm bewegt wird, verhindert dies den Start von TMSA. Der zu überprüfende Bildschirmbereich wurde reduziert und es wird nunmehr nichts links von Spalte 150 geprüft.

3) TAPManager angepasst: Play = Schließe TMSArchive und starte TAP
Derzeit wird im TAPManager Modus sowohl bei Nutzung der OK oder der Wiedergabetaste ein TAP gestartet und das TMSArchive Fenster bleibt angezeigt.
Nun wird bei Nutzung der Play-Taste, das TMSAchive Fenster vor dem Start des gewählten TAPs geschlossen. Die OK-Taste funktioniert weiterhin wie zuvor.

4) BackgroundCopy (bgc) TAP Integration
Es gibt nun 4 neue Einstellungsmöglichkeiten unter Optionen. Als erstes kann man jetzt zwischen TMSArchive Background Copy oder bgc Jobfiles wählen.
Beide werden auf die gleiche Weise gestartet, d.h. das Ziel aus dem Zielordner Auswahlfenster wählen und OK drücken. Bei Verschiebung einer Datei in einem Ordner der sich auf einem Mount befindet, wird eine Hintergrundkopie ausgelöst - abhängig von der Einstellung, entweder über TMSArchive Background Copy oder über einen bgc Jobfile.
Auswahl Background Copy: TMSArchive wird im Hintergrund eine Kopie (keine Verschiebung) versuchen. Mit manchen NFS Mounts gibt allerdings Probleme, weshalb eine Warnung über diese Kopierart ausgegeben wird. Die zweite neue Einstellungsoption, kann konfiguriert werden, um diese Warnung zu umgehen und es wird dann versucht die Datei zu kopieren.
Auswahl bgc: Ein bgc Jobfile wird erzeugt und das BackgroundCopy Tap wird gestartet. Ob eine Datei kopiert oder verschoben wird, kann über die dritte Einstellungsoption gewählt werden. Wenn ein bgc Jobfile erstellt wird, zeigt TMSArchive dies an und die Erstellung des Jobfiles muss bestätigt werden. Die vierte Einstellungsoption, ermöglicht es diese Abfrage auszuschalten.

5) Automatisches entleeren des Papierkorbs (Autoclean)
Der Grenzwert bezieht sich nur auf die interne Festplatte. D.h. wenn die „Autoclean“ Option aktiviert ist, wird dann z.B. jede Stunde der Speicherplatz auf der internen Festplatte überprüft, und wenn der kleiner ist als der Schwellenwert, wird die Papierkorb Bereinigung ausgelöst. Es erfolgt keine Speicherplatz Überprüfung der externen Festplatte.
Recycling-Dateien auf externen Festplatten wurden gelöscht wenn „Autoclean“ lief. Dies hat sich nun geändert, und nur Recycling-Dateien auf der internen Festplatte werden automatisch bereinigt (gelöscht). Recycling-Dateien auf externen Laufwerken bleiben erhalten, bis sie manuell gelöscht werden.

6) Optionales „Zwangs“ löschen
Ein langer Druck auf die Blaue Taste wird eine Datei jetzt „Zwangs“ löschen anstatt diese in den Papierkorb zu verschieben. Sollte die Recycle Funktion des Papierkorbs nicht genutzt werden, dann wird ein langer Druck auf die Blaue Taste die gleiche Funktion haben wie die normale Betätigung der Taste (d.h. es erfolgt ein Löschen mit einem Bestätigungsbildschirm).

[tango]

Hi,

TMSArchive v5.1a (beta) is now on TAPtoDate.

Regards,
Tango.

[Twilight]

twilight

[Ricki]

Great job Tango. :d rinking:

[macfan]

for fulfilling all my wishes! Now TMSArchive is equal to or better than SmartFiler in every feature . Even the BackgroundCopy-Feature is now better in TMSArchive, because TMSArchive starts BackgroundCopy automatically, SmartFiler doesn't.

Gruß, Horst

[db1]

Thanks a lot for your work.

[ameise999]

danke :

gruss

[ramibi]

Von mir auch mal wieder einen Dankl

[mini49]

[quote="tango"]Hi Everyone,


5) Recycle bin autoclean
The threshold value only applies to the internal HDD. ie. if autoclean enabled, then every hour the freespace on the internal HDD is checked and if it is less than the threshold the recycle bin cleanup will be triggered. There is no check of external HDD freespace.
Recycled files on external drives were being deleted when an autoclean ran. This has been changed now, and only recycled files on the internal drive will be auto cleaned (deleted). Recycled files on external drives will remain until they are manually deleted.
[/quote]


Hi tango,

thank you for all the time you invest in this TAP.

I'm however a little bit unhappy with 5) above. What was the main reason for this change? Previously I knew that with the green key I could empty the internal and the external disc at once automatically. Now after your change I have to clean all the recycled files on the external disc by hand one after the other. I think this is a step backwards.

Thank you
mini49

[db1]

Tango,

I have no problems using the last version, but I've another request.

The space of recycled files should be added to free space shown, otherwise one will always end up with the free space threshold (if there is no other autodelete set than the threshold) and one does not know how much space would be really available if needed.

[Ricki]

[quote="mini49"]What was the main reason for this change?

Thank you
mini49[/quote]


This was a request by another user here. Mayabe Tango will give it a second thought.

[tango]

Hi mini / Ricki,

The change to the Recycle Bin Autoclean came from a request regarding how the autoclean worked. The autoclean should never have deleted files from external drives. This was an oversight when compatability for external drives was added. The idea behind the autoclean was to ensure there was always room on the internal HDD for new recordings. Autocleaning an external drive doesn't help free space for new recordings.

Another reason for not autocleaning external drives, is that they may not only be used for the Topfield. A USB or external HDD could contain large directory structures that we don't want to traverse. Or they could possibly contain non-Topfield *.del files that would be accidentally deleted.


I can understand why you think manually deleting individual recycled files on an external HDD would be a backwards step.
Maybe I can add a new config option to exclude/include external drives from recycle bin cleaning. But you would have to accept that if you include external drives then the problems above would return.

I welcome any thoughts or suggestions?

Regards,
Tango.

[tango]

[quote="db1"]The space of recycled files should be added to free space shown, otherwise one will always end up with the free space threshold (if there is no other autodelete set than the threshold) and one does not know how much space would be really available if needed.[/quote]

Hi db,

Unfortunately adding up total of all recycled files can be slow. I have to add the size of each recycled file one by one and to do this I need to traverse the whole directory structure. There is a way to do this already, but it would be inefficient to do this every time the filelist is displayed.

If you want to see the total size of all recycled files, go to the Recycle Bin and press the White key.
Does this help?

Regards,
Tango.