Forum Replies Created
-
Posts
-
code :
< this text will scroll << this text will scroll faster /2s:2seconds /8s:8seconds /2s:call now /1s:readthis <<< this text scrolls even faster << this text will scroll into and out of the PS /2s:KIIS-FMOr as Leif documented it…
Have fun 🙂
Sorry I didn't reply immediately.
To stream to different mount points on a Shoutcast 2 server, the stream index does go into the "Server IP":
server:port,streamindexSo using your example server "myserver.com:8000", the "Server IP" settings for two encoders would be:
myserver.com:8000,1
myserver.com:8000,2Getting BS.412 consistent is a combination of a few things.
The first is getting a consistency to the power, and often that means needing to have a consistent bass sound at the right loudness. If the bass is too loud, that'll tend to make the power vary mostly depending on the bandwidth and deepness of the bass even if it sounds consistent overall, vs songs with not much bass/deepness. If you want a decently louder than "flat" bass sound on air, you'll just have to settle for being more quiet elsewhere.
The second is to not lean heavily on the BS.412 limiting. If you do, you'll find out why judging loudness from the dBr measurement is not accurate at all, and why I remind people about it fairly often when I see people equating dBr and loudness. Getting a more consistent power measurement, while not compromising your loudness consistency, will allow you to be close to the peak dBr more of the time, and be louder on air, and not run into the dBr limiting effecting your loudness consistency.
What market/s is your station in?
It worked in BBP because you were using a VST wrapper as Winamp plugin, and that wrapper was providing a normal Winamp plugin interface/window to BBP.
BreakawayOne doesn't support VST plugins that don't have their own interface/window, yet.
It does, you just need to have a supported encoder in the path. Someone made an installer that has some codecs that BreakawayOne can use that someone linked here: https://mega.nz/#!gdAEAQTQ!XW4hi5v2PkJOUYzLghs6cBfJcg-VmBBeqEZlAOlzCMA
The VSTs are the first thing the audio touches after coming from a soundcard input. That is so that nothing will interfere with anything that needs to have unaltered audio, such as a declipper. A nice side effect is it was easy to put in the list of inputs in other cores, so that you don't have to process the same input with the same VST plugins more than once.
Please contact:
broadcast@claessonedwards.com
after you know (and test) the features you need to buy.If you need the price list, visit the official site
http://www.breakawayone.com/
and click on "Buy".There shouldn't be any echo happening. It sounds like it's not configured correctly. Let me know if you'd like me to look at it with TeamViewer, Ammyy Admin, etc, via private message.
"No block size selected", so… go back into Config mode, and click on "Auto-configure Block Size" for each of the inputs & outputs you're using.
You should also use "Kernel Streaming" interface whenever possible. You should usually get lower frame jitter from that, vs Wave.
The other thing I see that's wrong is that you're assigning 3 different things to the same soundcard output. If you want to be able to have a physical soundcard output that can switch between different patch points, use the "Monitor Output" for that.
What I was asking is what inputs & outputs are you using in BreakawayOne, so I can know if you are not routing the signal correctly in BreakawayOne.
In BreakawayOne config, what Input/s and Output/s are you using? In BreakawayOne App/Service, what core/s are you trying to use?
Let's take a look at the latencies on your system then.
Read the very basic info here, to understand a little about what this does, and download/install it.
http://www.resplendence.com/latencymonClose BreakawayOne App or stop the BreakawayOne service.
Then run LatencyMon, and press the green "play" button to start monitoring latency. When it seems like the 2nd-4th meters aren't increasing anymore, wait another minute, then press the red "stop" button to stop monitoring.
If LatencyMon says:
then repeat the process again with BaOne App or service running. If it *still* says that, then simply let me know.If not, the please continue.
Then please copy the first report like this:
and paste it in a reply here between code tags. (which you can insert by clicking this button in the font/formatting area of this forum while you're replying:
)For example 🙂
code :_________________________________________________________________________________________________________<br />CONCLUSION<br />_________________________________________________________________________________________________________<br />Your system appears to be suitable for handling real-time audio and other tasks without dropouts. <br />LatencyMon has been analyzing your system for 0:00:31 (h:mm:ss) on all processors.<br /><br /><br />_________________________________________________________________________________________________________<br />SYSTEM INFORMATION<br />_________________________________________________________________________________________________________<br />Computer name: SSDOMINATOR<br />OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)<br />Hardware: ASRock, P55 Extreme<br />CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz<br />Logical processors: 8<br />Processor groups: 1<br />RAM: 16375 MB total<br /><br /><br />_________________________________________________________________________________________________________<br />CPU SPEED<br />_________________________________________________________________________________________________________<br />Reported CPU speed: 2811 MHz<br /><br />Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.<br /><br /><br />_________________________________________________________________________________________________________<br />MEASURED INTERRUPT TO DPC LATENCIES<br />_________________________________________________________________________________________________________<br />The interrupt to DPC latency reflects the measured interval in which a DPC could execute in response to a hardware request from the moment the interrupt service routine started execution.<br /><br />Highest measured interrupt to DPC latency (µs): 249.112174<br />Average measured interrupt to DPC latency (µs): 4.192113<br /><br /><br />_________________________________________________________________________________________________________<br /> REPORTED ISRs<br />_________________________________________________________________________________________________________<br />Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.<br /><br />Highest ISR routine execution time (µs): 167.860192<br />Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation<br /><br />Highest reported total ISR routine time (%): 0.053645<br />Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation<br /><br />Total time spent in ISRs (%) 0.072883<br /><br />ISR count (execution time <250 µs): 39851<br />ISR count (execution time 250-500 µs): 0<br />ISR count (execution time 500-999 µs): 0<br />ISR count (execution time 1000-1999 µs): 0<br />ISR count (execution time 2000-3999 µs): 0<br />ISR count (execution time >=4000 µs): 0<br /><br /><br />_________________________________________________________________________________________________________<br />REPORTED DPCs<br />_________________________________________________________________________________________________________<br />DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.<br /><br />Highest DPC routine execution time (µs): 257.982924<br />Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 378.66 , NVIDIA Corporation<br /><br />Highest reported total DPC routine time (%): 0.069330<br />Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.<br /><br />Total time spent in DPCs (%) 0.247498<br /><br />DPC count (execution time <250 µs): 252099<br />DPC count (execution time 250-500 µs): 0<br />DPC count (execution time 500-999 µs): 1<br />DPC count (execution time 1000-1999 µs): 0<br />DPC count (execution time 2000-3999 µs): 0<br />DPC count (execution time >=4000 µs): 0<br /><br /><br />_________________________________________________________________________________________________________<br /> REPORTED HARD PAGEFAULTS<br />_________________________________________________________________________________________________________<br />Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.<br /><br /><br />Process with highest pagefault count: chrome.exe<br /><br />Total number of hard pagefaults 1<br />Hard pagefault count of hardest hit process: 1<br />Highest hard pagefault resolution time (µs): 11.133404<br />Total time spent in hard pagefaults (%): 0.000004<br />Number of processes hit: 1<br /><br /><br />_________________________________________________________________________________________________________<br /> PER CPU DATA<br />_________________________________________________________________________________________________________<br />CPU 0 Interrupt cycle time (s): 0.601174<br />CPU 0 ISR highest execution time (µs): 99.373533<br />CPU 0 ISR total execution time (s): 0.027945<br />CPU 0 ISR count: 31381<br />CPU 0 DPC highest execution time (µs): 136.338314<br />CPU 0 DPC total execution time (s): 0.221039<br />CPU 0 DPC count: 167816<br />_________________________________________________________________________________________________________<br />CPU 1 Interrupt cycle time (s): 0.170953<br />CPU 1 ISR highest execution time (µs): 9.009249<br />CPU 1 ISR total execution time (s): 0.001496<br />CPU 1 ISR count: 285<br />CPU 1 DPC highest execution time (µs): 84.583778<br />CPU 1 DPC total execution time (s): 0.003217<br />CPU 1 DPC count: 930<br />_________________________________________________________________________________________________________<br />CPU 2 Interrupt cycle time (s): 0.191277<br />CPU 2 ISR highest execution time (µs): 8.114194<br />CPU 2 ISR total execution time (s): 0.000720<br />CPU 2 ISR count: 141<br />CPU 2 DPC highest execution time (µs): 140.123799<br />CPU 2 DPC total execution time (s): 0.023857<br />CPU 2 DPC count: 4684<br />_________________________________________________________________________________________________________<br />CPU 3 Interrupt cycle time (s): 0.153085<br />CPU 3 ISR highest execution time (µs): 14.964781<br />CPU 3 ISR total execution time (s): 0.000146<br />CPU 3 ISR count: 10<br />CPU 3 DPC highest execution time (µs): 44.680896<br />CPU 3 DPC total execution time (s): 0.008062<br />CPU 3 DPC count: 1375<br />_________________________________________________________________________________________________________<br />CPU 4 Interrupt cycle time (s): 0.380591<br />CPU 4 ISR highest execution time (µs): 0.0<br />CPU 4 ISR total execution time (s): 0.0<br />CPU 4 ISR count: 0<br />CPU 4 DPC highest execution time (µs): 93.144077<br />CPU 4 DPC total execution time (s): 0.049773<br />CPU 4 DPC count: 33050<br />_________________________________________________________________________________________________________<br />CPU 5 Interrupt cycle time (s): 0.161991<br />CPU 5 ISR highest execution time (µs): 0.0<br />CPU 5 ISR total execution time (s): 0.0<br />CPU 5 ISR count: 0<br />CPU 5 DPC highest execution time (µs): 0.0<br />CPU 5 DPC total execution time (s): 0.0<br />CPU 5 DPC count: 0<br />_________________________________________________________________________________________________________<br />CPU 6 Interrupt cycle time (s): 0.368786<br />CPU 6 ISR highest execution time (µs): 0.0<br />CPU 6 ISR total execution time (s): 0.0<br />CPU 6 ISR count: 0<br />CPU 6 DPC highest execution time (µs): 105.887940<br />CPU 6 DPC total execution time (s): 0.081814<br />CPU 6 DPC count: 25654<br />_________________________________________________________________________________________________________<br />CPU 7 Interrupt cycle time (s): 0.547412<br />CPU 7 ISR highest execution time (µs): 167.860192<br />CPU 7 ISR total execution time (s): 0.153160<br />CPU 7 ISR count: 8034<br />CPU 7 DPC highest execution time (µs): 257.982924<br />CPU 7 DPC total execution time (s): 0.235259<br />CPU 7 DPC count: 18591<br />_________________________________________________________________________________________________________<br />Then please run BreakawayOne App or start the service, and do the same thing with LatencyMon and copy/paste that second report into code tags also.
It could also be beneficial to pay attention to LatencyMon meters to see if something suddenly increases any of them exactly when the skipping in BaOne starts happening. If that does happen, then stop LatencyMon immediately and copy/paste that, since that will surely show (at least part of) whatever is causing this to happen.
It may also be useful to see what your top ISR and DPC counts are for your drivers…
