search

dipunumber2 / soundflower

Automatically exported from code.google.com/p/soundflower
GNU General Public License v2.0
0 stars 0 forks source link

soundflower 64 channel and protools 10 #191

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Using SF64 alone or part of an aggregate causes protools to crash on launch 
using 0sx10.8.2
2.
3.

What is the expected output? What do you see instead?
Using SF2channel works fine so i assume a 64 channel problem with PT - which is 
likely as PT is restricted to 32 but usually just ignores any more

What version of the product are you using? On what operating system?
latest 1.66b and osx 10.8.2

Please provide any additional information below.
Though I guess its not directly a SF problem I wondered if anyone had it working

Original issue reported on code.google.com by mickb...@gmail.com on 17 Mar 2013 at 2:33

GoogleCodeExporter commented 9 years ago 
I

Original comment by mickb...@gmail.com on 17 Mar 2013 at 2:39

GoogleCodeExporter commented 9 years ago 
I forgot to mention I found a workaround returning to SF1.5.2 with only 16 
channels
which seems to be stable though is not recommended for use with with 10.8.2

Original comment by mickb...@gmail.com on 17 Mar 2013 at 2:40

GoogleCodeExporter commented 9 years ago 
Anyway to change soundflower 64ch to 16ch?

Original comment by ggenar...@yahoo.com on 6 Apr 2013 at 1:14

GoogleCodeExporter commented 9 years ago 
I did some more tests and found the  64ch SF to work in protools now but any 
aggregate devices using it still crashed protools - so maybe its an aggregate 
problem. The older 16 ch version still works fine

Original comment by mickb...@gmail.com on 6 Apr 2013 at 1:33

GoogleCodeExporter commented 9 years ago 
Go to your Library/Preferences folder on your HD. Right click on your 
Preference folder and choose "Get info". Go down to sharing and permissions and 
set "everyone" to "Read & Write". You will then be able to use your aggregate 
device with soundflower 64ch in Pro Tools 10, without any crashes.

Original comment by carlospv...@gmail.com on 25 Apr 2013 at 9:54

GoogleCodeExporter commented 9 years ago 
Cheers for this what interface are you aggregating with this solution. Ive just 
tried it on both libraries permissions and using my metrichalouln8 and SF 1.66 
with 64 channels as an aggregate and protools still quits on launch with that 
aggregate device. Protools10 does have a 32 channel limit but it will launch 
using SF64 alone and using SF64 aggregated with the 2 channel internal device 
though it will of course only access the first 32 which id expect.  This does 
contradict other reported problems with any aggregate device over 48 channels 
but doesnt tell me where the problem lies and im back again to the 1.52 SF16 
channel.

Original comment by mickb...@gmail.com on 26 Apr 2013 at 12:23

GoogleCodeExporter commented 9 years ago 
Unfortunately I am not able to test this out with an interface at the moment. I 
just tried to add the built-in inputs, and you are correct; it does crash. On 
the Audio Midi Setup I have only soundflower 64ch and built-in outputs selected.

Original comment by carlospv...@gmail.com on 26 Apr 2013 at 2:39

GoogleCodeExporter commented 9 years ago 
Hi, Soundflower has run fine with ProTools 10.3.8, but now not more on ProTools 
11.3. The SF driver is recognized and the routing can be done, but the audio is 
distorted like running without a clock. This issue happen only in ProTools 
aggregate, using the Build-in device + Soundflower64, not using only 
Soundflower as main audio interface. 
I've tryed that with the same session, same I/O routing, on PT 10.3.8 and PT 
11.3. The first one is ok.
best regards
Italo

Original comment by keepsoun...@gmail.com on 21 Dec 2014 at 1:01

GoogleCodeExporter commented 9 years ago 
Ive recently moved along to Mavericks and cant even get PT11 working as an 
aggregate with SF64 and BuiltIn output but
as it always crashed PT with SF64 and MultiInterfaces as an aggregate I did 
sort of give up on it.  I did get SF64
working alone and using SoundflowerBed you can route protools to the builtin 
output.

I have gone back to SF16 again v 1.52 which does work in aggregates  in 
protools 11.3 and have used it for long periods of time
when i need SF64 for something I'll just have to uninstall and reinststall 

mick

Comment #8 on issue 191 by keepsoun...@gmail.com: soundflower 64 channel and 
protools 10
https://code.google.com/p/soundflower/issues/detail?id=191

Hi, Soundflower has run fine with ProTools 10.3.8, but now not more on ProTools 
11.3. The SF driver is recognized and the routing can be done, but the audio is 
distorted like running without a clock. This issue happen only in ProTools 
aggregate, using the Build-in device + Soundflower64, not using only 
Soundflower as main audio interface.
I've tryed that with the same session, same I/O routing, on PT 10.3.8 and PT 
11.3. The first one is ok.

Original comment by mickb...@gmail.com on 23 Dec 2014 at 8:59

GoogleCodeExporter commented 9 years ago 
I'm on Mavericks, trying SF 1.6.6 (the installer is called 1.6.6b, i think, but 
the app file is named 1.6.6..???)

Reaper output to Aggregate Device of H4 interface (1xIn/1xOut and clock master) 
&  SF 2ch (1xIn/1xOut & Resample). System prefs In/Out -H4, and SF setup 2ch - 
H4.

2ch works ok for audio out from Cubase Elements 7 (Audio Device SF2ch) into 
Reaper

64 channel is the only other option with this version of SF, and it either 
crashes OS Audio SetUp, or I get noise/distortion of unusable proportions.

NB I don't know how I should be setting it up.

Original comment by je...@playtomusic.co.nz on 24 Dec 2014 at 12:20