VideoHelp Forum
+ Reply to Thread
Page 2 of 3
FirstFirst 1 2 3 LastLast
Results 31 to 60 of 71
Thread
  1. Be careful. h.264 will usually use YUV 4:2:0 chroma subsampling. If your source is RGB or YUV 4:2:2 conversion to 4:2:0 will not be lossless. Also, many programs convert interlaced sources to 4:2:0 incorrectly, blending the colors of the two fields together. And if your source is interlaced you want to encode interlaced. Handbrake doesn't directly support interlaced h.264 encoding. You have to use the "extra options" box to force interlaced encoding.
    Quote Quote  
  2. So how do I tell it to stick with 4:2:2? Also, if I need to export lossless H.264 after editing in Premiere, at what bit rate is it lossless? It will let me export up to 300Mbps, which seems too high.
    Quote Quote  
  3. Member DB83's Avatar
    Join Date
    Jul 2007
    Location
    United Kingdom
    Search Comp PM
    There really seems to be an issue with your system if the nle does not import/deal with even basic formats correctly.
    Quote Quote  
  4. I don't know what that issue could be. I would like to use H.264 at this point since it works. I just need a way to capture lossless H.264 with VirtualDub.
    Quote Quote  
  5. You can use x264vfw in VirtualDub. But VirtualDub does not handle interlaced YV12 properly. And AVI is often problematic for h.264.
    Quote Quote  
  6. You can use x264vfw in VirtualDub. But VirtualDub does not handle interlaced YV12 properly. And AVI is often problematic for h.264.
    That won't seem to work.

    "Couldn't find compatible format.
    Possible reasons:
    * Codec may only support YUV
    * Codec might be locked.
    * Codec might be decompression-only"
    Quote Quote  
  7. Now I just tried UT codec. Same problem. The audio is only about a minute long, even after waiting for the conform progress bar to finish in Premiere.
    Quote Quote  
  8. Member
    Join Date
    May 2014
    Location
    Memphis TN, US
    Search PM
    You definitely have a problem with Premiere Pro and standard codecs. There's nothing weird about huffyuv, Lagarith, UT codec, etc. They're used everywhere. You don't by any chance have some oddball codec pack installed such as K-Lite, do you?
    - My sister Ann's brother
    Quote Quote  
  9. You don't by any chance have some oddball codec pack installed such as K-Lite, do you?
    No, I just use VLC. I also have Windows 10 installed, but I am not sure if that is causing the problem.

    Anyway, I might drop Premiere Pro. I am testing Sony Vegas right now, and it doesn't seem to have these issues. I was able to import lossless files effortlessly. Also, I checked the waveform monitor and it is not crushing the whites and the blacks.

    Click image for larger version

Name:	Capture.PNG
Views:	145
Size:	57.5 KB
ID:	33352
    Quote Quote  
  10. It looks to me like it is crushing the blacks. You've got a ton at -9 IRE. That's what the numbers represent, isn't it? When you see them piled up like that, it's not a good sign.
    Quote Quote  
  11. There is a lot of black in the image, along with a lot of flashing gray dots. It's TV antenna noise or whatever it's called.
    Quote Quote  
  12. Member
    Join Date
    May 2014
    Location
    Memphis TN, US
    Search PM
    Originally Posted by Hypersonic1 View Post
    There is a lot of black in the image, along with a lot of flashing gray dots. It's TV antenna noise or whatever it's called.


    Manono's right. That histogram shows crushed blacks.

    What's next? 'Scopes of tape leader?

    Vegas has many of the same problems as Premiere vis-a-vis resizing, etc., but at least you can read lossless with it. Why not save some dough and get Movie Studio Platinum? Be careful about RGB in Vegas, it uses Studio RGB. What features are you using in Vegas Pro that Movie Studio doesn't have?
    Last edited by LMotlow; 28th Aug 2015 at 18:56.
    - My sister Ann's brother
    Quote Quote  
  13. Manono's right. That histogram shows crushed blacks.
    Then why would it be crushed at -9 IRE?
    Quote Quote  
  14. Click image for larger version

Name:	Capture.PNG
Views:	91
Size:	207.7 KB
ID:	33354

    Some spikes are slightly over -20 IRE.
    Quote Quote  
  15. Member
    Join Date
    May 2014
    Location
    Memphis TN, US
    Search PM
    Originally Posted by Hypersonic1 View Post
    Manono's right. That histogram shows crushed blacks.
    Then why would it be crushed at -9 IRE?
    I guessed you missed post #21: https://forum.videohelp.com/threads/373765-I-am-considering-capturing-via-FireWire?p=24...=1#post2407101.
    - My sister Ann's brother
    Quote Quote  
  16. No I read that. It didn't make sense because black is zero and white is 255.
    Quote Quote  
  17. Originally Posted by Hypersonic1 View Post
    No I read that. It didn't make sense because black is zero and white is 255.
    No. In standard definition rec.601 YUV digital video black is 16, white is 235. On a properly calibrated display any Y values below 16 are display as the same shade of black as 16, any Y values above 235 are displayed with the same brigntess as 235.
    Quote Quote  
  18. How does that apply to the waveforms I just showed you? I don't see what the problem is. With Adope Premiere, everything was between 0 and 100.
    Quote Quote  
  19. Originally Posted by Hypersonic1 View Post
    With Adope Premiere, everything was between 0 and 100.
    Which is where properly encoded video is supposed to be.

    IRE=0 --> Y=16
    IRE=100 --> Y=235
    Quote Quote  
  20. Since mine goes below 0 what does that map to?
    Quote Quote  
  21. Somewhere between Y=0 and Y=16. There can be no values below Y=0; no values above Y=255.
    Last edited by jagabo; 28th Aug 2015 at 22:06.
    Quote Quote  
  22. Why would I want my videos to be from 16 to 235? That looks obsolete.
    Quote Quote  
  23. Because that's what almost every commercial distribution and delivery format uses.
    Last edited by jagabo; 29th Aug 2015 at 08:45.
    Quote Quote  
  24. Originally Posted by Hypersonic1 View Post
    Since mine goes below 0 what does that map to?
    Between 0 and 16. And since most of it is at 0, the damage can't be repaired. Go back and start over.

    Originally Posted by Hypersonic1 View Post
    Then why would it be crushed at -9 IRE?
    The link I gave earlier explained all that and more. The author wasn't entirely sure what -9% IRE mapped to but it's most likely 0.
    Image Attached Thumbnails Click image for larger version

Name:	-9IRE.jpg
Views:	60
Size:	15.8 KB
ID:	33359  

    Last edited by manono; 28th Aug 2015 at 23:27.
    Quote Quote  
  25. Between 0 and 16. And since most of it is at 0, the damage can't be repaired. Go back and start over.
    The damage cannot be done because the below zero luma information still shows up in the waveform monitor. That means I should be able to adjust the levels to bring those blacks up and the whites down.
    Quote Quote  
  26. Why doesn't this 7.5 IRE setup have any effect on the video? The waveform changes, but the video looks the same after checking the box.

    Click image for larger version

Name:	Capture.PNG
Views:	101
Size:	57.0 KB
ID:	33361
    Quote Quote  
  27. 7.5 IRE setup is in the analog signal. It's normally removed when the video is digitized. That's why the DVD recorder has the high/low option on the input.
    Quote Quote  
  28. Originally Posted by manono
    The link I gave earlier explained all that and more. The author wasn't entirely sure what -9% IRE mapped to but it's most likely 0.
    If you extrapolate via IRE 100 and IRE 0, a Y value of 0 maps to approximately -7.2 IRE.
    Quote Quote  
  29. If you extrapolate via IRE 100 and IRE 0, a Y value of 0 maps to approximately -7.2 IRE.
    So what is the problem? I have taken the lossless file and exported it from Vegas, and it still shows values below zero. I don't see how that is loss.
    Quote Quote  
  30. What makes you think inter station white noise would conform to international video standards?

    Whenever you see a solid white line at the bottom of a waveform monitor:

    Click image for larger version

Name:	aft.png
Views:	98
Size:	57.0 KB
ID:	33362

    the implication is that a bunch of data points below that line were pushed up, crushed, from below. Ie, the waveform originally looked something like:

    Click image for larger version

Name:	bef.jpg
Views:	90
Size:	117.5 KB
ID:	33363
    Last edited by jagabo; 29th Aug 2015 at 10:12.
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!