Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - sentinel

Pages: [1]
Articles / Re: Routing signals directly to SignalScope using Soundflower
« on: January 12, 2010, 12:27:11 AM »
I installed and was using SoundSource before I started having issues with SignalScope. I'd set SoundSource 'Input' to Soundflower and then set SignalScope's input to the same, so that's why I asked earlier about how SignalScope handles inputs, I wonderd if I'd used SignalScope to override something which caused this issue. I have noticed that if I go to Device I/O, that both 'Line In' and 'Soundflower' are switched on. I'd also selected Soundflower as SignalScope's output when Soundflower was working correctly, but I remember that SignalScope's output was selected to 'Built-In Audio' when I was having issues.

I'll have a further poke at this later on, see if I can pin a sequence of events down.

Edit: after poking, I found that if I start SignalScope Pro directly (i.e. by not calling my saved project), then select Soundflower as my output via SoundSource and Soundflower as SignalScope Pro's input, i.e. *not* a system-wide input via SoundSource, then I get my signal. When I look at Device I/O, I notice this:

- In my saved project, when I start it, both 'Line in' and 'Soundflower' are turned on.
- In the new project, only 'Line in' or 'Soundflower' is turned on, depending on the selected input on the main control panel.

Edit2: In my saved project, 'Line in' and 'Soundflower' are both activated only if 'Soundflower' is the selected input.

Articles / Re: Routing signals directly to SignalScope using Soundflower
« on: January 10, 2010, 03:00:10 AM »
Hi Ben,

Sorry for not responding quickly, I thought I had set this to email me if someone responded.

To answer your questions:
1. Yes
2. 10.5.8
3. I have SoundSource (from Rogue Amoeba) to help me switch between inputs and outputs. Normally yes, Line Out would be my default output, but SoundSource can change this. An example: if I use SoundSource to switch from Line Out to Soundflower and then restart, Soundflower is selected as the 'default' output upon reboot.
4. Yes
5. 44.1kHz
6. No

A note: I had used Soundflower for this task before and it worked, so I'm not sure what changes I made broke it.

Articles / Re: Routing signals directly to SignalScope using Soundflower
« on: January 02, 2010, 04:24:53 PM »

I've been looking at this a bit more. I have restarted the computer, set up Soundflower so that it is sending signals correctly (confirmed with LineIn from Rogue Amoeba), then started my project. I had previously saved it so that inputs and outputs were set to 'Built-in Audio'. As soon as Signalscope starts, there is a double-pop from my speakers and the sound fades. How does Signalscope interact with inputs and outputs?

Articles / Re: Routing signals directly to SignalScope using Soundflower
« on: December 31, 2009, 09:46:21 PM »

I'm using Soundflower 1.5.1 to run signals from Quicktime Player 7.6.4 to Signalscope Pro 2.1.5. I have had an intermittent problem where I can no longer get a signal to Signalscope through Soundflower (line-out works fine). I recently did the following: started Quicktime, selected Soundflower (2ch) as output and tested OK, then started Signalscope via a saved project - and Soundflower cut out. The standard fix for this (so far) is a restart of the computer (a PowerPC G5 iMac).

Would anyone be able to help out at all?

SignalScope Pro / Length of capture
« on: December 28, 2008, 09:26:32 PM »

I'm using SignalScope Pro to analyse the noise from a process which continues for at least 12 minutes. I previously used SignalScope 1.8.4, where I could record a spectrogram for 15 minutes. Is there any way I could record a spectrogram for longer than the current 20 seconds?

Pages: [1]