-
dcoder_ committed patchset 146 of module DSPACK to the DSPack CVS repository, changing 1 files.
2008-11-13 17:23:25 UTC by dcoder_
-
go to www.progdigy.com the dspack forums have all the info you need.
2008-06-08 11:05:02 UTC by nobody
-
3 new package DPRs to handle Delphi 2007 compilation, a new jedi.inc file to extend the compiler definitions to D8, D2005, D2006, D2007, and a change to DSEditors to take the existing definitions from Jedi.inc instead of reinventing that wheel. To be placed back in the relevant directories.
2007-10-07 03:40:39 UTC by lesimard
-
Hi.
This problem also happens for me too. SOMEBODY CAN HELP, please?.
2007-06-29 19:47:01 UTC by nobody
-
Hi,
this Problem comes from the Qdvd.dll on my system it wasnt registered, after reigstering it again, all runs perfectly.
2007-05-30 08:36:48 UTC by nobody
-
This is not a bug, Quicktime is one thing and DShow another one. You can not run Quicktime format on DShow with out appropriated codecs.
2007-04-29 21:34:49 UTC by cryptonome
-
This is not a DSPack ERror, i have the same problem on one PC, but PowerDVD has the same Problem on this PC, this must be a DirectX or Codec Problem
Cylence@gmx.de.
2007-04-20 07:32:14 UTC by nobody
-
Will there be an update fior Vista?
Taking projects in Delphi 2006 and running them on Vista, the video is flipped upside down. Works OK on all older versions of Windows.
2007-04-05 19:09:44 UTC by nobody
-
I am using DSPack V2.3.4 for video display and capture.
Most of time, it worked fine. But sometimes, I got bad captured image.
I used TSampleGrabber.GetCurrentBuffer to get the YUV data and convert it to BMP file. Is there any bug in TSampleGrabber.GetCurrentBuffer that will cause bad captured image?
Thanks in advance.
Feng Wang
Email: fwang11@pub3.fz.fj.cn
2007-03-16.
2007-03-16 01:59:40 UTC by nobody
-
I found 3 Memory leaks using memcheck:
Added the following Code to TDSVideoWindowEx2.Destroy:
// Was created but never freed.
FFullScreenControl.Free;
// The Filter is automatically Added via SetFilterGraph but never cleared.
FFilterGraph.RemoveFilter(self);
FFilterGraph.RemoveEventNotifier(self);
After that the memory leak was gone.
Kind regards.
2007-02-14 11:32:08 UTC by rh-phoenix