Joe Mcneilly
Forum Replies Created
-
I’ll give that a shot. Hopefully the text will stay crisp! Thanks for the suggestion.
-
When you specify “FTP” as the destination, there’s no obvious path to the local file. So if the FTP fails, the output file seems to vanish. But it must be in a local cache somewhere, right?
-
If I go below .1, it automatically bumps it back up to .1 =/
-
Thanks for the tips. Producer Pro is so flaky! It’s totally inconsistent with picking up the signal from the io, and when it does it can’t always display it correctly. though when it actually works, down-converting is much smoother.
I’m going to try running it on a Mac Pro tower, see if the extra processors will help. Thus far I’m very disappointed in Producer Pro, they really oversell it and its practically worthless.
-
I’ve just started testing a similar system – Ustreaming from io/HD on a 17″ MBP. i bought the producer pro desktop application, but still get some choppiness in the stream (even at SD bitrates) and have probs with the audio coming out of sync both during broadcast and in the recorded file.
Occasionally Producer Pro fails to identify the audio input from the io, and there’s an irritating system conflict that makes Producer crash if the io is powered on when I launch it. If i turn the io off, then launch Producer, it complains that it can’t find the io. So I turn the io on after launching Producer, then I have to go through the device configuration menus every single time to get Producer to correctly see input stream.
I’m thinking Producer Pro may be choking a bit on transcoding the ProRes stream coming from the io, so I i’m going to try using a Hauppauge HD-PVR i have sitting around. I’m also going to try ‘casting from a more powerful desktop system, but that kills the mobility of the laptop. hoping to not have to buy another piece of hardware to make this work smoothly. If anyone has any tips or suggestions, I’d love to hear them!
-
The EX1 is a fantastic camera, workflow is really streamlined. I hate upscaling and mixing formats, if you can shoot at your delivery size life is much easier!
-
I’ve contacted the folks who make the software for comment… in the meantime I’ve discovered a workaround that doesn’t require transcoding.
I can put the file into a Motion project, and then import the Motion project to FCP with no problems. WTF?I’m really baffled as to why some Quicktime-based programs (QT Pro, Motion) have no trouble with these files but Final Cut is rejecting them. Aren’t they all based on the same architecture?
If I get any more useful bits from the makers, I’ll post them.
-
The only reason I’m transcoding is that importing in their native format is failing. Otherwise, I wouldn’t be going to ProRes or changing the framerate.
-
OK, weirdly enough if I transcode to ProRes but drop the framerate to 30 (native is 720p 59.94) the footage will now import to both FCP 6 and 7. this is not ideal as it adds an extra step to the workflow and forces me to work at 30 fps instead of 60, but its a start. any ideas why this is happening?
-
1280×720, 59.94