Home › Forums › Breakaway Audio Enhancer › Breakaway 1.20.12 Release Candidate
- This topic has 42 replies, 3 voices, and was last updated 15 years, 12 months ago by lpy7.
-
AuthorPosts
-
November 25, 2008 at 8:22 am #4531AnonymousGuest
[quote author=”Leif”]In fact astonishingly few programs use Kernel Streaming — I only know of a handful, besides my own software: 3rd party Kernel Streaming plug-in for winamp, the ASIO4ALL driver, Foobar 2000 player.
You’re absolutely right about the volume control issue regarding programs just modifying the system volume control — this is a big contributing factor to why that volume control gets disabled when you install Breakaway — the pipeline is supposed to ignore it 🙂.
///Leif[/quote]
Right. I use SAM Broadcaster, but not for streaming a netcast for now, using Kernel Streaming and it bypasses the mixer and goes right to the audio chipset. It’s great.
I use very few programs when watching video. Besides using Firefox, I use Media Player Classic and will watch Joost on occasion. Other than that, I don’t use much else. It is a pain to have to fight software that don’t have independent volume or the inability to have Kernel Streaming. I don’t close one program and go load another. I usually leave all of the running and when I feel the urge to change, I change. I was fighting this problem before installing Breakaway anyway, but I did notice that I didn’t have to worry about at first install. I was under the impression that the mixer was rendered useless, which I thought was a excellent idea. However I see that I’m still going to fight Windows. Oh well.
I am going to recommend this to a friend of mine that does voiceover work. He might get a kick out of this product.
November 25, 2008 at 1:55 pm #4532LeifKeymasterVery very strange..
On my XP systems, opening the mixer and muting the pipeline has NO effect. Audio continues.
Which operating system are you guys running? Could it be a vista-related issue?
///Leif
November 25, 2008 at 6:22 pm #4533AnonymousGuestI’m running XP.
November 26, 2008 at 4:04 am #4534AnonymousGuest[quote author=”Leif”]Very very strange..
On my XP systems, opening the mixer and muting the pipeline has NO effect. Audio continues.
Which operating system are you guys running? Could it be a vista-related issue?
///Leif[/quote]In Vista, muting via Windows mixer (mute in systray):
If my default sound device is Breakaway, muting has no effect.
If my default sound device is the soundcard Breakaway is sending audio to (the backend processing sending to sound card), muting stops the sound, but Breakaway’s mute is not in effect, and it appears to continue processing. No Breakaway indicators change status.
The default sound device isn’t important; what matters is that the application in question is set to output into Breakway’s pipeline. Some applications only output into the default sound device, so if I want that processed, Breakway must be set as the default sound device.
November 27, 2008 at 12:17 am #4535LeifKeymasterOh, this explains it.
If the sound card is the default sound device, and you mute that device, obviously no audio will not be heard. This is in what you asked it to do, and no amount of programming will get around it 🙂.
It is recommended to keep Breakaway the default device.
///Leif
November 27, 2008 at 7:17 am #4536AnonymousGuestBreakaway Pipeline 1 is the preferred sound device. If it wasn’t, Breakaway wouldn’t be processing the audio. This is a strange monster. 😕
I have a few things to look at that I just thought of. When those things are looked at, I’ll try again and give you a update. I might uninstall and then reinstall Breakaway. Something might have happened from the constant restarts and it got messed up. I’m not giving up on this. I realize that the software behaves a certain way and it’s not doing so on this machine. My SQL database crashed from the restarts, too so the machine is plagued with issues right now anyway.
Philip
November 28, 2008 at 12:42 am #4537LeifKeymasterVery strange indeed.. I still don’t understand how the mute can be affecting the pipeline, since it (correctly) doesn’t on all my systems.
It is still possible to have audio go into Breakaway without the pipeline being the default sound device — you would then have to set each application to play into the pipeline instead of the default device. When Carl mentioned having done this, I thought I had found the culprit, but life is never that easy is it… 😕
///Leif
November 28, 2008 at 2:51 am #4538AnonymousGuestCertainly isn’t.
I’m waiting for a good opportunity to restart the machine, if it doesn’t force me to do so beforehand. 🙂 I’ll let you know of the results.
November 29, 2008 at 6:04 pm #4539AnonymousGuestHi Leif,
How about adding peak/average levels to the input and output sides of the meters? It would be cool to display an average level so the effects on loudness could be quantified.
Thanks,
StuartNovember 30, 2008 at 4:57 am #4540AnonymousGuestI’ve found a sure way to crash Breakaway Personal. It is slightly involved, but you should be able to reproduce it running Vista.
First, right click the GUI window and uncheck the Show Titlebar option, then right click again and Minimize the GUI. If you have your taskbar autohide, in the lower left of your screen you will see the corner of a title bar window labeled Breakaway. Double click it and Breakaway will crash.
Problem signature:
Problem Event Name: APPCRASH
Application Name: breakaway.exe
Application Version: 1.2.0.12
Application Timestamp: 491ee6c6
Fault Module Name: breakaway.exe
Fault Module Version: 1.2.0.12
Fault Module Timestamp: 491ee6c6
Exception Code: c0000005
Exception Offset: 000626f8
OS Version: 6.0.6001.2.1.0.768.2
Locale ID: 1033
Additional Information 1: 1346
Additional Information 2: a44ed44edff8ed281cf2dd47b78527a6
Additional Information 3: dc17
Additional Information 4: f9e6f0a51245962ba46dcdc7a85b90cbSurly you would say do not try to restore the Breakaway GUI window by double clicking there, use the systray or taskbar. What fun is that? Nothing is foolproof to a sufficiently talented fool.
November 30, 2008 at 8:27 am #4541LeifKeymasterNow that is well and truly a reproducable bug, Carl!
Good find.
I bow to your level of talent in this matter 😆
The crash is indeed a bug, but the problem is really earlier — windows without a titlebar should not be minimizable, as they will then inevitably leave that titlebar window behind. To be honest, I just never tried it.
I will add code to make the Minimize option go away completely when in this state. If minimize was successful, there would be no way to bring the window back other than by clicking on the tray icon, and at that point we might as well have closed the window altogether. Would save resources. 🙂
///Leif
December 2, 2008 at 12:43 am #4542AnonymousGuestI figured that it could just be the chipset and Windows not playing nice, but after doing a few things it still exhibits the same issues as it as always. I guess it a problem I’m going to have to live with until I get a sound card.
PcW
December 2, 2008 at 9:55 am #4543lpy7MemberInteresting. Tried that Minimise bug on mine but it didn’t crash.
-
AuthorPosts
- You must be logged in to reply to this topic.