Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Selur

Pages: [1] 2 3 ... 8
1
H.264/AVC / Re: Getting the latest x264
« on: June 10, 2013, 12:46:17 AM »
No clue about 'generally accepted download site', but these to work:
http://komisar.gin.by/index.html
http://x264.fushizen.eu/

2
Newbies / Re: H264 to DXGM
« on: June 04, 2013, 12:25:37 AM »
Isn't DXGM just normal Mpeg-4 ASP whit DXGM as fourcc ? (so converting to xvid and changing the fourcc should produce dxgm files)

4
H.264/AVC / What happend to x264.nl ?
« on: May 28, 2013, 08:58:38 AM »
x264.nl now redirects me to http://www.videolan.org/developers/x264.html is it gone for good?
What happend?

Cu Selur

5
You are probably right. :)

6
Uploaded the folder content temporary here.
Compilation went fine with the patch. (patched the checkout directly, without the previous patch)

Quote
But google 10.6 only have OpenCL 1.0 so it wouldn't work anyway as minimum version is 1.1
Seems like it, now I get:
Quote
x264 [warning]: OpenCL: Unable to find a compatible device
Do you know if it would help to update to Lion? (my mac mini got a Geforce 9400m; and Lion is the latest that can run on it :()
Latest available driver seem to be: http://www.nvidia.com/object/quadro-macosx-256.02.25f01-driver.html

Cu Selur

7
afaik Mac OS starting with 10.6 directly ships with the OpenCL, but no clue about what needs to be loaded,...

when calling ls -R * on /System/Library/Frameworks/OpenCL.framework/ I get:
Quote
CodeResources   OpenCL

Frameworks:

Headers:
cl.h      cl_ext.h   cl_gl.h      cl_gl_ext.h   cl_platform.h   opencl.h

Libraries:
AMDil.dylib         PTX.dylib         libCLVMCPUPlugin.dylib      libcl2module.dylib      libclparser.dylib
ImageFormats         libCLVMAMDilPlugin.dylib   libCLVMPTXPlugin.dylib      libcldcpuengine.dylib

Libraries/ImageFormats:
float_rgba.dylib   half_rgbx.dylib      sint32_rgba.dylib   snorm8_rgba.dylib   uint8_rgba.dylib   unorm8_a.dylib      unorm8_i.dylib
float_rgbx.dylib   sfixed14_rgba.dylib   sint8_rgba.dylib   uint16_rgba.dylib   unorm16_rgba.dylib   unorm8_argb.dylib   unorm8_rgba.dylib
half_rgba.dylib      sint16_rgba.dylib   snorm16_rgba.dylib   uint32_rgba.dylib   unorm16_rgbx.dylib   unorm8_bgra.dylib   unorm8_rgbx.dylib

Resources:
Info.plist      cl_conversions.h   cl_kernel.h      cl_kernel_shared.h   runtime.amdil.bc   runtime.i386.bc      runtime.ptx.bc      runtime.x86_64.bc   version.plist

Versions:
A   Current

Versions/A:
CodeResources   Frameworks   Headers      Libraries   OpenCL      Resources   _CodeSignature

Versions/A/Frameworks:

Versions/A/Headers:
cl.h      cl_ext.h   cl_gl.h      cl_gl_ext.h   cl_platform.h   opencl.h

Versions/A/Libraries:
AMDil.dylib         PTX.dylib         libCLVMCPUPlugin.dylib      libcl2module.dylib      libclparser.dylib
ImageFormats         libCLVMAMDilPlugin.dylib   libCLVMPTXPlugin.dylib      libcldcpuengine.dylib

Versions/A/Libraries/ImageFormats:
float_rgba.dylib   half_rgbx.dylib      sint32_rgba.dylib   snorm8_rgba.dylib   uint8_rgba.dylib   unorm8_a.dylib      unorm8_i.dylib
float_rgbx.dylib   sfixed14_rgba.dylib   sint8_rgba.dylib   uint16_rgba.dylib   unorm16_rgba.dylib   unorm8_argb.dylib   unorm8_rgba.dylib
half_rgba.dylib      sint16_rgba.dylib   snorm16_rgba.dylib   uint32_rgba.dylib   unorm16_rgbx.dylib   unorm8_bgra.dylib   unorm8_rgbx.dylib

Versions/A/Resources:
Info.plist      cl_conversions.h   cl_kernel.h      cl_kernel_shared.h   runtime.amdil.bc   runtime.i386.bc      runtime.ptx.bc      runtime.x86_64.bc   version.plist

Versions/A/_CodeSignature:
CodeResources

may be this helps.

Cu Selur

Ps.: btw. seems like the 'notification'-feature of the forum isn't working.

8
Thanks! The patch seems to fix the problem. (compiled 8bit and 10bit version)
When trying to use it I get: "x264 [warning]: failed to load OpenCL" but that's another issue.
The mac mini I use got a NVIDIA GeForce 9400M which should support OpenCL, but no clue if I need to install anything else to use it with x264 or if it's too old. :)

9
using:
Code: [Select]
./configure --disable-lavf --enable-staticI get:
Code: [Select]
platform:      X86_64
system:        MACOSX
cli:           yes
libx264:       internal
shared:        no
static:        yes
asm:           yes
interlaced:    yes
avs:           avxsynth
lavf:          no
ffms:          no
gpac:          no
gpl:           yes
thread:        posix
opencl:        yes
filters:       resize crop select_every
debug:         no
gprof:         no
strip:         no
PIC:           no
visualize:     no
bit depth:     8
chroma format: all

You can run 'make' or 'make fprofiled' now.
it fails with: http://pastebin.com/G1sjBEj6
if I use --disable-opencl compilation works fine.
Is there a way to compile x264 with opencl support on Mac OS X 10.6.8 or does it require a newer Mac OS X version?

Cu Selur

10
H.264/AVC / Re: x264 settings
« on: April 28, 2013, 11:10:25 PM »
Code: [Select]
x264 --fullhelpshows the settings which are used by a preset
Rumbah over from doom9 also keeps a fullhelp.txt online (http://forum.doom9.org/showthread.php?p=1620606#post1620606)

11
What do you command line calls look like?
And yes decoding with ffmpeg and piping to x264 for encoding can work fine.

12
Newbies / Re: Some questions on h264
« on: March 30, 2013, 05:59:48 AM »
I normally use MakeMKV to copy DVDs to hdd and reencode with Hybrid (not ment for newbies); both work on Mac/Linux/Windows so they are a good combination for me.

13
Newbies / Re: Some questions on h264
« on: March 29, 2013, 09:36:59 AM »
1. ffmpeg can use x264 and there should be no difference between ffmpegs and x264 output if ffmpeg is using x264 as encoder; I'm not even sure if libav still contains a functional H.264 encoder on it's on or if it has switched to x264 completely,...
2. I prefer qaac because it's output sounds better to me, but there are probably some more objective audio codec comparisons out there (iirc the hydrogenaudio community did some aac listening tests where both qaac and nero's aac encoder were part of)

14
Newbies / Re: Some questions on h264
« on: March 29, 2013, 06:47:01 AM »
regarding:
1. x264 is better than the libav H.264 implementation (ffmpeg normally can use both)
2. no clue, everybody simply used what best meets their needs
3. yes/no, a. you can use the external encoder feature of Virtual Dub to encode using the x264.exe, b. there's an unofficial vfw x264 version c. there might also be support for x264 vfw encoding through ffdshows vfw interface

15
Code: [Select]
--cabac --ref 16 --deblock -1:-1 --partitions i4x4,i8x8,p8x8,b8x8 --me umh --subme 6 --psy-rd 1.0:0.0 --merange 16 --trellis 2 --8x8dct --cqm jvt --deadzone-inter 21 --deadzone-intra 11 --qblur -4 --threads 6 --bframes 8 --b-pyramid normal --b-adapt 2 --b-bias 0 --direct spatial --keyint 250 --min-keyint 25 --scenecut 40 --crf 18.0 --qcomp 0.60 --qpmin 10 --qpmax 51 --qpstep 4 --ipratio 1.40 --pbratio 1.30 --aq-mode 1 --aq-strength 1.00should be a conversion the encoding settings (aside from zones=202334,207820,q=70) to the normal x264 command line syntax.
Not sure if it helps unless MeGui has some sort of "import x264 cl settings" option.

About the concatenating: I would demux both streams and then append them through mkvmerge/mmg. (I would not try to concatenate the raw H.264 streams.)

16
H.264/AVC / Re: x264 and Flash Player 11, how to get low-latency playback?
« on: February 18, 2013, 02:30:36 AM »
Quote
I tried many combinations of low-latency settings such as:
never done anything in this section of x264 usage, but you also tried: av_opt_set(context->priv_data, "tune", "zerolatency", 1) to enable zerolatency, right?

17
H.264/AVC / Re: VBR worse than CBR?
« on: February 16, 2013, 05:46:30 AM »
I agree that in theory such a stream can be created, but I doubt that you can encounter a natural occurring stream which, if you aim for a specific file size, will create the same output through 2pass and 1pass encoding. (assuming you do not find a way to cripple the 2pass settings in a way that it is basically a 1pass encoding)

18
H.264/AVC / Re: VBR worse than CBR?
« on: February 15, 2013, 12:35:37 AM »
2pass is only a waste of time you are not aiming for a specific file size, it's not dependent on the content,..

19
H.264/AVC / Re: VBR worse than CBR?
« on: February 14, 2013, 10:53:09 PM »
Quote
Is there some reasonable scenario to do that?
sure, if you capture it 1st just to have it, but later need it at a specific size.

Normally you use:
1. crf if you don't need a specific file size
2. 2pass if you need a specific file size

Cu Selur

20
H.264/AVC / Re: Audio Cutting
« on: February 07, 2013, 02:37:47 AM »
Quote
Should it be like this?
more like:
Code: [Select]
video=FFVideosource("xxx")
audio=FFAudiosource("yyy")
AudioDub(video, audio)
Trim(last, 0, 40000)
return last
or
Code: [Select]
video=FFVideosource("xxx")
audio=FFAudiosource("yyy")
av = AudioDub(video, audio)
av = av.Trim(0, 40000)
return av
or
Code: [Select]
AudioDub(FFVideosource("xxx"), FFAudiosource("yyy")).Trim(0, 40000)

21
H.264/AVC / Re: Audio Cutting
« on: February 05, 2013, 12:27:52 PM »
if you also want to reencode the audio, you could:
1. load the audio source in Avisynth
2. AudioDub(video,audio)
3. trim the audio alongside the video

otherwise you will probably have to calculate the cut times and cut the audio with the audio editor of your choice.

22
Encoder GUIs / Re: "Encoding settings" of Mediainfo = Staxrip settings ???
« on: February 05, 2013, 05:43:36 AM »
I even wrote a gui that converts the 'Encoding settings' to x264 cli syntax: Mis2x264 - MediaInfo Encoding settings to x264 cli so it StaxRip has some sort of x264 command line options importer this might help.

Cu Selur

23
Newbies / Re: Psy-RD
« on: February 01, 2013, 06:27:48 AM »
Quote
Psy RDO measures, in addition to normal PSNR-wise distortion, the difference in complexity between the reconstructed frame (what the video will look like on decoding) and the source frame. It values complexity values as close to that of the original frame as possible. Thus, it strongly biases against blurring, and for that matter, any significant loss of detail. Even on non-grainy sources, this generally results in a reduction of banding, increased sharpness, and better retention of fine details. The speed cost is relatively low, though Psy RDO requires regular RD to be enabled.
source: http://x264dev.multimedia.cx/archives/37

http://forum.doom9.org/showthread.php?t=138293 might also be interesting to read.

24
Newbies / Re: Psy-RD
« on: January 30, 2013, 06:48:44 AM »
why not?

25
Newbies / Re: x264 cli error
« on: January 08, 2013, 08:25:43 AM »
I would try a more simple call, e.g.:
x264 --crf 19 --vf crop:0,132,0,132 --input-res 1920x1080 --preset slow --tune film  --fps 24000/1001 -o Looper.2012.mkv Looper.mkv
other than that 'No clue' (assuming your system has no heat problems etc.)

26
Newbies / Re: x264 cli error
« on: January 08, 2013, 01:38:38 AM »
Quote
If lav is the issue any suggestions as an alternative in linux?
no (even on windows there's no real alternative, aside from DGDecNV which isn't freeware; okay and going through directshow)

----
If the video stream in your blu-ray folder (I assume on hdd) is faulty using another ripper might help (makemkv might work).

27
Newbies / Re: x264 cli error
« on: January 07, 2013, 11:32:15 PM »
Quote
[h264 @ 0x2b0d580] number of reference frames (0+5) exceeds max (4; probably corrupt input), discarding one
Segmentation fault fps, 5173.71 kb/s
That sound like your input is corrupt (or lav can't decode it properly) at one point. -> tried another source?
Since you mentioned you convert blu-ray content, I hope you used a decent ripper to copy the content to your hdd, since x264 won't be able to circumvent any encryption / copy protection.
Btw. Why are you using eac3to to demux the video before encoding and not feed the mkv (makemkv is a good tool to do Blu-ray/DVD to mkv and aside from the WIndows version it was a Linux and a Mac version aside directly to x264?

28
Newbies / Re: x264 cli error
« on: January 07, 2013, 09:51:25 AM »
Quote
I've tried it several different ways with and without the - fps syntax including 23.976 and - - force -cfr (something to that effect).
I normally use "--fps 24000/1001" and you are the first user that I see using "--fps 24000/1001p".

Quote
Do I need to run this through ffmpeg or should x264 be able to handle this? From what I've read this should all be able to run in x264 cli with lavf support I'm just scratching my head at this point.
libavf should be able to decode normal stuff (there might be problems if the content is interlaced, which shouldn't be the case since your inptu should be 24p; not sure how interlaced avc is nowadays supported by lav)

Quote
Also, is compiling from git the best or correct way to install x264 in Linux?
should be as valid as installing it from through the package manager,...

Cu Selur

29
Newbies / Re: x264 cli error
« on: January 07, 2013, 06:41:22 AM »
"--fps 24000/1001p"
are you sure the 'p'- at the end is right? (never say this syntax except in mkvmerge)

30
Newbies / Re: x264 cli error
« on: January 06, 2013, 11:46:28 PM »
wild quess: "rc-lookahead 175" causes x264 to run out of ram -> iirc. 175 should consume 4GB+ of RAM
=> try if it helps to lower rc-lookahead  (even preset placebo only uses 60!), try something like 15 or 40

Pages: [1] 2 3 ... 8