Forum Replies Created
-
AuthorPosts
-
January 29, 2010 at 12:47 pm in reply to: Question: Should I Increase INPUT vs OUTPUT (44100 vs 48000) #5102
timmywa
ParticipantSo, the question is… Should I stream at 48000? If most of the world’s consumer-level soundcards are kickin at 48000 anyway, does it make sense or since the "industry standard" is 44100, should I keep it there? Perhaps there are apps or hardware that can’t playback a 48000 stream…
timmywa
ParticipantThere is a feature in MP3GAIN called Maximize or something that does more "gain riding". Purists would never use it as it changes the song. But it’s a little more aggressive.
January 28, 2010 at 12:26 pm in reply to: Question: Should I Increase INPUT vs OUTPUT (44100 vs 48000) #5100timmywa
ParticipantSo to answer my own question… If I leave edcast’s setting to 44100…
Player Out to Pipeline (44100)
/
Breakaway Pipeline In (44100)
/
Breakaway Out Audigy (44100)
/ (conversion here on audigy??)
Edcast In Audigy (44100)
/
Edcast Out Encoder (44100)
/
Encoder Out Shoutcast (44100)This looks cleaner as there are less conversions in the chain. If the source material was never 48000, I guess the earlier theory is that breakaway is being nice to the audigy by feeding it audio at it’s native speed and handling that conversion internally. But it would have to be converted back, eventually, as my stream runs at 44100. This is JesseG’s method, btw.
January 28, 2010 at 1:21 am in reply to: Question: Should I Increase INPUT vs OUTPUT (44100 vs 48000) #5099timmywa
ParticipantTo add another element to this for streaming…. If I leave defaults as is in 44100 out 48000 (changing both to 2 channels)… would I also set the edcast cfg file’s LiveInSampleRate setting to 48000 as well??
This setting would look like this:
Music from player @ 44100 (that’s what they are encoded at)
|
|
/
Breakaway In Pipeline @44100
|
| (conversion here)
/
Breakaway Out to sb audigy @ 48000
|
|
/
Edcast In from sb audigy @48000
|
|
/
Edcast to encoder @48000
|
| (conversion here??)
/
Encoder to shoutcast @44100This seems to have 2 conversions one in ba and one in the encoder in edcast. I guess my question is twofold… Is this above diagram correct? Also, how do you keep the best quality and least conversions/most efficient transfer of clean audio?
I could change the encoder in edcast to send out at 48000, but i may loose some compatibility.
Help me here music whizzes… (I know JesseG has his own opinions, which I greatly respect and value. I’m looking for more opinions here)
Thanks!
timmywa
ParticipantBAE too… 😉
timmywa
ParticipantSean, what station??
timmywa
ParticipantSpeaking of the NR feature….
What kind of downsides are there?
I understand if there’s some high-end hiss or noise, the NR feature will try to get rid of it, but at what cost??
Thanks.
January 18, 2010 at 12:43 pm in reply to: Breakaway DJ – Device Does Not Support Requested Format #9730timmywa
Participant[quote author=”Leif”]Two reasons:
1 – The Breakaway core (a common building block of all Breakaway products except Breakaway RTA) did not support it. Breakaway uses 32-bit math, split as 16 bits for audio and 16 bits of headroom. However, it now has a mode where it can use 24 bits for audio and 8 bits of headroom (still +48dB), so this reason doesn’t exist any more.
2 – Simplicity vs Benefit: Generally, sound card drivers support 16-bit and not 24-bit, and the benefit of 24-bit is very small compared to the compatibility headache. Also, all Breakaway versions (even the $29 one) uses an advanced ultrasonic noise dithering algorithm for the output, which to me sounds perfectly clean even turning the volume down to -40dB.
I may do 24-bit support in the future though, but my to-do list spans volumes already, so please don’t hold your breath! I’d hate to lose a good customer 😉.
Best,
///Leif[/quote]Given this outstanding response, would I do best to switch the 24-bit feature off on my soundcard? Or will it not affect things either way?
Thanks.
January 18, 2010 at 3:51 am in reply to: Breakaway DJ – Device Does Not Support Requested Format #9723timmywa
ParticipantLeif, is there a reason you’ve not put 24-bit support in any of your products to this point?
timmywa
ParticipantThere’s also a Noise Reduction feature that you can enable that is a downward expander to help tone down some tape hiss or other noise.
timmywa
ParticipantMag, I don’t think memory’s the big clincher in this software. Most of the power draw is from the CPU. Best bet is Intel Dual-Core or better. Although I saw a major improvement in stability and clean sound going from a p4 2.6ghz (non-HT) to a p4 2.8 Hyper-Threading CPU. I was amazed!
Athlon CPUs will work but Leif’s code is built upon the Intel feature set and takes advantage of it.
The other key hardware is the sound card.
Hope that helps at least some.
timmywa
ParticipantSounds good, Leif!
You’re such a tease!
This feature would be useful for a/b comparisons.
Thanks again!
January 7, 2010 at 7:30 pm in reply to: Breakaway 1.30.02 with transparent toolbar for Windows Aero! #5040timmywa
ParticipantOther than being all about the bleeding edge, any reason a 32 bit xp user would benefit? Any other changes?
timmywa
ParticipantEdcast is still much better than shoutcast DSP. MUCH!
timmywa
ParticipantWELL SAID, sgeirk!
-
AuthorPosts
