Reply to thread

Message: [QUOTE="Bombastus, post: 91165, member: 2178"] Reverie 1.14 runs on Linux as a standalone x86_64 application, not as a VST3, LV2, or JACK client. You cannot insert it on an Ardour channel, automate it from Bitwig, or open it inside REAPER. That sounds restrictive only if you expect a conventional effect. Reverie is an offline ambient soundscape generator that accepts a source file, builds and renders a texture, then returns another audio file. Its Linux playback can pass through ALSA, PulseAudio, or PipeWire, but those systems let you hear the app rather than turn it into a hosted processor. The difference is easy to miss when reading [B][URL='https://goldmidi.com/community/threads/parallel-minds-brought-reverie-1-14-to-linux.76476/']the Linux changes in Reverie 1.14[/URL][/B] because the iPad edition gained host-aware audio units in the same release. Those instruments and capture tools are limited to iPadOS. On a Linux desktop, the reliable approach is an [B]offline render-and-import workflow[/B]. [HEADING=2]Reverie stays outside the Linux session[/HEADING] Begin in your DAW by bouncing the material you want Reverie to process. A vocal stem, sustained synth part, isolated guitar note, or field recording gives the generator a cleaner target than a full master. Reverie accepts WAV, MP3, FLAC, OGG, M4A, and AIFF, so an extra conversion is usually unnecessary. Open that file in Reverie and use the waveform handles to isolate the useful region before rendering. This matters when a long take contains count-ins, silence, drum hits, or room noise that should not feed the processing chain. You hear the selected region while adjusting its boundaries, which makes the cut less arbitrary. Generation then happens entirely inside Reverie. Your DAW transport, tempo map, JACK graph, plugin automation, and audio-buffer setting do not control the render because the desktop app is not attached to the session. Movement, brightness, stretch, duration, style, and any custom DSP chain are set in Reverie itself. That removes several Linux-audio complications. You do not need Carla, a virtual loopback, or a PipeWire patch bay to feed Reverie into the DAW, because those tools solve live routing while this handoff happens on disk. If both apps can open the same project folder, the connection already exists. Once a result works, export it into the DAW project’s audio directory and import it onto a fresh track. REAPER, Ardour, and Bitwig do not need a special Reverie integration for this step. Place the texture at the required bar, add fades, and treat it like any other rendered stem. [HEADING=2]File choices prevent avoidable rework[/HEADING] The free tier exports WAV and limits each result to three minutes. Pro extends a render to 30 minutes and adds WAV, FLAC, OGG, and AIFF output in 16-bit or 24-bit modes. For a texture that will receive more EQ, compression, editing, or automation, 24-bit WAV or AIFF leaves useful headroom without perceptual encoding. FLAC is a sensible lossless choice when storage or transfer size matters and your DAW reads it cleanly. OGG can suit compact listening copies, but keeping a WAV, AIFF, or FLAC master avoids rebuilding a keeper merely because a later session needs a different delivery format. One render can serve several edits. Reverie preserves the source sample rate from input to output. If a 44.1 kHz source enters a 48 kHz project, the DAW may therefore resample the result during import. Bouncing the source at the project rate before sending it to Reverie keeps that conversion decision under your control and makes exchanges with another producer more predictable. The generated bed has a fixed duration rather than a live relationship with the tempo grid. A later tempo change will not regenerate its internal motion, although your DAW can still time-stretch the imported clip if instructed. This separation is useful for film beds and long drones, but rhythmic material needs an intentional placement check after every arrangement change. Name exported trials with the source, style, duration, and version instead of overwriting one generic file. Reverie can produce different results from the same input, and descriptive filenames let the DAW retain alternate takes without confusing them. [HEADING=2]Rendered audio remains the authoritative asset[/HEADING] Pro seeds can restore a processing chain and its parameter choices when the same source file is available. They are valuable production notes, not replacements for exported audio. Reverie 1.14 changed the final limiting stage, so a seed made in 1.13 restores its chain in 1.14 without recreating a bit-identical file. Archive the accepted render beside its source, seed, and Reverie version rather than relying on regeneration. The DAW project should reference the exported file inside its own media folder, not a temporary download or desktop location. That small discipline prevents missing-file warnings and preserves the exact texture that survived your mix decisions. [/QUOTE]

Name