Error creating output media reaper

I edited two items which were split from each other.
Then I tried to glue them and got a out an «Error creating Output Media».
(and nothing is glued back)
Any explanation for this?

__________________
Thanks
superkristen

Technology has given us the ability to repeat all our mistakes we have learned from history, …. but much faster, deadlier, and with greater accuracy!

__________________
Thanks
superkristen

Technology has given us the ability to repeat all our mistakes we have learned from history, …. but much faster, deadlier, and with greater accuracy!

Ok, the most simple obvious question first:

Disc full by any chance ?

I leave all the Paths blank and let it default to the directory the files are in. In all the years I have used Reaper I have never named a path before and never had problems glueing tracks together.

I get a «format Spec» in the Consolidation Box when I get the «Error creating Output Media» box.

__________________
Thanks
superkristen

Technology has given us the ability to repeat all our mistakes we have learned from history, …. but much faster, deadlier, and with greater accuracy!

I leave all the Paths blank and let it default to the directory the files are in. In all the years I have used Reaper I have never named a path before and never had problems glueing tracks together.

I get a «format Spec» in the Consolidation Box when I get the «Error creating Output Media» box.

I’ve been trying to glue audio events together, also to no avail. I get the same error, and it cites «Format spec» as well. I have all my default directories set.

Has anyone come up with a work-around for this? It looks like bug to me!

ps — there is nothing «whacky» about rendering to an external HDD. Reaper sees the drive letter and renders to any media, irrespective of internal or external.

just a wild guess but plz try it:

first . glue each item to only itself. then try to glue them together

You are correct — any HDD can power down eventually, depending on your Power Settings. For drive letter changes, once a drive has been connected, the OS will reserve the drive letter for that drive’s serial number. *BUT* you are correct in that, if another external drive is plugged in, it can «bump» the letter of the previous drive, and keep it for itself.

However, all these are moot points when speaking of rendering. When performing a render operation, the access to the external drive is only for the actual render time. After that, the OS no longer needs to access that drive (until the next render).

Couple of things,

1. What OS? What directory are these things being ‘glued’ to? Does reaper have permission to write there?

2. How big are the files? is the combined size of the ‘glued’ file over a system limit (given the format that you’ll be gluing to?)

Источник

I edited two items which were split from each other.
Then I tried to glue them and got a out an «Error creating Output Media».
(and nothing is glued back)
Any explanation for this?

Ok, the most simple obvious question first:

Disc full by any chance ?

does the project your in have a folder assigned for the media files?

Gwok is right.Check in options/preferences if a path is defined to savec the project and the media files.

I leave all the Paths blank and let it default to the directory the files are in. In all the years I have used Reaper I have never named a path before and never had problems glueing tracks together.

I get a «format Spec» in the Consolidation Box when I get the «Error creating Output Media» box.

I leave all the Paths blank and let it default to the directory the files are in. In all the years I have used Reaper I have never named a path before and never had problems glueing tracks together.

I get a «format Spec» in the Consolidation Box when I get the «Error creating Output Media» box.

I’ve been trying to glue audio events together, also to no avail. I get the same error, and it cites «Format spec» as well. I have all my default directories set.

Has anyone come up with a work-around for this? It looks like bug to me!

ps — there is nothing «whacky» about rendering to an external HDD. Reaper sees the drive letter and renders to any media, irrespective of internal or external.

there is nothing «whacky» about rendering to an external HDD. Reaper sees the drive letter and renders to any media, irrespective of internal or external.

Things can get wacky for a few reasons. Rarely computers will change drive letter names for external drives if they have been disconnected and something else had been connected to the port in between. And I could have sworn that some external HD’s will power down after idele time (or is this in the power management?)

just a wild guess but plz try it:

first . glue each item to only itself. then try to glue them together

Things can get wacky for a few reasons. Rarely computers will change drive letter names for external drives if they have been disconnected and something else had been connected to the port in between. And I could have sworn that some external HD’s will power down after idele time (or is this in the power management?)

You are correct — any HDD can power down eventually, depending on your Power Settings. For drive letter changes, once a drive has been connected, the OS will reserve the drive letter for that drive’s serial number. *BUT* you are correct in that, if another external drive is plugged in, it can «bump» the letter of the previous drive, and keep it for itself.

However, all these are moot points when speaking of rendering. When performing a render operation, the access to the external drive is only for the actual render time. After that, the OS no longer needs to access that drive (until the next render).

Couple of things,

1. What OS? What directory are these things being ‘glued’ to? Does reaper have permission to write there?

2. How big are the files? is the combined size of the ‘glued’ file over a system limit (given the format that you’ll be gluing to?)

Couple of things,

1. What OS? What directory are these things being ‘glued’ to? Does reaper have permission to write there?

2. How big are the files? is the combined size of the ‘glued’ file over a system limit (given the format that you’ll be gluing to?)

1. Windows 7; Dir = Project Folder; yes, Reaper has permission to write there and is writing there when I record

The files are a looped section of less than 5 seconds, so probably somewhere around 10Mb.

Ok then. I was just throwing ideas out. By the way Tim, that VU meter shirt you are wearing on your website. Does that one light up and pulse to rhythms? If so, I have that shirt. lol.

Have you double checked the format/specs used for gluing etc? This smells like it doesn’t like WHAT it is writing more than WHERE it is writing. Just to be sure on «where». exactly where is the attempted file writing happening as in the Exact path and when you get the error does it reference that path?

Have you double checked the format/specs used for gluing etc? This smells like it doesn’t like WHAT it is writing more than WHERE it is writing. Just to be sure on «where». exactly where is the attempted file writing happening as in the Exact path and when you get the error does it reference that path?

That’s a great question Karbo. but why did you use my quote to kick it off. You computer guys are a mystery sometimes. rolleyes:

That’s a great question Karbo. but why did you use my quote to kick it off. You computer guys are a mystery sometimes. rolleyes:

Dammit, I meant to hit reply. :confused:

Dammit, I meant to hit reply. :confused:

Good stuff. You could code a program that turns sand into water in the desert, but you can’t navigate a mouse.

Have you double checked the format/specs used for gluing etc? This smells like it doesn’t like WHAT it is writing more than WHERE it is writing. Just to be sure on «where». exactly where is the attempted file writing happening as in the Exact path and when you get the error does it reference that path?

Good question Karbo — but I’m not sure where I set the format specs for gluing. Do you know where that option is?

Reaper does not reference the Path in its error, and I have tried multiple paths, both relative and absolute.

Thanks for all the help guys — I really appreciate it!

PS Richie — re the shirt — yes 🙂

Good question Karbo — but I’m not sure where I set the format specs for gluing. Do you know where that option is?

Reaper does not reference the Path in its error, and I have tried multiple paths, both relative and absolute.

Thanks for all the help guys — I really appreciate it!

PS Richie — re the shirt — yes 🙂

The setting you are looking for is not in general preferences, but instead in the project settings (top menu, file, project settings. Click the media tab and look at the bottom of the settings dialog.

Источник

My postings in the Video mangling subforum did not get much traction, so I stick my neck out here and claim that this a bug in Reaper.

As the title says, when I try to render video with mp3 as audio format, I get an error message saying «Error initializing audio encoder». In short, it is not possible (for me) to render any video format together with mp3 as audio format. Rendering mp3 audio only works fine.

W7x64, Reaper v6.15/x64

Would anyone care to confirm or refute, please.
Thanks,

Works here:

My (very vague) hunch would be LAME/FFMPEG incopatibilty?
I’m using LAME 3.99.5/FFMPEG v58.46.100 (Zeranoe build iirc).

edit:
You can get your current installed FFMPEG version via Preferences > Video. > Show available decoder information

Reaper by default only includes a minimal FFMPEG version, not sure it’s possible with that one.

Works here:

My (very vague) hunch would be LAME/FFMPEG incopatibilty?
I’m using LAME 3.99.5/FFMPEG v58.46.100 (Zeranoe build iirc).

edit:
You can get your current installed FFMPEG version via Preferences > Video. > Show available decoder information

I use ffmpeg/libav DLL decoder v58.91.100, latest (and final?) Zeranoe build. And Lame 3.99.5.

Thanks for checking this. Now I know it is not Reaper but something else, maybe what you suggest. I’ll start by trying to hunt down ffmpeg v58.46.100.

Thanks.
I found older versions on Wayback Machine.

And indeed, with an older version of ffmpeg it works for me here now to render mov/mp4 with mp3 as audio format. This is probably something the devs need to look into.

Still, with this older version both the mp3 and aac have the audio 12 ms late, mp3 has more of the audio cut off at the beginning than aac, and aac has clearly audible artifacts.

OK, so experimenting with different versions of ffmpeg, it seems that this is a bug with the recent version of ffmpeg on Windows. Versions 4.3.0 and 4.3.1, which are both internally labeled v58.91.100, give this error:

If I use ffmpeg version 4.2.3 (v58.54.100) or earlier, it works fine.

If I have «aac» instead of mp3, it works fine with new and old versions of ffmpeg (but with bad crackling).

Necroing this to say I just ran into this today too — same problem.
(Also want to preface this with I know absolutely NOTHING about working with video, or how encoders/codecs work)

Available Decoder Info:

Just wanted to trim a .webm I had and then save the trimmed file.

Turns out I needed the extended FFMPEG for importing video from WEBM, and when trying to render it as any video file with MP3 output, I get:

Not entirely sure what to do — downgrade to a different FFMPEG inside of «UserPlugins»?

Yeah, versions 4.3.0 and 4.3.1 are both internally labeled v58.91.100, and they do not work with mp3 as audio format. Use 4.2.3 or earlier.

EDIT: It seems that the github page has updated ffmpeg, but not the readme file. Version 4.1.3 has its internal label 58.35.100, so the one you have installed is not 4.1.3, but either 4.3.0 or 4.3.1. You can find 4.2.3 on WaybackMachine https://web.archive.org/web/20200918. oe.com/builds/

I’ve been dealing with this same error message for over a year, and I haven’t been able to export any h264 files in Reaper. But seeing your shot of the «Available Decoder Info» gave me a clue. My Reaper was getting its «avcodec-58.dll» from C:WindowsSystem32. I have no idea how these files got there, but once I temporarily removed them, Reaper read the files from UserPlugins and everything now works.

This has caused me literally a year of headaches. I can’t thank you all enough for this thread!

Источник

Внимание! авторам, имеющих авторское право на тот или иной текст бренд или логотип, для того чтобы ваша авторская информация свободно не распространялась в ресурсах интернета вы должны ее удалить с таких ресурсов как vk.com ok.ru dzen.ru mail.ru telegram.org instagram.com facebook.com twitter.com youtube.com и т.д в ином случаи размещая информацию на данных ресурсах вы согласились с тем что переданная вами информация будет свободно распространятся в любых ресурсах интернета. Все тексты которые находятся на данном сайте являются неотъемлемым техническим механизмом данного сайта, и защищены внутренним алфавитным ключом шифрования, за любое вредоносное посягательство на данный ресурс мы можем привлечь вас не только к административному но и к уголовному наказанию.

Согласно статье 273 УК РФ

385

386

387

388

389