Illegal Regions

I just started a new tune.
I put in a drum loop then recorded a guitar track.
I got "Illegal Regions" message. I clicked OK. It laid down the track OK, apparently.
I recorded another guitar track and got the "illegal region" message again.
Anybody know what this is about? I just upgraded to 7.2.0.
Thanks.

The "Illegal Regions" message is related to your
computer's memory.
Are you running any other programs whilst working in
Logic? If so, quit them, including turning Airport
off.
No airport. I’m usually running Safari, itunes and Mail, oh and the rme fireface Mixer and Settings programs run all the time automatically. But, none of this is any different from my normal work habits before I installed 7.2.
You can also try to free up your memory by opening
File > Project > Clean up..., and remove whatever
files you don't need.
It says “nothing to remove.”
Further:
Go to Preferences > Editing, and lower your "Limit
Multiple Undo Steps".
I did this.
Go to Preferences > Audio > Drivers, and uncheck 64
Busses.
This was already unchecked.
Go to Preferences > Audio > Sample Editor, and reduce
the number of undo steps.
Changed from 5 to 3.
Did you edit your regions after recording? If so,
remove the ones your are not using any longer.
No.
How much free space do you have on your system drive?
It should be at least 20%, f.e. if you have an 80 GB
HD, leave at least 16 GB free.
It’s about 30%
Your RAM seems to be maxed out for your computer, so
we can not improve there. But with 2GB you should not
encounter the problems you have because of a RAM
issue anyway.
Your profile states that you are still on Panther.
You said you recently upgraded to LP 7.2.0. Did you
also upgrade to Tiger (highly recommended!!!)?
I am on 10.4.6
If that is the case, you need to re-install Pro >Application Support:
I didn’t do this yet but will.
Good luck and let us know
I did all of the above minus the proapp install.
Apparently, the problem is solved.
Thank you, sonther, for your help
G5 Dual 2.0 Mac OS X (10.4.6) 2 GB RAM * Logic Pro 7.20

Similar Messages

Illegal Region Number

After months of trouble free running, I'm getting "Illegal Region Number" error messages popping up with no clue as to which region or any other information. Usually (but not always) it happens when I've hit stop after recording an audio track.
It doesn't matter which song I'm in, and I've trashed the preferences.
This error message doesn't affect anything; nothing is lost, and the arrangements in question play just fine, so I just dismiss the error box and continue.
But I'm curious - any insights?

There are a few preferences like lowering undo steps, reducing autmation res and data, as well as emptying (Logic's)trash upon save which free up memory. If you open song information you can see what is taking up memory and what may be expendable. Cutting a region creates multiple regions so removing unused can really help to keep memory low. Leaving lots of room on your sytem drive and upping your RAM will also give you less problems. Committing edits (like if there is a passage with 200 regions and they all have fades on them-gluing them together and removing unused should also free alot of the memory. Some peope really like reorganizing memory, I consider kind of risky. Keeping backups of songs instead of high udos and backups for the glued audio files, etc is another good practice for this problem.
Come to think of it, I have run into this one. Last I had it was while chopping away at bass takes, creating stacks of cuts fades regions, etc. If you let it continue it just starts making things up, region placement, bad fades, anchor voodoo, just little problems like that which don't matter (!?!-JK). Cleaning house, saving all audio files as SDII or AIFF (whichever the existing ones are not), renaming regions were what I had done to overcome the problem long enough to get everything into another session. The memory situation is IMO a huge limitation in Logic, it really restricts what a user can do and requires us to put on the janitor jumpsuit way too frequently : (
7.1.1 was also a bad move for me, some people get along with it fine but it just caused more problems than any other version of 7 on my system.
I would guess this is a Logic issue and not an audio file or system issue and these are the things I do to overcome this problem and related ones. In fact, it is very unlikely IIME that it is anything nut a Logic issue. Good luck and if you see this one start moving things to a new session ASAP.
J

Has anyone ever got the error message "illegal region number"?

it happens everytime i stop recording something, and it never did it before today. and do you guys think this firepod is a perfect match with GB?

I've only seen that error once in 3+ years of using GB, and it was on a crazy project combining 3 separate projects into a 4th.
I spent 3 days trying to track down the problem and eventually gave up and reverted to a previous version of my project because I could neither track down the cause, nor fix the problem.
The one thing I can tell you with absolute certainty is that it has nothing to do with your FirePod.

Illegal region message, Logic Pro X

Hi all,
I have a brand new macbook Pro 15 (late 2014) with 16GB memory. I was receiving this message last night when importing and slicing audio. There was very little happening in the project so its hardly down to memory running out!
Logic Pro X
Macbook Pro
Intel Core i7 4770
I had several instances of battery 4 open with fully loaded palettes.

Nobody seems to know what it means, but I found some tips on how to get rid of it.
https://discussions.apple.com/message/1415891?messageID=1415891&amp%3b#1415891

Logic 10.0.5 is out! Three new drummers, LOADS of fixes.

I have not yet finished reading the release notes, it is almost 5,000 words...
http://support.apple.com/kb/TS4498
Logic Pro X 10.0.5: Release notes
Symptoms
Logic Pro X 10.0.5 is an update to Logic Pro X. Logic Pro X is a new paid version of Logic Pro.
Resolution
Logic Pro X 10.0.5 update
New features and enhancements
Includes 3 new Drummers and 11 new Drum Kit Designer patches.
Significant enhancements to Channel EQ and Linear Phase EQ plug-ins, including:
Redesigned, easier-to-use interface that's also accessible within the Smart Controls area
Double Precision processing provides more accurate filtering, especially for low frequencies
Oversampling option improves high-frequency clarity
Option to apply EQ only to stereo left, right, middle, or side signals
There is now an option to set the Piano Roll to a light background color.
Selected notes in the Piano Roll are now highlighted by a selection frame.
When Logic is stopped or in Play mode, the glyph on the Metronome button in the control bar now illuminates to indicate that “Click while recording” is enabled.
The Shuffle commands are improved (see Logic Pro X Help for details).
User interface
There is now a command to assign region names to track names.
The waveform size in an audio region now adapts to the value of the region gain parameter.
Loops that belong to the same family can now be selected and changed using a new control in the region header.
Logic Pro X now assigns region and Mixer channel colors that are closer to the original colors when opening a project created in an earlier version of Logic.
Option-clicking a disclosure triangle in the Project Audio window now toggles all disclosure triangles in the window.
The Windows menu again lists all currently open windows.
The Mixer can now be reliably resized when in All mode.
Renaming multiple selected Mixer channels now reliably renames all channel strips in the selection.
When creating a duplicate track, the correct track icon and color are now assigned to the duplicate.
The song title is now automatically populated in the Share to iTunes dialog when sharing a song created in Logic 9 or GarageBand for iOS.
It's once again possible to browse or load patches onto the Output channel strip via the Library.
The View menu items One Track and Selected Regions in the Piano Roll are now disabled when Link mode is disabled.
Performance
Improves processor balancing for multi-output software instrument configurations.
Improves handling of multiple displays on OS X Mavericks v10.9.
Resolves an issue that in some cases might cause audio clicks and pops when scrolling.
Moving an automation line while playing no longer spikes in CPU usages, or clicks and pops in the audio output.
Resolves an issue that could cause clicks and pops in the audio output when adjusting the gain or output level settings during playback in the various plug-ins.
Logic's interface no longer freezes when using the Native Instruments Maschine controller to adjust two macro controls simultaneously.
Fixes an issue in which a warning about not enough memory might be displayed when performing Undo after editing a protected track.
Adjusting the frequency controls while playing audio through the Stereo Spread plug-in no longer causes audible zipper noise.
Improves the performance of scrolling when dragging regions in the Tracks area beyond the currently visible section.
Playing notes live into the Arpeggiator plug-in no longer sometimes leads to spikes in CPU usage.
Fixes an issue that could cause a spike in CPU usage when recording near the end of a project.
Logic 9 projects that contain a macro object in the Environment now behave more reliably when opened into Logic Pro X.
Multiple instances of the Scripter plug-in no longer have the potential to cause stuck notes.
The Scripter plug-in is no longer prone to causing stuck notes when using the Delay Note Until Next Beat preset.
Switching between presets in the Space Designer plug-in no longer sometimes results in noise.
General
Regions copied from a Track Stack can now be muted as expected even when they are within a Track Stack that is muted.
Deleting an audio Track Stack while it was soloed no longer leaves all the remaining tracks muted.
Entering a new crossfade value in the Region inspector for multiple selected regions now works as expected.
Region-based automation data beyond the end of a region is now chased properly even when playback is started after the last automation node within the bounds of the region.
Logic now maintains the correct relative levels when automation on multiple tracks belonging to the same Group are copied by dragging.
Resolves an issue in which track automation might be deleted when switching patches.
The default display setting when showing automation on Track Stacks is now Volume, instead of Display Off.
A track is now created as expected when using a control surface to set the automation mode of a channel strip not previously assigned to a track.
Moving a SMPTE locked region can no longer cause the automation on the track to move.
The position of the automation line no longer jumps unexpectedly when it is selected after creating 4 automation points with a Marquee selection.
Adjacent automation points of the same value are no longer sometimes inadvertently deleted when moving automation points on a grouped track.
The Repeat Section Between Locators command now includes automation on tracks that contain no regions in the repeated section.
When using Touch mode, Logic no longer writes unneeded automation points at the held value when holding a fader at the same position where there is an existing automation ramp.
Writing automation to an Aux not assigned to a track can no longer potentially cause tracks in a Track Stack to be rerouted to that Aux.
Copying multiple regions where only some affected tracks contain automation no longer activates Automation Read mode on the channel strips that have no automation.
Chase now works as expected for MIDI controllers on channels other than channel 1.
Takes are now shortened as expected when the take folder containing them is shortened by an edit operation and No Overlap mode is enabled.
Fixes an issue in which the visible area might jump unexpectedly when comping in a take folder that was not on the selected track.
Fixes an issue that caused some audio regions to be immovable when duplicate regions are packed into a take folder.
Packing regions with names containing non-ASCII characters into a take folder no longer creates garbled take names.
Numbers assigned to MIDI takes now increment reliably.
Expanding a take folder no longer potentially causes the playhead to fall out of sync with the audio output.
When using OS X v10.9, the playhead in the Audio Editor now consistently maintains the correct position when switching from Flex Time to Flex Pitch mode.
It's now possible to set a loop to a length of less than 1/16 note.
The position of beat markers in the Global Beat Mapping track are now updated appropriately when using the various Cut/Insert Time commands.
Inserting a beat marker in the Beat Mapping track no longer creates unexpected tempo events in some circumstances.
Expanding a take folder no longer potentially causes the playhead to fall out of sync with the audio output.
Resolves an issue in which some MIDI notes might unexpectedly change position when Beat Mapping.
Adding a Beat Mapping marker no longer intermittently removes existing tempo events.
Inserting a fade-in using Shift-Control and the Pointer tool now works consistently.
Using the Fade tool to set fade-ins on multiple regions in a set of grouped tracks now works reliably.
Dragging regions on multiple grouped tracks with the Drag Mode set to X-Fade no longer potentially results in crossfades of varying lengths.
The Delete command now works as expected on selected regions that are inside a collapsed Group in the Project Audio window.
It's now possible to add a green Apple MIDI loop to the Tracks area as an audio loop by dragging it from the Loops browser while pressing the Option key.
Logic Pro X no longer creates separate tracks for non-overlapping regions when unpacking folders in projects created by earlier versions of Logic.
Using the menu that appears when pressing the Metronome button in the Control Bar, it's now possible to set the metronome to sound only during count-in.
Improves the reliability of Undo in several areas.
The Mixer window no longer intermittently moves when scrolling past the minimum or maximum value of the fader using a scroll wheel or gesture.
It's now possible to select or open folder tracks in the Mixer.
Right-clicking an Aux or Output channel strip in the Mixer and selecting Create Track now behaves as expected even if the channel strip is not initially selected.
Command-click again works reliably to deselect a Mixer channel within a selected group of channels.
The display of audio waveforms of regions in a track no longer change unexpectedly when enabling or disabling the Groove status on a track.
Looped regions inside a folder now update the point they are supposed to stop playing after extending the length of the folder.
Overwriting an existing project no longer potentially leaves assets from the original project in place.
When creating a new project from a Logic 9 template, the default save path is no longer the location of the template.
Improves the mapping of Smart Controls to channel strip settings created in Logic 9.
The Follow Tempo parameter in the Region inspector is no longer incorrectly disabled for Apple Loops in songs last saved in GarageBand 6 or earlier.
Clicking and holding down on the upper-right corner of a region no longer unexpectedly enables looping in the Region inspector, with a loop length of zero.
The Region Inspector no longer displays a Loop checkbox for selected Track Stack folder regions.
It's once again possible to disable Quantize in the Region Inspector for a region on a track slaved to a Groove Master track.
Saving a song created from a template no longer resets the tempo to 120 BPM.
Text for alert messages now always displays correctly on control surfaces.
Changing Region inspector parameters for MIDI regions on the main track of a Track Stack now behaves as expected.
It's again possible to change the Transpose value in the Region Inspector using the + and - keys.
Logic now consistently responds to Play or Stop key commands when a floating Region inspector window is open.
It's no longer possible to give the same name to more than one project alternative.
MIDI played from the Musical Typing Keyboard and Logic Remote is now routed through the Physical Input object in the Environment, which allows Environment processing of MIDI as it is being played into Logic from these sources.
Logic no longer adds 2 extra frames to the value when entering a SMPTE position in a project set to a non-drop frame rate.
Regions copied by option-dragging in projects with a start position earlier than bar 1 now end at the desired position.
Moving the first arrangement marker in a project no longer inadvertently moves other arrangement markers.
Resolves a rare issue that could cause the timing of a track in a project with many tempo changes to be altered after turning Flex on and then off.
Logic now asks the user to save the project when closing a project immediately after entering text into the Project Notes area.
It's now possible to consistently add, remove, or edit plug-ins on tracks that were frozen in Source Only mode.
Pressing the Control key while dragging a region with the Snap Mode set to Bar now moves the region by beats instead of ticks, as expected.
Editing the left border of an audio region now behaves as expected when the Snap setting is set to “Snap Regions to Relative Value”.
Resizing a region with the Snap setting set to “Snap Regions to Absolute Value” now behaves as expected.
Resolves an issue that caused an event in the Event List to move later than expected when editing its position.
The “Capture as Recording” command now works as expected when multiple MIDI tracks are record-enabled.
It's now possible to preview sections of an audio file outside the current region borders by clicking the area in the Project Audio window.
The tap-to-click option for trackpads now works reliably with all drop down menus.
The “Discard Recording and Return to Last Play Position” key command now reliably discards the recording.
It's again possible to use the Tab key to navigate to the next control while working with plug-ins in Controls view.
The MIDI Activity display now shows chords as they are played when using Musical Typing.
All currently found audio files are now reliably saved with a project when using Save As or Save a Copy As with a project in which one or more audio files are missing.
The name of a project is now correctly updated after saving a project created from a template.
Fixes an issue in which clicking on the level LED in the track header did not select the track.
Resolves an issue in which changes made to the setup for Mackie Control and other MCU-compatible control surfaces were not saved by Logic Pro X.
Setting the Display Time preference to “SMPTE/EBU with Subframes”, “SMPTE/EBU without Subframes,” or “SMPTE/EBU with Quarter frames” can no longer cause the time display to jump unexpectedly.
Saving a project for the first time no longer resets the record path when it was previously set to an external path.
Performing undo in the Piano Roll or after deleting a flex marker no longer has the potential to unfreeze currently frozen tracks in the project.
Sample rate, tempo, and key information is now reliably stored within template files.
Fixes an issue in which the Repeat Regions dialog did not have key focus when opened, making it necessary to click it with the mouse before pressing Return to confirm the operation.
Individual MIDI Draw points in the Piano Roll are now easier to grab.
Deleting a track no longer has the potential to inadvertently delete regions on other tracks.
Cut/Insert Time edits no longer add unexpected tempo changes.
Scrubbing the SMPTE display in the LCD no longer moves the playhead to the wrong position.
Copying an arrangement marker to a position between two other arrangement markers now moves the end-of-song marker to accommodate the new section, as expected.
Audio
Audio regions now appear as expected in the Audio Editor, even when cycle is enabled and there are no audio regions within the cycle area.
Flex Pitch now correctly detects notes for take regions that have manually inserted flex markers.
The timing of notes played during the count-in on EXS24 or Drummer tracks is now more reliable.
Pasting an audio region into a take folder now correctly places the region on the selected take lane.
When saving an EXS instrument, the default save location is now ~/Music/Audio Music Apps/Sampler Instruments.
Editing the start point and anchor in the EXS audio editor now consistently alters playback as expected.
Logic no longer overwrites an existing audio file of the same name when performing a bounce with the option to create a split stereo file enabled.
Audio tracks assigned to output to a bus now consistently maintain that assignment when imported into a different song.
User-defined controller assignments now work as expected to control MIDI plug-in parameters.
The Record Repeat command now deletes the previous recording when used after recording in Cycle mode.
Quantize now operates reliably on takes that are displayed in the Audio Editor.
The Tuner window is no longer affected by the Content Link setting of other plug-in windows.
Audio now plays for multiple cycle iterations when using marquee selection to define the cycle area.
When the Edit command “Analyze Audio for Flex Editing” is used, Logic now properly resets any existing pitch edits on the selected audio files.
Command-clicking a selected note in Flex Pitch mode in the Audio Editor now deselects the note, as expected.
Setting a track to Flex Edit mode with the Slicing algorithm no longer processes the track with Flex if no edits have been applied.
It's again possible to set Software Instruments to mono.
Logic no longer creates an extra audio file when merging or format-converting audio files.
Resolves an issue in which the Mixer did not show the 8th bus send on a channel strip.
Changing the input format of a stereo output channel strip to mono now creates a second mono output channel strip on the Mixer for the other channel in the stereo pair.
Setting an external recording path now reliably resets the Audio Assets setting. Conversely, enabling the Audio Assets setting now disables an externally set recording path.
The compressor meter in the channel strip is now in sync with the meter in the plug-in window.
Drummer
Improves the translation of articulations when an Ultrabeat-based patch is assigned to a Drummer track.
When a project starts on an upbeat, a Drummer region at the project start now automatically creates a fill at the beginning.
Changes to Drummer regions are now reliably applied when the regions are set to follow a flexed audio track.
MIDI editors
The Link mode button is now available for the Piano Roll editor.
The “Limit Dragging to One Direction” setting now works as expected in the Piano Roll.
It's now possible to grab notes shorter than 15 ticks for editing in the Piano Roll.
Double-clicking a region with MIDI Draw enabled now consistently opens or closes a MIDI editor.
Resolves an issue in which recently recorded MIDI notes might disappear from view in the Piano Roll when recording with cycle engaged.
It's again possible to alter the pitch of notes in the Piano Roll via MIDI input.
Using Option-Shift to edit the end points of multiple selected notes to the same position in the Piano Roll Editor now works as expected.
In the Piano Roll, it's again possible to use Option-Shift in conjunction with the Velocity tool to set all selected notes to the same velocity.
An Event Float window that is linked no longer switches unexpectedly to the Region level when using arrow keys to move from note to note in the Piano Roll.
Pasting events in the Piano Roll when the playhead is to the right of the region border will not trigger the error “Illegal Region number”.
It's now possible to copy a note in the Piano Roll to a different pitch at the same position when the note starts before the left edge of the region.
It’s now possible to move notes in the Piano Roll by increments smaller than 13 ticks when the “Limit Dragging to One Direction” setting is enabled.
User-inserted rests no longer incorrectly appear as notes in the Piano Roll.
Copying a muted note in the Piano Roll now creates a muted copy of the note, as expected.
Fixes an issue in which some note events might not be selectable in the Step Editor.
The contents of the Event List are now updated properly when deselecting a region from a multiple selection while Content Link mode is enabled.
The Event List now displays the correct LSB values for 14-bit pitch bend events.
Editing Release Velocity values in the Event List now behaves as expected.
The “Copy selected events” option in the MIDI Transform window now behaves as expected.
Score Editor
Fixes an issue that could cause the menu option for switching between Parts and Score view in the Score Sets window to disappear.
Double-clicking a region with the All Instruments filter setting active now reliably reveals all regions on that track, rather than just the single region.
The contents of the Event List editor are more consistently updated when changing the region selection from the Score window.
Newly inserted key signatures no longer display “xx Major” in some circumstances.
The Chord Grid Editor now correctly names Add 9 chords.
The clef menu no longer disappears for a Mapped Instrument staff style set to “No Clef”.
It's again possible to create a new Chord Grid library that uses an alternate tuning.
It's now possible to adjust the Velocity setting in the MIDI Meanings settings window by scrubbing the value with the mouse.
The length adjustment in the MIDI Meanings settings window can now be adjusted via a pop-up menu.
In the Staff Style window, the check marks indicating that a style is used in the current song now reliably update to reflect changes when Content Link mode is off.
Grace notes now scale properly when the scale setting of a Score Set is less than 100.
Resolves an issue that prevented reassigning instruments assigned to a Score Set after performing certain other edits.
Fixes an issue that prevented naming a floating score Part box set.
Plug-ins
Solo now works as expected on channel strips using an external I/O plug-in
Ultrabeat can now find samples that have been relocated from the default install location.
Ultrabeat now correctly applies the Fine Pitch adjustment to all triggered samples when trigger mode is set to Multi.
It's now possible to halve/double the current rate of the Arpeggiator plug-in by clicking the Slow/Fast buttons.
The ES1 synth plug-in can now be set to offer 32 and 64 voices per instance.
The Scripter plug-in now allows System Realtime MIDI events to pass through.
The Scripter plug-in now offers an option to keep current control values when recompiling a script, rather than resetting all values back to their defaults.
The Scripter MIDI plug-in now includes a Set Parameter function.
Switching between Vintage Electric Piano patches while holding notes no longer potentially results in momentary jumps in level.
The Vintage Electric Piano no longer potentially creates audible pops when switching patches when the Drive is enabled and set to Type II.
It's now possible to continue working with the Scripter editor window when Logic Pro X is not in focus.
The Surround Compressor plug-in now properly shows all the new circuit types available in Logic Pro X.
It's again possible to copy or paste settings in the Space Designer plug-in window.
The order of controls in the Retrosynth Filter Envelope and Amp Envelope sections has been reorganized to improve usability.
The plug-in window no longer appears empty for Waves plug-ins opened in projects created in Logic 9.
Fixes an issue in which inserting a plug-in on multiple stereo Software Instrument channel strips would insert mono versions of the plug-in on some channel strips.
EXS24 or Kontakt settings are no longer removed from a song if the Audio Device buffer size is changed before saving the song.
Resolves an issue in which adjusting parameters on the Channel EQ while playing back might cause minor clicks and pops in the audio signal.
Moving an Amp Designer instance to a different plug-in slot no longer sometimes changes its sound.
“Save as Default” for Audio Unit presets again works as expected.
Video
It's now possible to exchange movie files in a project by dragging a new movie file into the Movie window or the Movie inspector.
Logic Pro X can now work with the following professional video codecs, if OS X Mavericks v10.9 and the codecs are installed: Apple Intermediate Codec, Apple ProRes, AVC-Intra, DVCPRO HD, HDV, XDCAM HD / EX / HD422, MPEG IMX, Uncompressed 4:2:2, XAVC.
There is now a Show/Hide Movie Window command in the View menu when the current project contains a movie.
Resolves an issue in which some movies that were compatible with QuickTime X did not play in Logic Pro X.
Exporting audio to a movie with a portrait orientation no longer causes the movie to rotate 90 degrees.
Logic is now able to export surround AAC audio to a movie even if the original audio in the movie was originally kept.
The visible frame of a movie now updates as note lengths in the Piano Roll are changed.
Import/export fixes and improvements
XML projects imported from Final Cut Pro X now contain volume and pan automation when opened in Logic Pro X.
Exporting a project as an Final Cut Pro/XML file with the “Export as Final Cut Compound Clip” option enabled now behaves as expected.
Includes several improvements to the way Logic handles audio sample-rate conversion when importing Final Cut Pro XML.
Logic now shows a progress bar when importing large Final Cut Pro XML projects.
32-bit float audio files in Final Cut Pro XML projects are now converted to 24-bit files during import so they play properly when imported into Logic.
The start time of imported Final Cut Pro XML projects is now consistently correct.
It's now possible to export Music XML when the Score window is in linear view mode.
Logic no longer shows multiple alerts when importing a Final Cut Pro XML project containing videos in a format not supported by Logic.
Songs created in GarageBand 6 no longer load in Logic Pro X with an extra channel in the Mixer.
Fixes an issue in which audio in a song imported from GarageBand 6 might play back too fast in Logic Pro X.
Logic now offers to include embedded tempo and marker information when using Track Import to bring an audio file into a project that contains no other audio regions.
Simultaneously dragging multiple MIDI files into the Tracks area now behaves as expected when using No Overlap mode.
The default destination path for exported MIDI files is now the project folder instead of ~/Music/Logic.
When importing projects, there is now an Add All button in the Aux import dialog.
The user settings in the Bounce window are now retained after sharing to iTunes.
Split stereo SD2 files no longer incorrectly import as AIFF files when the WAV file option is enabled.
The “Share Song to iTunes” command now creates a playlist with the name entered if there is not already an iTunes playlist with that name.
MIDI events that precede the start point of a region are no longer included when the region is exported as a MIDI file.
Stability and reliability
Includes several fixes related to stability and reliability, including to resolve issues that could cause Logic to quit unexpectedly in these circumstances:
When changing the length of a time-stretched region
When importing tracks from another project
When recording with the color palette open
When bypassing an instance of the Maschine plug-in
When exporting Music XML after applying Enharmonic Shift to some notes
When changing the range on an Environment fader whose style was set to Text
When quitting a project that has a Surround Compressor inserted on a channel strip
When removing a control surface from the Control Surface setup window when the Logic Remote is also present
When changing the range value of a Smart Control during playback.
When reapplying a Time and Pitch operation after undoing a previous one
When dragging an audio region from a take folder to a new song

Thanks Erik,
If nothing else, this huge list of updates and fixes, shows clearly that the Logic Dev team is working hard on fixing and improving LPX to a major degree.... and from the list of fixes done.. show they do read the bug reports submitted!
As an aside....
I recall how all the 'naysayers' prior to LPX (and in some cases, since...) were proclaiming how Logic was dead, the team was being disbanded, we won't see any further development, the Dev team doesn't listen or care... and so on....... I wonder where those people are now?

ACPI BIOS is attempting to write to an illegal PCI Operation Region

I've seen a lot of posts from 2008-2010 about people getting this error in windows, but no solutions.
ACPI BIOS is attempting to write to an illegal PCI Operation Region (0x41c)
Has anybody had any success in fixing it? For me, I crash after running a game in windows for about 5-10 minutes. Computer freezes, have to do a hard restart. This error is found in the system log.

I know Nvidia has had some teething problems and the Mobility type cards on some have issues with some games.
Have you tried any of those Windows "Registry fixer" type utilitys or similar type maintenace applications? I've been told that Windows has to be "defragged" fairly often and the "Registry" fixed, etc. I'm by no means an expert, just from what i've read from other forums and the like. I just read stuff with a "grain of salt" and just average it out.:)
I buggered my XP boot setup when I was messing with installing Windows 7 so I can't tell you what I used, I THINK it was AVG, it's a virus checker also. (Free's a very good thing.) My kid (went to the dark side) had me download Windows Defender for W7 and so far it hasn't screwed anything up yet. (a whole month now) So far Windows 7 plays everything I have so I haven't really tried too hard to fix XP. Yeah, kind of a pain to redo everything.
My only other answer would be to try the Microsft forums and see if they have any answers. There are areas there that I've never been able to find again tho, it's so "All over the place" trying to find stuff, for me any way.
Sorry I can't help more.....

ORA-01741: illegal zero-length identifier

Hi Friends,
I am facing a weird situation while creating a report with region having type as SQL Query(PL/SQL function body returning SQL Query).
I have a package function which takes 4 parameters and returns a SQL query in a varchar2 variable.
Now when I have the following code in my region source and on applying changes is showing ORA-01741: illegal zero-length identifier
DECLARE
l_query VARCHAR2 (5000);
BEGIN
SELECT apx_dashboard_pkg.f_int_monthly_grid (:p5_1, :p5_2, :p5_3, :p5_4)
INTO l_query
FROM DUAL;
RETURN l_query;
END;
If I change my code as below by passing values and run, then it does the job perfect.
DECLARE
l_query VARCHAR2 (5000);
BEGIN
SELECT apx_dashboard_pkg.f_int_monthly_grid(200712,
'IC',
3,
'AVARO'
INTO l_query
FROM DUAL;
RETURN l_query;
END;
I have no clue where I am doing wrong.
Please help me.
Thanks,
Raj.

Thanks guys for your responses.
Varad,
I have tried with 'Generic Column Names' and it worked wonderfully.
Scott,
I would definitely consider your point because it might be the reason for erroring out in some of my pages in the application.
Thanks a lot.

To check illegal skype access of my skype account

Hi,
I was not online on skype and attending one business meeting. My friend called me and said that I abused him on skype while I was not accessing that time. When I access my skype account. I found that he was true. Somebody has accessed and abused him. The same time I changed my password. I would like to know that how am I get report of the person who accessed illegally my account from which region and from which IP Address. Can I take a legal action against the guy who illegally accessed my account. Many thanks in advance to help me to arrange the details or to get information of illegal access.
Best regards,

Hi, Jaminy, and welcome to the Community,
Report this incident to your local law enforcement agency. The police have the resources to obtain the information you seek from Skype directly; Skype's Customer Service representatives do not have access to this information.
Here is a link to start with: contact customer service
Best regards,
Elainem77
Was your question answered? Please click on the Accept as a Solution link so everyone can quickly find what works! Like a post or want to say, "Thank You" - ?? Click on the Kudos button!
Trustworthy information: Brian Krebs: 3 Basic Rules for Online Safety and Consumer Reports: Guide to Internet Security Online Safety Tip: Change your passwords often!

DVD drive region semi-free?

I've been having a small issue with my iMac and DVDs.
First off, I'm in Region 4, which is what my mac is set to.
Secondly, I have a lot of discs from other regions.
Now, my discs that are region one will not play in the DVD player (as expected), and prompt me to change the drive to region 1 to play them, warning of 4 changes left (also as expected).
Now, the thing is, some of these region one discs, that wont play in DVD player, will play fine in VLC, yet others wont. This is the thing that's puzzling me.
Now, my drive is the MATSHITA DVD-R UJ-875 type, which I've read a lot about, but as it will play some out of region discs, yet not others, does anyone know what's up?
Now, to top that all off, I'm in Australasia, where it's illegal to ship RPC-2 Drives, so if there is firmware blocking some of my discs, can I get apple to fix it because of that?
All in all this is mainly an inconvenience, since I can play any disc on the DVD player in my living room (like I said, you can't buy region locked DVD players here), but it'd be nice to play them on my Mac (which is in my bedroom) if I want to.
Any help?

Now, the thing is, some of these region one discs, that wont play in DVD player, will play fine in VLC
Be careful about this. It may not apply in your case, but when I got my new iMac recently I put a Region 1 DVD in (I'm in Region 2) and accessed it in VLC without any warnings of any sort: but the next time I played a Region 2 DVD in DVD player it said it was in Region 1 and gave the usual warning: so VLC may still be using up your changes - without telling you.

Templates in DW CS5.5 and editable regions

I have a template page that has an editable region defined as follows:
<div class="sidebar1">
    <nav>
      <ul>
        <li><a href="#">Home</a></li>
        <li><a href="#"></a></li>
        <li><a href="#"></a></li>
        <li><a href="#"></a></li>
        <li><a href="#">Members Only</a></li>
        <li><a href="#"> Gallery</a></li>
        <li><a href="#">Constitution</a></li>
        <li><a href="#">Links</a></li>
      </ul>
    </nav>
    
</div>
      
<article class="content">
    <h1>BCEF Clubs</h1>
    <section>
other code goes here
</section>

Note the </div> tag after the start of the editable region. This is a proper tag, as it is needed to close the sidebar1 div.
When it is not in an editable region, the </div> does not show up in yellow in design veiw and it works in every repect.
When the editable region is introduced, the </div> shows yellow in design view, and it works in every respect.
It validates using the W3C validation page.
Pages built with it also show the tag as yellow but they do not display it when live or in a browser.
If I delete the </div> as dreamweaver suggests, the css breaks and the page will not work.
It seems that DW thinks that this is an illegal tag. If I click my mouse on the  tag, and collapse the tag, all the code in the editable region + that in the sidebare 1 div, ( even that before the editable region begins) collapses. The editable region does not allow edits in the sidebar1 code outside the region.
I need to put the editable region within part of the sidebar 1 div so that I can add aditional floated items in the sidebar 1 div if needed later.
Is this a bug or am I missing something?

This would make more sense.
</nav>

<p>Some unique sidebar1 content goes here</p>

</div>
<article class="content">

<h1>Unique heading here</h1>
<section>
other code
</section>

</div> 
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
Message was edited by: Nancy O. Forgot to close the .content div.

Getting my macbook pro DVD player to become region free

I travel a lot. The last 3 years has been 5 continents and over 20 countries. The fact we now live in a globally accessible world means this DVD region BS needs to stop. Good example, in the next 6 weeks I will travel/live in 3 different DVD regions. Why I shouldn't be allowed to use my laptop for work/travel everywhere I go is ridiculous.
Rant aside, I have found a few things online, but am wondering if there's something authoritative as to how to go about doing? Also, are there any complications vis-a-vis apple care? Or any other issues that I should be aware of?
Thanks.

This is a murky subject. Basically, DVD region codes aren't meant as a DRM measure since they don't affect the copying of a work, or restrict playback by an individual, only by device (there's nothing preventing you from having a drive for every region). For members of the World Trade Oragnization (like the USA), it doesn't qualify as DRM either and, in fact, it technically not permitted by terms of the WTO's General Agreement on Tariffs and Trade and Technical Barriers to Trade agreements.
So, why do RCS-enforcing drives still exist? First, because DVD producers want them to and require DVD manufacturers to include it in order to license the DVD trademark and CSS technology. Technically speaking, DVD manufacturers are allowed to provide mechanisms to disable region codes in their products (which is why most set-top boxes have a way to disable them by typing certain codes using the remote control). In response to the WTO rules: the availability of region-free options, plus the ability for people to own separate players for specific regions, allows the media companies to argue that RCS doesn't constitute a barrier to trade or a market discriminator. So, as long as there exists means to circumvent RCS restrictions, the restrictions are legal to implement (so goes the argument).
Why do media companies region code their disks? By dividing the world into economic subdivisions, they can exercise price controls / discrimination. In fact, Blu-Ray discs have different market segmentation because the economics underlying the controls have changed.
Anyway, the gist is that while it's perfectly legal for you to make your player region-free (in fact, in several parts of the world, you'll find that RCS is officially considered an illegal restraint on free trade), there's no official mechanism for you to do so on your Macintosh computer. Depending on the model of drive you have i, you may be able to find replacement firmware on the Internet and update it, but doing so will void your warranty from Apple.
Most people will simply purchase a small USB external drive that's region-free or can be flashed to be made region-free. Depending on what part of the world the drive was to be marketed in will determine whether the drive is region-free by default. Generally speaking, only drives from Matsushita drives are consistently RCS-enforcing. In many countries, code-free or region-free players are the default.

DVD player region permanently set

I recently bought a used MacBook. The optical drive handles music CDs, CD-ROMs and DVD-ROMs fine, but it won't play movie DVDs. Apparently the previous owner(s) changed the DVD region setting five times, so it is now permanently set to something other than Zone 1 (North America).
My question is: what's the fix for this? I'm betting just reinstalling the DVD Player software won't reset the region. Will replacing the Superdrive with a new one solve the problem, or is there some software setting somewhere in addition to the hardware?

Well, as usual nobody could help me so I found my own fix. The answer is that the setting is the firmware of the DVD drive.
There is a fix, but it's probably illegal. I finally found the right combination of free downloads to "flash" the firmware and replace it with a region-free version. There were many warnings about bad things that could happen, but since my DVD drive was already basically worthless I didn't have much to lose.
1. Use "DVD Info X" to verify the firmware settings.
2. Download the firmware hacks, but they only work in Tiger (OS 10.4)
3. Download "Matsushita Flasher" which allows the hacks to run in 10.6
4. Download "RegionX" which allows you to manually set the region code once the hacks have been applied.
Problem solved.

Session state of page item different from one region to another region

hi,
on one particular page I have two regions. A page item (LOV pop-up) is set in the first region. I leave this region with a button and jump back with a branch to the same page. The page item has now the selected value (as is shown by session state window). So far so good.
The second region (SQL query type) uses this page item. However, for some reason the page item is NULL in that second region.
Can anyone explain this behavior ?
ron

thanks Joel,
I did already what you suggested. The title in region 2 is evaluated to the same value as in region 1.
The SQL query (that actually runned with identical syntax before) is:
select bla from blatable where bla = :P920_RU
this generates:
report error:
ORA-12801: error signaled in parallel query server P000
ORA-01741: illegal zero-length identifier
So apperently the bind variable is evaluted to (or cached as) NULL.
I noticed something strange in the session window. There are several page items in the application. All of them are listed in the 'Session State' region. The page item that makes problems is the only one that is also listed in the 'Page Items' region. It is even listed when I start the session window from another page. Weird.
any other ideas ?
Actually, how could you possibly clear session state between rendering two regions ?
Ron

DVD Region Code

Problem:
Most of my DVDs have the Hong Kong region code (whatever it is) and my macbook will not play those dvds only the north american region coded ones. Is there some kind of codec to let me play these other DVDs which make up 95% of my DVD collection?
Thanks

Hi Alex
I'm afraid the answer is most likely to be no. But this depends on which model of DVD drive you have. If you have a Matshita drive then you probably haven't got a chance. Other drives may play other region DVDs using VLC media player . The only other option is to flash the firmware in your DVD drive, which I understand is at least potentially illegal. Googling the web will return information on this, and make sure you are aware of the risks of any action you might want to take.
Matthew Whiting

Region Free DVD Player

Is there any way to make the DVD Drive in my iMac region free? I have looked through some google searches and have not had much success. I know I could just rip it with HandBrake or MacTheRipper and then watch it but that is a lot of work just to watch a movie. I also have VLC on my computer and that works. But is there any way to permanently change the DVD Drive's firmware to region 0 (all) so that I could watch the DVD in DVD Player or Front Row?
Also would this be illegal and would it void my AppleCare warranty?
Info:
MATSHITA DVD-R UJ-846:
Firmware Revision: FB2U
Interconnect: ATAPI
Burn Support: Yes (Apple Shipped/Supported)
Cache: 2048 KB
Reads DVD: Yes
CD-Write: -R, -RW
DVD-Write: -R, -RW, +R, +RW, +R DL
Burn Underrun Protection CD: Yes
Burn Underrun Protection DVD: Yes
Write Strategies: CD-TAO, CD-SAO, DVD-DAO
Media: No

The short answer is no. This is a longstanding issue with these drives and a very common complaint.
You need to purchase an external drive. Don't forget to submit a feature request for the region free drives (or, at the very least, the ability to swap out the drive with one that is region-free).
Region codes haven't been valid for years. It's a pretty serious issue. I believe Apple even sells region-locked drives in Australia and New Zealand (where region coding is an illegal trade practice).

Illegal Regions

Similar Messages

Maybe you are looking for