similar to: BlockSize Length in Vorbis Encoder

Hi All, Can any one link me or send me a complete detailed spec of Vorbis encoder? I found the Vorbis_I_spec.pdf but it does not provide much information about encoding procedure. Ravi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/vorbis/attachments/20050829/cf209e5a/attachment.html

Hi All, Sorry if this is too much silly. Vorbis encoder gives out packets of information. 1. Is it that each packet contain information of one frame/window either 256 / 2048 or any length set by encoder? If yes then the encoded packet will be variable in length. 2. Every packet is divided into segments, how does the encoder decide on number of segments in each packet? It must be dependent upon

Hi, If this is true: "Granule Position Information in Ogg Header is a hint for the decoder and gives some timing and position information." So say if granule position is 10000, it means that 10000 PCM samples are encoded in this page approximately. If this is true we can neglect this information, it will not effect the decoding right(but might effect for streaming)? Ravi

Hi, can someone explain whats the meaning of the two blocksizes in the first header of Vorbis, please? So far I assumed that they meant that 2^b0 and 2^b1 were the only two blocksizes used during the whole encode, but something makes me believe they are not: if b0 and b1 are 0xb8 respectively (that I interpeted as 2^11 = 2048 and 2^8 = 256) I observe 3 different deltas between each couple of

--- filters/blocksize/nbdkit-blocksize-filter.pod | 4 ++-- filters/blocksize/blocksize.c | 19 +++++++++++++++++++ 2 files changed, 21 insertions(+), 2 deletions(-) diff --git a/filters/blocksize/nbdkit-blocksize-filter.pod b/filters/blocksize/nbdkit-blocksize-filter.pod index b6cf4dd..0abed2f 100644 --- a/filters/blocksize/nbdkit-blocksize-filter.pod +++

I examined each filter to see which ones implement a cache and do not properly consider consistency across clients for flush requests. For these filters we should force .can_multi_conn to return false. I believe only one filter (blocksize) needs to be updated and all the other ones are safe. --- filters/blocksize/blocksize.c | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git

Hi, I am using Microsoft Word Viewer to view documents via wine. CUPS is installed and working perfectly. But when I try to print via Word Viewer, it says no printer found :(. I checked the config file in wine, and its shows that CUPS is present. Kindly let me know how to get it working :) -Regards Anurag __________________________________________________________ Give your Company an email

Hi! I'm going to build a maildir-based mailserver with a ~56 gb mail-partition. What blocksize/bytes-per-inode/number of inodes should i use (i don't want to ran out of inodes and don't want to sacrifice too much space for filefragments)? Is there a drawback when lowering the blocksize/increasing the number of inodes (except the maximum filesystem size)? The inodes used by a file is

пн, 24 лют. 2020 о 22:53 Richard W.M. Jones <rjones@redhat.com> пише: > > Since the blocksize option was added since the minimum version of > libguestfs for virt-v2v, we need to make it conditional so that > virt-v2v can still be compiled with the older libguestfs. > > This commit does the minimum fix to make it build. It doesn't > conditionalize the --blocksize

Hi, I want to use an ext3 Partition (~1TB) for Mail Storage, this means tons of small files. Has anyone recommendations about blocksize, inodes, etc. for mkfs.ext3 ? Thanks in advance, David -- View this message in context: http://www.nabble.com/Ext3----which-blocksize-for-small-files--tf2601442.html#a7257363 Sent from the Ext3 - User mailing list archive at Nabble.com.

On 1/5/19 8:50 AM, Richard W.M. Jones wrote: > I examined each filter to see which ones implement a cache and do not > properly consider consistency across clients for flush requests. For > these filters we should force .can_multi_conn to return false. > > I believe only one filter (blocksize) needs to be updated and all the > other ones are safe. > --- >

Allow `launch` call to accept an optional argument, called `blocksize`. Example: $ guestfish --listen -a raw.img $ guestfish --remote -- launch blocksize:4096 The actual qemu command is: [...] -device virtio-scsi-ccw,id=scsi -drive file=raw.img,cache=writeback,id=hd0,if=none -device scsi-hd,drive=hd0,physical_block_size=4096,logical_block_size=4096 [...] Signed-off-by: Tuan Hoang

From: Nikolay Ivanets <stenavin@gmail.com> This patch adds '--blocksize' command line option for virt-make-fs tool. This option allows specifying disk sector size as described in 'guestfs_add_drive_opts' libguestfs API. --- make-fs/make-fs.c | 28 ++++++++++++++++++++++++++-- make-fs/test-virt-make-fs.sh | 5 ++++- make-fs/virt-make-fs.pod | 10 ++++++++++

Hi I've got serious problem with my Vorbis-Decoder. The error seems to happen in the inverse Mdct. Before the imdct the values seems to be correct (compared with those of jOrbis (www.jcraft.com/jorbis/)). But after the transformation the values shows a strange behaviour. In [0, blocksize/2] the values are correct, but in [blocksize/2, blocksize] the values are wrong. The difference in

From: Nikolay Ivanets <stenavin@gmail.com> This patch adds '--blocksize' command line option for virt-make-fs tool. This option allows specifying disk sector size as described in 'guestfs_add_drive_opts' libguestfs API. --- make-fs/make-fs.c | 30 ++++++++++++++++++++++++++++-- make-fs/test-virt-make-fs.sh | 5 ++++- make-fs/virt-make-fs.pod | 10 ++++++++++

From: Nikolay Ivanets <stenavin@gmail.com> This patch adds '--blocksize' command line option for virt-get-kernel tool. This option allows specifying disk sector size as described in 'guestfs_add_drive_opts' libguestfs API. --- get-kernel/get_kernel.ml | 22 ++++++++++++---------- get-kernel/virt-get-kernel.pod | 8 ++++++++ 2 files changed, 20 insertions(+), 10

Since the blocksize option was added since the minimum version of libguestfs for virt-v2v, we need to make it conditional so that virt-v2v can still be compiled with the older libguestfs. This commit does the minimum fix to make it build. It doesn't conditionalize the --blocksize option altogether. However I believe, at least for virt-v2v, that is OK since the --blocksize option is not used

Hi, I made an ext3 filesystem with 8kB block size: # mkfs.ext3 -T largefile -v -b 8192 /dev/md0 Warning: blocksize 8192 not usable on most systems. mke2fs 1.38 (30-Jun-2005) Filesystem label= OS type: Linux Block size=8192 (log=3) Fragment size=8192 (log=3) 148480 inodes, 18940704 blocks 947035 blocks (5.00%) reserved for the super user First data block=0 290 block groups 65528 blocks per group,

From: Nikolay Ivanets <stenavin@gmail.com> v4 fixes issues found during code review: - whitespace-change-only hunks are removed - options are alphabetically orderred now v3 is just a spelling correction spotted by Eric Blake https://www.redhat.com/archives/libguestfs/2020-February/msg00111.html In v2 I've moved '--blocksize' parameter description into the separate file called

Dear Samba-Users, could you please help me with the following two questions: 1. How can I increase the maximum SMB-blocksize from currently 4 KByte to the "regular" 64 KByte with my Red Hat Samba-Client (The server is already configured to 64 KByte and with a Windows-client this SMB-blocksize can be used.) 2. How can I deactivate the buffer on the SMB-client, so that the same file is