Hi Phil, maybe I did something wrong, but
- when I downloaded DOT.TUNES (OSX) and clicked GetKey (without entering data) it hung and I had to kill it in order to be able to continue. - I don't see anything special for iPhones there - except that I could buy an iPhone-Plugin. Not sure what that is supposed to do, except loading a couple of different CSS. best andy at 02.09.2007 6:16 Uhr, [EMAIL PROTECTED] wrote: > > Hey all not at all trying to spam here but thought I would follow up > to my original question and promise, and let you all know about the > official release of our application called DOT.TUNES that lets you > stream anything (except ITMS files or non-iphone encoded videos) to > your iPhone! Check it out at http://www.dottunes.net > > Now that the project has launched I will have more time to spend here > learning all the latest tricks. > > And hats off to Joe Hewitt as always for providing iUI which served as > a nice tutorial for what was possible! > > Phil > TriAgency / DOT.TUNES development team > > http://triagency.com > http://www.dottunes.net > > > On Jul 20, 12:11 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: >> yeah we figured it out, the byte range request wasnt right initially. >> as soon as that was fixed we were fine. >> >> On Jul 16, 5:30 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> >> wrote: >> >> >> >> >> >>> Ok - try again. I spoke too quickly. The issue for me seemed to be >>> that my server wasn't sending "content-range" when iphone/quicktime >>> asked for all of the bytes by range. In other words, it appears to be >>> important that range be provided by the server when a range is >>> requested by the client, even if it's the whole range. I don't send a >>> range if none requested. >> >>> On Jul 16, 12:41 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> >>> wrote: >> >>>> I think I figured it out. I was having the same problem. Check to >>>> see if your server is responding with status 206 Partial Content. I'm >>>> doing something with CGI.pm and had to put in a little hack to get it >>>> to take my declaration of the status. Suddenly the content started >>>> playing on the iphone. I guess the iphone doesn't like to make a >>>> content-range request and get a status of 200. >> >>>> On Jul 6, 12:47 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: >> >>>>> Also Christopher the odd thing is that when I run the test CURL on my >>>>> remote webserver and custom server on the same file I get the same >>>>> response. >> >>>>> curl -range 0-99http://www.triagency.com/Marksmen.mov >> >>>>> is the format I am using... Any thoughts? >> >>>>> On Jul 6, 2:49 pm, "Christopher Allen" <[EMAIL PROTECTED]> >>>>> wrote: >> >>>>>> On 7/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> >>>>>>> Greetings all. I can post a .MOV or .MP3 file that has been encoded >>>>>>> according to the Apple spec, on any of my normal webservers, pull up >>>>>>> that URL and have the file play back beautifully over the iPhone. >> >>>>>>> Where I am stuck, is that we have a app that has a custom webserver >>>>>>> built into it. This server responds fine to every device and browser >>>>>>> so far in serving mp3 or quicktime files (including on Safari 2 & 3 on >>>>>>> OSX). >> >>>>>> I think the answer is fairly simple, your custom webserver isn't >>>>>> handling byte-range requests. >> >>>>>> As >>>>>> per:http://developer.apple.com/iphone/designingcontent.html#configure_you >>>>>> ... >> >>>>>> [quote] >>>>>> Configure Your Server >> >>>>>> HTTP servers hosting media files for iPhone must support byte-range >>>>>> requests, which iPhone uses to perform random access in media >>>>>> playback. (Byte-range support is also known as content-range or >>>>>> partial-range support.) Most, but not all, HTTP 1.1 servers already >>>>>> support byte-range requests. >> >>>>>> If you are not sure whether your media server supports byte-range >>>>>> requests, you can open the Terminal application in Mac OS X and use >>>>>> the curl command-line tool to download a short segment from a file on >>>>>> the server: >> >>>>>> curl -range 0-99http://example.com/test.mov-o/dev/null >>>>>> If the tool reports that it downloaded 100 bytes, the media server >>>>>> correctly handled the byte-range request. If it downloads the entire >>>>>> file, you may need to update the media server. For more information on >>>>>> curl, see Mac OS X Man Pages. >> >>>>>> Ensure that your HTTP server sends the correct MIME types for movie >>>>>> family file suffixes shown in the following table. >> >>>>>> File name suffix MIME type >>>>>> .mov video/quicktime >>>>>> .mp4 video/mp4 >>>>>> .m4v video/x-m4v >>>>>> .3gp video/3gpp >>>>>> Be aware that iPhone supports movies greater than 2 GB. However, some >>>>>> older web servers are not able to serve files this large. Apache 2 >>>>>> supports downloading files greater than 2GB. >> >>>>>> RTSP is not supported. >>>>>> [/quote] >> >>>>>> Let us know if this was the problem. >> >>>>>> -- Christopher Allen > > > > > -- Andy Fuchs ----------------------------------------------------------------- Elgato Systems GmbH Nymphenburger Straße 14 http://www.elgato.com D-80335 München, Germany Amtsgericht München, HRB 108591 Geschäftsführer: Dr. Markus Fest ----------------------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en -~----------~----~----~----~------~----~------~--~---
