From: Tito D. C. <ti...@da...> - 2007-04-30 13:42:11
|
Hi, after some more research about the extended80 format I propose to drop AIFF support for now: I don't want to bloat ShapeFusion with other format I/O routines to debug, which require complex code and possibly a new separate class for extended80. I think exporting to WAVE is enough for now. Does QuickTime have problems with that? What do you think? As you may have noticed I've entered a very busy period and I won't have much time for our editor. My own goal is still the color table editor, which I hope to begin soon. I'll basically reproduce the bitmap editor structure. In the well on the right there will be the color table, with big color samples adjusted to fill the well (something like the 'best fit' option for bitmaps and frames). Selecting one of them will enable a checkbox for setting the 'self luminescent flag'. Double-clicking one of them will pop up the color picker. Selecting two samples will enable a button for blending the colors inbetween. Bye Tito -- Physics is reverse engineering |
From: tiennou <tie...@gm...> - 2007-04-30 13:50:00
|
Hi ! > Hi, after some more research about the extended80 format I propose to > drop AIFF support for now: I don't want to bloat ShapeFusion with =20 > other > format I/O routines to debug, which require complex code and =20 > possibly a > new separate class for extended80. I think exporting to WAVE is enough > for now. Does QuickTime have problems with that? What do you think? I agreed with that, bloating with useless features is a BadThing=E2=84=A2.= I =20 didn't had any problem with loading WAVE files with QT, so I guess =20 they are good. > As you may have noticed I've entered a very busy period and I won't =20= > have > much time for our editor. Same here, I've been looking for work. > My own goal is still the color table editor, > which I hope to begin soon. I'll basically reproduce the bitmap editor > structure. In the well on the right there will be the color table, =20 > with > big color samples adjusted to fill the well (something like the 'best > fit' option for bitmaps and frames). Selecting one of them will =20 > enable a > checkbox for setting the 'self luminescent flag'. Double-clicking =20 > one of > them will pop up the color picker. Selecting two samples will enable a > button for blending the colors inbetween. I'm okay with this... And I don't know how we could make this more =20 'efficient'. This is "just" a color table after all. The feature I =20 think will be really useful is blending between colors. Bye, tiennou |
From: Gregory S. <wo...@tr...> - 2007-04-30 13:57:15
|
On Sat, 28 Apr 2007, Tito Dal Canton wrote: > Hi, after some more research about the extended80 format I propose to > drop AIFF support for now: I don't want to bloat ShapeFusion with other > format I/O routines to debug, which require complex code and possibly a > new separate class for extended80. I think exporting to WAVE is enough > for now. Does QuickTime have problems with that? What do you think? Why not use the libsndfile library? That's what Aleph One uses for AIFF/WAV replacement sounds. The library is only a few 100K and the code required to import/export files is fairly minimal. Plus I've already built a universal binary framework of it, which you can just drop into Xcode. > As you may have noticed I've entered a very busy period and I won't have > much time for our editor. My own goal is still the color table editor, > which I hope to begin soon. I'll basically reproduce the bitmap editor > structure. In the well on the right there will be the color table, with > big color samples adjusted to fill the well (something like the 'best > fit' option for bitmaps and frames). Selecting one of them will enable a > checkbox for setting the 'self luminescent flag'. Double-clicking one of > them will pop up the color picker. Selecting two samples will enable a > button for blending the colors inbetween. That sounds good, but I suspect most users will not use ShapeFusion to edit the color table, except possibly for the self-luminescent flag, they'll probably just import one from Photoshop. Gregory |
From: tiennou <tie...@gm...> - 2007-04-30 16:04:03
|
Hi ! Le 30 avr. 07 =C3=A0 15:54, Gregory Smith a =C3=A9crit : > On Sat, 28 Apr 2007, Tito Dal Canton wrote: > >> Hi, after some more research about the extended80 format I propose to >> drop AIFF support for now: I don't want to bloat ShapeFusion with =20 >> other >> format I/O routines to debug, which require complex code and =20 >> possibly a >> new separate class for extended80. I think exporting to WAVE is =20 >> enough >> for now. Does QuickTime have problems with that? What do you think? > > Why not use the libsndfile library? That's what Aleph One uses for > AIFF/WAV replacement sounds. The library is only a few 100K and the =20= > code > required to import/export files is fairly minimal. Hmm, that would be cool, and it handles an impressive number of file =20 formats. I'll take a look at using this... Does it read System 7 sound files ? Bye, tiennou |
From: Tito D. C. <ti...@da...> - 2007-04-30 16:51:32
|
On Mon, 2007-04-30 at 09:54 -0400, Gregory Smith wrote: > Why not use the libsndfile library? That's what Aleph One uses for > AIFF/WAV replacement sounds. The library is only a few 100K and the code > required to import/export files is fairly minimal. Had a thought about it actually. Tiennou, may you have a look at it? One more reason to finally implement a configure script on linux, I guess. I'd appreciate dropping that custom WAV code. > Plus I've already built a universal binary framework of it, which you can > just drop into Xcode. Already configured for static linking? Cool. > That sounds good, but I suspect most users will not use ShapeFusion to > edit the color table, except possibly for the self-luminescent flag, > they'll probably just import one from Photoshop. Yeah, I plan to code importing ASAP. Tito -- Physics is reverse engineering |
From: Gregory S. <wo...@tr...> - 2007-04-30 18:02:28
|
On Mon, 30 Apr 2007, Tito Dal Canton wrote: >> Plus I've already built a universal binary framework of it, which you can >> just drop into Xcode. > Already configured for static linking? Cool. No, dynamic linking. You just include the framework in the app bundle. For GPL apps like Aleph One and ShapeFusion it doesn't matter much, but for closed source it's pretty cool because you can replace the entire framework in the Finder just by showing package contents, thus satisfying LGPL. Gregory |
From: Gregory S. <wo...@tr...> - 2007-04-30 17:58:52
|
On Mon, 30 Apr 2007, tiennou wrote: > Does it read System 7 sound files ? It doesn't appear to, which is disappointing. It can read Apple's new Core Audio file format, which nobody uses. It's possible that the library maintainer would integrate System 7 file support if someone sent him a patch. I know there is code in the library to handle resource forks on the Mac for SD2 files. Gregory |
From: tiennou <tie...@gm...> - 2007-05-02 11:52:41
|
Le 30 avr. 07 =C3=A0 19:58, Gregory Smith a =C3=A9crit : > On Mon, 30 Apr 2007, tiennou wrote: > >> Does it read System 7 sound files ? > > It doesn't appear to, which is disappointing. It can read Apple's =20 > new Core > Audio file format, which nobody uses. > > It's possible that the library maintainer would integrate System 7 =20 > file > support if someone sent him a patch. I know there is code in the =20 > library > to handle resource forks on the Mac for SD2 files. I've talked with the maintainer. He was kind enough to add support =20 for our System 7 files. I'm currently waiting on his answer to see =20 how I can tweak ShapeFusion around this... tiennou |
From: Gregory S. <wo...@tr...> - 2007-05-02 13:29:35
|
On Wed, 2 May 2007, tiennou wrote: > I've talked with the maintainer. He was kind enough to add support for our > System 7 files. I'm currently waiting on his answer to see how I can tweak > ShapeFusion around this... Ooh, if it supports IMA (like the rest of libsndfile) that could be useful to Aleph One, since some old scenarios use IMA sounds in their Sounds files. Gregory |