Loading Profile...
Bug in Record times for Cablecast 4.5.6 Build 10
This was very strange - since we ran the update, we set up a record for the meetings as usual, but the data was flipped accidentally - the time and length were reversed, so it thought the meeting was 19 hours long, and started at 5 am.
I came in Monday, and the record started at 5 am instead of 7 pm - so we stopped the recording, changed the numbers in the record to the right times, and the meeting recorded at 7 pm - the correct time - but it was still recording when I came in this morning - so it must still think the 18 hour recording input was valid, even though we changed it to 5 hours.
It might be a bug in the way the record is saved, or we just might have to scrap changing a record session in favor of making a new record - but this is the first time that it's come up, and I believe we've swapped the numbers, saved, and then changed them before the event happened without any ill effects before.
Anyone else had this happen? Thanks.
Tom Giarrosso
Executive Director
Salem Community Television
44 Geremonty Drive
Salem NH 03079
(603) 893-7069 x-118
I came in Monday, and the record started at 5 am instead of 7 pm - so we stopped the recording, changed the numbers in the record to the right times, and the meeting recorded at 7 pm - the correct time - but it was still recording when I came in this morning - so it must still think the 18 hour recording input was valid, even though we changed it to 5 hours.
It might be a bug in the way the record is saved, or we just might have to scrap changing a record session in favor of making a new record - but this is the first time that it's come up, and I believe we've swapped the numbers, saved, and then changed them before the event happened without any ill effects before.
Anyone else had this happen? Thanks.
Tom Giarrosso
Executive Director
Salem Community Television
44 Geremonty Drive
Salem NH 03079
(603) 893-7069 x-118
Follow this discussion to get notifications on your dashboard.
-
Inappropriate?I had this problem after I installed a new version. I think it was 4.5.5 or 4.5.6
Go to Location Settings > IO > Devices > Encoder
Set Device End Action to Stop Record
After that version is installed the encoder does not know what to do when it has reached the end time so it just keeps recording. -
Inappropriate?Now doesn't that sound familiar?????
John M. Goran, NCE
Cable TV Coordinator
Brunswick TV 3
28 Federal St.
Brunswick ME 04011
Office 207.725.0614
Fax 207.725.6637
tv3@brunswickme.org
www.brunswickme.org -
Inappropriate?Ok I think I found the bug here.
In the 4.2 Documentation the Device End Action only shows a "Stop" and not a "Record Stop" which is in the newer version. -
Inappropriate?You guys are right. We added the "Record stop" action recently in order to fix an issue that Mr. Goran was having. You should check that your encoders are using this new action instead of the old "Stop" action.
Please let me know if I can be of further assistance.
Brandon McKenzie
Hardware Specialist / Developer Liaison
Tightrope Media Systems
(612)866-4118
brandon@trms.com -
Inappropriate?Update - I'm still having the same problem. Came in this AM and it was still recording at 43 gigs+. I checked and the stop record tab was selected. I'll try a reboot and see if that'll set it right, but is there another place I need to change a setting on the encoder so it will recognize the time to stop the recording?
Tom -
Inappropriate?Hi Tom,
Which control module are you using to control the encoder?
-John
--
John Reilly
Developer
Tightrope Media Systems -
Inappropriate?OptibaseMoviemakerCM
-
Inappropriate?Here's something to check...
Did you install the 4.5.6 control modules on your encoder? If the encoder is running an older version than the server, the encoder might not get the new "record stop" event.
-John
--
John Reilly
Developer
Tightrope Media Systems -
Inappropriate?4.5.6 is installed on the Encoding machine. I also see 3 previous versions on it as well. I'm assuming I can delete those, but I wouldn't think they would be the issue here.
Tom -
Inappropriate?Tom, give our tech support department a call when you get a chance. We would like to discuss this with you.
Brandon McKenzie
Hardware Specialist / Developer Liaison
Tightrope Media Systems
(612)866-4118
brandon@trms.com -
Inappropriate?Just ran into the same problem yesterday, and I feel kind of dumb, because I found this topic, but assumed that it wouldn't apply to us since we have "Move file" selected instead of "Stop".
Nope. 19gb of recording later, and a missed program, and I need to figure out if the record stop will work or if I need to manually move the files from now on? -
Inappropriate?Sean Fichera figured out the toggle that fixes the issue...
In cablecast - Main Menu:Location Settings:Devices:Edit
Under the Encoder, I toggled Device End Action to 'Stop Record' - it was set to none as a default.
That took care of the problem. Good Luck!
Thanks
Tom
quote:Originally posted by Gman
Just ran into the same problem yesterday, and I feel kind of dumb, because I found this topic, but assumed that it wouldn't apply to us since we have "Move file" selected instead of "Stop".
Nope. 19gb of recording later, and a missed program, and I need to figure out if the record stop will work or if I need to manually move the files from now on?
EMPLOYEE
EMPLOYEE
