similar to: More spec notes

Hello :-) I am trying to run the next script, it generates "random areas" inside a map of the american continent, and then plot it, it?s suppose that every frame gives you the evolution of the program but at some point it stops with the weirdest of the errors I?ve ever seen in R, I don?t even have a line like that :-| Error in if (random_matrix[x_list[random_sq] - 1,

Hi, is there an error in the last part of the algorithm describing how to read a floor1 header? According to point 18 and 19, the vector [floor1_class_dimensions] must have at least [floor1_partitions] elements, but when reading/computing these two values on the beginning of the header, they are not related to eachother, and my attempts to apply this algorithm to real ogg-files gives me

Hi! While implementing a Vorbis I decoder, I have found a few errors in the specification. After making the following changes everything works as advertised, thank you! Errata: 1.) In section 7.2.2 Floor1 header decode (on a side not wouldn't 7.2.2.1 be the logical number here, looking at the overall structure of the document?), step 21 element element ([j] + [floor1_values]) should

I've been tinkering (not very seriously) with writing a vorbis (and ogg) decoder from scratch using only the documentation. I've got as far as starting to decoding floor 1 without any problems. However, there's a problem in the floor 1 header decode. Specifically: 22) [floor1_values] = [floor1_values] + [floor1_class_dimensions] element [i] hould probably be: 22) [floor1_values] =

Hello I've got a question about list indexing. If anyone can help or point in the direction of some documentation, that'd be great. I've checked the Introduction to R and R language definition. Say you have a list of vectors: >

I?m sorry, in my last email I forgot to attach the data I?m using wich is a matrix of 175x175 filled with 0?s and 1?s 0 is the sea 1 is the continental land The script is area.r Thank you very much. Carlos L?pez -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -------------- next part -------------- An embedded and

I have undertaken a small project of writing a Vorbis decoder completely from the spec, with the goal of catching any errors, both typographically and algorithmically, in the spec. My "reference" decoder is also being written in an extremely methodical style, with practically no algorithmic optimization, such that it will be clear that every step has been copied exactly from the spec.

Hi According to vorbis I spec, there are several configurations. There are 2 formats of floor, 3 formats of residue and 3 look up types of VQ codebook, etc. I think to get all kinds of vorbis file with these configurations but what I have got from network only support some of the formats (Ex. floor1, residue 1 & 2, VQ lookup type0 & 1). I downloaded several freeware vorbis encoder

Sent: Sunday, June 07, 2009 5:43 PM Subject: Question about R an SPSS Dears Sirs: Venables, Smith and R-Development Core Team I am reading about the functional features of R statistical software, because I want to compare these progarm with the basic module of SPSS software. I would like to know if the R version 2.9.0 application is capable of read and procces entry files

Non of these errors occured in earliers versions of R. > library(tcltk) /usr/lib/dld.sl: Unresolved symbol: Tcl_GetVar2Ex (code) from /opt_local/opt/R/lib/R/library/tcltk/libs/tcltk.sl /usr/lib/dld.sl: Unresolved symbol: Tcl_GetString (code) from /opt_local/opt/R/lib/R/library/tcltk/libs/tcltk.sl /usr/lib/dld.sl: Unresolved symbol: Tcl_SetVar2Ex (code) from

A small feature request. When running the spec rake task, if any of the folders ''spec/models'', ''spec/controller'', or ''spec/views'' doesn''t exist or if they don''t contain any specs, the spec usage is printed. In my case I didn''t have a views directory. I was able to get rid of the usage output by creating the

Hello, I have two questions concerning floor1 encoding/decoding. First I'll ask about the FLOOR1_fromdB_LOOKUP table: what is it's purpose? Is it to convert the amplitude differences between [floor1_Y] values to a dB scale? And, if I'm right with that, here comes the 2nd question: when render_line0 is used to encode floor1, then floor1_inverse2 must be used in decode (in order to

Hello, I was printing some Floor1 X values from a test audio file, and the values that I've obtained look mostly like the following: [23,33,46,65,79,93,111,130,158,186,220,260,312,372,464,556,750,1024] => For long blocks [8,16,33,70,128] => For short blocks Obviously they are not in Hz, so, could someone please tell me what is the unit used? In the specs it's said that the Floor1

Hello, There is a bug in the current version of vorbis/lib/floor1.c. The line that says:- qsort(sortpointer,n,sizeof(int),icomp); should be:- qsort(sortpointer,n,sizeof(int *),icomp); But somebody probably fixed that already. :) Also, I'd like to know how I can encode a file using the channel coupling modes. oggenc doesn't have an option for that yet. Greetings,

Hello, I've read in a thread from this mailing list ( http://lists.xiph.org/pipermail/vorbis-dev/2009-September/020019.html) that the usage of FLOOR1_fromdB_LOOKUP table is to convert Floor1 values from a dB scale to a linear scale. In a dB scale, given a reference value, the other dB values are obtained from it, normally dB_value = 10log(p1/p0), where p0 is the reference value. Supposing p0

Hello, I've been "playing" a little with the floor1 encoding, and my game has posed me a question. I've been modifying (just curiosity) manually, and randomly (not too great modifications), the quantized [floor1_Y] values, just before coding them with the codebooks. As, if I'm not wrong, the [floor1_Y] obtained are then removed to get the residue vectors for each channel, I

Hi, We are two students doing project with Vorbis audio compression for our B.Sc studies. We have two questions: Our first question related to the floor1 inverse dB lookup table. As we understood the floor values encoded as offset integers (Y) from 1 to 256 and then used as index in the floor1_inverse_dB_table to get an encoded value. This value (denoted as X) is inverse of linear frequency so

Hello, You know, I always worry about the precision and the float constants... and there is a large lookup table in the floor1.c ... and I figure out a way to keep the code size and speed, but to improve the precision at this lookup table. (the difference is small, but audible) Here is the modifications in the floor1.c: tatic unsigned long FLOOR_fromdB_LOOKUP[256]={

Hi I just did an update to lates trunk ================= context "Given a generated venue_spec.rb with fixtures loaded" do fixtures :venues specify "fixtures should load two Venues" do Venue.should have(2).records end end ================== gives me ========== 1) TypeError in ''Given a generated venue_spec.rb with fixtures loaded fixtures should load two

Hi everyone, after having an extensive look at the reference decoder as well as the specification documents, I'd like to point out what I think to be some minor omissions/flaws in the latter, and suggestions for correcting them. --- #1: in vorbis-spec-floor1.html, packet decode: Between 14) and 15) a crucial step is missing. Please insert: 14a) [cval] >>= [cbits] ---- #2: in