+ Reply to Thread
Results 61 to 90 of 2189
this whole thing about other container support makes me sad and adds distrust in the development teams of video processing utilities. as a long time programmer i see no reason to develope an (crippled) encoder and say that it is not at the top of a list of priorties or other nonsense reason to include support. if i were a c/c++ skilled programmer i would have added the avisynth or other proxy/frameserve support. heck, if i knew how to write a proxy (frameserver) mechanism i would just create one so we could all move foward in this new encoder.
in fact, from this point forward, anyone who creates a spinoff h265 encoder, should brand it a new name, VH265 sounds good to me. enough of this nonsense. lets move forward, and figure out how to write are own frameserve!
Well here is a video and information on how to insert a video. H265 in mp4 container with GPAC
MPEG-HEVC Support in GPAC
mp4 video play slow with virtualdub capture.I have renamed video.hm10 to video.h265
General Complete name : C:\mp4test\video.mp4 Format : MPEG-4 Format profile : Base Media Codec ID : iso4 File size : 14.1 MiB Duration : 3mn 56s Overall bit rate : 499 Kbps Encoded date : UTC 2013-08-03 19:50:24 Tagged date : UTC 2013-08-03 19:50:24 Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Codec ID : hvc1 Codec ID/Info : High Efficiency Video Coding Duration : 3mn 56s Bit rate : 497 Kbps Maximum bit rate : 2 290 Kbps Width : 1 280 pixels Height : 720 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 25.000 fps Bits/(Pixel*Frame) : 0.022 Stream size : 14.0 MiB (100%) Title : h265:FMT=HEVC@GPAC0.5.1-DEV-rev4692 Encoded date : UTC 2013-08-03 19:50:24 Tagged date : UTC 2013-08-03 19:50:25
Last edited by Trepack; 3rd Aug 2013 at 15:32. Reason: Insert Mediainfo
just a question, i'm pretty sure some of you mentioned something about using mencoder to pipe non-y4m video to x265, has anyone tried anything like this:
i would try it myself but i've been trying a number of half-assed approaches to see if i can "trick" existing open source apps that use x264.exe into thinking x265.exe is x264 and getting it to encode hevc thinking it's avc.
it's not going well, but i still have a few tricks up my sleeve.
Wow! 1280x720 at 1.16fps on a Q6600 XP machine is really slow. Good thing it's a small file so it shouldn't take too long. The command __gops 4 was not a valid command so I had to leave it off but it seems to be encoding alright. We'll see.
Using vhelp's command: x265.exe --q 20 --width 1280 --height 720 --rate 29.970 --frame-skip 0 --frames ALL --input "C:\Tools\x265-2013-08-03[3db96ea]\Untitled-2b.avi" --rect --max-merge 1 --hash 1 --wpp --no-rdo --tu-intra-depth 1 --tu-inter-depth 2 --no-tskip --output "C:\Tools\x265-2013-08-03[3db96ea]\Untitled-2b.h265"
So far at least, these are the FourCCs accepted by the Lentoid H265 DirectShow Decoder:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Tools\x265-2013-08-03[3db96ea]>x265.exe --q 20 --width 1280 --height 720 --ra
te 29.970 --frame-skip 0 --frames ALL --input "C:\Tools\x265-2013-08-03[3db96ea]
\Untitled-2b.avi" --rect --max-merge 1 --hash 1 --wpp --no-rdo --tu-intra-depth
1 --tu-inter-depth 2 --no-tskip --output "C:\Tools\x265-2013-08-03[3db96ea]\Unti
yuv [info]: 1280x720 29Hz, frames 0 - 1317 of 1318
x265 [info]: detected SIMD architectures SSE2 SSE3 SSSE3
x265 [info]: performance primitives: intrinsic assembly
x265 [info]: Main profile, Level-3.1 (Main tier)
x265 [info]: thread pool with 4 threads, WPP enabled
x265 [info]: CU size : 64
x265 [info]: Max RQT depth inter / intra : 2 / 1
x265 [info]: ME method / range / maxmerge : star / 64 / 1
x265 [info]: Keyframe Interval : 32
x265 [info]: WaveFrontSubstreams : 12
x265 [info]: QP : 20
x265 [info]: enabled coding tools: rect amp no-rdo rdoq sao sao-lcu sign-hide
x265 [info]: frame I:42 kb/s: 5310.86 PSNR Mean: Y:53.640 U:55.469 V:56.305
x265 [info]: frame P:1276 kb/s: 912.29 PSNR Mean: Y:53.157 U:52.511 V:53.625
x265 [info]: global: kb/s: 1052.46 PSNR Mean: Y:53.173 U:52.605 V:53.710
visual studio error: An unhandled win32 exception occurred in x265.exe 
It looks like a file was encoded though, 5.78 MB. I'll have to mux it and see if it plays.
^ Yes. But more importantly, they are the FourCCs that an AVI (or a VfW-compatible MKV) file must have, in order to allow the media splitter to connect to the H265 decoder.
Last edited by El Heggunte; 4th Aug 2013 at 20:13. Reason: .....
just use .265 like .264 does. these are to denote the format anyway. and once the proper container(s) have been finalized, it will be a matter of when the encoder(s) sport their prefered container, i.e., .ts m2ts .mkv and so on. no doubt, mkv will probably be chosen.
in my initial encoder trails i was using .h265 as the extension since the video was raw from some of the encoders only option. it aided me to realize the videos i was encoding were raw (containerless) videos.
but if you can wrap in a new container, i.e., mkv, then obviosly you use those extention names.
visual studio error: An unhandled win32 exception occurred in x265.exe 
Just a VERY-wild guess (because I don't have Visual Studio) --- there is at least one service related to Visual Studio running in the background, and you should stop or disable it/them.
Last edited by El Heggunte; 4th Aug 2013 at 22:24.
I tried turning the debugger off last night but it still kept popping up. Do I need to turn off error reporting service also?
I created a smaller resolution file but it's not working in graph studio either. A corrupt frame starts up and instead of playing normally, frame by frame, it just scrolls to the right for four or five frames and locks up the player. The progress bar still moves to the end but the video doesn't play and I have to manually stop Graph Studio because it stopped responding.
How do I get this .265, hvc1 or whatever file into an mp4 container? Mymp4box doesn't recognize the file type.
MP4Box from one of the GPAC "nightlies":
http://gpac.wp.mines-telecom.fr/downloads/gpac-nightly-builds/#Windows 32 bits
BUT if you already have this, then just drop the GUI(s) and use the command prompt.
P.S.: And if your copy of x265 is creating invalid streams, well......
No existe Gop en la nueva version de X265 - -. El archivo HEVC encodeado por la nueva version de X265 no es capaz de ser decodeado por el decodeador de Strongene y ya he reportado este problema a Strongene
Thanks again, Trepack
And this one is for Selur "et al"
I wrote to Steve Borho:
Now, to the main subject...
The thing says:
2. SYSTEM REQUIREMENTS
Hardware: AVX capable CPU recommended
At least 8GB of RAM
Software: Win7/8 x86_64
Microsoft Visual C++ Redistributable Update 3
Minor fact: OK, this is actually a PBKAC, but some people have
interpreted "recommended" as *mandatory* :-\
This document was written to be distributed with a very specific x265.exe that we were providing to potential consortium members.
And yes a lot of people take it out of context.
The documented system requirements were only for the one particular build of the alpha version.
(Changed software status from "alpha" to "pre-alpha" as detailed in the referenced ExtremeTech article.)
Last edited by El Heggunte; 6th Aug 2013 at 01:12.
Thanks, good to know.
Last edited by El Heggunte; 5th Aug 2013 at 13:42.
I hope not to bother him with my words, which to me is just easier to understand Spanish, but I understand that the forum is English ¿forgive him this once?
@ El Heggunte
Know how to solve the problem by closing with control + c to windows detects an error in the application as well as when the program ends encode?
Is a program problem?
Last edited by Trepack; 5th Aug 2013 at 13:07.
Last edited by El Heggunte; 5th Aug 2013 at 17:10. Reason: .................
JEEB me ofrecio una forma de configurar cmake, el cual hace posible que mingw pueda encodear x265 de 64bits
La respuesta de Strongene
Gracias por su interes. Si se confirma de que dicho problema es nuestro, intentaremos solucionarlo lo antes posibles
La segunda respuesta
Vale, Gracias, lo resolveremos lo antes posible
I do not speak English
I don't speak Spanish or Chinese. Your post do absolutely nothing for me.
Hard to produce a working file when every encoder uses a different command line. Every file I try to create ends with a crash in the encoder and the out put, although it kind of plays (corrupt frames) crashes every player.
Working sample commands would be nice for each encoder so we can tell if it's our command line or our system that refuses to create a working file.
I just formatted a spare drive and will install a back up image of my operating system when I knew everything was working fine. I've installed and uninstalled so much crap the last couple of months trying to get 265 and VP9 to work that I don't know how much damage I've done to the operating system.
Maybe XP with 4GB of memory and a Q6600 cpu is just not good enough to create a working file.
Thanks for your GCC 4.8.1 builds, including the 64-bit and 16bpp versions
BUT, when I try to run one of 32-bit MSVS builds under Windows XP Pro, ......
blah-blah- blah, x265_32BIT-8bpp.exe is not a valid Win32 application.
2013-07-31 22:27 <DIR> . 2013-07-31 22:27 <DIR> .. 2013-07-31 22:06 3,084,417 x265_32BIT-16bpp.exe 2013-07-31 22:00 4,660,633 x265_32BIT-8bpp.exe 2013-07-31 22:25 3,883,557 x265_64BIT-16bpp.exe 2013-07-31 22:16 5,765,800 x265_64BIT-8bpp.exe 4 File(s) 17,394,407 bytes 2 Dir(s) 33,731,781,632 bytes free
2013-07-31 23:03 <DIR> . 2013-07-31 23:03 <DIR> .. 2013-07-31 22:46 1,592,320 x265_32BIT-16bpp.exe 2013-07-31 22:38 2,588,160 x265_32BIT-8bpp.exe 2013-07-31 23:03 1,676,288 x265_64BIT-16bpp.exe 2013-07-31 22:56 2,702,848 x265_64BIT-8bpp.exe 4 File(s) 8,559,616 bytes 2 Dir(s) 33,731,781,632 bytes free
Last edited by El Heggunte; 5th Aug 2013 at 16:11. Reason: add P.S.