Форумы для гитаристов
У нас самая большая гитарная тусовка

В связи с текущими событиями на форуме вводятся новые правила. Ознакомление обязательно.
- Форумы для гитаристов »
- Гитара »
- guitar.studio »
- Тема: Cockos REAPER — общая тема (все вопросы оставляем тут)
Страницы: [ . 255 256 257 258 259 260 261 [262] 263 264 265 266 267 [Дальше >>] Вниз
Автор Тема: Cockos REAPER — общая тема (все вопросы оставляем тут) (Прочитано 407127 раз)
0 Пользователей и 1 Гость просматривают эту тему.
Страницы: [ . 255 256 257 258 259 260 261 [262] 263 264 265 266 267 [Дальше >>] Вверх
- Форумы для гитаристов »
- Гитара »
- guitar.studio »
- Тема: Cockos REAPER — общая тема (все вопросы оставляем тут)
Could not import 1 of 1 items reaper что делать
Drop and drag mp3 files gives me the «Could not import 1 of 1 items!» box.
If I INSERT> Media, it drops in 2 measures only and shows OFFLINE, no waveform, no playback.
I can convert to wav and they’ll drop in just fine.
I found an old thread discussing this and made sure under
Preferences> General> Paths that Store all peach caches in alternate path
is set to the Users\AppData\Local\Temp\REAPEAKS and that (under Media)
«Store peak caches in alternate path if unable to write to media file directory» was checked, too.
This is a gigantic pain in the ass, any help is much appreciated.
| keeppracticing |
| View Public Profile |
| Send a private message to keeppracticing |
| Find More Posts by keeppracticing |
Human being with feelings
Join Date: May 2017
Location: Leipzig
Posts: 6,472
Which program did you use to create the mp3? And did converting it with another tool into mp3 do the same thing?
Is it happening with all mp3s or just selected ones? Was it always the same way or did it «just start» recently?
Is it the same thing with FLAC, video, off, opus, etc?
| Meo-Ada Mespotine |
| View Public Profile |
| Visit Meo-Ada Mespotine’s homepage! |
| Find More Posts by Meo-Ada Mespotine |
Human being with feelings
Join Date: Apr 2013
Location: Atlanta
MP3s were emailed to me, just found out they were purchased on iTunes. (Even after converting to wav, importing into my sessin, editing, and then re-rendering to a new mp3 file, the metadata still showed up in Windows Media Player displaying the name of the artist and song title from the 1st of the 3 songs I mashed up — perhaps it’s an iTunes anti-piracy thing?)
When I take the wav file that I converted it into and convert it back to mp3, the new mp3 imports properly into a session.
This is the first time this has ever happened to me, but I’m on a brand new Lenovo P70 laptop Win 10. I just tried importing mp3s I have, both purchased ones and self made, and both imported properly.
(I don’t have any video or FLAC files to test out.)
Last edited by keeppracticing; 04-15-2018 at 04:53 PM .
| keeppracticing |
| View Public Profile |
| Send a private message to keeppracticing |
| Find More Posts by keeppracticing |
Human being with feelings
Join Date: Dec 2012
Posts: 13,322
@keeppracticing, could you please share the file with me, so I’ll try to investigate? Of course, I’ll delete it after.
__________________
Donate ► Chroma — coloring tool ► SoundCloud ►All the REAPER names
Human being with feelings
Join Date: Apr 2013
Location: Atlanta
MP3 files emailed over, thanks!
| keeppracticing |
| View Public Profile |
| Send a private message to keeppracticing |
| Find More Posts by keeppracticing |
REAPER Could Not Import 1 Of 1 Items (Step-By-Step Fix)

If you are having trouble importing media items into REAPER, there is either something wrong with the file you are trying to import, or it is an invalid file format. Although REAPER is compatible with a long list of file types, there are a few that it does not support.
Contents show
Trouble Importing A Media Item In REAPER
What is incredible about the average modern DAW (Digital Audio Workstation) is that it allows music producers to work with many different media files such as audio, music, video, image, and MIDI.
However, there is nothing more frustrating than trying to import a file into your REAPER project only for REAPER to say, ‘REAPER Error: Could Not Import 1 of 1 Items!’.
In this step-by-step guide, I will walk you through how to import media items into REAPER.
REAPER Error Could Not Import 1 of 1 Items
Sometimes, you will get an error message in REAPER that says, ‘REAPER Error: Could Not Import 1 of 1 Items’.
This means that the file you are trying to import is either corrupt/not intact or an unsupported file format.
What You Will Need To Follow This Tutorial
Here is a list of what you will need to follow in this tutorial:
- REAPER DAW
- A file converter in some cases (very unlikely)
Step One – Troubleshoot
The first thing you will want to do if REAPER gives you the message, ‘REAPER Error: Could Not Import 1 of 1 Items!’ is some troubleshooting to figure out your problem.
Your problem could be either that the file you are trying to import has issues or is corrupt, or it could be that you are trying to import a file type that REAPER does not support.

Step Two – Getting An Acceptable File
If your problem is that the file is corrupt or missing data, you will need to go back to the source where you received it and get an intact file.
This could mean emailing the person you’re collaborating with to get an acceptable media file, getting the desired file from a different source, or maybe even just re-downloading the file.
Could not import 1 of 1 items reaper что делать
will be used to construct table of contents —> , the anchor, and the plaintext subject must all be on the same line —> top Introduction
ReaScript is a feature that allows you to edit, run and debug scripts within REAPER. Scripts are simple text files from which you can call any REAPER action, and also call back into most of the REAPER API functions (the same API used by compiled REAPER plug-ins and extensions). ReaScript can be used to create anything from advanced macros to full-featured REAPER extensions.
Supported scripting languages:
EEL2
A language developed in-house (but open source) which has some similarities to C and JavaScript. EEL is also used to write JSFX plug-ins, OSCII-bot scripts, and video processing effects in REAPER. EEL offers outstanding run-time performance. It supports basic UI management (dedicated script window, docking, context menus, mouse input, etc) and graphics manipulation (drawing primitives, loading image files, etc). EEL is embedded within REAPER and requires no additional downloads or settings.
Lua (v5.3)
A popular scripting language. Lua is probably easier to learn and use than EEL or Python, and offers good performance. It supports the same UI and graphic features as EEL. As a general-use scripting language, Lua also benefits from third-party resources, libraries, tutorials, and code examples. Lua is embedded within REAPER and requires no additional downloads or settings.
Python (v2.7-v3.x)
Another popular scripting language. Python must be downloaded and installed separately (see requirements) and as such, will never be as portable between users as EEL or Lua. Within REAPER, Python performance is not as good as EEL or Lua, and does not offer any UI or graphic features. However, Python does benefit from a vast number of third-party resources, libraries, tutorials, and code examples.
EEL and Lua are embedded within REAPER and will work automatically.
Python requirements
You must have Python installed on your computer and enabled in REAPER preferences (Options > Preferences > Plug-Ins > ReaScript). ReaScript should work with any version of Python between 2.7 and the current 3.x release. OS X normally comes with Python already installed. If you don’t already have Python, it is available as a free download for Windows or Mac from multiple sources. For 32-bit REAPER, you need 32-bit Python (regardless of the operating system). For 64-bit REAPER, you need 64-bit Python. A list of Python distributions is here.
Once Python is installed, REAPER should automatically detect it, and ReaScript will work. If REAPER does not detect Python, you can enter the Python install directory manually in REAPER preferences.
ReaScript documentation is available online , but the API is extended frequently, and up-to-date documentation can be generated by REAPER itself.
From within REAPER, under the Help menu, choose «ReaScript documentation». This will open a web page with a complete list of REAPER Extension API functions that can be called from ReaScript. This help page will also explain the basics of how to call API functions and how to import functions/modules from other ReaScripts, and list additional REAPER-specific built-in functions that are available for each scripting language.
EEL documentation
The EEL2 language reference guide is a good place to read about basic EEL2 scripting. REAPER’s EEL2 implementation goes beyond those basics, though, including the addition of file I/O and network functions, which are described in the REAPER-generated ReaScript documentation, within the list of EEL built-in functions (see fopen(), tcp_connect(), et al)
Lua documentation
The Lua v5.3 reference manual is available here.
REAPER-specific functions (mostly UI/graphic functions) are also described in the REAPER-generated ReaScript documentation, within the list of Lua built-in functions.
Python documentation
There is extensive online documentation for Python 2 and Python 3.
You will need to either write a new script, or load a script from another user. Scripts can be placed anywhere on disk, but it is convenient to keep them all in the REAPER/Scripts resource directory. To find the resource directory: Options > Show resource path in explorer/finder.
To create a new script, show the Actions window (bound to the ? key by default), and click ReaScript: «New. «. You will be prompted for the location to save the script (the default location is the recommended REAPER/Scripts resource directory). The type of script will be deduced from the file extension you enter (.eel, .lua, or .py).
To load a script, click ReaScript: «Load. » in the Actions window, and select the script file you want to add to the action list (multiple selection is allowed).
Once you have written or loaded a script, it will be added to the action list, and you can treat the script just like any custom action: run it from the Actions window («Run» button, or double-click), bind it to a key shortcut, mouse wheel, MIDI/OSC controller, or toolbar button. You can get binding information at runtime too, details here.
ReaScripts can also be run à la carte, via the actions «ReaScript: run. » and «ReaScript: run last script».
To edit and/or debug a script, select it the Actions window, and click ReaScript: «Edit. «.
The ReaScript Integrated Developement Environment (ReaScript IDE) will open:

The right pane shows both built-in and user defined variables, which is handy for debugging.
Just try it. Experiment!
ReaScript is mostly fault-tolerant. Most programming mistakes will give error messages that will help you fix the mistake. While it is still possible to crash REAPER with scripts, you shouldn’t be able to do any permanent damage — just be sure to save any important projects before testing ReaScripts.
A very simple way to test ReaScript is by calling the API test function:
EEL2:
APITest();
Lua:
reaper.APITest()
Python:
RPR_APITest()
When you run this script, you should see a window that says «Test OK».
- Syntax error: typo, missing newline, incorrect indentation in Python, etc.
- Unknown extension API. Perhaps the script was written against a newer version of REAPER.
- Incorrect use of the Extension API. Verify how the function parameters and return value should be used in the REAPER-generated ReaScript documentation.
- Lua: invalid «objects». Check variables for nil before passing to functions.
- Python: REAPER cannot find the Python library. Is the proper 32/64-bit Python installed? Is it enabled in Preferences?
To call any REAPER built-in action from ReaScript, use Main_OnCommand(actionID, 0). Find the ID of a given action by opening the Actions window, and right-clicking it: «Copy selected action ID». For example, from ReaScript/EEL you would call the REAPER action «Item: Split item under mouse cursor» like this:
Main_OnCommand(40746, 0);
Deferred scripts
By default, ReaScripts are run on-demand and terminate after execution. However, you can write scripts that run in the background until terminated by the user. This can be used to write scripts that react to events, such as the current playback position, a track selection change, user input, etc. See defer()/ reaper.defer()/ RPR_defer() and atexit()/ reaper.atexit()/ RPR_atexit() in the REAPER-generated ReaScript documentation.
A deferred script with a user interface window will run modelessly, and can be docked, just like a built-in REAPER window.
The list of scripts that are currently running in the background is available in the Actions menu. To stop a deferred script, or to run a new instance, click the script in this list. Note that no undo point is automatically added when running/terminating deferred scripts, unless you create one explicitly.
-
SetExtState() and GetExtState() allow ReaScripts to set and get key/value pairs that will persist between ReaScripts, and optionally persist between REAPER instances as well. For example, a Python module called «utility» might want to remember that some flag is set:
RPR_SetExtState("utility", "someflag", "2", True) val=RPR_GetExtState("utility", "someflag") # even if called after REAPER is closed and reopened, val will be equal to "2"
There are also API functions for manually creating undo points, as well as API functions to Undo and Redo previous points.
- These functions operate on the active project only (if multiple tabs are open) — do not switch project tabs from your code while in an Undo block.
- You must always pair Undo_BeginBlock with Undo_EndBlock . If you call Undo_BeginBlock and then fail to call Undo_EndBlock , an undo block will be left open, which may cause undesired undo behaviors.
- The final parameter of Undo_EndBlock is a bitmask of what you would like to add to the undo state. If you are simply calling other actions (via Main_OnCommand or similar functions), this should be 0. If you modify the state of the project directly, it’s safest to set the bitmask to -1. A more specific combination of flags may be an optimization, depending on what your script is doing.
- Always give the «desc» parameter of Undo_EndBlock a valid (non-empty) descriptive string.
Lua example:
reaper.Undo_BeginBlock() m = reaper.GetMasterTrack(0) reaper.TrackFX_GetByName(m, "ReaEQ", 1) reaper.Undo_EndBlock("Add ReaEQ FX to the master track", -1)
- 1: track configurations
- 2: track FX
- 4: track items
- 8: project states
- 16: freeze states
Action binding
You can query various contextual information about the script, at runtime, using get_action_context()/ reaper.get_action_context() (sorry, no Python support) . You can retrieve MIDI/OSC/mouse-wheel/trackpad input values when the script is bound to MIDI/OSC controllers (both absolute and relative modes are supported), or to the mouse-wheel/trackpad.
Here is a basic Lua example which monitors received MIDI/OSC input values:
function run() is_new,name,sec,cmd,rel,res,val = reaper.get_action_context() if is_new then reaper.ShowConsoleMsg(name .. "\nrel: " .. rel .. "\nres: " .. res .. "\nval = " .. val .. "\n") end reaper.defer(run) end function onexit() reaper.ShowConsoleMsg("<-----\n") end reaper.defer(run) reaper.atexit(onexit)
Toggle state
ReaScripts can have ON/OFF states. Here is a minimal EEL example that toggles the current state each time the script is performed. If this script were bound to a toolbar button, each button press would alternately turn the button on or off.
get_action_context(#fn, sec, cmd); state = GetToggleCommandStateEx(sec, cmd); SetToggleCommandState(sec, cmd, state<=0?1:0); RefreshToolbar2(sec, cmd);
For more help on ReaScript, to download script examples, to report bugs, to request additional API functions, to share ReaScripts, or just to discuss the possibilities, please use the REAPER ReaScript Forum.
