[RealMac]

I'm using EyeTV on a Mac Pro equipped with 10.4.9 and an EyeTV USB Hybrid. I seem to have issues with the software. Sometimes it crashes on me and when I try to quit it the OS will not let me. Other times it appears to be making attempts to record, but doesn't actually do so. Here is a screenshot... Obviously since the files did not write to disk I get a -50 error. Was wondering if anyone else has experienced these issues. If so, what did you do to address them?



I'm downgrading to 2.3.1 to see if the problems continue to be an issue.

[RealMac]

[RealMac]

I used to have the hardware plugged directly into the front of my machine. Now I have it plugged into my USB hub to see if conditions improve.

Machine Name: Mac Pro
Machine Model: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 4 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B04
SMC Version: 1.7f8

[RealMac]

If anyone is reading this, if you contact ElGato directly they will send you a newer build. I am running 2.4b22 on my machine now. Still evaluating system stability. This morning my machine actually paniced. I sent the panic.log along with my system profile to bugreporter.apple.com as well.

*********

Tue Mar 20 02:01:30 2007
panic(cpu 1 caller 0x003A33C1): IOGMD: not wired for the IODMACommand
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x48aabc08 : 0x128d08 (0x3cb134 0x48aabc2c 0x131de5 0x0)
0x48aabc48 : 0x3a33c1 (0x3ef2d8 0x7ecb630 0x48aabc88 0x8c2ddd0)
0x48aabcc8 : 0x3a365d (0x7ba4100 0x3 0x48aabce0 0x80)
0x48aabd68 : 0x3a3012 (0x7ba4100 0x0 0x48aabdac 0x3bde54)
0x48aabdc8 : 0x61138bef (0x7ba4100 0x0 0x8ef66b4 0x20)
0x48aabdf8 : 0x5fdba87e (0x8156700 0x8ef6680 0xe000400e 0x8ef66b4)
0x48aabe38 : 0x5fdc8f64 (0x71df800 0x72beb40 0xe000400e 0x8ef66b4)
0x48aabe68 : 0x5ffeaecc (0x71df800 0x73c9a00 0x48aabe88 0x5ffef464)
0x48aabe88 : 0x5ffe6041 (0x71df800 0x73c9a00 0x0 0x6)
0x48aabec8 : 0x5ffe89d3 (0x71df800 0x0 0x1 0x1352bb)
0x48aabee8 : 0x5ffe18e0 (0x71df800 0x0 0x706c970 0x706c8b0)
0x48aabf08 : 0x39a463 (0x71df800 0x0 0x1 0x38073e)
0x48aabf58 : 0x399635 (0x7340400 0xe03 0x48aabf78 0x58ba7038)
0x48aabf88 : 0x39936b (0x72b4a00 0x2c 0x6c 0xffffffff)
0x48aabfc8 : 0x19ac1c (0x72b4a00 0x0 0x19e0b5 0x818b340) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBUserClient(2.7.0)@0x61135000
dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x5fdb7000
com.apple.driver.AppleUSBEHCI(2.7.0)@0x5ffde000
dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x5fdb7000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x58a05000
com.apple.iokit.IOUSBFamily(2.6.5)@0x5fdb7000

Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386

[mikeylee]

Realmac,

I had the exact same issue and found out it is a problem with the Eyetv USB hybrid not re-initalizing after the computer goes to sleep. You have to unplug it, wait a few seconds, and then plug it back in. It is a pain but does not do it if you restart the computer. Just waking up from sleep mode. I changed my power settings so the screen and the hard drive shut down, but ht e computer does not go to sleep and have had no problems.

I hope that helps a bit,

Mikeylee

[RealMac]

Mikeylee, thanks for replying to my post when no one else did. So far with the new beta I have not experienced this problem or any other general system stability issues. I'm trying to avoid having to unplug / plug back in if at all possible. Once again I will keep people on here updated about my experiences.

[hldan]

Originally Posted by mikeylee 

Realmac,

I had the exact same issue and found out it is a problem with the Eyetv USB hybrid not re-initalizing after the computer goes to sleep. You have to unplug it, wait a few seconds, and then plug it back in. It is a pain but does not do it if you restart the computer. Just waking up from sleep mode. I changed my power settings so the screen and the hard drive shut down, but ht e computer does not go to sleep and have had no problems.

I hope that helps a bit,

Mikeylee

You might want to check with Elgato in regards to this. I bought 2 EyeTV Hybrids at Macworld this year. One of them worked perfectly and the other wouldn't initialize after my Mac woke up from sleep. I emailed Elgato and first they sent me the beta software and I wasn't interested in installing it because one of my units worked perfectly so I didn't want beta software for the other one so Elgato ended up exchanging it and all is good. It's a known issue.

[RealMac]

Hi hldan. I don't put my machine to sleep, but will try this out later on. So far a day of testing and no problems.

[RealMac]

Another kernel panic:
*********

Sat Mar 24 04:01:25 2007
panic(cpu 0 caller 0x003A33C1): IOGMD: not wired for the IODMACommand
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x48b1bcd8 : 0x128d08 (0x3cb134 0x48b1bcfc 0x131de5 0x0)
0x48b1bd18 : 0x3a33c1 (0x3ef2d8 0x8048900 0x48b1bd68 0xaa1cdd0)
0x48b1bd98 : 0x3a365d (0xb55a200 0x3 0x48b1bdb0 0x80)
0x48b1be38 : 0x3a3012 (0xb55a200 0x0 0x48b1be7c 0x3bde54)
0x48b1be98 : 0x610abbef (0xb55a200 0x0 0x8fc38b4 0x20)
0x48b1bec8 : 0x5fd9587e (0x923b700 0x8fc3880 0xe000400e 0x8fc38b4)
0x48b1bf08 : 0x5fda3f64 (0x71ce000 0x72e13c0 0xe000400e 0x8fc38b4)
0x48b1bf38 : 0x5ffc5ecc (0x71ce000 0x839ed80 0x48b1bf68 0x1a3010)
0x48b1bf58 : 0x5fda3ef6 (0x71ce000 0x839ed80 0x48b1bf78 0x19e23a)
0x48b1bf78 : 0x13d7d9 (0x71ce000 0x839ed80 0x0 0x0)
0x48b1bfc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x8aca3b4) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBUserClient(2.7.0)@0x610a8000
dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x5fd92000
com.apple.driver.AppleUSBEHCI(2.7.0)@0x5ffb9000
dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x5fd92000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x589e0000
com.apple.iokit.IOUSBFamily(2.6.5)@0x5fd92000

Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386


*********

[Rev2Liv]

I'm not running with nearly as much firepower as you guys, but on my Intel Mac Mini Core Duo 1.83Ghz, When I load EyeTV, it often states "Device Could not be initialized." My usual fix is to unplug and replug the EyeTV Hybrid or quit the app and then relaunch it. PITB, hopefully they'll fix this problem soon.

[hldan]

Originally Posted by Rev2Liv 

I'm not running with nearly as much firepower as you guys, but on my Intel Mac Mini Core Duo 1.83Ghz, When I load EyeTV, it often states "Device Could not be initialized." My usual fix is to unplug and replug the EyeTV Hybrid or quit the app and then relaunch it. PITB, hopefully they'll fix this problem soon.

Okay I spoke too soon, my new replacement also has the issue of "Device could not be initialized". Elgato just sent me the link to download the beta software. I will install it and test it out and report back my experiences. My only concern is I have 2 of the Hybrids and it only happens to one of them but most issues are software related so I will try this first. I don't like the fact that Elgato does not have a customer support 800 number. The only offer email support. That sux!

[fmcgirt]

Today I bought an EyeTV 250 to use to transfer VHS tapes to my MacBook Pro with 10.4.9 from a Sony SLV-D300P VCR/DVD combo. Also tried a Sony DVP-S360 but can't get past the "Device cannot be initialized" message. Both units work fine on a TV so I know they are OK.

Elgato sent me the latest beta, 2.4b29, but no joy. Have tried other USB ports, system restarts, plug/unplugs, etc., so I am beginning to think I have a bad device. Wonder what the failure rate is on 250's?

Also is there a better (more reliable) way to do this?

Thanks for any help or info,

Frank

[hldan]

Originally Posted by fmcgirt 

Today I bought an EyeTV 250 to use to transfer VHS tapes to my MacBook Pro with 10.4.9 from a Sony SLV-D300P VCR/DVD combo. Also tried a Sony DVP-S360 but can't get past the "Device cannot be initialized" message. Both units work fine on a TV so I know they are OK.

Elgato sent me the latest beta, 2.4b29, but no joy. Have tried other USB ports, system restarts, plug/unplugs, etc., so I am beginning to think I have a bad device. Wonder what the failure rate is on 250's?

Also is there a better (more reliable) way to do this?



Thanks for any help or info,

Frank

I'm inclined to think that some of the newer models seem to work differently with the current software. I have 2 models and one of them works great with the software out of the box and the other had the issues with "Device Cannot be Initialized". As I posted earlier I offered to post back my experiences with the beta software that Elgato sent me. I tried it and I have had zero issues. My Mac wakes from sleep and records my shows and all is well. Elgato will need to offer a much better version of their software because every version so far crashes every now and then. It's acceptable but it's annoying when your favorite show is being recorded.

Anyways I noticed that your software version is different than what Elgato sent me. I have version 2.3.3 (build 2499). If that's not the version you have then can try this link and get the version I have. Try it and let us know your experiences. Under most cases when it comes to computer related issues it's usually software issues and not the hardware.
http://downloads.elgato.com/downloads/eyetv233-2499.zip

[fmcgirt]

hidan,

Thanks for the response. I have tried three SW versions: 2.3.1, 2.3.3 and the beta 2.4b29, all with about the same results. After plugging in the 250 I first get the "No signal" screen, then the "Please wait a moment screen" and then the "Device cannot be initialized screen". Obviously, USB detects the plugin but the 250 is unable to pass any signal or at least the sw doesn't detect any. Sure is a pain. Unless Elgato comes up with something tomorrow I think I am headed for a Canopus ADVC110. It is firewire and supposedly interfaces nicely with iMovie and iDVD.

Thanks for the help,

Frank

[hldan]

Originally Posted by fmcgirt 

hidan,

Thanks for the response. I have tried three SW versions: 2.3.1, 2.3.3 and the beta 2.4b29, all with about the same results. After plugging in the 250 I first get the "No signal" screen, then the "Please wait a moment screen" and then the "Device cannot be initialized screen". Obviously, USB detects the plugin but the 250 is unable to pass any signal or at least the sw doesn't detect any. Sure is a pain. Unless Elgato comes up with something tomorrow I think I am headed for a Canopus ADVC110. It is firewire and supposedly interfaces nicely with iMovie and iDVD.

Thanks for the help,

Frank

Did you try the version that I posted? It's a beta. There's 2 versions of "2.3.3" One is the retail and one is the beta. The one I posted is the beta and solved my issue. It's version 2.3.3 (2499). The retail one is (2429)

[JKT]

One other thing, what USB port are you plugging the device into? If it isn't on the Mac itself, try that. If you are using a hub, it could be the USB port on the hub that is causing you issues.

[fmcgirt]

Thanks for both suggestions. Yes, I have tried both USB ports on the MacBook Pro and my USB Hub. Also I have tried the 2499 build along with the rest. It actually seemed to work for awhile and only after a restart. Then when I started the VHS Asssitant the screen went to "Device cann..." and never came back. I have tried several restarts since then and it has never worked again. I really don't think it is my USB port since I use it often for other stuff with no glitches.

Frank

EDIT: Just tried SW 2.2.1 and it seemed to work for about 30-45 sec and then the video froze and the message "Channel not available.." appeared. I really hate this but I guess I am just too used to other Apple stuff just plugging in and working. EyeTV really needs to do some QA and further development on their products - 250 at least.

[hldan]

Originally Posted by fmcgirt 

Thanks for both suggestions. Yes, I have tried both USB ports on the MacBook Pro and my USB Hub. Also I have tried the 2499 build along with the rest. It actually seemed to work for awhile and only after a restart. Then when I started the VHS Asssitant the screen went to "Device cann..." and never came back. I have tried several restarts since then and it has never worked again. I really don't think it is my USB port since I use it often for other stuff with no glitches.

Frank

EDIT: Just tried SW 2.2.1 and it seemed to work for about 30-45 sec and then the video froze and the message "Channel not available.." appeared. I really hate this but I guess I am just too used to other Apple stuff just plugging in and working. EyeTV really needs to do some QA and further development on their products - 250 at least.

Okay, then you will need to contact Elgato and get an exchange. I had to do that for my other unit but not because of the connection issue, it was physically damaged out of the box. I went to the website and put in a ticket and within 48 hours they sent me a replacement. I think you have done everything you should have gone through. The EyeTV devices are not all like this so most likely you will get a replacement that works just fine. Don't hestitate, put in a ticket now for your replacement.
One last thing, if they send you another one be sure and use Spotlight to search and remove all traces of the EyeTV software then reinstall directly from the included CD.

[fmcgirt]

Thanks, hidan. I just got an email from them saying they were sending me an "advanced replacement" so hopefully I will be OK. And i will remove all the EyeTV stuff before using it.

I really appreciate your help and suggestions.

Frank

[hldan]

Originally Posted by fmcgirt 

Thanks, hidan. I just got an email from them saying they were sending me an "advanced replacement" so hopefully I will be OK. And i will remove all the EyeTV stuff before using it.

I really appreciate your help and suggestions.

Frank

Cool, glad I could help. One thing, my name is HLDAN not HiDan. It looks like an "i" but it's an "L". Darn MacNN and their weird fonts!

[fmcgirt]

Originally Posted by hldan 

Cool, glad I could help. One thing, my name is HLDAN not HiDan. It looks like an "i" but it's an "L". Darn MacNN and their weird fonts!

Sorry about that.

[RealMac]

I posted this video to my website: http://www.therealmac.net/mac/eyetvunabletoquit.mp4

[hldan]

Originally Posted by RealMac 

I posted this video to my website: http://www.therealmac.net/mac/eyetvunabletoquit.mp4

Mine has done that at times but it's not just EyeTV. Some programs won't force quit due to the processes they are in the middle of. The only way to get out of it is to log out and log back in. You don't have to restart. It will force quit.

[JKT]

With my EyeTV DTT, if I have to force quit the EyeTV software due to a crash, I also need to unplug the device to cause the programme to terminate completely, otherwise it will stay (crahsed, but) running.

Try it the next time it happens for you. Unplug the device after selecting force quit and the process will end. Leave it unplugged for a few seconds (10+), then plug it back in and you should be able to open EyeTV again (or it will launch automatically if that is how you have it set up in the preferences).

[RealMac]

I unplugged it and still it wouldn't quit. Maybe I didn't have it unplugged long enough though. We'll see what happens.

[JKT]

Try force quitting then unplugging the device - it should quit as soon as you unplug it if it "works" the same way as my DTT.

[RealMac]

I went to work, came back and my machine paniced. This is upsetting...

panic(cpu 3 caller 0x003A33C1): IOGMD: not wired for the IODMACommand
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x48803cd8 : 0x128d08 (0x3cb134 0x48803cfc 0x131de5 0x0)
0x48803d18 : 0x3a33c1 (0x3ef2d8 0xb967e9c 0xb91fa70 0x808d3b8)
0x48803d98 : 0x3a365d (0x9d1ad80 0x3 0x48803db0 0x80)
0x48803e38 : 0x3a3012 (0x9d1ad80 0x0 0x48803e7c 0x3bde54)
0x48803e98 : 0x60fadbef (0x9d1ad80 0x0 0x9d070b4 0x20)
0x48803ec8 : 0x5fd9587e (0x8122000 0x9d07080 0xe000400e 0x9d070b4)
0x48803f08 : 0x5fda3f64 (0x71ce000 0x72e5f00 0xe000400e 0x9d070b4)
0x48803f38 : 0x5ffc5ecc (0x71ce000 0x73a6400 0x48803f68 0x1a3010)
0x48803f58 : 0x5fda3ef6 (0x71ce000 0x73a6400 0x48803f78 0x19e23a)
0x48803f78 : 0x13d7d9 (0x71ce000 0x73a6400 0x19e23a 0x809fbb4)
0x48803fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x809fb70) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBUserClient(2.7.0)@0x60faa000
dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x5fd92000
com.apple.driver.AppleUSBEHCI(2.7.0)@0x5ffb9000
dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x5fd92000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x589e0000
com.apple.iokit.IOUSBFamily(2.6.5)@0x5fd92000

Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386

Model: MacPro1,1, BootROM MP11.005C.B04, 4 processors, Dual-Core Intel Xeon, 2.66 GHz, 4 GB
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Memory Module: DIMM Riser A/DIMM 1, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 2, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 3, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 4, 512 MB, DDR2 FB-DIMM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (4.80.79.1)
Network Service: AirPort, AirPort, en2
Network Service: Parallels Host-Guest, Ethernet, en3
Network Service: Parallels NAT, Ethernet, en4
PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-1
Serial ATA Device: ST3160812AS P, 149.05 GB
Serial ATA Device: HDS722525VLSA80, 232.89 GB
Parallel ATA Device: SONY DVD RW DW-D150A, 1.35 GB
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: Natural® Ergonomic Keyboard 4000, Microsoft, Up to 1.5 Mb/sec, 500 mA
USB Device: USB-PS/2 Optical Mouse, Logitech, Up to 1.5 Mb/sec, 500 mA
USB Device: Apple Cinema HD Display, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: USB2.0 MFP(Hi-Speed), EPSON, Up to 480 Mb/sec, 500 mA
USB Device: iMic USB audio system, Griffin Technology, Inc, Up to 12 Mb/sec, 500 mA
FireWire Device: iSight, Apple Computer, Inc., Up to 400 Mb/sec
FireWire Device: built-in_hub, unknown_value, Unknown
FireWire Device: ST3750640A, Seagate, Up to 400 Mb/sec
FireWire Device: unknown_device, unknown_value, Unknown

[King Bob On The Cob]

Originally Posted by RealMac 

I went to work, came back and my machine paniced. This is upsetting...

panic(cpu 3 caller 0x003A33C1): IOGMD: not wired for the IODMACommand
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x48803cd8 : 0x128d08 (0x3cb134 0x48803cfc 0x131de5 0x0)
0x48803d18 : 0x3a33c1 (0x3ef2d8 0xb967e9c 0xb91fa70 0x808d3b8)
0x48803d98 : 0x3a365d (0x9d1ad80 0x3 0x48803db0 0x80)
0x48803e38 : 0x3a3012 (0x9d1ad80 0x0 0x48803e7c 0x3bde54)
0x48803e98 : 0x60fadbef (0x9d1ad80 0x0 0x9d070b4 0x20)
0x48803ec8 : 0x5fd9587e (0x8122000 0x9d07080 0xe000400e 0x9d070b4)
0x48803f08 : 0x5fda3f64 (0x71ce000 0x72e5f00 0xe000400e 0x9d070b4)
0x48803f38 : 0x5ffc5ecc (0x71ce000 0x73a6400 0x48803f68 0x1a3010)
0x48803f58 : 0x5fda3ef6 (0x71ce000 0x73a6400 0x48803f78 0x19e23a)
0x48803f78 : 0x13d7d9 (0x71ce000 0x73a6400 0x19e23a 0x809fbb4)
0x48803fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x809fb70) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBUserClient(2.7.0)@0x60faa000
dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x5fd92000
com.apple.driver.AppleUSBEHCI(2.7.0)@0x5ffb9000
dependency: com.apple.iokit.IOUSBFamily(2.6.5)@0x5fd92000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x589e0000
com.apple.iokit.IOUSBFamily(2.6.5)@0x5fd92000

Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386

Model: MacPro1,1, BootROM MP11.005C.B04, 4 processors, Dual-Core Intel Xeon, 2.66 GHz, 4 GB
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Memory Module: DIMM Riser A/DIMM 1, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 2, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 3, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 4, 512 MB, DDR2 FB-DIMM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (4.80.79.1)
Network Service: AirPort, AirPort, en2
Network Service: Parallels Host-Guest, Ethernet, en3
Network Service: Parallels NAT, Ethernet, en4
PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-1
Serial ATA Device: ST3160812AS P, 149.05 GB
Serial ATA Device: HDS722525VLSA80, 232.89 GB
Parallel ATA Device: SONY DVD RW DW-D150A, 1.35 GB
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: Natural® Ergonomic Keyboard 4000, Microsoft, Up to 1.5 Mb/sec, 500 mA
USB Device: USB-PS/2 Optical Mouse, Logitech, Up to 1.5 Mb/sec, 500 mA
USB Device: Apple Cinema HD Display, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: USB2.0 MFP(Hi-Speed), EPSON, Up to 480 Mb/sec, 500 mA
USB Device: iMic USB audio system, Griffin Technology, Inc, Up to 12 Mb/sec, 500 mA
FireWire Device: iSight, Apple Computer, Inc., Up to 400 Mb/sec
FireWire Device: built-in_hub, unknown_value, Unknown
FireWire Device: ST3750640A, Seagate, Up to 400 Mb/sec
FireWire Device: unknown_device, unknown_value, Unknown

I'm just a low level peon tech worker, and hacker of OS X, but this is what my intuition leads me to believe.

Lets look at your crash log...

IODMACommand is a class to convert memory references to I/O bus addresses.

Tell ElGato that they may be trying to write to a memory space that was marked as read (probably writing to a read buffer during the prepare call of IODMACommand, or forgetting a complete command) . It's a problem that comes up with 64-bit machines according to this technical article:

http://developer.apple.com/technotes/tn/tn2090.html

In specific, this part of the article:

"Because the DART requires different caching for reads and writes, the DMA direction is important on hardware that includes a DART. While you may receive random failures if the direction is wrong in general (on any system), if you attempt to call WriteBytes on a memory region whose DMA direction is set up for reading, you will cause a kernel panic on 64-bit hardware."

Looking at your crash log, it may be happening as your computer is recognizing the EyeTV hardware (Your system profile log does not indicate that the EyeTV is connected to your computer.) or it is entirely unrelated to your EyeTV.

Best of luck with all this though.

[kat81]

just thought I'd jump in. I've had my eyetv 250 for...I think I got it as soon as it came out. Never had any major issues with it, either. The few issues I've had were either resolved with email Elgato tech support, or with software updates. Recently I had an issues, so they sent me a beta. It didn't fully fix things, and they said that 2.4 will be released within a few weeks, and it has a few major additions/changes.
So I'm not sure why so many of you are having issues. Maybe my iMac G5 and EyeTV 250 just love eachother

[fmcgirt]

As a quick followup. Still waiting for my 250 replacement and borrowed a Canopus ADVC 110 which has a fireware connector to MacBook Pro and no extra required software. For transferring VHS tapes tp iMovie it just works and actualy seems to improve the original tape quality!!! I highly recommend it.

Now if I could just find a way to improve the iDVD encode speed of a shared iMovie project, all would be great.

Thanks for all the help and suggestions on the EyeTV 250.

Frank

[RealMac]

King Bob on the Cob, I relayed the message to support who in turn said they would relay it to their programmers. Hopefully some good will come out of this.

[hldan]

Originally Posted by fmcgirt 

Now if I could just find a way to improve the iDVD encode speed of a shared iMovie project, all would be great.

Thanks for all the help and suggestions on the EyeTV 250.

Frank

iDVD encode speed will be much faster if you don't add a music track to your iMovie project. It's encoding the audio and the video together that slows the process.

[RealMac]

I have switched eyetv over to use one my internal drive instead of my external. We shall see if the crashing / quitting issues persist. My internal drives don't go to sleep at all. I've been unable to prevent my external from sleeping. ::crosses fingers:::

[fmcgirt]

Originally Posted by hldan 

iDVD encode speed will be much faster if you don't add a music track to your iMovie project. It's encoding the audio and the video together that slows the process.

So how do I handle the audio from an old movie on VHS tape that I want to transfer to DVD using iMovie/iDVD? Can I add the audio from the tape after encoding the video?

Frank

[fmcgirt]

Actually I believe I am encoding the audio and video separately in iDVD. It encodes the Menu asset, then the Video asset and finally the Audio asset before burning the DVD. And it is encoding the Video asset that takes about 3X real movie play time. The audio goes pretty fast after the video is finished. I am using a 1.8MHZ Duo with 2GB memory and no other apps running.

Is there better (faster) software that I could be using instead of the iMovie/iDVD combo?

Thanks for the help,

Frank

[hldan]

Originally Posted by fmcgirt 

Actually I believe I am encoding the audio and video separately in iDVD. It encodes the Menu asset, then the Video asset and finally the Audio asset before burning the DVD. And it is encoding the Video asset that takes about 3X real movie play time. The audio goes pretty fast after the video is finished. I am using a 1.8MHZ Duo with 2GB memory and no other apps running.

Is there better (faster) software that I could be using instead of the iMovie/iDVD combo?

Thanks for the help,

Frank

How are you getting the A/V footage from your VHS to your Mac? Are you using the transfer box from EyeTV? Well when transferring from VHS or a Camcorder you have no other choice but to record both the audio and the video at the same time. The video does indeed take longer to encode this way however if you were to lay your own audio track or if you modify the existing audio track transferred from VHS the audio encoding takes 2x as long. Always count on about 2hrs to burn to iDVD from iMovie. When dealing with video you don't really want high speed X-fer because the quality will go way down. Even if it looks like it's stuck and you get a beachball it's acutally encoding and it will finish.

[fmcgirt]

Originally Posted by hldan 

How are you getting the A/V footage from your VHS to your Mac? Are you using the transfer box from EyeTV? Well when transferring from VHS or a Camcorder you have no other choice but to record both the audio and the video at the same time. The video does indeed take longer to encode this way however if you were to lay your own audio track or if you modify the existing audio track transferred from VHS the audio encoding takes 2x as long. Always count on about 2hrs to burn to iDVD from iMovie. When dealing with video you don't really want high speed X-fer because the quality will go way down. Even if it looks like it's stuck and you get a beachball it's acutally encoding and it will finish.

I am using a Canopus 110 to get video from a VCR to the Mac. Firewire device that works great! And actually improves tape quality. Still waiting for the EyeTV 250 replacement - not impressed with their device (probably software) or service. Guess if you want TV though they must be best.

I have never seen the beachball except when iDVD is encoding the audio - then it isn't for long. To burn a 2hr movie using iDVD after transferring the project from iMovie takes about 5 hours.

Frank

[hldan]

Originally Posted by fmcgirt 

I am using a Canopus 110 to get video from a VCR to the Mac. Firewire device that works great! And actually improves tape quality. Still waiting for the EyeTV 250 replacement - not impressed with their device (probably software) or service. Guess if you want TV though they must be best.

I have never seen the beachball except when iDVD is encoding the audio - then it isn't for long. To burn a 2hr movie using iDVD after transferring the project from iMovie takes about 5 hours.

Frank

Yeah, that sounds about right, most of the movies I record on my camcorder are about 45 minutes and the encoding and burn time are about 2 hrs. So if your 2hr movie takes about 5 hrs to encode and burn that makes sense.
I don't know all the necessary process iDVD needs to go through but you should try burning your final movie to Roxio Toast Titanium. I just end up using iDVD because of the one button convenience but Toast may encode and burn in less time. The best thing to do is merge just 20 minutes of video from your VHS into iMovie and then transfer it to Toast (if you have Toast) and see how long the encoding and burning takes.
Then do the same thing on iDVD from iMovie and compare the times. If you have never tried it Toast is the best app that should be on every Mac.
BTW, EyeTV Hybrid is the best by far and eats up anything on the Windows side but the software is buggy as hell. It's not the hardware. We may have to wait for the next version of EyeTV for it to work well.

[fmcgirt]

Thanks, I'll try Toast.

[fmcgirt]

I tested Toast but I can't tell much difference in encoding speed from iDVD.

Also today I finally received a replacement for my 250 but they sent a Hybrid Stick instead of the correct device. Plus it took them from 3/27 until today to get it to me by UPS ground. This company really sucks!!!!!

Frank

[hldan]

Originally Posted by fmcgirt 

I tested Toast but I can't tell much difference in encoding speed from iDVD.

Also today I finally received a replacement for my 250 but they sent a Hybrid Stick instead of the correct device. Plus it took them from 3/27 until today to get it to me by UPS ground. This company really sucks!!!!!

Frank

Sorry to hear that. I have been lucky getting super fast service from them because I live in the San Francisco Bay Area which is the same place Elgato's headquarters are. Well email them and tell them to send you the right one. Specifically request for a brand new one inside the retail box since you've been inconvenienced. As far as Toast vs. iDVD, it was worth a try but they most likely work the same.

[fmcgirt]

hldan,

Had to cancel a Toast session and it left a very large portion of my HD unavailable. Do you know where this area might be stored?

Frank

[hldan]

Originally Posted by fmcgirt 

hldan,

Had to cancel a Toast session and it left a very large portion of my HD unavailable. Do you know where this area might be stored?

Frank

Wow, never heard of that happening. I know iDVD and Toast suck up a lot of ram during a session so it's possible a portion of hard disk is reserved during a session. The best thing to do in this situation is to reset PRAM. Upon a restart, after the chime sounds hold down all buttons on the keyboard "Cmd,Option, P,R". Wait for the chime to sound again and let go and it will restart.

[fmcgirt]

Originally Posted by fmcgirt 

hldan,

Had to cancel a Toast session and it left a very large portion of my HD unavailable. Do you know where this area might be stored?

Frank

Never mind. It released it. I thought it was just a temp area that should have been released on Toast exit but it took a while. Probably because it was about 80GB.

Have already emailed them about the mixup but no response as yet.

Thanks for the help.

Frank

[RealMac]

Running 2.4b32 now, part of the problem I've been experiencing is due to my drive not being able to keep up with the data quickly enough. The lack of write ability somehow is causing the audio to stop completely. A possible solution here would be to have a drive dedicated solely to video vs having it for bittorrent, and watching movies from. I will experiment with the standard DVD setting to see how I fare. In other news, I accidentally deleted my EyeTV folder. Well I saved 25gb off a drive that was almost full to begin with. Doh.

[fmcgirt]

Still no response from EyeTV about defective device and mistaken shipment of Hybrid instead of replacement 250. This has been going on since Mar 26 (2007). Anybody got any ideas about how to get them to stand behind their stuff and respond. I have now sent three emails with nothing.

Frank

[pastafazoule]

hi i just received my eyetv hybrid replacement and its doing the same thing as the first one,Device Could Not Be Initialized when i start up the computer, so i have to pull the usb and put back in and it works,what do i do now,i am running 2.4b29,is there a newer software version

[fmcgirt]

Originally Posted by fmcgirt 

Still no response from EyeTV about defective device and mistaken shipment of Hybrid instead of replacement 250. This has been going on since Mar 26 (2007). Anybody got any ideas about how to get them to stand behind their stuff and respond. I have now sent three emails with nothing.

Frank

Finally got a response at 11:00 AM yesterday and continued conversations today. Turns out the person at Elgato was not available last Friday and over the weekend to respond to my emails. Replacement 250 is being shipped and hopefully that will resolve the issue.

Frank

[RealMac]

Originally Posted by pastafazoule 

hi i just received my eyetv hybrid replacement and its doing the same thing as the first one,Device Could Not Be Initialized when i start up the computer, so i have to pull the usb and put back in and it works,what do i do now,i am running 2.4b29,is there a newer software version

See PM

[RealMac]

For what it's worth, I've been running beta 32 for a few days without a kernel panic. I'm not going to lie, I like to have recording at the highest quality possible, even without HD. I still am reluctant to set the app to record at its highest setting until I have an ample amount of free HD space.

2.7GB per hour with MPEG-2 results in beautiful rich quality, but it eats disk space like no tomorrow. I'm finding the 1.8 GB for the standard setting to be the sweet spot. The video CD setting feels like a postage stamp, reminiscent of the quicktime 1.x days.