• Jun 07, 2017  To have us re-initialize the offline files cache and database for you, go to the 'Fix it for me' section. If you prefer to fix this problem yourself, go to the 'Let me fix it myself' section. Fix it for me To fix this problem automatically, click the Fix itbutton or link.
• There are several causes of Access database (ACCDB) and (MDB) files corruption  which make it damage. According to professional these reasons can be classified into two categories first is hardware and second is software. Cause 1# File System Damage.
• Jul 12, 2012  Detecting and removing corrupt files. The most common cause of a crash is having a corrupt file in your music library. You will need to make sure you have all your files analyzed and remove any files marked as corrupt. To remove corrupt files: Disconnect your.
• Nov 18, 2015  Search index getting corrupted on Windows 10 On my workstation with Windows 10 RTM, searching programs from the start menu usually does not work. Or it works for a while, after which the search crashes again.
• It can determine which Serato Scratch Live Drivers are either missing, corrupt, or have become obsolete. Next, Easy Driver Pro searches a database of over 11 million drivers and matches missing, corrupt, or obsolete Serato Scratch Live Drivers to the latest, most compatible drivers for your operating system.
• May 15, 2019 Repairing corrupt SQL Server Database can be a tedious task if you don’t know the right technique. There is manual technique available to repair corrupt SQL database but a professional and authentic third-party software is always the best approach to do it.

Jul 03, 2019  One such issue is to move a corrupt mailbox from one server to another, but deploying the right Exchange data recovery software software like Stellar Repair for Exchange helps to repair and move corrupt mailboxes from one Exchange server to another. In fact, deploying mailbox exchange recovery software acts as a ready reckoner for any problem.

Here are ten of the most common Microsoft Access problems and their solutions. Don’t give up hope if your problem is not on this list. Chances are, if you’re having the problem, someone else has already had it and figured out the solution. That’s why the Internet is a valuable resource.

That’s just not normal—normalizing empty Access tables

One of the hardest things to do (yet most important when building a database) is building the table structures properly. This process is known as normalization. A properly normalized database should never have just one table containing redundant information. Consider the following table:

Do you see the redundant information? Right you are. It’s the customer name and address. What is causing the redundancy? Right again! It’s the two phone numbers for customer Jones. The correct way to normalize this table would be to split it into two tables — one for customer name and address information and the second for phone numbers. This would eliminate the need to repeat the second Jones record in the Customers table.

If you’re having trouble normalizing empty tables, fill each table with five to ten records. Viewing the tables with data usually makes it easier to spot normalizing issues.

Here’s how to get started normalizing your tables:

1. Examine each table as it is currently structured.
   Are you repeating any information unnecessarily (as you saw with the address and customer name earlier)?
2. If you have duplicate information, determine why you’re repeating it (for example, the multiple phone numbers for one customer).
3. Break the one table into two tables to eliminate the redundancy.
4. Repeat Steps 1 through 3 for each table until all redundancy is eliminated.

You may find that splitting one table into two still does not eliminate all redundancy in a table. In that case, keep splitting the tables until all redundancy is gone.

You type 73.725, but Access changes it to 74

Automatic rounding can frustrate the living daylights out of you, but correcting it is easy. By default, Access sets all number fields to accept long integers. As you may remember from your high school math days, an integer is a negative or positive whole number. To accommodate decimals, you change the field-size setting so it accepts decimals. Here’s how:

1. Open the table in Design view and then click the field that’s not cooperating.
2. On the General tab of the Properties area at the bottom of the screen, click the Field Size box.
3. Click the down arrow at the end of the box, and then select Single, Double, or Decimal from the drop-down menu that appears.
4. Save the table, and your automatic rounding problem is over.

For details about the difference between Single, Double, and Decimal field sizes, press the F1 key while in the Field Size property box. The Help screen gives a detailed description of each field size, the numbers it will hold, and the amount of space reserved for that size. Access requires an Internet connection to use its help system.

The words they are a-changing—problems with Access AutoCorrect

Sometimes those “helpful” features in Access can become a nuisance. One such feature is called AutoCorrect. You may be familiar with it from Microsoft Word, where it is often a great thing. Databases, however, often contain acronyms, part numbers, and the like. AutoCorrect can have a field day with such “words”. You may not even realize it as you enter your data.

You have two choices to resolve this problem.

• Undo AutoCorrect’s effects as they occur. Press Ctrl+Z right after AutoCorrect has botched your data entry. Access puts the data back to the way you typed it. Unfortunately, for this to work you actually have to notice that Access has changed what you entered.
• Turn AutoCorrect off entirely. To turn off AutoCorrect, follow these steps:

1. Click the File tab in the upper left corner of the Access screen.

2. Click the Options button in the menu down the left side of the screen.

The Access Options dialog box appears.

3. Click Proofing from the list on the left.

Your proofing choices appear.

4. Click the AutoCorrect Options button.

The AutoCorrect dialog box appears.

5. Uncheck some or all of the check boxes in the AutoCorrect dialog box.

You can disable some or all of the AutoCorrect features, depending on what AutoCorrect is doing to annoy you at present. Uncheck the Replace Text as You Type option if you no longer want Access to “fix” your “spelling errors” for you.

6. Click OK two times to save your changes.

You can now type your problem text correctly, without AutoCorrect’s interference, and have it stay as you typed it.

Was there and now it’s gone—accidental data deletions in Access

You might’ve heard this one a lot over the years: “The database deleted my record!” Well, I’ve got news for you: The database doesn’t do anything without us humans commanding it. And humans can make a couple of mistakes:

• Accidental deletion: There are several ways to delete a record accidentally. Usually a keyboard shortcut for Delete is pressed, such as Ctrl+– (delete record) or Ctrl+X (cut).

The Undo command (Ctrl+Z) will not reverse the deletion of a record.

• Data error: A record may appear deleted if someone inadvertently changes a particularly vital piece of information. For example, suppose the record in question contains an order date of 12/15/19, and someone inadvertently changes the date to 12/15/09. The order date isn’t what’s expected, so the record may seem to have been deleted.
• If a data error makes the record seem deleted, there are several possible fixes, as outlined in the following sections.

Undo

Don’t panic. Before doing anything else, press Ctrl+Z. That’s the Undo command. If the record comes back, you’re in luck. Undo reverses data-entry errors that may cause the record to appear deleted. However, this will work only if you Undo right after the data-entry error takes place.

Search for the missing record

If you try the Undo command and the record doesn’t come back, there’s still a chance that a data-entry error is hiding it by putting it where you don’t expect it to be. Open the table that contained the record and search for it in some way other than you normally would. Look for anything out of the ordinary on similar records. Here are some examples:

• If you normally search for orders by date, search by client. See whether an order similar to the missing one exists for that client and has an unusual date (say, the same month and day as the missing order but with the wrong year).
• Try looking at all orders on the date in question to see whether the client on each order seems to be correct. It could be that the client was changed inadvertently on the missing order.

Backup recovery

If you can’t find the record anywhere, copy the record from a backup of the database file.

This solution works only if you’ve backed up your database since the record was originally added. If you back up at night and the record was entered during the same day it went missing, that record will not be in your backup.

You run an Access query, but the results are unexpected

Query-writing is an art form. Even the experts mess up every now and then. Here are some common solutions to unexpected query results:

• Check criteria for accuracy. A single misplaced keystroke is all it takes to turn your query into a dud. Check your criteria for spelling or syntax errors — and then run the query again.
• Try the Unique Values property. Ever see two copies of each record in your query results when you were expecting just one? A quick fix often comes from using the Unique Values property. This property tells Access to stop with the doubling, already — and, if the query results contain a group of exact duplicates, to return only one row from the group. Here’s how to use this property:

1. Open the problem query in Design view.

The Design tab on the Ribbon appears.

2. Click the Property Sheet button from the tab’s Show/Hide Ribbon group.

The Property Sheet window opens to the right of the query grid.

3. Click in the gray area between the field lists in the top half of the query grid.

The Property Sheet should now display Query Properties. (Look right under the Property Sheet’s title bar to confirm this.)

4. Click in the Unique Values row of the Property Sheet.

A drop-down list arrow appears at the end of the Unique Values row.

5. Select Yes from the drop-down list and run the query.

The doubling should disappear.

• Correct the selection logic. Juggling a bunch of AND and OR connections in a query can quickly mess up even the hardiest of database designers.
• Fix table relationships. If your query results show way too many records, and the query uses two or more tables, improper relationships (also called joins) are the likely cause.
• Check table relationship types. If your query involves two or more tables, and you get fewer records than you expected, incorrect table relationships are the likely cause. For example, if you have an order entry database and run a query listing all customers and their orders, by default, you’ll see only those customers who have placed an order. To see all customers, whether or not they’ve placed orders, do the following:

1. In Design view, right-click the join (the line connecting the two tables) and choose Join Properties from the menu that appears.

2. Examine the types of joins offered and choose the one that says something like “Include ALL records from ‘Customers’ and only those records from ‘Orders’ where the joined fields are equal”.

The actual text you see differs according to the names of your tables. To query aficionados, this is called an outer join. Very cool.

3. Click OK and run the query.

You should now have all records from the Customers table whether or not there are corresponding records in the Orders table.

If your query involves several criteria, some calculated fields, and numerous relationships, try breaking the task into several smaller steps instead of trying to solve the problem all at once. The step-by-step approach lets you focus on each piece, one at a time, making sure each works perfectly before moving on to the next one.

If your query still doesn’t work no matter what you do, ask someone else to take a look. I’ve often worked on a tough query problem for hours, shown it to someone else, and heard those magical words: “That’s simple. Djay for ios select all songs. Just do this.” And the problem is solved. Getting a fresh pair of eyes on the problem often solves things fast.

The dreaded Parameter dialog box in Access

At some point, when opening a query, form, or report, you’ll see a Parameter dialog box when you don’t want to see a Parameter dialog box. Do you throw your hands in the air and curse the universe? Of course not! Whenever you see a Parameter dialog box unexpectedly (you can set them on purpose), it means that Access can’t find a field referenced by either the form or report or the query behind the form or report. Say that the problem is with a report. To troubleshoot, start with the query behind the report. Open that query in Datasheet view and see if you get the parameter. If you do, what field is it asking for? That field is the one Access can’t find. So, switch the query to Design view and find the column with the field that Access can’t find. The problem field is usually a Calculated field that references other fields. Is each field and table name spelled correctly? If not, correct the spelling errors. Is each field in the table it’s supposed to be in? For example, if your reference reads Orders.LastName and the LastName field is in the Customers table, correct the error by typing Customers.LastName.

If the query runs without a parameter, then the problem is on the report. So, open the report in Design view and check each control on the report that is bound to a field. If Access can’t find one of the fields the control is supposed to display, it’ll put a green triangle in the upper left corner of the control. Check each one for the green triangle. If you find the green triangle, check the spelling of the field referenced by the control. For example, if the control is supposed to display LastName (no space) and the reference in the control says Last Name (space), then remove the space so that the control on the report matches the field name from the query. Also check the report’s underlying query to confirm the problem field is selected in the query.

The slowest Access database in town

An Access database may end up on the shared drive of a business so it’s available to everyone who needs it. The problem with placing the entire Access database on the shared drive is that it often runs slowly on each user’s workstation (that’s a fancy word for an individual computer). You’ll also likely run into errors if multiple people attempt to use the database at the same time. The complaints start rolling in, and you don’t know what to do.

The solution to this problem lies in splitting the Access database file into two separate files:

• Front end: Contains all the database objects except the tables

The front end resides on the user workstation. Midi controller garageband ipad.

• Back end: Contains just the tables

The back end resides on the shared server.

The front end is linked to tables in the back end.

All you’re really sharing is the data — so the data is all that should go on the shared drive. By setting things up this way, the only information that must travel across the network is the data requested by the user. Such a setup dramatically speeds database performance and allows multiple users to enter and edit data at the same time.

Splitting the dataset is not as hard as you might think. Access makes it a snap with the Database Splitter Wizard. Follow these steps to split your database:

1. Back up the database you want to split.
   If anything goes wrong (unlikely, but hey, you can never be too safe when it comes to data!), you can try again with the backup copy.
2. If necessary, move the database you want to split to a folder on your shared drive.
   This step allows the Database Splitter to set up table links properly for you.
3. Open the database file you want to split from the shared folder.
   Make sure you have a backup copy of this database before going any further. Also make sure all database objects are closed.
4. Click the Database Tools tab on the Ribbon.
   The Move Data group appears on the Ribbon. It contains a button called Access Database.
5. Click the Access Database button.
   The Database Splitter Wizard dialog box appears.
6. Click the Split Database button and let the wizard do its thing.
   You will be prompted for a back-end database filename. Enter a name, sit back, and watch the fun unfold before your very eyes.
7. Copy the front-end file (the original file you split) to each user’s workstation.
   Have the users open the file from their workstations — and see how they marvel at the improved speed of the database! You are a hero. Yea!

Don’t have a shared drive or want to get rid of your share? You can still have multiple users in your database at one time by placing your data in the cloud.

Your Access database file is as big as a house

As time goes by, you find your database file growing larger and larger. This is a result of deleting objects and records over time. If, for example, you create a query and then later delete it because it’s no longer needed, Access doesn’t automatically remove the space occupied by that query from the database file. The same is true for records. As you delete records from a table, the space that those records occupied in the database file remains. Eventually, the file can become four or five times the size required to hold the data and objects within it.

Why should you care if the file size increases? Here are two reasons:

• A smaller database file runs faster. Performance is a key component to happy database users. You want your forms to load quickly and your queries and reports to run as fast as possible.
• A regularly compacted database is more stable. If the database is used often, compacting regularly helps keep file and table corruption from occurring.

The Compact and Repair command removes the excess. It is good practice to compact your database regularly (once a week is usually fine). Always compact it after making any design changes. Here’s how:

1. Open the bloated database and click the Database Tools tab on the Ribbon.
   The Tools group appears at the very left of the Ribbon.
2. Click the Compact and Repair Database button from the Tools group.
   The status bar (lower right of your screen) displays a progress bar that notifies you of how the compact process is progressing. When the progress bar disappears, compacting is complete — and you’ll be left with a much trimmer (faster and more stable) database file. If you’ve split your database, don’t forget to compact both the front- and back-end files.
   

Configuration Database Corrupt

Want a database file to compact each time you close it? Follow these steps:

1. Click the File tab on the Ribbon.
2. Click the Access Options button in the menu bar down the left side of the screen.
   The Access Options dialog box appears.
3. Click Current Database from the list on the left.
   Options for the current database appear.
4. Check the Compact on Close check box.
5. Click OK to save your changes.
6. Click OK from the resulting message box.
7. Close the database and note the lower right status bar.
   The database is compacting before it closes!

Compact on close is used best on the front-end file only. Compacting the back end on close may cause corruption of the back-end file should another user be in it when you close out of it. Do not turn on Compact on Close on the back-end file.

You get a mess when importing your spreadsheet ito Access

It’s common practice to upgrade a collection of spreadsheets to an Access database after the spreadsheet solution no longer suits your needs. It’s also common to find the imported spreadsheet (now table) data in a state of disarray. The easiest way to solve this problem is by cleaning up the spreadsheet before you import it. Here are a few tips for a tidy import:

• Double-check information coming from any spreadsheet program to be sure that it’s consistent and complete.
  Above all, make sure that all entries in each column (field) are the same data type (all numbers, all text, or all whatever).
• Remove any titles and blank rows from the top of the spreadsheet.
  An ideal spreadsheet for import will have field names (column headings) in row 1 and data starting in row 2.
• Make sure your spreadsheet column headings are short and unique so Access can easily translate them to field names during import.

We’re sorry; your Access database file is corrupt

It started out as a day just like any other. However, on this day, you are getting an error when you open the front end of your split Access database. You can’t seem to open any forms or reports. It’s funny how a few little messages can ruin your day. You start wondering if you backed up the data file last night and when the file was actually corrupted. Then you start wondering how you’ll get out of this mess.

Fear not. There is a simple solution to a corrupt database. Here are the steps:

1. Browse to the folder that contains the back-end file.
2. Double-click the file to open it.
   Access will launch and attempt to repair the file. You should see a repair progress bar on the right part of the status bar. If all goes well, the file opens.
3. Close the back-end data file.
4. Reopen the front-end file and everything should be working normally.

If, after following the preceding directions, the corrupted file still doesn’t open, you have a serious problem that could take some effort to clean up. The next step is to resort to a backup copy of the database. Check what data is missing between the backup and your recollection of the corrupted file. Yes, you’ll have to reenter any missing data. Sorry!

If you don’t have a backup, all hope is not lost. You can buy software designed specifically to repair corrupted Access database files. Try searching the web for repair corrupt Microsoft Access database files. Make sure the software works with Microsoft Access 2019 and it is from a legitimate company.

It’s been a good while since the spawn of Serato and Ableton‘s partnership has been given the spotlight. But this latest update to Serato Scratch Live is all about adding The Bridge‘s MixTape functionality to Rane‘s Sixty-One and Sixty-Two mixers, as well as turning the Sixty-Two into a MIDI beast of epic proportions.

The official and complete word from Serato Towers:

What’s New in 2.4.2

Features

• Added Mixtape support for the Rane Sixty-One and Sixty-Two:
  Record your Serato DJ performance as an Ableton Live Set, complete with song placement and fader movements. Then use Live’s collection of effects, instruments and production tools to edit, enhance and polish your mix. Note: Mixtape requires The Bridge
• Multi-channel layer support for the Sixty-Two:
  MIDI mapping is now possible for all MIDI control/note values for the 2nd to 16th channel layers of the Sixty-One and Sixty-Two. This requires the latest firmware updates. Get more information on how to use the Multi-channel MIDI layers for the Sixty-Two.

Bug fixes

Playback Fixes

• Fixed SP-6 bug where, when selecting loop start positions, the white playhead will move to the beginning of the selected start loop.
• Fixed SP-6 bug where, when hot plugging, the selected loop slot will not reset to loop 1 if it was previously set to loop 2, 3 etc.
• Re-instated instant doubling always occurring when drag dropping between decks and SP-6 slots, even when the ‘Instant Doubling’ option is disabled.
• Fixed bug where the offline player was sometimes not in auto-play mode.
• The offline player and the left deck are no longer ‘on’ when Scratch Live is launched.

Library fixes

• Improved iTunes XML importing.

This is to address the issue where iTunes library importing would fail when the library contained non utf-8 encoded strings. These formatting errors are an issue with iTunes library exporting.

• iTunes folders are collapsed on startup. Note that collapse state for them is not saved to preferences.
• The iTunes “Grouping” attribute is now loaded from the iTunes library.

File writing fixes

• Fixed an mpeg4 tag writing bug where the track number was being saved to the year tag.
• Fixed track number write bug where for track x of y, where x is the track number and y is the total number of tracks for the album, y was being deleted. This affected mpeg4 files.
• Fixed a bug where .wav file tags couldn’t be read or written to properly because of non-wide aligned chunks. A symptom is overviews always being rebuilt. Note that these files are technically corrupt and will therefore not be able to be analysed.
• Fixed bug where is was not possible delete the year tag of a track.
• Fixed bug where, on first track load for a file that has an .xml and .ovb meta data (located in _Serato_/Metadata), the overview would be rebuilt.
• Fixed bug where tracks with .xml metadata would always do a tag write after they are used for the first time in a Scratch Live session.
• Fixed bug where if there is a non-ascii character in the album field of an mpeg4 file, then incorrect characters could be saved to that field when the file is tag edited (evident upon track load).
• Fixed bug where the ‘total number of discs’ meta data in an mpeg4 file was being incorrectly written to.
• Autogain info can now be saved/loaded to/from OGG files.

Hardware related fixes

• Fixed a Sixty-Two bug where instant doubling could still occur when the track scroll knob is turned during the double click.
• Fixed a Sixty-Two bug where, when using the track scroll knob, it was not possible to rapidly go: load->scroll->load; some of the track loads would be missed.
• When enabling DJ FX flex fx sending, all the channel/deck mappings are now turned off as a means of ensuring that audio reactive video is turned off when a user changes from a non-flex-fx capable device to a flexfx capable device (i.e. switching from an SL 2 to a Sixty-Two).
• Fixed a Sixty-Two bug where the Sixty-Two’s SP-6 trigger button lights still flashed if the SP-6 panel is closed and the play head reaches the end of the track.
• The Sixty-One and Sixty-Two effect sliders in Setup->Hardware->Effects are now midi mappable.
• The Sixty-Two’s recording option now defaults to Mix and not PGM 1.
• Added midi mapping ability for a Sixty-One joystick press.

GUI fixes and changes

• Fixed bug where the UI bar of SSL would still appear on a secondary monitor (when the secondary monitor is above your main monitor).
• Fixed bug where, on startup, the UI bar would be visible, even though SSL starts in fullscreen mode.
• Fixed bug where, if the window is restored, dragged so that the centre of the window is outside the bounds of the display, then maximised again, the OS X Menu bar would be visible and obscure the Scratch Live window mode controls.
• The recording widget’s time area now has the colon and dot visible again.

Serato Video related fixes

• It’s now possible to midi map two midi knobs/sliders to the Serato Video faders. A standard midi mapping will adhere to the ‘link’ state of the Serato Video fader and a ctrl+shift mapped slider will disregard the ‘link’ state.

This benefits DJs who wish to keep their MIDI capable mixer’s faders un-linked from Serato Video sometimes, but still wish to control Serato Video’s faders with another midi controller.

This means you can now use third party mixers to fade video and audio at the same time, but also independently, just the same way as you can with Rane mixers.

• The Serato Video up fader and cross faders can be shift+ctrl midi mapped so that they adhere to the hardware link settings. A standard midi mapping to these faders will ignore the hardware link states.
• Fixed bug where the mouse/midi/GUI auto cross fader control would not work if fader-link and cue-link was enabled at the same time.
• Fixed bug where, when the Serato Video cue-link button is enabled, the left/right GUI auto cross fade buttons were not working.
• Fixed a bug where the TTM 57SL mapping to the Serato Video auto cross fade control was not working correctly.
• Fixed bug where midi mapping was not possible with some text and image effect controls.
• It should be possible to turn audio effects off now via the Setup > Serato Video > Effects options.

Other fixes

Access Database Corrupt

• Fixed the DJ FX bug where deck assignment settings were not being loaded on startup.

Sixty-One firmware release notes (1.12)

Changes since 1.04

• Fixed bug where control panel is loaded with incorrect parameter values.
• Modified Magnetic Fader curve.
• Added Analog Insert Sensitivity Parameter.

Sixty-Two firmware release notes (1.17)

• Added MIDI Control Layer functionality.
• Added live FlexFX Effect Parameter adjustment from the control surface.
• Added External Insert Sensitivity Parameter.
• Added option to disable automatic lighting of LEDs.
• Added support for smarter and easier user MIDI LED lighting.
• Added support for relaying MIDI Real Time Messages between USB ports.
• Added handling of multiple MIDI channels for MIDI messages sent to device.
• Modified Magnetic Fader curve.
• Fixed undesirable flanging of Echo effect due to fluctuations in tracked BPM.
• Fixed bug in Low Cut Echo so that first reflection is filtered.
• Fixed bug where control panel is loaded with incorrect parameter values.

Change list for ASIO and Core Audio drivers

Sixty-Two 1.1.0f2

• Supports MIDI layers. Removed MIDI channel assignment from driver. The mixer processes MIDI channels based on the MIDI layer.
• Added Analog (External) Sensitivity Control. The +4dBu setting is the normal setting, use the -10dBV setting for external devices with low output voltage (2.0Vrms or lower).
• Added User Button Lighting Control. Enable this option when you want to light button LEDs with MIDI note changes (disables the mixer from providing the momentary button LED flash).
• Passes all MIDI Real-Time messages to/from MIDI system (such as START/STOP/CONTINUE). These are enabled/disabled with the MIDI clock options.
• Firmware 1.17 embedded for firmware update.

Sixty-One 1.1.0f1

• Added Analog (External) Sensitivity Control. The +4dBu setting is the normal setting, use the -10dBV setting for external devices with low output voltage (2.0Vrms or lower).
• Firmware 1.12 embedded for firmware update.

Download Links

Running more than one version of Scratch Live

Installing this version will by default overwrite any previous version you had installed, however it is easy to have more than one version of Scratch Live installed if you wish.

If you have an important gig coming up, you might like to stick with the version you know until you are comfortable with this version. Here’s how to do it:
Windows Users

Before installing, find the Scratch Live executable (by default it is in C:Program filesSeratoScratchLIVE, and rename it. It makes sense to name it in a way that suggests which version of Scratch Live it is. For example, if you’re renaming Scratch Live 1.9.2 call it Scratch Live 1.9.2.exe. When you install the new version, the old executable will not be deleted, and you can choose which you want to run by going into that folder and double clicking on the appropriate executable.

Mac users

Before installing, rename the existing application file as above (eg. Scratch Live 1.9.2) – you have to be admin to rename it. (If you aren’t admin, you can copy it to another location, and then rename it.)

Backing up your data

Before you make any changes to your Scratch Live setup, including installing a new version, as a general rule we highly recommend that you backup your data and your music files. The easiest way to backup your data is to simply copy your Scratch Live folder to another location on the drive:

• For the drive that contains “My Documents” (or your Home drive on Mac), just copy the Scratch Live folder which is in “My DocumentsMy Music” to another location on this drive. Alternatively make a copy of the folder where it already is and rename it by adding the date to the folder name so you know what’s in the backup.
• To back up the database and crates from an external drive, copy the _ScratchLive_ folder (which is in the root of the drive) into another folder on the same drive.

So The Bridge isn’t over after all (real heads know what I did there). Of all The Bridge’s features, I personally find MixTape to be of most interest. I hold out hope that one day, it’ll reach ITCH controllers, but for now these mixers are lucky enough to get some love. And we’ll check it out when we get them in for review. Not long now.