[Mark Whitney]

[Noel Powell] “but I can’t say I would recommend the upgrade to a light user. I certainly don’t find the new versions to be more reliable, I kind of hate the new Preview architecture, and for the life of me, I can’t understand why they would remove the multithreading capabilities.”

Must have been some issues I’m guessing. I ended up turning it off in CS6 in fact. Had some problems (don’t recall exactly now) and a couple others on the Newtek forum mentioned having the same problem. Oh, I remember. Even with a clean close of project & program, would get multiple messages pop up to close the program. Very annoying.

[Mark Whitney]

Thanks Jim.

Old doesn’t have to equate to obsolete.

[Mark Whitney]

Hey Noel,

I really don’t know but I keep encountering more each week actually. Would be an interesting study. Had a message exchange just this week with someone on another forum that is still using CS2 of Photoshop. Even for me that’s a bit too retro, but if your trusty hammer isn’t broken…

I started with AE back with ver. 7 I think it was, so saw ALL the hits & misses with the various upgrades. It really got infuriating when they’d add something new, only to remove it in the next .5 release. A LOT of user screaming brought back Audition though when they tried to foist some other audio piece of excrement on us that removed most of the tools & features we’d come to depend on.

Sometime back in the early or mid naughts though, I won a full Production Premium Suite of 5.0, upgraded to 5.5 then 6.0. Didn’t even have a 64-bit system initially but that gave me incentive.

Then the accounting weasels took over at Adobe.

Of course they claimed the reason for going to subscription was piracy. They couldn’t see that their real problem was that they were just too top heavy, most likely upper level management. I once needed to contact someone for a very simple issue and got bounced to eight, count then EIGHT different people before getting someone who knew what to actually do. And then it took only 2-3 minutes to resolve. I’d of course been on the phone over 45 mins, but my time meant nothing.

CS6 is/was very stable for me and I still only use a fraction of what it can do anyway and didn’t see any major feature in the CC’s that I couldn’t live without or work around with a bit of effort & imagination. Then I started to see in the various forums that nothing had really changed. People were still having issues each time a new version came out. Scripts suddenly wouldn’t work, crashes, SDK’s weren’t being released in a timely manner to developers, etc. The plus side is that an end user could at least have a previous version installed at the same time which you really couldn’t before. Back then, an upgrade was a one way street unless you wanted to do a full uninstall, install, & re-register. The only difference now really is that users get to pay monthly for the privilege of having Adobe use them as guinea pigs.

But the weasels don’t make it easy.

Try to look something up in your PDF docs and the links (if not broken) take you to the CC version instead of an archived site for what you actually have. Really? A company the size of Adobe can’t maintain useful information for past users? It was individual freelance users that made Adobe a success in the first place. So as more unknowing new users come down the pike, they’re deliberately kept in the dark & think they have no options. With a little effort, one can STILL get CS6, but neophytes certainly wouldn’t know that.

I often use AE for a lot of Photoshop type tasks as it has more transfer mode options & other features. For example even now, I don’t think the current CC version of Photoshop has yet to add variable mask edges capability. Tried to look that up and couldn’t find it mentioned as a feature anyway. Only recently have some features been introduced that would be nice to have, but nothing I can’t live without.

If some situation does come along that I absolutely have to use a CC version of any of Adobe’s products, I’d just get it for a month or so, and just the app I need not the full suite certainly, then drop it like rabid ferret. I routinely use Photoshop, After Effects, Audion, Illustrator, Encore, and Premiere, but sometimes not for months at a time for any one program. Do the math & see what that would cost monthly! It’s just me here, not some huge firm that can write off the cost. I only do this as a sideline plus about to retire from my regular line of work. If I was just starting out, I’d certainly consider Affinity’s products and strongly urge them to come out with an After Effects equivalent that can use AE’s effects and such. I know there’d be a HUGE market. The weasels need some competition.

OK. Need to go refill my mug now so will someone kindly help me down off this soapbox?

[Mark Whitney]

[Vaggelis Valassopoulos] “When i select the 640×480 res the video output is 4:3 and recognized as Square pixels by premiere and it doesnt look transformed to me, but with 720×576 I get a little more content and a little more bars (its fine i will crop them afterwards) and the PAR is DV/D1 PAL 1.0940 and when i playbacked its 5:4 and a little stretched and transformed.
The signal is PAL_B and i assume that with 640×480 the virtualdub does a resize by itself.

to sumup i want to record in DV/D1 PAL 1.0940 and right in premiere to trim and export it as X*576 or 640*480 in 1:1 PAR Square pixels!
How can i achieve this”

Hey Vaggos,

Wow. You’ve quite a variety of things going on there alright. I inherited completing a documentary a few years back where I literally had to deal with every format & codec on the planet, several no longer available, so it can get confusing to say the least.

What I’d recommend to do first is to record a short clip as a test subject before dealing with your 45′ file. Start Premiere (I’m using CS6 but the basics should still be the same) and create a new project. When it brings up the next requestor to chose a New Sequence, you can actually just cancel. That’ll open up the main interface with a blank timeline.

Now, in the Project window, right click and Import your file. Single click select your file and you’ll see what Premiere sees as to the dims and aspect ratio for that file. At this point, go ahead and with the clip still selected, right click on it and select New Sequence from Clip (about half way down in that box that opens). That’ll put a new sequence in the timeline matching the files specs. Not what you’re after yet; it’s mostly just for comparison.

Now, create a New Sequence (Ctrl-N) or select from the menu or the little page with a folded corner icon at the bottom of the Project window. You can search around looking at the Preset Description to find something with the 1.0 aspect you’re wanting, OR in the tab just to the right of the Presets is the Settings panel. Select an Editing mode (or start with Custom) and enter the values you need. Remember to Save this Preset. It’ll end up under a Custom folder in the Presets tab.

Now drag your clip into this new sequence and when it asks, click on the Keep Existing Settings. Drag the timeline indicator & see if that’s giving you what you need. You might have to select the clip in the timeline, right click and choose Scale to Frame Size but most likely not since you customized the size to begin with.

I’d probably do a test render of this to confirm it’s doing what you want. If so, create a new project using 45′ min. file & your new Custom preset.

Hope it works out for you.

[Mark Whitney]

I just happened across this the other day. You wouldn’t have found this searching with any logical params related to your issue though. I saved it for future reference as I’ve run into the same issue.

Take a look starting ~ 13:30

https://www.youtube.com/watch?v=9aBw5LqUT5w

I haven’t tried it but it should work for cameras as well I’d think. Other than that, it’s just a slick tutorial with some other worthwhile techniques.

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Mark Whitney]

You also might try rendering to a sequence instead of a video file. If it fails you haven’t lost everything.

Do the diagnosis suggested above & then see if you can resume from the problem frame.

If that works then you can simply convert the sequence to the desired video format.

[Mark Whitney]

Ah dang. Ya, the rd_ script works only on the selected Layers but no option to select just a particular property(s).

Sounds like ya got a very useful script in the works.

[Mark Whitney]

In lieu of being able to post directly, take listen to this:

https://youtu.be/7O1yRqrkhac?list=PLLAxCYjglxf7xO1FnM0KpotI6GTwMSaqU

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Mark Whitney]

[Dave LaRonde] “And I don’t know of ANY audio application that can do what you want and maintain the original pitch. Or animate variations in pitch, for that matter.”

Adobe Audition has that feature actually. Works fairly well within reasonable change percentages but no keyframing per se that I recall. Probably just treat the entire audio in a separate file & edit as needed.

From the Audion reference PDF:
Stretch and Pitch effect (Waveform Editor only)
The Time And Pitch > Stretch And Pitch effect lets you change the pitch of an audio signal, the tempo, or both. For example, you can use the effect to transpose a song to a higher key without changing the tempo, or you can use it to slow down a spoken passage without changing the pitch.

I’d post an example but the Forum’s utility for that is still goobered. Wish I knew who to poke with sharp stick to get that fixed. Been this way for weeks now.

[Mark Whitney]

Just so you aren’t re-inventing the wheel, you might want to check out the suite of free scripts at the Redefinery, this one in particular:

// rd_RemoveKeys.jsx
// Copyright (c) 2006-2013 redefinery (Jeffrey R. Almasol). All rights reserved.
// check it: https://www.redefinery.com
//
// Name: rd_RemoveKeys
// Version: 3.0
//
// Description:
// This script displays a palette with controls for removing keyframes from
// the selected layers.

Details of the usage on some of these:

https://www.youtube.com/watch?v=DFHtmmuEpHA&t=52s

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.