Originally Posted by scoombs
My email chain follows, and it should be noted that as of this writing, I have received no reply to my last response:
I figured I would update on responses from VividLogic to date, and it seems like they may finally look into it. I got this email from them following my last few exchanges:
You have a file named "ConfigLogSvr.exe" (100 KB) waiting for download.
Hi Scott, Please send us file you recorded using the URL: http://www.yousendit.com
. Also, please find attached a diagnostic tool "configlogsvr" which logs all the actions of FireBus DTVR. The instructions to use this tool are given below: 1) Change the Windows service settings (so that the log files do not get over written on reboot). Go to control panel -> Administrative Tools->Services From the list of services, choose FireBus DTVR. Double click on FireBus DTVR. In the settings for this service, change Startup Type to 'Manual' from the current setting of 'Auto'. Select 'Apply' followed by 'OK'. FireBus Service cleans up the log file everytime it starts up. This is why we are setting the service to manual mode. Please make sure that service is in manual mode and start it manually only for the case where we are capturing the logs. When the PC reboots after a recording, please do not start the service. First copy or rename the log file before starting the service. 2) Configure the logging application Unzip the attached zip file using WinZip. Copy conFigLogSvr.exe application to the FireBusDTVR/Bin folder of your installation. (e.g., C:/Program Files/FireBusDTVR/Bin). Double click to start the application. On the Application's UI, make the following selections: Option: 1) ALL LOG MESSAGES TraceLevel: Maximum Exclusives: Check all the check boxes General Settings: Check File Logging After you make the selections, click Apply and then choose OK. After the logserver is configured as above, start a recording to the PC DTVR as you have tried before. Logs will be created in the FireBusDTVR/log folder. Please send us the vl_FirebusLog_1.log file. You can set the FireBus DTVR service back to 'Auto' mode after sending the log file. Please do not share the ConfigLogSvr application. This application has been provided only for debugging purposes. Please send us the logs and the content recorded during the recording session which fails for you. We will analyse the logs and see what the problem is. Thanks & regards, VividLogic support
You can click on the following link to retrieve your file. The link will expire in 7 days
and will be available for a limited number of downloads.
ConfigLogSvr.exe (100 KB)
This email was automatically generated, please do not reply to it.
If you have any questions, please email email@example.com
The YouSendIt Team
If your email client does not accept HTML, please use this link to download your file:http://s56.yousendit.com/d.aspx?id=3...F3SH8567WNXDGO
Sent: Thursday, March 09, 2006 7:53 PM
To: Support Support
Subject: RE: Firebus Issues
Thank you again for your reply, but I assure you I DO know how to read, and am aware of the in-the-clear requirement from your documentation. I am also aware of the specification that DTVR supports ATSC conforming streams of "about 19.39 mbps", and I also successfully read the response below that says DTVR supports "up to 24 Mbps".
1.) I confirmed all of my content channel sources are flagged as COPY FREE, so digital content protection is not the issue in this case.
2.) You have stated the high bound for bit-rate as 24 mbps, and I conclude from the other documentation that the nominal rate is 19.39 mbps. Can you inform me what the lower bound for bit-rate is please?
If at all possible, I would prefer suggested troubleshooting recommendations, rather than random snippets from the product specification sheet.
From: Support Support [mailto:firstname.lastname@example.org]
Sent: Thursday, March 09, 2006 3:47 AM
Subject: Re: Firebus Issues
PC DTVR records ONLY IN THE CLEAR contents. This means that it will not record any scrambled or copy protected HD data. You are able to record and play back to the integrated AVDisc because this AVDisc has digital content protection support.
Thanks and regards