The Aux Sends are a new feature, and let you set up a completely different submix, perhaps for monitoring on headphones or to send to a hardware effects unit.
Since multiple channels can be routed to the hardware outputs, and the summed signals can therefore cause clipping, additional meters display the Output buss levels. Admirable though this is, it doesn't mean that the will now work with everything, but simply that there are fewer unknowns for potential users.
A list of compatible A PCI adaptor cards is posted, while Firewire host controllers based on the NEC chip set are not recommended, although you can work round the problems if you're prepared to use the supplied AC adaptor instead of powering the via the Firewire buss see Powering The box for more details. Apple Macs that meet the minimum spec will all work. The Output page provides control over the 10 hardware outputs, plus the headphone and Aux busses.
Once again there are meters, level faders, Link, Mute and Solo buttons, but this time there's also a rotary Balance control linked to the stereo faders. However, if you click on this it changes to Aux, and this is how you can route your Aux submix to any combination of hardware outputs — a very handy feature indeed. The Aux output doesn't have a Solo button, but it does have an extra pair of rotary pan controls. In the control panel's Output page you have final control over the signals being sent to the various hardware outputs, including the twin headphone sockets.
Notice here that I've routed the Aux signal to the phones, to receive the monitoring submix previously set up in the mixer page. Having got this far, I can finally explain the function of the front-panel rotary encoder. Switching to Output Bus provides similar control over any combination of signals being sent to the hardware outputs, while Input, Phones and Aux are hopefully now self-explanatory.
When switching between the five options, the mixer remembers your previous Ctrl settings. Overall, the system is very well thought-out, and the Control Panel's virtual encoder control knob provided me with smooth control over my selected parameters. However, I found several practical problems with the front-panel rotary encoder.
First, it's so closely positioned to input two's gain control that it can be difficult to get your fingers in for a 'twirl'. Second, feedback via Firewire seemed erratic, making the software faders jump about following a smooth change from the front-panel control, and sometimes even causing them to go in the wrong direction.
By the way, both digital outputs carry exactly the same signal. I am so sick of Microsoft not being more community friendly when they can see all the problems everyone has just like I can. Too cold so far to have any ambition to do it. Laura Gullett Cleveland, OH. In reply to LauraRGullett's post on February 13, I recently came across an interesting post that might be worth investigating.
Take a look at what James Shield had to say about firewire devices at the Windows 7 will not recognize Firewire iLink cable thread. Have you had any luck yet with your Firewire problem. Have exactly the same problem. I use vegas Pro v I can see and control the camera but cannot capture any HDV footage. Have tried Legacy driver and texas instruments one. No help. If you've found a solution I would love to know it. Thanks Paul Cox.
In reply to paulcox's post on May 23, I do have an answer that most don't want to hear. It cost me money but I finally! Plus, one internal USB 2. Just remember to reboot after each installation of a driver. Note: try and find the heritage driver from a XP 32 machine and copy it to your 64 system if you can get a hold of it.
What I learned for sure was that others who said that you must use a A port with the 4 pin Sony cable were indeed correct.
Click on the arrow next to it and it will show you what is connected. Check the following things: 1 Look under other devices that are listed to see if the device, such as a scanner, shows up. Make sure your Firewire cable is plugged in all the way at both ends. Try a different Firewire port. Try a different Firewire cable. Make sure the Firewire card has the VIA chipset, especially if you are connecting a scanner to the Firewire port.
IEEE port 6. Make sure the device you are connecting to the Firewire cable is powered on. If you are attaching a scanner to the Firewire port, you most likely need the software from this website: VueScan Scanner Software.
Connect the Hard Drive to the Firewire port using a Firewire cable. Once, your connected, the power on the device. Click on the arrow next to Disk Drives. This will show you all of the disk drives connection to the computer, including the external Firewire Hard Drive as shown below. Click on the arrow next to Sound, Video and Game Controllers.
This should show you the Audio device connected to the computer. Also, it show up under Other Devices, as shown below. Depending on the audio equipment you are connecting will depend on where it shows up. Note: Depending on the audio device you are trying to connect, you may need install an audio driver for the device along with the Legacy Firewire driver.
See if it needs a separate audio drive for that specific piece of equipment. Look under other devices that are listed. This has not happened in the last 5 years, so it is nothing to worry about. I just wanted to mention it, in case it should ever happen again. The Fix for Windows 7 For Windows 7 simply replace the new driver with the Legacy driver that comes with Windows 7. Click on the Close button and exit out of all of the other windows. Then Reboot your computer. You will now be able to import video via the FireWire port on your computer.
If you are still having a problem importing video after you have switched the FireWire driver to Legacy, then the problem may be with the FireWire port.
This is a common problem. The FireWire port will work with an external driver, but it won't let you import video from your video camera. Most people report this problem with Dell computer, but it does happen with other brands, even brand new computers. This problem is usually with the FireWire port that is built into the motherboard. The fix is simple: 1. Install a FireWire card into one of the open slots in the computer 2.
Using the instructions above, set the drive to Legacy. Reboot the computer. Then connect the FireWire cable from the video camera, into the new FireWire port that you just added. Use a Firewire card with the VIA chipset. If you notice the FireWire device is transferring slowly or not working, then just repeat the above steps and reinstall the Legacy driver.
Make sure the software you are using still works with Firewire capture. Any input appreciated, Flo. Posted 30 May - AM Hey there jaclaz youre everywhere arent you My motivation with this is quite the same as with Win9x: I will probably never use it but if i can make it work i want to make it work New ideas on the driver's codes would be really great!
As for the testing, i still dont have any Firewire devices so it will never get to any potential vendor-checking. What i do have however, is a Creative Audigy2 card with Firewire on board, somewhere in storage Dont have much hope with this exotic implementation of a rare interface, especially in DOS.
BUT your reply and Capt. Dan gave me hope that this will be useful to someone, so i will find and test that card today. Oh and i honor your disclaimer, but not sure if i want to become your Jane Flo.
Posted 09 June - PM Hi all, after doing a little more research i found that the Iomega package is universal, so you can trash DAToptics' Firewire, and my idea. Cheers, Flo. Posted 10 June - AM I dont have any firewire stuff either. But if you put your testing results on the Web [in this case boot-land], im sure eventually somone will search for such a topic and might find your creations and results usefull.
0コメント