- This topic has 30 replies, 7 voices, and was last updated 15 years, 4 months ago by
.
-
Posts
-
I’m running it on windows 7…32 bit. seems to be running fine.
[quote author=”DjSmooth”]I’m running it on windows 7…32 bit. seems to be running fine.[/quote]
Okay, I found out what causes it to exhibit the bug I was seeing. If you use large fonts set to 150% as I do (the PC is used on a TV) you should get the bug. I dropped down to the default font size and can adjust the settings now. It would be nice for this bug to be fixed, but not essential I guess so long as the work around is clearly stated.
Stuart
That’s an important clue! I never would have found that.
But.. *How* could this possibly be?? I can think of no rational explanation yet — it definitely shouldn’t have an effect.
I wonder if the same thing happens in XP with large fonts. Time to try it 🙂.
///Leif
Ok, I increased the DPI in XP, but it had no effect. So that’s good news.
Windows 7, I tried Breakaway and Breakaway Live and they’re both affected (Text size was set to Larger – 150%).
What I found is, when I placed the window in the top half of the screen, the controls worked fine. In the bottom half, the controls were zapped all the way to the left.
A similar thing also happens with Winamp, but the opposite halves; trying to select something from the Media Library only works from the bottom half.
Text size set to 125% appeared to have no affect.
I see it! Breakaway currently runs extremely poorly in Windows 7 x64 with font size 150%. Not only does the sliders pull all the way to one side with no hope of adjusting (WTF?) but the child process also completely fails to start, so I have to uncheck Audio Realtime Priority for it to run.
That’s not a very good user experience. I’m going to have to get to the bottom of this.
///Leif
Okay, I’m at the bottom of it. 🙂
There’s one more thing to trigger the problem.. Aero has to be on.
With Aero, and a high DPI setting, Windows helpfully scales the whole window, and reports back scaled pixel coordinates for everything. When I ask Windows what resolution my screen is (1280×1024), it responds 860×563 or something like that. When I ask "where is the mouse cursor", it responds in scaled-down coordinates. However, when I tell it "please move the mouse cursor to X,Y", it moves to the REAL coordinates! So, if I ask windows "where’s the mouse", and then tell windows to send the mouse to that same place, the mouse cursor will move.. a lot. Doh!
If I didn’t know better (which I don’t), I’d say it was a bug in Windows 7 RC. When this happens, my program gets thrown for a loop, where the disparity gets interpreted as the user quickly dragging the mouse left, and the slider jumps all the way to the left.
The other bad thing about this DPI scaling is that it looks like crap! Breakaway is already a resizable app (at least the main window), so to avoid this problem (and the ugly scaling), I found out that there is an API to tell windows that "I’m DPI aware, thanks".
So, I now call that API, and the problem is gone. It’s not a great solution, because it’s now incompatible with visually impaired individuals. I will have to implement proper DPI awareness in the future, but at least now it runs.
0.90.75 is released! Check the first page of this thread.
///Leif
I just installed 0.90.76, excellent idea having Core 1 for speakers and 2-4 for broadcast.
I thought it’d be good to have Core 1 as the speaker output and Core 2 for streaming but then I heard the "Live Demo" thing. I guess it can’t be done with only a single core registered?
quote :I thought it’d be good to have Core 1 as the speaker output and Core 2 for streaming but then I heard the “Live Demo” thing. I guess it can’t be done with only a single core registered?Actually it can — using just the 1 core you bought!
The Encoder plug-in output is before the audio gets sent to the speaker controller. Thus, if you run the encoder as a plug-in in Breakaway Live, you can do any amount of speaker equalization (to calibrate your own monitoring setup) without affecting the outgoing stream at all.
Best,
///LeifI see now, all makes sense. Was just learning how the new stuff works.
I just blinked, and there’s .90.77. Nice.
quote :I see now, all makes sense. Was just learning how the new stuff works.I’d say you’re doing extremely well considering there’s no freaking manual. I’m about to start writing it. Not looking forward to it…
///Leif
[quote author=”Leif”]
[*]New version of Breakaway Pipeline included, which works much better on dual and quad core systems. To get the new version of the pipeline, you must UNINSTALL all previous breakaway products, and reboot your machine, and then run the new Breakaway installer. It will not upgrade an existing pipeline, because if it’s still on your system, the old one must be working fine already. So, if the old pipeline is working fine, don’t worry about it! No need to reboot or uninstall, just install the new one on top.///Leif[/quote]
Hi: This AM tried to upgrade from .69 to .77 by "installing on top". Installer would not allow it. Installer complained that an earlier version was detected and the product must be uninstalled & comp rebooted. Installed died after that. Tried a couple of times, then backed up ini, uninstalled and installed. That worked fine, just no way that I can see to install on top of an existing working install.
Hi Keith! Sorry about that confusion. Due to an unforeseen compatibility issue with upgrading on top, I added code to check the pipeline version, and force a clean install if you had an old version. Then, I forgot to upgrade the text! I apologize for the confusion, and perhaps I need to make it easier for users, for example by having a tool to uninstall and reinstall just the pipeline, so you don’t have to mess with the ini file. I’ll look at it tomorrow.
///Leif
Is the latest instruction for upgrade installation to install over the current BA Live install, or to uninstall older version and then install the upgrade?
Just demoing Live .79 on my p4 3ghz ht system running xp pro with 3gb ram. Creative audigy 2zs pci. When I’m just listening and tweaking with the controls, at some random intervals the meters and scope freeze and I can’t adjust controls for a few seconds. The audio continues and is being processed just fine, the interface just freezes. I’ve not had any previous BA installs, other than RTA.
I watch the cpu util % and it seems to stay normal during this pause. Is this a function of the demo limitation? What can I look at?
Thanks.
[quote author=”AuBadge”]Is the latest instruction for upgrade installation to install over the current BA Live install, or to uninstall older version and then install the upgrade?[/quote]
Install over the current install. Sorry for the confusion.
[quote author=”timmywa”]Just demoing Live .79 on my p4 3ghz ht system running xp pro with 3gb ram. Creative audigy 2zs pci. When I’m just listening and tweaking with the controls, at some random intervals the meters and scope freeze and I can’t adjust controls for a few seconds. The audio continues and is being processed just fine, the interface just freezes. I’ve not had any previous BA installs, other than RTA.
I watch the cpu util % and it seems to stay normal during this pause. Is this a function of the demo limitation? What can I look at?
Thanks.[/quote]
I’ve had a couple of other reports of this, but I have never been able to reproduce it on any of the multitude of systems I’ve tried it on. It’s a bug, not a demo limitation. Hopefully I’ll be able to reproduce it and track it down some day — thankfully it’s not affecting the audio. *phew*
///Leif
- The forum ‘Breakaway Professional Products – [discontinued]’ is closed to new topics and replies.