Only noise in v.o. tool with MBox

I recently upgraded to a Mac Pro and I installed Final Cut Studio (Universal) and all the available upgrades. I have an MBox 1 with ProTools LE and Digi CoreAudio Manager 7.1.1 installed.
In ProTools the MBox works fine.
Today I tried to use the Voice Over Tool with the MBox in Final Cut Pro. When I switch the input to the MBox the input level shoots up to 0 dB and over, even if i disconnect the mike (input 1) and turn the gain down to zero.
If I record to the timeline I get only noise up to exactly -6 dB.
There's no settings in the Digi CoreAudio Manager that have any effect, the audio settings in System Preferences don't seem to matter... So what's wrong? All devices are set to record/play 48 kHz.
In my previous setup (G4) this configuration never failed....
Mac Pro 2.66 GHz Mac OS X (10.4.8) 2 Gb RAM, ATI Radeon X1900 XT, Sony DSR-11, FCP 5.1.1
Mac Pro 2.66 GHz Mac OS X (10.4.8) 2 Gb RAM, ATI Radeon X1900 XT, Sony DSR-11, FCP 5.1.1

You should ground reference all floating signals for this module as stated in the User's Manual.
Justin
National Instruments
Product Support Engineer - Conditioned Measurements

Similar Messages

GB vs. Pro Tools With Mbox or Apogee Duet 2 and Neumann TLM 102

Any guidance on this is greatly appreciated....I am VO artists really being forced into home recording. Can not do a USB Mic into the MBP as the sound is not professional enough. But I do use GB. Based on that, and the fact I only record my voice, I have a series of questions
First question: I'm thinking of getting Apogee Duet 2 as opposed to an Mbox. Any opinion? The Mbox comes with Pro Tools
Second question: Is Pro Tools better software than GB? Remember this is for voice-over work.
Third question: Has anyone out there used either the Apogee Duet 2 or Mbox with a Neumann TLM 102 mic? Do you hear a difference between Apogee Duet 2 and Mbox with the Neumann?
Forth question: If you were in my shoes, and just wanted a super duper VO sound, should I be looking at something other than mBox and Apogee?
Again, to be clear: I'm not recording instruments, so I don't need a lot of bells and whistles...just great, and I mean great sound quality...
Thanks so much
Oh....real important...running OS 10.7.4 if that affects the above... I alos know 10.7.4 is getting upgraded ( spoke to Apple) because of the QT Pro 7 problems, amongst others

Go with the Duet 2, no question. You'll hear the difference...
Pro Tools and GarageBand are both great apps, its really a question of what your'e trying to do with it. Unless there's anything you're trying to do but can't do in GarageBand, there's no real advantage to Pro Tools for what you're doing.
Apogee has always been a "no bells and whistles" company - it simply works and sounds great.
Hope this helps!

Problems with OSS (ALC1200, one speaker only noise)

Hi, im trying to use OSS since a half year, but never got it up running. There is always only noise/scrappy sound on the right front speaker and on the same time on the right Headphone speaker. In OSS test it says ok when testing. Devices are /dev/oss/oss_hdaudio0/pcm0 when this occures the first time, and /dev/oss/oss_hdaudio0/spdout at the second time.
Card is the ALC1200 onboard-chip of the Asus P5Q. Its is recognised by alsa & oss as ALC888, and normally working in alsa.
ossinfo -v3 -a :
HD Audio play front /dev/oss/oss_hdaudio0/pcm0 (device index 0)
Legacy device /dev/dsp0
Caps: DUPLEX TRIGGER MMAP
Modes: IN/OUT
Out engine 1: 0/HD Audio play front
Available for use
Engine 2: 9/HD Audio play front (vmix)
Available for use
Engine 3: 10/HD Audio play front (vmix)
Available for use
Engine 4: 11/HD Audio play front (vmix)
Available for use
Engine 5: 12/HD Audio play front (vmix)
Available for use
Input formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Output formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Device handle: PCI82fe1043-0000:00:1b.0-au01
Related mixer dev: 0
Sample rate source: 0
Preferred channel configuration: Not indicated
Supported number of channels (min - max): 2 - 8
Native sample rates (min - max): 44100 - 192000 (44100,48000,96000,192000)
HW Type: Not indicated.
Minimum latency: Not indicated
HD Audio play rear /dev/oss/oss_hdaudio0/pcm1 (device index 1)
Legacy device /dev/dsp1
Caps: TRIGGER MMAP
Modes: OUTPUT
Out engine 1: 1/HD Audio play rear
Available for use
Input formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Output formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Device handle: PCI82fe1043-0000:00:1b.0-au02
Related mixer dev: 0
Sample rate source: 0
Preferred channel configuration: Not indicated
Supported number of channels (min - max): 2 - 2
Native sample rates (min - max): 44100 - 192000 (44100,48000,96000,192000)
HW Type: Not indicated.
Minimum latency: Not indicated
HD Audio play center/LFE /dev/oss/oss_hdaudio0/pcm2 (device index 2)
Legacy device /dev/dsp2
Caps: TRIGGER MMAP
Modes: OUTPUT
Out engine 1: 2/HD Audio play center/LFE
Available for use
Input formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Output formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Device handle: PCI82fe1043-0000:00:1b.0-au03
Related mixer dev: 0
Sample rate source: 0
Preferred channel configuration: Not indicated
Supported number of channels (min - max): 2 - 2
Native sample rates (min - max): 44100 - 192000 (44100,48000,96000,192000)
HW Type: Not indicated.
Minimum latency: Not indicated
HD Audio play side /dev/oss/oss_hdaudio0/pcm3 (device index 3)
Legacy device /dev/dsp3
Caps: TRIGGER MMAP
Modes: OUTPUT
Out engine 1: 3/HD Audio play side
Available for use
Input formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Output formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Device handle: PCI82fe1043-0000:00:1b.0-au04
Related mixer dev: 0
Sample rate source: 0
Preferred channel configuration: Not indicated
Supported number of channels (min - max): 2 - 2
Native sample rates (min - max): 44100 - 192000 (44100,48000,96000,192000)
HW Type: Not indicated.
Minimum latency: Not indicated
HD Audio play pcm4 /dev/oss/oss_hdaudio0/pcm4 (device index 4)
Legacy device /dev/dsp4
Caps: TRIGGER MMAP
Modes: OUTPUT
Out engine 1: 4/HD Audio play pcm4
Available for use
Input formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Output formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Device handle: PCI82fe1043-0000:00:1b.0-au05
Related mixer dev: 0
Sample rate source: 0
Preferred channel configuration: Not indicated
Supported number of channels (min - max): 2 - 2
Native sample rates (min - max): 44100 - 192000 (44100,48000,96000,192000)
HW Type: Not indicated.
Minimum latency: Not indicated
HD Audio play spdif-out /dev/oss/oss_hdaudio0/spdout0 (device index 5)
Legacy device /dev/dsp5
Caps: TRIGGER MMAP
Modes: OUTPUT
Out engine 1: 5/HD Audio play spdif-out
Available for use
Input formats (0x00001410):
AFMT_S16_LE - 16 bit signed little endian
AFMT_AC3 - AC3 (Dolby Digital) encoded audio
AFMT_S32_LE - 32 bit signed little endian
Output formats (0x00001410):
AFMT_S16_LE - 16 bit signed little endian
AFMT_AC3 - AC3 (Dolby Digital) encoded audio
AFMT_S32_LE - 32 bit signed little endian
Device handle: PCI82fe1043-0000:00:1b.0-au06
Related mixer dev: 0
Sample rate source: 0
Preferred channel configuration: Not indicated
Supported number of channels (min - max): 2 - 2
Native sample rates (min - max): 44100 - 192000 (44100,48000,88200,96000,192000)
HW Type: Not indicated.
Minimum latency: Not indicated
HD Audio play spdifout /dev/oss/oss_hdaudio0/spdout1 (device index 6)
Legacy device /dev/dsp6
Caps: TRIGGER MMAP
Modes: OUTPUT
Out engine 1: 6/HD Audio play spdifout
Available for use
Input formats (0x00001410):
AFMT_S16_LE - 16 bit signed little endian
AFMT_AC3 - AC3 (Dolby Digital) encoded audio
AFMT_S32_LE - 32 bit signed little endian
Output formats (0x00001410):
AFMT_S16_LE - 16 bit signed little endian
AFMT_AC3 - AC3 (Dolby Digital) encoded audio
AFMT_S32_LE - 32 bit signed little endian
Device handle: PCI82fe1043-0000:00:1b.0-au07
Related mixer dev: 0
Sample rate source: 0
Preferred channel configuration: Not indicated
Supported number of channels (min - max): 2 - 2
Native sample rates (min - max): 44100 - 192000 (44100,48000,88200,96000,192000)
HW Type: Not indicated.
Minimum latency: Not indicated
HD Audio rec mix /dev/oss/oss_hdaudio0/pcmin0 (device index 7)
Legacy device /dev/dsp7
Caps: DUPLEX TRIGGER MMAP
Modes: IN/OUT
In engine 1: 7/HD Audio rec mix
Available for use
Engine 2: 9/HD Audio play front (vmix)
Available for use
Engine 3: 10/HD Audio play front (vmix)
Available for use
Engine 4: 11/HD Audio play front (vmix)
Available for use
Engine 5: 12/HD Audio play front (vmix)
Available for use
Input formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Output formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Device handle: PCI82fe1043-0000:00:1b.0-au08
Related mixer dev: 0
Sample rate source: 0
Preferred channel configuration: Not indicated
Supported number of channels (min - max): 2 - 2
Native sample rates (min - max): 44100 - 96000 (44100,48000,96000)
HW Type: Not indicated.
Minimum latency: Not indicated
HD Audio rec mix /dev/oss/oss_hdaudio0/pcmin1 (device index 8)
Legacy device /dev/dsp8
Caps: TRIGGER MMAP
Modes: INPUT
In engine 1: 8/HD Audio rec mix
Available for use
Input formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Output formats (0x00001010):
AFMT_S16_LE - 16 bit signed little endian
AFMT_S32_LE - 32 bit signed little endian
Device handle: PCI82fe1043-0000:00:1b.0-au09
Related mixer dev: 0
Sample rate source: 0
Preferred channel configuration: Not indicated
Supported number of channels (min - max): 2 - 2
Native sample rates (min - max): 44100 - 96000 (44100,48000,96000)
HW Type: Not indicated.
Minimum latency: Not indicated
/dev/dsp -> /dev/oss/oss_hdaudio0/pcm0
/dev/dsp_in -> /dev/oss/oss_hdaudio0/pcm0
/dev/dsp_out -> /dev/oss/oss_hdaudio0/pcm0
/dev/dsp_ac3 -> /dev/oss/oss_hdaudio0/spdout0
/dev/dsp_mmap -> /dev/oss/oss_hdaudio0/pcm0
/dev/dsp_multich -> /dev/oss/oss_hdaudio0/pcm0
ossmix:
Selected mixer 0/High Definition Audio ALC888
Known controls are:
jack.green.mode <front|rear|center/LFE|side|pcm4|input> (currently front)
jack.green [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.green.mute ON|OFF (currently OFF)
jack.black.mode <front|rear|center/LFE|side|pcm4|input> (currently rear)
jack.black [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.black.mute ON|OFF (currently OFF)
jack.orange.mode <front|rear|center/LFE|side|pcm4|input> (currently center/LFE)
jack.orange [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.orange.mute ON|OFF (currently OFF)
jack.gray.mode <front|rear|center/LFE|side|pcm4|input> (currently pcm4)
jack.gray [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.gray.mute ON|OFF (currently ON)
jack.pink.mode <front|rear|center/LFE|side|pcm4|input> (currently input)
jack.pink [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.pink.mute ON|OFF (currently ON)
jack.fp-pink.mode <front|rear|center/LFE|side|pcm4|input> (currently input)
jack.fp-pink [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.fp-pink.mute ON|OFF (currently ON)
jack.blue.mode <front|rear|center/LFE|side|pcm4|input> (currently input)
jack.blue [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.blue.mute ON|OFF (currently ON)
jack.fp-green.mode <front|rear|center/LFE|side|pcm4|input> (currently front)
jack.fp-green [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.fp-green.mute ON|OFF (currently OFF)
record.mix.mute.mic1 ON|OFF (currently ON)
record.mix.mute.fp-mic1 ON|OFF (currently ON)
record.mix.mute.linein1 ON|OFF (currently ON)
record.mix.mute.fp-headphone1 ON|OFF (currently ON)
record.mix.mute.green1 ON|OFF (currently ON)
record.mix.mute.black1 ON|OFF (currently ON)
record.mix.mute.orange1 ON|OFF (currently ON)
record.mix.mute.gray1 ON|OFF (currently ON)
record.mix.mute.input-mix1 ON|OFF (currently ON)
record.mix1 [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
record.mix.mute.mic2 ON|OFF (currently ON)
record.mix.mute.fp-mic2 ON|OFF (currently ON)
record.mix.mute.linein2 ON|OFF (currently ON)
record.mix.mute.fp-headphone2 ON|OFF (currently ON)
record.mix.mute.green2 ON|OFF (currently ON)
record.mix.mute.black2 ON|OFF (currently ON)
record.mix.mute.orange2 ON|OFF (currently ON)
record.mix.mute.gray2 ON|OFF (currently ON)
record.mix.mute.input-mix2 ON|OFF (currently ON)
record.mix2 [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.mic [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.fp-mic [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.linein [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.fp-headphone [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.green [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.black [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.orange [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.gray [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.input-mix <mic|fp-mic|linein> (currently linein)
misc.front-mute ON|OFF (currently OFF)
misc.input-mix-mute1 ON|OFF (currently ON)
misc.front1 [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.front2 <front|input-mix> (currently front)
misc.rear-mute ON|OFF (currently OFF)
misc.input-mix-mute2 ON|OFF (currently ON)
misc.rear1 [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.rear2 <rear|input-mix> (currently rear)
misc.center/lfe-mute ON|OFF (currently OFF)
misc.input-mix-mute3 ON|OFF (currently ON)
misc.center/lfe1 [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.center/lfe2 <center/LFE|input-mix> (currently center/LFE)
misc.side-mute ON|OFF (currently ON)
misc.input-mix-mute4 ON|OFF (currently ON)
misc.side1 [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.side2 <side|input-mix> (currently side)
misc.pcm4-mute ON|OFF (currently ON)
misc.input-mix-mute5 ON|OFF (currently ON)
misc.pcm41 [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.pcm42 <pcm4|input-mix> (currently pcm4)
vmix0-enable ON|OFF (currently ON)
vmix0-rate <decimal value> (currently 48000) (Read-only)
vmix0-channels <Stereo|Multich> (currently Multich)
vmix0-src <Fast|Low|Medium|High|High+|Production|OFF> (currently Fast)
vmix0-outvol <monovol> (currently 25.0 dB)
vmix0-invol <monovol> (currently 25.0 dB)
vmix0.pcm9 [<leftvol>:<rightvol>] (currently 25.0:25.0 dB)
vmix0.pcm10 [<leftvol>:<rightvol>] (currently 25.0:25.0 dB)
vmix0.pcm11 [<leftvol>:<rightvol>] (currently 25.0:25.0 dB)
vmix0.pcm12 [<leftvol>:<rightvol>] (currently 25.0:25.0 dB)
I tried to turn everything off at record. Oh and this sound is only there when i play sound, not when i do nothing. Any ideas?

I'd like to use OSS instead of alsa - just for curiosity and for the rumored "better quality"
I followed wiki and got OSS working, except the same problem as stated above. First I get noise from right front speaker (pcm0) and second from spdout_std (the last one osstest testes). The second last one (spdout) gives good sound though, so I could symlink /dev/dsp to /dev/oss/oss_hdaudio0/spdout, but then how to get sound out from the optical SPDIFF output?
Has anybody solved this yet, or do I have to go back ALSA?

When I power up my Mac-Pro I only get a flashing file folder with a ? inside the folder. I suspect my hard drive is maxed to capacity can anyone help me as to what I should do?

When I power up my Mac-Pro I only get a flashing file folder with a ? inside the folder. I suspect my hard drive is maxed to capacity can anyone help me as to what I should do?

Whatever the problem is you no longer have a bootable system. You need to try reinstalling OS X.
Reinstall Snow Leopard without erasing the drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1.
Reinstalling Lion/Mountain Lion Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

Update on tooling with Java ME Embedded 8.1 Developer Preview

If you are having problems with connecting via USB or with static IP addresses, please see:
Update on tooling with Java ME Embedded 8.1 Developer Preview
Best,
-- Terrence

Hello,
I am just viewing this course now and am stuck on finding the raspberry pi 8.1 EA binary:
oracle-jmee-8-1-ea-raspberrypi-linux-bin-b01-20_may_2014.zip
The only thing I can find on this page (which is what the document your link brings up has)
http://www.oracle.com/technetwork/java/embedded/javame/embed-me/downloads/index.html
is 8.0:
oracle-jmee-8-0-rr-raspberrypi-linux-bin.zip
Please help...
Thanks

How can I use Pro Tools with Fire Wire interface and Fire Wire external HD

If Mac Book Pro has only one Fire Wire jack and I want to use Pro Tools with an M Audio 1814 Firewire interface and an external Fire Wire HD how do I get around the fact that the Mac Book Pro has only one fire wire jack?
Pro Tools says that they DO NOT recommend using USB 2 Hard Drives as recording drives.
If I plug my External HD into the back of the 1814 it is way too slow to use, plus, I don't know why, Pro Tools is telling me that my External HD is "not a valid audio volume". It is a MAC OS Extended (Journaled) external Firewire HD (G-TECH G-DRIVE)
Stuck...
Message was edited by: Mezcla

You could consider getting a firewire hub or get an expresscard 34 adapter with a firewire port.
I personally use a Belkin Expresscard adapter that gives me an extra firewire port as well as two extra USB 2.0 ports.
Good luck.

Need connectivity of SAP Oracle with Third Party tool with dsn

Hi Friends,
We need to access SAP's Oracle database with third party tool with the help of dsn creation. For that we need to create 2 staging tables and need a new segment for these tables. Our data will move from SAP transactions to these 2 tables and we want to fetch this data via dsn into another third party S/W.
I am unaware of such kind of working, can you please help me how to create new segment and how to create dsn for accessing tables in this segment.
Our requirement is as follow.
The staging tables are required in the SAP database with user name and password. The user should have all access to the staging table only.
Requesting your kind help on this issue. Please suggest for further processing of activity.
Rgds, Krishan Raheja.

Hi,
Common way to integrate SAP (database) with third party Application is to use and implement SAP Connector (Java or .Net).
Using this, you can fetch the data from SAP database to use it in Third party application.
As per my understanding the method you mentioned, will void the SAP database license term.
So Please check before doing such configuraiton. Also that method is NOT recommended..
Regards.
Rajesh Narkhede

Is there a way to use eraser tool with soft edges?

Hi,
I am wanting to erase the edges of a rectangular object so that it blends better with the background, and am wondering if there is a way of doing this using the eraser tool with soft edges?
Here is a snapshot to illustrate further what I mean:
You should be able to see that above the curve on the left there is a gradient which extends to the top of the image. This is the rectangle which I have applied a gradient to. At the top of the rectangle the colour is the same as the background. What I am trying to do is to blend the left edge of the rectangle in with the background above the curve (below the curve there is a line so no blending is needed). The way I thought of doing this is using the eraser tool with a soft edge. I can do this in Photoshop, but I'm not sure if this is possible or the best approach in Illustrator.
I would be grateful for any advice on this,
Thanks,
Nick

I don't really understand yoru end goal. However, the answer to yoru Eraser Tool question is no. There is no such thing as a "soft edge" for the eraser tool.
The ways to blend objects in specific areas only would be:
Gradients with transparent stop
Gradient mesh with transparency nodes
Opacity masks
Fake it by blending to the same color as the background.

Anybody used PlateSpin or other V2V migration tool with Oracle VM?

We're actually trying to migrate a few XenServer guests over to Oracle VM, but would like a more comprehensive package. One that keeps coming up is PlateSpin, although I'm by no means glued to it as a solution. Ideally, this would be a reasonably flexible tool with p2v, v2v, and v2p. Our environment is currently Xen only (Citrix and Oracle).

886374 wrote:
In playing with OVM 3.0 so far, I see that local storage (as the accelerator cards would show up as) is not really appropriate for Production Systems. It appears I can create a Repository on these physical disks and then present them to the VM guest. Then add these cards as my Oracle ASM disks for my "fast" storage, and do the same with the FiberChannel storage for my "slower" disks. Because of the Local Storage used for part of the VM guest, we would not be able to Live Migrate or have High availability I believe. Is this correct? Correct.
If we have the two servers as mentioned above. Could I take the database VM down and move it to the other server (ie Cold Migration)? The local storage (ie the accelerator cards) could physically be moved from one physical host to the other, but I am not sure, since this is virtualized disk, if this would be allowed or how it could be recognized on the other Oracle VM Server. This might be a "dream", but might be something we would like to do if an emergency arose or if more maintenance needed to be done on Server 1. Any comments?You would have to shutdown the VM, migrate it to an unassigned folder, edit the VM, remove the local storage from Server 1, migrate to Server 2 and add the local storage from Server 2. Whether or not this means moving your hardware is up to you.
Does anyone have other solutions to run Solid State disks (approximately 2TB worth) and Oracle VM, running a single guest that runs the database? We have been unable to find iSCSI or FiberChannel enclosures that can handle solid state drives in the 1 to 2 TB range of capacity. So perhaps there are other enclosures out there that can act as Shared Storage that can operate with SSDs. Thank you for any comments and suggestions.I know the Sun storage appliances use hybrid storage, i.e. a mix of SSD/spinning disks, but I don't know the details. Our Exadata machines have 5TB of Flash storage per cell, so I know we have such options.

Pacman upgrade: Replace sysvinit-tools with core/procps-ng?

Today, when I upgraded my Arch, I got the following message:
:: Replace sysvinit-tools with core/procps-ng? [Y/n]
I didn't find anything in the news. I later chose 'yes', but I wanted to know what this message means, just curiosity. Doesn't sysvinit is a init daemon, like systemd?
└─[$] <> sudo pacman -Syyuu
[sudo] password for thiago:
:: Synchronizing package databases...
core 105.3 KiB 932K/s 00:00 [----------------------------------------------------] 100%
extra 1521.8 KiB 1208K/s 00:01 [----------------------------------------------------] 100%
community 2.0 MiB 1199K/s 00:02 [----------------------------------------------------] 100%
multilib 109.4 KiB 1032K/s 00:00 [----------------------------------------------------] 100%
:: Starting full system upgrade...
:: Replace sysvinit-tools with core/procps-ng? [Y/n] n
resolving dependencies...
looking for inter-conflicts...
:: procps-ng and sysvinit-tools are in conflict. Remove sysvinit-tools? [y/N] ^C
Interrupt signal received

$ pkgfile -l sysvinit-tools | grep bin
core/sysvinit-tools /usr/bin/
core/sysvinit-tools /usr/bin/bootlogd
core/sysvinit-tools /usr/bin/fstab-decode
core/sysvinit-tools /usr/bin/killall5
core/sysvinit-tools /usr/bin/last
core/sysvinit-tools /usr/bin/lastb
core/sysvinit-tools /usr/bin/pidof
$ pacman -Ql procps-ng | grep bin
procps-ng /usr/bin/
procps-ng /usr/bin/free
procps-ng /usr/bin/pgrep
procps-ng /usr/bin/pidof
procps-ng /usr/bin/pkill
procps-ng /usr/bin/pmap
procps-ng /usr/bin/ps
procps-ng /usr/bin/pwdx
procps-ng /usr/bin/slabtop
procps-ng /usr/bin/sysctl
procps-ng /usr/bin/tload
procps-ng /usr/bin/top
procps-ng /usr/bin/uptime
procps-ng /usr/bin/vmstat
procps-ng /usr/bin/w
procps-ng /usr/bin/watch
$ pacman -Qi procps-ng | grep Replace
Replaces : procps sysvinit-tools
sysvinit-tools is not an init system, it was a package that provided tools that used to be associated with sysvinit. Procps-ng now provides those sames tools and thus replaces sysvinit-tools.
EDIT: oops - many of the tools in sysvinit-tools are not provided by procps-ng. pidof is the only one I'd use anyways, and that one is covered. Perhaps the others are specific to sysvinit, I'm not sure.
Last edited by Trilby (2013-12-09 15:49:38)

Trouble with audio i/o with Mbox...

This may actually be a system-wide issue, not a Logic Pro issue, but it only affects me vis-a-vis Logic, so here we go...
I'm trying to use the (original) MBox as an Core Audio interface with Logic Studio. I installed the Core Audio drivers and the Mbox shows up in the drop-down menu of devices in both the Sound Control Panel in my System Prefs and in the Audio Preferences in Logic Studio. But there's no actual audio i/o happening. Having selected it as the device in prefs, and trying to playback output through the Mbox -- or record input through it, there's just nothing happening. Silence, and no response on the meters to input. Other audio interfaces work (i.e. a USB mic/headset; built-in mic and speakers, etc). The internal soundcard on the Mbox seems to be fine, as I can hear the input from the mic running into the Mbox in the headphones I have connected to the device.
I quit Logic and rebooted the Mbox. When I relaunched Logic, and the Digi CoreAudio Manager opened, I started getting a sort of morse code type of sound through my cans. Not feedback, more like digital beeps and such. But in any event still no input/output connecting with the Mac.
Two things to add to the mix: (1) while the device is visible in the System Prefs Sound Control Panel, it doesn't register any input or output on its little built in meters, either -- which makes me think this is s system-wide issue, not a Logic issue; (2) the first time (and only the first time) I selected the Mbox as the Core Audio device in the Logic Prefs, the meters in Logic Pro appeared to indicate there was a feedback loop (peaking on inputs and outputs), though there was no actual sound. I switched off the 48V button on the MBox which killed that problem, but since then, it won't register anything at all.
Any ideas? Thanks!

Digidesign Hardware/drivers are not yet compatible with Leopard. There are thousand of threads about this whenn you do the Google search.
http://duc.digidesign.com/showflat.php?Cat=&Number=1247756&Main=1247729

Visitor Tools with Left Nav Shell

Has anyone out there implemented visitor tools with a custom shell? I have written
a shell the puts navigation to the left of the portal page. I am wondering how
to bring in visitor tools as well, since this is it's own shell.
Thanks.

In your shell file, split the <netuix:header/> element into opening and closing elements, and add an attribute that points to the JSP that enables visitor tools. For example:
<netuix:header>
<netuix:jspContent contentUri="/framework/markup/shell/support/header.jsp"/>
</netuix:header>
Note that you won't see the visitor tools if you preview the portal in Workshop. The visitor tools are only enabled in a streaming portal (one you've created in the Admin Portal).
Depending on where you want the visitor tool links to show up, copy the code from /framework/markup/shell/support/header.jsp into the appropriate JSP.
If you haven't already seen this topic, here's some basic info about enabling the visitor tools in a portal (which doesn't describe the custom shell scenario):
http://edocs.bea.com/workshop/docs81/doc/en/portal/buildportals/visitorToolsAdd.html

Merge photoshop tools with LR

The current retouching tools in LR are limited and it would be more efficient if tools such as the clone stamp tool (with opacity adjustment), the patch tool and healing brush are incorporated.These tools seem are more flexible and work faster than the current circular clone/heal tool in LR. I would also like to see the curves function made more sensitive so that points on the curve can be tweaked for more subtle tonal variation and a masking function added as corrections in LR tend to be across the board.
LR sharpening of subjects with texture is not well catered for.In a landscape,the masking slider might be used to eliminate noise in the sky, but this will simultaneously, smooth out texture in stone or rock.Although, the adjustment brush can be used to selectively sharpen,an enhance texture control such as used in plugins would be faster.Alternatively a masking brush could be introduced to eliminate sharpening where it is not required.

Versions of Photoshop have different installation trees and user preferences. You do not merge Photoshop versions. Each version is independent. When you install newer versions of Photoshop the are options to migrate your presets and Preferences. You can start and use any version installed on your machine. For the most part newer version of Photoshop are backwards compatible with older versions of Photoshop. However some changes Adobe make to Photoshop change user interfaces and and the way Photoshop performs some functions these changes break some user actions, scripts and user work-flows. In fact all the version you listed CS4, CS5 and CS6 have comparability issues. In that respect Photoshop CC is not any better it has compatibility issues.
Newer versions of Photoshop have new functions and updated old function. Older versions can not handle everything save by newer versions of Photoshop. If you save PSD and PSB files with the maximum compatibility option checked. Older version should be able to open you layer document with layers that look like what was saved though some layer may be altered and may even be a different layer kind then was saved. If you need to support older versions of Photoshop always use the maximum compatibility option.

I turned off my computer while installing something and now I only get the start-up screen with the apple logo. How do I fix this?

I turned off my computer while installing something and now I only get the start-up screen with the apple logo. How do I fix this?

Reinstall OS X:
Reinstall OS X without erasing the drive
Do the following:
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.
Reinstalling Lion Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion: Select Reinstall Lion and click on the Continue button.
Note: You can also re-download the Lion installer by opening the App Store application. Hold down the OPTION key and click on the Purchases icon in the toolbar. You should now see an active Install button to the right of your Lion purchase entry. There are situations in which this will not work. For example, if you are already booted into the Lion you originally purchased with your Apple ID or if an instance of the Lion installer is located anywhere on your computer.

How do I fix a initializing problem with my macbook pro? I only get to the blank screen with the apple logo and the "processing something"sign... it just doesn't start the system....

How do I fix a initializing problem with my macbook pro? I only get to the blank screen with the apple logo and the "processing something" sign... it just doesn't start the system....
Please help
Marcelo

If there is no loading bar, it's usually a problem with a third party kext file in OS X itself.
You can press the power button down to force a hardware shutdown, then reboot holding the shift key down on a wired or built in keyboard, this will disable them and you go around and update your third party software.
Gray, Blue or White screen at boot, w/spinner/progress bar
Also take this time to backup your users files off the machine if possible.
Most commonly used backup methods
Sometime that won't work and you need to do more
..Step by Step to fix your Mac

Only noise in v.o. tool with MBox

Similar Messages

Maybe you are looking for