Page 1 of 1
Old tfl recordings
Posted: Sat Aug 17, 2019 7:15 pm
by HealwSteel
I came across my old TFL recordings, which are .bin format. They dont show up in 1.5. Any idea how to view them?
Re: Old tfl recordings
Posted: Sat Aug 17, 2019 8:13 pm
by juliocpaes
HealwSteel wrote:I came across my old TFL recordings, which are .bin format. They dont show up in 1.5. Any idea how to view them?
Hi H.Steel,
check on your Myth TFL, the folder "tags" // "Local" // if have the folder "RECO" inside this folder (RECO) you should have your "TFL recordings" ... if there is no such folder, try making one.
Re: Old tfl recordings
Posted: Sun Aug 18, 2019 12:48 pm
by HealwSteel
Thanks Julio. I have the recordings folder, but the file type is .bin on the old recordings. The films I've saved with TFL 1.5 are ".type".
I've Did done a search for a converter, but keep getting .bin to text, not type. Did the updates/patches change the format? Myth II 1.80 saves the films with the type format.
Re: Old tfl recordings
Posted: Sun Aug 18, 2019 3:51 pm
by Melekor
The file extension should not matter, myth ignores it. You can use a hex editor to see what the difference is between your old and new files, just looking at the first 64 bytes which is myth's tag header.
Were the old recordings done on a mac? I suspect the .bin might be a format that encapsulates both the file and the old mac metadata.
Re: Old tfl recordings
Posted: Mon Aug 19, 2019 2:02 am
by HealwSteel
Ahh, i bet i did record them on a mac. Shucks.
Re: Old tfl recordings
Posted: Mon Aug 19, 2019 1:28 pm
by Melekor
Even if that's the case, I'm sure there's a way to extract the data.
Re: Old tfl recordings
Posted: Fri Aug 23, 2019 9:35 am
by HealwSteel
Oh Lord I distinctively remember a bad headache trying to convert a Mac replay to work on a pc before. I have no clue how to use a hex editor anymore, not that i ever did. Any experience doing a quick conversion/extraction?
Re: Old tfl recordings
Posted: Sat Aug 24, 2019 4:51 pm
by Melekor
I don't have experience, but here's something you can try:
I think your files are probably in MacBinary format.
https://en.wikipedia.org/wiki/MacBinary
You could try using MacBinConv to see if you can extract the data fork.
https://sourceforge.net/projects/macbinconv/
Usage:
Code: Select all
usage: macbinconv.exe <input> <output>
where <input> is one of:
-sfm <filename> : where filename is a Services for Macintosh NTFS file
-as <filename> : where filename is an AppleSingle encoded file
-ad <filename> <macdata> : where filename is datafork, macdata is an AppleDouble encoded file
-mb <filename> : where filename is a MacBinary I,II or III encoded file!
-dfrf <datafile> <resfile> : where datafile is the data fork of the file and resfile is the resource fork. Any of them can be none.
-osx <filename> : where filename is a MacOSX encoded file for non HFS volumes
and <output> is one of:
-sfm <filename> : writes to a file used by Serices for Macintosh should be on an NTFS volume
-as <filename> : file will be encoded to filename AppleSingle file
-ad <filename> <macdata> : file will be encoded to filename AppleDouble file
-mb <filename> : encodes the file as MacBinaryIII to filename
-dfrf <datafile> <resfile> : files data fork will be encoded to datafile while file resource fork will be encoded to resfile.
-info [md5] : prints information to the stdout, if md5 is defined prints md5 fingerprint.
-osx <filename> : where filename is a MacOSX encoded file for non HFS volumes
Suggested command line:
Code: Select all
macbinconv -mb [input] -dfrf [output] dummy.res