- Sagetv placeshifter port movie#
- Sagetv placeshifter port install#
- Sagetv placeshifter port manual#
- Sagetv placeshifter port software#
- Sagetv placeshifter port code#
S_Add_a_New_Favorite_on_the_Left_or_Edit_a_Current_Favorite_from_below_Press_Right_on_a_Favorite_to_change_its_priority_= Add a New Favorite on the Left or Edit a Current Favorite from below. Favorite priority cannot be changed in this sorting mode. S_Add_a_New_Favorite_on_the_Left_or_Edit_a_Current_Favorite_from_below_Favorite_priority_cannot_be_changed_in_this_sorting_mode_= Add a New Favorite on the Left or Edit a Current Favorite from below.
Sagetv placeshifter port movie#
S_Add_ShowID_as_part_of_Movie_Favorites= Add ShowID as part of Movie Favorites
Sagetv placeshifter port manual#
S_Add_Manual_Recording_status_for_this_show= Add Manual Recording status for this show S_Add_Channel_to_Lineup= Add Channel to Lineup S_Action_to_take_when_SageTV_Window_is_closed= Action to take when SageTV Window is closed S_Action_After_Selecting_Airing= Action After Selecting Airing S_Accept_the_new_diskspace_usage_rule_= Accept the new diskspace usage rule. S_Accept_the_current_settings= Accept the current settings S_ALWAYS_OVERRIDE_and_record_this_favorite_instead_of= ALWAYS OVERRIDE and record this favorite instead of S_ALWAYS_IGNORE_conflicts_between_these_favorites= ALWAYS IGNORE conflicts between these favorites Please go to "Source Setup" or "Configure TV Recording" to set up a video source. S_A_video_source_needs_to_be_configured_before_you_can_test_playback_Please_go_to_Source_Setup_or_Configure_TV_Recording_to_set_up_a_video_source_= A video source needs to be configured before you can test playback. S_this_will_cause_other_conflicts_= (this will cause other conflicts) S_set_to_0_to_use_system_default_bitrate_= (set to 0 to use system default bitrate) S_set_to_0_to_use_default_bitrate_for_encoder_= (set to 0 to use default bitrate for encoder)
Sagetv placeshifter port code#
The only advantage that you get with the stable release (implicitly) is that the code is more tried and tested.S_Block_size_is_sometimes_referred_to_as_Cluster_Size_or_Allocation_Unit_Size_= "Block size" is sometimes referred to as "Cluster Size" or "Allocation Unit Size" The last stable is missing several new features present in the current beta that you might one day decide you would like to mess around with. If the beta is working for you, I would leave it alone. When I noticed how old the firmware you were running was, it was definitely a red flag. Good to see the firmware got you working. I really do enjoy working on these projects.
Sagetv placeshifter port install#
Is there any reason why I should go back and install the stable version of OpenDCT?
Sagetv placeshifter port software#
Thank you for developing the OpenDCT software and all the work you do for SageTV. I learned from JustFred after posting about no video that Comcast changes to H.264 hosed the old Prime firmware so I bit the bullet and updated the firmware and installed the OpenDCT beta software and guess what! I'm running the old firmware because it was working fine until last week using SageDCT. I'll also try the latest version in the next few days. I thought the only way to recover from that was to reboot Sage and OpenDCT. After seeing the errors Sage reports the network encoders as "functioning=false". I have not tried restarting OpenDCT while Sage is running. OpenDCT has saved me HOURS of time in remapping channels I am just trying to understand the issue to see if I can find a work-around. Please don't take my comments as criticism, I know how much time and effort goes into these things. I can't recall if I asked this of you already, but have you already tried just restarting the OpenDCT service when you see this issue instead of the entire computer?Įdit: I am working on some pieces of code specific to what you're experiencing and focused on where you're seeing problems. When OpenDCT says it can't communicate with the device for the 2nd time, it has already taken the entire connection down, ran detection to make sure the IP address has not changed and attempted to reestablish a connection. A fair amount of effort was put into handling all of the usual problems you might run into on a less than perfect network. I've seen the behavior you're experiencing on other computers from other users, but I have never seen it happen on my own network without the device being unplugged. If anything you could say that the network support in Java can be fussy, but that's probably not accurate. I suspect we would be seeing postings similar to yours a lot more often if that was the case. I don't know if finicky is the right word. I don't really have anything better to go on.
0 kommentar(er)
