Forum Replies Created
-
Posts
-
Sorry to hear of your woes. Similar to another post in this forum, I get very suspicious when something which has been working flawlessly suddenly behaves badly with a change of hardware or OS.
Is the new hardware on the same OS level as the old? Windows 10 or 11? How similar is the configuration – Motherboard, sound card, RAM?
When you say that the old machine “blew up”, are any of the components salvageable? Could you swap the old hard drive/configuration back in? Is the sound card serviceable?
I’d like to see some settings images and oscilloscope patterns.
@lumper5x. If this really is a problem on the “latest and greatest” version, it may take some time to track down. It may be a driver specific to your particular environment, or it may be widespread.
Either way, the short time solution would be to roll back the latest and greatest to a stable platform, and wait until we can re-produce the error, and then work on a fix.
The AAC Plus zip file (link available elsewhere on the forum) contains three files – enc_aacplus.dll, enc_aacplus.dll and nscrt.dll and these should all be copied to the BA1 installation folder (typically “C:\Program Files\BreakawayOne”). You should then close and re-open BA1 for the list to update. If you are running BA1 as a service, you will need to shut that down and re-start it for the list to update.
Sadly, Keith passed some time ago, but his son, John is taking care of business. The correct email address should be support@claessonedwards.com. I raised this matter with John privately and he tells me that the new codes have been passed to you now.
Glad you got things going again, although a very drastic method which shouldn’t have been necessary.
You only use the pipeline as an intermediate step if your playout software normally goes directly to a sound device. BAE needs to be “sandwiched” between the player and the output device so that the presets and tweaking can be applied to the audio before it is passed to the output device. So the process becomes Playout SW > Pipeline > BAE > Sound device.
If your software allows it’s output to be seen as an input device to BAE, then you don’t need the pipeline.
I have exactly the same setup as you on my home system, except I use the “internal” stream option instead of Icecast. I can have the HD core playinf straight out of my home system, but, down in my workshop half a kilometre away, I can listen to the stream over my network.
You can only select different presets in the HD core > Audio Processing section, but the preset you select should automatically be heard in the stream (slightly delayed due to buffering). I say this without actually being able to try the Icecast option, but I am certain it would behave exactly the same way.
I also find lots of screen prints are useful. Open your core, common, audio, preset, Stream etc pages and press Ctrl + PrtSc and then save the images in a document, and then back up that document with your configuration file.
Are you using the Breakaway pipeline at all? If so, do you have the latest version for Windows 11 which is 4.31. The fact that you are getting this message “Error opening Breakaway Pipeline for test tone output!”, suggests to me that there is a mis-match.
The other possibility, seing as it has suddenly started after many years, is that a recent W11 update has clobbered something. Usually uninstalling and reinstalling BAE gets around this problem, but it might be something new that you have stumbled across. Check your Windows Update History to see if there is something that was installed at the same time as the fault developed.
Ah! Now this looks promising – url0=http://192.168.10.12:8282/parameter/fm1/misc/rds_ps=3t:<< %output1:format0%/%format0%/%output2:format0%/%output3:format0% So, we have now established your LAN IP. We now have to find the parameter substitutions. What happens if you copy/paste "url0=http://192.168.10.12:8282/parameter/fm1/misc/rds_ps=3t:<< %output1:format0%/%format0%/%output2:format0%/%output3:format0%" (without quotes) into the BA1 field? Alternately, Can you point the "RS" spec to that ini file on your hard drive?
I don’t personally use the FM Core (although I have a licence to configure one). I know that fm1/misc/rds_ps is to set parameters for the Program Service part of RDS and that, typically, they point to locations (usually on your server hard drive), so Leif would probably set up a folder (Maybe “RDS”) into which information would be written and then picked up by the fm1/misc/rds_ps spec. We need to reconstruct that/those links without me having the faintest idea what they were.
Did he/do you have some sort of scheduled task (or AHK) running which retrieves something from Ots logs or from the RAC in Ots? I assume this is coming from a PC using Ots as the playout system?
I don’t suppose that you have a recent backup of your hard drive? Screenshots, maybe?
Without knowing the original parameters, it’s going to be pure guesswork to try and reconstruct what you had, but we might be able to work through available options to see what we can achieve.
You say that you are “only getting Artist and Title” now. What other information were you providing before that is now missing?
G’day, Teddy. Nice to “see” a familiar face around here.
I’m not sure from your post whether you have clobbered a setting that you had working or whether the default parameter has been knocked out. If it’s the latter, you can see the default settings by entering “http://{your BA1 IP address}:8282”. This will take you into the internal web server and you can then scroll through all of the possible settings.As an aside, you can also export all of your configuration to a file and use it to restore if things go wrong (or you set up another server).
Have you tried the suggestions provided by MrKlorox? They worked for “Whay”. Also, particularly using ASIO, latency should be very low. Use the smallest possible buffer size without artefacts or jitter.
I use ASIO with the HD core and I cannot detect any problems with lip synch when watching music videos.
