View Full Version : Ut Video Codec Suite - a new lossless video codec for Windows!
Pages :
1
2
3
4
5
6
7
8
[
9]
10
11
12
13
14
15
kolak
14th February 2015, 01:15
If you encode utvideo with ffmpeg than even original decoder may be slow. There was some patch for utvideo and slices in ffmpeg. Make sure that you use latest ffmpeg and try adding -slices.
Even so ffmpeg version seams to be no near as good as original code.
Magicyuv is faster, though not 2x :)
umezawa_takeshi
7th March 2015, 15:48
Version 15.1.0 (http://umezawa.dyndns.info/wordpress/?p=5393) was released on 2015-02-28.
Bug fixes
Mac version do not use assembly language version routine.
Windows version is not affected by this problem.
readme (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.1.0-readme.en.html) / Windows (exe) (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.1.0-win.exe) Mac OS X (zip) (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.1.0-macosx.zip) / source code (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.1.0-src.zip)
umezawa_takeshi
25th April 2015, 14:58
Version 15.2.0 (http://umezawa.dyndns.info/wordpress/?p=5514) is released on 2015-04-25 JST.
New features
Added diagnostic log console.
Bug fixes
ULRA, ULRG: RGBA/RGB32 output from decoder is broken if encoded with "Optimize for compression ratio" and "Assume interlace video".
NOTICE TO MAC USERS: File name of QuickTime component is changed (old: utvideo.component, new: utv_qt.component). You have to delete old component file.
Run utv_logc to open diagnostic log console.
The bug exists in decoder. re-encoding is not necessary.
readme (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.2.0-readme.en.html) / Windows (exe) (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.2.0-win.exe) Mac OS X (zip) (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.2.0-macosx.zip) / source code (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.2.0-src.zip)
umezawa_takeshi
9th August 2015, 21:49
Source code repository of Ut Video Codec Suite was pushed to GitHub.
The URL is https://github.com/umezawatakeshi/utvideo
kolak
9th August 2015, 22:29
10/12bit RGB modes?
16bit I assume is tricky?
umezawa_takeshi
10th August 2015, 20:08
not yet at all.
umezawa_takeshi
22nd September 2015, 14:18
Version 15.3.0 (http://umezawa.dyndns.info/wordpress/?p=5691) is released on 2015-09-22 JST.
Others
Removed MFT Codec.
License (GPLv2) (http://umezawa.dyndns.info/archive/utvideo/gplv2.txt) / readme (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.3.0-readme.en.html) / Windows (exe) (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.3.0-win.exe) Mac OS X (zip) (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.3.0-macosx.zip) / source code (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.3.0-src.zip)
umezawa_takeshi
9th January 2016, 15:58
Version 15.4.0 (http://umezawa.dyndns.info/wordpress/?p=5691) is released.
Performance Improvements
Improved efficienty of QuickTime components.
License (GPLv2) (http://umezawa.dyndns.info/archive/utvideo/gplv2.txt) / readme (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.4.0-readme.en.html) / Windows (exe) (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.4.0-win.exe) Mac OS X (zip) (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.4.0-macosx.zip) / source code (http://umezawa.dyndns.info/archive/utvideo/utvideo-15.4.0-src.zip)
WorBry
25th January 2016, 18:06
It's been a good while since I used UTVideo but having just installed version 15.4.0 I'm surprised to find that the RGB (ULRG) and RGBA (ULRA) formats don't appear in the list of VFW codecs under Compression in VirtualDub, as would be expected:
http://umezawa.dyndns.info/archive/utvideo/utvideo-15.4.0-readme.en.html
All I see listed are:
YUV420 BT.709 VCM (ULH0)
YUV422 BT.709 VCM (ULH2)
PRO YUV422 10bit (UQY2)
http://i.imgur.com/KIHoDTj.png
I'm running Win7 64-bit. Same thing with both 32-bit and 64-bit VDub 1.10.4.
Tried installing a earlier version of UTVideo 13.3.1, but still no RGB.
What gives ?
ChiDragon
25th January 2016, 20:00
Since you're also missing the BT.601 FOURCCs, did you open an HDYC video before looking at the Compression list?
What if you view the list with no video open in VDub?
WorBry
25th January 2016, 20:27
What if you view the list with no video open in VDub?
I see the same thing no matter what.
WorBry
25th January 2016, 20:57
Here's something interesting. I remembered a utility I used to use for checking and swapping installed VFW codecs (32bit) when I was working with DV - VCSwap. Installed that (surprised it even worked on Win7) and this is what it shows:
http://i.imgur.com/S0OcMTA.png
The "missing" fourcc's are listed there under 'active' vfw codecs, and all point to the utv-vcm.dll in the System32 folder, but they are not declared by "Description" as such.
I've no idea how to resolve that.
Sparktank
26th January 2016, 00:53
It's been a good while since I used UTVideo
Did you install only _or_ did you uninstall old version first then install new version?
WorBry
26th January 2016, 02:49
I should have been more specific; I meant it's been a good while, easily more than a year, since I used UTVideo for encoding RGB. I used it briefly maybe 6 weeks ago for encoding a couple of files HD files in YV12, but I honestly can't recall if the RGB codecs were listed then. That must have been version 15.3.0 as I kept copies of all the update exe files going back to 13.3.1 and the last one on file was 15.3.0. Seeing that RGB codecs were not listed and that an update was available, I just installed 15.4.0 over it (assumed 15.3.0), but still no RGB codecs. So I completely uninstalled 15.4.0 and tried again, but no joy. Uninstalled again and tried the earliest version I had on file (13.3.1), but still no RGB codecs. Uninstalled 13.3.1 and re-installed 15.4.0 again, and that's where it's at now. Nutty-crunch is that I just can't recall when the RGB codecs were last listed. Pathetic I know, but what to do?
Sparktank
26th January 2016, 05:39
I wasn't sure what version you installed prior, hence asking about uninstall/install process.
The installation notes in the Readme:
If version 10.2.0 or older is installed, you have to uninstall that version before you install this version.
Check. (done a multiple times)
If VCM codec is not registered properly, merge utvideo.reg in install destination with registry as a last resort. This file assumes Windows directory is C:\Windows.
For me, on Win7 (x64), the reg file can be found (installed to):
C:\Program Files\utvideo\utvideo.reg
Have you tried merging that reg file?
The reg file looks like this if you open in it in text editor:
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
"VIDC.ULRA"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.ULRG"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.ULY0"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.ULY2"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.ULH0"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.ULH2"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.UQY2"="C:\\Windows\\system32\\utv_vcm.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32]
"VIDC.ULRA"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.ULRG"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.ULY0"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.ULY2"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.ULH0"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.ULH2"="C:\\Windows\\system32\\utv_vcm.dll"
"VIDC.UQY2"="C:\\Windows\\system32\\utv_vcm.dll"
WorBry
26th January 2016, 06:10
For me, on Win7 (x64), the reg file can be found (installed to):
C:\Program Files\utvideo\utvideo.reg
Have you tried merging that reg file?
The reg file looks like this if you open in it in text editor:
Yes, I did try merging the reg file and it made no difference. Opening now the reg file in Notepad it is exactly the same as what you have posted.
If it's of any relevance at all, the UTVideo Global Configuration panel looked like this after fresh install of 15.4.0, with nothing ticked:
http://i.imgur.com/2PnHVD6.png
Grasping at straws, tried ticking either or both the config options, but made no difference.
Sparktank
26th January 2016, 06:44
What a conundrum.
Can't think of much else to do.
Except maybe uninstall again, but this time use something like CCleaner to clean all junk, clean the reg. Then reboot before installing newest version again (even right-click to install as Admin, even if single/only user on the PC).
And merge reg file again and reboot after.
Beyond that, I defer to other wizardry others can conjure up.
WorBry
27th January 2016, 01:39
A conundrum indeed.
Well I took your advice.
Uninstalled UTVideo 15.4.0, rebooted and ran CCleaner. Ran the CCleaner registry scan. There were two entries that I could see there relating to UTVideo:
One an "Application Path Issue" linked to the location of the UTVideo.exe installation file for version 13.3.1, which must have been retained from when I installed 13.3.1 from that location.
http://i.imgur.com/aPZNdZS.png
and other an Obsolete Software Key
http://i.imgur.com/lZAiPeH.png
Fixed (deleted) both of those, rebooted and re-installed UTVideo 15.4.0 (As Administrator). No change. Merged the reg file and rebooted - no change.
Made a full disc back-up. Repeated the process again, this time "fixing" all registry issue entries detected by the CCleaner registry scan. Installed UTVideo 15.4.0 again - no change. Merged the reg file and rebooted - no change.
Restored the full disc backup. I could have just made and restored a back-up of the registry, but I'm a bit twitchy about registry cleaners - had a bad experience on my last PC running XP.
So, I'm back to square one, minus those two fixed UTVideo registry entries.
Maybe the UTVideo developer could offer some advice if he's looking in.
Sparktank
27th January 2016, 02:42
Do you have UAC enabled or something?
If you download the installer and right-click it to see the properties dialogue box, does it show "unblock file" ?
WorBry
27th January 2016, 03:13
Yes, UAC is enabled and the UTVideo installer properties show the option to "Unblock File". But surely when the UAC screen "Do you want to allow the following program from an unknown publisher to make changes to this computer" pops up, clicking Yes does the same thing doesn't it?
Ignus2
27th January 2016, 04:43
The description and short name of a codec comes after loading the codec dll, not from the registry. If they are not there it means codec initialization with those fourccs fails in some way. Though that would be very strange.
Greets,
I.
Sparktank
27th January 2016, 05:58
Yes, UAC is enabled and the UTVideo installer properties show the option to "Unblock File". But surely when the UAC screen "Do you want to allow the following program from an unknown publisher to make changes to this computer" pops up, clicking Yes does the same thing doesn't it?
I would unblock the file before installing and go through the pop-up with UAC.
I think they're separate entities.
On my laptop, I had UAC disabled but would still need to unblock files from trusted soures to get full functionality.
With some AVS plugins/tools from here, if I forget to unblock the archive before extracting and try to run something, I would still get the pop-up even though UAC is disabled. (and I am single/only user as Admin)
When I experience issues with programs, I check the source installer (archive) and ensure that it has been ublocked.
Unblocking helps resolve most issues I have on that crummy laptop (also Win7 x64).
WorBry
27th January 2016, 07:51
Thanks for your continued efforts to find a solution.
Tried unblocking the installer file first, but I'm afraid it made no difference....still no pesky RGB codecs.
WorBry
27th January 2016, 18:37
The description and short name of a codec comes after loading the codec dll, not from the registry. If they are not there it means codec initialization with those fourccs fails in some way. Though that would be very strange.
And thanks for your reply also Ignus2. I'll take your word for that. Needless to say I have no idea what to do about it.
Reason why I'm 'revisiting' UTVideo is that I'm been tinkering with KDenlive in Linux (Kubuntu) of late, examining the various available input and output formats and their behavior with respect to YUV levels.
Testing some raw full-scale (0-255 luma) 1080/30p.mov clips from a Nikon camera, the KDenlive preset transcode formats (DNxHD, "Matroska.mkv" (HuffYuv)) compress to 16-235. Tried encoding these and some other formats (including UTVideo, FFV1) independently with FFMPEG. Despite setting the "full scale" pix_format flags yuvj422p and yuvj420p, FFMPEG auto-reverts to yuv422p and yuv420p (reporting pixel format incompatibility) and outputs 16-235 scale YUV. The only two formats I've got to work with the full scale pix_format flags are RawYUY2/YV12 and x264, and neither would be my choice for an input intermediate.
That said YV12/YUY2.avi encodes created with the vfw UTVideo work just fine and the "full scale" is respected in KDenLive. So there's an option there. As regards RGB transcode options, well (RawRGB aside), I suppose I could use FFMPEG UTvideo RGB for now, but it would be nice to have the vfw UTVideo RGB options.
Frustrating - so near and yet so far .
umezawa_takeshi
30th January 2016, 17:51
First, sorry for being late.
I have read preceding posts. What a conundrum.
As Ignus2 said, codec's short name and description are retrieved from DLL, not from registry. So it indicates initialization failure of codec.
Could you try following?:
Open command prompt and run C:\Program Files\utvideo\utv_logc.exe
This program is log viewer for Ut Video Codec Suite.
Run VDub and open "Select video compression" dialog.
You will see something like this in command prompt:
{0} Veedub64.exe[2108]: OPEN
{0} Veedub64.exe[2108]: <utv_core> Ut Video Codec Suite 15.4.0 (x64)
{0} Veedub64.exe[2108]: <utv_core> CPUID vendor="GenuineIntel"
{0} Veedub64.exe[2108]: <utv_core> CPUID procbrand=" Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz"
{0} Veedub64.exe[2108]: <utv_core> CPUID family=06H model=2AH
{0} Veedub64.exe[2108]: <utv_core> CPUID march="Sandy Bridge" (ID 00010004)
{0} Veedub64.exe[2108]: <utv_core> supports POPCNT
{0} Veedub64.exe[2108]: <utv_core> supports OSXSAVE
{0} Veedub64.exe[2108]: <utv_core> supports XMM/YMM state by OS
{0} Veedub64.exe[2108]: <utv_core> supports AVX1
{0} Veedub64.exe[2108]: <utv_core> supports SSE4.2
{0} Veedub64.exe[2108]: <utv_core> supports SSE4.1
{0} Veedub64.exe[2108]: <utv_core> supports SSSE3
{0} Veedub64.exe[2108]: <utv_core> supports SSE3
{0} Veedub64.exe[2108]: <utv_core> supports SSE2
{0} Veedub64.exe[2108]: <utv_core> DllMain(hModule=000007FEE2EF0000, dwReason=DLL_PROCESS_ATTACH, lpReserved=0000000000000000)
{0} Veedub64.exe[2108]: <utv_vcm > DllMain(hModule=000007FEF9640000, dwReason=DLL_PROCESS_ATTACH, lpReserved=0000000000000000)
{0} Veedub64.exe[2108]: <utv_vcm > CVCMCodec::Open(icopen=NULL)
{0} Veedub64.exe[2108]: <utv_vcm > 00000000003F7210 CVCMCodec::CVCMCodec(fccHandler=FFFFFFFF)
{0} Veedub64.exe[2108]: <utv_core> CCodec::CreateInstance(utvf=00000000)
{0} Veedub64.exe[2108]: <utv_core> found utvf=00000000
{0} Veedub64.exe[2108]: <utv_vcm > 00000000003F7210 m_pCodec=00000000003987F0, TinyName="Dummy"
{0} Veedub64.exe[2108]: <utv_vcm > CVCMCodec::Open(icopen=000000000012EBD8, icopen->fccType=63646976, icopen->fccHandler=61726C75)
{0} Veedub64.exe[2108]: <utv_vcm > 00000000003F7230 CVCMCodec::CVCMCodec(fccHandler=41524C55)
{0} Veedub64.exe[2108]: <utv_core> CCodec::CreateInstance(utvf=554C5241)
{0} Veedub64.exe[2108]: <utv_core> found utvf=554C5241
{0} Veedub64.exe[2108]: <utv_core> 00000000028B0080 CCodecBase::CCodecBase(pszTinyName="ULRA", pszInterfaceName="VCM")
{0} Veedub64.exe[2108]: <utv_vcm > 00000000003F7230 m_pCodec=00000000028B0080, TinyName="ULRA"
{0} Veedub64.exe[2108]: <utv_vcm > 00000000003F7230 CVCMCodec::~CVCMCodec()
{0} Veedub64.exe[2108]: <utv_core> 00000000028B0080 CCodecBase::~CCodecBase()
{0} Veedub64.exe[2108]: <utv_vcm > 00000000003F7210 CVCMCodec::~CVCMCodec()
{0} Veedub64.exe[2108]: <utv_vcm > DllMain(hModule=000007FEF9640000, dwReason=DLL_PROCESS_DETACH, lpReserved=0000000000000000)
{0} Veedub64.exe[2108]: <utv_core> DllMain(hModule=000007FEE2EF0000, dwReason=DLL_PROCESS_DETACH, lpReserved=0000000000000000)
{0} Veedub64.exe[2108]: CLOSE
{1} Veedub64.exe[2108]: OPEN
{1} Veedub64.exe[2108]: <utv_core> Ut Video Codec Suite 15.4.0 (x64)
(snip)
Post all of that. (It should be very long. sorry)
I hope it shows a clew.
However, The process from loading DLL to retrieving codec information is completely same for all FourCC in Ut Video Codec Suite. I'm not sure that we can finally find solution...
WorBry
30th January 2016, 20:20
Thanks for responding to my cry for help :)
Here's the log file
C:\Program Files\utvideo>utv_logc.exe
{0} VirtualDub.exe[2536]: OPEN
{0} VirtualDub.exe[2536]: <utv_core> Ut Video Codec Suite 15.4.0 (x86)
{0} VirtualDub.exe[2536]: <utv_core> CPUID vendor="AuthenticAMD"
{0} VirtualDub.exe[2536]: <utv_core> CPUID procbrand="AMD FX(tm)-6300 Six-Co
re Processor "
{0} VirtualDub.exe[2536]: <utv_core> CPUID family=15H model=02H
{0} VirtualDub.exe[2536]: <utv_core> CPUID march="Unknown" (ID FFFFFFFF)
{0} VirtualDub.exe[2536]: <utv_core> supports BMI1
{0} VirtualDub.exe[2536]: <utv_core> supports LZCNT
{0} VirtualDub.exe[2536]: <utv_core> supports POPCNT
{0} VirtualDub.exe[2536]: <utv_core> supports OSXSAVE
{0} VirtualDub.exe[2536]: <utv_core> supports XMM/YMM state by OS
{0} VirtualDub.exe[2536]: <utv_core> supports AVX1
{0} VirtualDub.exe[2536]: <utv_core> supports SSE4.2
{0} VirtualDub.exe[2536]: <utv_core> supports SSE4.1
{0} VirtualDub.exe[2536]: <utv_core> supports SSSE3
{0} VirtualDub.exe[2536]: <utv_core> supports SSE3
{0} VirtualDub.exe[2536]: <utv_core> supports SSE2
{0} VirtualDub.exe[2536]: <utv_core> DllMain(hModule=74800000, dwReason=DLL_PROC
ESS_ATTACH, lpReserved=00000000)
{0} VirtualDub.exe[2536]: <utv_vcm > DllMain(hModule=74E50000, dwReason=DLL_PROC
ESS_ATTACH, lpReserved=00000000)
{0} VirtualDub.exe[2536]: <utv_vcm > CVCMCodec::Open(icopen=NULL)
{0} VirtualDub.exe[2536]: <utv_vcm > 00291A58 CVCMCodec::CVCMCodec(fccHandler=FF
FFFFFF)
{0} VirtualDub.exe[2536]: <utv_core> CCodec::CreateInstance(utvf=00000000)
{0} VirtualDub.exe[2536]: <utv_core> found utvf=00000000
{0} VirtualDub.exe[2536]: <utv_vcm > 00291A58 m_pCodec=00291A68, TinyName="Dumm
y"
{0} VirtualDub.exe[2536]: <utv_vcm > CVCMCodec::Open(icopen=0018EEE8, icopen->fc
cType=63646976, icopen->fccHandler=30686C75)
{0} VirtualDub.exe[2536]: <utv_vcm > 00291A78 CVCMCodec::CVCMCodec(fccHandler=30
484C55)
{0} VirtualDub.exe[2536]: <utv_core> CCodec::CreateInstance(utvf=554C4830)
{0} VirtualDub.exe[2536]: <utv_core> found utvf=554C4830
{0} VirtualDub.exe[2536]: <utv_core> 002A4E78 CCodecBase::CCodecBase(pszTinyName
="ULH0", pszInterfaceName="VCM")
{0} VirtualDub.exe[2536]: <utv_vcm > 00291A78 m_pCodec=002A4E78, TinyName="ULH0
"
{0} VirtualDub.exe[2536]: <utv_vcm > 00291A78 CVCMCodec::~CVCMCodec()
{0} VirtualDub.exe[2536]: <utv_core> 002A4E78 CCodecBase::~CCodecBase()
{0} VirtualDub.exe[2536]: <utv_vcm > 00291A58 CVCMCodec::~CVCMCodec()
{0} VirtualDub.exe[2536]: <utv_vcm > DllMain(hModule=74E50000, dwReason=DLL_PROC
ESS_DETACH, lpReserved=00000000)
{0} VirtualDub.exe[2536]: <utv_core> DllMain(hModule=74800000, dwReason=DLL_PROC
ESS_DETACH, lpReserved=00000000)
{0} VirtualDub.exe[2536]: CLOSE
{1} VirtualDub.exe[2536]: OPEN
{1} VirtualDub.exe[2536]: <utv_core> Ut Video Codec Suite 15.4.0 (x86)
{1} VirtualDub.exe[2536]: <utv_core> CPUID vendor="AuthenticAMD"
{1} VirtualDub.exe[2536]: <utv_core> CPUID procbrand="AMD FX(tm)-6300 Six-Co
re Processor "
{1} VirtualDub.exe[2536]: <utv_core> CPUID family=15H model=02H
{1} VirtualDub.exe[2536]: <utv_core> CPUID march="Unknown" (ID FFFFFFFF)
{1} VirtualDub.exe[2536]: <utv_core> supports BMI1
{1} VirtualDub.exe[2536]: <utv_core> supports LZCNT
{1} VirtualDub.exe[2536]: <utv_core> supports POPCNT
{1} VirtualDub.exe[2536]: <utv_core> supports OSXSAVE
{1} VirtualDub.exe[2536]: <utv_core> supports XMM/YMM state by OS
{1} VirtualDub.exe[2536]: <utv_core> supports AVX1
{1} VirtualDub.exe[2536]: <utv_core> supports SSE4.2
{1} VirtualDub.exe[2536]: <utv_core> supports SSE4.1
{1} VirtualDub.exe[2536]: <utv_core> supports SSSE3
{1} VirtualDub.exe[2536]: <utv_core> supports SSE3
{1} VirtualDub.exe[2536]: <utv_core> supports SSE2
{1} VirtualDub.exe[2536]: <utv_core> DllMain(hModule=747E0000, dwReason=DLL_PROC
ESS_ATTACH, lpReserved=00000000)
{1} VirtualDub.exe[2536]: <utv_vcm > DllMain(hModule=74820000, dwReason=DLL_PROC
ESS_ATTACH, lpReserved=00000000)
{1} VirtualDub.exe[2536]: <utv_vcm > CVCMCodec::Open(icopen=NULL)
{1} VirtualDub.exe[2536]: <utv_vcm > 00291A58 CVCMCodec::CVCMCodec(fccHandler=FF
FFFFFF)
{1} VirtualDub.exe[2536]: <utv_core> CCodec::CreateInstance(utvf=00000000)
{1} VirtualDub.exe[2536]: <utv_core> found utvf=00000000
{1} VirtualDub.exe[2536]: <utv_vcm > 00291A58 m_pCodec=00291A68, TinyName="Dumm
y"
{1} VirtualDub.exe[2536]: <utv_vcm > CVCMCodec::Open(icopen=0018EEE8, icopen->fc
cType=63646976, icopen->fccHandler=32686C75)
{1} VirtualDub.exe[2536]: <utv_vcm > 00291A78 CVCMCodec::CVCMCodec(fccHandler=32
484C55)
{1} VirtualDub.exe[2536]: <utv_core> CCodec::CreateInstance(utvf=554C4832)
{1} VirtualDub.exe[2536]: <utv_core> found utvf=554C4832
{1} VirtualDub.exe[2536]: <utv_core> 002A43F8 CCodecBase::CCodecBase(pszTinyName
="ULH2", pszInterfaceName="VCM")
{1} VirtualDub.exe[2536]: <utv_vcm > 00291A78 m_pCodec=002A43F8, TinyName="ULH2
"
{1} VirtualDub.exe[2536]: <utv_vcm > 00291A78 CVCMCodec::~CVCMCodec()
{1} VirtualDub.exe[2536]: <utv_core> 002A43F8 CCodecBase::~CCodecBase()
{1} VirtualDub.exe[2536]: <utv_vcm > 00291A58 CVCMCodec::~CVCMCodec()
{1} VirtualDub.exe[2536]: <utv_vcm > DllMain(hModule=74820000, dwReason=DLL_PROC
ESS_DETACH, lpReserved=00000000)
{1} VirtualDub.exe[2536]: <utv_core> DllMain(hModule=747E0000, dwReason=DLL_PROC
ESS_DETACH, lpReserved=00000000)
{1} VirtualDub.exe[2536]: CLOSE
{2} VirtualDub.exe[2536]: OPEN
{2} VirtualDub.exe[2536]: <utv_core> Ut Video Codec Suite 15.4.0 (x86)
{2} VirtualDub.exe[2536]: <utv_core> CPUID vendor="AuthenticAMD"
{2} VirtualDub.exe[2536]: <utv_core> CPUID procbrand="AMD FX(tm)-6300 Six-Co
re Processor "
{2} VirtualDub.exe[2536]: <utv_core> CPUID family=15H model=02H
{2} VirtualDub.exe[2536]: <utv_core> CPUID march="Unknown" (ID FFFFFFFF)
{2} VirtualDub.exe[2536]: <utv_core> supports BMI1
{2} VirtualDub.exe[2536]: <utv_core> supports LZCNT
{2} VirtualDub.exe[2536]: <utv_core> supports POPCNT
{2} VirtualDub.exe[2536]: <utv_core> supports OSXSAVE
{2} VirtualDub.exe[2536]: <utv_core> supports XMM/YMM state by OS
{2} VirtualDub.exe[2536]: <utv_core> supports AVX1
{2} VirtualDub.exe[2536]: <utv_core> supports SSE4.2
{2} VirtualDub.exe[2536]: <utv_core> supports SSE4.1
{2} VirtualDub.exe[2536]: <utv_core> supports SSSE3
{2} VirtualDub.exe[2536]: <utv_core> supports SSE3
{2} VirtualDub.exe[2536]: <utv_core> supports SSE2
{2} VirtualDub.exe[2536]: <utv_core> DllMain(hModule=74800000, dwReason=DLL_PROC
ESS_ATTACH, lpReserved=00000000)
{2} VirtualDub.exe[2536]: <utv_vcm > DllMain(hModule=74E50000, dwReason=DLL_PROC
ESS_ATTACH, lpReserved=00000000)
{2} VirtualDub.exe[2536]: <utv_vcm > CVCMCodec::Open(icopen=NULL)
{2} VirtualDub.exe[2536]: <utv_vcm > 00291998 CVCMCodec::CVCMCodec(fccHandler=FF
FFFFFF)
{2} VirtualDub.exe[2536]: <utv_core> CCodec::CreateInstance(utvf=00000000)
{2} VirtualDub.exe[2536]: <utv_core> found utvf=00000000
{2} VirtualDub.exe[2536]: <utv_vcm > 00291998 m_pCodec=002919A8, TinyName="Dumm
y"
{2} VirtualDub.exe[2536]: <utv_vcm > CVCMCodec::Open(icopen=0018EEE8, icopen->fc
cType=63646976, icopen->fccHandler=32797175)
{2} VirtualDub.exe[2536]: <utv_vcm > 00291A58 CVCMCodec::CVCMCodec(fccHandler=32
595155)
{2} VirtualDub.exe[2536]: <utv_core> CCodec::CreateInstance(utvf=55515932)
{2} VirtualDub.exe[2536]: <utv_core> found utvf=55515932
{2} VirtualDub.exe[2536]: <utv_core> 002A8468 CCodecBase::CCodecBase(pszTinyName
="UQY2", pszInterfaceName="VCM")
{2} VirtualDub.exe[2536]: <utv_vcm > 00291A58 m_pCodec=002A8468, TinyName="UQY2
"
{2} VirtualDub.exe[2536]: <utv_vcm > 00291A58 CVCMCodec::~CVCMCodec()
{2} VirtualDub.exe[2536]: <utv_core> 002A8468 CCodecBase::~CCodecBase()
{2} VirtualDub.exe[2536]: <utv_vcm > 00291998 CVCMCodec::~CVCMCodec()
{2} VirtualDub.exe[2536]: <utv_vcm > DllMain(hModule=74E50000, dwReason=DLL_PROC
ESS_DETACH, lpReserved=00000000)
{2} VirtualDub.exe[2536]: <utv_core> DllMain(hModule=74800000, dwReason=DLL_PROC
ESS_DETACH, lpReserved=00000000)
{2} VirtualDub.exe[2536]: CLOSE
WorBry
30th January 2016, 20:33
And here's the log file when opening VirtualDub 64-bit, which I don't normally use and is located in a folder on a separate volume from the C:\ drive
C:\Program Files\utvideo>utv_logc.exe
{0} Veedub64.exe[3296]: OPEN
{0} Veedub64.exe[3296]: <utv_core> Ut Video Codec Suite 15.4.0 (x64)
{0} Veedub64.exe[3296]: <utv_core> CPUID vendor="AuthenticAMD"
{0} Veedub64.exe[3296]: <utv_core> CPUID procbrand="AMD FX(tm)-6300 Six-Core
Processor "
{0} Veedub64.exe[3296]: <utv_core> CPUID family=15H model=02H
{0} Veedub64.exe[3296]: <utv_core> CPUID march="Unknown" (ID FFFFFFFF)
{0} Veedub64.exe[3296]: <utv_core> supports BMI1
{0} Veedub64.exe[3296]: <utv_core> supports LZCNT
{0} Veedub64.exe[3296]: <utv_core> supports POPCNT
{0} Veedub64.exe[3296]: <utv_core> supports OSXSAVE
{0} Veedub64.exe[3296]: <utv_core> supports XMM/YMM state by OS
{0} Veedub64.exe[3296]: <utv_core> supports AVX1
{0} Veedub64.exe[3296]: <utv_core> supports SSE4.2
{0} Veedub64.exe[3296]: <utv_core> supports SSE4.1
{0} Veedub64.exe[3296]: <utv_core> supports SSSE3
{0} Veedub64.exe[3296]: <utv_core> supports SSE3
{0} Veedub64.exe[3296]: <utv_core> supports SSE2
{0} Veedub64.exe[3296]: <utv_core> DllMain(hModule=000007FEF0C30000, dwReason=DL
L_PROCESS_ATTACH, lpReserved=0000000000000000)
{0} Veedub64.exe[3296]: <utv_vcm > DllMain(hModule=000007FEF7D00000, dwReason=DL
L_PROCESS_ATTACH, lpReserved=0000000000000000)
{0} Veedub64.exe[3296]: <utv_vcm > CVCMCodec::Open(icopen=NULL)
{0} Veedub64.exe[3296]: <utv_vcm > 0000000000321620 CVCMCodec::CVCMCodec(fccHand
ler=FFFFFFFF)
{0} Veedub64.exe[3296]: <utv_core> CCodec::CreateInstance(utvf=00000000)
{0} Veedub64.exe[3296]: <utv_core> found utvf=00000000
{0} Veedub64.exe[3296]: <utv_vcm > 0000000000321620 m_pCodec=00000000003328C0,
TinyName="Dummy"
{0} Veedub64.exe[3296]: <utv_vcm > CVCMCodec::Open(icopen=000000000012E8B8, icop
en->fccType=63646976, icopen->fccHandler=30686C75)
{0} Veedub64.exe[3296]: <utv_vcm > 0000000000321640 CVCMCodec::CVCMCodec(fccHand
ler=30484C55)
{0} Veedub64.exe[3296]: <utv_core> CCodec::CreateInstance(utvf=554C4830)
{0} Veedub64.exe[3296]: <utv_core> found utvf=554C4830
{0} Veedub64.exe[3296]: <utv_core> 0000000000341FA0 CCodecBase::CCodecBase(pszTi
nyName="ULH0", pszInterfaceName="VCM")
{0} Veedub64.exe[3296]: <utv_vcm > 0000000000321640 m_pCodec=0000000000341FA0,
TinyName="ULH0"
{0} Veedub64.exe[3296]: <utv_vcm > 0000000000321640 CVCMCodec::~CVCMCodec()
{0} Veedub64.exe[3296]: <utv_core> 0000000000341FA0 CCodecBase::~CCodecBase()
{0} Veedub64.exe[3296]: <utv_vcm > 0000000000321620 CVCMCodec::~CVCMCodec()
{0} Veedub64.exe[3296]: <utv_vcm > DllMain(hModule=000007FEF7D00000, dwReason=DL
L_PROCESS_DETACH, lpReserved=0000000000000000)
{0} Veedub64.exe[3296]: <utv_core> DllMain(hModule=000007FEF0C30000, dwReason=DL
L_PROCESS_DETACH, lpReserved=0000000000000000)
{0} Veedub64.exe[3296]: CLOSE
{1} Veedub64.exe[3296]: OPEN
{1} Veedub64.exe[3296]: <utv_core> Ut Video Codec Suite 15.4.0 (x64)
{1} Veedub64.exe[3296]: <utv_core> CPUID vendor="AuthenticAMD"
{1} Veedub64.exe[3296]: <utv_core> CPUID procbrand="AMD FX(tm)-6300 Six-Core
Processor "
{1} Veedub64.exe[3296]: <utv_core> CPUID family=15H model=02H
{1} Veedub64.exe[3296]: <utv_core> CPUID march="Unknown" (ID FFFFFFFF)
{1} Veedub64.exe[3296]: <utv_core> supports BMI1
{1} Veedub64.exe[3296]: <utv_core> supports LZCNT
{1} Veedub64.exe[3296]: <utv_core> supports POPCNT
{1} Veedub64.exe[3296]: <utv_core> supports OSXSAVE
{1} Veedub64.exe[3296]: <utv_core> supports XMM/YMM state by OS
{1} Veedub64.exe[3296]: <utv_core> supports AVX1
{1} Veedub64.exe[3296]: <utv_core> supports SSE4.2
{1} Veedub64.exe[3296]: <utv_core> supports SSE4.1
{1} Veedub64.exe[3296]: <utv_core> supports SSSE3
{1} Veedub64.exe[3296]: <utv_core> supports SSE3
{1} Veedub64.exe[3296]: <utv_core> supports SSE2
{1} Veedub64.exe[3296]: <utv_core> DllMain(hModule=000007FEF0BE0000, dwReason=DL
L_PROCESS_ATTACH, lpReserved=0000000000000000)
{1} Veedub64.exe[3296]: <utv_vcm > DllMain(hModule=000007FEF7CE0000, dwReason=DL
L_PROCESS_ATTACH, lpReserved=0000000000000000)
{1} Veedub64.exe[3296]: <utv_vcm > CVCMCodec::Open(icopen=NULL)
{1} Veedub64.exe[3296]: <utv_vcm > 0000000000321620 CVCMCodec::CVCMCodec(fccHand
ler=FFFFFFFF)
{1} Veedub64.exe[3296]: <utv_core> CCodec::CreateInstance(utvf=00000000)
{1} Veedub64.exe[3296]: <utv_core> found utvf=00000000
{1} Veedub64.exe[3296]: <utv_vcm > 0000000000321620 m_pCodec=00000000003328C0,
TinyName="Dummy"
{1} Veedub64.exe[3296]: <utv_vcm > CVCMCodec::Open(icopen=000000000012E8B8, icop
en->fccType=63646976, icopen->fccHandler=32686C75)
{1} Veedub64.exe[3296]: <utv_vcm > 0000000000321640 CVCMCodec::CVCMCodec(fccHand
ler=32484C55)
{1} Veedub64.exe[3296]: <utv_core> CCodec::CreateInstance(utvf=554C4832)
{1} Veedub64.exe[3296]: <utv_core> found utvf=554C4832
{1} Veedub64.exe[3296]: <utv_core> 0000000000341410 CCodecBase::CCodecBase(pszTi
nyName="ULH2", pszInterfaceName="VCM")
{1} Veedub64.exe[3296]: <utv_vcm > 0000000000321640 m_pCodec=0000000000341410,
TinyName="ULH2"
{1} Veedub64.exe[3296]: <utv_vcm > 0000000000321640 CVCMCodec::~CVCMCodec()
{1} Veedub64.exe[3296]: <utv_core> 0000000000341410 CCodecBase::~CCodecBase()
{1} Veedub64.exe[3296]: <utv_vcm > 0000000000321620 CVCMCodec::~CVCMCodec()
{1} Veedub64.exe[3296]: <utv_vcm > DllMain(hModule=000007FEF7CE0000, dwReason=DL
L_PROCESS_DETACH, lpReserved=0000000000000000)
{1} Veedub64.exe[3296]: <utv_core> DllMain(hModule=000007FEF0BE0000, dwReason=DL
L_PROCESS_DETACH, lpReserved=0000000000000000)
{1} Veedub64.exe[3296]: CLOSE
{2} Veedub64.exe[3296]: OPEN
{2} Veedub64.exe[3296]: <utv_core> Ut Video Codec Suite 15.4.0 (x64)
{2} Veedub64.exe[3296]: <utv_core> CPUID vendor="AuthenticAMD"
{2} Veedub64.exe[3296]: <utv_core> CPUID procbrand="AMD FX(tm)-6300 Six-Core
Processor "
{2} Veedub64.exe[3296]: <utv_core> CPUID family=15H model=02H
{2} Veedub64.exe[3296]: <utv_core> CPUID march="Unknown" (ID FFFFFFFF)
{2} Veedub64.exe[3296]: <utv_core> supports BMI1
{2} Veedub64.exe[3296]: <utv_core> supports LZCNT
{2} Veedub64.exe[3296]: <utv_core> supports POPCNT
{2} Veedub64.exe[3296]: <utv_core> supports OSXSAVE
{2} Veedub64.exe[3296]: <utv_core> supports XMM/YMM state by OS
{2} Veedub64.exe[3296]: <utv_core> supports AVX1
{2} Veedub64.exe[3296]: <utv_core> supports SSE4.2
{2} Veedub64.exe[3296]: <utv_core> supports SSE4.1
{2} Veedub64.exe[3296]: <utv_core> supports SSSE3
{2} Veedub64.exe[3296]: <utv_core> supports SSE3
{2} Veedub64.exe[3296]: <utv_core> supports SSE2
{2} Veedub64.exe[3296]: <utv_core> DllMain(hModule=000007FEF0C30000, dwReason=DL
L_PROCESS_ATTACH, lpReserved=0000000000000000)
{2} Veedub64.exe[3296]: <utv_vcm > DllMain(hModule=000007FEF7D00000, dwReason=DL
L_PROCESS_ATTACH, lpReserved=0000000000000000)
{2} Veedub64.exe[3296]: <utv_vcm > CVCMCodec::Open(icopen=NULL)
{2} Veedub64.exe[3296]: <utv_vcm > 0000000000321620 CVCMCodec::CVCMCodec(fccHand
ler=FFFFFFFF)
{2} Veedub64.exe[3296]: <utv_core> CCodec::CreateInstance(utvf=00000000)
{2} Veedub64.exe[3296]: <utv_core> found utvf=00000000
{2} Veedub64.exe[3296]: <utv_vcm > 0000000000321620 m_pCodec=00000000003328C0,
TinyName="Dummy"
{2} Veedub64.exe[3296]: <utv_vcm > CVCMCodec::Open(icopen=000000000012E8B8, icop
en->fccType=63646976, icopen->fccHandler=32797175)
{2} Veedub64.exe[3296]: <utv_vcm > 0000000000321640 CVCMCodec::CVCMCodec(fccHand
ler=32595155)
{2} Veedub64.exe[3296]: <utv_core> CCodec::CreateInstance(utvf=55515932)
{2} Veedub64.exe[3296]: <utv_core> found utvf=55515932
{2} Veedub64.exe[3296]: <utv_core> 00000000003420A0 CCodecBase::CCodecBase(pszTi
nyName="UQY2", pszInterfaceName="VCM")
{2} Veedub64.exe[3296]: <utv_vcm > 0000000000321640 m_pCodec=00000000003420A0,
TinyName="UQY2"
{2} Veedub64.exe[3296]: <utv_vcm > 0000000000321640 CVCMCodec::~CVCMCodec()
{2} Veedub64.exe[3296]: <utv_core> 00000000003420A0 CCodecBase::~CCodecBase()
{2} Veedub64.exe[3296]: <utv_vcm > 0000000000321620 CVCMCodec::~CVCMCodec()
{2} Veedub64.exe[3296]: <utv_vcm > DllMain(hModule=000007FEF7D00000, dwReason=DL
L_PROCESS_DETACH, lpReserved=0000000000000000)
{2} Veedub64.exe[3296]: <utv_core> DllMain(hModule=000007FEF0C30000, dwReason=DL
L_PROCESS_DETACH, lpReserved=0000000000000000)
{2} Veedub64.exe[3296]: CLOSE
WorBry
31st January 2016, 00:01
And if it provides any other clues, here's the log file when I open Corel VideoStudio Pro x8 (64-bit) which is the NLE I use. In the Project Setting options for creating custom DV/AVI profiles, UTVideo is listed as one of the available (64-bit) VFW codec options. But like VirtualDub, the RGB fourcc's do not show up there either.
C:\Program Files\utvideo>utv_logc.exe
{0} vstudio.exe[4912]: OPEN
{0} vstudio.exe[4912]: <utv_core> Ut Video Codec Suite 15.4.0 (x64)
{0} vstudio.exe[4912]: <utv_core> CPUID vendor="AuthenticAMD"
{0} vstudio.exe[4912]: <utv_core> CPUID procbrand="AMD FX(tm)-6300 Six-Core
Processor "
{0} vstudio.exe[4912]: <utv_core> CPUID family=15H model=02H
{0} vstudio.exe[4912]: <utv_core> CPUID march="Unknown" (ID FFFFFFFF)
{0} vstudio.exe[4912]: <utv_core> supports BMI1
{0} vstudio.exe[4912]: <utv_core> supports LZCNT
{0} vstudio.exe[4912]: <utv_core> supports POPCNT
{0} vstudio.exe[4912]: <utv_core> supports OSXSAVE
{0} vstudio.exe[4912]: <utv_core> supports XMM/YMM state by OS
{0} vstudio.exe[4912]: <utv_core> supports AVX1
{0} vstudio.exe[4912]: <utv_core> supports SSE4.2
{0} vstudio.exe[4912]: <utv_core> supports SSE4.1
{0} vstudio.exe[4912]: <utv_core> supports SSSE3
{0} vstudio.exe[4912]: <utv_core> supports SSE3
{0} vstudio.exe[4912]: <utv_core> supports SSE2
{0} vstudio.exe[4912]: <utv_core> DllMain(hModule=000007FEED7D0000, dwReason=DLL
_PROCESS_ATTACH, lpReserved=0000000000000000)
{0} vstudio.exe[4912]: <utv_vcm > DllMain(hModule=000007FEED820000, dwReason=DLL
_PROCESS_ATTACH, lpReserved=0000000000000000)
{0} vstudio.exe[4912]: <utv_vcm > CVCMCodec::Open(icopen=NULL)
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78620 CVCMCodec::CVCMCodec(fccHandl
er=FFFFFFFF)
{0} vstudio.exe[4912]: <utv_core> CCodec::CreateInstance(utvf=00000000)
{0} vstudio.exe[4912]: <utv_core> found utvf=00000000
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78620 m_pCodec=0000000004CCEC70, T
inyName="Dummy"
{0} vstudio.exe[4912]: <utv_vcm > CVCMCodec::Open(icopen=000000000012BDE8, icope
n->fccType=63646976, icopen->fccHandler=30686C75)
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78640 CVCMCodec::CVCMCodec(fccHandl
er=30484C55)
{0} vstudio.exe[4912]: <utv_core> CCodec::CreateInstance(utvf=554C4830)
{0} vstudio.exe[4912]: <utv_core> found utvf=554C4830
{0} vstudio.exe[4912]: <utv_core> 0000000004E67B70 CCodecBase::CCodecBase(pszTin
yName="ULH0", pszInterfaceName="VCM")
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78640 m_pCodec=0000000004E67B70, T
inyName="ULH0"
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78640 CVCMCodec::CompressGetFormat(
pbihIn=0000000004E76F50, pbihOut=0000000004E77400)
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78640 pbihIn : biSize=40, biWidth=
320, biHeight=240, biPlanes=1, biBitCount=8, biCompression=00000000, biSizeImage
=76800
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78640 CVCMCodec::CompressGetFormat(
pbihIn=0000000004E76F50, pbihOut=0000000004E77400)
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78640 pbihIn : biSize=40, biWidth=
320, biHeight=240, biPlanes=1, biBitCount=16, biCompression=00000000, biSizeImag
e=153600
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78640 CVCMCodec::CompressGetFormat(
pbihIn=0000000004E76F50, pbihOut=0000000004E77400)
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78640 pbihIn : biSize=40, biWidth=
320, biHeight=240, biPlanes=1, biBitCount=24, biCompression=00000000, biSizeImag
e=230400
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78640 CVCMCodec::~CVCMCodec()
{0} vstudio.exe[4912]: <utv_core> 0000000004E67B70 CCodecBase::~CCodecBase()
{0} vstudio.exe[4912]: <utv_vcm > 0000000004E78620 CVCMCodec::~CVCMCodec()
{0} vstudio.exe[4912]: <utv_vcm > DllMain(hModule=000007FEED820000, dwReason=DLL
_PROCESS_DETACH, lpReserved=0000000000000000)
{0} vstudio.exe[4912]: <utv_core> DllMain(hModule=000007FEED7D0000, dwReason=DLL
_PROCESS_DETACH, lpReserved=0000000000000000)
{0} vstudio.exe[4912]: CLOSE
{1} vstudio.exe[4912]: OPEN
{1} vstudio.exe[4912]: <utv_core> Ut Video Codec Suite 15.4.0 (x64)
{1} vstudio.exe[4912]: <utv_core> CPUID vendor="AuthenticAMD"
{1} vstudio.exe[4912]: <utv_core> CPUID procbrand="AMD FX(tm)-6300 Six-Core
Processor "
{1} vstudio.exe[4912]: <utv_core> CPUID family=15H model=02H
{1} vstudio.exe[4912]: <utv_core> CPUID march="Unknown" (ID FFFFFFFF)
{1} vstudio.exe[4912]: <utv_core> supports BMI1
{1} vstudio.exe[4912]: <utv_core> supports LZCNT
{1} vstudio.exe[4912]: <utv_core> supports POPCNT
{1} vstudio.exe[4912]: <utv_core> supports OSXSAVE
{1} vstudio.exe[4912]: <utv_core> supports XMM/YMM state by OS
{1} vstudio.exe[4912]: <utv_core> supports AVX1
{1} vstudio.exe[4912]: <utv_core> supports SSE4.2
{1} vstudio.exe[4912]: <utv_core> supports SSE4.1
{1} vstudio.exe[4912]: <utv_core> supports SSSE3
{1} vstudio.exe[4912]: <utv_core> supports SSE3
{1} vstudio.exe[4912]: <utv_core> supports SSE2
{1} vstudio.exe[4912]: <utv_core> DllMain(hModule=000007FEED7B0000, dwReason=DLL
_PROCESS_ATTACH, lpReserved=0000000000000000)
{1} vstudio.exe[4912]: <utv_vcm > DllMain(hModule=000007FEED800000, dwReason=DLL
_PROCESS_ATTACH, lpReserved=0000000000000000)
{1} vstudio.exe[4912]: <utv_vcm > CVCMCodec::Open(icopen=NULL)
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78720 CVCMCodec::CVCMCodec(fccHandl
er=FFFFFFFF)
{1} vstudio.exe[4912]: <utv_core> CCodec::CreateInstance(utvf=00000000)
{1} vstudio.exe[4912]: <utv_core> found utvf=00000000
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78720 m_pCodec=0000000004CCEC70, T
inyName="Dummy"
{1} vstudio.exe[4912]: <utv_vcm > CVCMCodec::Open(icopen=000000000012BDE8, icope
n->fccType=63646976, icopen->fccHandler=32686C75)
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CVCMCodec(fccHandl
er=32484C55)
{1} vstudio.exe[4912]: <utv_core> CCodec::CreateInstance(utvf=554C4832)
{1} vstudio.exe[4912]: <utv_core> found utvf=554C4832
{1} vstudio.exe[4912]: <utv_core> 0000000004E67B70 CCodecBase::CCodecBase(pszTin
yName="ULH2", pszInterfaceName="VCM")
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 m_pCodec=0000000004E67B70, T
inyName="ULH2"
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CompressGetFormat(
pbihIn=0000000004E76F50, pbihOut=0000000004E77400)
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 pbihIn : biSize=40, biWidth=
320, biHeight=240, biPlanes=1, biBitCount=8, biCompression=00000000, biSizeImage
=76800
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CompressGetFormat(
pbihIn=0000000004E76F50, pbihOut=0000000004E77400)
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 pbihIn : biSize=40, biWidth=
320, biHeight=240, biPlanes=1, biBitCount=16, biCompression=00000000, biSizeImag
e=153600
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CompressGetFormat(
pbihIn=0000000004E76F50, pbihOut=0000000004E77400)
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 pbihIn : biSize=40, biWidth=
320, biHeight=240, biPlanes=1, biBitCount=24, biCompression=00000000, biSizeImag
e=230400
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::~CVCMCodec()
{1} vstudio.exe[4912]: <utv_core> 0000000004E67B70 CCodecBase::~CCodecBase()
{1} vstudio.exe[4912]: <utv_vcm > 0000000004E78720 CVCMCodec::~CVCMCodec()
{1} vstudio.exe[4912]: <utv_vcm > DllMain(hModule=000007FEED800000, dwReason=DLL
_PROCESS_DETACH, lpReserved=0000000000000000)
{1} vstudio.exe[4912]: <utv_core> DllMain(hModule=000007FEED7B0000, dwReason=DLL
_PROCESS_DETACH, lpReserved=0000000000000000)
{1} vstudio.exe[4912]: CLOSE
{2} vstudio.exe[4912]: OPEN
{2} vstudio.exe[4912]: <utv_core> Ut Video Codec Suite 15.4.0 (x64)
{2} vstudio.exe[4912]: <utv_core> CPUID vendor="AuthenticAMD"
{2} vstudio.exe[4912]: <utv_core> CPUID procbrand="AMD FX(tm)-6300 Six-Core
Processor "
{2} vstudio.exe[4912]: <utv_core> CPUID family=15H model=02H
{2} vstudio.exe[4912]: <utv_core> CPUID march="Unknown" (ID FFFFFFFF)
{2} vstudio.exe[4912]: <utv_core> supports BMI1
{2} vstudio.exe[4912]: <utv_core> supports LZCNT
{2} vstudio.exe[4912]: <utv_core> supports POPCNT
{2} vstudio.exe[4912]: <utv_core> supports OSXSAVE
{2} vstudio.exe[4912]: <utv_core> supports XMM/YMM state by OS
{2} vstudio.exe[4912]: <utv_core> supports AVX1
{2} vstudio.exe[4912]: <utv_core> supports SSE4.2
{2} vstudio.exe[4912]: <utv_core> supports SSE4.1
{2} vstudio.exe[4912]: <utv_core> supports SSSE3
{2} vstudio.exe[4912]: <utv_core> supports SSE3
{2} vstudio.exe[4912]: <utv_core> supports SSE2
{2} vstudio.exe[4912]: <utv_core> DllMain(hModule=000007FEED7D0000, dwReason=DLL
_PROCESS_ATTACH, lpReserved=0000000000000000)
{2} vstudio.exe[4912]: <utv_vcm > DllMain(hModule=000007FEED820000, dwReason=DLL
_PROCESS_ATTACH, lpReserved=0000000000000000)
{2} vstudio.exe[4912]: <utv_vcm > CVCMCodec::Open(icopen=NULL)
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78720 CVCMCodec::CVCMCodec(fccHandl
er=FFFFFFFF)
{2} vstudio.exe[4912]: <utv_core> CCodec::CreateInstance(utvf=00000000)
{2} vstudio.exe[4912]: <utv_core> found utvf=00000000
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78720 m_pCodec=0000000004CCEC70, T
inyName="Dummy"
{2} vstudio.exe[4912]: <utv_vcm > CVCMCodec::Open(icopen=000000000012BDE8, icope
n->fccType=63646976, icopen->fccHandler=32797175)
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CVCMCodec(fccHandl
er=32595155)
{2} vstudio.exe[4912]: <utv_core> CCodec::CreateInstance(utvf=55515932)
{2} vstudio.exe[4912]: <utv_core> found utvf=55515932
{2} vstudio.exe[4912]: <utv_core> 000000000E097FD0 CCodecBase::CCodecBase(pszTin
yName="UQY2", pszInterfaceName="VCM")
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 m_pCodec=000000000E097FD0, T
inyName="UQY2"
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CompressGetFormat(
pbihIn=000000000E0801B0, pbihOut=000000000E080660)
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 pbihIn : biSize=40, biWidth=
320, biHeight=240, biPlanes=1, biBitCount=8, biCompression=00000000, biSizeImage
=76800
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CompressGetFormat(
pbihIn=000000000E0801B0, pbihOut=000000000E080660)
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 pbihIn : biSize=40, biWidth=
320, biHeight=240, biPlanes=1, biBitCount=16, biCompression=00000000, biSizeImag
e=153600
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CompressGetFormat(
pbihIn=000000000E0801B0, pbihOut=000000000E080660)
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 pbihIn : biSize=40, biWidth=
320, biHeight=240, biPlanes=1, biBitCount=24, biCompression=00000000, biSizeImag
e=230400
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CompressGetFormat(
pbihIn=000000000E0801B0, pbihOut=000000000E080660)
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 pbihIn : biSize=40, biWidth=
720, biHeight=480, biPlanes=1, biBitCount=8, biCompression=00000000, biSizeImage
=345600
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CompressGetFormat(
pbihIn=000000000E0801B0, pbihOut=000000000E080660)
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 pbihIn : biSize=40, biWidth=
720, biHeight=480, biPlanes=1, biBitCount=16, biCompression=00000000, biSizeImag
e=691200
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::CompressGetFormat(
pbihIn=000000000E0801B0, pbihOut=000000000E080660)
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 pbihIn : biSize=40, biWidth=
720, biHeight=480, biPlanes=1, biBitCount=24, biCompression=00000000, biSizeImag
e=1036800
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78740 CVCMCodec::~CVCMCodec()
{2} vstudio.exe[4912]: <utv_core> 000000000E097FD0 CCodecBase::~CCodecBase()
{2} vstudio.exe[4912]: <utv_vcm > 0000000004E78720 CVCMCodec::~CVCMCodec()
{2} vstudio.exe[4912]: <utv_vcm > DllMain(hModule=000007FEED820000, dwReason=DLL
_PROCESS_DETACH, lpReserved=0000000000000000)
{2} vstudio.exe[4912]: <utv_core> DllMain(hModule=000007FEED7D0000, dwReason=DLL
_PROCESS_DETACH, lpReserved=0000000000000000)
{2} vstudio.exe[4912]: CLOSE
umezawa_takeshi
31st January 2016, 10:02
According to log output,
codec opening request is not sent to DLL
In addition, DLL is not loaded
It indicates that Windows give up opening codec before loading DLL of Ut Video Codec Suite. hmm...
BTW, according to the output of VCSwap that you posted before, you have installed ffdshow. Earlier version of ffdshow (or libavcodec, on which ffdshow is based) have implementation of ULRA, ULRG, ULY2 and ULY0, but don't have ULH2, ULH0 and UQY2. (I don't know that your version 1.3.4524.0 have implementation of ULH2 and ULH0). Are there any relationship...?
WorBry
31st January 2016, 16:37
Thanks.
I'm not sure I understand what association you are suggesting might be related to the UTVideo issue.
Yes, I have CLSID's Rev4525 (Nov 17 2013) of FFDShow installed. Again, I can't recall when it was first installed, but it's been quite a while. Can't see any mention of UTVideo FourCC's there in the FFDShow "VFW Configuration" or "Video Decoder Configuration" codec listings. So I'm not really sure what you are referring to.
I've tried uninstalling both FFDShow and UTVideo 15.4.0, and then re-installing 15.4.0 (after a clean-up with CCleaner) but it's made no difference.
If it's of any relevance at all, I recall (about 6 weeks back) installing 64-bit versions of FFDShow I had on file (rev4531_20140628_x64 and CLSID's rev4533_20140929_clsid_x64) to do some tests in Corel VideoStudio Pro x8 (64-bit) but couldn't proceed because FFDShow didn't appear at all in the list of available 64-bit VFW codecs in the VSProx8 Project Configuration settings. Just why, I don't know. But instead of uninstalling FFDShow-x64, I just rolled-back to a system back-up I'd made beforehand, so I can't see how that episode could have messed things up for UTVIdeo in some way.
Grasping at straws here. Anything else to try ?
EDIT: Plus, I've just tried restoring a full disc back-up (Acronis True Image) of the Win7 x64 system from 25th Nov 2015 - so before all of that. There I find UTVideo 13.3.1 was installed , but the situation was the same. The only FourCC's listed in VDub were:
YUV420 BT.709 VCM (ULH0)
YUV422 BT.709 VCM (ULH2)
PRO YUV422 10bit (UQY2)
Tried uninstalling 13.3.1, followed by a reboot and CCleaner clean-up before installing 15.4.0, but no change.
I have earlier system back-ups, but this was the first good backup after some hardware/network changes and I don't really want to go through that episode again. I've now returned the system to how it was. I never restore anything with System Restore by the way, only back-ups.
So what to do? Is this possibly a bug that I didn't pick-up on earlier?
Ignus2
1st February 2016, 03:35
According to log output,
codec opening request is not sent to DLL
In addition, DLL is not loaded
It indicates that Windows give up opening codec before loading DLL of Ut Video Codec Suite. hmm...
BTW, according to the output of VCSwap that you posted before, you have installed ffdshow. Earlier version of ffdshow (or libavcodec, on which ffdshow is based) have implementation of ULRA, ULRG, ULY2 and ULY0, but don't have ULH2, ULH0 and UQY2. (I don't know that your version 1.3.4524.0 have implementation of ULH2 and ULH0). Are there any relationship...?
That's a clue!
Worbry, you do have ffdshow vfw installed. In your screenshot of codecs, I can see ff_vfw.dll, most certainly that's your problem.
Either delete the registry key for it or delete the dll itself.
This is tricky for 32 bit variants, as the registry and system32 folder is redirected for them.
I suggest you delete these two files:
C:\Windows\system32\ff_vfw.dll. (the 64-bit codec)
C:\Windows\SysWow64\ff_vfw.dll (the 32-bit codec)
EDIT: The location of those DLLs might be somewhere else, I don't know where ffdshow puts them. If they are not there, search for them or look in the registry. Also, it's best to delete the registry keys for ff_vfw.dll too (both).
Make sure to use a 64-bit file manager, as 32-bit programs are redirected to SysWow64.
Greets,
I.
WorBry
1st February 2016, 06:00
Thanks Ignus2,
Sorry for my ignorance, for all to see, but I tried uninstalling FFDShow - wouldn't that do the same ?
And whats a "64-bit file manager" ?
Ignus2
1st February 2016, 10:15
Thanks Ignus2,
Sorry for my ignorance, for all to see, but I tried uninstalling FFDShow - wouldn't that do the same ?
And whats a "64-bit file manager" ?
It should, but as the screenshot shows, it didn't (or system restore messed up somehow).
Just use Windows explorer. (Total Commander 32-bit edition for example is not a 64-bit file manager.)
Greets,
I.
LigH
1st February 2016, 10:31
People old enough to remember the "Norton Commander" (but not excluding younger people) may also like the Far manager (http://www.farmanager.com), which is also available in 32 and 64 bit. It is a real text mode application, adapting to any arbitrary console window size. There are several plugins available, e.g. a Registry browser too. And it doesn't camouflage system directories with localized shell objects, it shows their real name on disk. Cool admin stuff!
WorBry
1st February 2016, 16:43
It should, but as the screenshot shows, it didn't (or system restore messed up somehow)
If you mean the VCSwap screenshot, yes that was at the start when FFDShow was installed. Following umezawa_takeshi's post I uninstalled it, and found it didn't resolve anything.
After your last post about locating and deleting the ff_vfw.dll's and registry keys, I installed FFDshow again to see what you were referring to. A regular Windows Explorer search turned up just one ff_vfw.dll in the C:\Windows\ SysWOW64 folder. Didn't take any direct action on that being unable to locate the other ff_vfw.dll.
But on uninstalling FFDShow again the ff_vfw.dll in the C:\Windows\ SysWOW64 folder disappeared, as might be expected. Hence my asking whether uninstalling was not just doing the same thing. As of now FFDShow is uninstalled.
So, would you suggest I go at it again looking for any registry keys that could still be there? Un-ventured territory for me, this registry stuff.
qyot27
1st February 2016, 18:26
Just use CCleaner to scrub the registry; repeat until you don't get any results back.
WorBry
1st February 2016, 19:57
Thanks. Just tried that. With FFDShow already uninstalled, I then uninstalled UTVideo 15.4.0, rebooted and ran CCleaner's registry cleaner three times (rebooting between each clean). Reinstalled UTVideo 15.4.0. Still no RGB FourCC's.
Ignus2
2nd February 2016, 12:42
The problem is the way VFW works. The codec DLL given for a given fourcc in the registry is not authoritative. VFW will probe every codec sometimes for a given fourcc and the first to respond wins. As the description and short name didn't appear in VCSwap I was assuming the codec initialization failed, and as Takeshi examined, the UT DLL was not loaded at all, so something else responded, and I assumed it was the FFVFW variant as it also handles UT codecs.
At least, that's my assumption.
Can you post a new screenshot of VSwap?
Greets,
I.
umezawa_takeshi
2nd February 2016, 16:24
I install ffdshow and UtVideo in test VMs in preceding order and reversed order, but VCswap shows that all of FourCC is still available in both case. My hypothesis may be rejected, or there are more conditions. hmm...
I sometimes hear that all of FourCC in UtVideo is not available, but I have never heard that some of FourCC in UtVideo is not available...
The problem is the way VFW works. The codec DLL given for a given fourcc in the registry is not authoritative. VFW will probe every codec sometimes for a given fourcc and the first to respond wins
Is that so? I didn't know that.
raffriff42
2nd February 2016, 22:48
It's kinda that way, according to Avery Lee:One video codec to break everything (http://www.virtualdub.org/blog/pivot/entry.php?id=139)
The way that video codecs work in Windows is that each one is queried in turn and asked if it supports the compressed video format. If a codec says "yes," then that codec is used to decode the video. Otherwise, Windows proceeds to the next video codec down the line, until it either finds one that can handle the format or runs out of video codecs. The details are different between Video for Windows and DirectShow, but the general idea is the same. This provides a great deal of flexibility, because a video codec can decode more than one format. Some MPEG-4 video codecs, for instance, can helpfully also decode uncompressed YCbCr formats that are difficult to find dedicated codecs for, like YV12.
It also adds a bit of fragility, in that occasionally a video codec's decompression query routine acts as follows:
Q: Do you support video format....
A: Yes!
Q: Uh, I didn't tell you the video format. You really support this?
A: Yes!
The errant video codec then proceeds to capture every video format that comes its way, and happily barfs whenever it gets any format other than the one it was supposed to handle...
LigH
3rd February 2016, 12:46
I remember from old Windows versions that it was possible to change the order of VfW codecs (not as detailed as DirectShow merits, but at least at all). But I am afraid that you may not find access to this dialog easily since Vista. It was contained in simple dialogs like you may know from the device manager; VfW codecs used to be handled like devices once.
shekh
3rd February 2016, 14:57
Another thing to try, delete ALL entries from these registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32
And then import utvideo.reg or reinstall utvideo.
The idea behind this: what if codec enumeration fails because of some other broken codec entry.
LigH
4th February 2016, 09:14
Another thing to try, delete ALL entries from these registry keys:
:eek: Insanity level is OVER 9000!!! :confused:
That will probably destroy the whole legacy multimedia system. Even deleting "all VIDC.* entries" would possibly be overkill.
WorBry
6th February 2016, 05:44
Can you post a new screenshot of VSwap?
Sorry for the delay in coming back on this. I'm afraid needs required that I reinstall FFDShow for some other work, but I did check VCSwap at the stage when FFDShow was uninstalled and I had gone on to try those other suggestions - as per posts #446 and #447:
Just use CCleaner to scrub the registry; repeat until you don't get any results back.
Thanks. Just tried that. With FFDShow already uninstalled, I then uninstalled UTVideo 15.4.0, rebooted and ran CCleaner's registry cleaner three times (rebooting between each clean). Reinstalled UTVideo 15.4.0. Still no RGB FourCC's.
And I assure you that no ff_wfw.dll was not listed there in VCSwap at that point.
:eek: Insanity level is OVER 9000!!! :confused:
That will probably destroy the whole legacy multimedia system. Even deleting "all VIDC.* entries" would possibly be overkill.
So maybe not a good idea to try that then?
shekh
6th February 2016, 10:43
So maybe not a good idea to try that then?
You dont lose anything.
My algorithm would be:
go to
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32
Rename Drivers32 to Drivers32~ (for use as backup)
Make fresh Drivers32 key
make string value vidc.ulra = C:\Windows\system32\utv_vcm.dll
open 32bit VD and see it codec is listed
yes: move other keys from Drivers32~ key to Drivers32 one by one
no: roll back all changes by renaming Drivers32~ to Drivers32
IMO there is no need to restart system at any point.
sargan
7th February 2016, 20:17
People old enough to remember the "Norton Commander" (but not excluding younger people) may also like the Far manager (http://www.farmanager.com), which is also available in 32 and 64 bit. It is a real text mode application, adapting to any arbitrary console window size. There are several plugins available, e.g. a Registry browser too. And it doesn't camouflage system directories with localized shell objects, it shows their real name on disk. Cool admin stuff!
Used to love Norton Commander - great interface at the time
WorBry
8th February 2016, 03:56
I'm just watching how things progress with:
http://forum.doom9.org/showthread.php?p=1756489#post1756489
Q-the-STORM
10th February 2016, 11:41
Is there a way to use UtVideo Pro YUV422 10bit in Premiere Pro CC 2015?
I'd like to export to UtVideo Pro YUV422 10bit and then encode with x264, but in Premiere only RGB, RGBA, 420 bt601, 420 bt709, 422 bt601 and 422 bt709 are available...
umezawa_takeshi
10th February 2016, 17:58
Is there a way to use UtVideo Pro YUV422 10bit in Premiere Pro CC 2015?
Practically, NO. "UtVideo Pro YUV422 10bit" (UQY2) is almost useless at the moment.
In addition, x264 probably does not accept UQY2 (because libavcodec does not support it, either).
WorBry
12th February 2016, 19:30
Thanks for all of your responses. I haven't tried shekh's suggestion as yet....
You dont lose anything.
My algorithm would be:
go to
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32
Rename Drivers32 to Drivers32~ (for use as backup)
Make fresh Drivers32 key
make string value vidc.ulra = C:\Windows\system32\utv_vcm.dll
open 32bit VD and see it codec is listed
yes: move other keys from Drivers32~ key to Drivers32 one by one
no: roll back all changes by renaming Drivers32~ to Drivers32
IMO there is no need to restart system at any point.
and I will at some point; that said, I'm not exactly sure about the step "Make fresh Drivers32 key". How do I do that?
But for now I can transcode my clips to UTVideo RGB with FFMPEG, directly or piped from VapourSynth.
I have another question though about transcoding full scale (0-255) YV12 sources to UTVideo with FFMPEG. As mentioned in an earlier post:
http://forum.doom9.org/showpost.php?p=1755029&postcount=434
When transcoding native AVC HD clips (mov or mp4) from DSLR cameras recorded with full range (0-255) YV12 luma to UTVideo (YV12 or YUY2), the yuvj420p and yuvj422p pix_format designations are not accepted and FFMPEG reverts to yuv420p and yuv422p resulting in compression to limited 16-235 scaling. Same occurs with other lossless/near-lossless formats like HuffYuv, FFV1, ProRes, DNxHD e.g
ffmpeg -i path..../DSCN0968.MOV -vcodec utvideo -r 30000/1001 -pix_fmt yuvj420p -s 1920x1080 path...../DSCN0968_UTVYV12_Fullscale.mkv
ffmpeg log gives:
Incompatible pixel format 'yuvj420p' for codec 'utvideo', auto-selecting format 'yuv420p'
[swscaler @ 0x7d08e0] deprecated pixel format used, make sure you did set range correctly
In my tests the only two formats where the yuvj420p and yuvj422p pix_format are respected are uncompressed rawvideo (YV12, YUY2) and x264. Interestingly, when these transcodes are loaded into KdenLive and Clip Properties (metadata) are examined, they are reported as having yuv420p or yuv422p pix_format's despite being full scale. Whereas the original camera clips display the yuvj420p and yuvj422p pix_formats.
It occurred to me then that if I use the rawvideo transcodes as input for FFMPEG encoding to UTVideo it might be possible to preserve (pass-through) the full range scaling. Tried that and lo and behold that is the outcome, e.g.
ffmpeg -i path..../DSCN0968.MOV -vcodec rawvideo -r 30000/1001 -pix_fmt yuvj420p -s 1920x1080 path..../DSCN0968_RawYV12_Fullscale.mkv
then
ffmpeg -i path...../DSCN0968_RawYV12_Fullscale.mkv -vcodec utvideo -r 30000/1001 -s 1920x1080 path /DSCN0968_UTVYV12_Fullscale.mkv
So there is at least a way to transcode the native clips to UTVideo and preserve the full scale luma, at the cost of generating very large uncompressed intermediates.
My question is – is it possible to set up a single FFMPEG command that avoids this two stage process ? I'm afraid I don't have any experience with FFMPEG piping (other than basic piping out from VapourSynth with vspipe). My several attempts always result in FFMPEG crashing due to memory allocation problems.
Edit: sorry about the text formatting. I had to draft the post offline and it got messed up.
vBulletin® v3.8.11, Copyright ©2000-2025, vBulletin Solutions Inc.