search for: bytestream

...osix shell at the time of the edit/pipe, whatever? And what MPE filetype are you working on? Problem is that samba doesn't know anything about MPE filetypes (like fixed ascii, binary, etc), and when a posix program under MPE (like samba) accesses one of these files, it is doing so thru a 'bytestream emulator' provided by mpe. DEPENDING on what MPE filetype the original file is, this emulator is going to add crlf line termination to the file, etc... So Unless you are working strictly on bytestream type files, your results are going to be interesting. There are a couple of MPE specific co...

...ll Wendling wrote: > Chris rewrote the original LLVM bytecode into it's present bitcode form. The newer code is much smaller than the previous form. That would be my guess for why he chose to call it bitcode. Of course, he can say for himself. :-) The format is literally a bitstream, not a bytestream. See this document for more details: http://llvm.org/docs/BitCodeFormat.html -Chris

Hi, I want to take a .wav and generate a bytestream that I can feed direct to speex_decode(). The speexenc program appears to produce it wrapped up in an ogg stream, and it doesn't have any sort of "raw" mode. I've tried hacking on it to remove the ogg parts, but I must have got it wrong, as my decode dies after decoding 160 by...

.... It's reasonably trivial if the definition is that the forwarded-for extension chain happens once when agent connections are opened. Then the ssh process just needs to send the extension, wait for the reply (whether positive or not-supported), eat it, and move on with forwarding the remaining bytestream. -- Hector Martin "marcan" (marcan at marcan.st) Public Key: https://mrcn.st/pub

Am 30.09.2010 00:34, schrieb Chris Lattner: > > The format is literally a bitstream, not a bytestream. See this document for more details: > http://llvm.org/docs/BitCodeFormat.html Ah... something I always meant to ask: How does the LLVM infrastructure deal with the added overhead of packing/unpacking a bitstream? Ignore it since modern CPUs can deal with that? Some ingenious algorithm? Last...

...Ref`, I also provide *WritableThinStream* for cases where your data is not read-only. This is another area where functionality is provided that was not present in existing abstractions (i.e. writeability). I have several implementations of this class and some abstractions for working with them. *ByteStream* and *MutableByteStream* provide a concrete implementatino where the backing store is an `ArrayRef` or `MutableArrayRef`. *MappedBlockStream* (which is PDB specific) provides an implementation that seeks around a file, piecing together blocks from various locations in a PDB file. When a call to `...

...***A) APIs assume local codepage. We should do in llvm; - Treat pathstring in argv as blackbox. Never parse (char*)pathstring without any knowledge. - UTF8 would be useless on win32. Win32 does not manipulate utf8 implicitly in anywhere. - Path API should hold pathstring as API-native form (bytestream on unix, UCS2 wchar_t on win32). - Path should be manipulated as API-native form as possible. In future, we might consider "-finput-charset" and "-fexec-charset" on clang. Please consider an source file; //////// #include "むすめは/まおちゃん.h" char const literal[] = &quot...

...gt; > We should do in llvm; > > - Treat pathstring in argv as blackbox. Never parse > (char*)pathstring without any knowledge. > - UTF8 would be useless on win32. Win32 does not manipulate utf8 > implicitly in anywhere. > - Path API should hold pathstring as API-native form (bytestream on > unix, UCS2 wchar_t on win32). > - Path should be manipulated as API-native form as possible. Isn't it more straightforward to use utf-8 internally and use the conversion functions provided by the win32 API when calling other win32 API functions, and always call the wide versions of...

...serialization. mfplat: Implement attributes deserialization. mfplat: Print warning instead of fixme for unsupported interfaces in attributes object. mfplat: Remove typedef for attributes structure. mfplat: Implement media type wrapping. mfplat: Implement IStream-based bytestream object. mfplat: Set capabilities flags for IStream-based bytestream object. mfplat: Set default attributes for file-based bytestream object. mfplat: Add IMFGetService stub for file-based bytestream. mfplat: Create dummy descriptor using public API. mfplat: Add more att...

Anyone, can you say what was the reason to rename bytecode? I am still interesting in 2010/9/29 Duncan Sands <baldrick at free.fr> Hi Ariel, > As long as I know English the word "bit" is a "small pice", . Why in set of > documentation ir is "bytecode", in other set or llvm source is "bitecode"? > What is the right? Different people call the

Chris rewrote the original LLVM bytecode into it's present bitcode form. The newer code is much smaller than the previous form. That would be my guess for why he chose to call it bitcode. Of course, he can say for himself. :-) -bw On Sep 29, 2010, at 5:15 AM, Ariel Feinerman wrote: > Anyone, > > can you say what was the reason to rename bytecode? I am still interesting in >

I would guess that the sampleenc and sampledec programs (I think they're in the doc dir) would be closer to what you want. On Apr 28, 2004, at 3:18 PM, Gervase Markham wrote: > Hi, > > I want to take a .wav and generate a bytestream that I can feed direct > to speex_decode(). The speexenc program appears to produce it wrapped > up in an ogg stream, and it doesn't have any sort of "raw" mode. I've > tried hacking on it to remove the ogg parts, but I must have got it > wrong, as my decode dies a...

...3. The third page is marked (cont) because it contains data that continues a previous packet. Specifically it contains only one segment, the last 1388 bytes of the setup header. So to extract the setup header you need to get the two segments of 3570 and 1388 bytes. If you're looking at the raw bytestream, there is an OggS page header in between those two segments. If you replace the setup header you need to rewrite the second page as its checksum will change. Conrad.

Where is documentation on the format of the icecast stream. I can only find docs on the server. I've asked this before and several said RFC 2616, which says NOTHING about icecast streams. So, where is the docs on the actual streaming. Is it mp3? mp3 with id3v2? tj

...am able to create a connectnion with XMPP4r through a worker in backgrounddrb. I have the problem in returning the object from the worker to my rails application. My code is as follows: class ChatWorker < BackgrounDRb::MetaWorker require ''xmpp4r'' require ''xmpp4r/bytestreams'' require ''xmpp4r/roster/helper/roster'' require ''xmpp4r/roster/iq/roster'' include Jabber Jabber::debug = true set_worker_name :chat_worker def create(args = nil) # this method is called, when worker is loaded for the first time logge...

Hi everyone, Just wanted to let you know that 0.8.0 is out. You can get it from the usual place and here's the small notes that go with it: "CELT 0.8.0 brings quality improvements for high bit-rates and for transients in general. It also adds the possibility of changing the frame size dynamically, which requires a minor change in the API. At last, the new PLC algorithm from 0.7.1 is

...successfully. Now All i want to know is how to send request to openfire server from my rails application using "jabber" as how i did for gmail. Below is the piece of code i used to connect with gamil from "jabber". require ''xmpp4r'' require ''xmpp4r/bytestreams'' require ''xmpp4r/roster/helper/roster'' require ''xmpp4r/roster/iq/roster'' require ''xmpp4r/vcard'' require ''xmpp4r-simple'' include Jabber Jabber::debug = true jid = Jabber::JID::new("mygmailid")...

Hi, I have an older phone with touch screen from Philips. It have it connected to Sipura 3000 FXS port and majority of features work ok. But phone also has touchscreen and web browser that I'd love to use for accessing my local web pages. But the phone only allows me to setup ISP phone number (username and password) and it wants to call it to get to Internet. Since it is connected to

...eThinStream* for > cases where your data is not read-only. This is another area where > functionality is provided that was not present in existing abstractions > (i.e. writeability). > > I have several implementations of this class and some abstractions for > working with them. *ByteStream* and *MutableByteStream* provide a > concrete implementatino where the backing store is an `ArrayRef` or > `MutableArrayRef`. *MappedBlockStream* (which is PDB specific) provides > an implementation that seeks around a file, piecing together blocks from > various locations in a PDB fil...

On Fri, Jul 17, 2009 at 12:48:27PM -0700, Ralph Giles wrote: > > In my ongoing quest to restore corrupted ogg files, I'm trying to find > > an easy way to identify the setup header without having to actually > > decode it. I understand that it starts with [packet_type] = 5 and then > > the string 'vorbis', but is there some way to figure out where it > >