Alsa limiter for 6 channels

This is my .asoundrc, and the pair compressor + limiter works fine for stereo input:
pcm.ladcomp_compressor {
type ladspa
slave.pcm "ladcomp_limiter";
path "/usr/lib/ladspa";
plugins [{
label dysonCompress
input {
#peak limit, release time, fast ratio, ratio
controls [0 1 0.5 0.99]
pcm.ladcomp_limiter {
type ladspa
slave.pcm "plughw:Audigy2";
path "/usr/lib/ladspa";
plugins [{
label fastLookaheadLimiter
input {
#InputGain(Db) -20 -> +20 ; Limit (db) -20 -> 0 ; Release time (s) 0.01 -> 2
controls [ 20 -1 0.8 ]
Unfortunately, it does not work for 6 channels.
I.e., this one works fine:
$ ALSAPCM='pcm.ladcomp_compressor' speaker-test -c 2 -t wav -l 5
This one does not and you hear only the left and right channels.
$ ALSAPCM='pcm.ladcomp_compressor' speaker-test -c 6 -t wav -l 5
Of course the hardware is wired correctly and this one works:
$ ALSAPCM='pcm.surround51' speaker-test -c 6 -t wav -l 5
Since normally you have to select surround51 manually I thought that the problem could be in the output pcm, and I rewrote like this. But it is the same:
#[...] analogous 51 compressor omitted
pcm.plug51 {
type plug
slave.pcm "surround51"
slave.channels 6
pcm.ladcomp_limiter51 {
type ladspa
slave.pcm "plug51"
path "/usr/lib/ladspa"
plugins [{
label fastLookaheadLimiter
input {
#InputGain(Db) -20 -> +20 ; Limit (db) -20 -> 0 ; Release time (s) 0.01 -> 2
controls [ 20 -1 0.8 ]
Is there a way? Any insight?

For the moment lets forget about the compressor. This line does not work:
$ ALSAPCM='pcm.ladcomp_limiter51' speaker-test -c 6 -t wav -l 5
I tried adding "slave.channels 6" in the pcm.ladcomp_limiter51 section, just below slave.pcm. But it does not work at all. I.e., I get this error: -- ALSA lib pcm.c:6973:(snd_pcm_slave_conf) Unknown field channels --
Adding only "channels 6" seems to have no effects, I still hear only the front left and right channels. Also adding the input section has the same effect.
Perhaps the limiter does manage only two channels? It is possible to split the 6 channels in three different limiters and mix back again? Or there is another limiter that manages 6 channels?
Edit, the problem DOES seem in the limiter, the compressor by itself works:
pcm.dmix6 {
type plug
slave.pcm "surround51"
slave.channels 6
pcm.ladcomp_compressor51 {
type ladspa
slave.pcm "dmix6";
path "/usr/lib/ladspa";
plugins [{
label dysonCompress
input {
#peak limit, release time, fast ratio, ratio
controls [0 1 0.5 0.99]
Last edited by ezzetabi (2013-10-13 00:33:02)

Similar Messages

I am not able to set high and low limits for each channel seperately using LabWindows/CVI

I am using AI_StartAcquisition and AI_ReadAcquisition functions to acquire data using PCI 6025E DAQ card and iam using Lab/Wuindows/CVi5.0 software. But one of my transducer has its range in +/- 500 mV soi need to set the high low limits of each channel seperately for that i am using commond string function(cmd) but still i am not able to set the limits properly. Does anyone has any idea about this trouble

You can set the gain on a per channel basis by using the lower level functions. (As opposed to the easy i/o functions.) For example, look at the "SCANsingleBufSync.C" NI-DAQ shipping example that uses the SCAN_Op() function. It's gain parameter is an array of gains that will allow you to change the input limits for each channel separately.
-Russell

Anyone deploying Auto-RF for channel-assignment only?

Hi folks,
Curious to know if anyone is deploying LWAPP Auto-RF just for Dynamic Channel Allocation (DCA), not for Dynamic Transmit Power Control (DTPC).
We have a dense deployment of APs (ten floors of a hospital in a 4-leaf clover design with "pods" at each leaf having 2 APs each) and have enabled DCA only, with a static Tx Power constant of TPL3 (31mW). Note: the original IOS AP setup was at 20mW and we intend to lower the TX Power to TPL4. Its our understanding that AP neighbor beacons (sent at 100mW) are controlling DCA behavior regardless of this.
We are finding that DCA is going nuts in this environment (12-24 channel changes/day on several floors of APs all at once). It seems to never to stabilize. And it impacts both APs in a coverage area: each floor "pod" loses both APs (due to client de-authentications prior to the channel change) at the same time. See attached DCA reports for two floor pods APs (9 floors apart).
Is it acceptable to enable Dynamic Channel Allocation but not enable Dynamic Transmit Power Control in this way? Could this be contributing to the DCA activity?
Thanks folks,

Sabhasin,
I appreciate your response, however the issue, even with the current enhancements over execution of the DCA algorithm, is that it sends simultaneous channel-change requests to multiple APs at once, and dis-associates active clients from their APs, and any nearby APs that they might be able to connect to, with no regard to applications.
As before, it also lacks the means to set a Rogue AP RSSI DCA floor (rogues are the main trigger for DCA), and the DCA beacons sent from each AP to determine DCA changes is sent at 100mW and 1Mbps data rate, rather than the user-configured data-service rate, which the clients hear and use. As a result APs are changing channels for no good reason as far as the clients are concerned. As it stands now, good luck using more than one subnet (via AP Groups VLANs) per building w/o DCA kicking clients off and changing their IP address (and breaking apps). Unless they can treat these clients like a standard roam event, one subnet per building is the limit (and aren't we supposed to be following Cisco's wired subnet design policies of one VLAN per floor?).
There have been recent changes to the algorithm to modify the execution. The "5dB better SNR" metric now has a range of 3 values instead of one, DTPC will not power up if it has only 1 client on the fringe of coverage, and they've defaulted the neighbor RSSI to -71). This "numbs" DCA so it is not as reactive, but its equally or more important that it be sensitive to existing (including non-intelligent) associated clients and traffic.
What happpened to providing min/max TxPower limits for DTPC, and how about deferring DCA on APs with clients or any traffic (not just voice)?
Its all well and good to make things work for Intel and the CCX/CCKM compliant crew, but if you have any of the other brands of WLAN NICs (like those made by medical device manufacturers, who won't subscribe to fast roaming features until they're adopted by the IEEE) you are best keeping RRM disabled until it delivers on its promise as stated in the following 802.11TGv Objectives draft:
Service and Function Objectives
Solutions shall define mechanisms to provide the service listed below.
[Req2000] TGv shall support Dynamic Channel Selection, to allow STAs to avoid interference. Solution shall be able to change the operating channel (and/or band) for the entire BSS during live system operation and be done seamlessly with no intermittent loss of connectivity from the perspective of an associated STA. Solution shall not define algorithm for channel selection.
P.S. And how about a detailed doc showing how to tune the product in a live environment? Is it too much to ask for a legitimate case study with requisite RF environment assumptions and real before and after data with a mixed client base?

Memory limitation for session object!

what is the memory limitation for using session objects?
venu

as already mentioned there is no actual memory limitation within the specification, it only depends on the jvm's settings
how different app-server handle memory management of session objects is another part of the puzzle, but in general you should not have problems in writting any object to the session.
we had the requirement once to keep big objects in session, we decided to do a ResourceFactory that returns us the objects, and only store unique-Ids into the session.
We could lateron build on this and perform special serialization tasks of big objects in the distributed environment.
Dietmar

How to make a good UI for channel selection using DAQmx

A lot of my Labview programming was with earlier verisons of labview (pre Labview 7), and there are a ton of new features that I'm trying to digest (currently using Labview 8.2).
My question is (in general terms), how are people programming their UI for selecting channels and such when using DAQmx hardware? What I have in mind is a compacDAQ system with a number of modules. The user would be able to pick and choose which channels to monitor. Using MAX as part of that process seems counter intuative, and somewhat static (yeah I know you can change it there, but it feels more like something you would use for something that really doesn't change much). I'd like all the UI to be within the VI.
Are programmers using the create task VIs for that or something else?
Thanks in advance.
Solved!
Go to Solution.

I wholeheartedly second the motion to keep MAX out of the picture as far as users are concerned.
Setting up UI's for channel selection is a breeze in DAQmx when you create channels on the block diagram. The control you create off the Channels input will populate itself with the inputs that it knows are capable of performing the desired task...
<<< My configuration knows that my Module 5 is capable of doing Analog Input.
So... Just create a panel that waits for the user to select the proper channel. I also run a quick check of the user's selection before creating / starting the task. For example, if they choose ai30 or higher, and I know that the system isn't wired for those inputs, I'll not allow that selection. Also check for using two of the same input, etc.
Richard

Limitation for CLOB columns? - ORA-01704: string literal too long

Hello!
I'm trying to update a CLOB column with more than 35000 characteres, but I get "ORA-01704: string literal too long".
The code:
declare
l_clob clob;
begin
update test set test = empty_clob()
WHERE ID = 1
returning test into l_clob;
dbms_lob.write( l_clob, length('A...here 35000xA...A'), 1,'A...here 35000xA...A');
end;
Is there any limitation for CLOB columns?
Thanks for help.
Daniel

user605489 wrote:
32768 characteres :)Actually it's 1 character less than 32K...
*32767*
SQL> declare
2 v_vc varchar2(32768);
3 begin
4 null;
5 end;
6 /
v_vc varchar2(32768);
ERROR at line 2:
ORA-06550: line 2, column 17:
PLS-00215: String length constraints must be in range (1 .. 32767)
SQL>I guess it comes from a legacy thing where signed words (2 bytes) are/were used to represent a value. As the most significant bit of the word is used to represent the sign of the number the range goes from -32768 to 32767.

Tolerance limits for contract

Hi all,
   Is there any possibility to maintain tolerance limits for Quantity in Quantity Contract (doc type MK),,,
ex: Quantity Contract (MK) -- target quantity = 100
      it should allow me to create release orders (Purchase orders) for 105 quantity(tolerance of +5%)
regards
urendra

Hi,
By using Purchasing Value Key in Material Master you can control over and under deliveries.But its applicable to that material.
If Purchasing Info Record exists for that material then tolerance limit which is given in inforecord takes priority.
Regards,
Ramesh
Message was edited by:
        Ramesh

Tolerance limits for Price Variation

Dear All,
I have set the Following in Customizing.
In the following node : IMG-------> Materials Management ----------> Purchasing -----------> Purchase Order ---------> Set tolerance limits for price Variance.
In this, For Company code & Tolerance Key "PE" combination, it has been set " Check Limit 20%" in the Percentage field ( Upper limit ).
Now, I have a material having a Moving Average price of 100 INR in the material master Accounting view. When I create a PO for 130 INR, there is no warning/error message that is popping up? Isn't the system supposed to throw a message here, since 130 inr exceeds 120 INR, or am I missing something out here ?
Note : 120 INR = 100 + (20%)(100) = 120 INR.
Regards
Sathya

Hi Sathyanarayana Rao V N
You can benefit from M8 messages for incoming invoices with tolerances to solve your problem. You have to configure your system messages with error.
Regards.
M.Ozgur Unal

Tolerance limits for PO,MIGO..etc..?

Dear all
Can anybody explain me about the tolerance limits in SAP-MM,
1.what is tolerance limits..?
2.Why tolerance limits need in SAP-MM..?
3.How to configure in SPRO
Which are all the area has to maintain Tolerance limits according to MM point of view
Advance thanks
goods answers will be highly rewardable.
Thanks
sap-mm

Hi
tolerance limits for price variancesin Purchase order
When processing a purchase order, the system checks whether the effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible.
Variances are allowed within the framework of tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message.
In the SAP System, the types of variance are represented by the tolerance keys. For each tolerance key, you can define percentage and value-dependent upper and lower limits per company code.
Standard settings
The standard SAP System supplied contains the following tolerance keys:
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
SE Maximum cash discount deduction, Purchasing
Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
Note
You can specify whether the system message appears as a warning or error message using the menu options Environment -> Define Attributes of System Messages.
For Invoices specify the tolerance limits for each tolerance key for each company code.
When processing an invoice, the R/3 System checks each item for variances between the invoice and the purchase order or goods receipt. The different types of variances are defined in tolerance keys.
The system uses the following tolerance keys to check for variances:
AN: Amount for item without order reference
If you activate the item amount check, the system checks every line item in an invoice with no order reference against the absolute upper limit defined.
AP: Amount for item with order reference
If you activate the item amount check, the system checks specific line items in an invoice with order reference against the absolute upper limit defined. Which invoice items are checked depends on how you configure the item amount check.
BD: Form small differences automatically
The system checks the balance of the invoice against the absolute upper limit defined. If the upper limit is not exceeded, the system automatically creates a posting line called Expense/Income from Small Differences, making the balance zero and allowing the system to post the document.
BR: Percentage OPUn variance (IR before GR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units : quantity invoiced in order units and quantity ordered in order price quantity units : quantity ordered in order units. The system compares the variance with the upper and lower percentage tolerance limits.
BW: Percentage OPUn variance (GR before IR)
The system calculates the percentage variance between the following ratios: quantity invoiced in order price quantity units: quantity invoiced in order units and goods receipt quantity in order price quantity units : goods receipt quantity in order units. The system compares the variance with the upper and lower percentage limits defined.
DQ: Exceed amount: quantity variance
If a goods receipt has been defined for an order item and a goods receipt has already been posted, the system multiplies the net order price by (quantity invoiced - (total quantity delivered - total quantity invoiced)).
If no goods receipt has been defined, the system multiplies the net order price by (quantity invoiced - (quantity ordered - total quantity invoiced)).
The system compares the outcome with the absolute upper and lower limits defined.
This allows relatively high quantity variances for invoice items for small amounts, but only small quantity variances for invoice items for larger amounts.
You can also configure percentage limits for the quantity variance check. In this case, the system calculates the percentage variance from the expected quantity, irrespective of the order price, and compares the outcome with the percentage limits configured.
The system also carries out a quantity variance check for planned delivery costs.
DW: Quantity variance when GR quantity = zero
If a goods receipt is defined for an order item but none has as yet been posted, the system multiplies the net order price by (quantity invoiced + total quantity invoiced so far).
The system then compares the outcome with the absolute upper tolerance limit defined.
If you have not maintained tolerance key DW for your company code, the system blocks an invoice for which no goods receipt has been posted yet. If you want to prevent this block, then set the tolerance limits for your company code for tolerance key DW to Do not check.
KW: Variance from condition value
The system calculates the amount by which each delivery costs item varies from the product of quantity invoiced * planned delivery costs/ planned quantity. It compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
LA: Amount of blanket purchase order
The system calculates the sum of the value invoiced so far for the order item and the value of the current invoice and compares it with the value limit of the purchase order. It then compares the difference with the upper percentage and absolute tolerances defined.
LD: Blanket purchase order time limit exceeded
The system determines the number of days by which the invoice is outside the planned time interval. If the posting date of the invoice is before the validity period, the system calculates the number of days between the posting date and the start of the validity period. If the posting date of the invoice is after the validity period, the system calculates the number of days between the posting date and the end of the validity period. The system compares the number of days with the with the absolute upper limit defined.
PP: Price variance
The system determines by how much each invoice item varies from the product of quantity invoiced * order price. It then compares the variance with the upper and lower limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks if a price check has been defined for subsequent debits/credits. If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product of the quantity to be debited/credited * order price and compares this with the upper and lower tolerance limits (absolute limits and percentage limits).
PS: Price variance: estimated price
If the price in an order item is marked as an estimated price, for this item, the system calculates the difference between the invoice value and the product of quantity invoiced * order price and compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
When posting a subsequent debit/credit, the system first checks whether a price check has been defined for subsequent debits/credits, If so, the system calculates the difference between (value of subsequent debit/credit + value invoiced so far) / quantity invoiced so far * quantity to be debited/credited and the product quantity to be debited/credited * order price. It then compares the variance with the upper and lower tolerance limits defined (absolute limits and percentage limits).
ST: Date variance (value x days)
The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.
VP: Moving average price variance
When a stock posting line is created as a result of an invoice item, the system calculates the new moving average price that results from the posting. It compares the percentage variance of the new moving average price to the old price using the percentage tolerance limits defined.
Variances are allowed within predefined tolerance limits. If a variance exceeds a tolerance limit, however, the system issues a message informing the user. If an upper limit (except with BD and VP) is exceeded, the invoice is blocked for payment when you post it. You must then release the invoice in a separate step. If the tolerance limit for BD is breached, the system cannot post the invoice.
Note that if you set all limits for a tolerance key to Do not check, the system does not check that tolerance limit. Therefore any variance would be accepted. This does not make sense particularly in the case of the tolerance key Form small differences automatically.
Thanks & Regards
Kishore

Tolerance Limits for Date and quantity..??

Hi Experts,
We would like to set the GR Tolerance Limits in the Configuration level.
how to set the Tolerance Limits for Date and quantity..??
if we created PO 100qty and date 01-05-009.
if we receive the goods on 20-04-2009 and 50qty...
For GR .. Migo should be give error message..
where can i set this Tolerance Limit Configuration.... can u please explin me..
Thanks in Advance,
Anthyodaya.

Hai
for quantity tolerence limit u can do it while creating P O in item details-->delivery tab.
for date go to SPRO-->mm>purchasing->material master> define purchase value key>in that st.del.time var here it wil compare the dates and shows how much deviation is occuring for GR date
configure messages in SPRO-->mm>environment data--> define attributes of system messages
hope it may help u
regards
chandrasekhar

Maintain Tolerance limits for tolerance key B1

Hi,
When We tried to reverse a 'reversal' document using MBST but the system does not let me a throws up the following message no. M8125...
"maintaintolerance limits for tolerance key B1 (CoCode 5000)".
I checked configuration in OMc0, we have lower limit 10 % anf Higher limit 10% and BOTH 'check limit'.
Still I donot where is the problem?
Can somebody throw smoe light on this issue? Please....

Any Help?

Maintain tolerance limits for tolerance key PE (CoCode S001)

Dear all
im getting error when i creating PO
Maintain tolerance limits for tolerance key PE (CoCode S001)
Please help me
Regards
venu gopal

Hi
You need to maintain the Tolerance key
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
Maintain the tolearnce key in
SPRO-> IMG-> Materials Management-> Purchasing-> Purchase Order-> Set Tolerance Limits for Price Variance
If you want the sytem to propmt for a warning or Error message you can configure the same in
SPRO-> IMG-> Materials Management-> Purchasing-> Environment Data-> Define Attributes of System Messages

Maintain tolerance limits for tolerance key PE

Hi,
How can I correct the error below?
"Maintain tolerance limits for tolerance key PE"
Thanks

REFER BELOW SDN POST
Re: TOLERANCE KEY ERROR DURING MIGO
MAINTAIN TOLERANCE LIMITS FOR TOLERANCE KEY PE ACCOUNT ASSIGNMENT -
> Please follow this link --> SPRO -> MM-> Purchasing --> Purchase Order --> Set Tolerance limits for price variance --> Here you have to set for Tolerance keys PE and SE. Just copy them from std co. code.
Message was edited by:
SHESAGIRI.G

As of yesterday, calendar subscribers are no longer getting event alerts. We are not exceeding the limits for number of calendars

As of yesterday, calendar subscribers are no longer getting event alerts. We are not exceeding the limits for number of calendars, and have not installed new hardware or software. What else could be causing this, and how do I fix it? This is critical!

The warranty entitles you to complimentary phone support for the first 90 days of ownership.

What are Azure limitations for Websockets in Cloud Services (web and worker role)?

A WebSocket Server should be built on Azure platform with OnPrem connections and have questions regarding limitations for Websockets in Azure Cloud Services - web and worker roles.
Websockets can be configured for Web Sites and limitations are understood, but Azure Websites is not an option.
Nevertheless it is planned to run a web service (without UI - no web site) as a Cloud service which has secure websocket (WSS) connections to OnPrem machines. Websocket protocol is enabled for IIS8 on Cloud services web and worker roles. Azure Service Bus Relay
is not an option.
Questions:
1) Are Websockets supported for Azure Cloud services web and worker roles? we assume yes
2) What are potential limitations from Azure side to support concurrent Websocket connections? We are aware that CPU, memory etc are limitations, but are there additional limitations from MS Azure side?

Hi,
As I know, azure cloud service web and worker role support Websockets, users can connect to the role via the special endpoint, if we use Azure cloud service, I think we can monitor the metrics such as CPU, memory, etc... and scale our cloud service via these
metrics to keep the websockets working, refer to
http://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-scale/ for more information about how to scale a cloud service.
Regards

Alsa limiter for 6 channels

Similar Messages

Maybe you are looking for