I doubt that their has been any development work on bringing vorbis to
the Mac. I am trying to do just that.
I want to know whether you think I should try to port it using the
various components tht are being used to bring vorbis to Be and others
OR if i should wait till September when the public beta of Mac Os X (
which is based on Unix). I have been told that unix stuff will be fairly
easy to port to X, especially BSD stuff. i was hoping the public beta
would be out by now so I could star development right away.
Any ideas, comments, concearns, insults?
Dan Weinand
Crowmatek
Software & Design
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
On Sun, 30 Jul 2000, Dan Weinand wrote:> I want to know whether you think I should try to port it using the > various components tht are being used to bring vorbis to Be and others > OR if i should wait till September when the public beta of Mac Os X ( > which is based on Unix). I have been told that unix stuff will be fairly > easy to port to X, especially BSD stuff. i was hoping the public beta > would be out by now so I could star development right away.I think it's still important to have support for traditional MacOS. You're correct that the unix versions should be trivial to port so OS X (though you'll still want to do a UI) but it will be some years, I suspect, before most people have upgraded. To not support such a major platform would be rude. Especially one used by so many musicians. IMO, of course.> Any ideas, comments, concearns, insults?I would start with ogg123 using one of the cmd-line compatibility libraries and writing a MacOS output module for libao. Vorbize should be even easier, though you'll want to import AIFF (libsndfile?) and cdda support. Once those're working, write a real ui for them. In the vorbize case, I think the droplet interface makes the most sense. Drag some number of files onto it, it pops up a dialog for the comments header and starts compressing. If you drop an .ogg file on it, it should open a comment *editor* dialog (preferable the same interface as before). In the player case, I don't know what to do. Obviously the easiest thing is to write a plugin for a popular player (a la WinAmp) if such a thing exists on mac. You could also try a simple, optional progress window, with the play/stop/skip etc. at menu options. Sorry if the above is obvious, but you did ask for ideas. :) Hope that helps, -ralph --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
>I doubt that their has been any development work on bringing vorbis to >the Mac. I am trying to do just that. > > I want to know whether you think I should try to port it using the >various components tht are being used to bring vorbis to Be and others >OR if i should wait till September when the public beta of Mac Os X ( >which is based on Unix). I have been told that unix stuff will be fairly >easy to port to X, especially BSD stuff. i was hoping the public beta >would be out by now so I could star development right away.What I would do is implement Vorbis as QuickTime components. This would allow any QuickTime-based application to get Vorbis support for free. You could easily make a Windows version as well since QuickTime is fully supported on Windows. BTW...You may want to check the archives for this mailing list. I believe somebody has ported Vorbis to the Mac. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
On Sun, 30 Jul 2000, Dan Weinand wrote:> I doubt that their has been any development work on bringing vorbis to > the Mac. I am trying to do just that. > > I want to know whether you think I should try to port it using the > various components tht are being used to bring vorbis to Be and others > OR if i should wait till September when the public beta of Mac Os X ( > which is based on Unix). I have been told that unix stuff will be fairly > easy to port to X, especially BSD stuff. i was hoping the public beta > would be out by now so I could star development right away. > > Any ideas, comments, concearns, insults?Porting to OSX should be trivial. It's not worth worrying about. Even once OSx is out there will still be a ton of MacOS users with systems fast enough for vorbis (anything 68060 or ppc should eventually work great for playback) but not running OSX. It would be very valuable to have a macos port of vorbis today. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
Since Segher volunteered to work on the importing and decoding side of QuickTime support, see http://www.xiph.org/archives/vorbis-dev/200102/0252.html I figured that I would work on the export and encoding side. I've got an export component that can export to WAVE files from anything QuickTime supports, but I'm having trouble with the vorbis encoder on Mac. Both encoder_example and Drop Ogg (beta 3 based) will not correctly encode for me. I'm using Audion and N2MP3Pro202 as my players, I'm guessing that they are Beta 3 based. N2MP3Pro also has an encoder in it, and that works for me. Was there a format change such that beta 4 encoded material won't play in a beta 3 player? DropOgg encoded files seem to play at twice the original rate (and frequency) for a short while then the player aborts. encoder_example encoded files sometimes do that, sometimes the player won't load them. I've looked at the vorbis header in the files that play fast, and it has the same sample rate as the original WAVE file, so it's not something simple like that. Does anyone have the encoder working on their Macintosh? Any hints on debugging this problem? I.e. similar problems happen on other big endian systems... I'm running on a 604 based mac (8500) running System 9.1. Steve Nicolai --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.