Frage von Andre Ludewig:
Hi folks,
am a newbie here and maybe my question is quite easy to
Reply ...
Did my first attempts started, of my JVC GR-D23E via firewire
to grape with:
- Windows Movimaker
- Premiere 6.0
- The supplied Capture-/Schnittprogi of JVC
In all cases I get after the recording is not the most
720x576 pixels set in the (dry!) File. Windows claims
While in the file properties but it would be 720x576 for display only
the 360x288! In the file properties when playing on the (old)
Windows Media Player is strangely synonymous then these small values.
I can only see something wrong? MiniDV If there is something systemic
extrapolated? Is my firewire input lazy (too slow?). Do I have a
Driver problem?
On my old VAIO Schläppi grappt Windows Movimaker incidentally, of the
Camera also only 360x720!
Have tried everything now and hope to here a few helpful hints.
The detour via S-Video capture card and I wanted to actually not
go ...;-)
Thank you ever
and greetings from the Baltic Sea beach
André Ludewig
Antwort von Carla Schneider:
Ludewig Andre wrote:
>
> Hi folks,
>
> Am a newbie here and maybe my question is quite easy to
> Answer ...
>
> I started my first attempts, of my JVC GR-D23E via firewire
> To grape with:
> - Windows Movimaker
> - Premiere 6.0
> - The supplied Capture-/Schnittprogi of JVC
>
> In all cases I get after the recording is not the most
> 720x576 pixels set in the (dry!) File. Windows claims
> While in the file properties but it would be 720x576 for display only
> The 360x288! In the file properties when playing on the (old)
> Windows Media Player is strangely synonymous then these small values.
>
> I can only see something wrong? MiniDV If there is something systemic
> Extrapolated? Is my firewire input lazy (too slow?). Do I have a
> Driver problem?
About the Firewire input 720x576 DV video in, something else may
the Camera does not.
If the software is synonymous then the video as a DV-avi dv capture raw or would,
there would be nothing to synonymous change.
But if the program the video in another format (eg mpeg) Convert
, it is possible depending on the hardware that it is not full size
can create very well but the half, because of the camera, the video
only in real time.
Remedy: The video in DV format and then convert.
> On my old VAIO Schläppi grappt Windows Movimaker incidentally, of the
> Camera only 360x720!
--
http://www.geocities.com/carla_sch/index.html
Antwort von Andreas Erber:
Ludewig Andre wrote:
> Hi folks,
>
> Am a newbie here and maybe my question is quite easy to
> Answer ...
>
> I started my first attempts, of my JVC GR-D23E on
> Firewire to grape with:
> - Windows Movimaker
> - Premiere 6.0
> - The supplied Capture-/Schnittprogi of JVC
>
> In all cases I get after the recording is not the most
> 720x576 pixels set in the (dry!) File. Windows
> Claims in the file properties it would be 720x576 but to
> Display, only 360x288! In the file properties in the
> Play on the (old) Windows Media Player is strangely
> Then synonymous these small values.
>
> I can only see something wrong? MiniDV If there is something systemic
> Extrapolated? Is my firewire input lazy (too slow?). I
> A driver problem?
> On my old VAIO Schläppi grappt Windows Movimaker incidentally
> Of the Camera also only 360x720!
>
Alternate times to uncompressed Avi records may klappts then? At least
the P4 2500 MHz avi packed full resolution not to compress.
LG Andy
Antwort von Alexander Blinne:
The DirectShow filter fà ¼ r of Microsoft DV decode standard DV ¤ Ãxig
at half charge ¶ sung to interlace artifacts to hide. Ordinary
Players such as Media Player Classic (no, that is not of Microsoft)
to show a configuration of the filter, which is then full
¶ charge measurement can switch.
Antwort von Andre Ludewig:
First, many thanks for the answers!
> Alternate times to uncompressed Avi records may klappts then?
Sure, I had already made ...
> Workaround: The video in DV format and then convert.
synonymous I have done!
> The DirectShow filter for decoding of Microsoft DV DV standard
> On half resolution to interlace artifacts to hide.
Aha! That is sometimes an interesting statement!
Now I'm only pushed to this phenomenon, since, after cutting in
Premiere extreme artifacts (edition: with uncompressed avi 720x576)
occurred.
Frame example here: http://www.katjusch.de/720erausgabe.jpg
Take a look at these awful horizontal lines at the edges with large
Contrast jumps!
After dragging the original file into ribbed cut window I get
following properties:
"Average data rate 3,66 MB / sec
Image size 720x576
24 bit color depth
Pixel Ratio 1:1,067
25 frames / sec!
If I select 360x288 project settings, there is no such
Artifacts! The corresponding sample frame (Comparison with the subsequently
inflated to 720x576 resolution) shows the good:
http://www.katjusch.de/360erausgabe.jpg
Am I now a setting in Premiere overlooked?
Regards
André
Antwort von Birger Jesch:
Andre Ludewig "
wrote ...
> First, thanks for the answers!
>
>> Set times to uncompressed Avi records may klappts then?
> Sure, I had already made ...
That is nonsense. DV-AVI should be synonymous as such into the system.
>
>
>> The DirectShow filter for decoding of Microsoft DV DV standard
>> At half resolution to interlace artifacts to hide.
>
> Aha! That is sometimes an interesting statement!
Exactly. For the media player (yes, of the Windows), there is actually a
Registry setting. Where in the miniFAQ directly over (or under) your contribution.
> Now I'm only pushed to this phenomenon, since, after cutting in
> Premiere extreme artifacts (edition: with uncompressed avi 720x576)
> Occurred.
> Example frame here: http://www.katjusch.de/720erausgabe.jpg
These are not artifacts, but in the fast movements occurring
interlacten fields. Perfectly normal and only (and only there!) On a
PC monitor to see.
> Take a look at these awful horizontal lines at the edges with large
> Contrast jumps!
Keyword interlacing.
>
> After dragging the original file into ribbed cut window I get
> Following properties:
> "Average data rate 3,66 MB / sec
> Image size 720x576
> 24 bit color depth
> Pixel Ratio 1:1,067
> 25 frames / sec!
So DV-AVI, as it should be.
>
> If I select 360x288 project settings, there is no such
> Artifacts! The corresponding sample frame (Comparison with the subsequently
> Inflated to 720x576 resolution) shows the good:
> http://www.katjusch.de/360erausgabe.jpg
Logically, this is so synonymous every 2nd Line, ie a full half omitted.
>
> Am I now a setting in Premiere overlooked?
no.
>
> Greetings
> André
>
Gruss Birger
Antwort von Andre Ludewig:
> These are not artifacts, but with quick movements
> Occurring interlacten fields. Perfectly normal and only
> (And only there!) On a PC monitor to see.
For an exclusive look at the PC monitor, I can
Avi worked from a DV source only save as 360x288?
... shame!
Antwort von Carla Schneider:
Ludewig Andre wrote:
>
>> These are not artifacts, but with quick movements
>> Occurring interlacten fields. Perfectly normal and only
>> (And only there!) On a PC monitor to see.
>
> For an exclusive look at the PC monitor, I can
> Avi worked from a DV source only save as 360x288?
No, it is synonymous the full 720x576 resolution but with quick movements
Picture can be seen in the comb artifacts if for no deinterlacing Watch Cool
used.
But because gasoline normal user is stupid to understand this, just take
360x288 by default, people who would want it otherwise, just pay the cost of the move,
but then synonymous know what they do.
> ... Shame!
--
http://www.geocities.com/carla_sch/index.html
Antwort von Birger Jesch:
Andre Ludewig " wrote ...
>> These are not artifacts, but with quick movements
>> Occurring interlacten fields. Perfectly normal and only
>> (And only there!) On a PC monitor to see.
>
>
> For an exclusive look at the PC monitor, I can
> Avi worked from a DV source only save as 360x288?
> ... Shame!
No, for an exclusive viewing on the PC (since I currently falls
only slightly in the direction Muldimedia CD), _muss_ you deinterlace.
In addition, your wrong format 360x288, since DV Videodas Display --
Aspect-ratio <> Pixel Aspect Ratio is. Correct would be 384x288, otherwise
are all (round) balls to eggs. After the deinterlacer can then
actually (almost) any image, eg. 640x480 etc.
The only important thing is that the image size an integer multiple of 2 is because
many codecs in YUV (4:2:2)-color work, some (particularly MPEG & Co)
may not only be 8 or 16 frame sizes divisible (keyword Quantization,
Macro blocks etc).
Birger
>
>
Antwort von Alexander Blinne:
Birger Jesch wrote:
>
> No, fà ¼ r an exclusive look at the PC (fà ¤ llt mir da moment
> Only slightly in the direction Muldimedia CD), _muss_ you deinterlace.
> In the à ¼ brige is your format 360x288 wrong, because DV Videodas Display --
> Aspect ratio <> Pixel Aspect Ratio is. True would re ¤ 384x288, otherwise
Still not quite right, of the 720 pixel in DV, only 704
Active Area and 4:3. the 720x576 entsprà ¤ chen So then 392x288.
You should try this for the sake of simplicity but simply erstmel at 704
cropping and then take it back 384.
Antwort von Birger Jesch:
"Alexander Blinne" wrote ...
> Birger Jesch wrote:
>>
>> No, fà ¼ r an exclusive look at the PC (fà ¤ llt mir da moment
>> Just in the direction Muldimedia CD), _muss_ you deinterlace.
>> In the à ¼ brige is your format 360x288 wrong, because DV Videodas Display --
>> Aspect ratio <> Pixel Aspect Ratio is. True would re ¤ 384x288, otherwise
>
> Still not quite right, of the 720 pixel in DV, only 704
> Active Area and 4:3. the 720x576 entsprà ¤ chen So then 392x288.
> You should try this for the sake of simplicity but simply erstmel at 704
> Cropping and then take it back 384.
Yes, it is exactly correct. ;-)
Gruss Birger
Antwort von Andre Beck:
Andre Ludewig " writes:
>> These are not artifacts, but with quick movements
>> Occurring interlacten fields. Perfectly normal and only
>> (And only there!) On a PC monitor to see.
>
> For an exclusive look at the PC monitor, I can
> Avi worked from a DV source only save as 360x288?
No.. You have three options:
a) To what it's like to play and something that will do the job
truly mastered, so a built in deinterlacer to 50fps
aufweist. Preferably an adaptive, Motion Compensation to be
such dormant.
b) Before deinterlace to 50fps, with the material, however, new
encoded and in the space bigger.
c) Before deinterlace to 25fps, with the material, however, in the
Time resolution is halved. That incidentally is still synonymous newly encoded
is because even the lesser of two evils.
> ... Shame!
No.. You want to learn what is interlaced and how to get the best out
makes.
--
The _S_anta _C_laus _O_peration
or "how to turn a complete illusion into a neverending money source"
-> Andre "ABPSoft" Beck ABP-RIPE Dresden, Germany, Spacetime <--
