[vorbis-dev] ACM codec

[Dan Miller]

I'm afraid it's been a while and my memory may be creaky, but I think the only changes I made to the ACM were fiddling with his Kanji text fields so it would compile.  I didn't actually get into the guts of the code at all.  For some reason I believe I ended up using 'mode 3'.
 
If you are using this for a specific project with specific apps that you control, I think you'll be alright.  I don't think there is too much going on with this ACM version so you're probably safe installing it on user's machines.  YMMV -dan

        -----Original Message----- 
        From: Dambrin Didier [mailto:gol at image-line.com] 
        Sent: Mon 11/11/2002 7:49 AM 
        To: vorbis-dev at xiph.org 
        Cc: 
        Subject: Re: [vorbis-dev] ACM codec
        
        


	> I successfully contacted him, received source code, and got permission to
        post it on my site for a project we did -- www.on2.com/vpvision.  Please
        feel free to use that code off my site under the license terms, which I
        believe were GPL or LGPL.
	>
        
        so you use it to encode the sound for a software VCR? cool
        
        
        
	> Be warned however that Vorbis+ACM is a nasty combination right now, for
        various reasons that Monty can explain if he is so inclined.  In a nutshell,
        there isn't a good match between Vorbis in its present state and the ACM
        interface.  This project used six different ACM tags, I never got a clear
        understanding of the differences between them.
	>
        
        Yes that's my problem too, his doc seems to tell about that, but in
        japanese. I already encoded a lot of my samples, I used 'mode 1' for safety.
        What I understood is that only bad uses of the ACM SDK were a problem, &
        indeed, it is a problem for CoolEdit that apparently can't load back ogg
        encoded waves (& can't save them in a proper way, anyway). Works like a
        charm with SoundForge, & the most important for me, FruityLoops loads them
        perfectly.
        
        I also wanted to know how 'strong' the codec was, that is, in case someone
        else changes the specs a little, if it'd conflict with the version our app
        would install, in case it's registered the same way in the system. I read
        that you indeed patched but renamed his original codec - do you think I
        should rather use yours? Did you fix some things, or enhance it for your
        app's needs maybe?
        
        In fact I also wanted to know if it's fine for him that we auto-install the
        codec ourselves (I guess so). I didn't plan to use his sources, I'm fine
        with the codec installed on the user's system, so that he can use it as
        well.
        
        
        
        
        --- >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 at xiph.org'
        containing only the word 'unsubscribe' in the body.  No subject is needed.
        Unsubscribe messages sent to the list will be ignored/filtered.
        

-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 5834 bytes
Desc: winmail.dat
Url : http://lists.xiph.org/pipermail/vorbis-dev/attachments/20021111/b3a69475/winmail.bin