The rest of your second post seems again all the hybrid video stuff, except for the garbled PCIE number. Unless you have a specific bug to point out, I don't want to discuss hybrid video handling. Go to videohelp or google for that, please. So, it seems we are left with: * DGDecodeNV CUDA errors * G...

Thank you for the DGCube. Because I'm dealing with DVD content DGSource output was YV12. To feed this to DGCube I ended up with converting to 16 bit depth for example: Source= DGSource("input.dgi",use_pf=true,fieldop=0,rw=1280,rh=960) SourceConv= ConvertBits(ConvertToYUV420(Source, matrix="170m:aut...

I ran some batch indexing and found a couple observations about commandline: [...]\dgdecnv_255\DGIndexNV.exe -e -at template.avs -i D:\otherPath\t00.mkv -o E:\outputpath\s01 I don't have to specify .dgi on the output for it to generate the .dgi file (in this example s01.dgi). avs generated from tem...

(some updates/notes since my last post) When using fieldop=1 I do get the 23.976 fps output, but ffmpeg is still showing top first. DGSource("input.dgi",use_pf=true,fieldop=1,rw=1280,rh=960) ffmpeg: Input #0, avisynth, from 's01.avs': Duration: 01:30:48.90, start: 0.000000, bitrate: N/A Stream #0:0...

Still trying to hit low-hanging fruit first. I'm dealing with hybrid dvd content. I have a 3:2 pulldown 97% film over the duration of DVD content. (The intro scrolling text is 0% film 0 Frame/Field Rpts) Video Info shows Frame Rate: 29.970030 fps Sequence: Frame/Field Frame Struct: Frame Coding: Pro...

I've used AI to help transcribe the legacy decomb524src.zip 32-bit visual studio 6 source code (including 32bit assembly references) to be compatible enough to compile with Visual Studio 2022 x64 so I can continue to use only Avisynth+ plugins64+ DLLs. Should I provide the modified source to this f...

In DGIndexNV.exe when I play to take a look at Video info, space bar and pause button don't seem to work. Stop does. (I tried to create steps to reproduce this issue and I cannot for the life of me get this to happen consistently now that I'm writing this post) If I click to a point in the slider a...

OK, let's hit some low-hanging fruit. The typos have been corrected and the DGDecodeNV manual was slipstreamed.

In the future please make separate threads for separate issues. when you lump things all together as in this thread it makes things very difficult for me to address and track.

Good to hear and thank you for the update. Now I have to head over to your other thread.

TS has a high-overhead mainly for error resilience. Remember it is was designed for broadcast applications.

https://www.obe.tv/why-does-mpeg-ts-still-exist/

hubblec4 wrote: ↑

Fri Jul 19, 2024 7:26 pm

Always we step by 192 Bytes forward and always is there on 5. position a Sync-Byte.
Means that the data for a frame a stored over multiple packets(in very small pieces)?

Yes, and that is why TS is a high-overhead format.

Ditto!

If you parse out the payload and write it to a file, voila, you have a demuxer.

You're up next in the batting order, flyordie. I'll start working on it tomorrow.

The newer versions require a newer GPU. For example, they require late versions of the GPU driver, which will not run on a 210. It's time for you to move to a more recent card and upgrade to 64-bit. Otherwise, you are stuck on 2053.

Slipstream for DGDecNV build 255:

* Fix demuxing of M2V and VC1 from MKV. flyordie

https://rationalqm.us/dgdecnv/binaries

Good to hear. Thank you for the update. The demuxed elementary streams should be the same without all the remuxing/demuxing, but if you are happy then so am I.

I tested with Dragon_Ball_Z. First I demuxed 00008.mpls with dgdemux to get dgdemux.avc. Then with eac3to: D:\tmp\DGDemuxGUI test>eac3to G:\Rips\Dragon_Ball_Z 1) 01005.mpls, 00008.m2ts+00010.m2ts, 0:29:23 - Chapters, 5 chapters - h264/AVC, 1080p24/1.001 (16:9) - RAW/PCM, Japanese, stereo, 48kHz - RA...

OK, I can run some tests. Please tell me how you demux with makemkv. I wasn't aware that it could demux.

@DelBoy83

Does this fix your issue?

I slipstreamed the fix for this file into DGIndexNV build 255, so please re-download and test.

This fix affects only M2V and VC1 in MKV. I'll be happy to look at any other mismatch cases you may run into. Please post them here.

Thank you, yes, that helps.

I assume you meant demuxed with DGIndexNV as DGIndex does not do MKV.

It points to an issue. Please be patient as we have a backlog right now after our down time. Gonna catch up as quick as we can.

Setting thread back to unresolved.

I don't really have time right now for a general exposition about it. So much going on and we're behind on some pending issues. It's hard to find time for general stuff not related to a specific problem with a DG tool. If you want to know for a specific case why the demuxed files differ, then please...

Thanks for the valuable and detailed report. Let's look at it after the 4th celebration.

Happy 4th to everybody!

Curly is back in town tomorrow so I'm sure he'll reply.

Anything with AI-this or AI-that gets instantly rejected.

AI-enhanced, watch out!

VSR resize ho-hum, twiddle your thumb.

Still, it's interesting to see new stuff, so thank you hydra3333.