Skip to main content

Filter by idea status

10000+ Ideas

Carlos_Oliveras
Carlos_OliverasKnown Participant

P: Normalize focal lengths to 35mm equivalent field of view (instead of "literal" EXIF values)Open for Voting

[I have rewrited this since the original post, since my original text was not as clear as it should be]   I think we all photographers refer to focal lengths in 35mm equivalent value (angle of view). But since there are a myriad of sensor sizes (and so, a myriad of crop factors), most of the time the Focal Length metadata (the "real" value) is not very useful, unless you only shoot full frame.   There is another metadata field called "Focal Length 35mm", but unfortunately, this field is only populated for some cameras (it never shows for any of my Canon cameras, for instance).   I understand this is not Lightroom Classic's fault, but some camera makers' (who, for some reason, are not filling in this field). But still, I reckon that some kind of fix is needed, since I think most of us think in terms of 35mm angle of view equivalent, and just seeing the "real" focal length is hardly informative. For instance, how many of us would like to base their lens-buying decisions on their most used focal lengths? Me, for instance, but I can't because of this.   But here comes another problem: even when this "Focal Length 35mm" field is populated, it is not available everywhere - unless I am missing something, I can't display this 35mm equivalent:   • As part of the info in Loupe Overlay• As part of the info in Grid Extras overlay• As a Metadata column filter (there's a plugin by Jeffrey Friedl that fixes this specific issue)• Under the histogram (only "real" focal length is shown)• In the Map module, in the small thumbnail pop up that appears when clicking the photo's orange pin in the map (only "real" focal length is shown)   I guess there could be at least 2 approaches to fix this:   - Force-populate the "Focal Length 35mm" when it is empty, and make small modifications where necessary to allow us to display it everywhere where we can also see "real" focal length - Keep things as they are but provide a preference so that "Focal length" is always converted and displayed as its 35mm equivalent   There could be other options of course, but whatever the solution, I think something should be done, since the current situation doesn't make much sense - the "real" focal length, which like I said only makes sense for full frame cameras, is being featured everywhere, while the 35mm equivalent angle of view, which is what most of us (if not all of us) use and care for, takes a back seat or isn't there at all.   Maybe this wasn't such an issue when Lightroom Classic first came out, but nowadays, like I said, we have a ton of sensor sizes (both cameras and smartphones), and "real" focal lengths by themselves have come to mean very little.   Thank you so much for considering this idea!

moch230Participant

Wiggle Transform/path "False re-indexing" fix requestOpen for Voting

Hi,I love to use the repeater and wiggle transform features on my shape layers as a way to simulate how C4d cloners work. With this I often stack multiple wiggle transforms with the wiggles per second set to 0. I do this to mimic the random effector. Then I like to add some fun variation to my strokes by adding a wiggle path with wiggles per second set to 0. I play with the index until I get the desired look I like.   The issues I am running into with this:1. Often when I add a new layer in my timeline, these functions appear to re-index themselves. The index number doesn't actually change, but a new variation is created (Lets call this "False Re-indexing). The look finessing I worked on goes to waste. 2. For objects that I want to animate and have the wiggles per second set to something other than 0... They often do a similar index shifting as I work on my project. Resulting in my shape layers making big jumps at random positions during preview. My hunch is that it renders the preview to a point, then as I work I add more layers making it do the false re-indexing, then it renders the rest of my work area. The caching doesn't account for this "False re-indexing" and doesn't rerender the earlier frames, resulting in a jumpy render. To combate this I have to purge all memory and cache several times an hour, which is quite annoying to have to do.  So ultimimately the main fix I am proposing is a fix for this "false re-indexing." And if there are reasons for the wiggle transform/wiggle path functions to act this way then can we have a setting to be able to turn the "false re-indexing" off? It would be nice to be able to finesse the settings in these functions and not have to worry about them changing.  Thanks, Miles Och

midjournalist_7435Participating Frequently

FEATURE REQUEST: add ducking for ANY tag or a trackOpen for Voting

The way ducking works in Premiere Pro is somewhat limited. You can apply it to a media which has been tagged. I can understand why - because this tool needs to know, what to duck against. But the media used for ducking has to be tagged as music or ambience only. So what if there was an option to select a track or several tracks to route the ducking "ears" to them or just use ducking with any tags?Why one might need this? Suppose I have a voiceover and I want to duck it against another one if they were recorded in a small room with microphones close enough to record an opponent's speech as an echo.To do this I have to duplicate the track, leave only the left channel in one and only the right channel in the other and use them both to duck against one another. But this way I have to tag them as music or ambience which deprives me of using the helpful tools found in the Essential Sound if the Dialogue tag is set. And you cannot tag a media twice. So what I suggest is either add a ducking feature to all the tags or just add a separate ducking instrument to be able to use it with any media. As far as I know ducking is made via the Amplitude filter but the ducking feature is only available in the Essential Sound tab when the media is tagged as Music\Ambience. So another way to implement this feature would be adding a ducking preset to the Amolitude filter with additional options where you can set it up to duck against other media or tracks.