12,000 bad creation dates

Hi,
I have had some problems with 10.9. 4 kernel panics since December and some Finder issues (delay in files appearing in new folders when moved, delay in creating new folders, other problems...). AppleCare has had me reinstall 10.9, migrate from my Time Capsule and other things that I can't remember in detail.
I am now noticing that I have ~12,000 files with bad creation dates. I did a search starting from 1993 and found that many. They vary; pics, docs and some apps! (I also have ~300 bad modification dates, from doing a quick similar search.)
In the past I have used a program, A Better Finder Attributes 5, to fix a few files that had shown up with bad dates. Most then were dates in the future, if I remember correctly. (I don't have any files created in the future now...)
I talked with AppleCare about this today. The guy, who has been very helpful, recommended I not use a program like that to fix them. He didn't think the bad dates would be a problem. Maybe not but I am sorely tempted to fix them.
What do you think? Why do you think this happened? Is it possible to get the original file creation and modification dates back?
Thanks.
John L

Hi Terry,
   The problem is that the creation date is not a part of UNIX file metadata but is part of the HFS metadata. That means that it's not accessible to traditional UNIX command line tools. However, Apple provides a command line tool with the Developer Tools that can do it, named SetFile. Unfortunately this tool can only act on one file at a time so it must be embedded in another command or script that invokes it repeated on a large group of files.
   You don't say which files have this problem. Thus I can't address the criteria by which you decide on which files to act. For the purpose of writing down a command, I'll assume that you want to act on all files contained in a directory whose path is /My/Directory and all of it's subdirectories. In that case you could use the following command:
find /My/Directory -type f -exec /Developer/Tools/SetFile -d 08/30/06 {} \;
Because of the "-type f" switch, this command will only act on files, not directories. That's not a requirement; you can act on directories as well. I just wanted an example to suggest that you can specify a tremendous variety of criteria in choosing on which files to act. About the only criteria you can't use in the "find" command is the creation date itself, since the "find" command is a traditional UNIX tool.
   You could still use the creation date to determine on which files to act but you would have to access it with GetFileInfo (also part of Apple's Developer Tools) and test the results in a script. Even though you have no interest in changing the modification date, if that was also "zeroed", you could use that to identify files that need to have the creation date changed.
Gary
~~~~
   Our business is run on trust. We trust you will pay
   in advance.

Similar Messages

Exit or BAdi for Validating GR posting date Greater than PO creation date.

Hi all ,
Is there any Exit or BAdi for restricting users to post GR date greater than PO creation date.
Regards
Gibi Philip

Gibi,
check this:
MB_CIN_LMBMBU04 posting of gr
Amit.

How can I change the file creation date?

I recently downloaded more than 1,000 photos from my vacation. I'm preparing to burn DVDs for a friend, and I noticed that when I copy the photos to the desktop, they don't all have the same date. I have read a couple of discussions here about the difference between photo creation date and file creation date, and I understand the difference. But something seems odd to me.
For purposes of illustration, let's take two photos: "A" was taken with the camera in the landscape position (how one normally holds a point-and-shoot); "B" was taken with the camera held in the portrait position (rotated 90 degrees). The photos were taken on April 24, about three minutes apart, but not imported into iPhoto until May 19.
In iPhoto, both files show the actual creation date. Yay!
The problem is with the files after having been copied to the desktop.
When copied to the desktop, the info panel for photo "A" shows April 24 for both the "created" and "modified" dates. Photo "B," however, shows May 19 for the "created" and "modified" dates.
Apparently, when the "B-style" photos were imported into iPhoto, the app automatically rotated them so that they are viewed correctly (without having to turn your head sideways). This is a very nice feature, but the result is that the file date changes.
Is there any way to change this? I want the DVD to show the date the photo was created, not imported to iPhoto. Picky, I know … but I'm like that.

Apparently, when the "B-style" photos were imported into iPhoto, the app automatically rotated them so that they are viewed correctly (without having to turn your head sideways). This is a very nice feature, but the result is that the file date changes.
Correct. Your camera has an Auto-Rotate feature. However, the camera does not actually rotate any pixels in the file, but instead flags it with an instruction: "Display me this way". This is a tag in the Exif metadata. When you import a file with this tag iPhoto creates a modified version. It does this because most of the apps that integrate with it - email clients, word processors etc - simply don't understand this Exif tag. So if you used the shot in a word processing doc, uploaded it to many Web site etc, the shot would come out sideways.
iPhoto has nothing to say about File dates. There are various file utilities that will edit the dates on Files
http://www.macupdate.com/app/mac/11143/a-better-finder-attributes
for instance. But there are otheers, search on MacUpdate
Regards
TD

Different creation dates on different computers

I downloaded the same photos from the same camera on the same day to my home and office computers, both into iPhoto. At home, the creation date is correct, but at work the date is wrong in every way including the year. I checked the system time and date, and that is correct. I ran TechTools pro, and found that there were other files with wrong modificatin dates, but otherwise no problems were detected. (the vast majority of file dates on my computer are correct.) We have two cameras at work, different Olympus models, and I have the same creation date problem with both of them when I download to my work computer, so I have to conclude that there is something wrong with this computer, but I can't for the life of me figure out what.

Cindy:
Welcome to the Apple Discussions. Are both computers running the same system and iPhoto versions? Are the date formats set the same on the two computers. They are set in the International pane?
First run Disk Utility and repair disk permissions. I doubt if that will do it but it's certainly won't hurt.
If you manually upload from the camera to the office computer before importing into iPhoto are the dates OK? Also try logging into another account on your office computer an trying an import into iPhoto from there. If it does import correctly then there's an issues with your primary account. It could be a bad or corrupt preference file other than iPhoto's. You can run Preferential Treatment (at VersionTracker.com) to find any obvious damaged files. Here's a method another user developed to look for incompatabilites:
Trouble Shooting Preferences
Go to HD/Users/Your_name/Library. Move the Prefs folder (in its entirety) to the desktop. Start iPhoto. Determine if problem is fixed.
If the problem IS fixed, then go to the new Prefs folder that the OS will have created and open it up. Except for those items that are obviously not related, move the contents to the old Prefs folder on the desktop, replacing what had been there. When in doubt, move the item. The worst thing that can happen is a harmless "alert" message. Then, trash what remains of the new folder. Finally, move the old (but modified) Prefs folder back to the library.
If the problem is NOT fixed, trash the new Prefs folder and move the old one back to its original location.
If none of the preveious works, a reinstall of the the combo updater that represents the latest system version on that computer might help. Follow up that reinstall with a permissions repair. Good luck.
OT

How can i change the Creation Date of a video (mts-Format)?

I work with Phohoshop Elements 13 an i use Online-Album (Revel)
My Problem:
I would like to change the Creation Date of a Video-File (mts-Format). I don't no why but the date (in Metadata) is wrong and i would like it to change. If i change it in Photoshop Elements the Date (Edit... Change Date...) it seems that the date has changed, but in reality in the Metadata is still the wrong date (see attachment).
Why this ist important for me:
The Adobe Revel (Online-Album) takes always the date from the metadata which is wrong.
Any idea how i can resolve my Problem?
How i can change the Metadata?

Hi,
Did you get help ? Or do you have a work around ? I have about 20.000 Pictures and countless videos to organize myself.
I just ran into the same problem. Except that after a while Adobe will undo the changes I have made to the date.
Here's a screen shot I just made of one of the files.
Look at this one ! This one is really interesting:
After changing the date to : 1889 . Adobe changed it to 01.01.1970 00:59

Production declaration based on order creation date in R/3

Hi,
Can we do the production declaaration in R/3 (mfbf) for PPDS planned orders sent to R/3 from APO based on order creation date?
This is because we need to differentiate between SNP and PPDS planned orders in R/3.
As there is no differentition in SNP and PPDS orders in R/3, while production decalration,
it's not possible that only PPDS orders will get consumed (in mfbf).
SO can we do production declaration based on order creation date instead of order number?
Please share the information.
Thanks,
Vinayak

Hello Santosh
Production versions are selected on the standard system according to the basic finish date, however, you can change the standard system behavior with the implementation of the following note:
351773 - Selection of production versions for planned order
Alternatively, you may use BAdI MD_MODIFY_PRODVERS to create your own logic to select the production versions.
BR
Caetano

Material Creation date by plant

Hello all,
In several of our report I need to enter the creation date of the material. My problem is that the creation date of material is a global information and sits in MARA. The users run the report by plant and therefore they are interested to know what was the creation date of the material for a specific plant and not in general. Where can I find this information? How can I know the date that the material was extended to a specific plant?
please, I need your help.
Thank you,
Liat

Dear Liat,
Plant Data for Material is stored in table MARC. Not sure, if date on which material has been extended to a particular plant will be stored in it.
If you cannot get the date from MARC, you will have to implement a proper BAdi/Enhancement so that you can store date on which material is extended to a particular plant for the combination of Material, Plant. You can fetch the same to be displayed in the reports.
You may also be interested in below transactions:
MM50 List Extendable Materials
MM60 Materials List
Regards,
Naveen.

How to Make Field "Creation Date" Mandatory (in EP Selection Screen)

Dear experts,
I am on SRM 7.0.
In Shopping Cart, i'd like to set Field "Creation Date" as Mandatory Field in EP Selection Screen / Criteria Maintenance.
Is there BADI or SPRO need to be maintained?
Thanks & regards,
Jack
Edited by: Jack4ever on Aug 9, 2011 7:42 AM
Edited by: Jack4ever on Aug 9, 2011 7:43 AM

Hi Jack,
Not sure if it possible in standard with any customizing but it might be able to achieve this through webdynpro enhancements.
Regards,
Prasanna

Bad expiration date

I have created a BPEL process with wait activity, there are input for process start time (datetime) and interval(duration). while creating an instance(workitem) in process, it moves to wait and on console i got the error
<Mar 23, 2011 9:27:53 PM SGT> <Error> <oracle.soa.bpel.engine.bpel> <BEA-000000>
<<BPELReceiveWMP::__defineExpirationDate> Bad expiration date format, and this
expiration date will be ignored
java.lang.IllegalArgumentException: Duration has to start with 'P'.
Input payload for process is:
<inputVariable>
<part name="payload">
<ns1:process>
<ns1:startDate>2011-03-23T16:30:00.000+08:00</ns1:startDate>
<ns1:interval>PT2M</ns1:interval>
</ns1:process>
</part>
</inputVariable>
And in wait have putted
string(bpws:getVariableData('inputVariable','payload','/client:process/client:startDate'))expression in "for" column
*WaitForStart (pending)
Mar 23, 2011 9:27:53 PM Bad expiration date "2011-03-23T16:30:00.000+08:00"
Mar 23, 2011 9:27:53 PM Waiting for the expiry time "never".*
environment is:
SOA 11.1.1.3.0
Jdeveloper: 11.3

I kept watching this forum for an answer and noticed one item where the user indicated that after a failure repeated attempts to clean and align heads 'magically' worked. I had not used the printer for a week and decided to give it one more try. It worked. The printer is just fine after sitting idle for a week and then trying the clean followed by align. It would still be interesting to understand why. I'm glad I didn't run out to buy more cartridges and throw this one out.

PSE 8 editor changing exif creation date

When I bought a new Dell duo-core computer with Windows 7 I upgraded from PSE 6 to 8. Since then, the editor in 8 sometimes replaces the exif creation date with the date and time it was modified. It isn't keeping the first and adding the second as date modified, just replacing it when I save a photo from the editor. It isn't doing that every time, so I can't figure out what would cause this. In two days in March, my exif creation date in 500-600 photos, many of which I didn't edit at all, were changed to either March 20 or March 21, 2010. Any idea how I can prevent this from happening? Hint: it appears as though all the photos affected were taken with an Olympus point and shoot or were scanned to PSE 6's Organizer. I can't find any photos from my DSLR that have been affected.

I hate to be the bearer of bad news, but it didn't help. I lost another photo today and had to retrieve it
for the Organizer from my Windows files. Instead of placing it next to the original photo (or in the same area), it placed it in a file called Adobe/Photoshop.com. I made sure again that the line you referred to isn't checked. In addition, when the photo doesn't get lost, the Exif date for the photo does get lost and the photo is dated today. These two problems seem to be connected, although I can never predict which one will occur. Anybody have more ideas? Could it be a Windows 7 issue rather than a Photoshop issue?

Video creation date not correctly read?

This might be a bug--it appears to me that Bridge is not reading the EXIF "date/time original" field for avi files--instead it is reading the MS windows dates which is a bad thing because any time you copy a file, these dates get changed. Even just moving a video file to another hard disk will destroy the MS windows "creation date". However the EXIF dates are untouched.
I'm using exiftool to read the metadata.
Bart

iPhoto uses EXIF metadata for it's creation date and videos do not have that metadata. You can use the Photos ➙ Adjust Date and Time.... menu option to change the date to whatever you need to get it to sort in the right order when sorted by Date.
OT

Change creation date with Applescript? Any one?

Is any one good with writing AppleScript? I've looked in the Help menu and I don't understand it.
I have a folder of over 1,000 pictures that has the incorrect "Date Created."   The correct date is actually in the "Date Modified" info for each picture. I have no idea how this came to be.
Given that there are so many files in the folder, using the "Touch -t" command in Terminal for each one individually is.. well.. daunting.
If any one knows how to write a quick Script to copy the "Date Modified" to the "Date Created" information going through each file in a folder (automated), karma would look good on you.
I've been going through page after page of web-search results of "change date created mac app" with no such luck.
(OS 10.8.2)
Thanks to any one that can help in any way.

Hi,
touch -t can change the creation date, but it can only set backward, not forward.
Here is a AppleScript that uses the class NSFileManager from the Foundation framework to change the file's creation date.
-- this script set the creation date of each file to the file's modification date
-- When the dialog will appear, just select the files whose creation date is incorrect.
set pathErr to getFiles()
if pathErr is not "" then -- if error on some file
activate
          display dialog "Done, but the creation date of some files have not been changed"
          tell application "TextEdit"
activate
                    make new document at end of documents with properties {text:(" The creation date of these files have not been changed :" & pathErr)}
end tell
else
          display dialog "The creation date of all the files have been changed."
end if
on getFiles()
script o
                    property tFiles : {}
end script
set o's tFiles to choose file with multiple selections allowed without invisibles
          set t to ""
          set tError to ""
set tc to count o's tFiles
repeat with i from 1 to tc
                    set t to t & " " & quoted form of POSIX path of (item i of o's tFiles)
if (i mod 250) = 0 or i = tc then -- 250 files sent to the shell to not exceed the limit of characters.
set r to my setCreationDateToModDate(t)
                              if r is not "" then set tError to tError & return & r
                              set t to ""
end if
end repeat
return tError
end getFiles
on setCreationDateToModDate(theseFiles)
          do shell script "/usr/bin/env python -c 'import os, sys
from Foundation import NSFileManager
df = NSFileManager.defaultManager()
nbr=len(sys.argv)
for i in range( 1, nbr ):
   f = sys.argv[i]
   my_dict, error = df.attributesOfItemAtPath_error_(f, None)
   if error is None:
      mDate = my_dict.fileModificationDate()
      cDateDict = {\"NSFileCreationDate\":mDate}
      b, error = df.setAttributes_ofItemAtPath_error_(cDateDict , f, None)
      if not b: print f' " & theseFiles
end setCreationDateToModDate
Works on OS X 10.5.x or newer.

Applescript for matching two files creation date

Hello,
I reopen here a question that I posted on another forum (macrumors):
I have converted almost 1,000 video files from MPG1 to MOV in order importing them to Final Cut Pro (FCP can't import directly MPG1!).
So I have TWO folders:
Folder 1 with the original VideoXXXX.mpg1 files
Folder 2 the converted VideoXXXX.mov files.
The file names on both folders are the same. And the number of files in the two folders are the same.
My problem is that the creation date of files in the Folder 2 is the "conversion" time (July 2012) instead the original creation time (from 2005 to 2010).
When imported to FCP, I need the creation time. The name doesn't include the time, so I don't know the file date looking only at the file name.
I need an Apple Script for changing the creation date to the files in Folder 2 files matching the creation date on the Folder 1 files.
- For file n on Folder 1, take name and creation date
- Look for the same file name on Folder 2
- Set creation date of file on Folder 2 to Creation date of original file
I have seen that it can be made with the "touch" command, but I'm new to applescripting and any help would be very appreciated!!
Thanks

Wooow...
How many helping responses! Thanks to you all.
I am trying the first sugested solution.
I have tried adding "file" to theOriginalFile twtwtw script.
(name of file theOriginalFile)
But the error persists (I changed -5 to -4, as the extension is only MPG)
tell application "System Events"
get POSIX path of every file of folder "HD Mac:users:fhuet:Desktop:Vid1" whose name extension = "MPG"
--> {"/Users/fhuet/Desktop/Vid1/MOV04859.MPG", "/Users/fhuet/Desktop/Vid1/MOV04860.MPG", "/Users/fhuet/Desktop/Vid1/MOV04882.MPG", "/Users/fhuet/Desktop/Vid1/MOV04905.MPG", "/Users/fhuet/Desktop/Vid1/MOV04906.MPG"}
get creation date of file "/Users/fhuet/Desktop/Vid1/MOV04859.MPG"
--> date "viernes, 31 de diciembre de 2004 23:39:00"
get text 1 thru -4 of name of file "/Users/fhuet/Desktop/Vid1/MOV04859.MPG"
--> error number -1720 from text 1 thru -4 of name of file "/Users/fhuet/Desktop/Vid1/MOV04859.MPG"
Resultado:
error "System Events ha detectado un error: Espectro no válido." number -1720 from text 1 thru -4 of name of file "/Users/fhuet/Desktop/Vid1/MOV04859.MPG"
If I do
set strippedFileName to name of file theOriginalFile
I got:
tell application "System Events"
get POSIX path of every file of folder "HD Mac:users:fhuet:Desktop:Vid1" whose name extension = "MPG"
--> {"/Users/fhuet/Desktop/Vid1/MOV04859.MPG", "/Users/fhuet/Desktop/Vid1/MOV04860.MPG", "/Users/fhuet/Desktop/Vid1/MOV04882.MPG", "/Users/fhuet/Desktop/Vid1/MOV04905.MPG", "/Users/fhuet/Desktop/Vid1/MOV04906.MPG"}
get creation date of file "/Users/fhuet/Desktop/Vid1/MOV04859.MPG"
--> date "viernes, 31 de diciembre de 2004 23:39:00"
get name of file "/Users/fhuet/Desktop/Vid1/MOV04859.MPG"
--> "MOV04859.MPG"
So it's OK. After that, obviously, it gives another error.
So, the problem is with the instruction
set strippedFileName to text 1 thru -4 of (name of file theOriginalFile). There must be a sintaxis error on that. It says "ESPECTRO NO VALIDO" ERROR
I keep trying and will try the other options.
But I'd like to test all of them, as it's the best way to well understand and study the lenguage.
Thanks again.

IPhoto has changed the creation dates to all of my photos

I recently bought a new MacBook Pro, my first computer since my iMac circa 2005. I've successfully transfered all of my photos to the new computer, but iPhoto has changed the creation dates of every file, so they're no longer in chronological order. I've used DVDs and Dropbox, I've exported the files, copied the data files from the hard drive, everything, but the result is still the same. I contemplated changing each file manually, but I have over 3,000 photos. Has anyone had this problem? Is there a way I can restore the correct dates?

Hi Keith,
Yes, it's date that the photo was taken that has been changed. When I look at the "photo info" of each individual photo, the "original date" is correct, but the transferred photos on my new computer always change to a 2007 date, despite the fact that the photos were taken as early as 2002.
Does this make more sense?
K

FMS 3.5 says 'Bad network data': error in handling RTMP extended timestamps / chunkSize?

Hello all,
For a client, I am working on a project where a live RTMP stream is published to an Adobe FMS 3.5.6 server from a java application, using Red5 0.9.1 RTMPClient code.
This works fine, until the timestamp becomes higher than 0xFFFFFF after 4.6 hours, and the RTMP extended timestamp field starts being used. I have already found: when the extended timestamp was written after the header, the last 4 bytes of the data were being cut off. I have fixed this locally, and now the data being sent seems to me to be conformant to the spec. However, FMS still throws an error message in the core log and then kills the connection from the Red5 client. Here is the error message:
This is the error message:
2011-06-03 14:28:02 13060 (e)2611029 Bad network data; terminating connection : chunkstream error:message length 11893407 is longerthan max rtmp packet length -
2011-06-03 14:28:02 13060 (e)2631029 Bad network data; terminating connection : (Adaptor: _defaultRoot_, VHost: _defaultVHost_, IP: 127.0.0.1, App: live/_definst_, Protocol: rtmp, Client: 5290168480216205379, Handle: 2147942405) : 05 FF FF FF 00 13 = 09 01 00 00 00 01 00 01 01 ' 01 00 00 00 00 00 13 4 09 0 00 00 01 ! 9A & L 0F FA F6 12 , B4 A6 CE H 8A AB DC G BB d k 1B 9F ) 13 13 D2 9A E5 t 8 B8 8D 94 ! 8A AE F6 AF } " U 0 D3 Q EF FF ~ 8D 97 D9 FF BE A3 F3 C9 97 o 9D # F9 7F h A4 F7 } / FB & F1 DC 9C BF BD D3 E7 CA 97 FE E2 B9 E4 F7 9E 1A F6 BA } C9 w FC _ / / w FE n EF D7 P 9C F4 BE 82 8E F7 | BE 97 B4 BB D7 FE ED I / FB D1 93 9A F9 X \ 85 BD DD I E3 4 E8 M 13 D3 " ) BE A9 92 E5 83 D4 B4 12 DE D5 A3 E6 F4 k DE BF Q 3 A0 g r A4 f D9 BD w * } F7 r 8A S 2 . AB BD EE ^ l f AF E1 0B $ AF 9D D7 - BF E8 ! D3 } D3 i E3 B8 F2 M A8 " B1 A5 EF s ] A5 BC 96 E5 u e X q D2 F1 r F9 i 92 b EE Z d F9 * A6 BB FD 17 w 4 DD 3 o u EB ] ] EF FE B5 B1 0A F2 A0 DD FD B2 98 DF E8 e F6 CB FD 96 V % A5 D5 k ] FD w EF AF k v AA E8 ! 9F / w BE FA 9A _ E F2 D3 , ? 17 } AD 7 EC B3 } 07 B5 | z { { A5 = 11 90 CF BF ; 4 FE EF 95 F7 E7 DF B9 , AF z 91 CF C9 BD DE CB { F5 17 } F2 E5 D7 DF z E6 [ 96 > Y m 9F EB AF DD D8 E8 v B9 A8 E9 % A7 | 1 CF 8B D Z k N DF F8 N FA S R FE . ~ CB A 9 E1 ) 8F 8E BB EC c 6 13 F1 AC FD FD FC 8A F7 F3 K B9 FA ^ / A4 FC B9 AA F6 DE C2 [ 1A E c r B3 BF E5 EC B5 x 94 FD . A9 t I Q % EA EC DE | K FE z A4 97 F9 " 1 0F CA FB F5 F5 p 9E 99 3 - ; B8 F4 F1 FF t A3 EC BC # DE AC 91 13 19 o < 06 F5 FD 7F 7 _ $ D B t B5 0D 8A C1 C1 BA 0B FE DB B7 83 _ } BD z F7 CB { FC M A9 8D = D5 B1 < 85 = EF E1 ; BA H y FC BC B4 C A2 D9 ` e E4 94 H 5 13 ' 93 93 8E E C2 1C R 97 9 X B7 FF 10 9F { ) F1 CF AB AC ] EE H A2 DE D3 C5 m F6 K A2 A7 A2 89 D2 z EB DF 97 ^ k 9E 99 BB E7 B6 97 w { ~ + C7 B2 } FE ' C4 | B6 o H DD r A8 9F DC FF F9 Q b l 93 T B6 EE FF 11 j CD s P C F1 3 R I F8 D8 R 9D 93 AA D5 + DE FC BE " B9 E1 ` CB BD 0F F5 C7 AA w CF 8D p 9A F7 g f N FF 84 B7 K Q 93 g E1 - D3 s } w v AE 96 98 ED CF BA E9 2 . f 99 95 97 o 13 CA F7 s e $ F4 B5 15 C4 A8 DE M F7 w \ 8D 00 C6 C2 b D3 / 7 w F2 ' BF CD 89 FF > D7 FB BC A2 S N FB A5 CD AF D3 F9 9D DF AE B5 17 CF 9D B7 , B9 9 ^ 7F [ 93 84 F7 } _ EA DF u \ 99 Z t E CA M EF 7 " AD FE 92 9E n 7F EB D8 C { 99 8B 9E w H BF B1 | g 9F F3 FA E1 - E5 CB BB x CF p 8B D2 w v EF w FA E2 F7 s C5 AC $ FC B4 DB BE G E4 DC F0 A0 96 F3 ! t DC FF % A5 CB A4 ^ AB D2 BD E7 9A E ' 08 + AF U 17 EB 8A w A7 N E4 A5 x 93 12 _ - ; 09 DD DF m 11 BE w \ } BA D3 t BC D9 97 9B C5 7F D8 H F1 D 7 8A ^ FA n F0 B8 W E6 84 5 - 8 B5 h o C4 F7 83 P 88 CB AE m t BB L 95 A9 s 90 A2 Y o DF K _ / l D2 D1 C9 91 ' E4 BD / / D 97 m BB E7 14 93 % C5 ; DD CF D8 : ~ B5 4 F FA U F0 8F w w DC FD 83 FC 13 EF w p DA A5 07 _ * - 1D 14 9D D5 84 F E6 F0 FF E4 15 w n A5 9F DE d AE F5 " - f D2 AE 96 1F # FA F1 x C1 L DF l M 06 8A E4 z DB 17 BA l DA e 15 CD 85 86 1F 09 82 h ] C6 { E7 C5 AF Z C5 B0 83 v D9 03 FC / ~ -
The message for which the hex dump is displayed, is a video message of size 4925 bytes. Below is the basic logging in my application:
*** Event sent to RTMP connector: Video - ts: 16777473 length: 4925. Waiting time: -57937, event timestamp: 16777473
14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.s.consumer.ConnectionConsumer - Message timestamp: 16777473
14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Channel id: 5
14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Last ping time for connection: -1
14:28:02.045 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Client buffer duration: 0
14:28:02.046 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - Packet timestamp: 16777473; tardiness: -30892; now: 1307104082045; message clock time: 1307104051152, dropLiveFuturefalse
14:28:02.046 [RtmpPublisher-workerThread] DEBUG o.r.s.n.r.codec.RTMPProtocolEncoder - !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!12b Wrote expanded timestamp field
14:28:02.046 [NioProcessor-22] DEBUG o.r.server.net.rtmp.BaseRTMPHandler - Message sent
I have captured the entire frame containing this message with wireshark, and annotated it a bit. You can find it here:
http://pastebin.com/iVtphPgU
The video message of 4925 bytes (hex 00 13 3D) is cut up into chunks of 1024 bytes (chunkSize 1024 set by Red5 client and sent to FMS). Indeed, after the 12-byte header and the 4-byte extended timestamp, there are 1024 bytes before the 1-byte header for the next chunk (hex C5). The chunks after that also contain 1024 bytes after the chunk header. This appears correct to me (though please correct me if I'm wrong).
When we look at the error message in the core log, the hex dump displayed also contains 1024 bytes, but it starts from the beginning of the message header. The last 16 bytes of the message chunk itself are not shown.
My question is this: is the hex dump in the error message always capped to 1024 bytes, or did FMS really read too little data?
Something that may be of help, is the reported 'too long' message length 11893407. This corresponds to hex B5 7A 9F, which can also be found in the packet, namely at row 0c60 (I've annotated it as [b5 7a 9f]. This location is exactly 16 bytes after the start of the 4th chunk data, not really a place to look for timestamps.
My assumptions during this bug hunting session were the following (would be nice if someone could validate these for me):
- message length, as specified in the RTMP 12 and 8-bit headers, defines the total number of data bytes for the message, NOT including the header of the first message chunk, its extended timestamp field, or the 1-byte headers for subsequent chunks. The behaviour is the same whether or not the message has an extended timestamp.
- chunk size, as set by the chunkSize message, defines the total number of data bytes for the chunk, not incuding the header or extended timestamp field. The behaviour is the same whether or not the message has an extended timestamp.
I believe I've chased this problem as far as I can without having access to the FMS 3.5 code, or at least being able to crank up the debug logging to the per-message level. I realize it's a pretty detailed issue and a long shot, but being able to publish a stream continuously 24/7 is critical for the project.
I would be very grateful if someone could have a look at this hex dump to see if the message itself is correct, and if so, to have a look at how FMS3.5.6 handles this.
Don't hesitate to ask me for more info if it can help.
Thanks in advance
Davy Herben
Solidity

Hello,
It took a bit longer than expected, but I have managed to create a minimal test application that will reproduce the error condition on all machines I've tested on. The application will simply read an H264 file and publish it to an FMS as a live stream. To hit the error condition faster, without having to wait 4.6 hours, the application will add a fixed offset to all timestamps before sending it to the FMS.
I have created two files:
http://www.solidity.be/publishtest.jar : Runnable java archive with all libraries built in
http://www.solidity.be/publishtest.zip : Zip file containing sources and libraries
You can run the jar as follows:
java -jar publishtest.jar <inputFile> <server> <port> <application> <stream> <timestampOffset>
- inputFile: path to an H264 input video file
- server: hostname or IP of FMS server to publish to
- port: port number to publish to (1935)
- application: application to publish to (live)
- stream: stream to publish to (output)
- timestampOffset: nr of milliseconds to add to the timestamp of each event, in hexadecimal format. Putting FFFFFF here will cause the server to reject the connection immediately, while FFFF00 or FFF000 will allow the publishing to run for awhile before the FMS kills it
Example of a complete command line:
java -jar publishtest.jar /home/myuser/Desktop/movie.mp4 localhost 1935 live output FFF000
Good luck with the bug hunting. Let me know if there is anything I can help you with.
Kind regards,
Davy Herben

12,000 bad creation dates

Similar Messages

Maybe you are looking for