T-Home Entertain mit dem Mac anschauen

Man kann die öffentlich rechtlichen Kanäle von T-Home Entertain auch ohne den Media-Receiver auf dem heimischen Rechner anschauen. Detailinformation gibt es hier.

Nun ist es ziemlich umständlich, das zu starten. Deshalb habe ich für meine liebe Frau ein Applescript geschrieben, das aus dem Dock heraus startbar ist.

Das könnt ihr hier runterladen: T-Home-VLC

Das Archiv enthält auch die Playlist. So ist es ein rundum sorglos Paket geworden.

Das ganze geht so:

  • File enpacken
  • T-Home-VLC.app nach Programme kopieren
  • im Dock ablegen
  • klicken

Bei mir reißt der Stream aber ab und zu ab. Dann im VLC einfach den Kanal wechseln und zurück und schon ist es wieder da. Nervig ist es aber trotzdem.

7 Kommentare

Upgrade to Snow Leopard – few problems which all could be solved

Now I have upgraded two Macs to Snow Leopard. All in all I had no problems, the installation seems to free 35 Gb – unbelievable! Read more details …

Weiter…

2 Kommentare

drobo – find ich gut

I reported about my problems with the Time Machine drive which was too small. So I bought a Drobo mass storage device beginning of July since I wanted a reliable and extensible storage solution. I am using it for Time Machine backups. only. Setting it up was pretty easy. I run the Time Machine in a sparse bundle creating with TimeTamer.

But initially the system was not very stable. Once it crashed – but did not loose the data. From time to time it refused to boot or to wake up. Finally it failed entirely. All lights were on but nothing else happened.

I contacted drobo hotline in Germany. We tried to reset the device – without success. Then I got it replaced within one day. Perfect service.

The replacement device is now very stable and boots much faster than the original one. It can happen that a new device causes problems. As long as the service of the manufacturer is ok, this is not a problem. The Drobo service was perfect in my case.

4 Kommentare

warum stimmt plötzlich die UUID nicht mehr

Heute hat TimeMachine mal wieder alle Backups gekillt. Im log steht:

Jun 27 08:32:44 buero4 /System/Library/CoreServices/backupd[479]: Starting standard backup
Jun 27 08:32:45 buero4 /System/Library/CoreServices/backupd[479]: Backing up to: /Volumes/Time Machine-Backups/Backups.backupdb
Jun 27 08:32:46 buero4 /System/Library/CoreServices/backupd[479]: Event store UUIDs don't match for volume: ExterneDaten_1
Jun 27 08:32:47 buero4 /System/Library/CoreServices/backupd[479]: Node requires deep traversal:/Volumes/ExterneDaten_1 reason:kFSEDBEventFlagMustScanSubDirs|
Jun 27 08:35:24 buero4 /System/Library/CoreServices/backupd[479]: Starting pre-backup thinning: 563.10 GB requested (including padding), 273.54 GB available

Das kann ich mir nicht erklären. Ich habe nichts an der Festplatte gemacht. Ich habe einen Memory Stick eingesteckt. Aber das mach ich jeden Tag. Warum stimmt da plötzlich die UUID nicht mehr? Oder ist es das hier?

Jun 27 08:02:20 buero4 kernel[0]: disk1s1: media is not present.
Jun 27 08:02:20: --- last message repeated 1 time ---
Jun 27 08:02:20 buero4 kernel[0]: disk1s1: media is not present.
Jun 27 08:02:20 buero4 kernel[0]:
Jun 27 08:02:20: --- last message repeated 1 time ---
Jun 27 08:02:20 buero4 kernel[0]: disk1s1: media is not present.
Jun 27 08:02:20 buero4 kernel[0]:
Jun 27 08:02:20: --- last message repeated 1 time ---
Jun 27 08:02:20 buero4 kernel[0]: disk1s1: media is not present.
Jun 27 08:02:20 buero4 kernel[0]:
Jun 27 08:02:20: --- last message repeated 1 time ---
Jun 27 08:02:20 buero4 kernel[0]: msdosfs_fat_uninit_vol: error 6 from msdosfs_fat_cache_flush
Jun 27 08:02:27 buero4 fseventsd[40]: log dir: /Volumes/NO NAME/.fseventsd getting new uuid: C36F7396-1CAB-42F5-9F63-636ACA26E40B

2 Kommentare

Safari opens awful lots of windows

Safari opens new window all the time …

but there is a solution. I found it on http://www.tuaw.com/2008/09/08/terminal-tips-force-safari-to-open-all-links-in-new-tab/

Just open Terminal (/Applications/Utilities/) and type in the following command: 

defaults write com.apple.Safari TargetedClicksCreateTabs -bool true

Once you restart Safari, all clicked links will open in a new tab. If you want to reverse the command for some reason, just replace “true” with “false.”

It also works for Safari 4.0.

4 Kommentare

Having lost my Backup History – what I have learned

I have lost my entire backup history in Time Machine. It is really a disappointer, that this great backup solution has such a weakness. The following happened:

  1. I replaced my external harddisk (with 460Gb of data)
  2. I restored the data from Time Machine (took 8 hours)
  3. I turned on Time Machine again
  4. Time Machine silently deleted all previous backups because it considered the restored data as new and tried to make space on the backup drive.
  5. Time Machine did not delete the latest backup (ok, that’s good) but refused to continue.
  6. I deleted the backup of the external harddisk.
  7. Time machine crated a new bakcup (took 10.5 hours)

But the history is gone. The main reason is, that Time Machine lost the connection to the data which itself had restored. The reason is, that Tima Machine used the MAC adress of the computer and the UUID of the partition to refer to the disks being backed up. As I created the partition on the external drive using Disk Utlity, the UUID was different (no, I do not like UUIDs! Their benefit – if there is one – is really overestimated).

How could I avoid the loss of the history? There were various solutions:

  1. Do not use Time Machine to fill the new hardisk. Use Disk Utility to clone. Hopefully the UUID is also cloned. But I did not try …
  2. Manually delete the backups of the external harddisk (this would avoid loss of backup history for the builtin drives).
  3. After restoring the data, change the UUID of the backup to the one of the new partition as shown here:

    http://www.macosxhints.com/article.php?story=20090213071015789

2009-06-03: I tried to change the UUID. It was not successful!!

However it is, Time Machine could be improved such that restoring data is the same no brainer  performing the backing.

Noch kein Kommentar

Meine Time Machine Begeisterung wurde etwas gedämpft

Heute habe ich eine externe Festplatte ausgewechselt und aus der Sicherung von Time Machine wieder hergestellt. So richtig intuitiv war das nicht, zumal TimeMachine keine (offensichtliche) Funktion hat, um eine externe Platte wieder herzustellen. Ich habe also die Platte so benannt wie die alte und dann die Top-Level Ordner in Time Machine wieder hergestellt. Das ging ja einfach.

Nun habe ich die automatische Sicherung wieder angestellt und muss feststellen, dass Time Machine die gerade restaurierten Daten wieder sichert. Das wäre ja nicht so schlimm, wenn es dabei nicht alte Backups löschen würde. Tut es aber. Da auf der externen Platte 600GB Bilder (RAW!) waren, verliere ich nun die Backups der anderen platte auch. Ich vermute, dass das ganze dann nochmal 8 Stunden dauert.

Backup requested by user

/backupd[26909]: Starting standard backup
/backupd[26909]: Backing up to: /Volumes/Time Machine-Backups/Backups.backupdb
/backupd[26909]: Event store UUIDs don't match for volume: ExterneDaten_1
/backupd[26909]: Node requires deep traversal:/Volumes/ExterneDaten_1 reason:kFSEDBEventFlagMustScanSubDirs|
/backupd[26909]: Starting pre-backup thinning: 563.34 GB requested (including padding), 37.08 GB available

Es sieht so aus, als ob Time Machine die Orientierung verliert, weil die UUIDs nicht stimmen.

Na ja, meine Kollegen wissen schon, dass ich mit UUIDs auf Kriegsfuss stehe.

Ach ja, und aus heiterem Himmel fing Spotlight auch noch an, das Sicherungslaufwerk neu zu indizieren, und das schon während ich die Platte wieder hergestellt habe. Das kann ich nicht so richtig einsehen.

Oder hätte ich die normale Sicherung nicht ausschalten dürfen während der Wiederherstellung?

2 Kommentare

How to synchronize the Camera with UTC

One of the big issues with geotagging is, that the camera needs to be synchronized with UTC such that geoencoding works precise. Today I found a way to do precisely enough. I tried it with my 20d and my 5d: Weiter…

Noch kein Kommentar

A Big Step for Geotagging on Mac

This weekend saw a big step for geotagging on Mac – I might say for geotagging at all – GPSPhotolinker 2.0 Beta.

Even if I am somewhat enthusiastic on myTracks, GPSPhotolinker is still very good and it will get much better in Version 2.0. Both tools are really great but they narrow the issue from different ends. I really would like to see the combination of both:

  • GPSPhotolinker has its focus on photos. It provides different methods determining the GPS coordinates which shall be attached to the photos.
  • myTracks has its focus on Trackmanagement including editing trackpoints. Photos are bound to trackpoints. It does not know about photos without trackpoint. Even if non tagged photos are loaded, they are attached to a trackpoint of a new track.

GPSPhotolinker 2.0 Beta 5 is very stable and also pretty fast, in particular when dealing with RAW images. I wonder how Jeff achieved this. Besides Geotagging, GPSPhotolinker evolves to a good meta data editor as well. It implements the recommendations specified by http://www.metadataworkinggroup.org.

Weiter…

Noch kein Kommentar

Edit GPX files

I found a new tool to fix my GPX tracks. Have a look on http://sourceforge.net/projects/mytracks. It also supports combining Photos with GPS data. But I do not trust it. But for removing errornous trackpoints, it is pretty good.

Noch kein Kommentar