 After installing QuickTime 7.2 or iTunes, Flash no longer works properly ...
|
| After installing QuickTime 7.2 or iTunes, Flash no longer works properly in any browser. |
1) Go the the Adobe Flash homepage and reinstall the latest Flash Player for Mac.
2) Start the QuickTime Player application. Go into QuickTime Player>QT Preferences. Click on the "ADVANCED" tab.
3) Make sure "ENABLE FLASH" is ON.
4) At the bottom you will see "MIME SETTINGS...". Click on this button.
5) Scroll down to "MISCELLANEOUS - MISCELLANEOUS FILE FORMATS".
6) Turn OFF the "FLASH MEDIA" option and click "OK".
7) Restart your computer.
[Page View]
|
|
|
How Do I Print Reason To Audio In Pro Tools?
|
| How Do I Print Reason To Audio In Pro Tools? |
It may be possible to free up resources by printing Reason to audio in a Pro Tools session. This may help with DAE errors in some sessions using Reason as a plug-in insert in Pro Tools.
In order to print the outputs of Reason to audio, you must connect the path that Reason is inserted on to an audio track in Pro Tools with unused Busses.
1. Create 1 new stereo audio track in Pro Tools.
2. Set the input of the sudio track to a stereo pair of unused busses such as bus 15-16 stereo.
3. Set the output of the track that Reason is inserted on to the same pair of busses.
In this example bus 15-16 stereo.
4. Make sure you have Pro Tools set to Input only monitor.
5. Record-enable the audio track.
6. Play the session to verify signal in both the track that Reason is inserted onto, and the audio track that you are going to record onto.
7. Record Reason onto the audio track.
8. Once you have printed Reason to audio, take the record enable off for the audio track and verify playback.
9. Make Reason inactive in the session. This is done by Control + Windows clicking (Control + Command click Mac). This will free up CPU resources used by this plug-in.
10. Quit the Reason application. This will free up any further resources used by this application. Remember to save if appropriate.
[Page View]
|
|
|
Sound quality when using Reason via ReWire is very poor, and can drop ...
|
| Sound quality when using Reason via ReWire is very poor, and can drop in and out. The problem is intermitant, and in some cases seems to only affect the sound when Malstrom is used within Reason |
This was resolved by increasing the Hardware Buffer Size to the maximum (2048 Samples within an LE system).
Higher H/W buffer Size settings can affect the accuracy of plug-in automation, mute data, and timing for MIDI tracks, in addition to increasing latency.
However, higher H/W buffer sizes are required for more audio processing and effects, especially during mixing when using more RTAS plug-ins.
[Page View]
|
|
|
Whenever I record enable an audio track or create an aux input the level ...
|
| Whenever I record enable an audio track or create an aux input the level meter will ramp up to the top yellow margins. |
Clean uninstalling and reinstalling fixed the problem.
[Page View]
|
|
|
Can I use my Digi 001, Mbox, Digi 002 or Digi 002 Rack in DAE mode in ...
|
| Can I use my Digi 001, Mbox, Digi 002 or Digi 002 Rack in DAE mode in Digital Performer? |
No. DAE mode is not necessary, since 3rd party applications must use the CoreAudio driver to play through the Digidesign hardware. Thus, you don't have access to DAE with an Digi 001, Mbox or 002.
Note: the Digi 001 is ONLY supported with the CoreAudio driver v6.1.2 for Mac OS 10.2x (Jaguar).
[Page View]
|
|
|
Where can MIDI Patch Names for Windows be found that are not in the default ...
|
| Where can MIDI Patch Names for Windows be found that are not in the default Digidesign MIDI Patch names folder? |
You need to create a device that is named the after the MIDI device.
1) To add the patches, collect the device from the links below.
2) Put the xml, .midnam files in the Program Files/Common Files/ Digidesign/MIDI Patch Names folder.
3) Create a session in Pro Tools.
4) On a MIDI track, call up the MIDI device you created for the patches you downloaded.
NOTE:
1) Make sure the name of the device and the patch name are spelled exactly the same less the .midnam extension.
2) Click on the patch names selector on the MIDI track then click change.
3) Navigate to the patch names in the Program Files/Common Files/ Digidesign/MIDI Patch Names folder.
4) Click on that device.
5) Click OK. Then your patches appear in the patch names for that device.
One user Website has an extensive collection of XML documents
for a majority of the MIDI device manufactures.
Try: http://digicake.com/midnam/
(The files here are .sit and require Stuffit Expander to decompress on the PC)
What's a midnam? Well, here's a handy midnam link from Digidesign:
http://www.digidesign.com/digiNews/2003/8-03/tech_tips.html
and for special characters used in xml files take a look at: webmonkey
http://hotwired.lycos.com/webmonkey/reference/special_characters/
Most of the following patches were written for Pro Tools and should work. Note: those that have "(DP4)" after them have only been tested in Digital Performer v.4 ; therefore, they may or may not work with Pro Tools. Please refer to the DUC (Digidesign Users Conference at http://duc.digidesign.com/) for more info (search for midnam). There are also many more resources appearing on the web.
[Page View]
|
|
|
Recorded MIDI notes (when using a software synth) are playing back earlier ...
|
| Recorded MIDI notes (when using a software synth) are playing back earlier than the other audio tracks or other MIDI tracks already in the Pro Tools session. |
This is an issue when using software synths (RTAS plug-ins) in Pro Tools.
When a user records a MIDI performance into Pro Tools, it sounds in time to the audio in the session. But, during playback the MIDI notes visually do NOT line up with the grid and do not play back in time to Pro Tools, the notes are early. This can also happen when using the CoreAudio driver for the Digidesign Hardware when using another sequencing program such as Digital Performer and using software synths.
In Pro Tools set the H/W buffer size to 1024 samples to prevent this from happening. Setups menu > Playback Engine. Set H/W buffer to 1024 samples.
Reported in Pro Tools 6.4 & 6.7 on Mac and Windows.
[Page View]
|
|
|
I'm using Digital Performer with the Digidesign Core Audio driver and ...
|
| I'm using Digital Performer with the Digidesign Core Audio driver and an Mbox. I get an error message when launching Digital Performer: "program error: client path to invalid argument to the system." |
This error was encountered by a user with an ice white iBook and can be solved by shutting down the computer, unplugging the Mbox, rebooting the computer and plugging the Mbox in after the computer has booted up completely.
See Abase 26365 for related info.
[Page View]
|
|
|
How do I upgrade Reason Adapted 2.5 to the full version of Reason 2.5?
|
| How do I upgrade Reason Adapted 2.5 to the full version of Reason 2.5? |
You can do this through a dealer, or online.
- Go to the Propellerheads website
- Click on the "Prop Shop"
- Choose the country at the bottom of the page
- Scroll until you find "Reason 2.5 Upgrade for Reason Adapted"
[Page View]
|
|
|
Digital Performer v4.1.2 posts a warning message when launching: "The ...
|
| Digital Performer v4.1.2 posts a warning message when launching: "The audio hardware did not respond. (MotuAudioSystem Mas MasCoreAudioWorkThread.cpp, 102 [57:01])." |
When launching Digital Performer, you may see the following warning message: "The audio hardware did not respond. (MotuAudioSystem Mas MasCoreAudioWorkThread.cpp, 102 [57:01])." This warning can be safely ignored. Digital Performer will open and play back projects correctly.
Taken from the Read Me for Digidesign CoreAudio Driver v6.5 (Mac OS X Only). Item # 50010.
[Page View]
|
|
|
