--- On Fri, 7/9/10, [email protected] <[email protected]> wrote:
> From: [email protected] <[email protected]> > Subject: Re: [Lives-users] 720P and mpeg4 > To: "LiVES users list" <[email protected]> > Date: Friday, July 9, 2010, 8:10 PM > On Sat, July 10, 2010 02:08, John > wrote: > > > > > > --- On Thu, 7/8/10, [email protected] > <[email protected]> > wrote: > > > >> From: [email protected] > <[email protected]> > >> Subject: Re: [Lives-users] 720P and mpeg4 > >> To: "LiVES users list" <[email protected]> > >> Date: Thursday, July 8, 2010, 11:42 PM > >> On Fri, July 9, 2010 01:19, John > >> wrote: > >> > I'm trying to edit and save a 1280 X 720P > file that I > >> took with my HP > >> > camera. I'm having a hard time finding a > codec that > >> can encode the clip > >> > without changing the resolution or frame rate > (29.970 > >> fps 32 bpp). I tried > >> > the transcode_encoder mpeg4 but it flipped > the video > >> upside down and it > >> > gave the video a blue hue. The original file > is a .mov > >> file that's about > >> > 212MB. I'd like to keep as much info but I > don't want > >> to end up with a GB > >> > file. Any suggestions? > >> > > >> > > >> > >> You could try with the x264 encoder and the > experimental > >> blu-ray 720p NTSC > >> format. There are some caveats though: > >> > >> 1) Currently audio encoding is not working (due to > a bug in > >> current mencoder) > >> 2) The framerate will be upsampled to 60000:1001 > >> 3) You will need a VERY recent version of x264 > (see > >> http://www.videolan.org/developers/x264.html) > >> > >> Actually this needs testing, so it would be really > helpful > >> if yu could try > >> this. > >> > >> Regards, > >> Gabriel. > >> > >> > >> > >> > > > > I'm having problems getting the file to load with > audio using 1.3.4. It'll > > cause lives to crash. > > > > jackd 0.118.0 > > Copyright 2001-2009 Paul Davis, Stephane Letz, Jack > O'Quinn, Torben Hohn > > and others. > > jackd comes with ABSOLUTELY NO WARRANTY > > This is free software, and you are welcome to > redistribute it > > under certain conditions; see the file COPYING for > details > > > > no message buffer overruns > > JACK compiled with System V SHM support. > > cannot lock down memory for jackd (Cannot allocate > memory) > > loading driver .. > > creating alsa driver ... > hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit > > control device hw:0 > > configuring for 48000Hz, period = 1024 frames (21.3 > ms), buffer = 2 > > periods > > ALSA: final selected sample format for capture: 16bit > little-endian > > ALSA: use 2 periods for capture > > ALSA: final selected sample format for playback: 16bit > little-endian > > ALSA: use 2 periods for playback > > JACK: unable to mlock() port buffers: Cannot allocate > memory > > JACK: unable to mlock() port buffers: Cannot allocate > memory > > cannot lock down memory for RT thread (Cannot allocate > memory) > > Jack audio error cannot lock down memory for RT thread > (Cannot allocate > > memory) > > subgraph starting at LiVES-3852 timed out > (subgraph_wait_fd=15, status = > > 0, state = Running, pollret = 0 revents = 0x0) > > > > > > **** alsa_pcm: xrun of at least 55.255 msecs > > > > > > Jack audio error zombified - calling shutdown handler > > jack shutdown, setting client to 0 and jackd_died to > true > > trying to reconnect right now > > unique name `LiVES_audio_out-01' assigned > > > > > > I'm not an expert with jack, but it looks like you are > trying to run it > with realtime thread priority. Nothing jack related has > changed in the > last version of LiVES. If you really need realtime priority > (e.g. with a > realtime kernel) then I suggest you run LiVES as root > (probably not a good > idea). Or you can delete your ~/.jackdrc file and let LiVES > re-create it > on startup. > > Cheers. > Gabriel. > > Not sure how it was set to realtime. Anyhow, deleting the file solved the problem. Okay, I downloaded and compiled the latest version of ffmpeg and x264. I'm trying to save the file as x264 blu-ray 720P NTSC but I get an error that says x264: option requires argument --'o' and then encoding failed. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Lives-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lives-users
