XStartTap BETA - Zeitabh.+verzög.Starten+BATCHMODUS von TAPS

[Alter Sack]

[quote=""Dixie""]Hat jemand eine Lösung?[/quote]
Klar, bei der nächsten Zeitumstellung nachts um 4Uhr einen manuellen Timer setzten, der
holt sich dann die korrekte Zeit .

[dvdbommel]

So

ich habe jetzt das TAP auch mal drauf ... damit ich meinen TOPF eher bedienen kann ...

Programmwahl und Lautstärke ...

habe jetzt auch das Uhr-Zeit versetzte Laden von Taps getestet ... inkl Batch Modus

ist echt super und funktioniert 1A

... warte jetzt eigentlich nur noch auf Zwitscher was ja den Batch Modus unterstützen soll ... @ ibbi ... oder

Gruß DVDbommel

[ibbi]

[quote=""dvdbommel""]... warte jetzt eigentlich nur noch auf Zwitscher was ja den Batch Modus unterstützen soll ... @ ibbi ... oder [/quote]

Tut es.

[kantjer]

Hi,

I have aXeL'd my FW last weekend and its working great. Only I now have a few issues with XStartTap, since modifying the FW some times one or more taps aren't started by XStartTap. Increasing the delay in the ini seems to improve things.I now delayed most Taps by 15 or more (except QT for the T4 fix). Also last night in batch mode it failed to executed 1 tap.

Can it be that aXeL is using so much CPU power that the XStart.ini isn't read completely?

Also 2 question about the Batch mode.
Will setting the delay in the ini act as a delay between starting taps in batch mode or is it ignored in batch mode?

When setting a start time window in the ini, does the time window only need to cover the boot time when in batch mode or does it need to cover the time the various taps can start in batch mode?

For example timer set at 3:00 to start a 3PG scan, file-copy and the shutdown, is it sufficient to set a 02:55-03:05 window or do I need to set say 02:55-06:00.

Thanks.
Bauke

[FireBird]

Hi Bauke,
[quote=""kantjer""]Can it be that aXeL is using so much CPU power that the XStart.ini isn't read completely?[/quote]
No. aXel just uses a different firmware decompression algorithm. It doesn’t modify the firmware and it terminates as soon as the firmware starts (about the time you get RUN in the display). AutoStart is executed much later.

Will setting the delay in the ini act as a delay between starting taps in batch mode or is it ignored in batch mode?

Batch mode is just a flag being passed to the TAP. It doesn’t affect any other parameters.

When setting a start time window in the ini, does the time window only need to cover the boot time when in batch mode or does it need to cover the time the various taps can start in batch mode?

The window is checked against the start time of XStart, so the running time of a TAP doesn’t matter (IIRC).

Regards, Alex

[kantjer]

[quote=""FireBird""]
No. aXel just uses a different firmware decompression algorithm. It doesn’t modify the firmware and it terminates as soon as the firmware starts (about the time you get RUN in the display). AutoStart is executed much later.[/quote]
Thanks for making that clear, than it must be a coincidence that this started at the same time as using aXeL.

[dvdbommel]

Ich nutze das überarbeitete Xstart 0.6 Tap von Firebird

aber irgenwie scheine ich einen Denkfehler bei den Zeitangaben zu machen

kann mir jemand mal erläutern wie die INI für folgende Startverteilung auszusehen hat

... da bei mir die TAPs jetzt teilweise nicht mehr gestartet werden:


ich wollte:

3pg im Batchmodus (1) um im Zeitraum von 5:25 bis 5:40 gestartet haben
RecCopy im B(1) im Zeitraum von 1:00 bis 4:30

Quicktimer immer also 0:00 bis 24:00
FastSkip von 5:50 früh bis zum nächsten Tag nachts um 0:50
3PG von 5:50 früh bis zum nächsten Tag nachts um 0:50
Automove von 5:50 früh bis zum nächsten Tag nachts um 0:50
Stirf von 5:50 früh bis zum nächsten Tag nachts um 0:50
Improbox von 5:50 früh bis zum nächsten Tag nachts um 0:50
Filer2 immer 0:00 bis 24:00
Reccopy ohne Batchmodus von 5:50 bis zum nächsten Tag nachts um 0:40


Gruß DVDbommel

[kantjer]

[quote=""dvdbommel""]Ich nutze das überarbeitete Xstart 0.6 Tap von Firebird

aber irgenwie scheine ich einen Denkfehler bei den Zeitangaben zu machen

kann mir jemand mal erläutern wie die INI für folgende Startverteilung auszusehen hat

... da bei mir die TAPs jetzt teilweise nicht mehr gestartet werden:
Gruß DVDbommel[/quote]This is my ini, maybe this helps

Code: Alles auswählen

00:00|00:01|0000|0|PowerRestore.tap
23:00|23:01|0000|0|PowerRestore.tap
08:00|24:00|0000|1|LNBfix.tap
00:00|02:45|0000|1|LNBfix.tap
05:00|24:00|0000|0|QuickTimer_Nederlands.tap
00:00|02:45|0000|0|QuickTimer_Nederlands.tap
05:00|24:00|0010|0|improbox.tap
00:00|02:45|0010|0|improbox.tap
05:00|24:00|0015|0|nicedisplay.tap
00:00|02:45|0015|0|nicedisplay.tap
05:00|24:00|0020|0|3PG.tap
00:00|02:45|0020|0|3PG.tap
05:00|24:00|0020|0|filer.tap
00:00|02:45|0020|0|filer.tap
05:00|24:00|0025|0|macro.tap
00:00|02:45|0025|0|macro.tap
05:00|24:00|0025|0|mei2archive.tap
00:00|02:45|0025|0|mei2archive.tap
05:00|24:00|0025|0|mei2eit.tap
00:00|02:45|0025|0|mei2eit.tap
05:00|24:00|0030|0|automove.tap
00:00|02:45|0030|0|automove.tap
05:00|24:00|0030|0|poweroff_nd.tap
00:00|02:45|0030|0|poweroff_nd.tap
05:00|24:00|0030|0|Standby.tap
00:00|02:45|0030|0|Standby.tap
05:00|24:00|0030|0|AutoReboot.tap
00:00|02:45|0030|0|AutoReboot.tap
02:55|03:05|0000|0|filer.tap
02:55|03:05|0000|0|mei2archive.tap
02:55|03:05|0000|1|3PG.tap
02:55|03:05|0000|1|RecCopy.tap
02:55|03:05|0000|1|Set_tuner.tap
02:55|03:05|0000|1|delay.tap
02:55|03:05|0000|1|Shutdown.tap

Why not start 3PG and RecCopy in one batch?
One tip if you want to do that make sure you run 3PG first (see my ini), I found out that if you run 3PG after RecCopy the batch stops after 3PG so no shutdown.

Bauke

[dvdbommel]

@ kantjer

thank you for your inspiration

I think my INI must then look like this:

00:00|24:00|0000|0|QuickTimer.tap
05:40|24:00|0000|0|FastSkip.tap
00:00|00:40|0000|0|FastSkip.tap
05:40|24:00|0010|0|improbox.tap
00:00|00:40|0010|0|improbox.tap
05:40|24:00|0020|0|3PG.tap
00:00|00:40|0020|0|3PG.tap
05:40|24:00|0025|0|STIRF-1.3C-beta.tap
00:00|00:40|0025|0|STIRF-1.3C-beta.tap
05:40|24:00|0030|0|automove.tap
00:00|24:00|0035|0|Jags_Auto-Off_05-30.tap
05:40|24:00|0040|0|filer.tap
00:00|00:40|0040|0|filer.tap
05:40|24:00|0045|0|RecCopy.tap
00:00|00:40|0045|0|RecCopy.tap
00:50|05:00|0000|1|RecCopy.tap
05:25|05:39|0000|1|3PG.tap

Gruß DVDbommel

[kantjer]

[quote=""dvdbommel""]00:50|05:00|0000|1|RecCopy.tap
05:25|05:39|0000|1|3PG.tap
[/quote]

This isn't going to work, RecCopy won't shutdown the system so 3PG can't start in batch mode. You will need something like this

Code: Alles auswählen

00:50|05:00|0000|1|RecCopy.tap
00:50|05:00|0000|1|Shutdown.tap
05:25|05:39|0000|1|3PG.tap
05:25|05:39|0000|1|Shutdown.tap

Or I think a better option would be

Code: Alles auswählen

00:50|05:00|0000|1|3PG.tap
00:50|05:00|0000|1|RecCopy.tap
00:50|05:00|0000|1|Shutdown.tap

In this case 3PG will do its scan, after it is finished XstartTap will start RecCopy en when that is finished the system is shutdown by the Shutdown tap.

You can find the Shutdown tap in post #84 of this thread.

Also make sure you set your timer at least 1 min. later than the start time set in the ini, the Toppy will start 1 min. earlier than the timer is set to.

Good luck

[ibbi]

[quote=""kantjer""]This isn't going to work, RecCopy won't shutdown the system so 3PG can't start in batch mode.[/quote]

Why does 3PG need a system being shut down in order to run in batch mode?

[kantjer]

[quote=""ibbi""]Why does 3PG need a system being shut down in order to run in batch mode? [/quote] Your right its the other way around in dvdbommel's ini RecCopy the system needs to shutdown for 3PG to do its thing. ops:

Code: Alles auswählen

00:50|05:00|0000|1|RecCopy.tap
05:25|05:39|0000|1|3PG.tap

[ibbi]

[quote=""kantjer""]Your right its the other way around in dvdbommel's ini RecCopy the system needs to shutdown for 3PG to do its thing. ops:

Code: Alles auswählen

00:50|05:00|0000|1|RecCopy.tap
05:25|05:39|0000|1|3PG.tap

[/quote]

I don't understand this either.

Do you mean that 3PG will shut down the system after having run in batch mode? If yes, this'd be too much of a good thing, because a TAP in batch mode should only exit itself.

[dvdbommel]

@ kantjer

last night i tested my ini:

00:00|24:00|0000|0|QuickTimer.tap
05:40|24:00|0000|0|FastSkip.tap
00:00|00:40|0000|0|FastSkip.tap
05:40|24:00|0010|0|improbox.tap
00:00|00:40|0010|0|improbox.tap
05:40|24:00|0020|0|3PG.tap
00:00|00:40|0020|0|3PG.tap
05:40|24:00|0025|0|STIRF-1.3C-beta.tap
00:00|00:40|0025|0|STIRF-1.3C-beta.tap
05:40|24:00|0030|0|automove.tap
00:00|24:00|0035|0|Jags_Auto-Off_05-30.tap
05:40|24:00|0040|0|filer.tap
00:00|00:40|0040|0|filer.tap
05:40|24:00|0045|0|RecCopy.tap
00:00|00:40|0045|0|RecCopy.tap
00:50|05:00|0000|1|RecCopy.tap
05:25|05:39|0000|1|3PG.tap

and it worked great ... the films have been copied and 3PG made his Scan and set timers and after that the toppy was in Stand By ...

everything worked like i expected ... so i don't know why i should use the shutdown TAP ... it's not needed

Gruß DVDbommel

[kantjer]

[quote=""ibbi""]I don't understand this either.

Do you mean that 3PG will shut down the system after having run in batch mode? If yes, this'd be too much of a good thing, because a TAP in batch mode should only exit itself.[/quote]

The ini shown in my post is copied from dvdbommel's ini.
If like you mention a TAP in batch mode only exits itself it can't shut down the system without the help of a Shutdown TAP.
Looking at dvdbommel's ini this would mean that after RecCopy has done its thing the system won't shutdown and therefore 3PG can't start in batch mode.

So I guess we are saying the same thing.

PS reading my post from last night again I can see it was getting late, it doesn't make very much sense to me either.

[kantjer]

[quote=""dvdbommel""]@ kantjer

last night i tested my ini:

00:00|24:00|0000|0|QuickTimer.tap
05:40|24:00|0000|0|FastSkip.tap
00:00|00:40|0000|0|FastSkip.tap
05:40|24:00|0010|0|improbox.tap
00:00|00:40|0010|0|improbox.tap
05:40|24:00|0020|0|3PG.tap
00:00|00:40|0020|0|3PG.tap
05:40|24:00|0025|0|STIRF-1.3C-beta.tap
00:00|00:40|0025|0|STIRF-1.3C-beta.tap
05:40|24:00|0030|0|automove.tap
00:00|24:00|0035|0|Jags_Auto-Off_05-30.tap
05:40|24:00|0040|0|filer.tap
00:00|00:40|0040|0|filer.tap
05:40|24:00|0045|0|RecCopy.tap
00:00|00:40|0045|0|RecCopy.tap
00:50|05:00|0000|1|RecCopy.tap
05:25|05:39|0000|1|3PG.tap

and it worked great ... the films have been copied and 3PG made his Scan and set timers and after that the toppy was in Stand By ...

everything worked like i expected ... so i don't know why i should use the shutdown TAP ... it's not needed

Gruß DVDbommel[/quote]

I think I can see why it worked:
after RecCopy did its thing the system stayed on until it was shutdown at 05:30 by Jags_Auto_Off.
Then the system was probably re-started by your 3PG timer.
Since like ibbi says in his post a TAP in batch mode doesn't shut down the system my guess is that 3PG after the scan initiated by the batch mode also did its timed scan and shut was down after that.

The advantage of using the Shutdown TAP after running RecCopy in batch mode is that it will shut down the system immediately when RecCopy is done instead of waiting until 05:30.

If your happy with running 3PG as a separate process and not in a batch together with RecCopy, like you are doing now, there is no need to run it in batch mode. Just start 3PG in normal mode set a timed scan and let it shutdown afterwards.

[tischla]

R2-D2 hat einen neue Version im UK-Forum gepostet:
http://forum.toppy.org.uk/forum/viewtopic.php?p=109467

leider hat er denn Quellcode nicht beigelegt, was ich sehr schade finde, da jegliche meiner Entwicklung auf der Basis von Deedbeef und mit Hilfe und Erweiterung von Firebird und anderen stattgefunden hat.
darf man ihm auf die Finger klopfen?

grüsse tischla

EDIT: Hat sich geklärt... quellcode liegt nun in R2-D2s zip bei .. Danke

[BR007]

@tischla
Seit Freitag letzter Woche habe ich auch an einer neuen Version 0.7 gearbeitet. Ich wollte eigentlich erst noch zu Ende testen, bevor ich dich fragen wollte, ob du Einwände gegen ein Veröffentlichung hast. Ich ziehe die Anfrage hiermit vor. Die Source-Codes würden natürlich mit veröffentlicht. Ich habe folgendes geändert:
- string handling optimiert (unnötige strlen, strcpy entfernt)
- MinStart-MaxStart geht jetzt auch über Mitternacht (also z.B. 08:00|01:00 usw)
- man kann Zeilen mit ; auskommentieren
- Leerzeilen werden überlesen

also z.B. so
06:00|08:00|0000|1|3PG.tap
06:00|08:00|0000|1|Shutdown.tap

08:00|01:00|0000|0|improbox.tap
08:00|01:00|0010|0|3PG.tap
08:00|01:00|0020|0|TF5000Display.tap
08:00|01:00|0025|0|TSRCommander.tap
08:00|01:00|0030|0|clock.tap
;08:00|01:00|0035|0|Videot3xt.tap
;08:00|01:00|0040|0|SuperPip.tap
08:00|24:00|0050|0|TapLauncher.tap
08:00|01:00|0055|0|PowerDown.tap

[tischla]

Hallo 007,

Deine Anpassungen find ich ausgezeichnet!
Wie wärs noch mit einer Sortierung der Spalte Startverzögerungen, sodaß man die Ini beliebig zusammenstellen kann. (das wär auf meiner Ideenliste noch so an Todos gestanden - aber bei meinen c Künsten wäre das ein Jahresprojekt geworden)

R2-D2 hätte in seiner Änderung eine neue Spalte eingeführt, die den Start abhängig vom Startmodus macht: d.h. Timer-Start oder Manueller-Start.

sollten wir uns nicht etwas absprechen, wer was wann machen könnte?

Code: Alles auswählen

# Rigid format.  Like this:
# MinStartTime | MaxStartTime | StartDelay | BatchMode | RunOnTimerBoot | TAPFilename
06:00|19:00|0000|0|0|StartChannelLCN.tap
00:00|24:00|0000|0|1|DescriptionExtender.tap
00:00|24:00|0000|0|1|mei2archive.tap
00:00|24:00|0000|0|0|RemoteExtender.tap
00:00|24:00|0000|0|0|eit2mei.tap
00:00|24:00|0015|0|0|MyStuff.tap
# Wakeup key
W=0x1001e
#

grüsse
tischla

[BR007]

Ok, ich fasse die Antwort als Genehmigung auf.
Das, was R2-D2 gemacht hat, scheint auch plausibel und nützlich.
Ich werde versuchen, die Änderungen von R2-D2 mit meinen "mergen", oder bist du diesbezüglich anderer Meinung?
Kann ich problemlos die neueste firebird lib verwenden, oder muss ich dazu was spezielles wissen?