[Chris Forsyth]

Aah ok – that is one more thing I will try when I get back to the studio.

Thanks

[Chris Forsyth]

Hey John,
Yes – am using the ASIO drivers.
And Presonus also has that type of applet – and the weird thing is – when I have the focus on the Presonus UI applet, I can change it manually to 48k, and it takes, but the minute I put the focus on the Vegas window – it switches the sample rate in the presonus applet back to 44k. Thats why I thought it might be a setting somewhere inside Vegas that I needed to change, since it seemed that putting the focus on Vegas was switching the firestudio to 44k – as if Vegas was calling for 44k.

Thanks

[Chris Forsyth]

I know what you mean about not being sure if you could use the computer this way – I thought the same thing when I was told to do that years ago – but I did it – and honestly have never missed it, and now have gotten so used to it than when i use my laptop the windows sounds actually annoy me 🙂

Anyway – thats a great suggestion (deselecting it as the default device). I’ll give that a shot – and if that doesn’t work, I’ll try enabling the on board device also to see if that fixes things.

Thanks for the insight and suggestions.

Best,
Chris

Thanks

[Chris Forsyth]

Ok, I see.
So if (as in earlier post) I have windows sounds disabled, I guess I could simply enable the on board sound chip, and not worry about hooking up speakers (if I leave Windows sounds disabled from within windows), and this should take care of the problem? I’ll give that a try when I get back to the studio.

Thanks

[Chris Forsyth]

Hi John:
Does it make a difference that I have system sounds disabled from within windows? (I thought this was standard practice). Set up this way, would windows ever have to switch to 44k to do anything?

Thanks

[Chris Forsyth]

Hi John,
I am indeed using the PSFS as the default device, and in fact have disabled the MB soundchip. I did that on the recommendation of either Presonus or Cakewalk (I use Sonar Producer for Audio) – I can’t remember which company told me to do that – probably Cakewalk. Whoever it was, said that “not disabling the onboard audio could cause conflicts and problems”.

That’s the way it’s always been, but maybe that is no longer an issue – and maybe I should re-enable the onboard audio.

Then again, I have my studio monitors hooked up through the Firestudio – so even using the on-board chip I don’t have any output for the audio… so I guess I’d need two separate audio setup’s?

Thanks

[Chris Forsyth]

I have the FS Project – not sure how different that is from the 26×26.
I did check the Firmware – one of the first things I did actually – hoping that would be a problem – but alas – it is current.

I haven’t checked drivers in a month or so – maybe there are new drivers.

Thanks

[Chris Forsyth]

Yes I did.
That is SO strange that you’d have to use legacy drivers!
Is presonus aware of this do you know?

Thanks

[Chris Forsyth]

Aah…good to know…I’ll render one out at that bitrate and see what that gives me in file size. I’ve never uploaded anything to YouTube, so I don’t know if there are any file size limitations. I’m guessing that the larger the file size, the longer the buffering time for the viewer?

Best,

Chris Forsyth

[Chris Forsyth]

John:

BINGO!!!
That did it!
Cant thank you enough.

Funny thing is, just using the default settings for that render option resulted in a 287MB file, vs the 87MB file that I started with. Maybe the default bitrate of 6mbps makes it that big? Not sure what it is – but the playback works wonderfully! Thanks so much again John.

Best,

Chris Forsyth