bibble and iView interoperability

[clarsen]

I use bibble extensively and sometimes wind up adding IPTC info via Bibble's interface.  This puts the new info in the '.bib' sidecar file, leaving the original JPG or RAW untouched.  If i subsequently update the JPG/RAW I don't get whatever changes were made via bibble.  Also, bibble doesn't seem to regenerate the sidecar when the JPG/RAW ITPC has changed which means any images processed through bibble don't have the IPTC changes made via photo mechanic.

I also use iView to incorporate images into a catalog.  This has a sync mechanism, but doesn't understand bibble sidecars.

Both of these applications don't do so well interoperating with others, but it would be nice if photomechanic could:
  - sync IPTC changes (e.g. keyword additions/removals) from/to '.bib' sidecar file making the JPG/RAW the most up-to-date source of IPTC info.
  - export coloring that iView understands (if it is possible)
  - when moving JPG or RAW files, move the associated '.bib' sidecar file if present in same directory.

Does any of this sound reasonable for an upcoming version?

Thanks,
-case larsen

[Kirk Baker]

I use bibble extensively and sometimes wind up adding IPTC info via Bibble's interface.  This puts the new info in the '.bib' sidecar file, leaving the original JPG or RAW untouched.  If i subsequently update the JPG/RAW I don't get whatever changes were made via bibble.  Also, bibble doesn't seem to regenerate the sidecar when the JPG/RAW ITPC has changed which means any images processed through bibble don't have the IPTC changes made via photo mechanic.

I also use iView to incorporate images into a catalog.  This has a sync mechanism, but doesn't understand bibble sidecars.

Both of these applications don't do so well interoperating with others, but it would be nice if photomechanic could:
  - sync IPTC changes (e.g. keyword additions/removals) from/to '.bib' sidecar file making the JPG/RAW the most up-to-date source of IPTC info.
  - export coloring that iView understands (if it is possible)
  - when moving JPG or RAW files, move the associated '.bib' sidecar file if present in same directory.

Does any of this sound reasonable for an upcoming version?

Is the 'bib' sidecar file text or XML, or something else?

-Kirk

[clarsen]

sorry for the delay, i didn't get email notify of the reply.

it's text.  here's example.  The IPTC section in particular is my concern, and really only keywords and caption specifically, but you can approach as what would be useful to others too...

[autorotate]
autorotate=1
rotateangle=0
rotateanglerad=0

[canon]
ccont=0
cfalse=false
csat=0
csharp=0
cwhite=0

[cms]
applyoutputprofile=false
applyprofile=false
colormode=2
customoutputprofile=\0
customprofile=\0
debugprofile=0
profile=0
profiletone=false
workingspace=1

[color]
blue=0
colorson=false
cont=0
green=0
hsvon=false
hue=0
light=0
red=0
sat=0
vibe=0

[crop]
crop.bottom=0
crop.imageheight=0
crop.imagewidth=0
crop.left=0
crop.right=0
crop.top=0
cropon=true
dpi=300

[crop2]
crop2_centerx=0.56942
crop2_centery=0.497382
crop2_constrained=false
crop2_dpi=300
crop2_height=5.21145
crop2_width=10.433

[curves]
curves_m_cn=4,2,2,2,2
curves_m_cx=4,17,0,0,0,0,0,0,0,0,65535,65535,65535,65535,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
curves_m_cy=4,17,0,0,0,0,0,0,0,0,65535,65535,65535,65535,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
curves_m_ihi=4,65535,65535,65535,65535
curves_m_ilo=4,0,0,0,0
curves_m_imid=4,1.000000,1.000000,1.000000,1.000000
curves_m_ohi=4,65535,65535,65535,65535
curves_m_olo=4,0,0,0,0
curves_m_ver=0
curveschanged=0
curvesmode=0
curveson=false

[demosaic]
dmblur=false

[exposure]
autolevel=false
exposureval=0
fill=0
fillamount=0.5
fillenabled=false
fillmask=0
fillrange=50
highlightrecmono=false
highlightrecthresh=0
highlightrecval=0
highlightval=0.001
hron=true
shadowval=0.01
tonechange=0

[group]
_cprogress=100
usecanon=false

[iptc]
BYLINE=Case Larsen
BYLINETITLE=\0
CAPTION=After 7 days, these are all effectively dead.
CAPTIONWRIT=\0
CATAGORY=\0
CITY=Union City
COPYRIGHT=\0
COUNTRY=USA
COUNTRYCODE=\0
CREDIT=\0
DATE=20060513;20060513
HEADLINE=\0
IMAGENAME=\0
INSTRUCTIONS=\0
KEYWORDS=day7;experiment;herbicide
PRIORITY=0
REFERENCE=\0
SOURCE=\0
STATE=CA
SUPCAT=\0
TIME=064943-0800;064943

[kodak]
_kprogress=100
klight=0
klook=0
knoise=0
ksample=0
ksamplex=0
ksampley=0
ksharp=0
kwhite=0
usekodak=false

[nogroup]
d1color=2
iptcloaded=false
nfringe=false
tag=true
version=8.2

[noiseninja]
bnn_auto=true
bnn_ccontrast=10
bnn_coarse=true
bnn_csmooth=10
bnn_cstrength=10
bnn_enabled=true
bnn_lcontrast=10
bnn_lsmooth=10
bnn_lstrength=10
bnn_profilename=\0
bnn_turbo=true
bnn_usmamount=60
bnn_usmradius=1.2

[pc]
pcenabled=true
pctintmeta=3

[scale]
bjorn=false
outputdpi=300
outputheight=1563
outputorientation=0
outputscale=100
outputwidth=3130
scaleconstraint=0
scaleenable=false

[sharpen]
chromanoise=0
chromanoiseon=false
fringe=0
lumanoise=0
lumanoiseon=false
newsharpen=100
noise=0
noiseon=false
sharpen=3
sharpenon=false
sharpenrad=0
sharpensense=6

[sharpening]
ZoomZoom=100
zoomX=1200
zoomY=600

[tone]
disablegains=false
gamma3=false

[wb]
ckelvin=5353
ctint=15
kelvin=5353
lkelvin=5353
lmb=1
lmr=1
ltint=15
lwhitetype=8
tint=15
whiteauto=false
whiteblue=65384
whitegreen=65384
whitered=65384
whitetype=8

[Kirk Baker]

I use bibble extensively and sometimes wind up adding IPTC info via Bibble's interface.  This puts the new info in the '.bib' sidecar file, leaving the original JPG or RAW untouched.  If i subsequently update the JPG/RAW I don't get whatever changes were made via bibble.  Also, bibble doesn't seem to regenerate the sidecar when the JPG/RAW ITPC has changed which means any images processed through bibble don't have the IPTC changes made via photo mechanic.

I saw your sample .bib file, thanks.
OK, so Bibble doesn't read IPTC from JPEGs at all then?

I also use iView to incorporate images into a catalog.  This has a sync mechanism, but doesn't understand bibble sidecars.

Understandable.  The .bib file is human readable, but is basically a proprietary file format.

Both of these applications don't do so well interoperating with others, but it would be nice if photomechanic could:
  - sync IPTC changes (e.g. keyword additions/removals) from/to '.bib' sidecar file making the JPG/RAW the most up-to-date source of IPTC info.

I could see reading the .bib file for an updated caption if the modification date of the .bib file was newer than the corresponding image.  I wouldn't really want to update the .bib file however.  What does Bibble do with RAW+JPEG pairs?  Single .bib file for both the RAW and the JPEG?

  - export coloring that iView understands (if it is possible)

I could see supporting that if I could find out what mechanism iView uses to do its coloring.

  - when moving JPG or RAW files, move the associated '.bib' sidecar file if present in same directory.

We could definitely do this, but in a RAW+JPEG pair, which of the two files should own the .bib file, such that if you decide to move one of them, should the .bib file be moved or left behind?

-Kirk

[RobertE]

  - export coloring that iView understands (if it is possible)

I could see supporting that if I could find out what mechanism iView uses to do its coloring.

Hi Kirk,

iView writes its color labels to the IPTC Urgency field.

-- Robert.

[Kirk Baker]

  - export coloring that iView understands (if it is possible)

I could see supporting that if I could find out what mechanism iView uses to do its coloring.

Hi Kirk,

iView writes its color labels to the IPTC Urgency field.

-- Robert.

iView has no other mechanism?  What if you use the Bridge Labels (you get to choose the name for the labels), do they transfer over to iView?

While it would be easy enough to optionally tie our color classes to the IPTC Urgency field, it would be great if there were a way to use some XMP field instead.

-Kirk