Data arriving too fast for processing

[paok1926]

hello all,

i want to stream an AAC stream to sc_trans and transcode it to differetn bitrates.
i started streaming HE-AAC High @ 256kbps (using Edcast standalone), and my config is this:

outprotocol_1=3
serverip_1=localhost
serverport_1=35000
uvoxstreamid_1=1
uvoxuserid_1=admin
uvoxauth_1=password
uvoxradiometadata_1=0
uvoxnewmetadata_1=1
encoder_1=mp3
bitrate_1=128000
samplerate_1=44100
channels_1=2

i starts streaming, and after a few moments, stops giving me this message:
msg:[DJPROTOCOLSHOUTCAST] Data arriving too fast for processing - some has been lost in the last second.

this is the output of command cat /proc/cpuinfo

# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 42
model name : Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
stepping : 7
cpu MHz : 3410.740
cache size : 6144 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm constant_tsc up pni monitor ssse3 lahf_lm
bogomips : 6821.48
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

any help ?

[DrO]

it means that more stream data is coming from the source connection than is being sent to the DNAS and it leads to the buffer filling up and information having to be dropped. other than making sure the DNAS is trying to keep up with things then there's little you can do about it.

-daz

[paok1926]

in other words, the server does not have enough cpu to process the incoming data in time ?

[DrO]

maybe though it really depends on what else you're doing on the machine at the same time as that could be limiting how sc_trans runs and in-turn affects it's ability to process and pass on the data (or rather not) to the DNAS.

then again it could be a bug in sc_trans or the dnas or just something specific to your machine or a combination of sc_trans and dnas bugs / design weaknesses working in combination (as what is publcally available for both of them probably aren't the best reflection of what they can be like). alas as i've not been able to replicate the issue in a long time, i don't know what i can really do to further look into the issue.

-daz