Difference between revisions of "User talk:Pvr4me"

From MythTV Official Wiki
Jump to: navigation, search
(Created page with "Sorry PVR4Me, I don't have another way to contact you. I believe you may be the user of the Torc for iOS application who posted a one star review just now. My e-mail address i...")
 
(Firewire capture)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Sorry PVR4Me, I don't have another way to contact you. I believe you may be the user of the Torc for iOS application who posted a one star review just now. My e-mail address is on the torc support page, and you are welcome to get in touch with me that way. You can also post to the google group, you simply have to join the group first. Here's the message I just sent to you on the group:
+
On [[MythTV on Mac OS X]] you say "firewire support possible" for the macport version of MythTV.
  
I noted that I got a 1 star review from someone in the USA who claims
+
Looking at the code for the portfile it sets the configure option --disable-firewire and the firewire option doesn't appear in the settings.
it's not possible to post messages to the group. You can post to the  
 
group, you simply need to become a member. Please join the group and
 
I can assist you.  
 
  
Please also read the support page carefully. The reason your stream
+
How does one enable firewire support on the macports version of MythTV?
is likely failing is because the backend is telling the app that it is
 
working on the stream, but it isn't. This is most commonly caused
 
because you are not building MythTV with the proper compile flags.
 
All of the required flags are covered in the support page:
 
  
http://www.fecitfacta.com/blog1/torc/
+
== Firewire capture ==
  
You'll find that mythtranscode has likely errored out in your backend
+
I have a one-off version of the port that builds 0.25 with firewire enabled. The other necessary ingredient is Apple's Firewire SDK.  As I read the license, it may '''not''' be distributed in any way and hence can't go on MacPorts.
log. However, as far as the API is telling the app, that transcode is
 
still going on. You need the --enable-libmp3lame and --enable-libx264
 
compile flags.
 
  
Please consider joining the group if you need more help. If you find
+
Only a single user is running Firewire variant at present. Are you interested?
that the above is true, please consider amending your review as the
 
app has no way of knowing why the stream doesn't continue to
 
transcode, it just knows that as far as the backend is telling it,
 
that transcode is still going (but there aren't any segments
 
available).
 
  
I am happy to assist you if you e-mail or Google Group me. Please just get in touch if the above does not help you.
+
* I am interested. I have the Firewire SDK installed already. What program do you use to change channels with firewire? --[[User:Doconnor|Doconnor]] 17:51, 16 August 2013 (UTC)
 +
 
 +
** Contact me at ctreleaven at cogeco dot ca .  I don't run a Firewire box, myself.  There are several scripts on the wiki that might be relevant:  http://www.mythtv.org/wiki/Category:Firewire_Priming_Scripts
 +
 
 +
Also, I see you wrote the HDPVR Capture on Mac page.  I take it you are using it to record?  I was wondering if `osascript` would make it possible for Myth to fire off the recording without having to involve Calendar.  It is too bad the author of HDPVRCapture doesn't make at least a basic version freely available.  I contacted him last year to ask about using his old command line version.  He wasn't interested.  WCT
 +
 
 +
* I fried my HDPVR by plugging in the wrong power supply, so I had to get a new one. The HDPVRCapture license is tied to the serial number of the HDPVR, so I would have to buy it again. Because of its instability and problems changing channels I've set up a Virtualbox mythbuntu install for recording instead. --[[User:Doconnor|Doconnor]] 17:51, 16 August 2013 (UTC)
 +
 
 +
** Sorry about the HDPVR.  Are you saying it was unstable or that the Firewire box?
 +
 
 +
*** HDPVRCapture was unstable. It crashed every day or so when idle and it often had long pauses between sending the digits of the channel number. I'm not sure how much is HDPVRCapture's fault and how much is Mac OSX's fault. --[[User:Doconnor|Doconnor]] 18:43, 16 August 2013 (UTC)

Latest revision as of 18:43, 16 August 2013

On MythTV on Mac OS X you say "firewire support possible" for the macport version of MythTV.

Looking at the code for the portfile it sets the configure option --disable-firewire and the firewire option doesn't appear in the settings.

How does one enable firewire support on the macports version of MythTV?

Firewire capture

I have a one-off version of the port that builds 0.25 with firewire enabled. The other necessary ingredient is Apple's Firewire SDK. As I read the license, it may not be distributed in any way and hence can't go on MacPorts.

Only a single user is running Firewire variant at present. Are you interested?

  • I am interested. I have the Firewire SDK installed already. What program do you use to change channels with firewire? --Doconnor 17:51, 16 August 2013 (UTC)

Also, I see you wrote the HDPVR Capture on Mac page. I take it you are using it to record? I was wondering if `osascript` would make it possible for Myth to fire off the recording without having to involve Calendar. It is too bad the author of HDPVRCapture doesn't make at least a basic version freely available. I contacted him last year to ask about using his old command line version. He wasn't interested. WCT

  • I fried my HDPVR by plugging in the wrong power supply, so I had to get a new one. The HDPVRCapture license is tied to the serial number of the HDPVR, so I would have to buy it again. Because of its instability and problems changing channels I've set up a Virtualbox mythbuntu install for recording instead. --Doconnor 17:51, 16 August 2013 (UTC)
    • Sorry about the HDPVR. Are you saying it was unstable or that the Firewire box?
      • HDPVRCapture was unstable. It crashed every day or so when idle and it often had long pauses between sending the digits of the channel number. I'm not sure how much is HDPVRCapture's fault and how much is Mac OSX's fault. --Doconnor 18:43, 16 August 2013 (UTC)