search for: scanline

...r down Fast carrier up Coarse carrier frequency 1699.81 (66) Training error 3.356434 Training succeeded (constellation mismatch 2.404210) Fast carrier trained Feb 11 19:27:21 NOTICE[20570]: chan_sip.c:7531 handle_request: Fast carrier down Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline 955 (got 1906, expected 1728). Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline 962 (got 2596, expected 1728). Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline 963 (got 1731, expected 1728). Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline...

...ards), sending a fax from an HO d135 all-in-one and tried a second Brothers "dumb" fax with the same results. Everything was compiled today and the non-fax asterisk is running just fine. Here's what appears to be a problem: Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline 0 (got 3198, expected 1728). Any help would be nice. Jon Here's the console log for the fax receive: -- Executing Answer("Zap/11-1", "") in new stack -- Accepting call from '8131231234' to '8133214321' on channel 0/11, span 1 -- Executing SetV...

...DLC underflow in state 5 Post trainability Changed from phase 4 to 5 Fast carrier up Coarse carrier frequency 1699.99 (66) Training error 9.098502 Training succeeded (constellation mismatch 8.396236) Fast carrier trained Fast carrier down Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline 251 (got 3285, expected 1728). Fax3Decode2D: (FakeInput): Uncompressed data (not supported) at scanline 252 (x 224). Fax3Decode2D: Warning, (FakeInput): Premature EOL at scanline 252 (got 224, expected 1728). Fax3Decode2D: (FakeInput): Bad code word at scanline 253 (x 1647). Fax3Decode2D: Warning,...

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

...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 the bash results in the following error Error in function (handle) : GDAL Error 1: TIFFReadDirectory:/tmp/RtmpPCALnL/file265f67a6: cannot handle zero scanline size Calls: <Anonymous> -> .Call Execution halted The scripts halts, although there are more images to process. The question is why the script halts and why the script is not halted (but still "decorated" with errors) when releasing it within the R console like so R CMD source...

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 helper drm_mode_size_dumb() that calculates scanline pitch and buffer size according to driver requirements. The series fixes the common GEM implementations for DMA, SHMEM and VRAM. It further changes most imple...

...d 448 MB RAM. I tried the same kernel without SMP. I tested with a HP OfficeJet 490 as well as with Hylafax-server/#ComUSR 56k faxmodem, both connected to an BT ATA286 and answered by my * box. Page is A4 on HP, and for Hylafax, I just send the faxcover. Everything is fine and then starting at scanline 1287 (changing from test to test but always around scanline 1200) [...] Fax3Decode1D: Warning, (FakeInput): premature EOL at scanline xxxx ( got xxxx, expected xxxx). or Fax3Decode1D: (FakeInput): Bad code word at scanline yyyy (x yyyy). or Fax3Decode1D: Warning, (FakeInput): line length mismatc...

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. There's currently quite a bit of code duplication >> among DRM's memory managers. Each calculates scanline pitch and >> buffer size...

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...

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....

...MMR Apr 4 16:49:59 localhost FaxGetty[6110]: MODEM Supports no ECM Apr 4 16:49:59 localhost FaxGetty[6110]: MODEM Supports T.30 Annex A, 64-byte ECM Apr 4 16:49:59 localhost FaxGetty[6110]: MODEM Supports T.30 Annex A, 256-byte ECM Apr 4 16:49:59 localhost FaxGetty[6110]: MODEM Supports 0 ms/scanline Apr 4 16:49:59 localhost FaxGetty[6110]: MODEM Supports 5 ms/scanline Apr 4 16:49:59 localhost FaxGetty[6110]: MODEM Supports 10 ms, 5 ms/scanline Apr 4 16:49:59 localhost FaxGetty[6110]: MODEM Supports 10 ms/scanline Apr 4 16:49:59 localhost FaxGetty[6110]: MODEM Supports 20 ms, 10 ms/scanli...

...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 vary, it sometimes saves the file in which case i get errors: Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline 0 (got 2383, expected 1728). Fax3Decode2D: (FakeInput): Bad code word at scanline 1 (x 137). and the resulting tif looks to be only a few rows long or more commonly it just fails entirely.. i paste the output below so you can see. is there anything obvious i'm doign wrong here? TIA! Steve....

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 offset...

...just slightly garbled. At first I thought this was a mechanical problem at the printer (for weeks), but just this morning I took a closer look and realized everything was too regular for it to be a mechanical failure (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 invisi...

...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 is only one scanline long. I am using asterisk CVS head of 2004-06-01 and spandsp-0.0.1k. A logfile from the console is attached below. May I kindly ask you to have a quick look at it? Many thanks, Jan Changed from phase 0 to 1 Slow carrier up Slow carrier down Slow carrier up Slow carrier down Slow carrier up...

...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 pix...

...d 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 vary, it sometimes saves the file in which case i get > errors: > Fax3Decode2D: Warning, (FakeInput): Line length mismatch at scanline 0 (got > 2383, expected 1728). > Fax3Decode2D: (FakeInput): Bad code word at scanline 1 (x 137). > > and the resulting tif looks to be only a few rows long > > or more commonly it just fails entirely.. i paste the output below so you can > see. is there anything obvious i...

...* 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 o...

...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...