Sudden latency! No change of buffer size or hardware. What give?

I'm trying to record a song and there's latency. I was recording two nights ago and everything was fine. The only thing that's happened between now and then is I unplugged my gear and replugged it today. The buffer size is set to 256 (and always has been as far as I know). Is it possible that the latency is due to a faulty hardware connection? I don't understand how it could be software related. Also, if the solution is to change my buffer size (which I tried and it does reduce the latency at 32) does that affect the sound quality? I find this all quite mysterious... and infuriating.

Reducing latency does not affect soundquality, but computer performance.
Buffer 256 induces pretty much latency. On my system, RME Babyface, 14.8 ms roundtrip.
And I find it quite useless to record with. So I go for buffer 64/32, or simply mute the channel I'm recording to.
And monitoring through my interface........But you didn't explain if your problem is MIdi or audio related.
With first version of LPX (10.0) I experienced som strange behaviour, too. It seems to have gone now.

Similar Messages

Where can I change the buffer size for LKM File to Oracle (EXTRENAL TABLE)?

Hi all,
I'd a problem on the buffer size the "LKM File to Oracle (EXTRENAL TABLE)" as follow:
2801 : 72000 : java.sql.SQLException: ORA-12801: error signaled in parallel query server P000
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-29400: data cartridge error
KUP-04020: found record longer than buffer size supported, 524288, in D:\OraHome_1\oracledi\demo\file\PARTIAL_SHPT_FIXED_NHF.dat
Do you know where can I change the buffer size?
Remarks: The size of the file is ~2Mb.
Tao

Hi,
The behavior is explained in Bug 4304609 .
You will encounter ORA-29400 & KUP-04020 errors if the RECORDSIZE clause in the access parameters for the ORACLE_LOADER access driver is larger than 10MB and you are loading records larger than 10MB. Which means their is a another limitation on read size of a record which is termed as granule size. If the default granule size is less then RECORDSIZE it limits the size of the read buffer to granule size.
Use the pxxtgranule_size parameter to change the size of the granule to a number larger than the size specified for the read buffer.You can use below query to determine the current size of the granule.
SELECT KSPFTCTXPN PARAMETER_NUMBER,
KSPPINM PARAMETER_NAME,
KSPPITY PARAMETER_TYPE,
KSPFTCTXVL PARAMETER_VALUE,
KSPFTCTXDF IS_DEFAULT,
KSPPIFLG MODIFICATION_FLAG,
KSPFTCTXVF VALUE_FLAG
FROM X$KSPPI X, X$KSPPCV2 Y
WHERE (X.INDX+1) = KSPFTCTXPN AND
KSPPINM LIKE '%_px_xtgranule_size%';
There is no 'ideal' or recommended value for pxxtgranule_size parameter, it is safe to increase it to work around this particular problem. You can set this parameter using ALTER SESSION/SYSTEM command.
SQL> alter system set "_px_xtgranule_size"=10000;
Thanks,
Sutirtha

Effect of Changing Stream Buffer Size

What is the downside (if any) of changing the Stream Buffer Size from Medium to Large when playing music files?

Streaming Buffer Size
Change how much audio or video is downloaded before it starts to play. Choosing a larger buffer can help video play more smoothly. If you have a fast Internet connection, a smaller buffer can help the movie start playing more quickly.

Changing input buffer size slows down simulated device?!?

hi,
my basic problem is having a 200279 buffer overflow.
for a quick fix I increased the buffer size using DAQmxSetBufInputBufSize, but now the signal coming from the simulated device is much slower.
how can it be?
thanx!

Hi,
Buffer overflow errors occur when data is written to the buffer faster than it is being read off of it. Buffer underflow errors occur when data is being read off the buffer faster than new data is being added. In order to avoid either of these, a general rule of thumb for NI devices is to acquire around 1/10th of a second of data. For example, for a sample rate of 100 Hz, set samples to read at 10 samples.
Is it possible for you to decrease the sample rate?

Suddenly Firefox has changed the text size of my mail page...I am unable to read the text or mail, it is so small. what has happened and how can I rectify this?

When opening my Mail window, I found the text size was virtually unreadable. It has decreased. and I have no idea how to rectify this. This problem only started today-

See this: <br />
https://support.mozilla.com/en-US/kb/Page+Zoom

Linux Serial NI-VISA - Can the buffer size be changed from 4096?

I am communicating with a serial device on Linux, using LV 7.0 and NI-VISA. About a year and a half ago I had asked customer support if it was possible to change the buffer size for serial communication. At that time I was using NI-VISA 3.0. In my program the VISA function for setting the buffer size would send back an error of 1073676424, and the buffer would always remain at 4096, no matter what value was input into the buffer size control. The answer to this problem was that the error code was just a warning, letting you know that you could not change the buffer size on a Linux machine, and 4096 bytes was the pre-set buffer size (unchangeable). According to the person who was helping me: "The reason that it doesn't work on those platforms (Linux, Solaris, Mac OSX) is that is it simply unavailable in the POSIX serial API that VISA uses on these operating systems."
Now I have upgraded to NI-VISA 3.4 and I am asking the same question. I notice that an error code is no longer sent when I input different values for the buffer size. However, in my program, the bytes returned from the device max out at 4096, no matter what value I input into the buffer size control. So, has VISA changed, and it is now possible to change the buffer size, but I am setting it up wrong? Or, have the error codes changed, but it is still not possible to change the buffer size on a Linux machine with NI-VISA?
Thanks,
Sam

The buffer size still can't be set, but it seems that we are no longer returning the warning. We'll see if we can get the warning back for the next version of VISA.
Thanks,
Josh

Changing Buffer Size - Logic Tweaks Out

I find that I'm unable to change the buffer size (for instance, after I record and want to play back without any glitches) without having to quit Logic and reload the file. I usually get a message that "some plug-ins have been disabled."
Everything is usually fine after I quit the file and reload. But I'm wondering if anyone else has this issue and if it can be avoided. It's mostly just a time-waster.
Thanks.

Nevermind. Thanks.

Changing Buffer Size

Every time I change the buffer size in audio preferences, Logic tells me that my memory is getting too low and then diagonal black lines appear across all my plug-ins. When I quit and reload, it usually works fine. Sometimes I have to quit Logic entirely and reload the project.
Not sure what's going on.

freeschaboy1 wrote:
Logic 9.1.1 with 4 GB of RAM.
I'm mostly using Miroslav Philharmonik - surprise, surprise!
I have about 10 instruments loaded, with an average of 5 channels per instrument. I suppose that's a lot.
Thanks.
There's your answer then You are likely to be running out of memory (as Logic warned you).
Some solutions that may help:
Get more memory (may not be possible for your particular Mac)
Use less/fewer memory intensive plugins.
Possibly, Miroslav P has a disk streaming option, that might at least allow you to run with less samples actually in memory.
Bounce some of the tracks to audio and remove the Instrument plugins to free up some memory.
and on...
CCT

VISA Set I/O Buffer Size fails with all but one value on Linux RT

I was unable to initialize a serial port on a cRIO-9030 using a code that works fine on VxWorks and Windows, when I tracked it down to this somewhat strange behaviour;
If you call VISA Set I/O Buffer Size on Linux RT (at least on the 9030 device) you will get error code 1073676424 for all size values other than 0.
That is a bit strange (what will the buffer size be then I might add...), but something even uglier is that if you leave the function's buffer size unwire, you will also get the error (because the function's default is 4096).
MTO

Under the hood VISA is using the POSIX serial interface for Mac OS X (same as for Linux and Solaris). This interface does not support changing the buffer size. Hence, the buffer size is fixed to the internal OS buffer size. The only thing that changing the buffer size will do (for the out buffer) is to have VISA not flush the data after every write. This is a limitation in the serial API for Mac OS X. Therefore, VISA reports a warning.

Most recent update changed all font sizes. What is best method to change back to to preexisting Fonts

The most recent update changed all font sizes (smaller). What is the best method to enlarge?

yeah, that's what I ended up doing late last night because the white font against pale gray background was driving me nuts. I hadnt changed anything. been using the same theme for about 4 months but then all of a sudden, like I said, the font color mysteriously changed.
anyway, thanks for your help.

Warning 1073676424 from VISA Set I/O Buffer Size.vi on a serial port

I am porting an application from LabVIEW 6.1 on Windows to LabVIEW 7 on OS X (Mac). It was very painless except some GUI modifications.
The application involves 30 KB data from a instrument through a RS232 serial port. I found the application misses data whenever the computer is busy. The problem came down to the unchanged buffer size.
Attempt to change the buffer size of a serial port with "VISA Set I/O Buffer Size.vi" fails with a warning of 1073676424 (The specified I/O buffer is not supported). Even the example vi from NI web site "Advanced _Serial_Write_and_Read.vi" has the same warning.
I wonder what I am missing.

Under the hood VISA is using the POSIX serial interface for Mac OS X (same as for Linux and Solaris). This interface does not support changing the buffer size. Hence, the buffer size is fixed to the internal OS buffer size. The only thing that changing the buffer size will do (for the out buffer) is to have VISA not flush the data after every write. This is a limitation in the serial API for Mac OS X. Therefore, VISA reports a warning.

I/O Buffer Size Requires Constant Changes

Every 20 seconds or so, I have change the I/O Buffer Size to stop a crackling noise and latency. When I change it, everything sounds clear for 20 seconds, and then goes back to sounding terrible and out of sync. Any help?

it sounds like you have an issue that isn't actually directly related to the buffer size. When you chnge the buffer size, you are reinitializing core audio. Something else is happening that causes your sync issues after about 20 seconds, then reintializing clears it.
What sort of setup do you have? Do you have an aggregate device? A clock? What sorts of instruments? etc.

I'm having sever latency issues on Logic 9 through the built-in input (despite having no plugins active and 32 bit buffer size selected)

I'm literally running a guitar straight into my computer (no plugins, no interface, just the "built-in input" on my macbook) and there's a LOT of latency. I'm very experienced with Logic and pro-audio (I have logic on my other computer and it works fine) but for some reason there's a ton of delay on my signal. NO idea where to start with this one. I've examined every option within Logic and nothing seems to be helping. I've changed every parameter, including buffer size, disabling and reenabling core audio, and low-latency mode, but nothing has worked.
Any advice would be appreciated, thanks.
Also, I'm using a late 2011 15" Macbook (Quad core, 4 GB ram)

Never heard of this before... what are you using for output in Logic's Audio Prefs?
Are you on 10.7.5 as you signature says? There is a supplemental update for early builds of 10.7.5 that were released.
Take a look at the Audio portion the "Audio-MIDI Setup" in Utilities.
Bit-depth, sample frequency? Try it at 16-bit 44.1kHz. Is Logic set to the same?
What kind of cable are you using to get the guitar into Logic, the Mac audio input jack is multifunction, could you be partially enabling the digital I/O.
just tossing some ideas..

How to change the field size cache/buffer in a query

I query a field from sql developer, the field is cases_history, it resides in a data mart in the global network of our company.
this field is big in size, it stores logs in a sequential way, so field size increases a lot.
when i query it and try a "single record view" the field is cut off and can´t see all of its content..
WHAT I THOUGHT AND IT DOESN´T APPLY
1. maybe in database connections in the system tab, I go to the oracle data mart that i am interested in and change buffer and cache
but it doesn´t work, sql developer keeps showing part of the field
2. maybe it was then the buffer size in sql developer, so I change it, but no luck
WHAT IS THE PROBLEM HERE?
MANY THANKS IN ADVANCE

many thanks in advance for your help,
1.the data type in the remote oracle data mart is VARCHAR2(4000)
2.editing with the pencil cuts off at somepoint (which is the same line and last word)
3.this is the query I write
||select case_history from wfm_case where case_id='xxxx'||
this is to test if I can get a long case_history, which we know it is because it is fully accessible through a web solution to revise cases.
PLS note. I have a tns connection which is of the following type :
(in data sources (odbc) -- system dsn -- oracle odbc driver configuration ...oracle .. buffer size =9000 , cache buffer size =4000 and FORCE SQL_WCHAR SUPPORT is enabled
many thanks,
Jordi.

Buffer Size and Latency

I knew the 2 might be connected but I recently read some information which confused me. I thought a larger buffer size was good, but I've just read that increasing the buffer size lengthens latency. Can anyone enlighten me on the relationship between these; just simple answers, please.

Audio is sent through the system in chunks. Chunks of the buffer size. Buffer size is measured in samples so a buffer setting of 256 samples rewquests and provides audio in 256 sample packets. As a real time application, this cannot be predicted so the buffer reads from the present/past as opposed to looking ahead of time. The chunk will be handed off to CoreAudio that much ( time ) later, in comparison. So...
Larger buffer increases track/plugin count since you allow the computer more time to manage it's tasks.
Decreasing allows for less total system throuhput ( = less latency ).
Many people have found a good balance for this ( if they need to dynamically alter system resources ) to be:
Low buffer size while recording, for minimal latency
Then increase buffer for mixdown, allowing more pluggies and tracks.
Your latency setting is also dependent on your audio hardware and system busses. So, a good interface and driver on a dedicated FireWire bus can allow you to decrease your buffer setting.
J

Sudden latency! No change of buffer size or hardware. What give?

Similar Messages

Maybe you are looking for