Search results

Generally you won't need ASIO4ALL, and anyway using it will not really allow using ASIO capabilities in full. If you choose the ASIO option, do you see your audio device there? If so, then it supports ASIO. And after selecting the device, you need to choose proper ASIO channels for input/output...

Thank you for the video, I added it to our bug report (please keep this video available so we can review it).

Noted for the upcoming export feature, thank you.

When using the File mode, the data is stored in the files, where your music files are. To back this up, it is enough to copy the music folder, this will also copy all the data in it.

Thank you for the suggestion, we'll add an export feature in one of the next updates.

In the original post you said that you set voice track attenuation (not auto intro attenuation) - those settings were separated in 7.1, and before that it was a single option for all. Does the track you belong to any file type or it's a regular music?

This should work. Rules are applied from top to the bottom, so more specific rules should be closer to the top, and more general to the bottom.

You can add a file type for TTS: https://www.radioboss.fm/support/radioboss-cloud/using-file-types/ Then in Setting->Crossfades set its mix point and fade out to zero or low values.

You can use ASIO device to eliminate the latency, this should help. Or use "Output to encoders only" and not hear yourself (and mic bed also).

Now it's controlled separately in Settings, Playback, Fading - Auto Intro section.

Currently there are only two options: when you hear the mic and its bed, and when you don't hear neither (when "Output to encoders only" is enabled). Listeners will hear both always.

It depends on how you set it to compare strings. "Equals" means that the strings must match (case insensitive), there are different options for partial match like starts with/ends with/contains. Probably you can use one of those. Metadata postprocessing rules are applied after the title string...

I'm sorry, for Cloud there's no printout function.

When you set it to "Output to encoders only" it affects both mic and its bed.

Metatada postprocessing works on the broadcasting title, as a single string - after the title is determined. That is, it happens after the XML file (or whatever metadata source you use) has been processed. That is, it processes the source, gets the title string, then it applied the metadata...

To test if the input works, you can add it to the main playlist and play it there. Then move it to AUX paylist, or keep it in the main playlist - depending on what end result you want to achieve. When AUX player is set to play on the main device, it will play on the Main Soundcard you set in...

This is a false positive. Some odd AI detection.

We'll consider adding this as a widget as well so that you can copy-paste the code to your web site.

If you want to run events when the silence is detected, the easiest way would be to use the runevent command as specified above.

In this case, adding Line Input to AUX player and playing it there will be equivalent to having the MIC button pressed (if both input and MIC are configured to use the same device).