Al Bergstein
Forum Replies Created
-
Thanks. Good input.
Alf
-
I owned an hmc150 for a year and a half and loved it. I recently sold it and upgraded to acanon xf305. It all depends on your shooting. What are you going to use it for? It’s not great for low light but to be sure it seems like a lot of wedding photogs do use it, given the boards i’ve been on.
As to vegas, i had 9 but upgraded to 10 & it works much better for avchd. It imports natively and with device explorer it imported them fine. No drop outs. If you can’t wait a few months for the hmc250 then you likely will like the 150, as long as you don’t shoot in really low light alot. I switch over to my 7d for that.
Another option to think about is the Canon xf100. Much better low light camcorder.also works well with vegas, in 4:2:2 at 50 mb. Superb picture imho.
But the bottom line is that you need to be clear about your requirements. For me the 150 was a superb camera for the price and i highly recommend it. Vegas 10d will handle the footage fine.
This is a low light shoot done with the 150, and boosted a bit in post. I think it turned out well.
https://m.youtube.com/index?desktop_uri=%2F&gl=US#/watch?v=9P6i9P9gk4MAlf
-
No, I’ll thank you both now! Thanks!
Alf
-
OS API’s are certainly one thing, but I would imagine that for Boris and other add on app developers there are programmatic API’s for FCP etc. I could be wrong, just extrapolating on other apps out in the world. And yes, likely the average user isn’t going to be doing a lot of additional GUI scripting I would assume.
From some of the screen shots posted in the last few days it appears that they are rolling out a bit of info about X to the dev community that cares about it at WWDC.
As to ‘bloat’ in OS’s, it seems inherent to me that as you add functionality and features, you add size. Most 64 bit OS’s that I’m aware of were larger than their 32 bit counterparts. In total MBs on the disk I mean, not just the address space (G). The OS for a phone is always going to be more efficient than a full function computer, I would guess.
So was there more about X that’s been brought out from the follow on days of WWDC? I’ve been heads down in a project, and unable to take much time to surf looking for stuff.
Alf
-
I use it Ray, with no problems. I did find I needed to go to 10 to get it to work better. of course, transcoding to AVI with Neoscene makes it edit better, but with huge file sizes created. Your workflow will need to be put your raw footage on one drive, transcode to AVI, and put that on your work drive, do your work finish the project, and then delete the AVI files and relink everything later if you ever need to come back to it. Or just edit natively if you don’t need great color grading or green screen effects. You might find you don’t.
Alf
-
Ok. I’m currently rendering and wanted to get back to this. Here’s the situation and you can try it or not. I take three or four separate camera angles. I make sure that the soundtracks are synced, (I can do it by hand as I use a clapper in the studio), I create a multitrack edit and collapse them to a single timeline. I make my camera cuts. Everything is fine. I finish the camera cuts, and then, for whatever reason, I decide I need to move a take, often it’s the first or last, for example, where I want to trim off something at the beginning. Let’s say I grab the first clip at the beginning of the multiclip edit,and try and move it. It crashes Vegas. Or I slip it to the beginning of another bit of clip (because I’m bumping it up against the previous footage). Then it crashes. I reopen Vegas, and go to that same place, and move that same footage, and boom, it crashes Vegas again. I can do it over and over again. So how did I get around it? I decided to try going out of multiclip and reexpanding the footage into multiple tracks, like you do when you are finished making your multitrack edits. Once I have the footage back into multiple tracks I can then move edits around just fine. This must be a known problem with Vegas, and the documentation does not warn about not doing this. What I can say is that once you have made your edits in multitrack mode, don’t try and mess with your timeline before you unpack those tracks.
Does this make sense? And while you may not experience this in HDV footage, I am using a combination of AVCHD (Canon GH2), MOV from a Canon 7D, Canon xf305 MPEG-2 and JVC MPEG-2. The software is having to handle much large file sizes than HDV.
My guess is that this is a bug. I’m going to eventually send it in to Sony, but I just don’t have time now. Back to work.
Alf
-
Here’s the crash log and the place I was at when it happened…not sure this will help, but for what it’s worth…I was attempting to add the Sony color corrector to this clip. It worked with other clips in this part of the multicamera edit.
Alf
-
Steve, I’m in the middle of a deadline that this editing is due tomorrow. I don’t do HDV, I have been working with multiple cameras using different formats, due to a lack of budget to shoot everything in the same format. I can most definitely reproduce this bug. I’ll work on getting something to the board after that. For now, I’ve posted that I’ve been able to work around it by moving the footage from the multiedit mode back into multitracks, if I’m saying that right. Got to get back to work, I have a long evening ahead of me.
Alf
-
Ok, Walter. You’ve been at this longer than I have. If you say that’s the way they traditionally work, I’m fine with assuming all is well. I have no need to run to the newest version immediately, and if the Coen Bros. feel that it’s the best thing they have used, then great! I’m onboard.
It’s odd to me that they wouldn’t be briefing 3rd party developers at the WWDC on how to program to this new app, given 64 bit changes, etc. and that they would like to have add-ons at launch of the real thing. Maybe they are just on a different path than the rest of Apple. I have no idea. I’m not going ballistic on this, just wondering what’s up…
Alf
-
Ok. Here’s something I think I’ve learned. If you are going to edit multicam, here’s what seems to be “stable” for me.
Create a multicam workflow.
Create a single multicam track.
Edit the video for camera changes.
Expand the multicam track out to it’s individual components.
Toggle off multicam workflow.
Edit the footage.This has allowed me to work without crashes today. This is *different* workflow than yesterday, when I tried editing the footage without expanding it out. To be clear, there is nothing in the documentation to warn you that you should do this kind of workflow.
Is this something that others, like John R, have found to be the proper workflow for multicam?
To be clear, I have not had crashes today, using this method, which I stumbled on.
Alf