Adobe Premiere Pro

[AudioVideoMaster]

So is "Adobe Premiere Pro", as Adobe titles it, really just version 7.0? Anyone know?

http://www.adobe.com/products/premiere/main.html

[Arky]

Well, it IS "version 7", but the 'Pro' tag is an attempt by Adobe to promote the fact that they've (FINALLY!!) re-coded Premiere from the ground up, and added some strong features. I suggest you read the following two articles for an overview of what's new.

http://www.creativecow.net/articles/kolb_tim/premiere_pro/index.html

http://www.creativecow.net/articles/velte_mike/premiere-pro/index.html

Also, you might like to cast a glance over this:

http://www.dvc.uk.com/news.php?newsID=72

Edition is a very serious competitor..:

http://dvc.uk.com/products/lev2.php?subnav=software&lev1=pinnaclesoftware&lev2=edition


Arky ;o)

[theReal]

I think Adobe tries to get a foot in the professional market. Up until now, most professionals only use Final Cut Pro for Mac, Silver or Avid (Avid IMO is kind of old fashioned and too expensive, but many pros use it anyways because they're used to it...)

I just got into this discussion as I am now working for a local tv station and all our cutters are using Final Cut Pro. I'm still a Windows guy and will give the new Premiere a try, but I guess it won't have a chance against FCP at our station... (and I can understand why a Mac is better for cutters who don't know much about computers - you just don't have to care about RAM and harddisks - you only buy a Mac and use it)

[AudioVideoMaster]

Originally posted by theReal
I think Adobe tries to get a foot in the professional market. Up until now, most professionals only use Final Cut Pro for Mac, Silver or Avid (Avid IMO is kind of old fashioned and too expensive, but many pros use it anyways because they're used to it...)

I just got into this discussion as I am now working for a local tv station and all our cutters are using Final Cut Pro. I'm still a Windows guy and will give the new Premiere a try, but I guess it won't have a chance against FCP at our station... (and I can understand why a Mac is better for cutters who don't know much about computers - you just don't have to care about RAM and harddisks - you only buy a Mac and use it)

My university I attend just switched over from Premiere to FCP this past year because of the "professional market" using it more. I guess to get us more prepared for that market.

They taught us on FCP in class but didn't require us to use FCP by having to turn in a project file. I picked up things about FCP as they taught us but like you I'm a windows user so in the end I ended up just using my own copy Premiere 6.5, that I had bought in the Fall of last year, for all of my projects. Mostly because I'm already very fast and efficient with Premiere and it's workings especially when I'm editing down to single frames to make multi-camera scenes line up right. I just couldn't get use to using the FCP interface and not having 2 mouse buttons amoung other things. :p

One of the things that always bothered me with FCP was having to save my edits in .mov files. Which I've always seen as being used for internet a/v files that were compressed. I always work uncompressed or with HuffyYUV on windows in Premiere so I know it won't degrade until I'm ready to compress to MPEG-2. So having to save in an 720x480 uncompressed mov file in class always made me wonder if I was degrading the file any. :confused:

[Nahie]

Originally posted by AudioVideoMaster
I just couldn't get use to using the FCP interface and not having 2 mouse buttons amoung other things.

I used to have a mac with FCP and, funny enough, you can use a two button mouse with FCP if you have one. I was using a MS optical intellimouse with USB port. Worked like a charm! The 2nd mouse button works just like holding down the star key thingy.

I don't know why apple doesn't ship 2 button mice but they work great...

The thing I really liked about FCP over Premiere is you could right click (with my 2 button mouse) and have the gaps between video clips automatically close...hopefully Premier Pro will have a feature like this...makes my style of editing go so much faster.

[AudioVideoMaster]

Originally posted by Nahie
I used to have a mac with FCP and, funny enough, you can use a two button mouse with FCP if you have one. I was using a MS optical intellimouse with USB port. Worked like a charm! The 2nd mouse button works just like holding down the star key thingy.

I don't know why apple doesn't ship 2 button mice but they work great...

The thing I really liked about FCP over Premiere is you could right click (with my 2 button mouse) and have the gaps between video clips automatically close...hopefully Premier Pro will have a feature like this...makes my style of editing go so much faster.

That's a neat tip there! I'll have to start carrying around a usb 2 button mouse when I know I'll be using the apple G4 computer lab at the school. :D

I don't know yet if Premiere Pro has that "closing gaps feature" but I know that Vegas 4.0 NLE has this option and it works quite well. Even preserves your transition lengths that have already been set later down the timeline.

[theReal]

One of the things that always bothered me with FCP was having to save my edits in .mov files. Which I've always seen as being used for internet a/v files that were compressed. I always work uncompressed or with HuffyYUV on windows in Premiere so I know it won't degrade until I'm ready to compress to MPEG-2.

.mov (Quicktime) is only a file container, just like .avi

The content of a Quicktime mov file can be DV, MPEG4 or whatever compression you like. I think you can even have Divx 5 in .mov

I guess the codec used for DV-based FCP projects is DV - so no quality loss here.

[BlueCup]

Originally posted in one of the review articles
One other significant Effect Control Window capability… the effects are applied down the list…. in order. Why is this important? Ever try to color correct a blue or green screen clip? Pretty tough as your critical key color gets changed along with the foreground causing you to have to adjust to pull a good key… or maybe compromise on how much correction you can use… This is no longer a problem.

Finally! That has been such a problem. I would have to bring each frame into Photoshop, select the blue bg, inverse, then colour correct.

I've worked with a few NLEs (Rex Edit, Avid) and I've always wanted to bring the work home and just do all it all with Premiere. I hope this new version starts to make more noise and be used more widely in production houses.

[nFury8]

This thing doesn't run on current gen Athlons. It needs SSE2, it's heavily optimized for the P4. But it only runs on WinXP??? We tried installing it on one of the Win2K machines in the office and it didn't recognize the OS? But I guess Athlon64 can take this baby just fine.
:)

[Arky]

I'm getting a little sick of developers recently producing software to run on XP-only, and to produce programs that run only on Intel's CPUs is also rediculous. It is a very worrying step in the direction of Jobs' ethos with Apple. Yes, I do understand the technical differences in instruction sets, and I don't object to optimizations, provided they don't exclude other legit CPUs, but it's a slap in the face for potential customers who have already made a substantial investment in a totally legitimate x86 Athlon chip. As for XP - I will never install it just because some 3rd party developer either can't be bothered to develop openly for Win2k, too, or has some under the table agreement with M$.

IMHO, Adobe should be ashamed of themselves for insulting all their WinNT and Win 2k-using customers, unless they are prepared to bundle an XP upgrade with every Adobe license purchase. I could spend over a grand on the Adobe Video Collection (not that I want Premiere, I should add), and then be faced with the absurd situation of having to shell out another £300 for an XP license, even though NONE of my other prgrams require it. I gleefully await the day a car company attempts to insult it's customer base by developing a car which only runs on one construction company's tarmac :rolleyes: If they do, they'll be in for a nasty backlash, and deserve to lose a great deal of custom. Wake up, Adobe!!


Arky ;o)

[communist]

It works fine here :)
Athlon XP 2000+
And I dont have SSE2 - only SSE(1).

[nFury8]

My mistake then about SSE2, since my main workhorse at home is an Athlon T-bird and it when I tried to install it, it gave me an error message requiring SSE optimization.. It's nice to know it runs on Athlon XP's then :). But still, there's nothing really earth-shaking about its supposedly 'new' features. Vegas already has most of it, if not all. Auto scene-detection, color correction, 5.1 audio support, blah. The only thing it offers as quite different is exclusive WinXP operability, which is hardly enticing, blah.

[GunX]

what is with "confirming scene bla bla" ? after importing DV files...

any capture made with scenealyzer, premiere pro wants to re-save the audio file in another format in "My Documents/Adobe/7.0/Conformed Audio Files"

why ? reconversion to what ? project is 16 bit 48Khz, original audio is identical.....why this gigantic waste of disk space ??

now, another user reported that if making capture from the first with Premiere, this thing doesn't happen !

does anybody knows by what else this procedure is conditioned ?

[GunX]

okay, so nobody knows.... the process takes place no matter what source wav you import (paramters, etc)...so I can live with it, perhaps it is necessarily to be done in order to have real-time playback based on the CPU horse :rolleyes:

but I come up over another incredible buggy and very annoying thing : exporting video and audio in the same avi results in a all messed up audio track (if u got a single little loud noise like a hand-clap, u got some very messy "scratch" there in the final file). the only thing u can do it's normalizing that audio track and keeping it all in very low volume (sometimes even this doesn't work).

but, if you export the audio in a single wav file, it comes out ok (normalized as it should around the rough edges)

[Arky]

Are you inadvertantly downsampling your audio from 48khz to 44.1khz?

Are you choosing an audio codec for your audio, or are you leaving it as 'uncompressed' wave audio?


Just trying to tie up any loose ends ;)


Arky ;o)

[GunX]

thx 4 the reply

no downsampling : 48Khz project, 48Khz sound form a miniDV cam (16 bit), same 48Khz @ export

no compression settings : WAV uncompressed (PCM)

[smok3]

Originally posted by GunX
thx 4 the reply

no downsampling : 48Khz project, 48Khz sound form a miniDV cam (16 bit), same 48Khz @ export

no compression settings : WAV uncompressed (PCM)

i got into the same problem when exporting the mix together with avi, fortunatelly i use other facilites to do the final mix, so that is not an issue for me, but still looks like a major bug. (i used uncompressed audio with huffyuv video for export in the problem case, audio was originaly 44.1 khz and exported as 44.1 as well.)