Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Windows / Hardware Encoding Capabilities
« Last post by apollo567 on February 26, 2017, 07:12:37 AM »
Hello,

I just wanted to ask where I can find more detailed information about which kind of Hardware accerlation for Videoencoding s currently available ?

I have currently a Skylake CPU with  a Pascal-Nvidia GPU in use.
Is the relevant Quicksync-Level or die Nvidia Videoprocessor VP8 already supportet in some way ?

Kind regards
apollo
12
Main version 2.6 / Re: Bugs report + suggestions
« Last post by AQUAR on February 26, 2017, 12:14:59 AM »
A layman's interpretation:   

Avidemux 2.6 branch is not a frame based video editor.
AFAIK this means that ADM its not aware of what the video decoder is doing wrt spitting out the next frame from the sequence of virtual frames in the video buffer.
You need to know all about the frame ordering before you can pinpoint a full frame.

Avidemux 2.5 branch was a frame based video editor.
It was doing the frame ordering itself on those simpler codecs.

I other words - its a consequence of dealing with advanced video codecs using time stamps.

Maybe Mean or Eumagga will explain better.
13
Main version 2.6 / Re: Can't install Nvidia libraries and compilation problems
« Last post by PhilB on February 25, 2017, 10:37:47 PM »
I downloaded from fosshub v 2.6.18 final - md5 947176e91a2a7fcd6790da7c0f19d5e3

bash bootStrap.bash --deb stopped before the end (buildCore)
but
bash bootStrap.bash --deb --with-cli successfully built the 10 deb files.

It worked once and I won't bet that if I type the same command with the same version it will work twice. Maybe that was luck... or the comp was in a good mood ...

I have kept and archived the logs coming from the /tmp directory.
14
Main version 2.6 / Re: Can't install Nvidia libraries and compilation problems
« Last post by PhilB on February 24, 2017, 10:55:25 PM »
I have checked everything. RAM, hard drives, all needed libraries are here.
I give up and will use the appImage.
Thanks for your help.
15
Main version 2.6 / Re: AVC with mpeg layer 2 sound crashes
« Last post by vlado44 on February 24, 2017, 08:06:25 PM »
Thanks  eumagga0x2a,

I enclose the log file. Thank you for your help.

Vlado
16
Main version 2.6 / Re: Bugs report + suggestions
« Last post by acritum on February 24, 2017, 12:12:12 PM »
And yet another suggestion [FRAMES] and [SAVE AS BMP].

I'm working with long videos now and I need to select and saveseveral hundred frames from these videos (kind of BMP thumbnails). First of all, I find it more convenient to refer to singe frames by a frame number rather than by time. If I need to remember a single frame to get back to it later, I'd rather write down 3652 as a frame number on a paper, than something like 00:02:11.633. Virtual Dub shows both time and frame number, but I'm not sure if it is possible with all file formats (Vdub works with AVI only). If it is possible, having this reference would be useful. And also a possibility to jump to a frame number (like "Go to time" button that we already have).

The next problem is that the frame saving process is too much boring. It's OK if we need to save one frame, but no more than that... When we press Ctrl-M, the default name shows 20161001_122859.bmp, but it is only fine for one file. If we save many files, we'll have to make up some unique names manually and this is not cool at all. As a solution, I suggest to set default file name to "sourcename_framenumber.bmp" when saving a single image. So, if we save many images, the names would be like 20161001_122859_1.bmp, 20161001_122859_554.bmp, 20161001_122859_15852.bmp... Alternatively (if it's hard to calculate the frame number), time offset of the frame can be used as a suffix making the fname unique (something like  20161001_122859_00_02_11_633.bmp). The work will become even faster if we could save frames without showing the confirmation window at all (as an option). Or maybe ask the target folder and file name template once for the first image, and then name and save the following frames automatically. I know this is not easy to implement and the perfect solution is not obvious, but again, these are just my thoughts and nobody has to do anything to make  them real if he doesn't want to. By now I found another solution, I just used ffmpeg.exe to extract all I-frames as BMP files and now review them and select the images that I need to keep and delete the others. This is really faster than saving single images with Ctrl-M in Avidemux and enter and confirm file names for every file, at least now.
17
Main version 2.6 / Re: Bugs report + suggestions
« Last post by acritum on February 24, 2017, 09:47:39 AM »
I'm going to reach the monthly suggestion count limit, but still there's another one (taken from Virtual Dub).
When saving a large file, it is quite useful if the software could calculate not only average bitrate but also expected final file size using the currently written data size or even the average bitrate during the time the encoding was in progress. It happens too often that some Rate Factor setting that was tested on a short 10-20 seconds footage gives acceptable bitrate, but when it comes to encoding the whole video, the bitrate may increase drastically at some moments. Suppose the file size between 1-2 Gigs can satisfy me, but if I see in the middle of the encoding that the projected file size is going to be above 3 gigs, I'd rather stop the encoding and tweak some settings instead of waiting 3-4 hours only to find out that the file that was finally created is too large and I don't need it. So, knowing what the final file size is expected to be can save a lot of time because the user can stop the encoding if he sees that the file is going to be larger than he expected.
18
Windows / Re: direct audio copy with m2ts files?
« Last post by mean on February 24, 2017, 06:52:52 AM »
It should work
19
Main version 2.6 / Re: Can't install Nvidia libraries and compilation problems
« Last post by Jan Gruuthuse on February 24, 2017, 05:25:19 AM »
MAke sure you have qt5 packages installed
 qttools5-dev-tools qtbase5-dev libqt5opengl5-dev
Check if these are installed:
Code: [Select]
dpkg -l qttools5-dev-tools qtbase5-dev libqt5opengl5-dev
Quote
ii  libqt5opengl5-dev:amd64        5.5.1+dfsg-16ubuntu7 amd64                Qt 5 OpenGL library development files
ii  qtbase5-dev:amd64              5.5.1+dfsg-16ubuntu7 amd64                Qt 5 base development files
ii  qttools5-dev-tools             5.5.1-3build1        amd64                Qt 5 development tools
If not all 3 showing ii
Please do (re)install:
Code: [Select]
sudo apt-get update && sudo apt-get install qttools5-dev-tools qtbase5-dev libqt5opengl5-dev
ps:
- click on [Select] form Code: [Select]
- the code section is now marked (selected)
- right mouse click on selection and select copy in pop-up menu
- in Terminal window right mouse click and select paste, press enter
- the commands should be executed
just in case, ...
20
Main version 2.6 / Encoder Settings for DVD Output
« Last post by Tojo4158 on February 24, 2017, 03:57:32 AM »
I've been trying to transcode some videos (MP4 with H.264/AVC codec) to DVD and keep ending up with resultant videos that have momentary choppiness throughout the video during DVD playback and in some cases have more serious drop outs for a half second or so.

My process has been to use Avidemux to cut and transcode to a compliant mpg file and then use DVD Styler in a copy mode to author the DVD without further transcoding.  However, I'm not sure I'm getting compliant mpg files from Avidemux.

Given the issue at hand, I've focused mostly on bit rate assuming it might be too high for DVD playback.  Sure enough, the MPEG Validator tool indicates that I have a non-compliant mpg file and that one of the issues is the peak bit rate of 11.8 Mpbs vs a max allowable of 9.8 Mbps for DVD.  The tool gives me the timecode of the peak which corresponds to one of the "serious" drops in the video/audio playback.  But there are other smaller "jitters" in the playback throughout. 

What I can't understand is why I have a peak of 11.8 Mbps.  I'm using the following settings to attempt to get the highest quality compliant DVD video I can.

Video output Mpeg2 (ff)
    Widescreen aspect ratio
    Two Pass Avg Bitrate
    6000 kbps
    224 VBV Buffer
    2 B Frames
    15 GOP
    8000 kbps Max Bitrate
    Progressive
    Rate distortion macro block detection
    1 Min Quant
    6 Max Quant
    2 Max Quant Diff
    No Trellis quant
    2000 kb filesize tolerance
    0.7 Quant compression
    0.7 Quant blur
Filters
    swResize 720x480
    Resample 29.97 NTSC

Audio settings AC3 (lav):
    128 kbps

Output Format Mpeg-PS Muxer (ff):
    Muxing Format DVD


Does the encoding process completely ignore the Max Bitrate field, or what could cause the output to go above the value listed in this setting? 

Any other advice that can be given to help create a compliant file with the highest reasonable quality (reasonable, meaning the output is at least close to fitting on a 4.7GB DVD-R).

Thanks
Pages: 1 [2] 3 4 ... 10