search for: scanlines

>From couple of weeks i am working on asterisk fax but was not successful. I am able to receive only half fax documents and its ending with blurred lines. I have tried with almost all the versions of spandsp 0.0.2pre4,pre10 etc but of no use. I have digium card to which i have plugged in 2 pstn lines and i have removed echocancellation too(zapata.conf) and also enabled g7111 alaw&Ulaw

I'm trying to install the RxFax in Asterisk. After much trouble getting app_rxfax.c (and friends) compiles and installed into Asterisk (thanks to the many asterisk-users messages) it did get it installed. I have been unable to receive a legible fax. app_rxfax provides lots of debugging information but none useful to me. I was hoping that someone has an idea what might be going on.

more detailed output Sep 21 15:54:31 DEBUG[1120357296]: pbx.c:1255 pbx_extension_helper: Launching 'RxFAX' Sep 21 15:54:31 DEBUG[1120357296]: channel.c:1699 ast_set_read_format: Set channel Zap/1-1 to read format SLINR Sep 21 15:54:31 DEBUG[1120357296]: channel.c:1666 ast_set_write_format: Set channel Zap/1-1 to write format SLINR Changed from phase 0 to 1 Slow carrier up Slow carrier

I'm running asterisk CVS HEAD from 20040601 with spandsp 0.0.1k and libtiff 3.6.0 (no other copies are installed). I've put the audio files up at http://www.mixdown.ca/~andrew/dump/akohlsmith-faxsegfault.tgz -- the machine I am faxing from is a Canon IR3300 printer/copier/fax, but I get similar crashes from $29.95 fax machines too. :-) I'm trying to get a decent backtrace but

Dear Everyone, I am using R 2.6.2 on my Redhat AS4. I installed the RPM offered on the cran website. I would like to use R from my bash console with the following command: /path/to/R --vanilla --slave --args < /data/myscript.R this script invokes a range of functions and tools, among others to process a bunch of raster images in a loop using GDAL. The thing is that releasing this command in

Dumb-buffer pitch and size is specified by width, height, bits-per-pixel plus various hardware-specific alignments. The calculation of these values is inconsistent and duplicated among drivers. The results for formats with bpp < 8 are incorrect. This series fixes this for most drivers. Default scanline pitch and buffer size are now calculated with the existing 4CC helpers. There is a new

Good evening all, to complete test that I made in august (and which where discussed here) about garbage when receiving fax, I went more down in my tests. At first, my setup is an * CVS-HEAD-09/08/04, spandsp-0.0.1k, X100P (Tiger Jet Network Model 300 128k), kernel 2.4.26 on an SMP SoftRaid machine (2x400Celeron 400) and 448 MB RAM. I tried the same kernel without SMP. I tested with a HP

Hi Am 10.01.25 um 02:49 schrieb Andy Yan: > Hi Thomas, > > At 2025-01-09 22:56:56, "Thomas Zimmermann" <tzimmermann at suse.de> wrote: >> Add drm_modes_size_dumb(), a helper to calculate the dumb-buffer >> scanline pitch and allocation size. Implementations of struct >> drm_driver.dumb_create can call the new helper for their size >> computations.

Call drm_mode_size_dumb() to compute dumb-buffer scanline pitch and buffer size. The hardware requires the framebuffer width to be a multiple of 8. The scanline pitch has be large enough to support this. Therefore compute the byte size of 8 pixels in the given color mode and align the pitch accordingly. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> Cc: Philipp Zabel <p.zabel

Call drm_mode_size_dumb() to compute dumb-buffer scanline pitch and buffer size. The hardware requires the scnaline pitch to be a multiple of 32 pixels. Therefore compute the byte size of 32 pixels in the given color mode and align the pitch accordingly. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> Cc: Rob Clark <robdclark at gmail.com> Cc: Abhinav Kumar <quic_abhinavk

I'm able to recieve fax with pure SpanDSP 0.0.2 + Asterisk successfully but I have problems with some fax machine so I wanted to try using HylaFax to recieve Fax instead of SpanDSP hoping that it'll solve my problem. I'm trying to connect Asterisk with SpanDSP using iaxmodem. My system looks like this: ISDN <---> Asterisk <---> IAXModem <---> Hylafax Asterisk

Hi, I just sent this to Steve Underwood, but then found a bunch of posts on the mailing list about similar issues.. does anyone have the fix? I'm running asterisk CVS-HEAD-06/28/04-18:13:13, spandsp 0.0.1k, libtif 3.5.7 one thing i just noticed is that calls come in with format '72' which is G711A-law or LinearPCM.. it uses PCM for the call, i assume this is ok the results of RxFAX

Release 2.21.5 (2013-03-21) =========================== Haswell reintroduces a command to load the scanline window from the command stream and so requires its own specialised wait-for-vsync routine - failure to do so was then causing hangs when trying to do tearfree video or use a compositor. * Prevent buffer leak if a non-fullscreen Window is closed with multiple pending swap events. * Fix

...ink smearing or something). Anyway the problem is that the bottom non-empty scanline of _very_ many letters/digits/symbols gets transposed over ontop of the topmost non-empty scanline of the same character. This results in the following conversion (rough ascii art - note there's a lot more scanlines involved due to far higher resolution, which means this is far more invisible). | AA | | AA AA | | AAAA | | AAAA | | AA AA | => | AA AA | | AAAAAAAA | | AAAAAAAA | | AA AA | | AA AA | | AA AA | | AA...

Hi, so far I had our PRI line connected via Digium TE410P and ZAP channel to asterisk which worked perfectly. I now have a second line coming in through a H.323 gateway and chan_oh323. rxfax() still works and receives faxes with G.711 alaw codec, but I always get one empty first page via H.323 - a one-page-fax becomes a two-page-fax with one empty page in front of it. It seems the empty page

...f4 On Fri, 2020-03-27 at 16:29 -0400, Lyude Paul wrote: > Adding Tejun to this thread per-Daniel's suggestion on IRC. > > Hi Tejun! So, I don't know what your experience with modesetting related > stuff > is so I'll quickly explain some important concepts here regarding scanlines, > vblanks, etc. If you already understand this, feel free to skip this next > paragraph. > > From the perspective of a computer, every time a computer monitor displays a > new frame it's done by "scanning out" the display image from top to bottom, > one row of pixe...

Sorry to bore you more with the clock issue, but have you check /proc/zaptel/<span> to make sure it's not missing interrupts? There's also an option to record the audio for the fax, you could listen to that vs a recorded file that will receive correctly on a fax machine and see whether there is an obvious difference? (Good luck, that'll be really scraping the barrel!!) Does it

...* scanout position query. Can be NULL to skip timestamp. + * mode: + * Current display timings. + * + * Returns vpos as a positive number while in active scanout area. + * Returns vpos as a negative number inside vblank, counting the number + * of scanlines to go until end of vblank, e.g., -1 means "one scanline + * until start of active scanout / end of vblank." + * + * Returns: + * + * True on success, false if a reliable scanout position counter could + * not be read out. + */ + bool...

Adding Tejun to this thread per-Daniel's suggestion on IRC. Hi Tejun! So, I don't know what your experience with modesetting related stuff is so I'll quickly explain some important concepts here regarding scanlines, vblanks, etc. If you already understand this, feel free to skip this next paragraph. >From the perspective of a computer, every time a computer monitor displays a new frame it's done by "scanning out" the display image from top to bottom, one row of pixels at a time. which row of...

...00, Lyude Paul wrote: > > Adding Tejun to this thread per-Daniel's suggestion on IRC. > > > > Hi Tejun! So, I don't know what your experience with modesetting related > > stuff > > is so I'll quickly explain some important concepts here regarding > > scanlines, > > vblanks, etc. If you already understand this, feel free to skip this next > > paragraph. > > > > From the perspective of a computer, every time a computer monitor displays > > a > > new frame it's done by "scanning out" the display image from...