Firebox issues

Hi
I am actually helping my worship leader troubleshoot his setup... he has a Presonus Firebox interface that has up until recently been working flawlessly, set up as follows:
guitar---preamp -\ /- iBook---Garageband
mic1---preamp - Firebox
mic2---preamp -/ \- Mixer---Studio Monitors
What has happened recently is that his iBook will recognize the Firebox when he plugs it in, ad the little dialog to start using it will appear... during the time that dialog box is open, everything seems to be working fine. We get signal from the mics and guitar through the Firebox and into the mixer, and all of the input level controls on the Track in Garageband seem to be functioning fine. As soon as we select the Firbox and close that dialog, the volume control at the bottom of the Track info section and the dropdown box to select the input channel (Channel 1 Mono etc) are disabled (Greyed out) and we lose all output from the Firebox including the Aux out to the mixer.
I don't know if this is caused by something in Garageband or the Firebox itself, so I figured I'd try here first.
I'm not sure what his laptop details are, except that it's OS X and I'm sure the latest version of Garageband.
Any help would be greatly appreciated.
Thanks
Dan

I have the same problem with the Presonus Firestudio Project and Snow Leopard. I'll download the beta drivers from Presonus's web site, uninstall the old drivers, install the new ones, and I can usually get the Presonus Firestudio Project to work -- briefly. Then maybe a day later, there's no sound, and usually the device isn't being recognized. So I'll repeat the whole uninstall, reinstall process, and the box will work and I can return to my projects in Logic, etc. -- for, typically, another few hours. It's now been more than 7 months since Apple released Snow Leopard, and Presonus still has nothing other than an unstable beta driver that is essentially nonfunctional? That's ridiculous. I could understand if this was an old, legacy product, but this thing is still being sold. If I want to keep making music on a Mac, I don't see any options other than to write off my $500 investment in the Presonus product, dump it in the trash, and shop for a new interface from another company. Can anyone recommend a Firewire interface in the $400-$800 range -- from manufacturer that is committed to, and has consistently supported, the Mac platform with updated drivers?

Similar Messages

Presonus FireBox issue

Hi.
I just purchased a Presonus FireBox as an upgrade from a Lexicon Omega audio interface. I have also used an M-Audio Firewire 410 briefly in the past with my black macbook. Before connecting my firebox I removed everything I could find that related to either previous audio interface from my computer so as to not interfere with the new one. But every time I plug the firebox into my macbook I get a blue light for a couple of seconds, then a permanent red light. I installed the drivers on my wife's PC and connected the firebox and it sync'd right up, steady blue light, so I know the firebox is working. I also am assuming that my firewire port on my macbook works since I have used the m-audio interface in the past. I tried plugging the firebox into the already booted computer, and booting the computer with the firebox already plugged in with the same results. I also reset the pram on my macbook and there's no improvement.
Is this an issue with OS X 10.5.8? I've only ever found info about 10.5.7 on Presonus's website. Do I need to move up to Snow Leopard?

Thanks for the response.
I tried messing with the Audio MIDI Setup but the problem is, the firebox doesn't even show up there. It's like the computer doesn't even recognized that there is something plugged in. That's why I tested the firebox on my wife's PC, to figure out which end was having the problem, the firebox or the computer. I suppose my firewire port could have crapped out, but it's obviously powering the firebox and I used it with an M-Audio Firewire 410 a few months ago with great results (the M-Audio wasn't mine, but after using it I wanted to switch to a firewire interface with more outputs for live performing and the firebox fit my budget).
Where is the firmware update on their site? I looked in Downloads for the firebox, and I searched for "firmware" in their main search and in the tech support forum and haven't found it.

Presonus Firebox issues

So I've had my firebox for about 4 months now and I just recently plugged it in and started up Logic. Well at first the light only glowed red and no matter what I did (restarts, unplugging, replugging) it wouldn't glow the pretty blue.
Well I finally got the light to turn blue but now my computer won't recognize the device. Audio MIDI setup does not recognize it, Logic Pro does not recognize it, Garageband won't recognize it, the Presonus Control Panel and update firmware applications don't recognize it. I'm so confused and frustrated with it.
Any suggestions?

I have the same problem with the Presonus Firestudio Project and Snow Leopard. I'll download the beta drivers from Presonus's web site, uninstall the old drivers, install the new ones, and I can usually get the Presonus Firestudio Project to work -- briefly. Then maybe a day later, there's no sound, and usually the device isn't being recognized. So I'll repeat the whole uninstall, reinstall process, and the box will work and I can return to my projects in Logic, etc. -- for, typically, another few hours. It's now been more than 7 months since Apple released Snow Leopard, and Presonus still has nothing other than an unstable beta driver that is essentially nonfunctional? That's ridiculous. I could understand if this was an old, legacy product, but this thing is still being sold. If I want to keep making music on a Mac, I don't see any options other than to write off my $500 investment in the Presonus product, dump it in the trash, and shop for a new interface from another company. Can anyone recommend a Firewire interface in the $400-$800 range -- from manufacturer that is committed to, and has consistently supported, the Mac platform with updated drivers?

Firebox issue: feedback with superfuzz and glam

I've been testing my new firebox and I'm getting horrible feedback (constant squeal) in the superfuzz and glam modes. I've noticed that for most effects, I need to increase the gain on the mic to about 3/4 of the way to get usable levels in garageband. If I increase it any more than that in superfuzz or glam modes the squealing starts. Increasing the headphones volume on the firebox also initiates the feedback. I'm using a new unibody MacBook pro with a 6-9 firewire cable. I'm connecting my electric guitar directly into the mic input (1 or 2). I've tried muting the other input sources in the control panel. I've tried it with and without the 12db boost. I have set the inputs and outputs to the firebox in the Audio/Midi utility, as well as in the Garageband preferences. Another thing is that there is no feedback during playback when monitoring is turned off. Let me know if you have any ideas, or if I should return the firebox. Thanks.

In addition, as you have a new TMS software version, I imagine that you are not using the old Cisco TMS appliance, so you probably have your TMS running under a standard Windows Server, and you probably have firewall, antivirus or any other security program running on that server.
Can you try to completly disable any local firewall and/or antivirus on the Windows where TMS is installed? If TMS begins to work as expected after turning off those security programs, I think you will have to add the TMS's executables as exception to the firewall/Antivirus softwares, so that they won't cause conflict with TMS's services.
In this folder you will find all the executables used by TMS's service:
C:\Program Files (x86)\TANDBERG\TMS\Services
For TMSPE, this is the path for the executable "C:\Program Files (x86)\TANDBERG\TMS\TMSProvisioningExtension\app\bin\wrapper-windows-x86-32.exe"
Try this and give us a feedback. =)
I hope this help.
Paulo Souza
Please rate useful replies and remember to mark any solved questions as "answered".

PreSonus Firebox SPDIF input issues

Hello all,
I'm hoping you folks could help me on an issue I've been having with getting the input chain correct to record a SPDIF input signal. I've searched this forum with no other postings found. I've also emailed PreSonus tech support without much luck. The emails I sent are posted below. I'll refrain from posting the replies as they are the property of PreSonus. I'm not looking to bash them. I just want to get on with recording. Please read through them if you feel you could be of help to me.
Thank you,
1st email...
Hello,
I'm an running the following equipment;
PreSonus Firebox
Logic Pro 7.1
Apple 12 inch powerbook running OSX Tiger
Focusrite Voice Master Pro
I recently purchased the digital A/D card with SPDIF for the Focusrite Voice Master Pro (preamp / channel strip). For the life of me, I have not been able to figure out the recording chain for the digital SPDIF input coming from the Focusrite Voice Master Pro. The Firebox manual shows a selection is needed for Windows XP within the Control application. However, non exists for OSX. I'm not a new user to DAW systems. I recently upgraded from a MOTU setup and used SPDIF to / from a DAT recorder without issue. Considering how simple it was to use digital recording with that set up, I know I must be just missing something here. But, after a week of reading the manuals and reading the Logic online forums, I'm still stumped. Please advise and help.
Thank you,
In the reply, I was told I had to download the control app for OSX and select inputs 5-6 within the logic channel strip. I did so and still no go.
2nd email...
Thanks for the reply. I did download the app and tried to use 5-6 input without luck. No signal, bummer. I guess I have more than one issue? I'll have to do some testing by changing cables and running the signal from my DAT player instead of the Focusrite. Maybe I have a bad A/D card on the Focusrite. I'll try running the Focusrite into the DAT as well. Is there any way to test and/or monitor the SPDIF on the Firebox (without Logic) for sync lock and signal? I tried installing the Cubase software included as a test, but I get an error message. So, no go there.
In this reply, I was told I should download the Firebox Mixer and a patch for Cubase. The mixer came with the unit so I really don't see the need to download it unless there's an update. I really don't have a need for Cubase. I just wanted to install it in order to use it as a test.
3rd email...
Hi,
Good news... I was able to send output and record to my DAT player via SPDIF. And, the Focusrite also recorded to my DAT player via SPDIF.
Bad news... No input via SPDIF via the Firebox.
I see that there are many options to route the output signal though the mixer, but no "real" input chain settings. There's a lack meter or peak monitoring on the mixer or the unit. There's no way to be certain the correct sample rate is set and/or received so that I can be sure a digital lock is established. I set Logic to input 5-6. Nothing. I can only assume that when a SPDIF signal is received, it's automatically set to 5-6. Is this correct? If so, something must be wrong with the unit. Perhaps you can tell me (or send me a screen shot of) the correct mixer setting I should be using so that I may test the Firebox.
To be honest, I'm about to trash this unit. I've spent several hours trying to figure what's wrong here. I find the documentation woefully inadequate. It's integration lacking. The fact I had to download the undocumented control software to get the SPDIF capability that was to already to be included with the unit as advertised was not what I was expecting. Partially against other manufactures products I've used. I do appreciate your help in this matter. At the same time, if I have to spend much more effort on this, I'm more likely find myself buying a better box. It will not be a PreSonus.
I sent that email 2 days ago and never got a reply.
I really don't want to buy something else when I'm likely to be just missing something. Please help.
Thanks,
Tim
G4 12inch Powerbook Mac OS X (10.4.4)
G4 12 inch Powerbook Mac OS X (10.4.4)

Well.... I did download that control app and I finally got the SPDIF input working. That's a different version than the 1st control app I was told to download just days before. WHATEVER. I'm a happy guy now. Wheee!!! The funny is/was that's the same download the presonus tech told me was the the mixer app. That's why I didn't download it right away. The 1st couple of times I used it caused some audio shuttering, but then that has gone away. Hopefully, that's not a new issue.
Good luck to all.
Tim

Having An Issue With Site Loading In Firebox

Hello,
I'm having a small issue that I could use some help with. I'm not really sure what is going on, but I'm having an issue with one of the pages from my site not loading when trying to view the page in Firefox. But if I load this page in Safari or Chrome, it loads just fine.
Here's the page URL to take a look: 
Specific link removed from display by moderator ~J99 <sitename>.com/top-10/top...services/

Any idea on why this could be happening or how to fix it? I'm not sure if it's just my computer, or if others are having the same issue.
Thanks in advance,
Mike

Hello Mike,
I have no problem loading and seeing the page <site>.com/top-10/...monitoring-services . General advice would be to try clearing cache and site cookies on the machine you are using.
*see [[Firefox can't load websites but other browsers can]]
I imagine you will have easy access to other machines on which you can test with Firefox so hopefully you will be able to test and demonstrate that the page does normally load on Firefox.
Website design is outside the scope of this forum, but you probably have a professional team working on that.
I did note from <sitenname>.com/disclosure/
<blockquote>Disclosure In regards to the new FTC regulations, we are making this page to be compliant with 100% transparency regarding disclosure of incentive and paid reviews. Every page on this site has been created to generate revenue. This site generates income through banner advertisements and affiliate links on product reviews.</blockquote>

[SOLVED] high CPU and freezing issues

Greetings,
While I don't claim to be an expert at these things, I'm no newbie either... at least as far as computers go. I admit there are still many things I need to learn about linux, but that's all part of the fun. Anyways on to the point of this topic.
After the power supply on my main pc died and shorted out the mother board with it, I have been forced to use an older computer. It is a computer that I know works as it was used by my wife as a desktop when she didn't feel like using her laptop. Odd.. I know, but hey, whatever she wants she gets .
It is an older pc, a compaq presario 5423. It is running an intel p4 1.6 gz processor and has an nvidia geforce 2 mx agp video card. Ever since the last xorg update that refuses to work with nvidia-96xx, I've been using the nv driver. I have tried briefly the other one (nouvelo or however it's spelled) and while it worked it seemed to slow my computer down and produce some odd effects like screen freezes and whatnot. It was running two 256 MB ram sticks, I replaced them with the two 512's from my main (dead) pc. I have the two hd's from my main pc on it, properly set up (I basically resinstalled arch so that I was sure it was done right, and just because I love the arch linux installation process, it is awesome IMO). I've been running this PC since.. October I believe... whenever it was that I submitted that e17 screenshot... I think that was October.
Here is the issue I am having. The CPU loves to max out.. ie.. reach 100% almost instantly. Open up a browser *poof* 100%, making me wait a moment before I can do anything else. Open up a few tabs.. *poof* 100%... and frequent freezes. It doesn't seem to matter what I am running, doing, using... it always happens. This happens in pekwm, fluxbox, openbox, e17, wmaker, firebox, twindy, fvwm, even the almighty awesome. Yes, those are all wm's I've tried. Forget trying to run KDE (I did, it loads... but that's about it. I had to hard restart because of total freeze-up). I've tried all kinds of browsers, firefox, chrome, iron, midori, auroa, konq... Midori hates me, the others are too heavy... only Chrome and Iron (both basically the same) work, but still experience the freezes and the like. Uzbl laughed at me as even trying to start it caused a massive CPU spike. I know, hard to believe.. which leaves me thinking there is a serious problem.
MPD spikes the CPU by 20% easily each song change. Googles even more so. Forget the heavyweights like amarok and exile. Pidgin spikes it when loading initially but evens out. Terminal spikes it only when compiling, updating, or building from AUR... or installing a package with pacman.
Here's the thing, when my wife used it before, using LXDE with Open Box and only a total of 512 MB she never experienced this. This box came with Windows XP which ran fine.. somewhat slow but fine. So this all leaves me thinking, something is just wrong. I am wondering if maybe bad RAM? Maybe the thing is just trying to give up the ghost? Before going and pulling out RAM though I want to see what you guys think.
Here's what HTOP has to say...
CPU(while writing this post): 36.8% (in pekwm!)
Mem: 187/1009 MB (all bars are lite up...)
Swp: 1/2863MB (already tapping into swap?)
Tasks: 128 total, 1 running
Load average: 0.26 0.08 0.06
So yeah, I researched online.. this processor is supposed to be able to even run KDE fine. So something has to be off. Any ideas?
Last edited by mythus (2009-11-20 12:13:53)

Well right before I changed drivers back to nvidia-96xx, I did a pacman -Syu check.. there was a new xorg update waiting for me. So I updated and switched back to nvidia-96xx driver.
Still having the fun CPU issues so this must not be an nv driver thing itself.
free -m provides the following...
total used free shared buffers cached
Mem: 1009 606 403 0 60 387
-/+ buffers/cache: 158 851
Swap: 2863 0 2863
Therefore it would seem that memory issue is not the problem.
Watching the cpu spike just because I type is very unnerving. Heck just running htop did a spike. Poor old computer... Just for S&G I tried once again to load kde. Neopunk killed it with it's massive cpu usage + x trying to match it. What can I say.. X was jealousy, there was no way X was going to let neopunk use more CPU than it.
Ah.. so nerve racking. I've been working on this for almost two months now. I'll look and she what distros I got lieing around.. been awhile since I burned one and not really wanting too.. had no desire since arch is what I want. But I suppose I do need to compare to see if it is something else like X causing this.
I'll do that in a bit.. I'll wait a moment incase anyone else has another suggestion. Give me time to get off my butt and do some honey-do's for my wife.

Problem with Presonus Firebox and Macbook Pro

I own a Presonus Firebox firewire audio inteface, which seems to have a problem with bus power. If I plug in the the firebox using firewire, it is not seen by the OS, and the blue power light flashes faintly. If I then plug in the mains power cord, it works fine. If I then unplug the power cord, it STILL works fine.
This has me beat...if there isn't enough power from the firewire port, how come it manages to stay on after I unplug the mains?
Any help would be greatly appreciated
17" Macbook Pro Mac OS X (10.4.6)

FINALLY someone else has this problem. I was
beginning to feel like the only person in the world!
Thats why I posted as soon as I saw your comments. I was also glad to see I was not alone. I have contacted presonus via email about it. What is the easiest way to contact apple? By phone support? I want to get this problem recognized as high up the ladder as possible, and not have to go the through their usual protocol of trouble shooting that I know wont fix it (i.e. repair permissions, reset pram, ect...).
Also, another thing we should do is post it on presonus's message boards to flag other users with the problem and get this issue into the spotlight so it gets fixed. I thought I saw that presonus has message boards but I could not find them. Please post their link if you know it. MacFix it is another good place that will draw attention to this problem. We should also post there. In addition I am going to email a Mac podcast I listen to about this. I know the host has a 17" MBP. Does this issue effect using external hard drives without AC adapter as well? That way I could have him test this.
Thanks for the work around but I would not even dare attempt that kind of soldering and such do to lack of experience. I'd consider paying you to make me one if you know what your doing and your sure it wont negatively effect anything:)
Paul

Can you please help to understand how the firefox decides on the Expires date for a cached javascript file ( my server did not set any Expire header, but firebox set it down).

# Question
Can you please help to understand how the firefox decides on the Expires date for a cached javascript file ( my server did not set any Expire header, but firebox set it down). I tried to understand but different javascript file gets different Expires date value when it is being cached. Please help me as I tried lot and could not get proper answer for this. Thanks in Advance.

Try posting at the Web Development / Standards Evangelism forum at MozillaZine. The helpers over there are more knowledgeable about web page development issues with Firefox. 
http://forums.mozillazine.org/viewforum.php?f=25 
You'll need to register and login to be able to post in that forum.

Clipping using Firewire Interface Presonus Firebox

Hello, I'm new to this forum and recently just getting acquainted with using GB 2 and my new Presonus Firebox interface, which I acctually bought from reading the recommendations on this forum. So thanks for the suggestions!
My issue is I'm recording my electric bass and acoustic electric guitar (one at a time) and both instruments are clipping during playback. I can't even hear or monitor my playing during recording.
I've attempted adjusting the levels on both the bass and acoustic guitar AND on the Firebox, from low-mid and high AND also in the System Preferences input volume control. Whether I record with low or mid volumes I 'm clipping.
I'm using inputs in the front, lines 1 & 2 for mic/instrument. I've even tried using the rear inputs 3 & 4 but I don't even get a reading. I must be doing something wrong.
So I wonder if this has anything to do with the kind of cables I'm using for recording. Or my computer's speed and memory. I'm using an iMac G4 from a few years back.
Previously, I was using my old Powerbook G4 for recording, also from a few years back, and I did NOT get any clipping when I recorded my acoustic electric guitar, but I did have to raise the levels on the guitar AND on the Firebox - almost to the max! - to get a decent volume recorded.
Please help! I'm still getting acquainted with all this techy stuff. Thanks in advance
imac Mac OS X (10.3.9)

I can't even hear or monitor my playing during recording.
You should be able to listen to (monitor) the tracks. Double click on the instrument icon on the track and from the monitor pulldown menu select 'on'. Monitoring is off by default.
As far as levels, don't worry about the main level. It can clip in the recording stage. Worry about the individual track levels. You may not be able to get them into the yellow but at least get them as high in the green as possible.
You have a number of gains to play with. My suggestion is to leave the system gain on its default setting. Play with the gains on your guitars (if you have any) and the Presonus. There is usually a track gain and a main gain. Put the main on about 1/2 and then adjust the track gain. If this creates too much background noise do the opposite. Every interface is different so you may need to play with it.
Note that the harder you strum the more volume goes to your mic so in setting up the levels make sure you are strumming as hard as you would in the loudest part of the piece. This will give you your top level.
If you are clipping slightly and occasionally it might be all right. I have had several recording go slightly into the red with no digital clipping. There may be a little wiggle room in Garageband's meters.
The main meter is a different story. All tracks combine together, some frequencies are identical which may boost that frequency more so you end in the red a lot. Most of us use some sort of compression to control this. You want the signal high but don't want it to clip.
The best plugin for beginners is the C3 Multi Band Compressor 1.2. It comes with a mess of presets. The mastering presets are particularly useful for your master track. You can download it here. Follow the directions to install it.
Here is a goofy thing. Garageband defaults to hiding the Master track. This is plain silliness because you need to mess with the Master track to get your final product done. In Garageband press ⌘ +b to see the master track. Double click on the master track and you will see pulldown menus that you can select various plugins. This is where you would use the C3 plugin mentioned above. Plugins used in the master track pulldown menus apply to all tracks.
This is a great page to learn more about garageband basics:
Apple - Support - GarageBand
Kurt

Optimising Performance with Firebox

I had a look over some of the discussions recently as I was having a few issues with the Presonus Firebox I bought last week. Thanks to helpful advice given to someone else, I was able to resolve the problems with digital crackling. I breathed a sigh of relief that I hadn't wasted my money!
I recorded a few pieces, nothing more two guitar tracks, to test it out. It sounded great. However, this morning I got up to start recording something and I've been having problems with the recording being stopped and the "Too Many tracks, effects, etc, try... Optimising Performance" box coming up.
I concede that my computer isn't the most powerful of the current range, but I am only recording one track of audio and that's it. There are no other tracks playing or even muted.
The set-up/arrangements is currently as follows:
The Firebox is going into the PowerBook and there's a 200GB La Cie external hard drive daisy-chained off the back of it. The only applications running are GB (2.02 or whatever the latest is), the two Firebox mixer and control applications, err, Airport (I could turn this off) and Bluetooth as I'm using a Bluetooth mouse so I can sit to one end of the room and isolate external noise away from the computer.
I've followed the standard GB advice on optimising. I've made sure settings in Energy Saver are set for highest performance. I've even tried changing to built-in audio for output (which I'm not listening to anyway as I play), but this seems to make no difference. All effects are switched off.
The problem doesn't appear consistent. Sometimes the recording stops after a few bars, sometimes it manages three minutes before halting. Agh! It's not really the sort of guitar piece that I can edit together from pieces and until I get this part down, I can't start on the rest as I'm not playing against any click track so that the tempo flows more freely over the course of the piece. Playing a five-minute piece and thinking you've finally got it without any fluffs, only to look up and see "Optimising Performance" from across the room is exasperating!!
I've never had any such issues with GB using built-in audio for similar. It can handle four audio tracks with limited effects quite readily. I tend to mix these down to one track and reimport them into a new one at this point.
There's a pressing need to get this guitar track done for a friend. Once the acoustic part is in, I really don't have any need for the Firebox as such. I could go back to using the old mic set up (a rather antique Sony mic rescued from a rubbish bin in Tokyo and using a MiniDisc as sort of pre-amp) but it's noisy and the sound isn't nearly as good as the new microphone. When the recording works, that is!
I imagine it's possible (is it?) to directly connect the audio output of the Firebox to the mic input on the computer and thus stick to built-in audio, but I'm sure that using Firewire should work. I'm hardly overloading anything currently.
Any suggestion or tips would be most gratefully listened to!

I think you may well be right and the computer isn't currently sufficient, but it does seem odd to me that it can't even handle one single track of audio with the Firebox connected via Firewire. I could understand five or six. Since the only thing that has changed in the set-up is the switch from built-in audio to the Presonus, it has to be that. Or rather, as you say, the computer being unable to deal with it adequately with the current RAM.
I'd lock the tracks but there is only one of them!
(Looks at credit card statement and wonders about upgrading..!)
Thanks.

Issues connecting to FTP sites from OS/X Computers

Hello,
I have a network that is mixed with Windows and OS/X Lion, Snow Leopard machines. We access external FTP servers to download files that are needed. None of my OS/X machines are able to connect to the FTP servers while all of my Windows machines are able to without a problem. What is even more strange is that if I attemp to connect to the server using a port such as 221 instead of 21, waiting for it to fail, and then connecting on 21, it works.
Our network is using private ip addresses and the firewall is a Firebox appliance.
Any ideas?
Here is a log from terminal ftp:
ftp> open ediftp.XXXXXXXXX.com
Connected to ediftp.XXXXXXX.com.
220 Gene6 FTP Server v3.10.0 (Build 2) ready...
Name (ediftp.XXXXXXX.com:jim): USERNAME
421 Service not available, remote server has closed connection.
ftp: Login failed
ftp>
And here is the log from Filezilla that shows a connection when using the invalid port trick:
Status:          Resolving address of ediftp.xxxxxxx.com
Status:          Connecting to xxx.xx.xxx.xxx:21...
Status:          Connection established, waiting for welcome message...
Response:          220 Gene6 FTP Server v3.10.0 (Build 2) ready...
Command:          USER xxxxx
Error:          Could not read from socket: ECONNRESET - Connection reset by peer
Error:          Could not connect to server
Status:          Waiting to retry...
Status:          Resolving address of ediftp.xxxxxxx.com
Status:          Connecting to xxx.xx.xxx.xxx:221...
Error:          Connection attempt interrupted by user
Status:          Delaying connection for 1 second due to previously failed connection attempt...
Status:          Resolving address of ediftp.xxxxxxx.com
Status:          Connecting to xxx.xx.xxx.xxx:21...
Status:          Connection established, waiting for welcome message...
Response:          220 Gene6 FTP Server v3.10.0 (Build 2) ready...
Command:          USER xxxxxx
Response:          331 Password required for xxxxxx.
Command:          PASS **********
Response:          230 User xxxxxxx logged in.
Command:          SYST
Response:          215 UNIX Type: L8
Command:          FEAT
Response:          211-Extensions supported:
Response:           AUTH TLS
Response:           CCC
Response:           CLNT
Response:           CPSV
Response:           EPRT
Response:           EPSV
Response:           MDTM
Response:           MFCT
Response:           MFMT
Response:           MLST type*;size*;create;modify*;
Response:           MODE Z
Response:           PASV
Response:           PBSZ
Response:           PROT
Response:           REST STREAM
Response:           SIZE
Response:           SSCN
Response:           TVFS
Response:           UTF8
Response:           XCRC "filename" SP EP
Response:           XMD5 "filename" SP EP
Response:           XSHA1 "filename" SP EP
Response:          211 End.
Command:          CLNT FileZilla
Response:          200 Noted.
Command:          OPTS UTF8 ON
Response:          200 UTF8 OPTS ON
Status:          Connected
Status:          Retrieving directory listing...
Command:          PWD
Response:          257 "/" is current directory.
Command:          TYPE I
Response:          200 Type set to I.
Command:          PASV
Response:          227 Entering Passive Mode (173,56,68,239,115,193)
Command:          MLSD
Response:          150 Data connection accepted from xx.xx.xxx.xxx:37545; transfer starting.
Response:          226 Transfer ok.
Status:          Directory listing successful
Jim

this is most likely a local firewall issue on the the Vista computer combined with your NAT not doing hairpinning. please see Matthew Kaufman's detailed treatment of the NAT/firewall issue at
   http://forums.adobe.com/message/1064983#1064983

Using Presonus Firebox with Garageband

I have a Presonus Firebox and I'd like to use it to record in garageband but I can't seem to get my microphone to pick up in garageband. It's hooked to the front on #1, the computer is hooked to the interface via firewire and my keyboard is connected to the interface as well. My keyboard is showing in garageband but I don't know how to get it on a track as well as my microphone. Someone please help! Thank You!

I don't know if you're experiencing the same problem I've been having using both a MOTU 828 firewire interface and Presonus Firebox. Take a look at the thread "GB and MOTU 828".
If it turns out you are having similar problems it would be great for you to give Presonus a call just to let them know you're having the problem. The more calls they can log the better chance that a fix from Apple will be forthcoming. I'm pretty sure it's not just a Presonus issue since my MOTU box had the same problem.
If you discover a fix I'd love to hear what it is. Unfortunately, at the moment I can't offer any help to you. I'm in the same (or similar) boat.

Presonus Firebox problem: I can see the audio levels but can't hear. Help!

Searched in the forums to what I think is a basic issue, but couldn't find anyone with an answer...
I have audio routed into my firebox from an external mixer. I can see the audio meter in the "in" sound panel of system preferences moving but I can't hear sound coming out of my soundsticks.
Audio routed out of my computer into external amp/stereo setup is audible, however.
Can anyone help me figure this out so I can move and and start setting Firebox up with Logic? LOL
My hardware specs (I'm running 10.4.11):
Hardware Overview:
Machine Name: Power Mac G4
Machine Model: PowerMac3,5
CPU Type: PowerPC G4 (2.1)
Number Of CPUs: 2
CPU Speed: 800 MHz
L2 Cache (per CPU): 256 KB
L3 Cache (per CPU): 2 MB
Memory: 1.5 GB
Bus Speed: 133 MHz
Boot ROM Version: 4.2.5f1
Serial Number:
Sales Order Number:

Your memory serves you well.
Yes, line outs from the mixer are hooked up to line ins 3&4 on the back of the firebox. What I can't figure out is that the Sound Panel of System Preferences shows a good input level, whereas the meter in Logic shows nothing (rec is enabled and blinking). If I switch cables to the 1&2 instrument ins on the front of the Firebox, I get levels in both Sys Prefs and Logic. I'm thinking, the problem can't be the Firebox, because the computer sees the signal either way. I'm running Logic 6.0 Platinum BTW.
I find Presonus and their manual to be lacking. They take days to write back with curt responses... Either they don't have enough people or the Firebox is not expensive enough for them to devote to customer service... I don't know

Yosemite - Managed Accounts Network Issues

I have an iMac mid 2011 (wow - doesn't time fly!) with several Managed Accounts for each of my children. However since updating to Yosemite, their accounts have very temperamental internet connectivity. However, if i fast switch to my standard account, the internet is working fine - switch back and their accounts still don't work.
I have upgraded /their accounts to Standard users and they now allow internet access.
I tried turning off the Apple network protection (i.e. to limit access to inappropriate sites etc) before using the nuke option but that didn't work.
I also manually set the DNS - no effect.
I did notice that the accounts could access the local LAN, just not the internet.
I use an Airport Time Capsule connected to a Firebox 7940 router which has been (until now) a great combo.
Does anyone have any ideas what happened?
How to fix this so that I can re-enable parental controls?
Kind regards,

Temporary resolve the https: site accessing issue for parental controlled account is to disable parental control.
For past a few weeks, my kids started abusing their computer time since there was no parental control anymore. I really need to get the parenting control back and get the situation under control.
I was planning to down grade Yosemite back to Mavericks and started backing up all files for each user account. Last night, unexpectedly I notice that Yosemite 10.10.1 is ready, so I figured to give it a try even it did not mention parental control issue. After install this pitch, I restored parental control for all my kids’ account. It seems resolved the issue.

Firebox issues

Similar Messages

Maybe you are looking for