Recent Posts

Pages: 1 ... 8 9 [10]
91
Main version 2.6 / Re: h265
« Last post by eumagga0x2a on February 20, 2017, 08:27:31 AM »
Avidemux [...] crashes with a floating point exception (division by zero in avidemux_core/ADM_coreUtils/src/ADM_infoExtractorH265.cpp:224) loading a real-life DVB-T2 sample ("Das Erste HD" from http://forum.kodi.tv/showthread.php?tid=228769&pid=2333904#pid2333904).

This is fixed by [h265 extractor] be resilient to missing timeframe info in sps, thanks!

Gtx 960 does support hdr (10-bit) [...]

It is nvidia driver in relation to vdpau that doesn't for now.

You are right, my bad. GTX 960 is feature set F, I've confused it with GTX 980 which is only feature set E.
92
Main version 2.6 / avidemux Cli/Qt5 2.6.18 64-bit deb download ubuntu 16.04.2 LTS
« Last post by Jan Gruuthuse on February 20, 2017, 08:11:43 AM »
ec18ae8           [dxva] Try to see if refresh can work (euma)
ubuntu 16.04.2 64 bit x86 SMP  QT5, x265 version 1.9: avidemux 2.6.18 170220-64bit Xenial with x265 version 1.9
93
Main version 2.6 / Re: Bugs report + suggestions
« Last post by eumagga0x2a on February 20, 2017, 07:47:40 AM »
Previous Avidemux versions required to type the name of the file in the "Save as" window and it was really annoying when dealing with many videos. The latest version offers the original file name in the "Save as" window but still there's something unpredictable happening with the folder where the output file is saved. As far as I understand it is the last used folder or the parent folder if the last one doesn't exist anymore or even the "Avidemux" program folder in some cases.

It would be interesting to investigate in which situations exactly the program directory gets automatically chosen. This is definitely not right, but regardless that the other behaviour matches my workflow (source and target are located always on different HDDs), I think that it should be this way. Avidemux will suggest the source folder as target if the lastdir_write preference is empty, which is currently questionable, because this facilitates overwriting the source video (you do get a prompt, but still).

Quote
This is quite confusing because when I save project-A in folder-A, close it, open project-B in folder-B, I expect the output file to be saved in folder-B

Source dir = target dir is actually a really bad practice when editing video files located on rotating storage devices, less so for SSD, of course.

Quote
I thought it would be useful if the user could specify what folder should be used as default output folder in the Avidemux settings. There can be several options such as:
* the last folder that was used for saving,
* the folder of the source video,

The latter would at least require implementing automatic renaming.

Quote
* the folder specified below
   [ c:\blablavla  ]

This should be covered by the current default behaviour once a video has been saved and is not needed IMHO. In general you are free to delete lines 51 and 52

Code: [Select]
    admCoreUtils::getLastWriteFolder(lastFolder);
        if(!lastFolder.size())

from avidemux/qt4/ADM_userInterfaces/ADM_gui/file_qt4.cpp and build Avidemux from source to make Avidemux always suggest the source directory as target (you do need Linux to accomplish this).

Quote
And do you know anything about wrong colors when opening an AVI file? For example, when I export an uncompressed AVI from Adobe Premiere, they play well in players, but when I open it in Avidemux, it shows the blueish colors instead of the normal colors.

Please provide a sample or at least the MediaInfo output for the file in question.
94
Main version 2.6 / Re: Bugs report + suggestions
« Last post by Jan Gruuthuse on February 20, 2017, 05:51:41 AM »
The source/creation process uses another colour plane. Switching this at start would help.
http://avidemux.org/smif/index.php/topic,16572.0.html
Technical info (developers, ....)
https://msdn.microsoft.com/en-us/library/windows/desktop/dd206750(v=vs.85).aspx

Beyond my basic user capabilities.
95
Main version 2.6 / Re: New to Avidemux
« Last post by Jan Gruuthuse on February 20, 2017, 05:18:47 AM »
96
Main version 2.6 / Re: Bugs report + suggestions
« Last post by acritum on February 20, 2017, 05:18:21 AM »
Thank you for the explanation. Luckily, Avidemux became more convenient than it was 2-3 years ago, so I think it's time to say good-bye to Free Video Editor. I liked it for fast cutting and one-click saving files (it adds "_cut" to the end of the original file name and saves it to the same folder with one click). Previous Avidemux versions required to type the name of the file in the "Save as" window and it was really annoying when dealing with many videos. The latest version offers the original file name in the "Save as" window but still there's something unpredictable happening with the folder where the output file is saved. As far as I understand it is the last used folder or the parent folder if the last one doesn't exist anymore or even the "Avidemux" program folder in some cases. This is quite confusing because when I save project-A in folder-A, close it, open project-B in folder-B, I expect the output file to be saved in folder-B, but instead of it, it is saved in folder-A. Of course, I can check the folder before saving the file and change it to folder-B, but when the folder names are typical such as 20161030_165422, the eyes get tired and sometimes I don't notice that the folder needs to be changed and the output file is saved to the folder of the previous source/output video (folder-A) and when the encoding is done and I can't see it in the folder-B with the source file, I need to look through many folders with previous projects to find it. Although I understand that saving many files from different locations to a single output folder is sometimes useful, but in the cases like the one I described above, it leads to much confusion. So I thought it would be useful if the user could specify what folder should be used as default output folder in the Avidemux settings. There can be several options such as:
* the last folder that was used for saving,
* the folder of the source video,
* the folder specified below
   [ c:\blablavla  ]

This simple patch can noticeably increase the speed and ease of work when dealing with many projects/files.


And do you know anything about wrong colors when opening an AVI file? For example, when I export an uncompressed AVI from Adobe Premiere, they play well in players, but when I open it in Avidemux, it shows the blueish colors instead of the normal colors. I found a solution in forums, by adding "Swap UV" filter, but this is not very convenient because it requires video recompression (and I like Avidemux for being able to copy the streams quickly). Is this problem known and are there any plans to fix it?
97
Main version 2.6 / Re: h265
« Last post by Jan Gruuthuse on February 20, 2017, 05:13:41 AM »
Gtx 960 does support hdr (10-bit)
https://developer.nvidia.com/getting-know-new-hdr
https://uk.hardware.info/reviews/5890/2/test-the-geforce-gtx-960-is-the-best-htpc-gpu-of-this-moment-h265-on-the-gtx-960-innpractice

It is nvidia driver in relation to vdpau that doesn't for now.
The topic is only h265, (codec, used both ways: (de/en)coding
98
Good  :) I wonder if explicitly calling the interpreter (bash) made the difference.

Command line :
bash bootStrap.bash --deb --with-core --with-cli --with-plugins

There is no need to use any of the --with- options above because they are the default, just

Code: [Select]
bash bootStrap.bash --deb --rebuild
("--rebuild" will try to preserve existing build directories). If you install liba52-0.7.4-dev, libmp4v2-dev, libass-dev and libmad0-dev, you could shave a few MiB off the size of the Avidemux binaries adding the options --with-system-libass --with-system-liba52 --with-system-libmad --with-system-libmp4v2 to the bootStrap.bash command line.
99
Main version 2.6 / Re: New to Avidemux
« Last post by Wachtman43 on February 20, 2017, 12:21:10 AM »
Thanks, folks.  I do respect copyrights and copy-protected material; however, my particular use involves some extenuating circumstances requiring occasional, personal use clips not readily available through the publisher.  Much obliged for your assistance.
Forgive me for imposing on you one more time.
I got the DVD files (VOBs) decrypted and on hard drive, and I can open them with Avidemux and define an A/B clip, but I have no idea what video, audio, and output format parameters to set.  Default parameters are "copy", "copy", and "AVI Muxer" respectively, which builds a file, but it won't import to my Sony Vegas editor.  By randomly selecting different values for these parameters, I find that some combinations will not convert, while others do result in a converted file, but so far not one which will import into my Sony Vegas editor.  Any ideas or recommendations? 
100
Main version 2.6 / Re: Can't install Nvidia libraries and compilation problems
« Last post by PhilB on February 19, 2017, 11:42:51 PM »
Thank you for your interest.

Here what I did :
Reboot the computer, delete the directory, create a new one /home/jon/avidemux2. extract the latest git inside it (the stable version would be fine too).
Command line :
bash bootStrap.bash --deb --with-core --with-cli --with-plugins.
After less than 5 minutes, I got the following message :
** ALL DONE **
** The installable packages are in the debs folder **

I now have 10 DEB files in this directory. Success !  :D
Pages: 1 ... 8 9 [10]