Forum Replies Created
-
AuthorPosts
-
LeifKeymaster
Hi Hwyann,
Undocking by pulling the window is supported, and should work great. It does for me anyway. What OS and Breakaway Live version are you using?
The toolbar is in the latest version (0.90.96) of Breakaway Live. Right-click on the windows taskbar and choose Toolbars, you should see it in the list.
You can always force the window to undock by right-clicking and choosing "Undock".
If the Titlebar (in Breakaway Live) is hidden, you should be to right-click and "Show Titlebar".
///Leif
LeifKeymasterDone! I’ve ordered an RME HDSP 9632. It will take a couple of weeks before I have it though — once it arrives, it has to be shipped again to Thailand (where I live).
///Leif
LeifKeymasterHmm.. RME HDSP.. Another customer is having a different problem running BBP ASIO on this card.
I may just have to buy one of these cards for testing purposes.
///Leif
LeifKeymasterFeedback?? I definitely wasn’t aware of that problem!
Could you post a screenshot of your i/o configuration screen?
///Leif
LeifKeymasterYes, I believe so. 🙂
///Leif
LeifKeymasterESI Juli@ is Tilt 7 if I remember correctly.
I finally have a Juli@ now but I don’t have a computer to try it on here (laptop) — will plug it in when I get home in a week or so. Still in the states 🙂.
///Leif
LeifKeymasterKS talks directly to the sound card driver, but it’s still not as low latency as ASIO, which was designed to be a robust low latency interface.
ASIO rocks, dude. 🙂
///Leif
LeifKeymaster[quote author=”JesseG”]Is this not correct?[/quote]
You’re making several assumptions that are only true if you very carefully make them true.
Peak-control *is* happening in Breakaway Live whether you like it or not (unless you turn Final Drive down to -6 — then it won’t happen with *most* content). If you add any further processing to it, this peak control is undone, any peak-controlling element before it in the chain becomes a distortion generator with no benefit.
Peak control *is* also happening inside whatever you put after Breakaway, unless you specifically attenuate. How do I know this? Because you can’t go over 0dB.
[quote author=”JesseG”]Pepperjack & I haven’t said anything about clipping, going over -0dBFS, or modulating past 75kHz. And Pepperjack and I are not talking about trying to control the loss of peak control with further dynamics processing. Unless I am mistaken.[/quote]
Indeed you haven’t, and that’s the issue. Audio processing isn’t magic, it’s science! Nothing good happens automatically. Bad things (like saturation, i.e. clipping, i.e. peak control) happens whether you are aware of it or not.
Come on, Jesse, you know better.
///Leif
LeifKeymaster[quote author=”JesseG”]Since peak control isn’t an issue for an internet stream[/quote]
How do you figure, exactly?
///Leif
LeifKeymaster[quote author=”Boki”]Question is,
Does Leif wants to make such STL software?[/quote]I do. When is another question, though.
Having this exciter in my possession will certainly increase motivation and thus scheduling priority 🙂.
///Leif
LeifKeymasterBEFORE!
Extremely important. Any kind of processing to an already peak-limited signal adds overshoot (undoes the peak control) without undoing the distortion. Thus, as the signal gets peak-controlled again, you end up with much more distortion.
It’s fine to do it before though — that’s what the Effects plug-in section is for. EQ’ing before the multiband compressor actually works great.
///Leif
LeifKeymasterYes. It would be a good idea to match the buffer size with the sound card’s.
Also, since you have an M Audio card, how about just using ASIO instead of KS?
///Leif
LeifKeymaster[quote author=”CiXel”]How do we enable older presets?Is it just adding: "include_obsolete_presets=1" into the breakawaylive.ini[/quote]
Almost!
In the [Master] section add ObsoletePresets=1
///Leif
LeifKeymaster[quote author=”timmywa”]Leif,
One further question… On Audio Repeater, the goal is to get below 10% jitter at 2 buffers. I think this goal is different in BAE… 2 buffers may be a bit low for solid audio… My question is if I get the lowest jitter through repeater at 2 buffers, 1024 size, do I actually use 2 buffers at 1024 inside BAE? or should I use 4 buffers at 512, or some other combination?
Or is my logic all messed up and the number of buffers should be the same inside BAE as it is in repeater?
Side question, when I tuned it with repeater, the input on pipeline was pretty high, maybe 1024, it seemed odd that a virtual device would have to have such a large buffer size. I could see an old audio card needing it as the hardware is crap, but this isn’t hardware at all.
I hope all this makes sense. Thanks![/quote]
Actually, I would say anything under 50% jitter is potentially acceptable, as long as it runs stably.
The number of buffers should be the same inside BAE as the repeater — it’s the same i/o code, BAE just does more work.
With the East Asian language bugs that were just reported here in the forum, it may not be too long before next release, because that’s something that does warrant going through the process of releasing again.
///Leif
LeifKeymaster[quote author=”Milky”]Thanks guys.
Any thoughts on my other post about the jitter being high but the audio was stable, and when I lowered the jitter (by increasing the buffers), the audio popped now and then?[/quote]That doesn’t make sense at all 🙂. How high was it when it was high?
///Leif
-
AuthorPosts