MovieCutter

[chris86]

Ich habe die neue Version auch schon getestet, bis jetzt aber "nur" ein nicht korruptes Dateisystem als Meldung erhalten.

Dazu noch folgende Fragen:
1) Bleibt die Meldung eigentlich stehen, wenn das Dateisystem als Fehlerhaft erkannt wird (bei mir dauert es recht lange und ich sehe nicht immer hin).
2) Wenn ich mehrere Filme schneide und den scan nur beim letzten durchführen lasse reicht das doch?
3) Wenn ich eine linux formatierte (Topf Format, Name fällt mir gerade nicht ein) externe gemountet habe, wird diese auch überprüft, bzw kann ich diese überprüfen lassen?
4) Denkst du, dass ein Kopieren einer korrupten Datei auf das Unterverzeichnis der gemounteten HD (mit BGC) reicht oder soll das kopieren explizit auf die ext. HD mit der FW erfolgen?

Ja!, ja (liefert aber weniger Informationen für die Fehlersuche), jein (nur wenn du den Schnitt auf dieser durchführst) und "vermutlich ja" (das hat noch keiner getestet, aber nach meinem Verständnis des Problems müsste ein Kopieren ausreichen, ein Verschieben jedoch nicht).

Z.B. gestern: Ich starte TTD (was wieder einmal keine Verbindung schafft, was ich mittlerweile am verhalten des Fortschrittsbalken erkenne, dann MC, dann kann ich plötzlich keine Bookmarks mehr in der laufenden Wiedergabe setzten. Ich stoppe die Wiedergabe, worauf der Topf ganz kontrolliert bei laufender Aufnahme herunter fährt. Nach Neustart nicht einmal ein "Prüfe Festplatte", die abgebrochene Aufnahme bis zum Zeitpunkt des Runterfahren vorhanden, und automatisch neu gestartet ...
Sowas hake ich mittlerweile einfach ab.

Eine etwas merkwürdige Einstellung, wie ich finde! Wo es doch hier engagierte Leute gibt, die sich über Feedback zu ihren TAPs freuen, und derartige Fehler gern beheben würden - wenn sie durch ausgiebigere Informationen und Logfiles unterstützt würden...

Noch eine Anmerkung zum Problem an sich: Wir sollten endlich aufhören die Schuld auf gewisse Sachen zu schieben: Zuerst war es der MC, dann hat sich herausgestellt dass das Problem auch die FW hat. Dann waren es bestimmte WD Platten, und jetzt werden es Montagsgeräte

Normalerweise ist es eine gute Idee, ein Problem einzugrenzen, bzw. die Gemeinsamkeiten der Betroffenen zu analysieren.
Wenn du eine bessere Möglichkeit kennst, wie man die Ursache finden könnte, dann sag Bescheid.

Ich denke es trifft die "Poweruser" mit vielen Taps in unterschiedlicher Reihenfolge gestartet (wenn ich denke, was die TAP Reihenfolge bei mir für einen Unterschied in der Bootzeit macht, möchte ich gar nicht wissen, was da so im Hintergrund abläuft), unterschiedlichen CAMs, anderen Firmwares und Settings.

Und User wie Twilight und Firebird (die das Problem trotz stärkster Bemühungen nicht reproduzieren konnten) sind für dich keine "Poweruser"?

Und wenn ich denke was mein Topf sonst noch für Macken hat, dann gehört das verschwinden von Aufnehmen halt auch dazu.

Wenn du meinst... ich persönlich bin nicht bereit, das einfach so zu akzeptieren...

[db1]

Gebe dir vollkommen recht, war (wie geschrieben) gestern einfach frustriert von den vielen Durcheinander.
Auf jeden Fall möchte ich die von Dir und vor allem auch die von Firebird und Twilight geleistete Arbeit noch einmal ganz fest loben.
Für mich selbst ist es wohl am Besten mal ne kleine Diskussionspause einzulegen ...

[Bernhard75045]

OT: Alles Gute dafür! Von mir ebenfalls Danke. Es gibt ja Schlimmeres. Man sagt ja, dass aller guter Dinge drei sind, und bisher scheint alles planmäßig zu verlaufen. Wenn ich dadurch das angedrohte Ersatzteil nochmals ein oder zwei Jahre hinauszögern kann hat es sich ja gelohnt...

[dRdoS7]

Hi,

I have MC v2.0j.

I have 3 problems:

1. I get an error message after the cutting:

Code: Alles auswählen

2014-04-12 15:45:26 CheckFileSystem: Checking file system of device '192.168.1.25:/DataF'...
2014-04-12 15:45:27 CheckFileSystem() E1c03.
2014-04-12 15:45:27 CheckFileSystem: File system check has been aborted!
2014-04-12 15:45:30 MovieCutterProcess() successfully completed!

When I installed this version I telneted in and did "chmod" as per Install.txt.

I noticed that in the install.txt:

Code: Alles auswählen

mportant Information for the Installation
==================================

(Source excluded) The ZIP archive please complete in the folder / Program Files -
   unzip on the receiver.

- Then (unique) login via telnet to the receiver and enter the following:
   chmod a + x /mnt/hd/Program Files/jfs_fsck

(must be done 2.0i or later only once during the initial installation of Movie Cutter!)


Wichtige Hinweise zur Installation
==================================

- Das ZIP-Archiv bitte komplett (ausgenommen source) in den Ordner /ProgrammFiles
  auf dem Receiver entpacken.

- Dann (einmalig) per Telnet auf dem Receiver einloggen und folgendes eingeben:
  chmod a+x /mnt/hd/ProgramFiles/jfs_fsck

(muss nur einmalig bei der ersten Installation von MovieCutter 2.0i oder höher durchgeführt werden!)

There are spaces between a+x, maybe that is the cause? I used the fisrt one, which has spaces.

The second probem is after the Toppy is started, MC sometimes stops by itself. I have to re-start manually.

Code: Alles auswählen

2014-04-12 15:27:33 ***  MovieCutter V2.0j started!  ***
2014-04-12 15:27:33 ====================================
2014-04-12 15:27:33 Receiver Model: TRF-7260 (32501)
2014-04-12 15:27:33 Firmware: TF-BCPF 1.00.02 (Dec 20 2012)
2014-04-12 15:27:33 Hard disk: ST9500325AS, FW 0001SDM1, Serial:             5VEX2EH4
2014-04-12 15:44:46 ***  MovieCutter V2.0j started!  ***
2014-04-12 15:44:46 ====================================
2014-04-12 15:44:46 Receiver Model: TRF-7260 (32501)
2014-04-12 15:44:46 Firmware: TF-BCPF 1.00.02 (Dec 20 2012)
2014-04-12 15:44:46 Hard disk: ST9500325AS, FW 0001SDM1, Serial:             5VEX2EH4
2014-04-12 15:44:52 ========================================

It stopped after 15:27:33.

The third problem is when I press the "white" key while TMSArchive is running and a file is playing, MC menu comes up. Sometimes in the foreground, TMSA actually stops, but the TMSA screen remains with MC over the top. Sometimes in the background, when I exit TMSA it is there, waiting.

The 2nd problem existed with MC v2.0h also.

Thanks,

dRdoS7.

Code: Alles auswählen

# chmod a+x /mnt/hd/ProgramFiles/jfs_fsck
# ls -l /mnt/hd/ProgramFiles/jfs_fsck
-rwxrwxrwx    1 root     root       971877 Apr 12  2014 /mnt/hd/ProgramFiles/jfs_fsck
#

[chris86]

Hi,

I have MC v2.0j.

1. I get an error message after the cutting:

Code: Alles auswählen

2014-04-12 15:45:26 CheckFileSystem: Checking file system of device '192.168.1.25:/DataF'...
2014-04-12 15:45:27 CheckFileSystem() E1c03.
2014-04-12 15:45:27 CheckFileSystem: File system check has been aborted!
2014-04-12 15:45:30 MovieCutterProcess() successfully completed!

When I installed this version I telneted in and did "chmod" as per Install.txt.

You have done everything right.
But it seems you are performing the cutting directly on a NAS...? I have never tested that. How does this work? And is the NAS formatted in JFS?

If you are really doing this on a NAS, that explains the error message. File system check on NAS is not supported (yet).
This is nothing to be worried about.

The second probem is after the Toppy is started, MC sometimes stops by itself. I have to re-start manually.

Code: Alles auswählen

2014-04-12 15:27:33 ***  MovieCutter V2.0j started!  ***
2014-04-12 15:27:33 ====================================
2014-04-12 15:27:33 Receiver Model: TRF-7260 (32501)
2014-04-12 15:27:33 Firmware: TF-BCPF 1.00.02 (Dec 20 2012)
2014-04-12 15:27:33 Hard disk: ST9500325AS, FW 0001SDM1, Serial:             5VEX2EH4
2014-04-12 15:44:46 ***  MovieCutter V2.0j started!  ***
2014-04-12 15:44:46 ====================================
2014-04-12 15:44:46 Receiver Model: TRF-7260 (32501)
2014-04-12 15:44:46 Firmware: TF-BCPF 1.00.02 (Dec 20 2012)
2014-04-12 15:44:46 Hard disk: ST9500325AS, FW 0001SDM1, Serial:             5VEX2EH4
2014-04-12 15:44:52 ========================================

It stopped after 15:27:33.

That is quite strange!
Do you sometimes use the "Sleep"-Key (that one with the little clock)?
MC has got an (undocumented) "Emergency-Exit-Key", which helps me with debugging situations when the OSD gets stuck or something like that. That means, if you press the Sleep key while MovieCutter is running in the background, it will stop.
If this is not the reason for your issue, please get back here. Then I will have to discover the problem deeper...

The third problem is when I press the "white" key while TMSArchive is running and a file is playing, MC menu comes up. Sometimes in the foreground, TMSA actually stops, but the TMSA screen remains with MC over the top. Sometimes in the background, when I exit TMSA it is there, waiting.

The 2nd problem existed with MC v2.0h also.

Okay, I can reproduce this issue. I will try my best if I can do something about that.

[Bobbycar123]

Hoffe,dass die Frage jetzt hier besser passt.
Ab und zu bekomme ich direkt vor dem Schneiden die Meldung "Receiver neu starten ? Ja/Nein. Bei Nein bin ich wieder raus, bei Ja gehts im Schnittmenue weiter und alles funktioniert. Bei Ja wird der Receiver aber nicht neu gestartet, denn es geht ohne Unterbrechung weiter. Diese Meldung kommt nicht immer, vielleicht nur bei bestimmten files. Hab den Zusammenhang noch nicht rausgefunden. Weiss jemand, was es damit auf sich hat?
Gruss
Werner

[chris86]

[quote="Bobbycar123"]Hoffe,dass die Frage jetzt hier besser passt.
Ab und zu bekomme ich direkt vor dem Schneiden die Meldung "Receiver neu starten ? Ja/Nein. Bei Nein bin ich wieder raus, bei Ja gehts im Schnittmenue weiter und alles funktioniert. Bei Ja wird der Receiver aber nicht neu gestartet, denn es geht ohne Unterbrechung weiter. Diese Meldung kommt nicht immer, vielleicht nur bei bestimmten files. Hab den Zusammenhang noch nicht rausgefunden. Weiss jemand, was es damit auf sich hat?
Gruss
Werner[/quote]
Ich nehme an, die angezeigte Warnung lautet "Receiver vor dem Schneiden neu starten! Trotzdem fortfahren?".
Diese Meldung wird angezeigt, wenn du versuchst, eine Datei direkt nach dem Aufnehmen zu schneiden, ohne den Receiver zwischendurch einmal neu gestartet zu haben.*
Dies wird nicht empfohlen, da es in solchen Fällen durch die Firmware zu einer Beschädigung des Endes der Aufnahme kommen konnte.
(Allerdings sollte diese Beschädigung inzwischen nicht mehr auftreten, und du kannst die Meldung getrost ignorieren. Ab der nächsten Version kann die Meldung dauerhaft deaktiviert werden)

* Falls die Meldung bei dir auch in anderen Fällen erscheinen sollte, lass es mich bitte wissen!

[dRdoS7]

Hi,

[quote="chris86"]You have done everything right.
But it seems you are performing the cutting directly on a NAS...? I have never tested that. How does this work? And is the NAS formatted in JFS?[/quote]

No, directly on the Toppy.

I did try it on a NAS. Windows 7 PC, NFS server mounted with NASMount. It didn't work. It did create some files. I copy files to the NAS with BGC TAP. I can post the MC log if you're interested.

[quote="chris86"]
Do you sometimes use the "Sleep"-Key (that one with the little clock)?[/quote]

Yes, it is used for SmartEPG to display the Timers list outside of SE. So that explains it!

I can edit the source to remove or change that, and compile it for my use.

It appears no-one else has the same problem.

I don't want to change from the "Sleep" key, because that is the one we have been using on our Toppies since 2004!!! Very had to get used to a different one.

[quote="chris86"]
Okay, I can reproduce this issue. I will try my best if I can do something about that.[/quote]

Another one that no-one else has had.

Great program BTW.

Thanks,

dRdoS7

[chris86]

No, directly on the Toppy.

Okay, that is very strange...
If you are using the internal HDD, then where does this device id come from? - '192.168.1.25:/DataF'
Could you please send me a full log from such a cut and send me a copy of your mount table on the Toppy? (You get the latter one by connecting on the Toppy via Telnet, then enter "mount".)

I can edit the source to remove or change that, and compile it for my use.

I chose the Sleep-key because I thought, that would be a key that noone uses on a regular basis. If this theory is wrong, I can use another key for this in the future... any suggestions?

Another one that no-one else has had.

Well, it is there - and anyone has to be the first to report it

[dRdoS7]

Hi,

Okay, that is very strange...
If you are using the internal HDD, then where does this device id come from? - '192.168.1.25:/DataF'
Could you please send me a full log from such a cut and send me a copy of your mount table on the Toppy? (You get the latter one by connecting on the Toppy via Telnet, then enter "mount".)

OK, here:

(none) login: 2014-04-14 10:43:11 BackgroundCopy: 7%, 186 MB/min
root
# 2014-04-14 10:43:19 BackgroundCopy: 8%, 209 MB/min
mount
rootfs on / type rootfs (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw)
none on /proc/bus/usb type usbfs (rw)
/dev/sda1 on /mnt/games type jfs (rw)
/dev/sda2 on /mnt/hd type jfs (rw)
192.168.1.25:/MediaFiles on /mnt/hd/MediaFiles/Shared type nfs (rw,vers=3,rsize=32768,wsize=32768,hard,proto=udp,timeo=7,retrans=3,sec=sys,addr=192.168.1.25)
192.168.1.25:/DataFiles on /mnt/hd/DataFiles/Shared type nfs (rw,vers=3,rsize=32768,wsize=32768,hard,proto=udp,timeo=7,retrans=3,sec=sys,addr=192.168.1.25)
# 2014-04-14 10:43:25 BackgroundCopy: 9%, 226 MB/min

I use NASMount, that is "Shared" in DataFiles folder.

I didn't even notice the reference to my NAS.

Okay, that is very strange...
I chose the Sleep-key because I thought, that would be a key that noone uses on a regular basis. If this theory is wrong, I can use another key for this in the future... any suggestions?)

Maybe add "Debug=1" in the settings file? :

I tried to compile the MC, but my TAP environment is different to your's. I used the one from this forum.

Well, it is there - and anyone has to be the first to report it

Yes, there is always one to spoil the fun!

Thanks,

dRdoS7

[Bobbycar123]

[quote="chris86"]Ich nehme an, die angezeigte Warnung lautet "Receiver vor dem Schneiden neu starten! Trotzdem fortfahren?".
Diese Meldung wird angezeigt, wenn du versuchst, eine Datei direkt nach dem Aufnehmen zu schneiden, ohne den Receiver zwischendurch einmal neu gestartet zu haben.*
Dies wird nicht empfohlen, da es in solchen Fällen durch die Firmware zu einer Beschädigung des Endes der Aufnahme kommen konnte.
(Allerdings sollte diese Beschädigung inzwischen nicht mehr auftreten, und du kannst die Meldung getrost ignorieren. Ab der nächsten Version kann die Meldung dauerhaft deaktiviert werden)

* Falls die Meldung bei dir auch in anderen Fällen erscheinen sollte, lass es mich bitte wissen![/quote]

alles klar, vielen Dank

Gruß

Werner

[keith_leitch]

Actually, I need some help with Moviecutter. Can I ask questions here? Basically, I cannot use the output with most video players on a PC, nor write it to DVD.

[chris86]

I have 3 problems...

Your issues 1 - 3 should be fixed.
Since I don't have a NAS, I cannot test the first one.
Could you please run a test cut with this version and provide me a full log of this cut?

[chris86]

Actually, I need some help with Moviecutter. Can I ask questions here? Basically, I cannot use the output with most video players on a PC, nor write it to DVD.

- And you can do that with recordings that have been not processed with MovieCutter!?
If yes, then please provide more details about what exactly you are trying to do with those files.
If no, then it is not a MC problem. Please start a new thread then!

[dRdoS7]

Hi,

I have attached both logs.

It did a FS check.

I did notice that when I finished the cut and exited MC OSD (not the TAP), when I pressed stop, the TMSArchive StopMenu didn't appear. I have only just started using the StopMenu in the last few days and don't know if it was the same with previous versions.

Thanks,

dRdoS7

EDIT:

With this version (test only?) the "Sleep" doesn't work. If I stop MC it works.

[keith_leitch]

- And you can do that with recordings that have been not processed with MovieCutter!?
If yes, then please provide more details about what exactly you are trying to do with those files.
If no, then it is not a MC problem. Please start a new thread then!

Umm..yes, I can, easily. Can't everyone? I FTP my recording onto my PC, then watch it in VLC or MPC, or import it as a clip to Windows DVD maker. However, all players other than MPC reject it after processing with MovieCutter, and Windows DVD maker claims it is corrupt.

Since my first post, I have discovered that running it through FFMPEG with the -target PAL-DVD option will allow me to use it in all of the ways mentioned above. However, I do have another question:

Does anyone know of a transcode that I can use to convert video recorded elsewhere so that it can be used with MovieCutter? I have tried several FFMPEG configurations to create MPEG2 files, but MovieCutter appears to require a NAV or INF file to go with it. I have even tried to run the RebuildNAV TAP on those files, with no luck.

[FireBird]

The stream needs to be MPEG2 Transport Stream - however that option is called in FFMPEG. And, of course, this method won't work with HD material.

[chris86]

I have attached both logs.
It did a FS check.

Thank you! Seems to work now

I did notice that when I finished the cut and exited MC OSD (not the TAP), when I pressed stop, the TMSArchive StopMenu didn't appear. I have only just started using the StopMenu in the last few days and don't know if it was the same with previous versions.

That is not a bug. It is intended behaviour. Since MC handles the Stop-Key, it shall not be processed a second time by another TAP.
But I changed that anyways. Give it a try now ;-)

EDIT:
With this version (test only?) the "Sleep" doesn't work. If I stop MC it works.

Okay, I (temporarily) removed the Exit event from the Sleep key for you. But MC still listens to this key, so it will not be sent to other TAPs...

Umm..yes, I can, easily. Can't everyone? I FTP my recording onto my PC, then watch it in VLC or MPC, or import it as a clip to Windows DVD maker. However, all players other than MPC reject it after processing with MovieCutter, and Windows DVD maker claims it is corrupt.

Well, the Australian Topfield PVRs use a stream format, which is slightly different from the European's to store their recordings.
With our devices, this issue has not been reported so far.
I am wondering now, if Australian devices do store a kind of header at the beginning of their *.mpg files?

-> Does the problem with your MediaPlayers occur on every recording that has been cut? Or does it happen only if you removed the beginning (and/or the ending) of the file?
(Could you please try that?)

-> Would you be able to provide me with a short test sample (original recording, less than a minute, which can be played in VLC and cut recording which cannot be played anymore)?

[dRdoS7]

Hi,

[quote="chris86"]
That is not a bug. It is intended behaviour. Since MC handles the Stop-Key, it shall not be processed a second time by another TAP.
But I changed that anyways. Give it a try now ;-)[/quote]

I didn't see another link, so I downloaded from the earlier post. The file was a slightly different size.

Yes, the Stop key is received by TMSArchive.

Also, I forgot to mention: the "White" key is now sent to TMSA and MC no longer appears.

I noticed that the "White" key no longer toggles between "Segment" & "Bookmarks" in MC. It now toggles menu-nomenu-mini OSD.

[quote="chris86"]
Okay, I (temporarily) removed the Exit event from the Sleep key for you. But MC still listens to this key, so it will not be sent to other TAPs...[/quote]

So, the Sleep key only works if I stop MC TAP?

I think it will be better if I only run MC manually. That way you don't have to make changes to suit only me.

When I exit MC, there is a large rectangle displayed in the top Right-hand corner. It contains "()" and the "Play" button doesn't work for a while. I guessed it might be some debugging screen?

Many thanks,

dRdoS7

[chris86]

Yes, the Stop key is received by TMSArchive.

Also, I forgot to mention: the "White" key is now sent to TMSA and MC no longer appears.

So that's good, right?
(Or are you telling me, the white key does no longer work at all!? That would be bad...)

I noticed that the "White" key no longer toggles between "Segment" & "Bookmarks" in MC. It now toggles menu-nomenu-mini OSD.

When I exit MC, there is a large rectangle displayed in the top Right-hand corner. It contains "()" and the "Play" button doesn't work for a while. I guessed it might be some debugging screen?

You are using a not-yet-released development version now, which integrates some new OSD-features. Some of the new features have not been fully implemented, neihter documented.

1. The white key toggles between 3 OSD modes: Full OSD, OSD without SegmentList, Mini OSD (which is a stub until now)
2. Toggling between Bookmark and Segment mode needs a new key.
   (Since I have not found the optimal key since now, it currently is on Guide, V/F and Fav key).
3. Behaviour of Exit-key changed:
   If you press it once, MC closes its OSD, but still continues to run in the background. It silenztly handles all its keys and you can still do anything that you could do with active OSD.
   If you press it twice, MC gets incative, letting other TAPs handle their events. (thats the behaviour of the earliert versions.
4. The black rectangle, you describe, is already intended and shows the current status of MC. But to see that, you will have to update you language file (/ProgramFiles/Settings/MovieCutter.lng). Add the following lines into the English section. Then fully exit MC and restart it.

   Code: Alles auswählen

   en_059=
   en_060=MovieCutter active
   en_061=Segment mode
   en_062=Bookmark mode
   en_063=Cut marker created
   en_064=Cut marker moved
   en_065=Cut marker deleted
   en_066=Bookmark created
   en_067=Bookmark moved
   en_068=Bookmark deleted
   en_069=Segment selected
   en_070=Selection removed
   en_071=Undo last action
   en_072=Minute jump: %d
   en_073=Minute jump off
   

So, the Sleep key only works if I stop MC TAP?

Currently yes. Maybe I will remove that in the release version for you...

That way you don't have to make changes to suit only me.

Oh no! All your reported issues were valuable and helped to find and fix some bugs in MC. So that benefits everyone! (Umm, maybe except for the Sleep-key thing )