Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
260
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 04:39 PM
This document was generated from CDN thread
Created by: Pooven Naidoo on 09-02-2010 03:58:26 PM
It seems by default that the PC Input is routed to the Loud speaker output. I cna change this either by API or the audio console, however when the codec reboots, power loss,physically unplugging the power the setup goes back to factory default. Is there a way to change the factory default setting and recall my settings instead.
onsite working on this.
Thanks
Pooven
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 10-02-2010 10:39:41 AM
Hi Pooven,
In ordere to store your settings, you can make a startup script that runs every time the codec boots.
Take a look at this post
Cheers,
Jonas
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 10-02-2010 11:15:21 AM
Hi again Pooven,
just want to add some information here. When using API's, all xConfiguration settings will be persistent. xCommands on the other hand are not persistant and are lost when rebooting.
When you use Audio Console the settings should be persistent since the application actually stores your settings in a startup script, and you should not need to create one. Make sure you close the Audio Console application window for your codec by clicking the 'x' mark on the corresponding tab in order to save the setup to the codec
Regards,
Jonas
Edit: The above statement (bold text) regarding saving of the audio setup to the Codec applies to TANDBERG Audio Console 1.0 only. In TANDBERG Audio Console 2.0 all settings will be stored when exiting the application.
Subject: RE: Audio Console c60
Replied by: Andy Wander on 20-05-2010 09:22:35 PM
I am having the same problem with a C40.
I was interested in your statement, " Make sure you close the Audio Console application window for your codec by clicking the 'x' mark on the corresponding tab in order to save the setup to the codec"
I can;t find any tabs that have "x" marks except for teh "Microphone", "Remote Inpout 3", etc. Are thois ethe ones you mean? If i close them, any inputs that were in those windows/tabs revert to "inactive", so I don;t think these are what you meant.
i am using Tandberg Audio Console 2.0.
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 21-05-2010 10:49:34 AM
Hi Andy,
Please disregard my above statements as they refer to TANDBERG Audio Console 1.0.
In the new version, all changes made are stored in a startup script in the user/scripts.d folder when you exit the Audio Console application. You can verify that your changes has been stored by viewing the contents of the startup.tsh file in this folder.
Thank you for highlighting this new and improved behavior in TANDBERG Audio Console 2.0.
Please let me know if you still have trouble saving your configuration to the TANDBERG Codec C40.
Kind Regards,
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 21-05-2010 03:42:55 PM
Jonas:
I used WinSCP to look on my C40, and there is no such file on my codec. As a matter of fact, the user/scripts.d folder is empty.
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 21-05-2010 03:56:20 PM
Hi Andy,
As long as there are no changes done, the folder will indeed be empty. Only when changes are done and after Audio Console is closed will the file appear. Remember to refresh your folder when using WinSCP for the file to appear.
Have you done any changes to the setup and closed the application, in addition to refreshing WinSCP folder view?
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 21-05-2010 04:18:18 PM
Yes, I have made changes many times, and closed the audio console both with and without saving a local xml file, over the last week.
I have also refreshed the folder in WinSCP.
There is still no file created.
I even created a blank file using WinSCP, in the user/scripts.d directory, and it is still blank.
just to confirm, this is the /user/scripts.d folder I should look in? and not some other user folder somewhere else in the directory tree?
Andy
Subject: RE: Audio Console c60
Replied by: Andy Wander on 21-05-2010 05:01:05 PM
I read in another posting that if the incorrect sw image is selected, it could affectthe saving of the startup file. I checked, and my C40 was using image2, so I set it to image1, rebooted, made some changes using the Audio Console, and it still does not save a startup file
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 25-05-2010 11:09:37 AM
Yes.
This is just partly true. It does not matter if you use image1 or image2. When you change image and do a reboot, both the codec software and filesystem will change, so an audio configuration stored in image2, will not apply to image1.
Is HTTP disabled on your system? Audio Console must have HTTP (not HTTPS only) enabled in order to be able to make changes to the system. If HTTP is disabled, enable it and reboot your system.
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 25-05-2010 09:21:08 PM
HTTP is enabled.
thanks for all of the info; i am thinking the codec is defective. Will follow up with cust svce.
Andy
Subject: RE: Audio Console c60
Replied by: Andy Wander on 07-06-2010 03:42:16 PM
I found out that the above info on where the audio settings are stored isn not wuite correct.
The file "/user/scripts.d/startup.tsh" is in fact not an actual file, but a link, which points to "user/userscripts/evaAudioStartup.tsh"
I am also confused, because teh local tandberg reps in HK(where this systemm is installed) are telling my technician that the reversion of all audio settings to factory default during a reboot is normal behavior for the C40.
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 08-06-2010 11:01:19 AM
Audio console actually just creates a pointer to a file that is stored in the usercripts folder. Nevertheless this does not make any difference when it comes to startup scripts. If the scripts.d folder contains the script itself or a pointer to a script is transparent.
Generally speaking, the codec runs the startup scripts from the /user/scripts.d/ folder, and as long as the pointer is stored in this folder and the startup script file that it points to is stored in the userscripts folder, you should be fine.
This is not correct. xConfiguration API audio settings are persistent. xCommand API's are not.
Audio settings are found in both xConfiguration API's and xCommand API's. Examples:
Hope this helps!
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 08-06-2010 02:18:05 PM
Yes, that is true, except if you are desperate for it to work, and you do like I did, and manually create an actual config file, then you have to know to store it in the userscripts folder, under the proper name.
Right, that is what is supposed to happen-but for some reason, i am on my second C40 that does not do this. The first codec did not create any files at all, and teh replacement, though it has the pointer and teh config file, does not seem to save to them, and does not initialize after a reboot to what is in the config file.
Thanks, we are getting closer to tracking the problem down, i think!
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 09-06-2010 10:36:50 AM
Hi Andy,
You can put a script in the /user/scripts.d folder and name it whatever you like (yourscript.tsh) and it will run on startup. Make sure you use unix end of lines, and that the file has proper permission (executable).
What software are you running on the C40?
I am not able to reproduce your issues.
Regards,
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 25-06-2010 08:14:37 PM
It appears that the issue was due to an admin passwod being set on the (2) C40 codecs we were testing on.
With the help of Bob Fitzgerald at Z-Care, I figured out that if the admin password was set to "" (blank), then the codec worked as it should, with the proper files being created and/or updated on teh C40.
-/user/scripts.d/startup.tsh (pointer to the actual script file)
-/user/userscripts/evaAudioStartup.tsh (the actual API script)
witth the password set to TANDBERG, or to my usual corporate password, no files were ever created or updated, and in fact, if I placed teh files theremanually, then the pointer file would be deleted on disconnecting Audio Console.
I hope this helps somebody else who may be pulling their hair out!
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 01-07-2010 11:17:57 AM
Hi Andy,
And thank you for your inputs.
I'm glad you solved your issue, however there is no reason that setting the password to blank should make any difference. I have tested this several times with passwords, and experience no problems either with creating scripts manually or by using audio console.
What software are you running?
Cheers,
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 01-07-2010 02:27:12 PM
Hi Jonas:
I agree, it should not require the password to be blank, but I have tested it on 2 units(1 in a production environment, the other sitting on my desk as we speak) and that is the only way that I can get the audio changes to take, and the files to be created.
The "production" C-40 codec is in my HK office, it is runnng TC3.1.0.215346 software. The local HK Tandberg reps tell our technicians thatthe C40 will NEVER save any changes made withthe Audio Console through a reboot, and teh only way to do it is to manually create the startup file and put it onteh codec. I tried that, and it didn't work.
The "test" C-40 codec is running TC3.0.0.211036 software. I will try upgrading it to the TC3.1.0.215346 later today and see what difference, if any, that makes.
I should mention that it would be really handy to have a document that tells how to use Audio Console. The help file is not all that great, and I have not been able to find any documentation on it's proper use. For instance, I "think" that it saves teh files to the codec when you disconnect. That's what it "seems" to do, when it is working. But I am not sure hat is what it's "supposed" to do.
Thanks for your help,
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 30-09-2010 02:17:39 PM
Hi Andy,
We have discovered a bug in Audio Console that prevents the startup script to be stored on the codec in some situations when having the password set.
I'm happy to inform that this has been fixed in the upcoming version.
Regards,
Jonas
Subject: RE: Audio Console c60
Replied by: Neil Silver on 30-07-2011 07:02:14 PM
Jonas
Slightly off topic!
Does there exist a stand-alone Audio Console as you describe in your post or is this just one part of the TC Console?
The reason I ask is that I wish to create an audio start-up xml script but not effect the video settings.
For the Video there is a standalone compositor demo and in the post above you mention Audio Console 2.0.
If it exists separately can you pleas point me to the download link.
Yours
Neil
Subject: RE: Audio Console c60
Replied by: Neil Silver on 02-08-2011 12:34:00 PM
I have a similar issue to those above.
I have created a Audio profile using the Audio Console and setup a C90 Codec using the same softawre.
I can see using winSCP that the startup.tsh has been updated with the correct xcommands
But the codec seems to religiously recall factory defaults!
Neil
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 11-08-2011 11:25:21 AM
Hi Neil,
Did you use TC Console for this? What software version are you running on your codec? The old Audio Console is now included in TC Console, and you will not modify the video settings if you only change the audio settings.
Jonas
Created by: Pooven Naidoo on 09-02-2010 03:58:26 PM
It seems by default that the PC Input is routed to the Loud speaker output. I cna change this either by API or the audio console, however when the codec reboots, power loss,physically unplugging the power the setup goes back to factory default. Is there a way to change the factory default setting and recall my settings instead.
onsite working on this.
Thanks
Pooven
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 10-02-2010 10:39:41 AM
Hi Pooven,
In ordere to store your settings, you can make a startup script that runs every time the codec boots.
Take a look at this post
Cheers,
Jonas
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 10-02-2010 11:15:21 AM
Hi again Pooven,
just want to add some information here. When using API's, all xConfiguration settings will be persistent. xCommands on the other hand are not persistant and are lost when rebooting.
When you use Audio Console the settings should be persistent since the application actually stores your settings in a startup script, and you should not need to create one. Make sure you close the Audio Console application window for your codec by clicking the 'x' mark on the corresponding tab in order to save the setup to the codec
Regards,
Jonas
Edit: The above statement (bold text) regarding saving of the audio setup to the Codec applies to TANDBERG Audio Console 1.0 only. In TANDBERG Audio Console 2.0 all settings will be stored when exiting the application.
Subject: RE: Audio Console c60
Replied by: Andy Wander on 20-05-2010 09:22:35 PM
I am having the same problem with a C40.
I was interested in your statement, " Make sure you close the Audio Console application window for your codec by clicking the 'x' mark on the corresponding tab in order to save the setup to the codec"
I can;t find any tabs that have "x" marks except for teh "Microphone", "Remote Inpout 3", etc. Are thois ethe ones you mean? If i close them, any inputs that were in those windows/tabs revert to "inactive", so I don;t think these are what you meant.
i am using Tandberg Audio Console 2.0.
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 21-05-2010 10:49:34 AM
Hi Andy,
Please disregard my above statements as they refer to TANDBERG Audio Console 1.0.
In the new version, all changes made are stored in a startup script in the user/scripts.d folder when you exit the Audio Console application. You can verify that your changes has been stored by viewing the contents of the startup.tsh file in this folder.
Thank you for highlighting this new and improved behavior in TANDBERG Audio Console 2.0.
Please let me know if you still have trouble saving your configuration to the TANDBERG Codec C40.
Kind Regards,
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 21-05-2010 03:42:55 PM
Jonas:
I used WinSCP to look on my C40, and there is no such file on my codec. As a matter of fact, the user/scripts.d folder is empty.
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 21-05-2010 03:56:20 PM
Hi Andy,
As long as there are no changes done, the folder will indeed be empty. Only when changes are done and after Audio Console is closed will the file appear. Remember to refresh your folder when using WinSCP for the file to appear.
Have you done any changes to the setup and closed the application, in addition to refreshing WinSCP folder view?
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 21-05-2010 04:18:18 PM
Yes, I have made changes many times, and closed the audio console both with and without saving a local xml file, over the last week.
I have also refreshed the folder in WinSCP.
There is still no file created.
I even created a blank file using WinSCP, in the user/scripts.d directory, and it is still blank.
just to confirm, this is the /user/scripts.d folder I should look in? and not some other user folder somewhere else in the directory tree?
Andy
Subject: RE: Audio Console c60
Replied by: Andy Wander on 21-05-2010 05:01:05 PM
I read in another posting that if the incorrect sw image is selected, it could affectthe saving of the startup file. I checked, and my C40 was using image2, so I set it to image1, rebooted, made some changes using the Audio Console, and it still does not save a startup file
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 25-05-2010 11:09:37 AM
Andy Wander:
just to confirm, this is the /user/scripts.d folder I should look in?
Yes.
Andy Wander:
I read in another posting that if the incorrect sw image is selected, it could affectthe saving of the startup file.
This is just partly true. It does not matter if you use image1 or image2. When you change image and do a reboot, both the codec software and filesystem will change, so an audio configuration stored in image2, will not apply to image1.
Is HTTP disabled on your system? Audio Console must have HTTP (not HTTPS only) enabled in order to be able to make changes to the system. If HTTP is disabled, enable it and reboot your system.
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 25-05-2010 09:21:08 PM
Is HTTP disabled on your system? Audio Console must have HTTP (not HTTPS only) enabled in order to be able to make changes to the system. If HTTP is disabled, enable it and reboot your system.
HTTP is enabled.
thanks for all of the info; i am thinking the codec is defective. Will follow up with cust svce.
Andy
Subject: RE: Audio Console c60
Replied by: Andy Wander on 07-06-2010 03:42:16 PM
I found out that the above info on where the audio settings are stored isn not wuite correct.
The file "/user/scripts.d/startup.tsh" is in fact not an actual file, but a link, which points to "user/userscripts/evaAudioStartup.tsh"
I am also confused, because teh local tandberg reps in HK(where this systemm is installed) are telling my technician that the reversion of all audio settings to factory default during a reboot is normal behavior for the C40.
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 08-06-2010 11:01:19 AM
Andy Wander:I found out that the above info on where the audio settings are stored isn not wuite correct.
The file "/user/scripts.d/startup.tsh" is in fact not an actual file, but a link, which points to "user/userscripts/evaAudioStartup.tsh"
Audio console actually just creates a pointer to a file that is stored in the usercripts folder. Nevertheless this does not make any difference when it comes to startup scripts. If the scripts.d folder contains the script itself or a pointer to a script is transparent.
Generally speaking, the codec runs the startup scripts from the /user/scripts.d/ folder, and as long as the pointer is stored in this folder and the startup script file that it points to is stored in the userscripts folder, you should be fine.
Andy Wander:
I am also confused, because teh local tandberg reps in HK(where this systemm is installed) are telling my technician that the reversion of all audio settings to factory default during a reboot is normal behavior for the C40.
This is not correct. xConfiguration API audio settings are persistent. xCommand API's are not.
Audio settings are found in both xConfiguration API's and xCommand API's. Examples:
- xConfiguration Audio Input Microphone 1 Level: 14 (persistent command)
- xCommand Audio Microphones Mute (non-persistent command)
Hope this helps!
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 08-06-2010 02:18:05 PM
Audio console actually just creates a pointer to a file that is stored in the usercripts folder. Nevertheless this does not make any difference when it comes to startup scripts. If the scripts.d folder contains the script itself or a pointer to a script is transparent.
Yes, that is true, except if you are desperate for it to work, and you do like I did, and manually create an actual config file, then you have to know to store it in the userscripts folder, under the proper name.
Generally speaking, the codec runs the startup scripts from the /user/scripts.d/ folder, and as long as the pointer is stored in this folder and the startup script file that it points to is stored in the userscripts folder, you should be fine
Right, that is what is supposed to happen-but for some reason, i am on my second C40 that does not do this. The first codec did not create any files at all, and teh replacement, though it has the pointer and teh config file, does not seem to save to them, and does not initialize after a reboot to what is in the config file.
Thanks, we are getting closer to tracking the problem down, i think!
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 09-06-2010 10:36:50 AM
Hi Andy,
You can put a script in the /user/scripts.d folder and name it whatever you like (yourscript.tsh) and it will run on startup. Make sure you use unix end of lines, and that the file has proper permission (executable).
What software are you running on the C40?
I am not able to reproduce your issues.
Regards,
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 25-06-2010 08:14:37 PM
It appears that the issue was due to an admin passwod being set on the (2) C40 codecs we were testing on.
With the help of Bob Fitzgerald at Z-Care, I figured out that if the admin password was set to "" (blank), then the codec worked as it should, with the proper files being created and/or updated on teh C40.
-/user/scripts.d/startup.tsh (pointer to the actual script file)
-/user/userscripts/evaAudioStartup.tsh (the actual API script)
witth the password set to TANDBERG, or to my usual corporate password, no files were ever created or updated, and in fact, if I placed teh files theremanually, then the pointer file would be deleted on disconnecting Audio Console.
I hope this helps somebody else who may be pulling their hair out!
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 01-07-2010 11:17:57 AM
Hi Andy,
And thank you for your inputs.
I'm glad you solved your issue, however there is no reason that setting the password to blank should make any difference. I have tested this several times with passwords, and experience no problems either with creating scripts manually or by using audio console.
What software are you running?
Cheers,
Jonas
Subject: RE: Audio Console c60
Replied by: Andy Wander on 01-07-2010 02:27:12 PM
Hi Jonas:
I agree, it should not require the password to be blank, but I have tested it on 2 units(1 in a production environment, the other sitting on my desk as we speak) and that is the only way that I can get the audio changes to take, and the files to be created.
The "production" C-40 codec is in my HK office, it is runnng TC3.1.0.215346 software. The local HK Tandberg reps tell our technicians thatthe C40 will NEVER save any changes made withthe Audio Console through a reboot, and teh only way to do it is to manually create the startup file and put it onteh codec. I tried that, and it didn't work.
The "test" C-40 codec is running TC3.0.0.211036 software. I will try upgrading it to the TC3.1.0.215346 later today and see what difference, if any, that makes.
I should mention that it would be really handy to have a document that tells how to use Audio Console. The help file is not all that great, and I have not been able to find any documentation on it's proper use. For instance, I "think" that it saves teh files to the codec when you disconnect. That's what it "seems" to do, when it is working. But I am not sure hat is what it's "supposed" to do.
Thanks for your help,
Andy
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 30-09-2010 02:17:39 PM
Hi Andy,
We have discovered a bug in Audio Console that prevents the startup script to be stored on the codec in some situations when having the password set.
I'm happy to inform that this has been fixed in the upcoming version.
Regards,
Jonas
Subject: RE: Audio Console c60
Replied by: Neil Silver on 30-07-2011 07:02:14 PM
Jonas
Slightly off topic!
Does there exist a stand-alone Audio Console as you describe in your post or is this just one part of the TC Console?
The reason I ask is that I wish to create an audio start-up xml script but not effect the video settings.
For the Video there is a standalone compositor demo and in the post above you mention Audio Console 2.0.
If it exists separately can you pleas point me to the download link.
Yours
Neil
Subject: RE: Audio Console c60
Replied by: Neil Silver on 02-08-2011 12:34:00 PM
I have a similar issue to those above.
I have created a Audio profile using the Audio Console and setup a C90 Codec using the same softawre.
I can see using winSCP that the startup.tsh has been updated with the correct xcommands
But the codec seems to religiously recall factory defaults!
Neil
Subject: RE: Audio Console c60
Replied by: Jonas Tysso on 11-08-2011 11:25:21 AM
Hi Neil,
Did you use TC Console for this? What software version are you running on your codec? The old Audio Console is now included in TC Console, and you will not modify the video settings if you only change the audio settings.
Jonas
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents