Quantcast
Channel: Doom9's Forum
Viewing all 52943 articles
Browse latest View live

BD Rebuilder Beta - Bug Reports Only

$
0
0
Quote:

Originally Posted by Mark_Venture (Post 1914869)
Just jumping in late on the NVENC/CUDA discussion...
Having GPU Accelerated encoding would be a plus, I can certainly understand why some want it. But I'm fine without it if BD-RB keeps working as well as it does!


I also was interested in GPU Accelerated encoding, but when JDobbs and other explained that there are fewer "quality" settings, compared to sw encoding, and the "best quality" BD-RB software settings gives a better final video, I am no longer interested in GPU Accelerated encoding.

I have two unused, older i7 pc's, attached to a KVM switch, and let BD-RB crank away at the highest possible settings making MKV files. So it takes 3 days or longer to make 1 MKV file using x265. The results are great, and "my" computer is left to do other things.

Now if they ever come out with GPU Accelerated encoding that offered "insane" High Quality video settings, I might be interested, but that might cost several hundred dollars for a video card, I probably would not be in a huge rush to buy such a graphics card, to get the same results I get now, with just waiting several days. Thanks everyone and JDobbs for explaing this!

VapourSynth Editor

$
0
0
I made a test build implementing a zoomable timeline, test it out here and give feedback. Ctrl + mouse wheel for zooming, zoom on current frame pointer. The basic skeleton should be done and I need feedback on the navigation experience. And don't mind the ugly color.

Media Player Classic - BE Win32/x64

$
0
0
Sorry, I misinterpreted the fact that HC is not showing the path of the used DVD Navigator as it is using dslibdvdnav but it does use the same OS version as BE does. So please forget that.
Thanks for all the hard work !

eac3to - audio conversion tool

Down Sizing ATMOS or TrueHD 7.1

$
0
0
Thanks tebasuna51, on your recommendation to use MeGUI or BeHappy to recode to AC3 5.1. I will have to try it. I have even been attempting to extract each channel to wav and then use SoundForge to create 5.1 output, but that creates a file that BD Rebuilder doesn't like to recognize. Plus it is a time consuming process when I can just use CloneBD and it will create 5.1 @640 from somewhere, lol.

Thanks again, tebasuna51! :thanks:

MKVToolNix v47.0.0 released

$
0
0
For batch muxing in staxrip you would:

-Disable indexing by installing LAV Filter and set source filter to DSS2.
-Select Copy/Mux video encoding profile.
-Select Copy/Mux audio profile.

MPC-HC v1.9.4

$
0
0
Quote:

Originally Posted by clsid (Post 1915218)
Use dx9 rendering in MPCVR and DXVA2 native decoding.

done, thank you all for reply. :D

Does Windows Media Encoder work on Windows 10?

$
0
0
Yeah. And the industry still hasn't caught up with Silverlight Enhanced Movies with their Blu-ray caliber extras and navigation.

I recall we did some good things with UX for accessibility using sideband XML for subtitles.

D2V Witch: cross-platform D2V creator

$
0
0
Thanks for the new version.

I confirm that PATH loading works and I've modified staxrip accordingly.

VirtualDub2

$
0
0
Are there any known issue for Windows 10 Version 2004 (Version 19041.329) when Capturing AVI? I have.

Today I wanted capture some AVI with my Dazzle DV100 (DirectShow) with VirtualDub. But instead to get my fluid and clean result as usually, the video is choppy and audio distorted.

To show you, I recorded a short clip (little compressed) and uploaded here: https://www.dropbox.com/s/ycn7ce9fyw...issue.zip?dl=1

I have also put my VirtualDub Settings into it.


Luckily, I have some other hard drive with Windows 10 Version 1809 (Build 17763.1039) on it.

So: Same hardware, same grabber, same player, same settings, same VirtualDub2 version -> no problem at all. The result is clean.

Now, to verify, it's 'not NVIDIA again', I took my older Laptop with integrated Intel HD graphics on it, also Windows 10 Version 2004 (Version 19041.329).
The result is again choppy and audio distorted.
And of course to verify, it's not my player, I checked my Nintendo N64 on my grabber, but the result is the same.

The choppy video and distorted audio is already in the Preview, not just the output file.

So it comes down, the only difference I notice between fine and distorted result is the Windows version.
What can I do and try now?

VirtualDub2 is build 44282

BD Rebuilder Beta - Bug Reports Only

$
0
0
Let me correct myself. CRF is disabled with X264's internal LAVF, but ABR is still an option. Since quicker-encode seems to use a CRF value, I would think a different decoder is needed.
I'd just like to know if that's a bug or a feature with force_noencode & quicker encode.

As far as your issue AmigaFuture... dude, I have no idea what you are even trying to do anymore. I figured you were capping OTA content. Since it's Comcast, I have to assume it's not QAM, and by MPEG-4, I'll assume you mean AVC video.

I don't know of a way to clean possible broadcast or encoding bugs under those conditions. I'm not sure there is. It could be a bug in the software you are using to cut the commercials.

TSM2UHD Discussion and Bug Reporting

$
0
0
Quote:

Originally Posted by SeeMoreDigital (Post 1914929)
Currently, all 'transport' muxing applications require Dolby TrueHD audio streams to also contain an embedded Dolby Digital core (ie: two streams in one).

Just to add... that they do it for good reason. It violates the BD standard if there isn't a DD core included.

TDeint and TIVTC

$
0
0
Japanese broadcast is often kind of messy like this. Look into JIVTC, which is much slower and harder to use but designed specifically around this problem.

ffmpeg weird output

$
0
0
Have a look at this mess.
https://imgur.com/a/KFElvLC

Have you ever seen such weird output? Original file is playing fine. If I use handbrake there are no issues as well. This is actually the first time anything like this happens.
For Background information: I use jellyfin (open source plex/emby).
This is the command line which I got from the logs
Code:

-map 0:0 -map 0:3 -map -0:s -codec:v:0 h264_nvenc -force_key_frames "expr:gte(t,n_forced*5)" -copyts -avoid_negative_ts disabled -start_at_zero -pix_fmt yuv420p -preset default -b:v 49360000 -maxrate 49360000 -bufsize 98720000 -profile:v high -vsync -1 -map_metadata -1 -map_chapters -1 -threads 0 -codec:a:0 ac3 -ac 6 -ab 384000  -y
Let me know what other (mediainfo?) information you need.
Huge thanks in advance :)

VapourSynth Installer, Applications, & Plugins for macOS


MeGUI: General Questions and Troubleshooting Thread

$
0
0
Quote:

Originally Posted by Lord Dredd (Post 1915175)
yes and I gotta say I found to be most vibrant , the first three sounded alright the was also great but the other one had beefed up audio volumes so to me that sounded well.

I am not an expert and and I listened to them on my desktop speaker which is okish

Two of the samples were just a straight downmix (no compression) and there's one with very mild compression via Avisynth. The main difference between the two DAN samples is the speed at which it reacts to volume changes. My settings (f=150 b=1) react quite quickly, whereas the other settings (f=2000 g=23 m=15 b=1) are much slower. Both have advantages and disadvantages.

The DAN uses a kind of "window" for determining and adjusting the volume. If you compare the two samples, my settings keep the speech at much the same level throughout and the loud parts shouldn't be any louder than for a normal downmix.
For the other sample, the speech is louder at the beginning, but there's a section just before the first explosion where the volume of the speech starts to fade away, then the first explosion is probably a little louder than it was originally. I'm pretty sure that's due to the larger "window" it uses to determine volume.

The disadvantage of it reacting quickly is it can cause "volume pumping" on occasion....
Imagine a section of audio that's mostly normal speech with some light traffic noise in the background. In between people talking, where there's mostly silence, the volume of the background traffic can increase noticeably, then drop back down to a quieter level while someone talks, then get louder again where there's silence. That's the type of "volume pumping" I'm referring to.
If you use a TV with it's audio set to "night mode" there's a good chance you'll hear volume pumping for days, or just as bad, it'll sound like someone turned the volume down during a loud part, and they're slowly turning it up again while it's quiet.

Anyway.... the settings I use are what I found to give good compression, without noticeable volume pumping 99% of the time, and without being able to hear the volume being slowly adjusted to prevent volume pumping.... but it's all personal preference.

Quote:

Originally Posted by Lord Dredd (Post 1915175)
strangely similar avisynth for a x264 video works well but when used with x265 cools the color off..
any tick you might wanna suggest to keep the colors as close to trhe original as possible.

I can't think why x264 and x265 should look different when all else is equal, unless it's a playback issue. Someone else may have a better idea as I never use x265.

By the way, I know MeGUI automatically adds frame rate conversion to the script for ffms2, but don't use it unless the source is variable frame rate and you want to convert to a constant frame rate, in which case MeGUI will probably pick the wrong frame rate to convert to anyway.
Even if the specified frame rate is exactly the same as the source frame rate (in which case it should do nothing) it can still, on occasion, cause frames to be dropped and duplicated when they don't need to be and make the encode look "jittery". I'm talking about this:
fpsnum=24000, fpsden=1001
Unless you're converting the frame rate, delete it from the script.

FranceBB LUT Collection

$
0
0
Ok, so I made a few tests.
I started with the PAL version of BT601 as you can see:


The curve is exactly the same and there's a reason: the difference between those two is so subtle that it can't really be noticed on this scale...

To test this, I indexed a BT709 file and I converted it to BT601 in three different ways:

1st Indexing only (my source file):

Code:

FFVideoSource("I:\temp\sample.ts")
Spline64Resize(848, 480)

2nd my LUT:

Code:

FFVideoSource("I:\temp\sample.ts")
Spline64Resize(848, 480)
ConvertBits(16)
ConvertToPlanarRGB()
Cube("C:\Programmi\AviSynth+\LUTs\test.cube", fullrange=true)

3rd the old good colormatrix:

Code:

FFVideoSource("I:\temp\sample.ts")
Spline64Resize(848, 480)
ColorMatrix(mode="Rec.709->Rec.601", interlaced=false, threads=0, thrdmthd=0)

4th Matrix from HDR Core:

Code:

FFVideoSource("I:\temp\sample.ts")
Spline64Resize(848, 480)
ConvertBits(16)
ConvertToDoubleWidth()
Matrix(from=709, to=601, rg=1.0, gg=1.0, bg=1.0, a=16, b=235, ao=16, bo=235, bitdepth=16)
ConvertFromDoubleWidth()

This is the original frame in Linear BT709:


This is the result of my linear Transformation:


This is ColorMatrix:


This is Matrix from HDR Core:


A few frame-comparison, but honestly the difference is so small that it's barely noticeable:












Could you test it, please, and let me know?


Link: FranceBB LUT


This one instead is made by Adam Stanislav and his results are pretty much the same as mine with very little difference. Can you check this one as well, please?
Link: Stanislav LUT

clever FFmpeg-GUI, a new small GUI for FFmpeg

$
0
0
The first screen is High DPI enabled, opening a source file throws an exception shown by .NET Framework exception dialog and that dialog is unusable at 288 DPI, so I cannot post the stack trace.

SORTED :) Windows 7 Pro Sux big time.

MKVToolNix v47.0.0 released

$
0
0
Quote:

Originally Posted by Boulder (Post 1915286)
My method for batch muxing of entire seasons is

Sometimes I have replace audio and subs from external sources. There is where real fun starts. :p
Viewing all 52943 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>