#xmp — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #xmp, aggregated by home.social.
-
Fellow #photographers who use #lightroom - pro tip and life saver - write your edits back to the file system using .XMP’s - so that when your catalog file falls over - you can simply restore your edits from disk.
Otherwise you risk losing all of your edits (don’t ask me how I know).
-
Fellow #photographers who use #lightroom - pro tip and life saver - write your edits back to the file system using .XMP’s - so that when your catalog file falls over - you can simply restore your edits from disk.
Otherwise you risk losing all of your edits (don’t ask me how I know).
-
Fellow #photographers who use #lightroom - pro tip and life saver - write your edits back to the file system using .XMP’s - so that when your catalog file falls over - you can simply restore your edits from disk.
Otherwise you risk losing all of your edits (don’t ask me how I know).
-
Fellow #photographers who use #lightroom - pro tip and life saver - write your edits back to the file system using .XMP’s - so that when your catalog file falls over - you can simply restore your edits from disk.
Otherwise you risk losing all of your edits (don’t ask me how I know).
-
Fellow #photographers who use #lightroom - pro tip and life saver - write your edits back to the file system using .XMP’s - so that when your catalog file falls over - you can simply restore your edits from disk.
Otherwise you risk losing all of your edits (don’t ask me how I know).
-
XMポイント(XMP)はアカウントのステータスごとに、貯まるポイントが変わるので効率よく貯めるためにはまずステータスを上げるのが重要です。
貯まったXMポイント(XMP)はボーナスや現金に交換することができます。
-
XMポイント(XMP)はアカウントのステータスごとに、貯まるポイントが変わるので効率よく貯めるためにはまずステータスを上げるのが重要です。
貯まったXMポイント(XMP)はボーナスや現金に交換することができます。
-
XMポイント(XMP)はアカウントのステータスごとに、貯まるポイントが変わるので効率よく貯めるためにはまずステータスを上げるのが重要です。
貯まったXMポイント(XMP)はボーナスや現金に交換することができます。
-
#TIL the `Object Name` field in #IPTC contains the title but truncated at 64 characters, whereas the `ImageTitle` field in #XMP or `Title`field in #DublinCore contain the full title. 🤷♂️
When you want to find the needle in the haystack… hum wait, no, a field in a photo metadata, there's #ExifTool: https://exiftool.org/TagNames/
-
#TIL the `Object Name` field in #IPTC contains the title but truncated at 64 characters, whereas the `ImageTitle` field in #XMP or `Title`field in #DublinCore contain the full title. 🤷♂️
When you want to find the needle in the haystack… hum wait, no, a field in a photo metadata, there's #ExifTool: https://exiftool.org/TagNames/
-
#TIL the `Object Name` field in #IPTC contains the title but truncated at 64 characters, whereas the `ImageTitle` field in #XMP or `Title`field in #DublinCore contain the full title. 🤷♂️
When you want to find the needle in the haystack… hum wait, no, a field in a photo metadata, there's #ExifTool: https://exiftool.org/TagNames/
-
#TIL the `Object Name` field in #IPTC contains the title but truncated at 64 characters, whereas the `ImageTitle` field in #XMP or `Title`field in #DublinCore contain the full title. 🤷♂️
When you want to find the needle in the haystack… hum wait, no, a field in a photo metadata, there's #ExifTool: https://exiftool.org/TagNames/
-
#TIL the `Object Name` field in #IPTC contains the title but truncated at 64 characters, whereas the `ImageTitle` field in #XMP or `Title`field in #DublinCore contain the full title. 🤷♂️
When you want to find the needle in the haystack… hum wait, no, a field in a photo metadata, there's #ExifTool: https://exiftool.org/TagNames/
-
📢 Honored to return to Yale University last week to speak at the Department of Computer Science colloquium on Operating Systems security -- exactly 10 years after my first talk there on the same topic!
In this "tin anniversary" edition, I reflected on how OS kernel exploitation and defense have evolved over the past decade, and shared highlights from some of our recent work in the field over the last five years:
✳️ xMP (IEEE S&P 2020: 📄 https://cs.brown.edu/~vpk/papers/xmp.sp20.pdf, 💾 https://github.com/virtsec/xmp) — Selective intra-kernel memory isolation using hardware-assisted virtualization.
✳️ SafeSLAB (ACM CCS 2024: 📄 https://cs.brown.edu/~vpk/papers/safeslab.ccs24.pdf, 💾 https://github.com/tum-itsec/safeslab) — Kernel heap hardening through memory tagging.
✳️ EPF (USENIX ATC 2023: 📄 https://cs.brown.edu/~vpk/papers/epf.atc23.pdf, 💾 https://gitlab.com/brown-ssl/epf) — Exploiting the (e)BPF sub-system for bypassing modern protections and ways to fix this.
(Joint work with @mikepo, Marius Momeu, Vaggelis Atlidakis, @dijin, and Sergej Proskurin.)
If this area of research interests you, you might also find our recent work on BeeBox (strengthening eBPF against transient execution attacks, USENIX Security 2024: 📄 https://cs.brown.edu/~vpk/papers/beebox.sec24.pdf, 💾 https://gitlab.com/brown-ssl/beebox) and IUBIK (leveraging memory tagging and pointer authentication to isolate attacker-controlled data in kernel space, to appear in IEEE S&P 2025) worth a look.
It was a real pleasure catching up with friends, colleagues, and students. And with the spring weather fully cooperating, I couldn't resist snapping a few photos of Yale's beautiful campus in the early morning light.
Thank you to my host Charalampos Papamanthou and the Yale CS department for the warm welcome and thoughtful discussion!
-
📢 Honored to return to Yale University last week to speak at the Department of Computer Science colloquium on Operating Systems security -- exactly 10 years after my first talk there on the same topic!
In this "tin anniversary" edition, I reflected on how OS kernel exploitation and defense have evolved over the past decade, and shared highlights from some of our recent work in the field over the last five years:
✳️ xMP (IEEE S&P 2020: 📄 https://cs.brown.edu/~vpk/papers/xmp.sp20.pdf, 💾 https://github.com/virtsec/xmp) — Selective intra-kernel memory isolation using hardware-assisted virtualization.
✳️ SafeSLAB (ACM CCS 2024: 📄 https://cs.brown.edu/~vpk/papers/safeslab.ccs24.pdf, 💾 https://github.com/tum-itsec/safeslab) — Kernel heap hardening through memory tagging.
✳️ EPF (USENIX ATC 2023: 📄 https://cs.brown.edu/~vpk/papers/epf.atc23.pdf, 💾 https://gitlab.com/brown-ssl/epf) — Exploiting the (e)BPF sub-system for bypassing modern protections and ways to fix this.
(Joint work with @mikepo, Marius Momeu, Vaggelis Atlidakis, @dijin, and Sergej Proskurin.)
If this area of research interests you, you might also find our recent work on BeeBox (strengthening eBPF against transient execution attacks, USENIX Security 2024: 📄 https://cs.brown.edu/~vpk/papers/beebox.sec24.pdf, 💾 https://gitlab.com/brown-ssl/beebox) and IUBIK (leveraging memory tagging and pointer authentication to isolate attacker-controlled data in kernel space, to appear in IEEE S&P 2025) worth a look.
It was a real pleasure catching up with friends, colleagues, and students. And with the spring weather fully cooperating, I couldn't resist snapping a few photos of Yale's beautiful campus in the early morning light.
Thank you to my host Charalampos Papamanthou and the Yale CS department for the warm welcome and thoughtful discussion!
-
📢 Honored to return to Yale University last week to speak at the Department of Computer Science colloquium on Operating Systems security -- exactly 10 years after my first talk there on the same topic!
In this "tin anniversary" edition, I reflected on how OS kernel exploitation and defense have evolved over the past decade, and shared highlights from some of our recent work in the field over the last five years:
✳️ xMP (IEEE S&P 2020: 📄 https://cs.brown.edu/~vpk/papers/xmp.sp20.pdf, 💾 https://github.com/virtsec/xmp) — Selective intra-kernel memory isolation using hardware-assisted virtualization.
✳️ SafeSLAB (ACM CCS 2024: 📄 https://cs.brown.edu/~vpk/papers/safeslab.ccs24.pdf, 💾 https://github.com/tum-itsec/safeslab) — Kernel heap hardening through memory tagging.
✳️ EPF (USENIX ATC 2023: 📄 https://cs.brown.edu/~vpk/papers/epf.atc23.pdf, 💾 https://gitlab.com/brown-ssl/epf) — Exploiting the (e)BPF sub-system for bypassing modern protections and ways to fix this.
(Joint work with @mikepo, Marius Momeu, Vaggelis Atlidakis, @dijin, and Sergej Proskurin.)
If this area of research interests you, you might also find our recent work on BeeBox (strengthening eBPF against transient execution attacks, USENIX Security 2024: 📄 https://cs.brown.edu/~vpk/papers/beebox.sec24.pdf, 💾 https://gitlab.com/brown-ssl/beebox) and IUBIK (leveraging memory tagging and pointer authentication to isolate attacker-controlled data in kernel space, to appear in IEEE S&P 2025) worth a look.
It was a real pleasure catching up with friends, colleagues, and students. And with the spring weather fully cooperating, I couldn't resist snapping a few photos of Yale's beautiful campus in the early morning light.
Thank you to my host Charalampos Papamanthou and the Yale CS department for the warm welcome and thoughtful discussion!
-
📢 Honored to return to Yale University last week to speak at the Department of Computer Science colloquium on Operating Systems security -- exactly 10 years after my first talk there on the same topic!
In this "tin anniversary" edition, I reflected on how OS kernel exploitation and defense have evolved over the past decade, and shared highlights from some of our recent work in the field over the last five years:
✳️ xMP (IEEE S&P 2020: 📄 https://cs.brown.edu/~vpk/papers/xmp.sp20.pdf, 💾 https://github.com/virtsec/xmp) — Selective intra-kernel memory isolation using hardware-assisted virtualization.
✳️ SafeSLAB (ACM CCS 2024: 📄 https://cs.brown.edu/~vpk/papers/safeslab.ccs24.pdf, 💾 https://github.com/tum-itsec/safeslab) — Kernel heap hardening through memory tagging.
✳️ EPF (USENIX ATC 2023: 📄 https://cs.brown.edu/~vpk/papers/epf.atc23.pdf, 💾 https://gitlab.com/brown-ssl/epf) — Exploiting the (e)BPF sub-system for bypassing modern protections and ways to fix this.
(Joint work with @mikepo, Marius Momeu, Vaggelis Atlidakis, @dijin, and Sergej Proskurin.)
If this area of research interests you, you might also find our recent work on BeeBox (strengthening eBPF against transient execution attacks, USENIX Security 2024: 📄 https://cs.brown.edu/~vpk/papers/beebox.sec24.pdf, 💾 https://gitlab.com/brown-ssl/beebox) and IUBIK (leveraging memory tagging and pointer authentication to isolate attacker-controlled data in kernel space, to appear in IEEE S&P 2025) worth a look.
It was a real pleasure catching up with friends, colleagues, and students. And with the spring weather fully cooperating, I couldn't resist snapping a few photos of Yale's beautiful campus in the early morning light.
Thank you to my host Charalampos Papamanthou and the Yale CS department for the warm welcome and thoughtful discussion!
-
📢 Honored to return to Yale University last week to speak at the Department of Computer Science colloquium on Operating Systems security -- exactly 10 years after my first talk there on the same topic!
In this "tin anniversary" edition, I reflected on how OS kernel exploitation and defense have evolved over the past decade, and shared highlights from some of our recent work in the field over the last five years:
✳️ xMP (IEEE S&P 2020: 📄 https://cs.brown.edu/~vpk/papers/xmp.sp20.pdf, 💾 https://github.com/virtsec/xmp) — Selective intra-kernel memory isolation using hardware-assisted virtualization.
✳️ SafeSLAB (ACM CCS 2024: 📄 https://cs.brown.edu/~vpk/papers/safeslab.ccs24.pdf, 💾 https://github.com/tum-itsec/safeslab) — Kernel heap hardening through memory tagging.
✳️ EPF (USENIX ATC 2023: 📄 https://cs.brown.edu/~vpk/papers/epf.atc23.pdf, 💾 https://gitlab.com/brown-ssl/epf) — Exploiting the (e)BPF sub-system for bypassing modern protections and ways to fix this.
(Joint work with @mikepo, Marius Momeu, Vaggelis Atlidakis, @dijin, and Sergej Proskurin.)
If this area of research interests you, you might also find our recent work on BeeBox (strengthening eBPF against transient execution attacks, USENIX Security 2024: 📄 https://cs.brown.edu/~vpk/papers/beebox.sec24.pdf, 💾 https://gitlab.com/brown-ssl/beebox) and IUBIK (leveraging memory tagging and pointer authentication to isolate attacker-controlled data in kernel space, to appear in IEEE S&P 2025) worth a look.
It was a real pleasure catching up with friends, colleagues, and students. And with the spring weather fully cooperating, I couldn't resist snapping a few photos of Yale's beautiful campus in the early morning light.
Thank you to my host Charalampos Papamanthou and the Yale CS department for the warm welcome and thoughtful discussion!
-
Ich bin überzeugt: Fotoverwaltungssoftware sollte Metadaten immer direkt in den Bilddateien speichern – plattform- und softwareübergreifend nutzbar.
Ob Gesichterkennung, Beschreibungstext, Kategorien oder manuelle Tags – all diese Infos gehören nicht nur in eine Datenbank, sondern auch als Metadaten direkt ins #Bild (EXIF/XMP/IPTC etc.).
Ich habe im Laufe der Jahre zwei Programme intensiver genutzt:
Damals unter Windows: #Picasa (RIP). Heute unter Linux: #Digikam.
Jetzt überlege ich, auf eine serverbasierte Lösung umzusteigen – aber immer bleibt dieselbe Frage:
Wie #portabel sind meine Daten, wenn die Software ausfällt oder ich wechseln will?
Eine Metadatenstrategie, die auf offene Standards setzt, erleichtert Backups, Migration, parallele Nutzung und langfristige Verfügbarkeit.
Wie seht ihr das?
#Fotomanagement #EXIF #XMP #Linux #Selfhosted #Fotosammlung #Foto -
Ich bin überzeugt: Fotoverwaltungssoftware sollte Metadaten immer direkt in den Bilddateien speichern – plattform- und softwareübergreifend nutzbar.
Ob Gesichterkennung, Beschreibungstext, Kategorien oder manuelle Tags – all diese Infos gehören nicht nur in eine Datenbank, sondern auch als Metadaten direkt ins #Bild (EXIF/XMP/IPTC etc.).
Ich habe im Laufe der Jahre zwei Programme intensiver genutzt:
Damals unter Windows: #Picasa (RIP). Heute unter Linux: #Digikam.
Jetzt überlege ich, auf eine serverbasierte Lösung umzusteigen – aber immer bleibt dieselbe Frage:
Wie #portabel sind meine Daten, wenn die Software ausfällt oder ich wechseln will?
Eine Metadatenstrategie, die auf offene Standards setzt, erleichtert Backups, Migration, parallele Nutzung und langfristige Verfügbarkeit.
Wie seht ihr das?
#Fotomanagement #EXIF #XMP #Linux #Selfhosted #Fotosammlung #Foto -
Ich bin überzeugt: Fotoverwaltungssoftware sollte Metadaten immer direkt in den Bilddateien speichern – plattform- und softwareübergreifend nutzbar.
Ob Gesichterkennung, Beschreibungstext, Kategorien oder manuelle Tags – all diese Infos gehören nicht nur in eine Datenbank, sondern auch als Metadaten direkt ins #Bild (EXIF/XMP/IPTC etc.).
Ich habe im Laufe der Jahre zwei Programme intensiver genutzt:
Damals unter Windows: #Picasa (RIP). Heute unter Linux: #Digikam.
Jetzt überlege ich, auf eine serverbasierte Lösung umzusteigen – aber immer bleibt dieselbe Frage:
Wie #portabel sind meine Daten, wenn die Software ausfällt oder ich wechseln will?
Eine Metadatenstrategie, die auf offene Standards setzt, erleichtert Backups, Migration, parallele Nutzung und langfristige Verfügbarkeit.
Wie seht ihr das?
#Fotomanagement #EXIF #XMP #Linux #Selfhosted #Fotosammlung #Foto -
Ich bin überzeugt: Fotoverwaltungssoftware sollte Metadaten immer direkt in den Bilddateien speichern – plattform- und softwareübergreifend nutzbar.
Ob Gesichterkennung, Beschreibungstext, Kategorien oder manuelle Tags – all diese Infos gehören nicht nur in eine Datenbank, sondern auch als Metadaten direkt ins #Bild (EXIF/XMP/IPTC etc.).
Ich habe im Laufe der Jahre zwei Programme intensiver genutzt:
Damals unter Windows: #Picasa (RIP). Heute unter Linux: #Digikam.
Jetzt überlege ich, auf eine serverbasierte Lösung umzusteigen – aber immer bleibt dieselbe Frage:
Wie #portabel sind meine Daten, wenn die Software ausfällt oder ich wechseln will?
Eine Metadatenstrategie, die auf offene Standards setzt, erleichtert Backups, Migration, parallele Nutzung und langfristige Verfügbarkeit.
Wie seht ihr das?
#Fotomanagement #EXIF #XMP #Linux #Selfhosted #Fotosammlung #Foto -
Ich bin überzeugt: Fotoverwaltungssoftware sollte Metadaten immer direkt in den Bilddateien speichern – plattform- und softwareübergreifend nutzbar.
Ob Gesichterkennung, Beschreibungstext, Kategorien oder manuelle Tags – all diese Infos gehören nicht nur in eine Datenbank, sondern auch als Metadaten direkt ins #Bild (EXIF/XMP/IPTC etc.).
Ich habe im Laufe der Jahre zwei Programme intensiver genutzt:
Damals unter Windows: #Picasa (RIP). Heute unter Linux: #Digikam.
Jetzt überlege ich, auf eine serverbasierte Lösung umzusteigen – aber immer bleibt dieselbe Frage:
Wie #portabel sind meine Daten, wenn die Software ausfällt oder ich wechseln will?
Eine Metadatenstrategie, die auf offene Standards setzt, erleichtert Backups, Migration, parallele Nutzung und langfristige Verfügbarkeit.
Wie seht ihr das?
#Fotomanagement #EXIF #XMP #Linux #Selfhosted #Fotosammlung #Foto -
Been busy deep diving into #digikam and #darktable... But I've entered a deeper rabbit hole —my really messy photo #metadata! Learnt a lot about #xmp #exif and #iptc, and using #exiftool (which is an amazing tool by Phil Harvey). #PhotoManagement #dam #photometadata
-
Been busy deep diving into #digikam and #darktable... But I've entered a deeper rabbit hole —my really messy photo #metadata! Learnt a lot about #xmp #exif and #iptc, and using #exiftool (which is an amazing tool by Phil Harvey). #PhotoManagement #dam #photometadata
-
Been busy deep diving into #digikam and #darktable... But I've entered a deeper rabbit hole —my really messy photo #metadata! Learnt a lot about #xmp #exif and #iptc, and using #exiftool (which is an amazing tool by Phil Harvey). #PhotoManagement #dam #photometadata
-
Been busy deep diving into #digikam and #darktable... But I've entered a deeper rabbit hole —my really messy photo #metadata! Learnt a lot about #xmp #exif and #iptc, and using #exiftool (which is an amazing tool by Phil Harvey). #PhotoManagement #dam #photometadata
-
Been busy deep diving into #digikam and #darktable... But I've entered a deeper rabbit hole —my really messy photo #metadata! Learnt a lot about #xmp #exif and #iptc, and using #exiftool (which is an amazing tool by Phil Harvey). #PhotoManagement #dam #photometadata
-
reposting my bulk XMP updating tool for photogrammetry users, got auto-deleted and this toot will serve as a comment section for a blog entry about it
https://matthewscheffel.com/projects/bulk-xmp-updater/
this tool is useful if you have a CSV file with reliable GPS data that you want mapped to JPEG images via XMP metadata headers. I think this is common if you're using some kind of "shim" system to snapshot GPS data aligned with image collection times.
-
reposting my bulk XMP updating tool for photogrammetry users, got auto-deleted and this toot will serve as a comment section for a blog entry about it
https://matthewscheffel.com/projects/bulk-xmp-updater/
this tool is useful if you have a CSV file with reliable GPS data that you want mapped to JPEG images via XMP metadata headers. I think this is common if you're using some kind of "shim" system to snapshot GPS data aligned with image collection times.
-
reposting my bulk XMP updating tool for photogrammetry users, got auto-deleted and this toot will serve as a comment section for a blog entry about it
https://matthewscheffel.com/projects/bulk-xmp-updater/
this tool is useful if you have a CSV file with reliable GPS data that you want mapped to JPEG images via XMP metadata headers. I think this is common if you're using some kind of "shim" system to snapshot GPS data aligned with image collection times.
-
About 100 loc into adapting exvi2 into one of my howngrown tools and I remember why I avoided that in the past. The #exiv2 API makes me want to sanitize by brain each time I look at its documentation or implementation.
Handling image metadata sucks, be it #EXIF, #IPTC, #XMP or anything else. However, a library shouldn't *increase* the pain.
Anyone aware of a halfway useable alternative that can be adopted/integrated into other languages? So ideally written in C or C++. Rust *might* work too.
-
About 100 loc into adapting exvi2 into one of my howngrown tools and I remember why I avoided that in the past. The #exiv2 API makes me want to sanitize by brain each time I look at its documentation or implementation.
Handling image metadata sucks, be it #EXIF, #IPTC, #XMP or anything else. However, a library shouldn't *increase* the pain.
Anyone aware of a halfway useable alternative that can be adopted/integrated into other languages? So ideally written in C or C++. Rust *might* work too.
-
About 100 loc into adapting exvi2 into one of my howngrown tools and I remember why I avoided that in the past. The #exiv2 API makes me want to sanitize by brain each time I look at its documentation or implementation.
Handling image metadata sucks, be it #EXIF, #IPTC, #XMP or anything else. However, a library shouldn't *increase* the pain.
Anyone aware of a halfway useable alternative that can be adopted/integrated into other languages? So ideally written in C or C++. Rust *might* work too.
-
About 100 loc into adapting exvi2 into one of my howngrown tools and I remember why I avoided that in the past. The #exiv2 API makes me want to sanitize by brain each time I look at its documentation or implementation.
Handling image metadata sucks, be it #EXIF, #IPTC, #XMP or anything else. However, a library shouldn't *increase* the pain.
Anyone aware of a halfway useable alternative that can be adopted/integrated into other languages? So ideally written in C or C++. Rust *might* work too.
-
About 100 loc into adapting exvi2 into one of my howngrown tools and I remember why I avoided that in the past. The #exiv2 API makes me want to sanitize by brain each time I look at its documentation or implementation.
Handling image metadata sucks, be it #EXIF, #IPTC, #XMP or anything else. However, a library shouldn't *increase* the pain.
Anyone aware of a halfway useable alternative that can be adopted/integrated into other languages? So ideally written in C or C++. Rust *might* work too.
-
@Pyb okkkk ! cest pas faux, le #CCSD doit s'améliorer mais #Medihal propose quand même une URL stable, une description en #XMP et #IPTC un affichage et récupération des fichiers en #TIFF et si qq'un veut les afficher en #IIIF les exports sont simples, nous avons même un chercheur retraité qui documente ses images en ligne... bref, à la #MMSH on préfère cette solution plutôt que le bazar de #Nakala ou les sites locaux voués à la #disparition
-
@Pyb okkkk ! cest pas faux, le #CCSD doit s'améliorer mais #Medihal propose quand même une URL stable, une description en #XMP et #IPTC un affichage et récupération des fichiers en #TIFF et si qq'un veut les afficher en #IIIF les exports sont simples, nous avons même un chercheur retraité qui documente ses images en ligne... bref, à la #MMSH on préfère cette solution plutôt que le bazar de #Nakala ou les sites locaux voués à la #disparition
-
@Pyb okkkk ! cest pas faux, le #CCSD doit s'améliorer mais #Medihal propose quand même une URL stable, une description en #XMP et #IPTC un affichage et récupération des fichiers en #TIFF et si qq'un veut les afficher en #IIIF les exports sont simples, nous avons même un chercheur retraité qui documente ses images en ligne... bref, à la #MMSH on préfère cette solution plutôt que le bazar de #Nakala ou les sites locaux voués à la #disparition
-
@Pyb okkkk ! cest pas faux, le #CCSD doit s'améliorer mais #Medihal propose quand même une URL stable, une description en #XMP et #IPTC un affichage et récupération des fichiers en #TIFF et si qq'un veut les afficher en #IIIF les exports sont simples, nous avons même un chercheur retraité qui documente ses images en ligne... bref, à la #MMSH on préfère cette solution plutôt que le bazar de #Nakala ou les sites locaux voués à la #disparition
-
@Pyb okkkk ! cest pas faux, le #CCSD doit s'améliorer mais #Medihal propose quand même une URL stable, une description en #XMP et #IPTC un affichage et récupération des fichiers en #TIFF et si qq'un veut les afficher en #IIIF les exports sont simples, nous avons même un chercheur retraité qui documente ses images en ligne... bref, à la #MMSH on préfère cette solution plutôt que le bazar de #Nakala ou les sites locaux voués à la #disparition
-
Moved over from Lightroom Classic to Lightroom. Kinda forced, since Lightroom Classic doesn't run on my new laptop with its Snapdragon CPU (ARM).
First, I was slightly upset about me not knowing beforehand, now though, after playing around a little bit, I feel I can make the jump. Lightroom seems modern and lighter in processing. Also I like the idea of not being dependent on a proprietary catalog file.
#adobe #lightroom #lightroomclassic #xmp #sidecar #photoediting #photography #door #hamburg
-
Moved over from Lightroom Classic to Lightroom. Kinda forced, since Lightroom Classic doesn't run on my new laptop with its Snapdragon CPU (ARM).
First, I was slightly upset about me not knowing beforehand, now though, after playing around a little bit, I feel I can make the jump. Lightroom seems modern and lighter in processing. Also I like the idea of not being dependent on a proprietary catalog file.
#adobe #lightroom #lightroomclassic #xmp #sidecar #photoediting #photography #door #hamburg
