Welcome Guest ( Log In | Register )


Important

The forums will be closing permanently the weekend of March 15th. Please see the notice in the announcements forum for details.

 
Input Vs Output Panes
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
shekh
Posted: Dec 17 2014, 09:00 PM


Advanced Member


Group: Members
Posts: 89
Member No.: 37903
Joined: 21-April 14



Just noticed that when I click "play input" the pixel format is temporarily changed to RGB for the duration of playback.
This does not happen with "play output". Without any plugins both panes seem identical. Does it have simple explanation why they behave differently?
I began to switch to input pane once I realized that "scan scene" buttons actually do something.. again what is the explanation they dont work with output pane?
 
     Top
Abrazo
Posted: Dec 17 2014, 09:09 PM


Advanced Member


Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10



1) Change to RGB during playback
I don't know for sure, but verify in VirtualDub, via the Options-menu > Preferences > Main, that the "Output color depth" is set to "Match display depth" instead of "Fastest (16 bit)".

2) Scan for scene change
I suppose that this is "by design". It has no use to search for a scene change in "two" panels that are displaying the same video at the same time, ... one panel should be sufficient for that.
 
     Top
dloneranger
Posted: Dec 17 2014, 09:35 PM


Moderator


Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07



On play input, virtualdub just decodes to the screens format (rgb) as it doesn't use the filter list at all, so doesn't have to do any conversions etc

On play output, the frames traverse the filter list and go through all the implicit conversions

Basically it's just an optimization

Scan scene's just for quickly finding scene changes and fades
It's pointlessly expensive to traverse the filter list, plus filters could stop it working altogether
eg
you may blend a fill to produce a fade in, then scene scan to where you want to do a fade out
If it operated on the output, then it'd never find the scene change as it's all black now

You have to remember that the filter list may be incredibly slow, it may have IVTC, temporal cleaners etc that all do a lot of seeking to produce just 1 frame of output
If it can be avoided then that's normally a good thing

--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3
 
    Top
shekh
Posted: Dec 17 2014, 09:51 PM


Advanced Member


Group: Members
Posts: 89
Member No.: 37903
Joined: 21-April 14



Interesting.
The default "0" format is selected during still frame and scene scan, but only when I click "play" it is changing to rgb "7".
Changed the option Preferences->Output color depth to "use output setting".
The selected format changed to "0"!
But it does not play. I got message:
CODE

The current output video format is not supported by the selected output path.


For the scene scan I didnt mean to scan filter output, just the same thing but apply filters on top. Makes sense when output is the only visible pane.
 
     Top
dloneranger
Posted: Dec 17 2014, 10:01 PM


Moderator


Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07



Best thing's to check the sourcecode
Play input, it's hardcoded
CODE
switch(g_prefs.main.iPreviewDepth) {
case PreferencesMain::DEPTH_DISPLAY:
 {
  DEVMODE dm;
  dm.dmSize = sizeof(DEVMODE);
  dm.dmDriverExtra = 0;
  if (!EnumDisplaySettings(NULL, ENUM_CURRENT_SETTINGS, &dm))
   dm.dmBitsPerPel = 32;

  switch(dm.dmBitsPerPel) {
  case 24:
   dubOpt.video.mInputFormat = nsVDPixmap::kPixFormat_RGB888;
   break;
  case 32:
   dubOpt.video.mInputFormat = nsVDPixmap::kPixFormat_XRGB8888;
   break;
  default:
   dubOpt.video.mInputFormat = nsVDPixmap::kPixFormat_XRGB1555;
   break;
  }
 }
 break;
case PreferencesMain::DEPTH_FASTEST:
case PreferencesMain::DEPTH_16BIT:
 dubOpt.video.mInputFormat = nsVDPixmap::kPixFormat_XRGB1555;
 break;
case PreferencesMain::DEPTH_24BIT:
 dubOpt.video.mInputFormat = nsVDPixmap::kPixFormat_RGB888;
 break;

// Ignore: PreferencesMain::DEPTH_OUTPUT

};

dubOpt.video.mOutputFormat   = dubOpt.video.mInputFormat;


You could add a request to phaeron for scene scan to work on the output pane if it's the only visible one?

--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3
 
    Top
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
4 replies since Dec 17 2014, 09:00 PM Track this topic | Email this topic | Print this topic

<< Back to VirtualDub Development Forum