There's still the issue that their own documentation lists the Firebox as
having a 50KHz range which it clearly does not. There's also this thing
called the Uniform Commercial Code as well as Truth-in-Advertising laws
which can be used to hold their feet to the fire.
Basically, they can handle
Presonus delivered a downloadable image that will reflash the PROM and
fixes the problem. Expect to hear more soon from Flex. They knew of
the problem and waited until a critical mass arrived on their door step.
Bob
Rick Fletcher, KG6IAL wrote:
There's still the issue that their own
You could file a complaint at the FTC as one of the options. The FTC
might write the company, and while they probably won't do more, that
may put some pressure on the company.
Chas, W1CG
At 01:15 AM 4/8/2006, Rick Fletcher, KG6IAL wrote:
There's still the issue that their own documentation
At the PreSonus.com web site under the technical
specifications for the Firebox it says:
As a commitment to constant improvement, PreSonus Audio
Electronics, Inc. reserves the right to change any specification
stated herein at any time in the future without notification.
Mike - AA8K
I'm still not able to get access to the shuttlepro.pref files on the site.
Could someone who can, please send me a pdf or word doc file with the
prefered allocation details for each button ??
I can open the . pref file with notepad but cant make any sense of what
it displays.
I know I'm as
Bob,
This is great news!
It is wonderful to know that as a group, we Flexers can add enough
density to reach critical mass and place it on their doorstep.
I look forward to putting the upcoming fix through its paces. Thanks to
all.
(OK, here is the ra-ra part) Way to go TEAM!
-Tim
---
Tim
Just wanted to report an xmit audio problem and its resolution so that
others with similar problems might possibly benefit.
Initially my audio reports were terrible. Admittedly, I was not using a
classy mic but even so I was expecting better. I spent some time on the air
and on the phone with
Keith,
You cannot open the .pref file directly. You should save the file and then
import it via the Shuttle Pro Control Panel. Please see the Shuttle Pro
Support document (pdf) on our download page as it describes this process in
detail.
Eric Wachsmann
FlexRadio Systems
-Original
Somewhere between 1.4.5 preview 12 and 1.4.5 preview 16 it appears the
buffer size selection on Setup-Audio got disconnected from the value the
code is actually using. Currently (1.6.0) it looks like the block_size is
locked to 2048 in audio.cs (private static int block_size1 is initialized
In setup.cs this function changes the audio buffer size when the setup
audio value is changed:
private void comboAudioBuffer1_SelectedIndexChanged(object
sender, System.EventArgs e)
{
if(console.PowerOn)
{
console.PowerOn = false;
I also had issues with this. I reloaded the driver (the current one on the
Griffin website) several times and unplugged and reseated the USB connector
several times. I was beginning to think in terms of a bad connector when the
thing finally started working one way or the other. I hate problems
Glad to hear everything worked out. Your problem was probably the ground
loop all along. Audio devices i.e. sound cards are very susceptible to
ground loop problems. A simple and inexpensive fix is to purchase a Ground
Isolator and some adapters from Radio Shack. You install it between the Mic
and
I should have provided more detail in my original post. I found that
the manual way of installing the device and its device driver (as per
the instructions on the Griffin Technology page) was the only way I
could get it to work correctly.
One of the challenges with the PowerMate is that when it
I'd posted to the list because I thought discussion of what's going on
inside the code was a good thing. My thought was open discussion of code
changes for an open project with multiple developers was a good thing so
other people mucking in the code are aware of changes/questions/etc.
I'll
At 02:25 PM 4/8/2006, Bill Tracey wrote:
I'd posted to the list because I thought discussion of what's going on
inside the code was a good thing. My thought was open discussion of code
changes for an open project with multiple developers was a good thing so
other people mucking in the code
This is my mistake for acknowledging a bug report here. All bug reports
for released versions are to be entered on the bug tracker. That way
everyone, including me, can have record of it. This is a promise: I
have acknowledged my last bug report here. If Jim wants to follow bugs
and
This one was stupidity itself. Very ugly. It should be tracked around
the world as a monument to programmer ineptitude.
Frank Brickle wrote:
Oh, well, why not take the easy way out? Just eliminate all remaining
bugs and then there's nothing to track ;-)
73
Frank
AB2KT
Robert McGwier
Since the Flex software no longer supports multiple sounds cards, how
would one achieve similar results? I want to use the built in sound
card for my speaker out, and also possibly at the same time send the
sound output to other software.
Would I use VAC to redirect the speaker sound out to a
Waste $20 seven times and you can get a Delta-44 and all your problems
would be solved :-)
-Tim
---
Tim Ellison ( [EMAIL PROTECTED] )
Integrated Technical Services ( http://www.itsco.com )
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of KD5NWA
Sent:
The problem I want to solve is peculiar to a Delta-44, but the Delta
card is a funky card, it's not like a standard sound card. It outputs
all sorts of noise when not in use and when you turn off the PC.
Leaving a Speaker connected to it is subjects me to all sort of noise
in the middle of
Takes a bit of work for someone to find the bug tracker..
Not visible in google
Not linked from the flex-radio.com website (at least not in any obvious
places, like, say, the support tab)
The support page has references to:
FAQ
Troubleshooting
Downloads
Oh, there it is.. in the title bar at
At 03:46 PM 4/8/2006, Robert McGwier wrote:
This is my mistake for acknowledging a bug report here. All bug reports
for released versions are to be entered on the bug tracker. That way
everyone, including me, can have record of it. This is a promise: I
have acknowledged my last bug report
Cecil,
I use VAC (and the Audio Repeater feature in particular) to route audio from
the output of the radio to a Bluetooth headset (or speakers from the Delta
44.) It's a little strange to think about routing audio like this, but it
seems to work pretty well once you get your head around it.
Bob
Do not apologize. Lot of us lurkers are interested and stimulated by
info
as to where things are in the software but are afraid to ask.
There is another point. We just started a reflector for those not
interested in software but in the operational aspects of the hardware.
24 matches
Mail list logo
