What container ? Sometimes a certain container causes problems in some TV models. If MP4 try remuxing to MKV or vice-versa
Also, officially it's the SAR (sample aspect ratio) flag when using h264 . PAR has been renamed to SAR in mpeg4-avc terminology
Did you set SAR only, or did you mess with container AR signalling ? Sometimes having both types of information at the same time can cause conflicting problems
On the other hand, certain players (hardware or software) might have preference where container AR signal overrides video stream AR signal or vice versa . But in general, stream signalling is best because if you remux, that info is retained
+ Reply to Thread
Results 181 to 210 of 318
working with these kind of videos, this noisy madness, you just denoise it first before posting on YouTube, you can use NeatVideo or whatever you have, you do it in NLE, I use Vegas, btw. SD resolution Neat Video I got it a time ago, it was cheaper than HD version. It is sort of must, if you do not want to fiddle manually elsewhere (VD, Avisynth, Vapoursynth) and for deinterlacing as a bonus using QTGMC, crop to 704x576, mask broken lines top and bottom. Then upscale to 1280x960 or any other 4:3.
if you feel video is too "plasticky" after denoise, just reduce denoising for Y channel, 50%, not 65% or whatever you feel. This is after denoise, QTGMC, crop and addBorders(masking lines), just before 4:3 resize, still in in 704x576, 50fps:
Upsizing PAL to 768 is equally a bad idea. 720x540 is much better, almost 1:1 to the x576, the loss of 36 pixels is meaningless. While adding 44 can create problems.
In general, adding/reducing horizontal pixels is fine. Adding/reducing the vertical starts to screw with source resolution, aliasing, and interlace (even when deinterlaced). Best avoided when possible. SD>HD (for documentaries) has challenges, one of the few valid reasons for upscaling content.
As to upscaling, I would thing that upscaling by a ratio other than 2, 3, etc., would worsen the file even more, so I keep the original 576p inside a 960x720p frame, with a 72-pixel black border up and down, and a 96-pixel black border on left and right sides.
PS: That pretty good quality what you got there, though I encode my MP4s/H.264 at 6000 Kbps - 8000 Kbps and you only used 2800 Kbps. Now, I don't understand why 704 x 576 if the DV source was 720. I also don't like much 50fps, since the vertical resolution of each frame is just 288 times 2 (and the image wiggles a little). I cannot see how any software can invent 288 horizontal lines if it's not by duplicating them, so for that I'd rather blend the two fields.
Also, if dealing with 24fps film (not the case) converting it to 50fps or 60fps is just killing it -- it horribly looks like video.
Last edited by celsoac; 21st Apr 2019 at 14:29.
for that dv sample in Vapoursynth I used: clip = core.std.SeparateFields(clip)
to see if there are fields, and it was there, so I used QTGMC, sure if it is not interlaced footage you'd not deinterlace. I know it could be kind of a bit disturbing for our brain, it kind of makes no sense , it is "super fluid" but crappy video with no resolution, ..... you video, your choice.
True 4:3 is within 704x576, not 720x576. Footage as you provided most likely. Those black borders are a giveaway, there is something even on top and bottom, so footage might be even slightly zoomed in, whatever broadcasters did, but those black borders left and right are more than 16 which I did not crop entirely, just total 16, so AR is more likely closer to the original if you cut 16 total from left and right and resize to 4:3
when noise is gone, bitrate goes drastically down,
Do you guys typically crop off the bottom to get rid of the lines on vhs captures if final destination is TV? I don’t know if new TVs still have overscan or to what degree but my files still show the lines on my tv. If so how do you handle with regards to DAR SAR etc .. to keep things at standard resolution?
Lordsmurf- regarding the 640x480 1:1 from DV, is that the best option to keep things universal to work on all players? (Especially when talking about an entire collection of videos, not just one or two.) Any drawbacks? The tv stretching the 720x480 ignoring the flag wasn’t even all that bad and I was also wondering if anyone finds the slight stretching due to “stupid” TVs at all acceptable these days or even noticeable from an untrained eye. Anyone that does this professionally for clients who want final files on a hard drive, what is the norm when you don’t know what they will be played on?
I don’t know if new TVs still have overscan or to what degree but my files still show the lines on my tv.
Lordsmurf- regarding the 640x480 1:1 from DV, is that the best option to keep things universal to work on all players?
anyone finds the slight stretching due to “stupid” TVs at all acceptable these days or even noticeable from an untrained eye. Anyone that does this professionally for clients who want final files on a hard drive, what is the norm when you don’t know what they will be played on?
Always keep master archives, best quality, encode copies in lower quality.
But you still have massive timing issues to worry about. You encodes are literally about 10% of the true quality that can be gotten from a VHS tape. All it takes is quality hardware and methodology. You can do it, too! But you have to listen to us, not argue. You may not be a professional, or even serious hobbyist, but some of us are. But it does take some time and funds.
QuickTime and save it again (no recoding, just change of container). Yet one more step, then. If anybody knows how to make Avidemux open DV directly, thanks.
QTGMC is available under mac using vapoursynth, but the learning curve is steep, more so than avisynth
I think selur's hybrid might be an option as a GUI (mac/linux/pc versions) . I think the windows version can run both avs/vpy variants, I think the mac version has the vpy variant (not sure)
I took my portable Hard drive to someone else’s house today to test how my mp4s play (quality, aspect ratio etc) and on one TV (Samsung, a few years old) the media player on the TV didn’t recognize the device and the other Tv didn’t even have a USB port. I have one of those media player devices that plugs into TV with HDMI (the hard drive plugs into the device), but I forgot the remote so I couldn’t try.
This is probably a question for another thread but since I feel like I know you all by now, might as well ask... what is a good method to save/store/share a collection of converted home videos between family members that will work across devices? Are people still using DVDs?
I believe I formatted my drive NTFS and it’s a western digital elements 2TB, figured this would be the most universally friendly option.
Last edited by Christina; 21st Apr 2019 at 20:21. Reason: Brain fart. Corrected “NTSC” to “NTFS”
That Hybrid is a good tip for Mac. It designs a script for you and also under its hood deals with audio and muxes it for you. Vapoursynth does not handle audio like Avisynth does.
Vapoursynth script I used to get that 704x576 mkv from 720x576 1-Test.dv:
import vapoursynth as vs from vapoursynth import core import havsfunc clip = core.ffms2.Source(1-Test.dv) clip = core.std.SetFrameProp(clip, prop="_FieldBased", intval=1) #intval=1 for bff clip = havsfunc.QTGMC(clip, Preset='Slower', TFF=False) clip = core.std.Crop(clip, left=4 , right=12, top=4, bottom=4) clip = core.std.AddBorders(clip, left=0 , right=0, top=4, bottom=4) clip.set_output()
NTSC is not a filesystem that you format, it's a a Tv format/spec that you design/encode for. I think what you meant was NTFS. That may be better performance-wise for you individually, but it is not the most cross-platform, common denominator. That would be FAT/FAT32. On devices like tvs, even exFAT is more common. Remember, NTFS is proprietary to Microsoft.
If you plan to share files, it is best to be aware of the various devices' limitations beforehand so you can either come with a mutually-acceptable, common denominator set of formats, or you break it up into multiple groups of formats where one works optimally on players A,B,C and another works optimally on C,D,E.
That is one good reason for continuing to use formats like DVD, Bluray - they are meant to be universally acceptable for their players. I wrote about this very thing a few years back when I mentioned how it would be a bit "Wild West" for many "general media" file players.
Last edited by Cornucopia; 21st Apr 2019 at 18:17.
Haha.. oops. Yes, of course I meant NTFS!! Multitasking during Easter festivities at its finest.
Ok, thank you. I will confirm which format I used when I’m back in front of computer.
I figured DVDs were sort of becoming a thing of the past and I’m surprised there aren’t more devices on the market for sharing personal media - I guess everything these days is YouTube, smart phones, and social media for a lot of people.
This is what I bought to try out, which takes the guesswork out but I swear it does something to the quality on playback.
Micca MPLAY-HD Mini 1080P Full-HD Digital Media Player for USB Drives and SD Cards https://www.amazon.com/dp/B074DKYT74/ref=cm_sw_r_cp_api_i_.zrVCb0Q9XP6B
Last edited by Christina; 21st Apr 2019 at 20:34.
Don't know the specs or ruggedness or quality, but it does look like a cute little player. Too bad you didn't have the remote as that probably would have been a good solution.
Thank you. I've installed Hybrid and Vapoursynth in my Mac (Mojave). Yes, the QTGMC plugin in Hybrid promises, and Hybrid itself, though cumbersone for a GUI-oriented person like me , looks great. I can see the output in the Preview window. However, it does not output video, due perhaps to a python error? Since I know close to nothing about scripts, python, and the like (I manage well with on-line commands from old-times when I started computing with UNIX!), could someone please give me a hand for fixing this? Below is the script and the error message. Thanks!
import vapoursynth as vs
core = vs.get_core()
# Import scripts folder
scriptPath = '/Applications/VÍDEO/Hybrid.app/Contents/MacOS/vsscripts'
# Import scripts
# Loading /Users/xxxx/xxxPathHiddenxxx/1-Test.dv using LWLibavSource
clip = core.lsmas.LWLibavSource(source="/Users/xxxx/xxxPathHiddenxxx/1-Test.dv", format="YUV420P8", cache=0)
# making sure input color matrix is set as unspec
clip = core.resize.Point(clip, matrix_in_s="unspec",range_s="limited")
# making sure frame rate is set to 25/1
clip = core.std.AssumeFPS(clip, fpsnum=25, fpsden=1)
# Setting color range to TV (limited) range.
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)
# setting field order to what QTGMC should assume
clip = core.std.SetFrameProp(clip=clip, prop="_FieldBased", intval=1)
# Deinterlacing using QTGMC
clip = havsfunc.QTGMC(Input=clip, Preset="Slow", TFF=False)
# adjusting output color from: YUV420P8 to YUV422P10 for ProResModel (i422)
clip = core.resize.Bicubic(clip=clip, format=vs.YUV422P10, range_s="limited")
Failed to evaluate the script:
Python exception: No attribute with the name lsmas exists. Did you mistype a plugin namespace?
Traceback (most recent call last):
File "src/cython/vapoursynth.pyx", line 1927, in vapoursynth.vpy_evaluateScript
File "src/cython/vapoursynth.pyx", line 1928, in vapoursynth.vpy_evaluateScript
File "/Users/xxxx/xxxPathHiddenxxx/tempPreviewVapoursynthFile16_35_23_268.vpy", line 12, in <module>
clip = core.lsmas.LWLibavSource(source="/Users/xxxx/xxxPathHiddenxxx/1-Test.dv", format="YUV420P8", cache=0)
File "src/cython/vapoursynth.pyx", line 1522, in vapoursynth.Core.__getattr__
AttributeError: No attribute with the name lsmas exists. Did you mistype a plugin namespace?
It means you didn't load the lsmash .dll dependency
In vapourysnth it's "vslsmashsource.dll"
I suspect it should be somewhere in the hybrid install directory
It might be a bit different on a mac, but in windows you load it like this, and the lsmas namespace is built into the .dll
For example, there are some newer 2019 builds here. (But DV is very old, nothing has probably changed in the last 20 years, so you don't need the latest and greatest)
Alternatively , you can use ffms2 to load the .dv clip (and I suspect hybrid has that .dll bundled somewhere too as "ffms2.dll" )
Hybrid for Mac still gives errors with QTGMC (not with other deinterlacers), either lsmas not found, or fmtc not found. Any help with QTGMC for Hybrid - MacOS would be greatly appreciated.
One thing I haven't done is try different versions of lsmash. I installed it fine, though, automatically, with > brew install l-smash , so it should have installed the right version for my OS.
Did you check this thread ?
Selur actually posted there with mediafire links , but he said he'd update hybrid, so they should be bundled
You should probably start another thread ; Selur (hybrid's author) probably won't look in this thread . Either post on selur's forum, or start another thread here, or one at doom9 (either in the vapoursynth or encoder gui subforums)
You can replace lsmash with ffms2 , and fmtc with resize (zimg / zlib) for functional equivalents
But those error messages are vapoursynth plugin issues, not necessarily hybrid the GUI issues . You're not loading or it's not finding the libraries
Hybrid for Mac. I'll try it, though.
Ffms2 doesn't load, either. Hybrid gives you the option of activating Vapoursynth preferences (see capture). None works.
[Attachment 48774 - Click to enlarge]
[Attachment 48776 - Click to enlarge]
Just ignore my posts, ok?
Maybe he wanted it more streamline instead of everything spelled out and cluttered?
selur is active on several forums, you can provide feedback on the GUI if you want things changed
quit hijacking the thread
Or use the arrow to the right.
Software has a learning curve. It'll take a good bit of time to fully understand Hybrid options. But it's worth it. And again, as a GUI, far easier than manual Avisynth or Vapoursynth usage.
I also suggest you stop being an ass to people who are trying to help you.
And perhaps open a new thread, as it is threadjacking. You're actually the interloper here, requesting help that is off-topic to the original topic, and you're not the original poster (not your thread).
Oh, and MacOS does NOT work that differently WRT libraries/dlls and symbolic links. Especially as it is a form of BSD unixlike. Once you know your way around, they translate pretty straightforwardly.