happpyg 20 Posted January 5, 2021 Posted January 5, 2021 I took some photos with my Drone yesterday yet despite all the date stamps I can see being correct for some reason the year in the Emby photo library shows as 1970? Can anyone see why? Not all photos in this folder did this, only the ones natively shot by the Drone, others that were modified in photoshop etc and saved again were fine and showed the correct year. Emby date added behavior is set to use file creation date which looks fine? Copy of original file : DJI_0095_drone_hdr.zip Thanks!
Happy2Play 9782 Posted January 5, 2021 Posted January 5, 2021 (edited) @LukeI see the same with this test file but don't know where 01/01/1970 is coming from. My test was on beta server. "Date added behavior for new content:" was on scan date. Spoiler File creation date : UTC 2021-01-05 23:02:20.972 File creation date (local) : 2021-01-05 15:02:20.972 File last modification date : UTC 2021-01-05 22:42:24.000 File last modification date (local) : 2021-01-05 14:42:24.000 C:\Users\Media\AppData\Roaming\Emby-Server\system>ffprobe -i "C:\Users\Media\Desktop\Videos\Photo\2021\DJI_0095_drone_hdr.JPG" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data ffprobe version 4.3.0-emby_2020_05_23-g8f222573e9+530 Copyright (c) 2007-2019 the FFmpeg developers and softworkz for Emby LLC built with gcc 9.2.0 (Rev2, Built by MSYS2 project) { Input #0, image2, from 'C:\Users\Media\Desktop\Videos\Photo\2021\DJI_0095_drone_hdr.JPG': Duration: 00:00:00.04, start: 0.000000, bitrate: 1105150 kb/s Stream #0:0: Video: mjpeg (Baseline), yuvj420p(pc, bt470bg/unknown/unknown), 4000x3000, 25 tbr, 25 tbn, 25 tbc "streams": [ { "index": 0, "codec_name": "mjpeg", "codec_long_name": "Motion JPEG", "profile": "Baseline", "codec_type": "video", "codec_time_base": "0/1", "codec_tag_string": "[0][0][0][0]", "codec_tag": "0x0000", "width": 4000, "height": 3000, "coded_width": 4000, "coded_height": 3000, "has_b_frames": 0, "pix_fmt": "yuvj420p", "level": -99, "color_range": "pc", "color_space": "bt470bg", "chroma_location": "center", "refs": 1, "r_frame_rate": "25/1", "avg_frame_rate": "0/0", "time_base": "1/25", "start_pts": 0, "start_time": "0.000000", "duration_ts": 1, "duration": "0.040000", "bits_per_raw_sample": "8", "extradata": "\n", "disposition": { "default": 0, "dub": 0, "original": 0, "comment": 0, "lyrics": 0, "karaoke": 0, "forced": 0, "hearing_impaired": 0, "visual_impaired": 0, "clean_effects": 0, "attached_pic": 0, "timed_thumbnails": 0 } } ], "chapters": [ ], "format": { "filename": "C:\\Users\\Media\\Desktop\\Videos\\Photo\\2021\\DJI_0095_drone_hdr.JPG", "nb_streams": 1, "nb_programs": 0, "format_name": "image2", "format_long_name": "image2 sequence", "start_time": "0.000000", "duration": "0.040000", "size": "5525750", "bit_rate": "1105150000", "probe_score": 50 } } Edited January 5, 2021 by Happy2Play
ebr 16185 Posted January 6, 2021 Posted January 6, 2021 That's the Unix epoch so it probably means it has a raw date of 0.
Happy2Play 9782 Posted January 6, 2021 Posted January 6, 2021 Are we saying something in the exif data not the file creation/scan date is used for photos?
happpyg 20 Posted January 9, 2021 Author Posted January 9, 2021 Thanks for the help guys, any more ideas on what is going on? I can't see a Unix epoch anywhere, all date/timestamps I can see in Windows between working and non-working files are the same? Only does this for footage straight from the drone, brand new DJI Mavic with latest firmware.
happpyg 20 Posted January 15, 2021 Author Posted January 15, 2021 Hello @Luke , is there anything I can do? Thanks
happpyg 20 Posted January 19, 2021 Author Posted January 19, 2021 @ebr @Happy2Play Hi Guys, not sure if this is still active and if Luke is seeing it? Am I missing something as it has gone stale for almost 2 weeks? Thanks!
Carlo 4561 Posted January 19, 2021 Posted January 19, 2021 This likely needs looking into as it needs to look at the file date/time when it the exif data is missing or default 1/1/70.
happpyg 20 Posted January 19, 2021 Author Posted January 19, 2021 6 hours ago, cayars said: This likely needs looking into as it needs to look at the file date/time when it the exif data is missing or default 1/1/70. Thanks cayars, I agree, the problem is I have no idea what is happening as there has been no responses despite asking - initial response from happy2play and ebr was great and instant but nothing since? I am not sure if there is something wrong with this thread or if it is being looked at at all? Not trying to push anyone but with no responses i've no idea where this is at or if it has been ignored/missed somehow? Thanks!
Carlo 4561 Posted January 19, 2021 Posted January 19, 2021 No, nothing wrong with the thread. It just needs to be looked at now by a dev.
happpyg 20 Posted January 19, 2021 Author Posted January 19, 2021 5 minutes ago, cayars said: No, nothing wrong with the thread. It just needs to be looked at now by a dev. Ok thanks
Happy2Play 9782 Posted January 19, 2021 Posted January 19, 2021 Yes as your issue is reproducible with the file provided, dev will have to comment on exactly what is happening. 1
Luke 42081 Posted January 28, 2021 Posted January 28, 2021 Your image file is actually tagged with both exif and xmp metadata. The exif data has the correct date taken, but look at what's in the xmp metadata: <?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?> <x:xmpmeta xmlns:x="adobe:ns:meta/"> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="DJI Meta Data" xmlns:tiff="http://ns.adobe.com/tiff/1.0/" xmlns:exif="http://ns.adobe.com/exif/1.0/" xmlns:xmp="http://ns.adobe.com/xap/1.0/" xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/" xmlns:drone-dji="http://www.dji.com/drone-dji/1.0/" xmlns:GPano="http://ns.google.com/photos/1.0/panorama/" xmp:ModifyDate="1970-01-01" xmp:CreateDate="1970-01-01" tiff:Make="DJI" tiff:Model="Test_Pro" dc:format="image/jpg" drone-dji:GpsLatitude="-33.4015931" drone-dji:GpsLongitude="+115.9784710" drone-dji:AbsoluteAltitude="+17.70" drone-dji:RelativeAltitude="+17.70" drone-dji:GimbalRollDegree="+0.00" drone-dji:GimbalYawDegree="+106.30" drone-dji:GimbalPitchDegree="+0.00" drone-dji:FlightRollDegree="-2.50" drone-dji:FlightYawDegree="+105.60" drone-dji:FlightPitchDegree="+2.00" drone-dji:CamReverse="0" drone-dji:GimbalReverse="0" drone-dji:SelfData="" crs:Version="7.0" crs:HasSettings="False" crs:HasCrop="False" crs:AlreadyApplied="False"> </rdf:Description> </rdf:RDF> </x:xmpmeta> <?xpacket end="w"?>
happpyg 20 Posted January 28, 2021 Author Posted January 28, 2021 53 minutes ago, Luke said: Your image file is actually tagged with both exif and xmp metadata. The exif data has the correct date taken, but look at what's in the xmp metadata: <?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?> <x:xmpmeta xmlns:x="adobe:ns:meta/"> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <rdf:Description rdf:about="DJI Meta Data" xmlns:tiff="http://ns.adobe.com/tiff/1.0/" xmlns:exif="http://ns.adobe.com/exif/1.0/" xmlns:xmp="http://ns.adobe.com/xap/1.0/" xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/" xmlns:drone-dji="http://www.dji.com/drone-dji/1.0/" xmlns:GPano="http://ns.google.com/photos/1.0/panorama/" xmp:ModifyDate="1970-01-01" xmp:CreateDate="1970-01-01" tiff:Make="DJI" tiff:Model="Test_Pro" dc:format="image/jpg" drone-dji:GpsLatitude="-33.4015931" drone-dji:GpsLongitude="+115.9784710" drone-dji:AbsoluteAltitude="+17.70" drone-dji:RelativeAltitude="+17.70" drone-dji:GimbalRollDegree="+0.00" drone-dji:GimbalYawDegree="+106.30" drone-dji:GimbalPitchDegree="+0.00" drone-dji:FlightRollDegree="-2.50" drone-dji:FlightYawDegree="+105.60" drone-dji:FlightPitchDegree="+2.00" drone-dji:CamReverse="0" drone-dji:GimbalReverse="0" drone-dji:SelfData="" crs:Version="7.0" crs:HasSettings="False" crs:HasCrop="False" crs:AlreadyApplied="False"> </rdf:Description> </rdf:RDF> </x:xmpmeta> <?xpacket end="w"?> Strange! I'll follow up with DJI, a quick google shows i'm not the only one with this issue apparently. Drone had a GPS lock and time on phone was all correct so not sure why those 2 tags still show 1970 when every other timestamp was correct. Thanks!
happpyg 20 Posted March 27, 2021 Author Posted March 27, 2021 On 1/28/2021 at 2:52 PM, Luke said: Let us know how that goes. Thanks. Hey Luke, this was the official response from DJI Support. "Please use the EXIF time as the reference. At present, the XMP time is not recorded. It is the default value so it is incorrect." Is there a way we can ignore the XMP data? Thanks
Luke 42081 Posted March 29, 2021 Posted March 29, 2021 It's possible, but we'd have to look at what unwanted side effects that might cause with other users.
happpyg 20 Posted March 30, 2021 Author Posted March 30, 2021 18 hours ago, Luke said: It's possible, but we'd have to look at what unwanted side effects that might cause with other users. Fair enough, thanks Luke
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now