.mos files

I am helping a gentleman who is using the Mamiya 645 AFD with a digital back from Leaf-Photography. It creates RAW files ending in .mos. We haven't been able to get Photoshop CS3, running on a Mac-Book with OSX 10.5, to open these files without going through an elaborate Leaf
conversion.
Is it possible to equip CS3 to open these files directly?
Thanks for your help.
Mary Lou

It's been over a year since the last posting on this thread, so I assume the poster has resolved the problem. However, for others - like myself - who are searching to the answer for this problem...
ACR only supports the uncompressed files created by Leaf backs - not the files created with lossless compression. Set the back to create uncompressed files and you should be fine.
-Brent

Similar Messages

How to view .MOS files in Adobe Bridge and Photoshop CS5?

I recently shot with a large format camera and used Capture One to tether during my shoot. I went home to look through my pictures and noticed that the files are .MOS files and they don't open in Bridge or Photoshop. How can I fix this?

Apparently it depends also on whether .mos was shot with compressed or uncompressed format. If uncompressed DNG will work http://www.luminous-landscape.com/forum/index.php?topic=11843.0;wap2

HT201070 there is no camera raw support for Leaf Aptus-II 8? I need to be able to read MOS files

there is no camera raw support for Leaf Aptus-II 8? I need to be able to read MOS files

OS X Mountain Lion: Supported digital camera RAW formats seems to indicate that you are correct.
Are you are trying to provide Apple - Aperture - Feedback or Apple - iPhoto - Feedback?
If so, use you can send direct feedback via the above link(s). You will not likely get a direct response, but you can be certain that the responsible Apple people will see your input for consideration in future product development.
If you seek a solution rather than to offer feedback, or until Apple supports your needs within the Mac OS, check whether Mamiya's Leaf RAW converter 1.2.6 for Mac meets your needs.
Message was edited by: EZ Jim
Mac OSX 10.8.4

Significant reduction in file size from Camera Raw to DNG

Hi,
I am currently testing the conversion of Leaf camera raw files into DNGs for a photographer's archive. I am hoping to convert all of the mos files to DNGs because Leaf Capture and the Leaf Raw Converter are not being updated and because the photographer wants to have an Adobe centered workflow. In my testing I discovered that converting mos files to DNGs through ACR 8.4 and LightRoom 5.4 resulted in a reduction of file size by nearly 50%. A 44.5MB mos file became a 23.6MB DNG. From what I've read only about 15-20% of the camera raw file should be lost and all of the data lost should be propietary.
Here-in lies my quesiton, is there any way that I can track or determine exactly what sort of compression is being done to the mos file and what information is or is not travelling in the conversion to DNG?
These are the settings I have used for converting raw files to DNGs:
ACR:
JPEG Preview: Medium Size
Embed fast load data
Don't use lossy compression
Preserve pixel counts
Don't embed original
LIGHTROOM 5.4:
Only Convert Raw files
Delete originals after successful conversion
File Extension DNG
Compatibility Camera Raw 7.1 and later
Jpeg Preview Medium Size
Embed Fast Load Data
Thanks!

50%? - I thought we were talking about 15-20%?
In my first post I questioned why I was seeing a reduction in file size of 50% when according to forums and articles I've read I should only be seing a 15-20% reduction in file size. I then wondered what data I might be losing, which you addressed.
Same as what? - what were the results.
I was referring to testing I preformed on camera raw files produced during different years (all mos). I converted all files with the same ACR and LR settings and found that the DNGs always reflected a 50% reduction in file size. This test suggests that any conversion issues is not necessarily related to how the camera raw files might have been differently built across years.
Adobe's raw data compression is touted by DNG zealots, but I haven't scrutinized it enough to corroborate or refute.., but my experience is that reduction is relatively marginal. All of this assumes original is also compressed - if uncompressed in original source, savings would be large.
The files I am dealing with are definitely uncompressed which could account for the large reduction in file size. I didn't realize until I posted to this thread that converting to a DNG results in a compression of the original image data. I understand that this compression is supposed to be lossless like a lossless compression to a tiff and thus result in no decrease in image quality or harm to the original image. I am baffled by how it is possible that any compression of a file (especially by 50%) could not result in a loss of important data but I will accept that it is possible to have a truly lossless compression and that the size reduction I am seeing could be a result of all of the different processes a file undergoes that you have outlined.
I looked into the effects that backwards compatibility has on the conversion process which might interest you http://dpbestflow.org/DNG#backwards-compatibility
I also posted to luminous landscape's forums http://www.luminous-landscape.com/forum/index.php?topic=89101.new;topicseen#new
Although it wouldn't surprise me if the DNG conversion process tossed the xmp-like metadata, and kept the original stuff, but it would surprise me if it tossed the original stuff - but as I said before, I haven't scrutinized for completeness so I don't know.
I've done testing in which I converted .mos camera raw files with their sidecar xmps and without their sidecar xmps. My tests revealed that the DNG definitely carries over xmp metadata although it is not clear to me exactly how it is carried and if anything is lost.

Convert compressed MOS to DNG

Hi guys!
Does anybody know if there is a way to convert compressed *MOS files coming from Leaf Digital Back directly to DNG, avoiding Capture One?
Thanks!

Have you tried the Adobe DNG converter? I am not familiar with the Leaf back. But I would suspect that since there are a number of Leaf models that are supported by Camera Raw you should be able to use the DNG converter on those files as well. Here is a list of cameras that Camera Raw, Lightroom and the DNG converter support:
Camera Raw plug-in | Supported cameras

RAW + old photoshop generated .XMP file conversion to DNG

I have a set of camera raw files (.mos) and .xmp side car files that were generated in photoshop several years ago. I am thinking about converting all of the files and side cars to DNGs because Leaf Capture software is no longer being updated.
Before I do I want to confirm that Lightroom can read both the raw AND the corresponding side car files and convert them into single dngs. I also want to know if the .xmp information is extractable after the dng is created in the same way that the raw/original file is extractable.
I've been trying to test lightrooms ability to read .xmp files on my own. I added a .mos file in a folder with a corresponding .xmp file and a .mos file in a folder without a corresponding .xmp file. Lightroom reads similar adjustment information for both images but only generates a preview that more closely resembles a finished retouched .PSD of the added .mos file that does not have the .xmp file in the folder it was added from. I'm at a bit of a loss regarding how to proceed.

nonovsco wrote:
Upate on situation: I followed up with the individuals that created the files and found out that the side car files were in fact generated by leaf and not photoshop. i tried another test and it looks like the folder with a .mos +.xmp file is now reading differently than a .mos file by itself. both suggest that changes were made to the files with modulations in the "develop" section of lightroom.
You can view the XMP file data in Notepad or any other text editor, just select 'Open' and select 'All File Types' so you can see the XMP files. It should be possible to store both C1 and LR develop settings in the same XMP file, but there may be some naming conflcts. Review of an XMP file with both C1 and LR develop settings saved to it should show the two different develop data sets in Notepad. Conversion to DNG should save ALL XMP data, but you may lose some of the (edit) Leaf proprietary data that may be in the raw file's metadata. For now I'd hold onto the raws + XMPs, even if you do convert to DNG.
You can use EXIFtoolGUI to examine the metadata in the new DNG files and compare it to the original XMP file's data. My Canon DSLRs appear to have all of the manufacturer's 'Makers Notes' copied over from the raw file into the DNG metadata.
http://freeweb.siol.net/hrastni3/foto/exif/exiftoolgui.htm

How to open Aptus II 5 files using Photoshop or lightroom?

My version of Photoshop and Lightroom (most recently downloaded from Creative Cloud) does not open the Aptus II 5 files although the camera is listed as being supported. What am I doing incorrectly? It will not read the .mos files. Appreciate your assistance.

It is listed as supported, but with this qualifying note (at the bottom of the page):

Problem geting Jar?s files directories??

Hi, i have one Jar file with three packages, one called instalerImages which is the one with the main class.
In that package i?ve got two folders, one with my aplication?s icons (i got them using getResource()) and another with archives i want to be copied to a external hard disk when running the aplication. this folder is called ficherosAlOverride, i ?ve got a method that copy a File [] and i want to create a new File for the ficherosAlOverride folder to use the listFiles() method to get the File[],
I?ve tried
File ficherosAlOverride=new File( myMainClass.class.getResource("/instalerImages/ficherosAlOverride).getFile())But when runnig the jar file ficherosAlOverride is a null pointer, altough when i run the programm in the IDE (eclipse 3.0) it works fine.
Can anybody help me or reffer to a previous topic with the answer?
I can post the jar file or the source if you want

I�ve changed it, the code is now.
File readme=new File(Principal.class.getResource("/instalerImages/images/Readme.txt").getFile());
               System.out.println("File to get the oparent folder "+readme);
               //Creamos un fichero con el directorio de ese fichero
               File directorioAlOverride=(readme.getParentFile());
               //Creamos un filtro para archivos mos y los leemos
               System.out.println("Folder "+directorioAlOverride);
               Filtro mos=new Filtro("mos");
               File[] ficherosMos=directorioAlOverride.listFiles(mos);
               System.out.println("File[] length "+ficherosMos.length);This is what i get when runnig it in Eclipse
File to get the oparent folder G:\Programas\eclipse\workspace\Instaler\bin\instalerImages\images\Readme.txt
Folder G:\Programas\eclipse\workspace\Instaler\bin\instalerImages\images
File[] length 42
An this is when i run the jar file by console
C:\>java -jar g:\instaler.jar
File to get the oparent folder file:\G:\instaler.jar!\instalerImages\images\Read
me.txt
Folder file:\G:\instaler.jar!\instalerImages\images
null
java.lang.NullPointerException
at instalerImages.Principal.main(Principal.java:103)
It seems it finds the folder, but the FileName Filter dosen�t work properly in the jar file.
Here is the jar file:
https://www.alumnos.unican.es/cgi-bin/web-ftpc.cgi/177113952681/DNLD?instaler%2ejar
And here the source code:
https://www.alumnos.unican.es/cgi-bin/web-ftpc.cgi/177113952681/DNLD?Instaler%2ezip
There are any reason for that??

Cannot apply any color settings to RAWs from CompactFlash card

Usually we shoot tethered around here, but i had to shoot to card yesterday and was having no luck using Bridge and ACR to apply color settings to my files. I would open a .MOS file in ACR from Bridge and change its color balance and/or exposure, etc. and click DONE and nothing would happen in Bridge. It would make an XML file that sat alongside it in the folder, but Bridge would not recognize these changes. There preview and the thumb would stay the same, and i wouldn't get that little circle icon with the arrows in it next to the thumb in Bridge.
Changing preview types, thumbnail types, auto-exporting cache, purging cache from Tools menu, reapairing permissions, changing parent folder permissions, restarting my Mac, dump Bridge's preferences etc. nothing worked. i even tried the same images on a different Mac with CS3 and Bridge and got the same results. If i made a New Camera Raw Default, that WOULD work, but i could not make specific single-image changes.
BUT, somehow as i was pulling my hair out, i found a fix. Going to the Finder, i Got Info on the RAW file, went to the Open With popup, found Adobe Photoshop CS3 again (even though it was already highlighted), clicked ADD, and closed the Info window. Instantly that file's Thumbnail in Bridge got rebuilt and now my color changes would stick.
Every file that comes off these cards needs that done to it, but never when we shoot tethered to the computer. Weird. I'm not sure if it's specific to the Digital back or not.
This was using a Leaf Aptus 75S mounted to a Mamiya RZ67 shooting to SanDisk 4GB Compact Flash cards. I'm running a G5 tower using OSX 10.4.11, Bridge 2.1.1.9, and ACR 4.4.1.
Any ideas?

answered in another forum

Aptus II 8 Adobe Standard color profile missing from LR3.5?

I was wondering, several versions ago, (2.7 I believe) the Leaf Aptus II 8 aka Leaf Aptus 40 was added to the list of supported cameras. My version of Lightroom 3.5 (MacOs 10.6.8) can read these files, however there is no Adobe Standard color profile for this back. When I go to the calibration tab it just shows embedded. These files are uncompressed .mos files and not jpegs or tifs. With my Leaf Aptus 75 I use the Adobe Standard profile and like it. Is this a bug or just an unsupported feature of the Aptus 40?

Thanks, that sounded like a good idea and it got me thinking. Why not trash the profile and import it from another computer. Doing that I found that the file sepraratly downloaded on another computer has the same problem so I can't move it over. The other computer is OS 10.5 Leopard whereas mine is 10.6 Snow Leopard. This leads me to believe that this is an Adobe issue.
Would any other Mac LR3 users please go to Library>Application Support>Adobe>Camera Raw>Lens Profiles>1.0>Canon and see if there is an "exec icon" next to the file named...... Canon EOS 5D Mark II (Canon EF 16-35mm f2.8 L USM) - RAW.lcp
I'd appreciate it and it will help isolate the problem.
Thanks
Greg Eddinger

Plugin aptus 65

Hello, photographer with the Leaf Aptus 65 which generates a file in MOS, but photoshop does not open this file. I need to download any plug-in?

Which version of photoshop and operating system are you using?
You can at this list of supported cameras for photoshop camera raw and see what version of camera raw you need
Camera Raw plug-in | Supported cameras
Then look at this list to see if your version supports the required camera raw plugin
Camera Raw-compatible Adobe applications
If your version of photoshop doesn't support the camera, you can still use the free adobe Dng Converter to convert your Leaf files so photoshop will open them.
Though since that camera is kinda old, it may just be that the files are compressed and camera raw can't handle those files
(from the bottom of the first link)
*** Note: Camera Raw doesn't support compressed MOS files from Leaf or Mamiya cameras. If you can't open your MOS file in Camera Raw, try using a camera proprietary
converter to remove the compression from the files. (Proprietary converters include Leaf Raw Converter or Phase One Capture One.)

In MOS I cannot find an option to file an SR for Oracle linux OS.

In my oracle support I cannot find any OS options when trying to file an SR. Did they get rid of this option?

Upgrade your browser to Firefox 8 and check
* getfirefox.com

I have an imac osx 5 mos.old. First time today I can not open my desktop folder/files. I need to read them. Message is: appleworks 6 quit unexpectedly. I need to read them. Is it possible that new software downloaded yesterday is problem?

I have an imac osx 5 months old. For the first time today I can not open my desktop folders which are very important to me. How can I open these folders.
The message when I click on the folder is "appleworks 6 quit unexpectedly". I can not open the folder. Is it possible that new software installed could cause the problem when I get the message "new softward available for your computer, install now. Maybe I should never install upgrade. Please help in layman's language how to open my folders. Thanks.

X423424X wrote:
The curious thing here is that on the one hand the code cannot be loaded so how could the trojan code be ever executed. But you would expect the "Unexpectedly quit" message if the intel trojan did get executed in a ppc app. So this begs the question when (and how) does the trojan code get executed in conjunction with launching an app?
I understand code injected into a specific app like safari that uses the global environment variable to access the code in /Users/Shared. But I don't understand how that code could be executed by attempting to run an randomly chosen ppc app. Unless of course other code has been injected is in a more critical place than just safari and that is scary.
Some of this was explained to us a few weeks back by an infected user who reverse engineered the code, working with Intego to figure out why he was being re-directed on Google searches. At the time, nobody believed much of anything he was saying, but F-Secure explains it more fullly in this analysis. Note that there is a filter component to keep it from loading code into apps that would be unstable, so watch for the next variant to filter out ppc only apps.
In a related matter, I got word from the PC side of the house that similar techniques are being used by drive-by infections that were injecting code into a running app which would disappear when they quit the app. A one-time infection, so to speak. Makes it really hard to even know you were temporarily infected, let alone how, why, what damage, etc.

Db file in Replica was created in wrong folder

Hello!
I created db file at \BDB_HOME\BDB_SUBx in Master, but in Replica site db file was created in wrong folder which is BDB_HOME.
Do I miss something than setting path to DatabaseEnvironmentConfig.CreationDir ?
\BDB_HOME
|
-BDB_SUB1
-BDB_SUB2
-BDB_SUB3
FYI
Ver.5.1.19 (HA)
C#
VisualStudio.Net 2010
Thanks,
Osamu

Hi Osamu,
This is a known limitation with BDB HA at the moment. This issue is tracked internally in SR #19041. We hope to fix it, but do not guarantee that it will make it, in the next BDB release, 5.2.
Osamu, if you have access to MOS (MyOracle Support) please consult Note 1250654.1 (Doc ID 1250654.1) -- How to Correctly Replicate a Directory Structure Involving Subdirectories Between Master and Client. This article explains in detail this issue and how to work around it for now.
For reference, to explain the issue in more detail, suppose on the master the environment directory structure looks something like this:
\BDB_ENV_HOME
     \BDB_SUBDIR_1
     - DbFile_1_1.db
     - DbFile_1_2.db
     - DbFile_1_N.db
     \BDB_SUBDIR_2
     - DbFile_2_1.db
     - DbFile_2_2.db
     - DbFile_2_N.db
     \BDB_SUBDIR_M
     - DbFile_M_1.db
     - DbFile_M_2.db
     - DbFile_M_N.dbOn the client site, the environment directory structure will be incorrectly replicated and will look something similar to this (with all database files ending up under one of the subdirectories):
\BDB_ENV_HOME
     \BDB_SUBDIR_1
     \BDB_SUBDIR_2
     \BDB_SUBDIR_M
     - DbFile_1_1.db
     - DbFile_1_2.db
     - DbFile_1_N.db
     - DbFile_2_1.db
     - DbFile_2_2.db
     - DbFile_2_N.db
     - DbFile_M_1.db
     - DbFile_M_2.db
     - DbFile_M_N.dbThe workaround to resolve this issue depends on a manual hot backup. AUTOINIT should be turned off via rep_set_config with DB_REP_CONF_AUTOINIT and 0. Than the client should be bootstrapped with the databases and logs from the master and recovery should be run as described in the Berkeley DB Programmer's Reference Guide, in the Hot failover section.
Basically, copy all the databases, copy the logs, run catastrophic recovery on the new client environment directory, and start the application. By turning off AUTOINIT you might need to take care of handling the REP_JOIN_FAILURE event error.
To summarize, the workaround implies the following actions:
1. On the client environment call DbEnv::rep_set_config like this:
DbEnv::rep_set_config(DB_REP_CONF_AUTOINIT, 0);With the C# API it's something like:
DatabaseEnvironmentConfig envConfig = new DatabaseEnvironmentConfig();
envConfig.RepSystemCfg = new ReplicationConfig();
envConfig.RepSystemCfg.AutoInit = false;
DatabaseEnvironment env = DatabaseEnvironment.Open(envHomeDir, envConfig);or you could use the DatabaseEnvironment's class RepAutoInit property.
2. Handle DB_REP_JOIN_FAILURE on the client environment, which could be returned from DbEnv::rep_process_message. Handling implies setting an event callback function via set_event_notify for DB_EVENT_REP_JOIN_FAILURE like this:
DbEnv::set_event_notify(eventsHandler);where eventsHandler is a callback function that respects this signature:
void (*db_event_fcn)(DB_ENV *dbenv, u_int32_t event, void *event_info)and internally checks to see if event is DB_EVENT_REP_JOIN_FAILURE. If it is, it may trigger copying of the backup files from the master onto the client.
With the C# API you will set an EventNotifyDelegate delegate using the EventNotify property and check the NotificationEvent.
3. Start the client. Because AUTOINIT is turned off, internal init will not be performed, hence it will not remove the directory structure on the client environment.
4. If the event callback function gets notified of the DB_EVENT_REP_JOIN_FAILURE it means that the backup of the master (databases and log files of the master) is required on the client. Take a manual hot backup as per the guidelines in the Hot failover section, and copy the database and log files onto the client; this is something that the event callback function can do, when it handles DB_EVENT_REP_JOIN_FAILURE by using something like rsync to copy the files between the machines.
5. If a backup was copied onto the client, run a catastrophic recovery in the client environment either manually via db_recover -c, or programmatically by specifying the DB_RECOVER_FATAL flag to the client's DbEnv::open call (with the C# API you specify it via RunFatalRecovery)
6. After the catastrophic recovery will have been performed and the client will have started, all the replication synchronization will work as expected, replication messages will be processed correctly, and the directory structure will be maintained.
Regards,
Andrei

Photoshop CC 2014, MAC OSX, I have no option to close a modified file without saving it - i.e. no "don't save".

Hi there.
I have an odd issue where when I open a file and make changes to it, I can't close the file by clicking the 'x' button, can't select "file close", can't "command W" or even quit or force quit photoshop until I have saved the file. It's very frustrating as I have had to make a "PSD TRASH" folder on my desktop specifically for saving random working files, which I clear out at the end of the day.
Has anyone else had this issue? I have compared my preferences to colleagues without this issue and they are set the same. I have also re-installed Photoshop CC 2014 on my machine with no success.
Any advice would be appreciated!
Cheers

What happens when you select File > Close exactly?
Please read these and proceed accordingly (restoring Preferences after making sure all customized presets like Actions, Patterns, Brushes etc. have been saved might be of special interest):
http://blogs.adobe.com/crawlspace/2012/07/photoshop-basic-troubleshooting-steps-to-fix-mos t-issues.html
http://forums.adobe.com/docs/DOC-2325

.mos files

Similar Messages

Maybe you are looking for