ANN: LR2/Mogrify 2.00 Released - add compress to file size feature

Hi all,
I’ve just released version 2.00 of my LR2/Mogrify for Lightroom, which should make quite a few of you happier…
The head-line news is that there’s now a compression feature that’ll automatically find the optimum JPEG compression value to produce the best quality image that’s no larger than the requested image size (including metadata). This is very useful for uploading to web sites that limit the maximum file size.
But that’s not all….
Watermarks can now be scaled to the shortest or longest edge, which means they’ll be the same size on landscape and portrait images.
Annotations also receive this feature, and I’ve finally found a solution to the problems with annotations containing accented characters and such like. You should now be able to add any text that you care to!
Regards,
Tim

Thanks Tim - super. Just for info purposes - I used the 'Check for Update' feature from within the plug-in this morning (prior to reading the update news) which stated no update available. So I downloaded and installed it directly from your site and alls well. I wonder could there be a small bug in the check for updates feature??

Similar Messages

Help with compress function--file sizes not substantially reduced

I've tried to use the compress function (right click "compress" or Finder/File/Compress) a few times on files from a variety of different programs. While this results in creating a zip file, the file size is not substantially reduced (e.g., from 43.4 MB to 42.9 MB). Is there a way to change how much a file is compressed?
Thanks in advance for your help.
Eric

Not all material is very compressible. Text files and word processor documents usually compress very well. Photos and movies don't compress much if at all due to the nature of their structure (in some cases, using a general-purpose compressor can actually make a file larger). So it will depend on what it is you're compressing.

How to compress pdf file size from 16mb to 4mb

Can you please tell me how to compress a PDF email size of 16mb to 4mb?

http://pdf-compressor.en.softonic.com/
However PDF compression in general depending on format (pdf-A, pdf-X, etc etc) may not work or work well.

Compressed Video File Size Too Large for DVD?

I exported a one hour and 51 minute FCP Studio sequence to Compressor. I chose the 120 minute 4:3 best quality and Dolby for the audio. It took six hours and thirty five minutes to compress. When I bring the compressed "assets" into DVD Studio Pro, it indicates 5.9 gig. That won't fit on a standard DVD-R disk. Should I have used a different compression scheme when I made my choice in Compressor? Can I fit the movie on a standard DVD, or do I have to go back to FCP to shorten the sequence? What size must it be in FCP to fit on a standard DVD after Compressor and DVD Studio Pro?
Thanks

iDVD encodes (compresses) the video before burning
the DVD, so there's no problem. Your iMovie project
will fit.
The iDVD capacity is best expressed in time instead
of size. iMovie 4/5 can include up to 2 hours of
video. A little less, counting iDVD features.
Karl
Hi Karl
I have an iMovie file that is 3hr and 10min long. I have a dual layer burner and dual layer DVD's to burn onto. Will this file fit onto the 8.5GB disc? or do I have to compress it somehow? If there is some software that will do this could you let me know?
The dual layer DVD's say they will fit 215 min of video on them, so why does it reject my file when starting iDVD?
Thanks for your help

Compressing the file size?

I'm new with working with this program. My project is complete. However, my file size is too big to place on the website. any suggestions??

Go to the file menu and choose "Export w/ Quicktime Conversion". This will give you many options for a smaller (albeit lower quality) file size.

How do I compress Wav files

Hi, I have some sound files that I want to be able to email to people, but I can't because the files are too big. Is there a way to compress these files(wav)?

You may refer to the following there method to compress WAV files
Method 1: Compress WAV to other audio format
Compress WAV to lossless compression audio format without losing audio quality like compress WAV to FLAC, compress WAV to Apple Lossless ALAC M4A
Compress WAV to lossy audio format like compress WAV to MP3, compress WAV to WMA, AAC, RA and etc.
Method 2: Lower WAV bit rate
With this method, we can easily reduce WAV file size without changing WAV audio format.
The lower the bit rate, the smaller the WAV file size, the lower quality of the WAV audio.
In most cases, WAV audio quality shows little difference between 128kbps and higher bitrates. WAV quality will become crappier if the bit rate is less than 128kbps.
Method 3: Compress WAV to other audio format as well as lower bit rate
The third way to compress a WAV file size is that we simultaneously apply Method 1 as well as Method 2.
Resources: How to Compress WAV File Size without Losing Quality on Windows or Mac?

ANN: More Mogrify Magick - Graphical watermarks. + Opinions on sharpening requested.

Hi,
I've just released version 1.3 of LR/Mogrify.
This version adds a feature that's been requested here before: graphical watermarking!
Via the user interface you can select the watermark, choose to resize it, define it's position on the image and the overlay mode used.
You can download it here: http://timothyarmes.com/lrmogrify.php
Sharpening after resize has also been requested, however I'd appreciate some feedback here before I add it. Mogrify has two commands to control sharpening, the -sharpen option has the advantage of being simple to use (http://www.imagemagick.org/Usage/convolve/#sharpen) whereas the -unsharp command has 4 parameters.
Since this isn't an interactive operation I feel that the -sharpen option is the best choice. Batch processing images with -unsharp doesn't make any sense to me. However, it's now open for discussion...
Tim

You are absolutely right. It seems this is a bug in the version of ImageMagick that gets installed by macports (6.3.6). That version will not recognize a profile in the image even if it is there and simply tag the image with the new profile if you only supply the destination profile. It works correctly if you specify both source and destination. If, however, you install from the latest source from the Imagemagick website, which is 6.3.7-10, you'll get a version if ImageMagick that works correctly where you'll only have to specify the destination. I just tested this on my home machine and my /opt/local/bin/mogrify works incorrectly (you have to specify both) and my /usr/local/bin/mogrify (the one I compiled myself) only needs the destination profile.
Hope this helps

ANN: WS Utilities (new plugin) released

Hi,
We've just released a new plugin called West Street Utilities which currently adds a host of new features for graphics management. These features include the ability to compare graphics in a file system against your FM source files, to see what is used and where. For more information, see:
http://www.weststreetconsulting.com/WSC_Utils.htm
Unlike our other plugins, this one is not structure-oriented and can be used on any FM 7, 8, or 9 file.
Thanks,
Russ Ward
Owner, WSC

[email protected] schrieb:
> You can download it here:
Hi.
Doesn't work for me on Windows. Calls to LrTasks.execute() in
LRMogrifyExportTask.lua fail. I spent quite some time on it. Quotation
of file paths really introduces trouble. Seems there is some problem
with quotation mark matching. If you use only one pair of them,
everything is fine. When there are multiple pairs, things get quite
strange...
For example, these command strings are supposed to work:
c:/somepath/someexecutable c:/anotherpath/file
"c:/some path/someexecutable" c:/anotherpath/file
c:/somepath/someexecutable "c:/another path/file"
If I quote both paths, blanks in the first path don't get escaped. Even
worse, I don't know of any other way to escape blanks here than use
quotation marks. Something like "\ " -- no chance(?). I even had a look
at the lua.org source code. Their os.execute() is mapped to ISO/ANSI C's
system() call. No idea what LrTasks.execute() does.
My suggested work-around would be like this, as LR at least allows use
of native file system calls:
-- LRMogrifyExportTask.lua --
-- Run Mogrify
local command = '"' .. opts.path .. '" ' .. commandLine
-- added
local realCommand = command
if WIN_ENV == true then
-- default folder on Windows is user dir -> good
local batchFileName = "lr_mogrify_runner.bat"
io.output(batchFileName)
io.write(command .. '\n')
io.close()
realCommand = '"' .. batchFileName .. '"'
end
-- /added
-- changed
if LrTasks.execute(realCommand) ~= 0 then
-- /changed
Herb

Attack and Release in Compression

Okay, rather than a problem, another of my academic "how does it work" discussions.
On another forum, I've been debating the meaning of "attack" and "release" in compression. My contention is that the attack time is how long it takes to achieve the preset level of gain reduction once the signal crosses the threshod level...and release is the opposite: the time it takes to return to no gain reduction, again once the levels cross the threshold in downward direction.
Another poster, who usually knows what he is talking about, contents that the attack and release times are triggered, not by levels hitting the threshold, but rather simply by the compressor sensing an upward or downward level change.
As proof he posted a test from Soundforge: A tone that transitioned between -12 and -3dB at 300ms intervals. He then applied compression with the threshold set to -16 (so everything should be compressed) and, indeed, the waveform shows the effect of attack and release at each transition even though the whole test should be compressed.
I tried the same in Audition and, although the artefacts aren't as noticeable as in Sound forge, you can see the pumping on the waveform.
I can't see that the attack and release can be clever enough to react to every change in level (especially on a real signal, not his test) so have to assume the cause is a bit more basic.
Here's a picture of the original file I made:
And here's the same file compressed with an attack of 2ms and a release of 5ms and a threshold of -15dB, i.e. lower than anything in the clip.
As you can see, you can see where the attack and release happens (I won't post a pic but, with attack and release set to zero, you can't see any transitions) so if anyone can explain this you'll cure my curiosity!

But I'd still like to know how software compression works anyway.
I do not claim credit for writing this description. It comes from another recording site I frequent but puts things in pretty plain words that we made a "sticky."
[quoted post]
Shotgun's Compressor Tools 1 of 2
What you have to do is understand what compressors do, and what each of the controls do IN GENERAL. Then you apply that knowlege to what you want out of using the compressor and what your ears hear AT THE TIME OF USE so that you can adjust as necessary. So, read below for an overview of the box as a whole and each knob you're likely to find on it.
Compression
From the name, one can surmise that a compressor is going to squish, squash, mash or pulverize something. Given that we plug audio signals into it, we can further surmise that what is getting squished, squashed, mashed or pulverized is, indeed, our audio signal. And one would be completely correct in assuming that. But what does that really mean?
Well, consider an audio signal. Let's say it's a recording of my mom yelling at me about leaving my laundry piled haphazardly in the hallway. First, mom starts out trying to reason with me, gently, "Shotgun, you know, it's just not condusive to laundry efficiency leaving that stuff piled haphazardly like that..." her voice is calm, even and even somewhat soft. As I stare at her blankly, not understanding the finer points of sorting one's laundry and transporting it to the appropriate room in the house her voice becomes stronger and louder. "SHOTGUN! I'M GOING TO BEAT THE LIVING **** OUT OF YOU WITH A TIRE IRON IF YOU DON'T PICK THIS **** UP IMMEDIATELY AND PUT IT WHERE IT BELONGS SO HELP ME GOD!" Now she's yelling, screaming, in fact. Her face is red and frankly, I've just soiled myself which makes the entire laundry issue even more complicated.
Now, let's assume we're going to lay this recording of mom over some Nine Inch Nails-style door slamming, pipe clanging, fuzz guitar backing tracks. It's going to be an artistic tour-de-force. However, when mom starts out, her voice was hitting only about 65-70dB--normal conversational speech. By the time she's done it's more like 105dB worth of banshee howling. Unfortunately, our backing tracks are a pretty even volume the whole way through. So, at the beginning of the track mom will be virtually inaduible whereas at the end she'll be drowning out my samples of whacking a stapler on a desk. How do we deal with that?
WE USE A COMPRESSOR!
You see, what a compressor compresses is volume. That is, technically, it compresses the amplitude of the signal, or its "gain". So for every decibel that goes into the compressor, only a fraction of it will come out. That means that (depending on our settings, see below) if mom's voice uncompressed winds up at 105dB then we can set our compressor so that it only gets as high as 52dB if we want. How does that help you ask? Won't it still be too low to hear over the backing music? Yes it will, but read on and we'll cover that in the controls discussion.
Threshold
The threshold control on a compressor sets a level below which the compressor will do no work. The control is graduated in dB (in this case dBV of signal level) and allows you to set an "on/off" point so that you can compress the LOUD parts of a signal, and leave the soft parts alone. At times you may want to set this control low enough so that you're affecting the entire signal, at times you may not. In the case of mom's rant-on-tape, what we may want to do is set the compressor so that it doesn't touch the signal until her voice reaches something like 85dB or so***, say, about halfway up the scale from softest to loudest. So, we set the threshold so that we only see activity on our "gain reduction" meter when the track gets to a certain point.
To USE the threshold control effectively, you generally need to use your ears. Have some idea, before you start, of what you hope to accomplish by using the compressor and set the threshold to Capture the part of a signal you wish to do whatever that is to. In our example I want to lower the louder parts of my mom's tirade so I set the threshold to activate the compression at some arbitrary point in the track. I could have done it several other ways and the only way to learn which is best is to experiment and listen.
Ratio
This is the control that tells us how much signal comes out of the box relative to what's coming in. It is graduated in terms of a ratio (hence the name) of output to input. So, let's say we set the control to point at "2:1". That means that for every 2dB of incoming signal, we're only going to get 1dB of outgoing signal. Which means that at its very loudest, mom's voice isn't going to be nearly as loud as it was originally. Keep in mind that this ratio only applies to signals that meet or exceed the threshold setting. Any signal that is below the threshold just passes through as though the compressor weren't there (kinda).
To use the ratio control effectively you, again, need some idea of what you want out of your compressor overall. In our case I just need mom's voice to be more easily mixed in with the backing tracks so I just want it to be kind of even. However, I still want it to start softer and get louder, just maybe not AS soft at the beginning and not AS loud at the end. That is, still changing, just not as much.
Attack
The attack control tells us that, once a signal meets or exceeds the threshold, how quickly does the compressor put the smack down on said signal? The control is usually graduated in intervals of time, usually marked in milliseconds. So, let's say that I set my attack control to say 5ms. That means that when the signal passing through reaches the threshold I've set, the compressor waits an additional 5ms before it begins to reduce the amplitude (again, gain). This seems counter-intuitive doesn't it? I mean, we want the level controlled WHEN it reachest threshold, right? Not 5ms later. Well, there are reasons for slightly delaying the attack (and for that matter release) times.
To use the attack time effectively (and by now you should have seen this coming) you need to know what you want out of your compressor in general. Do you want the signal clamped down on fairly quickly? Or not? How do you know? This brings in one of the most important concepts of recording: attack and decay. Each sound has an attack and a release. Imagine hitting a drum (the easiest place to see this concept). You hear the sharp, immediately loud sound as the stick hits the head, but you also hear the sound gently fade away, also. That initial WHACK, that initial spike in amplitude is the sound's attack. Everything else is it's decay. Note that I use these terms in a "Shotgun" type of way and there are more correct ways to say this, I think, but I tend to, over time, develop my own language, so you're at a disadvantage.
So then, we can hear an attack in mom's voice, too. It's more subtle than the attack of a drum hit with a stick, or a guitar player's pick against a string, but it's there. And if we set our compressor's attack time too short, we will lose all the definition of the attack of the sound. Sometimes that's desirable, but in our case it is not. A very large percentage of how people perceive sounds comes from the attack. You must strive to preserve that unless it is your desire to purposely not. Therefore, be very careful with the attacks under your care. In the case of a vocal track, the attack of the voice will lend very much to the intelligibility of the track, so we do NOT want to destroy it. So, we may want a slightly longer attack time than 5ms here. But we can only tell BY LISTENING. LISTEN to the track, sweep the attack control back and forth and listen to what happens to the attack of the sounds. If it sucks, move the control. Don't look at where it's pointing until you're satisfied with how it sounds. Then only look for the sake of curiosity because that setting may never work the same way again. if you're using a plug-in make sure you allow ample time for the movement to take effect. Moving a plug-in's controls can sometimes not take effect for a full second or two after you move it so if you're sweeping it back and forth rapidly you'll fool yourself. In the case of plugins, make a move and pause until it changes. If it doesn't change within 2-3 seconds, maybe you didn't move it far enough.
Release
As you might guess the release control handles the other end of the signal from the attack. That is, when a signal drops back below the threshold, how long does the compressor wait to actually stop compressing. All the same counter-intuitiveness applies here as well. However, remember that the decay or "tail" of a signal isn't as important to the listener as the attack so you can get away with a little more here. Again this control is going to be graduated in units of time, usually ms. However, the numbers will be larger than the attack times. Sometimes up into the 100's of ms or even full seconds.
To set a proper release time, again, understand what you want out of your compressor. Do you want a major thrashing to your sound, or do you just want kind of a gentle corrective measure? What you have to look out for in the case of release times is pumping. If your release time is set too short then the sound will drop below the threshold, the compressor will release it, but the sound will then jump UP in level because the compression is no longer making it softer, but it's below threshold. That probably sounds confusing, but it happens. And it will sound pretty odd. The first time you hear it you'll understand why it's called "pumping". It sounds almost like there's a new "attack" near the end of the signal's decay. As I've said before, sometimes this is actually desirable. Usually it's not though. Your goal is to set a release time long enough to give the sound time to naturally decay to a point that when the compressor lets go it won't "pump" yet short enough so that the compressor isn't still active when the next "attack" comes along. If you set your release time too long it will start ****ing around with the attacks because it's taking so long to let go the next loud signal is there before the last one is finished compressing. So, if you get your attack set where you think it's right, but then you start losing your attack again, consider dropping that release time lower (faster).
Make up gain
Here's where we answer your initial question of "Won't it still be too low to hear over the backing music?" Remember that we noted that mom's voice started out so low that it was lost in the music. And all we've done so far is to use our compressor to take the bite out of the louder part of the track so that it's not overpowering. So, doesn't this leave the softer part still lost? And, possibly, doesn't it make the WHOLE TRACK too soft now? Yes, it absolutely does. But that's what we have makeup gain for.
The makeup gain is going to look very similar to any other gain control you have seen. It will be marked off in dB, possibly starting at 0dB and moving up to some obscene amount like 20 or 40 or 60 or 100,000 or something. (It won't really be 100,000). The makeup gain does just what it says it does, too. It allows you to "make up" the gain that you're losing by compressing in the first place. Now, that doesn't mean it UNDOES what you just did, not by any means. It means that you can now take your newly compressed signal and make the WHOLE THING louder. This is how we're going to get the parts that are too soft up where they belong.
To set this control we're going to, of course, listen. What we've done thus far is to compress down the loudest parts of the signal so that they're not so loud. You can say that the loud parts are now "closer" to the soft parts so to speak. So what you do with your makeup gain is to take the whole lot and move it back UP some smaller amount so that now the loudest parts are just still loud, but not AS loud and the softer parts are still soft, but loud enough to be heard. Think of yourself playing basketball. If you're short like me, there's no way you can slam dunk a basketball. However, let's say you can lower your basketball goal by one foot. Now it's lower, but you still can't slam dunk it, but lowering it any more would ruin the rest of the game because you'd just be dropping the thing in and not shooting. So what you do is you make yourself magically grow a foot as well. Now the goal is still a reasonable height, but you can slam dunk because you've grown a bit yourself. Same sorta thing. Your signal isn't so low it sucks now, but it isn't so high you can't get anything useful out of it as well.
Here's a shocker: in terms of makeup gain there IS a general rule you can keep in mind. As you're setting your compressor's other settings you will notice the meter marked "gain reduction" giving you some idea of what you're doing to the signal. It could be a schitzophrenic little peak meter or it could be a big, slow, thoughtful VU meter. Either way it'll tell you "hey, you're getting about 5dB of gain reduction here pal!" So, this tells you you can START your makeup gain at a setting of +5dB. That should give you a compressed signal at the same general level as the uncompressed signal. Kinda. Sorta. It's a really ROUGH starting point, but it's a starting point nonetheless. Again, though, twist it and listen to get it where it really needs to be. You may want more, you may want less.
The ******** you'll hear
Now, as you get replies to this thread there will be plenty of numbskulls along to give the following answers:
(1) Shotgun you're such a ****ing *******. The guy just wanted some basic info, some basic starting points for his compressor why do you have to be such a *****?
(2) Shotgun, you don't understand compression and you've never done any recording, HAVE you?
(3) Here are my basic settings and they'll probably work
None of that is even remotely true. Sure, there are plenty of basic starting points anybody here could give you. In fact, many of these folks have only been using compressors for about 6 months, but even THEY will have ONE setting group that they like for some reason and are DYING to tell you it in order to appear knowlegeable. Do not listen to any of this ****. Develop your own views on good starter compression settings by appying what you learn and what you hear and what you observe in your own experience. There are so many different kinds of compressors that anybody who gives you a rough setting diatribe is just pissing in the wind. In fact, many types of compressors don't even HAVE some of the controls I mentioned. Some have more. Also, there are plenty of points we haven't covered. For example limiting, which is a special kind of compression that uses a very high ratio (often infinity:1).
[/quote]
This isn't the complete post but it is the pertinent section.
Jack

Problem with compressing unicode file names in zip file

Hi Everyone,
I have a problem while compressing the unicode file name in a zip file. I used the below code for compressing the unicode files.
String[] source = null;
// C:\\TestData\\unicode_filename.txt : unicode_filename.txt is the file created in japanesse language
source = new String[] {"C:\\TestData\\temp_properties.xml","C:\\TestData\\unicode_filename.txt" };
byte[] buf = new byte[1024];
// Create the ZIP file
String target = "C:\\TestData\\target.zip";
ZipOutputStream out = new ZipOutputStream(new FileOutputStream(target));
// Compress the files
for (int i = 0; i < source.length; i++)
     FileInputStream in = new FileInputStream(source);
     // Add ZIP entry to output stream.
     String fileName;
     File tempFile;
     ZipEntry zipEntry = new ZipEntry(source[i]);
     fileName = zipEntry.getName();
zipEntry = new ZipEntry(fileName);
zipEntry.setMethod(ZipEntry.DEFLATED);
getUTF8Bytes(source[i]);
// here I'm unable to find the unicode files and not able to understand.
out.putNextEntry(zipEntry);
// Transfer bytes from the file to the ZIP file
int len;
while ((len = in.read(buf)) > 0) {
out.write(buf, 0, len);
// Complete the entry
out.closeEntry();
in.close();
// Complete the ZIP file
out.close();Please help me how to fix this issue.
Thanks

Hi,
Thanks for your time for looking into my query.
Please check the below code for debugging the issue and throw your comments/suggestions for fixing the issue.
import java.io.File;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.FileOutputStream;
import java.io.IOException;
import java.util.zip.ZipEntry;
import java.util.zip.ZipOutputStream;
public class ZipTest
public static void main(String[] args) {
          String[] source = new String[] {"C:\\TestData\\APP_Properties.xml","C:\\TestData\\??.txt" };
          byte[] buf = new byte[1024];
          try {
               // Create the ZIP file
               String target = "C:\\TestData\\target.zip";
               ZipOutputStream out = new ZipOutputStream(new FileOutputStream(target));
               // Compress the files
               for (int i = 0; i < source.length; i++) {
                    FileInputStream in = new FileInputStream(source);
                    // Add ZIP entry to output stream.
                    String fileName;
                    File tempFile;
                    ZipEntry zipEntry = new ZipEntry(source[i]);
                    fileName = zipEntry.getName();
                    zipEntry = new ZipEntry(fileName);
                    zipEntry.setMethod(ZipEntry.DEFLATED);
                    getUTF8Bytes(source[i]);
                    out.putNextEntry(zipEntry);
                    // Transfer bytes from the file to the ZIP file
                    int len;
                    while ((len = in.read(buf)) > 0) {
                         out.write(buf, 0, len);
                    // Complete the entry
                    out.closeEntry();
                    in.close();
               // Complete the ZIP file
               out.close();
          } catch (IOException e) {
               e.printStackTrace();
     private static byte[] getUTF8Bytes(String s) {
          char[] c = s.toCharArray();
          FileOutputStream file;
          try {
               file = new FileOutputStream("C:\\TestData\\output.txt", true);
               int len = c.length;
               // Count the number of encoded bytes...
               int count = 0;
               for (int i = 0; i < len; i++) {
                    int ch = c[i];
                    if (ch <= 0x7f) {
                         count++;
                    } else if (ch <= 0x7ff) {
                         count += 2;
                    } else {
                         count += 3;
               // Now return the encoded bytes...
               byte[] b = new byte[count];
               int off = 0;
               for (int i = 0; i < len; i++) {
                    int ch = c[i];
                    if (ch <= 0x7f) {
                         b[off++] = (byte) ch;
                         file.write((byte) ch);
                    } else if (ch <= 0x7ff) {
                         b[off++] = (byte) ((ch >> 6) | 0xc0);
                         file.write((byte) ((ch >> 6) | 0xc0));
                         b[off++] = (byte) ((ch & 0x3f) | 0x80);
                         file.write((byte) ((ch & 0x3f) | 0x80));
                    } else {
                         b[off++] = (byte) ((ch >> 12) | 0xe0);
                         file.write((byte) ((ch >> 12) | 0xe0));
                         b[off++] = (byte) (((ch >> 6) & 0x3f) | 0x80);
                         file.write((byte) (((ch >> 6) & 0x3f) | 0x80));
                         b[off++] = (byte) ((ch & 0x3f) | 0x80);
                         file.write((byte) ((ch & 0x3f) | 0x80));
               file.write((byte) '\n');
               file.write((byte) '\r');
               file.flush();
               file.close();
               return b;
          } catch (FileNotFoundException e1) {
               e1.printStackTrace();
          } catch (IOException e1) {
               e1.printStackTrace();
          return null;
}Thanks
Aravind

Unable to add a Project File in RoboSource Control

Hi this is Savana Chandra Shekhar,
I am working on RoboHelp 9 with RoboSource Control 3.
Scanario 1: There are two users who want to work on the same project file from different location using RoboHelp and using version control 3. we have a server located in US and i myself located in India. Now, when i am trying to add or load the Project file in Robosource, i am unable to load or add the project file as the file size is around 160 MB.
Scanario 2: When i am using "add to version control" option after setting up the connection (By Proving : Connection Name, Server, Port No., Port Type), i am getting the as displayed below. Please refer the Image attached.
I will be greatful to you if you can please provide some firm solution regarding this issue.
Thanks
Savana Chandra Shekhar
Database: MARSHelpSource
to database,

I can. This is a bug you are seeing we will have fixed in a future release. You are working in a "Local" form (not an online form) and that "Add submit button" should not be shown at all, that is only for an online form. If you move your form online when signed in, then it would have a Submit button automatically in Web View and in Page View would be able to be turned on and off.
Thanks,
Josh

IPhoto compatibility with Nikon Compressed RAW files?

Hi,
Has anyone tried using iPhoto with the compressed RAW files generated by a Nikon D300s? Are they supported?
The 300s can create types of RAW files: 12- vs 14-bit and uncompressed vs lossless compressed. Which of these 4 types is/are supported by iPhoto?
Thanks,
Mike

Hi,
I looked into it a bit further, and apparently Apple does not support ANY TYPE of RAW file from the D300s! This is the camera that Nikon (who is not exactly a minor player in the digital camera market) describes as their "flagship" DSLR!
(Even more frustratingly, the D300s has the same sensor and image processor as the currently-supported D300, so the RAW file formats should be very similar and Apple shouldn't have to do too much work to add D300s support!)
On the other hand, Photoshop already supports it:
http://www.adobe.com/products/photoshop/cameraraw.html
EDIT: yes I know I should "submit feedback"... already done...
-Mike
Message was edited by: Mike G.

Compress video files for email from iPod

I manage an ipod Lab for an intensive English school. We want students to be able to email themselves larger audio and video files from directly from the iPod without having to go through iTunes/iPhoto. We often run into the problem with files being too large to email and are wondering if there is some sort of compression app that we can install on the iPod that will let us compress large files down for email. Something like ESFileExplorer for Android.
Thanks,
jHart

Video and audio files are almost impossible to compress with a separate general-purpose compressor application. Such compressors just don't work with the way video and audio files are structured and usually make a video or audio file larger, not smaller; they can't shrink the file size and just add unnecessary overhead. The only effective way to shrink a video or audio file is to re-encode the file with a lower bit rate, smaller frame size (for videos) or both. I don't know if there's any app on the iPod that can do such re-encoding, and even if there is, unless these videos and audio files are quite short, it's probable that they can't be shrunk enough to get through most email systems which usually have very low attachment sizes allowed, often on the order of 10 to 20 megabytes maximum.
A cloud-based storage solution such as Dropbox may be the only practical solution, though I'm not sure what video and audio apps would support saving to such as service. Someone else here may be able to offer suggestions.
Regards.

Is there a way to "compress" or reduce keynote file size?

I have transferred some PowerPoint presentations to Keynote and in general have had no difficulty. However, I can "compress" the pictures in PowerPoint which makes the file size much smaller.
Is there any way to reduce the file size of a Keynote presentation?
Thanks,
GS KLIVANS
MacBook Pro Mac OS X (10.4.10)
MacBook Pro Mac OS X (10.4.10)

hi I am trying to do a project of putting a keynote saved as a quicktime into garageband and adding audio and then compressing it via Share ...sent to itunes etc. It does get smaller.
But Are there any experts out there on putting a keynote with narration into garageband. I loose all of the timing control when I send it to quicktime. It seems like a LOT of steps.
Also, putting a narration into keynote is so long. Power Point just lets you record the narration on each slide. So I was putting it into garageband and trying to add the narration podcast style. Any suggestions.

Compress Text File Using PL/Sql

Hi All,
My Environment is -------> Oracle 11g Database Release 1 On Windows 2003 Server SP2
Requirement is ------------> Compress a text file using Oracle pl/sql
I am tryring to compress a text file using below pl/sql code,
DECLARE
src_file BFILE;
v_content BLOB;
v_blob_len INTEGER;
v_file UTL_FILE.file_type;
v_buffer RAW(32767);
v_amount BINARY_INTEGER := 32767;
v_pos INTEGER := 1;
v_blob BLOB;
BEGIN
src_file := BFILENAME('MY_FILES','expLive.log');
DBMS_LOB.fileopen(src_file, dbms_lob.file_readonly);
v_content := utl_compress.lz_compress(src_file);
v_blob_len := DBMS_LOB.getlength(v_content);
v_file := UTL_FILE.fopen('MY_FILES','test.log.zip','wb');
WHILE v_pos < v_blob_len
LOOP
DBMS_LOB.READ(v_content, v_amount, v_pos, v_buffer);
UTL_FILE.put_raw(v_file, v_buffer, TRUE);
v_pos := v_pos + v_amount;
END LOOP;
UTL_FILE.fclose(v_file);
EXCEPTION
WHEN OTHERS THEN
IF UTL_FILE.is_open(v_file) THEN
UTL_FILE.fclose(v_file);
END IF;
RAISE;
END;
i am able to get the zip file without any problem.But the Problem here is size of the zip file, Acutal Text File Size is 520 KB and zip file size is 241KB. is there any possible way to compress little bit further to 100KB?
Please Advice ....in case if you are have an example please share it.
Thanks for your helps
Shan

is there any possible way to compress little bit furtherYou can compress better (but slower) with
v_content := utl_compress.lz_compress(src_file, 9);
..

ANN: LR2/Mogrify 2.00 Released - add compress to file size feature

Similar Messages

Maybe you are looking for