Back to Home / #mythtv / 2003 / 05 / Prev Day | Next Day
#mythtv IRC Logs for 2003-05-11

00:02-!-orangey [] has joined #mythtv
00:02<orangey>hey guys!
00:02<orangey>anyone here use mythmkmovie?
00:02<FryGuy>i used it once
00:02<orangey>FryGuy: successfully?
00:03<FryGuy>the things it produces are broken though
00:03<FryGuy>like blue stuff all over the place
00:03<orangey>broken how?
00:03<orangey>did you have to use a patched mplayer?
00:03<FryGuy>are you the maker?
00:03<orangey>FryGuy: no
00:03<orangey>: )
00:03<FryGuy>yes I do
00:03<FryGuy>mythplayer works
00:04<orangey>OK.. just wondering if that was a prerequisite.
00:04<FryGuy>i think it is
00:04<orangey>I'm pretty sure my mplayer is patched..
00:04<FryGuy>i had to rewrite the patch though
00:04<FryGuy>change the directory
00:04<FryGuy>can mplayer play the .nuv files?
00:05<orangey>it could when I last checked, though admittedly that was a while ago.. it's possible mandrake has since overwritten it..
00:07<orangey>ok, looks like it was indeed overwritten
00:09<orangey>did you apply to the patch to the old-ass version?
00:10-!-rkulagow_ [] has quit [Read error: 110 (Connection timed out)]
00:10-!-rkulagow_ [] has joined #mythtv
00:12<FryGuy>no I got the one from mplayer.something
00:12<FryGuy>the foreign site
00:13<orangey>ok.. I think I'll stick to the version in the documentation..
00:18<orangey>OK, so mplayer works.
00:18<orangey>but mkmovie still doesn't
00:23-!-Edgan [] has joined #mythtv
00:31-!-Edgan [] has quit ["Client exiting"]
00:34-!-Edgan [] has joined #mythtv
00:42<Chutt>mdz, hi
00:42<Chutt>i think the guy's just dumb
00:42<Chutt>if you look at the comments he added
00:43<Chutt>like // Was there a problem?
00:43<mdz_>I just got to his second message
00:43<mdz_>this bit about 1000TB is crap
00:43<Chutt>and the next line down is 'perror("ERROR: file I/O problem")'
00:44<Chutt>thing is, it doesn't make is simpler
00:44<Chutt>it makes it more complex
00:44<mdz_>I do think that a subclass or something might be in order
00:44<mdz_>but this guy doesn't seem like he's going to be much help
00:44<Chutt>because you've got that magic file size in there for normal files
00:44<Chutt>having the different cases makes it explicit
00:44<Chutt>yeah, breaking it up into two different classes with a base class would be ok
00:45<Chutt>but they'd share a lot of code
00:45<Chutt>and, this stuff works right
00:45<mdz_>he changed a few things that, by his own admission, he did not understand
00:45<Chutt>there's absolutely no reason to futz with it, unless there's a problem
00:45<orangey>I do think, though, that his "energy" can be harnessed if one is a little more gentle..
00:45<Chutt>'circular file'
00:45<Chutt>like, look at the name of the class for what it's called
00:45<orangey>I think MDZ did a good job of setting criteria that are concrete.
00:46<mdz_>that was before I realized he was a twit
00:46<Chutt>what, you don't think me saying things like 'inane comments' is productive? :p
00:46<orangey>mdz: Still, it's more likely to make him productive.
00:46<orangey>Chutt: hehehe : )
00:46<orangey>Chutt: The guy could be a newbie
00:46<Chutt>he can code, apparently
00:47<orangey>Chutt: He's obviously got a bit of heart.. why not focus him on specifics..
00:47<mdz_>if he is, he should be asking more questions
00:47<Chutt>just needs to figure out _what_ to code
00:47<orangey>like "god, this class is a mess. why don't you work on that?".. then "fix" his code when he returns something..
00:47<orangey>maybe the reason he's having such trouble is that he's tackling mythtv instead of a portion therein
00:47<Chutt>i really don't like stuff that i have to fix in order to apply it
00:48<orangey>it's an investment
00:48<Chutt>and i especially don't like stuff that doesn't _do_ anything
00:48<orangey>today you're teaching him, tomorrow he's working.
00:48<orangey>(on his own)
00:48<Chutt>i shouldn't have to :p
00:49<orangey>anyway, all I'm saying is that the guy would have to be very counter-productive to be stonewalled in his attempts to help
00:52<Chutt>mdz, there's a semi working vp3 decoder in libavcodec
00:52<Chutt>now =)
00:53<Chutt>and, apparently, a working svq3 decoder (ie, all those quicktime movie trailers)
00:53<mdz_>yeah, I saw that on the theora-dev list a while back
00:53<mdz_>the guy was asking decent questions
00:53<mdz_>is svq3 the 'sorenson' codec?
00:53<mdz_>nice, there's a ton of content using that
00:53<orangey>mmmm. sorenson.
00:54<orangey>I thought the reason it wasn't linux-ated was because of license issues, though, not technical.
00:54<Chutt>there wasn't ever code for it
00:54<orangey>is it a very complex codec? or was it just not worked on?
00:55<Chutt>i dunno
00:55<orangey>mdz: would you like an mplayer patch modified for the latest mplayer?
00:55<Chutt>the vq3/lavc guy just committed stuff to make non-keyframes work
00:55<orangey>truth be told, all I did was take out the "rc5"
00:55<Chutt>so, coming along
00:56<Chutt>though it apparently crashes like 30 seconds in due to memory issues =)
00:57<Chutt>i'm just hoping he gets to an encoder sometime
00:57<Chutt>would be nice =)
00:57<Chutt>could distribute actual patent free (at least video/audio) binaries
01:00<Chutt>mdz, heh, i said the same thing
01:01<Chutt>7 minutes before you did :p
01:01<mdz_>damn you
01:01<mdz_>I'm too busy playing ur-quan masters
01:02<Chutt>star control
01:02<orangey>Chutt: A quick question before I head out.. Recently, mythfrontend has failed in transitioning from none to livetv/watchprerecorded about 1 / 3 times.. This isn't creating a segfault, though, though it totally jams up mythfrontend (apparently waiting for something?), and requires mfe to be killed at command line.. how can I produce some useful bug report?
01:03<Chutt>it's fairly similar to a segfault
01:03<Chutt>just recompile for debugging
01:03<Chutt>run mythfrontend in gdb
01:03<orangey>Chutt: so when I BT, it'll give the useful information, even if it was killed?
01:03<Chutt>when it hangs, switch to the term that's running gdb
01:03<Chutt>hit ctl-c
01:03<Chutt>then do the backtrace stuff
01:03<orangey>OK, great..
01:05<Chutt>make sure nothing's using /dev/dsp or whatever your output device is, though
01:05<Chutt>that's the biggest reason for it to freeze when starting to playback
01:06<orangey>I thought it dropped to prompt when that happened..
01:07<Chutt>not always
01:07<Chutt>_current_ cvs should be better about it
01:07<Chutt>like, as of last night
01:07<orangey>OK.. I will install and check it out.
01:07<mdz_>orangey: for bonus points, submit a patch for the HOWTO explaining the procedure
01:07<orangey>mdz: the bt'ing procedure?
01:07<Chutt>for the freeze
01:08<Chutt>should be pretty small
01:08<mdz_>I think there's a bit there about getting a backtrace for a segfault
01:08<Chutt>the howto has better segfault instructions now =)
01:08<mdz_>but not interrupting it to get a backtrace
01:09<orangey>mdz: will do as soon as I have a few : )
01:09<Chutt>i need to email VIA and ask about cpu temps for the nehemiah
01:11<Chutt>i don't think 85c is good.
01:17<Chutt>the temp thing is in the cpu
01:18<Chutt>so that's actual temperature, not measured outside
01:18<Chutt>and that's after being loaded 100% for a half hour or so
01:18<Chutt>and, lm_sensors could be reporting it wrong =)
01:26-!-_inman_ [] has joined #mythtv
01:43-!-Timon_ [] has joined #MythTV
01:44-!-Timon_ is now known as Timon
01:46-!-inman [] has quit [Read error: 110 (Connection timed out)]
02:04-!-__inman__ [] has joined #mythtv
02:13-!-_inman_ [] has quit [Read error: 60 (Operation timed out)]
02:23-!-rkulagow_ [] has quit [Read error: 110 (Connection timed out)]
02:30<[mbm]>anyone playing around with the serial port on the dct2000 cableboxes?
02:30<orangey>mbm: Who makes it?
02:31<orangey>mbm: I think there's a script floating on the myth lists somewhere.. moment..
02:33<orangey>what are you wondering about specifically, mbm?
02:33<[mbm]>if anyone was working on implementing it in mythtv
02:34<WarrenCanuck>i owuld guess changing channels useing a serial cable
02:34<orangey>hehehe : )
02:34<WarrenCanuck>one of the motorola digital cable boxen?
02:34* [mbm]figured out the protocol a week ago, thought maybe you guys could use it
02:34<[mbm]>WarrenCanuck: yep
02:35<WarrenCanuck>that would def be useful
02:35<WarrenCanuck>you hsoul rip it apart and figure out how to tap a raw mpeg2 stream form it ;)
02:35<WarrenCanuck>i'm sure if you post the specs someone would implement it
02:35<WarrenCanuck>but since you can run commands to change channels you could also write a standalone app
02:36<[mbm]>that'sthe thing, I don't want to go to all the trouble of finding the dev list, registering etc. was hoping to just catch someone on irc
02:36<orangey>mbm: I don't have personal experience with it, but:
02:36<orangey>the discussion of it indicates two things: 1) There is some work on it.
02:36<orangey>and 2) the Tivo knows how to control it.
02:36<[mbm]>where's the discussion?
02:36<WarrenCanuck>mbm: throw it up on a website and post the link in here
02:37<orangey>mbm: on the dev list, sadly.
02:37<[mbm]>got a url or something?
02:37<orangey>mbm: You can always capture from your tivo : )
02:38<[mbm]>you're bright.. how do you think I figured the protocol out? :)
02:38<WarrenCanuck>how does a dump from a palm pilot sync help?
02:38<orangey>mbm: That thread seems to indicate that scripts exist..
02:38<WarrenCanuck>no it doesn't orangy
02:38<WarrenCanuck>at least not that i can discern
02:39<orangey>oh.. it's lirc based:
02:39<orangey>I've set up the proper scripts and verified
02:39<orangey>> >> that they work correctly outside of MythTV.
02:39<WarrenCanuck>yeah :\
02:39<orangey>I've got an Actisys IR-200L & Motorola DCT2000 setup working
02:39<orangey>> >> stand alone under RedHat 8
02:39<orangey>doh. sorry
02:39<WarrenCanuck>mbm: you should throw the specs on some webspace somewhere
02:40<[mbm]>maybe, that's also work
02:40<WarrenCanuck>email them to me then
02:41<[mbm]>how about I just start rambling on here and someone can take an irc log?
02:43<[mbm]>basic format is
02:43<[mbm]>[start code][size][data][crc][end code]
02:43<[mbm]>where start is 0x10 0x70 or 0x10 0x78 (2 bytes)
02:44<[mbm]>size is another 2 bytes for the size of the data segment
02:44<[mbm]>crc is another 2 bytes
02:44<[mbm]>and end code is 0x10 0x03
02:44<orangey>what's left to figure out?
02:45<[mbm]>... 0x10 is a control code
02:45<[mbm]>orangey: q&a is at the end ;)
02:45<orangey>[mbm]: hehehe : )
02:46<[mbm]>if 0x10 appears as part of the data then it's written as 0x10 0x10
02:46<[mbm]>(the 0x10 0x10 only being one byte in terms of the size field)
02:48<[mbm]>the data field is further broken up into [seq][id][cmd][...]
02:48<[mbm]>sequence is one byte
02:49<[mbm]>id is one byte, 0x40 or 0x04
02:49<[mbm]>(0x04 for sending to the dct, 0x40 in the responses from the dct)
02:50<[mbm]>and the command field is one byte
02:50<[mbm]>sequence isn't too hard to figure out
02:51<[mbm]>it's one byte with the high nibble being used for new packets and the low nible used for responses
02:51<[mbm]>(think hex, one byte has two digits called nibbles)
02:52<[mbm]>if the seq was at 0x00 and you wanted to send a new packet then you send seq 0x10
02:52<[mbm]>the response will come back with the high bit set and the lower nible incremented
02:53<[mbm]>so 0x11|0x80 (aka 0x91)
02:54<[mbm]>(resposes in the above being simple acknowlegements, size is 2, just large enough for seq and id
02:55<[mbm]>as for the command field, it's used to specify the type of the packet
02:55<[mbm]>0x22 is used to simulate keystrokes
02:56<[mbm]>the byte following 0x22 is the key you want to send
02:56<[mbm]>cmd=0x20 is channel status, any time the dct changes channels you'll get one of these packets
02:57<[mbm]>two bytes following the 0x20 are a word representing channel number
02:57<[mbm]>then a byte for analog/digital
02:58<[mbm]>ugh this is tedious
02:58<[mbm]>I'll stop there and someone can bug me about the details later
02:58-!-PBlue_away [] has quit [Read error: 111 (Connection refused)]
02:59-!-Edgan [] has quit ["Client exiting"]
02:59<[mbm]>sofar the only packets I've seen used have cmd=0x00,0x22 or 0x20
02:59-!-PBlue_away [] has joined #mythtv
02:59<[mbm]>but that leaves alot open for other possible commands
03:02<[mbm]>the abridged version is basically this: <handshake><ack from dct>(done once per session) <keystroke><ack from dct> <channel status from dct><ack>
03:04<[mbm]>(now orangey can bug me with all his questions)
03:04-!-Edgan [] has joined #mythtv
03:04<orangey>what I'm wondering, basically, is what's left.. it seems like you're 90% there, to be conservative with my guess (I think more)
03:05<orangey>have you checked out how this sort of communications is done with DTV receivers?
03:05-!-hfb [] has joined #mythtv
03:05<[mbm]>I know the protocol enough that I could change the channal and detect what the result was
03:05<[mbm]>what I don't know is what else the protocol allows
03:06<[mbm]>the dct cablebox is slow as shit and having to specify a channel entirely from keystrokes is tedious
03:06<[mbm]>as the dct will pause to display each digit on the screen for a second
03:07<[mbm]>(made worse by the fact that after changing the channel it will display a banner with the show name for atleast 3 seconds)
03:07<orangey>well, the directv code has channel changes
03:07<orangey>where you pass a channel command, then the channel strings all together.
03:08<[mbm]>it's more like "5"<ack> "0"<ack> "1"<ack> <channel change packet>
03:08<orangey> for the implementation I use on my system.
03:08<[mbm]>you can't specify a channel in one packet as far as I can tell
03:08<orangey>ever, or with the dct?
03:08* [mbm]really doesn't give a damn about the way dtv does it
03:09<orangey>well, consider that the same companies are probably making these receivers for various media
03:09<[mbm]>umm no
03:09<orangey>so understanding how it's done in one medium will likely translate.
03:09<[mbm]>protocol motorola uses on the dct has nothing to do with how the dtv works
03:10-!-Timon [] has quit [Read error: 110 (Connection timed out)]
03:10<[mbm]>it's just some quirky motorola protocol
03:11<orangey>check out this output from a dtv receiver in a serial communication:
03:11<orangey>SEND: 0xFA [ú] 0x45 [E] 0x0 [] 0x0 [] 0xCE [Î]
03:11<orangey>RECV: 0xF0[START PKT] 0xF2[GOT EXTENDED] 0xF4[END PKT]
03:11<[mbm]>i told you before I really don't give a damn about the dtv protocol
03:11<orangey>that's sending the keystroke "1"
03:11-!-Received a CTCP PING 1052636274 360636 from [mbm] (to #mythtv)
03:11<-- [mbm]( has left #mythtv
03:12<orangey>alright.. but I think you miss opportunities that way.. because as far as I can tell, it's relatively similar to what you described in principle
03:26-!-_inman_ [] has joined #mythtv
03:33-!-hfb_ [] has joined #mythtv
03:33-!-hfb_ [] has quit [Remote closed the connection]
03:33-!-hfb_ [] has joined #mythtv
03:34-!-__inman__ [] has quit [Read error: 60 (Operation timed out)]
03:51-!-hfb_ [] has quit [Read error: 104 (Connection reset by peer)]
03:54-!-hfb_ [] has joined #mythtv
04:00-!-hfb [] has quit [Read error: 110 (Connection timed out)]
04:00-!-hfb [] has joined #mythtv
04:02-!-hfb_ [] has quit [Read error: 54 (Connection reset by peer)]
04:20-!-orangey [] has quit ["Client Exiting"]
04:29-!-hfb [] has quit [Read error: 60 (Operation timed out)]
04:30-!-hfb [] has joined #mythtv
05:10-!-hfb [] has quit ["Huh! Wasn't me!"]
05:24-!-bigguy [] has quit [Read error: 113 (No route to host)]
06:30-!-Drikus_ [] has joined #mythtv
06:30-!-Drikus___ [] has quit [Read error: 104 (Connection reset by peer)]
06:43-!-sc00p [] has joined #mythtv
07:14-!-Viddy [] has quit ["Client exiting"]
07:36-!-Viddy [] has joined #mythtv
07:39-!-Viddy [] has quit [Remote closed the connection]
07:41-!-Viddy [] has joined #mythtv
08:12-!-Viddy [] has quit [Remote closed the connection]
08:18-!-Viddy [] has joined #mythtv
09:43-!-iopener3 [] has quit ["ChatZilla 0.8.23 [Mozilla rv:1.3/20030410]"]
09:44-!-iopener5 [] has joined #mythtv
09:46-!-iopener5 [] has quit [Client Quit]
10:01-!-knight_ [] has quit [Read error: 110 (Connection timed out)]
10:53-!-rkulagow_ [] has joined #mythtv
10:53-!-_inman_ [] has quit [Read error: 110 (Connection timed out)]
11:11-!-orangey [] has joined #mythtv
11:37-!-Telpar [] has joined #mythtv
11:37-!-Telpar is now known as Sembiance
11:37<Sembiance>I'm working on building a MythTV system.
11:37<Sembiance>I'm starting out with the 'display unit'
11:37<Sembiance>Something that is going to be quiet, silent actually, and just pull an MPEG stream off it's 10/100 nic interface and display it using s-video/composite tv-out
11:42<Sembiance>I wish the 'remote wonder' worked in linux :(
11:44-!-bigguy [] has joined #mythtv
11:57<Sembiance>pretty quiet :(
11:58-!-Edgan [] has quit ["Client exiting"]
12:13-!-Edgan [] has joined #mythtv
12:18-!-sc00p [] has quit [Read error: 104 (Connection reset by peer)]
12:18-!-sc00p [] has joined #mythtv
12:26-!-orangey [] has quit [Remote closed the connection]
12:28<Sembiance>Anyone around at all?
12:29<Sembiance>I have some questions.
12:41<WizFactor>We all idle a lot here. Ask your question, and be patient, and someone will usually answer it eventually.
12:45<Sembiance>Okay, I'm building a system.
12:45<Sembiance>I'm going with a 'two' computer approach
12:45<Sembiance>I'll have a big server with multiple tuner cards and a big CPU sitting in the closet, being all noisy
12:45<Sembiance>just recording away, writing video file after video file to the hard drive
12:45-!-Tack [] has joined #mythtv
12:45<Sembiance>then I'm gonna have a tiny little SILENT PC next to my TV
12:46<Sembiance>it will get it's video stream via 10/100 ethernet
12:46<Sembiance>from the big box in the cloest
12:46<Sembiance>err closet
12:46<Sembiance>I'm workingon building the silent PC right now, putting together what components I'll need
12:46<Sembiance>Already got a motherboard, case, etc.
12:46<Sembiance>I was just wondering how much RAM this thing will need
12:46<Sembiance>I'd imagine I can easily get away with 256MB
12:47<Sembiance>it's just getting a video stream from the net and playing it
12:47<Sembiance>it shouldn't need too much RAM
12:47<Sembiance>Do any of you see any problems with this setup?
12:48<Sembiance>I can't think of any problems with doing it this way.
12:48<WizFactor>256 should be more than enough...
12:48<Sembiance>I'd go to 128MB but I'm only gonna save $6 by doing that :)
12:48<Tack>I'm capturing video and looking at the scrolling ticker on CNN as a gauge. It's quite jerky, although when I view it with xawtv it's of course fine. It's not harddisk speed, because I'm writing to a RAM disk for testing purposes. I've also tried mencoder using various codecs and settings, including raw copy, and in all cases it's choppy. I've tried disabling audio to rule out sync issues -- still choppy. I have RTC at 1024Hz. Any suggestio
12:50<WizFactor>Sembiance: I'd guess 128 might be enough, but probably not worth it for $6 ;)
12:50<Sembiance>wizfactor: Are there any problems you see with my design? With the main box in the closet and just the 'display unit' being next to the TV?
12:51<Sembiance>Hard drive space I'm looking at
12:51<Sembiance>I'm thinking of going with an ultra-silent small linux install
12:51<Sembiance>and go with a flash hard drive adapter to use Flash RAM has a hard drive
12:51<Sembiance>say 256MB or so maybe.
12:52<WizFactor>Sounds like a great setup to me ;)
12:52<Sembiance>cool :)
12:52<Sembiance>I figured to start with the display unit and try testing it with just some mpeg files and what not
12:52<Sembiance>then I can start recording things later on other boxes when I get around to it ;)
13:10-!-Timon [] has joined #MythTV
13:31-!-sc00p [] has quit ["Client exiting"]
13:34-!-hfb [] has joined #mythtv
13:44-!-rkulagow [] has joined #mythtv
13:48-!-Timon [] has quit [Read error: 113 (No route to host)]
13:52-!-hfb [] has quit ["Huh! Wasn't me!"]
14:06-!-Tack [] has quit [Killed (NickServ (Ghost: tack3!]
14:15-!-hadees [] has joined #mythtv
15:20-!-hadees [] has quit [Read error: 104 (Connection reset by peer)]
15:28-!-justin [] has quit [Killed (NickServ (Ghost: Justin1!]
15:28-!-justin_ [~justin@H233-225.STATE.RESNET.ALBANY.EDU] has joined #mythtv
15:42-!-Sembiance [] has quit ["thanks everyone for your help"]
15:45-!-rkulagow [] has quit [Read error: 110 (Connection timed out)]
15:46-!-rkulagow_ [] has quit [Read error: 110 (Connection timed out)]
15:46-!-rkulagow_ [] has joined #mythtv
16:19-!-root [] has joined #mythtv
16:21-!-root [] has quit [Client Quit]
16:24-!-axl [] has joined #mythtv
16:33-!-Drikus_ [] has quit ["leaving"]
16:51-!-rkulagow_ [] has quit [Read error: 110 (Connection timed out)]
16:51-!-rkulagow_ [] has joined #mythtv
16:53<-- axl( has left #mythtv
17:11-!-PhracturedBlue [] has joined #mythtv
17:11-!-PBlue_away [] has quit [Read error: 111 (Connection refused)]
17:11--> Spark^( has joined #mythtv
17:13<Spark^>if I'm getting "ERROR: something is currently using: /dev/dsp" and fuser -v /dev/dsp shows nothing, and artsd isn't running, what else can i check. i'm using non-alsa drivers (alsa went wrong when i upgraded my kernel so i reverted back)?
17:21--> Spark^^( has joined #mythtv
17:21<Spark^^>sodding modem :(
17:34--> Spark^^^( has joined #mythtv
17:40<-- Spark^has quit (Read error: 110 (Connection timed out))
18:02-!-iopener5 [] has joined #mythtv
18:11<-- Spark^^has quit (Read error: 60 (Operation timed out))
18:11<-- Spark^^^has quit (Read error: 60 (Operation timed out))
18:22-!-iopener5 [] has quit ["ChatZilla 0.8.23 [Mozilla rv:1.3/20030410]"]
20:28-!-PhracturedBlue [] has quit [Read error: 110 (Connection timed out)]
20:35-!-Viddy [] has quit ["Client exiting"]
20:37-!-crickert [] has joined #mythtv
20:38-!-bline [] has joined #mythtv
20:39<-- crickert( has left #mythtv
20:39-!-crickert [] has joined #mythtv
20:40-!-crickert [] has quit [Client Quit]
20:43-!-Viddy [] has joined #mythtv
20:44-!-PBlue_away [] has joined #mythtv
20:44-!-PBlue_away [] has quit [Client Quit]
20:58-!-foom [] has joined #mythtv
21:04-!-billytwowilly [] has joined #mythtv
21:04-!-billytwowilly [] has quit [Client Quit]
21:07-!-billytwowilly [] has joined #mythtv
21:16<billytwowilly>is anyone working on dvd ripping for mythtv? I searched the email archives for "dvd ripping" and got a bunch of stuff that doesn't really apply.
21:30-!-WizFactor [] has quit [Read error: 110 (Connection timed out)]
21:49<bigguy>billytwowilly: well the main developers aren't
21:49<bigguy>sorry for the late reply
21:49<bigguy>I just got back
21:49<billytwowilly>no prob. I'm happy I got any reply at all;)
21:49<billytwowilly>do you know if anyone is though?
21:50<bigguy>not that I know of
21:50<billytwowilly>I just picked up a dvdrom/48x cd burner that I'm going to put into my mythtv box once the mb arrives.
21:50<bigguy>why not just use DVD::Rip or whatever the best linux ripper is now
21:50<billytwowilly>and that would be a joygasmic feature;)
21:50<billytwowilly>yah, but that's a pain in the arse to use when It's hooked up to the tv.. I'd have to get a keyboard for it or something.
21:51<bigguy>well I know Isaac wouldn't put one in cvs
21:51<billytwowilly>oh well. I can't really complain. I don't know how to do it myself.
21:51<billytwowilly>why not?
21:52<billytwowilly>that would be a killer feature;)
21:52<bigguy>he said he would only allow it if it was a direct copy of the dvd and not a dvd->divx/xvid ripper
21:53<billytwowilly>but that's what would make it a killer feature..
21:53<billytwowilly>what's the reasoning behind that?
21:53<Chutt>not really
21:53<Chutt>dvds are low enough quality already
21:53<bigguy>I use my xp box for dvd ripping. unless DVD::Rip has greatly improved in the past month or so windows still has more and better option
21:54<Chutt>and there's plenty of conversion tools available elsewhere
21:54<Chutt>seems to be a waste of effort
21:54<billytwowilly>? dvd::rip blows anything I've encountered on windows away. it's literally 3 clicks, enter movie name and then wait a couple hours and it's done and done right.
21:55<bigguy>billytwowilly: The quality was very poor compared to what I get with gordianknot
21:55<bigguy>esp with the nth pass stuff thats in now
21:56<billytwowilly>really? I got amazing quality. I couldn't tell the difference between the dvd and the ripped divx movie. And all the problems I was having on windows with audio syncing were non-existant.
21:56<bigguy>I've ripped somewhere in the neighborhood of 350 movies
21:56<bigguy>if not more
21:57<billytwowilly>bigguy: I think your beef would be with the transcode people, not the dvd::rip people if the problem is quality anyway.
21:57<billytwowilly>I've ripped around 70 or so.
21:57<bigguy>well gordianknot uses virtualdub which I think is alot better anyway
21:58<bigguy>I did alot of rips using only transcode cause dvd::rip didn't have all the options I use
21:58<bigguy>but it's still not on par
21:58<billytwowilly>I couldn't argue on the merits of virtualdub and transcode, I can just comment on what I've seen and all the stuff I've ripped with transcode/dvd::rip has turned out vastly better than the stuff I did on windows.
21:59<bigguy>I always do a minimum of 2 cds with ac3 audio
21:59<billytwowilly>ahhh.. I do one cd with mp3 audio.
22:00<bigguy>I've done those as well
22:00<bigguy>back in the day ;)
22:00<billytwowilly>and I can't tell the difference from the dvd..
22:00<bigguy>poor vision ;)
22:01<billytwowilly>still, it would be cool to be able to throw in a dvd and rip it directly from mythtv.
22:01<bigguy>well you could always modify dvd::rip to suit your needs
22:02<billytwowilly>yah.. I suppose.. of course that would mean I'd have to find somewhere in my 70 hour work week to learn perl..
22:02<billytwowilly>darn non-existant coding skills;)
22:02<bigguy>you found time to irc ;)
22:03<billytwowilly>yah, for ten minutes while I'm writing an email to my girlfriend up north that I haven't seen in person since april 27...
22:03<bigguy>I haven't seen my girlfriend in ....
22:03<bigguy>oh wait I don't have one
22:04<bigguy>and I don't code either
22:04<bigguy>poor me
22:04<billytwowilly>how hard would it be to modify dvd::rip to be a part of mythtv?
22:04<bigguy>no idea
22:04<bigguy>I just know it's possible
22:04<billytwowilly>ahh, but no idea on how probable;)
22:04<billytwowilly>which usually means not probable;)
22:04<Chutt>craig longman wrote me a big long pissy email
22:04<Chutt>off list
22:05<bigguy>did he whine much?
22:05<billytwowilly>we should make him write a dvd::rip lookalike mythtv module.. he obviously has the time if he's writing long pissy emails;)
22:07<billytwowilly>Chutt: out of curiousity, what was the email regarding?
22:17-!-bigguy [] has quit [Read error: 54 (Connection reset by peer)]
22:20-!-bigguy [] has joined #mythtv
22:20-!-mdz__ [] has joined #mythtv
22:22-!-Chutt [] has quit [Read error: 110 (Connection timed out)]
22:23<foom>darn guess that explains why cvs isn't responding. ;P
22:34-!-mdz_ [] has quit [Read error: 110 (Connection timed out)]
22:40-!-Viddy [] has quit [Remote closed the connection]
22:46-!-kslater [] has quit ["Client Exiting"]
22:53-!-WizFacto1 [] has joined #mythtv
22:53-!-billytwowilly [] has quit [Remote closed the connection]
22:54-!-WizFacto1 [] has quit [Client Quit]
22:54-!-mdz__ [] has quit [Read error: 60 (Operation timed out)]
22:55-!-WizFactor [] has joined #mythtv
22:57-!-mykilx [] has joined #mythtv
22:59<mykilx>was curious if i can use mythtv with dishnetwork satellite system ?
22:59<mykilx>just found out about it today, looks great
22:59<bigguy>sure you can
22:59<bigguy>you still need a tv tuner card
23:00<mykilx>cool, i didn't find any info about what type of input you needed, wasn't sure if it only worked with cable
23:00<mykilx>so i couldn't use a card with video in, has to be a tuner card ?
23:00<bigguy>lots of people on the mailing list use it with dish and direc
23:01<mykilx>i'll prolly build a new box just for it
23:01<mykilx>i haven't gotten to the mailing lists yet lol
23:01<bigguy>right you need a card that's supported by either v4l or the ivtv stuff
23:01<bigguy>the ivtv stuff is a v4l2 interface for the haupage wintv PVR-250 and 350
23:02<mykilx>i suppose different cards give different quality/results
23:02<bigguy>supports mpeg2 video/audio hardware encoding
23:02<mykilx>are the haupage cards the way to go ?
23:02<bigguy>if you have the money I would think so
23:02<bigguy>although the driver is still in development
23:03<mykilx>or something like the AIW radeons?
23:03<bigguy>AIW isn't supported
23:03<mykilx>i'll have to check out prices
23:04<mykilx>i've been wanting to get a tivo, or a replay, but this looks alot better, and alot more fun
23:04<bigguy>I think the PVR-x50's are in the 100-200 dollar range
23:05<bigguy>you can get a cheaper bttv card but it's quality will be less and you'll be recording in mpeg4/mp3
23:05<mykilx>ATHLON XP 2500 "Barton" 128 bucks, they really came down in price from the last i looked
23:05<bigguy>I wish I had some money to spend on a new box now
23:05<mykilx>yeah, if i build a new box, i don't wanna fsck around lol
23:06<bigguy>if I had the money I'd wait for the x86-64 machines
23:06<bigguy>try to get a 4way box
23:07<foom>last i checked quality of mpeg4 encoding was better than mpeg2 encoding
23:07<mykilx>you think it will be worht the $$ at this point in time ?
23:07<foom>only reason there's so much excitement about pvr250 is that it is practically free CPU-wise
23:08<bigguy>mykilx: I said if I had the money ;)
23:08<mykilx>ok i see yor point
23:08<mykilx>if only my damn lotto numbers would hit
23:16-!-Viddy [] has joined #mythtv
23:21-!-Chutt [] has joined #mythtv
23:36* bigguyis [away -={ SLEEP }=- ]
23:38<Chutt>foom, you the guy that started the alsa stuff?
23:39<foom>i am
23:39<foom>chutt: would you like a mirror of your CVS repository?
23:39<foom>i can host an rsync'd version of it if you want
23:39<foom>public access read-only
23:40<Chutt>quite possibly
23:40<Chutt>notice it was down just now or something? =)
23:40<foom>yes. :)
23:40<Chutt>foom, i _will_ apply that, i was just wondering why you wanted to add it
23:40<Chutt>my power was out for an hour and a half
23:41<Chutt>anon cvs is working now, right?
23:42<Chutt>probably should make sure that the machine came back to life properly
23:42<foom>a few reasons: The ALSA code is much simpler than the OSS code, linux is moving towards alsa so new features show up only in that, so it seems like a good idea to have support for, and also because I had problems getting the alsa OSS emu to work right
23:42<Chutt>well, linux is moving towards the alsa _drivers_
23:42<Chutt>not the lib
23:42<Chutt>can you make things (eventually) optional?
23:43<Chutt>don't really want to add another dep
23:43<foom>it is fully optional except i don't know how to do the build process right
23:43<Chutt>i can work that out
23:43<Chutt>just add the proper ifdefs and stuff
23:43<foom>it's just one file, i can put ifdefs around the whole thing
23:43<Chutt>well, i assume there's some config code to add to the settings stuff, too
23:43<foom>yeah i haven't worked out that part yet. ;)
23:44<foom>it would be nice if you could type into the config fields
23:44<Chutt>line edits?
23:44<Chutt>or you want a combo box
23:44<Chutt>that's editable
23:44<Chutt>have you looked at mythmusic's audio stuff yet?
23:44<foom>i don't know if i *need* it to be editable or not but it sure would be nice if edits saved
23:44<foom>i just started looking at it
23:45<Chutt>it would be kinda neat if the two shared the output class
23:45<foom>my first goal was to make it work exactly like it does now for OSS and also have ALSA output
23:45<foom>which is working now. :)
23:46<foom>so yeah, I'm looking at the mythmusic stuff now
23:46-!-hfb [] has joined #mythtv
23:47<foom>I think I should have a complete working output half patch done soon, except proper GUI config
23:47<foom>should I work on that to get applied alone first? or keep doing the whole thing until it's all done?
23:48<Chutt>it probably won't be able to be activated without the gui stuff, right?
23:48<foom>unless you poke the DB yourself
23:48<Chutt>so as long as it doesn't break anything, doesn't really matter
23:48<foom>do you know if i can test the reencode stuff?
23:49<foom>that's part of the disabled transcode support right?
23:49<foom>i mean I'm gonna put in code that's likely to work but I don't know how to test it. :)
23:49<Chutt>yeah, that's the transcode stuff
23:49<Chutt>looks like the author's awol, though
23:49<Chutt>or i pissed him off by disabling all that =)
23:51<foom>so yeah, if you want, I can mirror your cvs repo for you on a nice fat pipe so you don't have to waste your dsl upstream on random people updating all the time. :)
23:51<Chutt>i'll get back to you on that
23:51<Chutt>but, i'll probably go for it
23:51<Chutt>i _may_ be getting some better hosting
23:52<Chutt>so if i do, i'll just stick the cvs server there
23:52-!-Viddy [] has quit [Remote closed the connection]
23:54<foom>oh yeah, one thing, I wasn't entirely sure from your message what the impact of the video_frame_rate in the OSS output code was
23:55<foom>as far as I know it doesn't matter how much data you wait to buffer before sending it to the soundcard
23:55<foom>but obviously someone thought that there was a reason to sync it to the framerate
23:55<Chutt>i think the idea was not to have too much data sitting in the soundcard buffers
23:56<Chutt>and i think it made the a/v sync code simpler
23:56<foom>I don't think it impacts it at all
23:57<foom>unless there's somethign I'm missing. :)
23:57-!-Viddy [] has joined #mythtv
23:57-!-Viddy [] has quit [Client Quit]
23:58-!-Viddy [] has joined #mythtv
23:58<foom>i guess maybe it's trying to calculate how much gets added to the buffer at once
23:59<foom>but that seems quite odd. Anyhow, my conclusion is that it serves no purpose and I'll hardcode works for me, and from what you've said I still think that should be fine.