[00:07] <lis> lol
[00:27] <Johndesigner> is bugzilla one of the easiest bug reporting programs?
[00:27] <nerochiaro> Johndesigner: absolutely not
[00:27] <Johndesigner> what should we use?
[00:28] <Johndesigner> my use is somewhat different (u/l graphics and many attachments)
[00:28] <Johndesigner> pain in the butt
[00:28] <nerochiaro> you can upload attaches on bugzilla
[00:29] <Johndesigner> yeah, but its kind of a hassle
[00:30] <Johndesigner> I'm wondering if a very left brained person find it to be nice
[00:30] <Johndesigner> it does show a lot of useful info
[00:30] <nerochiaro> i agree it can be made much more simple, but for the attaches thing, i think all other trackers handle them the same way
[00:31] <nerochiaro> i.e. one upload at a time
[00:32] <Johndesigner> its pretty unforgiving if you miss a checkbox
[00:32] <Johndesigner> but i don't know if I am being unreasonably judgemental about it
[00:33] <Johndesigner> as in -it could be worlds better than what existed before...
[00:34] <Johndesigner> Can someone volunteer to completely overhaul bug reporting as we know it?
[00:35] <Johndesigner> I'm only partially kidding
[00:35] <nerochiaro> you mean, write a new bug tracker ?
[00:35] <nerochiaro> or try installing different one to see if it works better ?
[00:35] <Johndesigner> yes :D
[00:36] <Johndesigner> the story is..
[00:36] <Johndesigner> we want to make this process super easy for moderately noobish ppl
[00:36] <Johndesigner> noble goal right?
[00:37] <Johndesigner> I do realize that it is a huge undertaking, but maybe just another system would work easier or be mroe understandalbe
[00:37] <nerochiaro> no, you're right. we can have a submission form for bugzilla that is guided and simplified. i have seen these in other places, so they're possible somehow
[00:37] <Lewis> nerochiaro: do you mind me asking where you are from?
[00:37] <nerochiaro> Johndesigner: as a compromise
[00:37] <nerochiaro> Lewis: Italy
[00:38] <Lewis> nerochiaro: ok. gracias
[00:38] <nerochiaro> Lewis: that's spanish ;)
[00:38] <Lewis> nerochiaro: lol
[00:38] <Johndesigner> something for the "this is irritating but I don't want to spend 10 minutes figuring out how to enter for the first time" folks
[00:39] <nerochiaro> Johndesigner: yes, exactly. something where you just fill in 2 boxes and go
[00:39] <chreekat> nerochiaro: do you know of any examples of those forms?
[00:40] <nerochiaro> i'm actually looking right now
[00:41] <Johndesigner> exactly - and that maybe get thrown into a "to be properly categorized" bin
[00:42] <nerochiaro> the one at gnome.org is an example of a guided bug submission procedure. it can be simplified a lot, but it's just an example
[00:46] <Johndesigner> hrm, what are your thoughts about requiring a registration? If I was just going to report that "such and such" pisses me off...i'd be slightly more irritated at needing to register
[00:46] <chreekat> you mean bugzilla.gnome.org?
[00:46] <Johndesigner> yeah, I just went to the site and slammed some buttons
[00:46] <srobertson> Johndesigner: users submitting bug reports generally ends in tears. super-generalization, i know, but...
[00:47] <srobertson> it's nice to discourage the kind of user who would submit without searching at least once for dupes
[00:47] <Johndesigner> True, that needs to be easier (or smarter seach) too
[00:47] <srobertson> Johndesigner: i hear you there
[00:48] <chreekat> eh heh. I searched for "snort" and got "Zarro Boogs found"
[00:48] <Johndesigner> I'm thinking that if we have a general bin to place the quick ones...even the crazy bastards can't mess things up
[00:49] <srobertson> chreekat: that's a "bug" in all versions of bugzilla
[00:49] <Johndesigner> hrm, but then some poor soul needs to go thru all that crap... i haven't thought this through you see
[00:49] <Johndesigner> <srobertson> Johndesigner: users submitting bug reports generally ends in tears
[00:50] <Johndesigner> heh that funny
[00:50] <Johndesigner> and true
[00:50] <chreekat> i'm only vaguely paying attention here (watching the simpsons), but i can do php if there is something specific we want
[00:50] <Johndesigner> sweet
[00:50] <srobertson> chreekat: write a php script to find all the bugs in the osd and then patch them
[00:51] <srobertson> ;)
[00:51] <chreekat> srobertson: no problemo, i'll have my cat help by walking on the keyboard
[00:51] <TasogareNoKagi> is that how you're supposed to debug? I've been doing it by hand for years, I feel old now.
[00:51] <Johndesigner> Basically, we are saying that neuros is this community friendly bunch...that repays the helpful folk by hassling them with a tax form
[00:52] <nerochiaro> Johndesigner: without registration you need to have 2 things: a separate are where to stash all crap from unregged users 2) some poor fella that you pay to go thru all that stuff and seaprate the bugs from the spam
[00:53] <srobertson> Johndesigner: well, i think that drupal 5 will prompt a cascade of web changes; another one of the "it's been six months let's revise everything" events (which I am responsible for at least encouraging if not starting)
[00:55] <Johndesigner> interesting...I have to believe that some revamping of bug reporting systems would be in that mix?
[00:55] <nerochiaro> Johndesigner: drupal != bugzilla
[00:55] <srobertson> nerochiaro, Johndesigner: yeah, drupal != bugzilla, but if we're redoing one, that would be a good time to look at the other
[00:56] <Johndesigner> sure sure, what was the questions (obvious diversion attempt)
[00:56] <Johndesigner> drupal = bugzilla got it
[00:56] <nerochiaro> Johndesigner: one thing i feel about bugzilla, is that it should put all these fields that are at the top, like milestone, severity etc, should be in a box at bottom, hidden, showable only with pressing an "advanced" button
[00:56] <nerochiaro> or something
[00:56] <nerochiaro> Johndesigner: no, the other way around
[00:57] <nerochiaro> Johndesigner: "!=" means "different from"
[00:57] * Johndesigner  is a programing no0b
[00:57] <nerochiaro> i know, shoul've seen that coming. sorry
[00:58] <nerochiaro> and that's a precious perspective to have around
[00:58] <Johndesigner> that != was a typo
[00:58] <Johndesigner> thanks, nero
[00:58] * Johndesigner  feels better about being a No0b
[00:59] <Johndesigner> how do i put the nick in front of message like - "Johndesigner: "!=" means "different from
[01:00] <Johndesigner> ?
[01:00] <Johndesigner> I'm a crappy typer for good measure
[01:00] <TasogareNoKagi> tab completion
[01:00] <srobertson> 'j' 'o' 'h' <hit tab>
[01:00] <nerochiaro> Johndesigner: depening on your client, either manually or typing the first letters of the neme and then TAB
[01:01] <srobertson> TasogareNoKagi: ctrl-w on the wrong window?
[01:01] <TasogareNoKagi> juuuuuuuust a bit :)
[01:01] <Johndesigner> srobertson, nerochiaro thanks
[01:01] <srobertson> Johndesigner: anytime
[01:01] <TasogareNoKagi> I tend to treat any text field like it was vim
[01:02] * Johndesigner  is now twice the man he used to be
[01:02] <Johndesigner> mad skillz now
[01:02] <Johndesigner> TasogareNoKagi, vim?
[01:02] <TasogareNoKagi> though could I get answers to my questions from earlier if possible?
[01:03] <TasogareNoKagi> Johndesigner: it's a text editor for unix OSes, and probably others I guess
[01:04] <Johndesigner> <nerochiaro> Johndesigner: one thing i feel about bugzilla, is that it should put all these fields that are at the top, like milestone, severity etc, should be in a box at bottom, hidden, showable only with pressing an "advanced" button
[01:04] <Johndesigner> agreed, some layout tweaks are needed
[01:07] <nerochiaro> Johndesigner: you're welcome to submit a design that you think is an improvement over the current one. We'll scoot some php guru at taking a stab at it
[01:08] <nerochiaro> TasogareNoKagi: sorry, can you recap these questions, i can't be arsed to read the log right now
[01:08] <nerochiaro> ;)
[01:08] <TasogareNoKagi> does the OSD have any rw file system storage when it's live, or is it all read only?
[01:09] <nerochiaro> there's an rw part, but it's small (and permanent)
[01:09] <Johndesigner> nerochiaro, currently the information is like many ppl talking to you all at the same time..hard to dicern where does what ..at least at first.
[01:09] <nerochiaro> Johndesigner: i absolutely agree
[01:09] <TasogareNoKagi> meaning it's saved through power cycles?
[01:09] <Johndesigner> nerochiaro, it on my (rahter long) list of things to cover
[01:09] <nerochiaro> TasogareNoKagi: yes, it's a partition of the internal flash
[01:10] <nerochiaro> Johndesigner: roger that
[01:10] <TasogareNoKagi> nerochiaro: thanks then
[01:10] <nerochiaro> Johndesigner: at least no one is ever bored at Neuros ;)
[01:10] <nerochiaro> TasogareNoKagi: can i ask you what you want to use that for ?
[01:11] <Johndesigner> heh, true, very true. I ahd to go running this am to avoid a panic attack
[01:11] <Johndesigner> kidding of course, but much to do, much to do
[01:11] <TasogareNoKagi> nerochiaro: I applied for the overnight transcoder idea from SoC, my idea was to base it around cron, which needs somewhere to put the crontabs, at least when they're being edited
[01:14] <nerochiaro> Johndesigner: i hear you :)
[01:14] <srobertson> TasogareNoKagi: there's also non-persistent storage available via tmpfs (a lot like a ramdrive)
[01:15] <nerochiaro> speaking of cron
[01:15] <TasogareNoKagi> yea that's what I was thinking of using initially, at least until I got things working
[01:15] <nerochiaro> i was just having a discussion with Gao on something like that yesterday
[01:15] <Maximander> oh, btw, back to bug tracking: trac is coming along.
[01:15] <nerochiaro> we need a scheduler for stuff (recordings and other stuff)
[01:15] <nerochiaro> Maximander: mantis too
[01:16] <Maximander> I use trac on sites I run with mysql auth off of the site's user tables
[01:16] <Maximander> works rather well
[01:16] <nerochiaro> and i was wondering, is cron the tool for the job or we should put out or own sched daemon ?
[01:16] <srobertson> Maximander: yeah, i raised trac as an option last "six-month reorg", but at the time it was missing some important features
[01:16] <srobertson> dependency tracking, blocks, stuff like that
[01:16] <srobertson> although personally i like trac a lot more than i like mediawiki and bugzilla
[01:17] <Maximander> yeah, trac is missing alot. but it's coming along, and has very, very active development
[01:17] <nerochiaro> i was considering something else than cron because we need to notify application(s) when a scheduled task fires. anyone knows of a good way for cron to do that ?
[01:17] <Maximander> I filled a bug against 0.10.x on saturday and had a reply in 38 minutes
[01:17] <nerochiaro> Maximander: reply or fix ?
[01:17] <TasogareNoKagi> nerochiaro: a kludge would be have the scheduled commands be scripts
[01:18] <Maximander> reply, saying it was fixed in HEAD
[01:18] <srobertson> nerochiaro: see my project proposal -- ipc could soon be available ;)
[01:19] <nerochiaro> srobertson: what kind of IPC you had in mind ?
[01:19] <Maximander> oh, srobertson: I don't think you were using it anymore, but that server on which you had an accout two years ago is gone
[01:19] <nerochiaro> TasogareNoKagi: that's an option, but how you notify apps anyway ?
[01:20] <srobertson> nerochiaro: you think i actually have thought that far ahead? you give me too much credit. let's just say *efficient* ipc.
[01:20] <Maximander> srobertson: in case you don't remember, that was meow.bamboozled.org
[01:21] <srobertson> Maximander: yeah, ftpbot died a long time ago and i never fixed it. heh, that was a loooong time ago
[01:21] <TasogareNoKagi> nerochiaro: that's where my knowledge of unix stops :/
[01:22] <srobertson> nerochiaro: what about DBUS? it's pretty tiny, right? (just throwing it out there)
[01:23] <Maximander> srobertson: if you still need servers, I have several more now. just not that one.
[01:23] <nerochiaro> srobertson: i'm not sure it's that tiny. it could be an option if the library requires veeery little space. what is that based on anyway ? sockets ?
[01:24] <srobertson> Maximander: i appreciate the offer, as much as i appreciate you giving me a hand then, but i'm good now (Verizon FiOS: 5mbps up)
[01:24] <Maximander> nice.
[01:25] <srobertson> nerochiaro: yeah, i'm reading the docs and although it's nice (plus Maemo uses it) it might be a little weighty for 32M exposed RAM
[01:31] <nerochiaro> srobertson: but you know what is it based on ?
[01:35] <srobertson> nerochiaro: whoops. xml over sockets.
[01:35] <srobertson> SOO FAST
[01:36] <nerochiaro> wow, not really what we want
[01:36] <srobertson> agreed. on the other hand, Knuth was not too far off with "premature optimization = sqrt(evil)" quote
[01:37] <nerochiaro> i agree
[01:37] <srobertson> so, it's almost certainly a no, but i'm not dropping it entirely from consideration
[01:37] <nerochiaro> and if the communication is restricted to: 1) app calls scheduler and says "i want to register for notification" 2) scheduler calls app to notify
[01:38] <nerochiaro> i think we can go with sockets. maybe not xml over sockets, that seems like a bit of extremely cumbersome for nothing
[01:39] <nerochiaro> problem is: apps should keep a socket listening for notifications
[01:40] <srobertson> or, in the spirit of DCOP, apps could connect to a central (very tiny) daemon which would route requests
[01:41] <nerochiaro> why add another daemon ? they can connect directly to scheduler
[01:43] <srobertson> okay, add scheduled events to daemon. i'd rather think of the daemon as "router" more than "scheduler" because IPC will not be limited to scheduling for long
[01:44] <nerochiaro> so you think of 2 deaemons. sched daemon and message router daemon ?
[01:46] <srobertson> i think it's important to construct a message router daemon first, and poke around with a protocol, before deciding
[01:46] <srobertson> it wouldn't be hard, though, to add scheduling to the router -- just add a way to "sleep" a message so it doesn't get sent for xxxx (or better probably, until xxxxx)
[01:47] <srobertson> otoh, this is not persistent
[01:48] <srobertson> okay, all, i really really have to work now
[01:48] <nerochiaro> ok, thanks for the input
[01:48] <srobertson> nerochiaro: thanks for yours
[01:49] <nerochiaro> srobertson: it's just that we're gonna need this stuff to finalize the EPG/Scheduled recording design, so i'm trying to gather all possible idea quickly
[01:49] <nerochiaro> srobertson: well, i'll leave you to work and go back to mine. see ya
[01:49] <srobertson> oh! okay. well, i'm happy to talk more wednesday, if that's not too late --
[01:50] <srobertson> and of course what i'd "rather" do when coding is subservient to what needs to be done
[01:50] <nerochiaro> srobertson: heh, of course
[01:50] <nerochiaro> srobertson: well, there's a thread in ML that you can contribute to
[01:50] <nerochiaro> srobertson: input on that would be welcome
[01:50] <srobertson> i shall peruse.
[01:56] * srobertson  is away: HOMEWORK. argh, university, hate crap classes, et al
[03:15] <nerochiaro> anders_: have a minute to spare for an xmms2 internals question ?
[03:16] <anders_> nerochiaro: Go ahead!
[03:16] <nerochiaro> i have just started looking at the way xmms2 does IPC, and specifically the async interface
[03:17] <nerochiaro> since we need something of that kind for stuff on the osd, i was wondering how much we could reuse of that system
[03:17] <nerochiaro> more specifically
[03:18] <nerochiaro> we want to have a scheduling daemon which should notify applications when it's done. and i was thinking that a system like the xmms2 async interface would be good for that
[03:19] <nerochiaro> apps register to the sched daemon and the daemon calls them back when done
[03:20] <anders_> src/lib/xmmsipc is just lowlevel message passing stuff.
[03:20] <anders_> Which has an async interface built on top.
[03:21] <anders_> src/lib/xmmsipc should be easy to rip out and reuse.
[03:21] <anders_> The higher level stuff is a bit more involved in xmms2 code. And will hopefully be changed to autogenerated code after the summer (SoC project)
[03:22] <anders_> Alex recently blogged about the ipc internals; www.geekfire.com
[03:22] <nerochiaro> oh, very interesting
[03:23] <nerochiaro> i was thinking that since we're going to use xmms2 anyway, this would reduce the overhead
[03:23] <nerochiaro> of having both xmms2 ipc and our own ipc
[03:23] <anders_> Right.
[03:25] <nerochiaro> it uses sockets underneath, for the actual communication, right ?
[03:27] <anders_> Yes. Both unix and tcp sockets.
[03:27] <anders_> src/lib/xmmsipc/{socket_tcp.c,socket_unix.c}
[03:34] <nerochiaro> anders_: the choice of unix or tcp is up to the application ?
[03:36] <anders_> nerochiaro: Yes. Application does: xmms_ipc_client_init ("tcp://127.0.0.1:1234/") and server does: xmms_ipc_server_init ("tcp://0.0.0.0:1234")
[03:37] <nerochiaro> so you use unix://socket_path for unix sockets or something like that ?
[03:38] <anders_> nerochiaro: Right.
[03:41] <nerochiaro> anders_: last question, then i'll leave you alone (or maybe go bother someone in #xmms2 ;)) - with a normal installation of xmms2, how much of this stuff is exposed in libraries and that other programs can build against ? the low-level ipc message passing or also the callback mechanism ?
[03:43] <anders_> The only thing exposed is xmmsclient.so
[03:43] <anders_> Which contains all that stuff inside, but not accessible.
[03:54] <nerochiaro> anders_: if we factor that out somehow, can it be of use to your project too ?
[03:55] <anders_> nerochiaro: It pretty much already factored out in our project, it just bundles it togheter.
[03:55] <nerochiaro> ok, even better
[03:56] <anders_> There is a src/lib/xmmsipc/test.c and a src/lib/xmmsipc/testclient.c but I'm not sure they are updated.
[03:56] <anders_> And it doesn't seem to use messages
[03:56] <anders_> So they are pretty useless.
[03:57] <nerochiaro> they write raw bytes to the socket, it seems
[03:58] <anders_> Yeah.
[03:59] <nerochiaro> xmms_ipc_msg.h is the API for messages, right ?
[04:00] <nerochiaro> so it's - create message, - put typed vars into msg, -send/recv msg over socket, - take out typed data from msg ?
[04:08] <turran> good morning :)
[04:09] <anders_> nerochiaro: Right
[04:18] <nerochiaro> turran: mornin'
[09:33] <JoeBorn> hi all
[09:35] <hellwolf> good evening JoeBorn
[09:36] <JoshMalone> 'lo
[09:36] <Johndesigner> howdy
[09:38] <Johndesigner> JoeBorn, see you in a few
[09:40] <JoeBorn> hi everybody
[09:40] <JoeBorn> Johndes|away, see you then!
[09:47] <Zygfryd> hello
[10:00] <nerochiaro> hi JoeBorn
[10:00] <nerochiaro> JoeBorn: seen my email about the TVTV contact ?
[10:02] <JoeBorn> yeah, I'm digging out of 135 emails\
[10:02] <nerochiaro> JoeBorn: ok, just wanted to make sure, since she's in germany so you might want to contact her before the day expires. it's 5PM there
[10:08] * vmarks  sends email to JoeBorn
[10:08] * vmarks  sends email to JoeBorn
[10:08] <vmarks> caribbean! who needs tv!
[10:08] <vmarks> doh.
[10:08] * vmarks  sends email to JoeBorn
[10:08] * vmarks  kids.
[10:32] <progeny> h
[10:33] <nerochiaro> i
[10:38] <vmarks> l
[10:38] <vmarks> o
[10:38] <vmarks> w
[10:47] <progeny> bye all
[13:45] <anders_> nerochiaro: Thursday CEST 19:00? Right?
[13:46] <nerochiaro> 20, we have dst
[13:46] <nerochiaro> no wait, what ?
[13:48] <nerochiaro> anders_: ?
[13:49] <anders_> nerochiaro: Proposed time for GSoC-mentors meeting.
[13:49] <anders_> nerochiaro: (I don't have my mail available right now)
[13:50] <nerochiaro> anders_: that's correct, but no one answered yet
[13:52] <anders_> nerochiaro: I might be able to make it.
[13:53] <nerochiaro> anders_: great. hopefully cr-tablet (crweb) will answer too. when you get back to email, please send a reply
[13:54] <anders_> I'm not 100% sure though. I'll be out of town.
[13:55] <nerochiaro> well, we can reschedule if you prefer
[13:55] <nerochiaro> just mention so in the email
[14:00] <nerochiaro> well, i'm be off for today. bye everyone
[14:03] <cr-tablet> i need a reschedule
[14:04] <cr-tablet> I have class at that exact hour
[14:05] <cr-tablet> any other hour/time would be good
[17:57] <pb101> Anybody familiar with NmsPlay()?
[20:18] * srobertson  is back (gone 18:21:51)
[20:18] <Emmett> UNDERPANTS
[20:19] <drawnout> anyone know why I can view some directories through smbclient on the OSD, but the on screen samba browser can't see them?
[20:19] <drawnout> I've enabled show hidden already
[20:20] <drawnout> and refreshed
[20:52] <srobertson> drawnout: forgive me if this is silly, but... permissions?
[21:01] <drawnout> srobertson: nope, I can view it through smbclient on the neuros
[21:03] <srobertson> what user does osdmain run as? root, i'm guessing
[21:03] * srobertson  still hasn't pulled out his magic lead wand to fix his serial
[22:03] <pb101> anybody awake?
[22:04] <srobertson> pb101: is that an honest question?
[22:04] <pb101> yeah, why not :)
[22:04] <cr-tablet> define... awake
[22:04] * srobertson  hugs little bottle of caffeine pills
[22:04] <srobertson> 'scuse me, alertness aids
[22:04] <pb101> beging able to respond.
[22:05] <cr-tablet> physically or mentally?
[22:05] <pb101> mentally, it's more important.
[22:05] <cr-tablet> ah..
[22:05] <cr-tablet> then no
[22:08] <pb101> cr, by the way, I followed your advice, and was able to rebuild the rootfs, boot from NFS, etc...it's all working great!
[22:08] <cr-tablet> i know
[22:08] <cr-tablet> i designed it
[22:08] <cr-tablet> :)
[22:09] <pb101> appreciate the help :) I was really approaching the whole thing from a different and way more difficult direction.
[22:10] <pb101> I am attempting to add more hooks to the TCP/IP piece, and I am having a problem with NmsPlay(). It's seems to be failing because it can't send commands.
[22:13] <pb101> any ideas?
[22:31] <cr-tablet> i haven't done any work with nms yet
[22:32] <cr-tablet> i've been designing a gui shell, and that will eventually wrap around the nms functions.
[22:32] <cr-tablet> i wasn't going to implement nms until the gui was done
[22:34] <drawnout> cr-tablet: hey, is there a way to disable the console bell for the development VM?
[22:35] <cr-tablet> sudo modprobe -r pcspkr
[22:35] <cr-tablet> maybe
[22:36] <drawnout> ah, thank you. loud noise is scary
[22:41] <pb101> cool, thanks
[22:43] <pb101> drawnout, I feel the same way about the beeping.
[23:27] <drawnout> is there any way to disable the watchdog timer from the command line?
[23:33] <pb101> is it rebooting your box?
[23:34] <drawnout> it is when I kill osdmain ;)
[23:34] <drawnout> after a minute or two
[23:34] <pb101> there is a bug in the software.
[23:35] <pb101> you can get around it by mounting the system using NFS, and simply keeping osdmain from starting by modifying the init scripts.
[23:36] <pb101> You can also get the rootfs, modify the init script, build a new upk image, and use it to boot.
[23:36] <drawnout> *nod* I'll get to that point eventually, but I just got the thing today and have a major research paper due on thursday
[23:36] <pb101> that's option a and b. I don't know about another solution...unless you wait until the firmware is fixed.
[23:37] <drawnout> na, I'm ok with it. I figured out what I need to figure out
[23:37] <pb101> it was bugging me too because it kept painting over my app.
[23:38] <drawnout> well I was hoping to find a way to adjust the resolution since I have a nice lcd tv, but the itfb module is proprietary, so little hope of that
[23:39] <pb101> yeah, the OSD is not 100% open-source.
[23:39] <drawnout> I know, I;m just hoping that's one of the pieces that will be rewritten during SoC
[23:40] <cr-tablet> the resolution can be modified
[23:40] <drawnout> how?
[23:40] <cr-tablet> ioctl
[23:40] <drawnout> ah, it does support it... excellent
[23:40] <cr-tablet> however
[23:40] <cr-tablet> it wont' do you much good
[23:40] <cr-tablet> NTSC doesn't work the same way as pc resolutions
[23:41] <cr-tablet> you can make the resolutions as high as you want, its still going to be NTSC
[23:41] <cr-tablet> the text you read is just going to get smaller
[23:42] <drawnout> so no D-1 ntsc?
[23:43] <cr-tablet> i don't believe so
[23:43] <cr-tablet> its ntsc 720x480
[23:43] <cr-tablet> there are actually 2 layers
[23:43] <cr-tablet> the gui layer, and the video layer
[23:43] <cr-tablet> the "frame buffer" resolution is whatever you want
[23:44] <drawnout> right now the fb is reporting 656x464
[23:44] <cr-tablet> but it doesn't effect output video
[23:44] <cr-tablet> the fb is just the gui display
[23:44] <cr-tablet> has nothing to do with video out
[23:44] <drawnout> now is the actual output 656x464 (which is ntsc) or 720x486?
[23:44] <drawnout> which is D-1
[23:44] <drawnout> ntsc
[23:44] <cr-tablet> 656x464 isn't ntsc
[23:44] <cr-tablet> 720x480 is ntsc
[23:45] <drawnout> www.strata.com
[23:45] <cr-tablet> ntsc isn't square
[23:45] <cr-tablet> ther is actually no horizontal set freq
[23:47] <drawnout> ah, I'm looking at ntsc for digital video, not analog