ReaClassical: Open Source Classical Editing Tools for REAPER

[Meo-Ada Mespotine]

Originally Posted by chmaha

Here's the contents of my reaper-render.ini with the first go at render presets:

<RENDERPRESET BIN+CUE 44100 2 0 1 10 1 0
  IG9zaQAAAAAAAAAAAAAAAAEAAAAAAAAA
>
RENDERPRESET_OUTPUT BIN+CUE 1 0 4209.386 0 0 $project 0 Exports/BIN+CUE 1000
<RENDERPRESET DDP 44100 2 0 1 10 1 0
  IHBkZA==
>
RENDERPRESET_OUTPUT DDP 1 0 4209.386 0 0 IMAGE.DAT 0 Exports/DDP 1000
<RENDERPRESET "FLAC 44.1k 16-bit" 44100 2 0 1 10 1 0
  Y2FsZhAAAAAFAAAA
>
RENDERPRESET_OUTPUT "FLAC 44.1k 16-bit" 3 2 180.36 0 0 "$format_$samplerate_$bitdepth/$regionnumber $region" 0 Exports/ 1000
<RENDERPRESET "FLAC 44.1k 24-bit" 44100 2 0 1 10 1 0
  Y2FsZhgAAAAFAAAA
>
RENDERPRESET_OUTPUT "FLAC 44.1k 24-bit" 3 2 180.36 0 0 "$format_$samplerate_$bitdepth/$regionnumber $region" 0 Exports/ 1000
<RENDERPRESET "FLAC 48k 16-bit" 48000 2 0 1 10 1 0
  Y2FsZhAAAAAFAAAA
>
RENDERPRESET_OUTPUT "FLAC 48k 16-bit" 3 2 180.36 0 0 "$format_$samplerate_$bitdepth/$regionnumber $region" 0 Exports/ 1000
<RENDERPRESET "FLAC 48k 24-bit" 48000 2 0 1 10 1 0
  Y2FsZhgAAAAFAAAA
>
RENDERPRESET_OUTPUT "FLAC 48k 24-bit" 3 2 180.36 0 0 "$format_$samplerate_$bitdepth/$regionnumber $region" 0 Exports/ 1000
<RENDERPRESET "MP3 192kbps" 44100 2 0 1 10 1 0
  bDNwbcAAAAAAAAAAAgAAAP////8EAAAAwAAAAAAAAAA=
>
RENDERPRESET_OUTPUT "MP3 192kbps" 3 2 100.28 0 0 "$format_192/$regionnumber $region" 0 Exports/ 1000
<RENDERPRESET "MP3 320kbps" 44100 2 0 1 10 1 0
  bDNwbUABAAAAAAAAAgAAAP////8EAAAAQAEAAAAAAAA=
>
RENDERPRESET_OUTPUT "MP3 320kbps" 3 2 100.28 0 0 "$format_320/$regionnumber $region" 0 Exports/ 1000
<RENDERPRESET "WAV 44.1k 16-bit" 44100 2 0 1 10 1 0
  ZXZhdxAAAA==
>
RENDERPRESET_OUTPUT "WAV 44.1k 16-bit" 3 2 180.36 0 0 "$format_$samplerate_$bitdepth/$regionnumber $region" 0 Exports/ 1000
<RENDERPRESET "WAV 44.1k 24-bit" 44100 2 0 1 10 1 0
  ZXZhdxgAAA==
>
RENDERPRESET_OUTPUT "WAV 44.1k 24-bit" 3 2 180.36 0 0 "$format_$samplerate_$bitdepth/$regionnumber $region" 0 Exports/ 1000
<RENDERPRESET "WAV 48k 16-bit" 48000 2 0 1 10 1 0
  ZXZhdxAAAA==
>
RENDERPRESET_OUTPUT "WAV 48k 16-bit" 3 2 180.36 0 0 "$format_$samplerate_$bitdepth/$regionnumber $region" 0 Exports/ 1000
<RENDERPRESET "WAV 48k 24-bit" 48000 2 0 1 10 1 0
  ZXZhdxgAAA==
>
RENDERPRESET_OUTPUT "WAV 48k 24-bit" 3 2 180.36 0 0 "$format_$samplerate_$bitdepth/$regionnumber $region" 0 Exports/ 1000

For now, feel free to add to your existing file or create reaper-render.ini in your resource path. FYI, I can't seem to get secondary formats to save with the presets. Anyone else have the same issue?

It should store it. I documented it definitely at some point so I manage to store it.
On windows at least.

[MonkeyBars]

Absolutely crushing it!! Keep up the inspiring work

[chmaha]

NEW: ReaClassical v23.19pre14

• Reposition Tracks: Add guard clauses to deal with zero track count, zero media items or presence of empty items

Just dotting the Is and crossing the Ts.

Also, FWIW, I'm thinking @ shortcut for adding aux/submix tracks (given they prefix with @) and Ctrl+Y for repositioning tracks given it is somewhat related to the Y shortcut for Create CD Markers script.

Originally Posted by MonkeyBars

Absolutely crushing it!! Keep up the inspiring work

Thanks so much for your support! It means a lot.

[chmaha]

Slowly working my way through the bits and pieces for the public release.

NEW: ReaClassical v23.19pre15

• Change Reposition Tracks name to Reposition Album Tracks to avoid confusing terminology

Just a small cosmetic change so that it is clear we are referring to CD tracks and not REAPER tracks in the TCP.

Second, the latest toolbar:



The Add Aux/Submix @ icon placed after Create folder and Create Source Groups scripts and the Reposition Album Tracks calculator icon. I'll add to the repository in April and it will, of course, be part of the new portable install.

Third, I updated all the UserPlugins zips that are pulled as part of the portable install scripts. There's no reason not to switch to latest bleeding edge SWS at this point.

If you already have a ReaClassical install go ahead and update SWS from here: https://www.sws-extension.org/downlo...3.2.0-a3693ad5 or download the relevant zip from https://github.com/chmaha/ReaClassic...rs/UserPlugins. ReaPack seems to auto-update which is nice.

[chmaha]

Further updates:

• Added various manual install files to the ReaClassical repository
• Bumped REAPER version to 6.78 in portable install scripts and .exe

Basically, I want everything in place so that in about 3 weeks I can just push v23.19 of the scripts and a snapshot of the base resource folder. I'll do a further update of the portable scripts if there's another new REAPER version released before then. So added to the manual install folder are the new toolbar and icons, keymaps, and reaper-render.ini for ReaClassical render presets.

My recommendation at this point is not to use manual install files at all but simply use the portable install scripts once a quarter to get the latest and greatest complete ReaClassical experience. Portable is absolutely no different to a regular install in terms of performance. Plus, you can carry it around on a pen drive

If you are wedded to your own permanent highly-customized REAPER setup and have projects that require ReaClassical functionality and lots more besides, my recommendation would be to install the ReaClassical scripts via ReaPack, switch to the included theme and project template (at least when doing classical-style editing) and then add any further settings as you wish from the portable install either manually or using the REAPER export/import configuration in preferences.

Originally Posted by Meo-Ada Mespotine

It should store it. I documented it definitely at some point so I manage to store it.
On windows at least.

Ah, it works some of the time, say if the secondary format is AIFF but not if MP3. Weird.

[chmaha]

NEW: ReaClassical v23.19pre16

• Add Aux/Submix Track: Only allow if folder already exists

To avoid aux/submix @ tracks being created first and making for a messy track order, I'm generally trying to encourage (force) people to use folders for everything. Obviously this makes sense for multi-mike setups. And, don't forget that if you don't have an interleaved stereo main pair or guide track, put your first mono track in track 2 (the first child of the folder). When you run Prepare Takes (T) it will copy a muted guide track to the parent.

Likewise, if you only have a simple stereo pair recording setup, you should still use a folder. Just make a folder with 2 tracks and leave the second empty. When you hide the child tracks using the E shortcut, it's just like using a single track. This way, all the scripts including source-destination editing work as expected.


NEW: ReaClassical v23.19pre17

• Prepare Takes: Change messagebox to yes/no if edits present

No need for a cancel button.


NEW: ReaClassical v23.19pre18

• Reposition Album Tracks: Show message if no media item take names found

In the event of no item take names, nothing will be moved so a courtesy message is useful here.


NEW: ReaClassical v23.19pre19

• Reposition Album Tracks: Respect relative positions of named tracks that run on from previous tracks

This one ended up being important. If you have an album with CD tracks (aka items with take names) that run on ("attacca") from previous ones via a quick crossfade etc, the script respects these and treats them like it would an unnamed track.

[studer58]

How likely is it that the periodic Reaper updates will break ReaClassical’s functionality ? It’s probably impossible to say with any certainty, but perhaps slower adoption of updates is wise, until the all-clear is given here ? There’s always a repository of earlier Reaper versions to roll back to in such cases.

[chmaha]

Originally Posted by studer58

How likely is it that the periodic Reaper updates will break ReaClassical’s functionality ? It’s probably impossible to say with any certainty, but perhaps slower adoption of updates is wise, until the all-clear is given here ? There’s always a repository of earlier Reaper versions to roll back to in such cases.

I'd say it is highly unlikely. The devs approach AFAIK is to take the approach of keeping everything backwards compatible as much as is humanly possible. In April, my only recommendation will be to update SWS to the latest bleeding edge so that the View Whole Project script works as expected. The stable release of SWS is quite long in the tooth at this point.

I wouldn't worry much. I include the REAPER update utility in the portable install so it is super simple to upgrade/downgrade REAPER versions. Obviously you can do likewise with ReaClassical via ReaPack.

My new approach of releasing scripts publicly once a quarter is simply so that users feel they have a decent amount of time in between feature updates. The only exception to that will be bugfixes which will hopefully be rare.

[mtierney]

Slightly off-topic, but I figured I'd ask here since chmaha has a DDP authoring GUI... has anyone had much success IMPORTING a DDP into Reaper on a Mac? It seems like no matter what I do, I can get the single audio track to import just fine, but I can't seem to get the markers loaded into my session. Thanks!

[chmaha]

Originally Posted by mtierney

Slightly off-topic, but I figured I'd ask here since chmaha has a DDP authoring GUI... has anyone had much success IMPORTING a DDP into Reaper on a Mac? It seems like no matter what I do, I can get the single audio track to import just fine, but I can't seem to get the markers loaded into my session. Thanks!

You could convert to WAV+CUE before you import and then use the Script: mpl_Convert CUE file into markers (DDP formatted).lua script to make your DDP markers. However, this wouldn't be compatible with my new way of generating DDP albums as it uses item take names for track starts. You could, of course, take a few minutes to adapt the session

[goldec]

Why does prepare takes script remove all of my take names?
What does "clean up take names" mean?

[chmaha]

Originally Posted by goldec

Why does prepare takes script remove all of my take names?

Because I designed it that way Knowing that the end goal is to use the "Create CD Markers" script to generate DDP etc which is based on take names, it made much more sense based on number of tracks vs number of possible edits (could be 100s?) to type in the required track starts as required. Plus, I assume nobody wants all the extension .wav .flac stuff there.

If there's another behaviour you'd prefer let me know. I could always split off that function into a different script I suppose. Maybe better would be to just pose a question so users have a choice. It's not like the Prepare Takes script is run more than once (or twice if you want to change the random colors!). There's still time to do either before I hit my feature "freeze" for 23.19.

Originally Posted by goldec

What does "clean up take names" mean?

"Clean up take names" is essentially just deleting the take names. I will re-word that to say "Delete...".

Thoughts from other users?

In the meantime:

NEW: ReaClassical v23.19pre20

• Prepare Takes: Improve wording of message when offering to remove item take names when edits present

[Meo-Ada Mespotine]

Originally Posted by mtierney

Slightly off-topic, but I figured I'd ask here since chmaha has a DDP authoring GUI... has anyone had much success IMPORTING a DDP into Reaper on a Mac? It seems like no matter what I do, I can get the single audio track to import just fine, but I can't seem to get the markers loaded into my session. Thanks!

There's an Api-function for metadata that allows getting the markers in audiofiles. I haven't tested if it supports markers in DDP only in other formats but if it supports DDP, it would allow scripts like "Import markers of selected items".

[chmaha]

Originally Posted by Meo-Ada Mespotine

There's an Api-function for metadata that allows getting the markers in audiofiles. I haven't tested if it supports markers in DDP only in other formats but if it supports DDP, it would allow scripts like "Import markers of selected items".

DDP filesets use a separate file for the marker information. The IMAGE.DAT is simply a raw signed-integer audio file.

[goldec]

Originally Posted by chmaha

"Clean up take names" is essentially just deleting the take names. I will re-word that to say "Delete...".

Thoughts from other users?

Thank you for the clarification.

When I use vertical editing the diferent takes at diferent times can be very much mixed up. I use take numbers to gauge how far into the recording process a certain take was recorded. That way I can get an idea of what to expect quality wise.

There is an action 41858 that I tried but sadly it didn't restore the names.

[chmaha]

Originally Posted by goldec

Thank you for the clarification.

When I use vertical editing the diferent takes at diferent times can be very much mixed up. I use take numbers to gauge how far into the recording process a certain take was recorded. That way I can get an idea of what to expect quality wise.

There is an action 41858 that I tried but sadly it didn't restore the names.

A simple undo (ctrl+Z) would have given you the take names back. Too late? In any case, that 41858 action ("Item: Set item name from active take filename") works for me. Just make sure you select all the items first before running it. Hopefully that's the problem solved for you.

I always place takes in order they were recorded (easiest route from recording) so in a vertical workflow, the bigger the track number, the later it was recorded.

I do think I'll add a yes/no question to the script to avoid automatically deleting take names.

[chmaha]

NEW: ReaClassical v23.19pre21

• Prepare Takes: Always ask if user wants to remove item take names

As was telegraphed, here is the improved Prepare Takes script which will now always ask the user if they wish to remove take names in addition to the grouping and coloring functions. I don't consider it a hassle to ask the question because a user might only use this script once or possibly 2-3 times depending on how the random coloring turns out.

[MonkeyBars]

Originally Posted by chmaha

I don't consider it a hassle to ask the question because a user might only use this script once or possibly 2-3 times

It's always a tricky UX question just how many warnings to display in a given Reaper script, right? Like you want it to "just work intuitively" but sometimes there are guardrails and limitations you have to call out. Then there's the wording, etc... a lot of thought goes into it.

[chmaha]

Originally Posted by MonkeyBars

It's always a tricky UX question just how many warnings to display in a given Reaper script, right? Like you want it to "just work intuitively" but sometimes there are guardrails and limitations you have to call out. Then there's the wording, etc... a lot of thought goes into it.

Yep. I'd prefer not to have the question asked at all but that's only because I always want to remove take names for my own work. However, that's just plain selfish

[chmaha]

NEW: ReaClassical v23.19pre25 (plus a few other previous releases!)

• mpl Markers to CUE: Complete revision of code including correcting a cue file specification error, added width to dialog box, removal of external dependencies and simplifying the main function to use separated functions
• Added Markers to CUE script to ReaClassical repository with permission

The script works similarly to before but now populates the dialog with the current year and and filename named after project name and automatically writes to a CUE file in the root of the project path. Before or after doing this, simply export a full project WAV, FLAC, AIFF or MP3 at mastered sample rate (and either 24-bit or 32-bit FP bitdepth) for a high-resolution audio+cue pair. For the next upload of the resource folder, I include a render preset for this purpose but you will need to change the sample rate as appropriate (set by default at 96k)

One of the major benefits of removing JS API dependency is that the script now works on Raspberry Pi

NEW: ReaClassical v23.19pre26

• Markers to CUE: Fix bug when dot but no extension present in filename
• Markers to CUE: Generate uppercase extension as part of a single function

Just a fix for a leftover bug from the original mpl script when if you typed something like "filename." it would still generate the cue file without a proper extension. Plus, I enjoyed engaging in some more refactoring.

[chmaha]

NEW: ReaClassical v23.19pre27

• Create Source Groups: Allow for (re)creating lead/follow groups with existing manually-created folders
• Create CD Markers: Create pregap markers by prefixing take name with "!"
• Markers to CUE: Match CUE file name with audio filename given in dialog

A relatively big update! Probably one of the last before I release everything publicly. A few explanations are probably good.

First, Create Source Groups will create or recreate track grouping (in terms of pan, mute, fader etc) whenever it is run. This includes if you have a series of manually-created folders because you forgot to run the script at the beginning. I should build in a check to make sure that all folders contain the same number of tracks otherwise it won't work well.

Second, You can now automatically add pregap "countdown" markers as part of the new Create CD Markers. Simply prefix your item take name with a "!" and pregap marker will be generated 3 seconds prior (and placed on an exact CD frame). Then adjust the position by dragging as desired. In 2023 they are definitely less useful but I came across a disc the other day that used it in the lead in to an attacca chorus movement from a solo. My advice is to use sparingly. If you are not familiar, some players will actually show a countdown on the LED which has no bearing on the audio at all but is apparently fun to look at

Third, the Markers to CUE script now creates a CUE filename that matches the audio filename you specify in the dialog. So, for example, entering Mahler_Symphony_1.wav will generate a matching Mahler_Symphony_1.cue file. It's the small things

NEW: ReaClassical v23.19pre28

• Markers to CUE: Save user-inputted metadata and recall on next run

Similar to Create CD Markers script, any metadata is saved in the project and recalled on next run saving you valuable time

Aside from the check for folder track count for Create Source Groups as mentioned above, I think that's about it for new features for the upcoming release!

[chmaha]

NEW: ReaClassical v23.19pre29

• Create Source Groups: Show error if folders don't have the same number of tracks

OK, this should work quite well. If there is a discrepancy between folder track counts, lead/follow stuff (pan, fader, mute etc) is removed until you sort out your folders (adding or deleting tracks as required). Then re-run the script and everything should go back to normal.

[chmaha]

NEW: ReaClassical v23.19rc1

• Whole Project View: Switch back to original vertical zoom function for updated SWS
• Aux and submix: Allow for creation of aux and submix (@ track prefix) that stay visible
• Sync FX and routing: All child routing is now also copied from destination to source groups
• Classical Take Record: Add guard clause if no folder/track selected
• New Script: Add Aux/Submix @ track with color #4C9165 to end of tracklist
• Create Source Groups: Don't apply grouping for aux/submix tracks
• Various Scripts: Use Solo in Place (SIP) to allow for unmuted sends to aux/submixes
• Various scripts: Change color of @ aux/submix tracks if created manually
• New Script: Reposition Tracks
• Reposition Tracks: Now works with both prepared takes grouping (T) and newer media/razor editing grouping
• Create CD markers: If run save a key/value pair and change opening dialog to yes/no options.
• Reposition Tracks: Use key/value pair to automatically re-run Create CD Markers after repositioning
• Reposition Tracks: Add guard clauses to deal with zero track count, zero media items or presence of empty items
• Reposition Tracks: Rename to Reposition Album Tracks
• Add Aux/Submix @ track: Only allow use if a folder exists already
• Prepare Takes: Change messagebox to yes/no if edits present
• Prepare Takes: Improve wording of message when offering to remove item take names when edits present
• Prepare Takes: Always ask if user wants to remove item take names
• mpl Markers to CUE: Complete revision of code including correcting a cue file specification error, added width to dialog box, removal of external dependencies and simplifying the main function to use separated functions
• Added Markers to CUE script to ReaClassical repository with permission
• Remove JS API from UserPlugins
• Create Source Groups: Allow for creating lead/follow groups with existing manually-created folders
• Create CD Markers: Create pregap markers by prefixing take name with "!"
• Markers to CUE: Match CUE file name with audio filename given in dialog
• Markers to CUE: Save user-inputted metadata and recall on next run
• PDF Guide: Switch to sans serif font and add typesetting info on first page

Here's a release candidate in preparation for this week's public offering. The only thing that changed from the previous pre-release is switching the PDF guide to a sans serif font TeX Gyre Heros (based on URW Nimbus Sans L). Hopefully it is a bit easier to read!

[chmaha]

NEW: ReaClassical v23.19 "Mary Earps"

OK, the 2023 2nd quarter release is here. See the release notes for full changelog and install/update instructions. Highlights include new scripts for repositioning CD tracks (changing the gap between items working across the whole destination group), adding special Aux/Submix (@) tracks which stay visible in the mixer (and work seamlessly with routing sync between destination and source groups), and super-easy creation of CUE files (with a heavily modified version of an mpl script). Create CD Markers script now allows the user to add pregap "countdown" markers by prefixing a ! in front of the item take name (defaults to 3 seconds before the actual track start and snapped to a CD frame).

For quick sense of what the various scripts can do, read page 16–19 of the PDF guide included in the metapackage (H shortcut for the help system if using the portable install or using my keymap) or here: https://github.com/chmaha/ReaClassic...er%20Guide.pdf

If you are new to ReaClassical or want the simplest no-fuss way to update to the new version:

1. Download a new portable install and use it as is (simple and recommended for people only interested in the features for classical music and similar) using the instructions at https://github.com/chmaha/ReaClassic...nstructions.md

If you have been using ReaClassical as a portable install previously or have a highly customized permanent REAPER configuration and wish to update in place:

1. Sync ReaPack to get ReaClassical v23.19
2. Download a new portable install as above
3. Copy across the various files/settings that you might need from the new install to your previous install (see below or page 2 of the release notes)
4. Delete the newly downloaded folder

Updated config files to be copied to your existing resource path (Options > Show REAPER resource path…):

1. SWS Extensions (v2.13.2.0) from UserPlugins
2. reaclassical-splash.png (found in the same location as the reaper binary)
3. Custom toolbar from MenuSets + contents of Data/Toolbar_icons
4. In the Actions list (?), import the "ReaClassical" (just shortcuts for the ReaClassical scripts) or "Full_Classical_DAW" keymap from KeyMaps (if you like the ReaClassical defaults) etc.

Then restart REAPER!

Given the project is now pretty stable in terms of feature set, I think the need to copy across files in future will be absolutely minimal. I'll be sure to notate which files have changed as above so it is easy to navigate.

[chmaha]

A few other minor updates:

1. The Linux portable install script now uses the same single-level folder structure as on Windows and MacOS. So, after running the latest script you will end up with a ReaClassical_23Q2 folder and directly inside that will be the resource path including the REAPER binary. Consistency between OSes is a good idea here.
2. In the keymap, I am now using N to open the SWS notes (extremely useful while recording) instead of the old Markers: Insert and/or edit marker at current position behavior.
3. I'm still thinking about how best to approach educational materials beyond the PDF guide. It is now a definite priority as I feel we've reached something resembling a stable set of features.
4. Please let me know how the latest public release works out for you! I'm keen to hear about any success stories, bugs that you come across, but also generic REAPER errors that I can replace with more useful information if any of the scripts are run without the necessary things being present. I've already caught most of them through a combination of forward-thinking and trial and error but I'm sure a few are still lurking.
5. Please also let me know of any feature requests either to mimic behavior from Sequoia, Pyramix etc or a way of doing things that doesn't currently exist.

If you like these new updates, please consider donating (I will limit these polite asks to coincide with the quarterly releases). Thanks so much to those who have done so already. It means a great deal to me.

EDIT:

Also, quite big news: I moved all the non-"RCPlugs" airwindows JSFX ports into their own repo. To get them, import https://github.com/chmaha/airwindows...main/index.xml into ReaPack (right click and copy the link).

I also made the RCplugs a metapackage so if you search for "RCPlugs" in ReaPack, you'll be able to install all the essential classical plugins in one go. It feels easier to manage this way.

[chmaha]

NEW: RCPlugs v1.1

• Remove superfluous UINT32_MAX line
• Replace M_PI with $pi

Just a little bit of tidying up of scripts with a switch to the built-in $pi value that I've been using in the more recent airwindows ports. Plus, since I removed the unnecessary random number generation in a lot of scripts, I cleaned up the UINT32_MAX line in @init.

[Sumalc]

Thank you so much, very happy with cd marker script.

[theorbe]

I discover reaclassical, thank you very much for your work. I have always worked with Sequoia and Reaper is difficult to access for me. Your videos will be particularly useful to understand how you work. I'll give you just one example that is difficult for me to understand: when recording I like to put the same take number on the score as on the recording. You suggest to remove the track references...but then how do you find your way?
Thanks again for your wonderful work

Translated with www.DeepL.com/Translator (free version)

[chmaha]

Originally Posted by theorbe

I discover reaclassical, thank you very much for your work. I have always worked with Sequoia and Reaper is difficult to access for me. Your videos will be particularly useful to understand how you work. I'll give you just one example that is difficult for me to understand: when recording I like to put the same take number on the score as on the recording. You suggest to remove the track references...but then how do you find your way?
Thanks again for your wonderful work

Translated with www.DeepL.com/Translator (free version)

Thanks for writing. First, and most important, the latest version of the Prepare Takes script no longer forces removal of the take names and will always ask. So, if you work with syncing take names with the score that's no problem:



You'd only want to remove them later if and when you want to use the Create CD Markers script which relies on item take names becoming the CD track names. Re-running Prepare Takes at that point will not re-color or re-group (presumably because you will have crossfaded edits) but will offer to remove the current item take names so you can add the real track names:



Because I'm also a professional musician, conductors and other musicians generally trust me to make the best edits I can so there's no need for an annotated score most of the time. We know which was the best overall take (fairly obvious) and then I'll listen critically and swap out parts as necessary. There are never more than maybe 5 or 6 takes of a section so it doesn't take very long to audition them. On the rare occasions a musician has very strong views about which take is best, I find meeting in person to do the edits works well. I'm comfortable making S-D edits quickly and with people watching so it makes it a very interactive process. It cuts down on further edits down the line given that exact edit points are agreed upon while auditioning the audio versus just being handed an annotated score which despite best efforts retains some "fuzziness".

[theorbe]

thank you very much for your answer.

[theorbe]

Thank you very much for your answer.
I have another question that I can't figure out:
There are some keyboard shortcuts that do not work ( I am on a 2015 MacBook pro):
- Whole Project View (')
- Source-Destination Markers (1, 2, 3, 4)
I haven't tried everything yet...
Thanks for your answer

[chmaha]

Originally Posted by theorbe

Thank you very much for your answer.
I have another question that I can't figure out:
There are some keyboard shortcuts that do not work ( I am on a 2015 MacBook pro):
- Whole Project View (')
- Source-Destination Markers (1, 2, 3, 4)
I haven't tried everything yet...
Thanks for your answer

All depends on how you installed ReaClassical. If you did the full portable install, the keymap should be set up. I've tested on Linux, Windows and MacOS and things seem to be set up correctly. I can, of course, double-check. I can't imagine there would be issues with the number keys (on the main keyboard above QWERTY).

If you only installed the scripts by importing my repo into ReaPack then the keymap will not be set up. Let me know and I can talk you through how to import it though I would always recommend the full portable install route as it is so easy, fully-featured and ready to go.

[theorbe]

Your answer allowed me (it seems) to understand the problem: I am in France and I use an AZERTY keyboard... some keys work differently... So I have to find other keyboard shortcuts available to make your application work?
Thanks again for your help

[chmaha]

Originally Posted by theorbe

Your answer allowed me (it seems) to understand the problem: I am in France and I use an AZERTY keyboard... some keys work differently... So I have to find other keyboard shortcuts available to make your application work?
Thanks again for your help

Yes, it seems if you open the actions menu with ? shortcut you should be able to reassign to what you want. From the diagram you provided, to access the Source-Destination shortcuts you need to press shift to get the numbers? The shortcut for whole project view is a special on the é key. Better to redefine the keymap for your keyboard I think as I prefer single key shortcuts wherever possible. Hopefully you wouldn't need to change too many. There's always the toolbar if you are OK with mouse clicking but, again, I like to get people onto keyboard shortcuts as they are the fastest way to work.

[theorbe]

Apparently everything works now.
After testing I preferred to keep my keyboard in AZERTY because it was easier for me.
I simply changed Source-Destination Markers (1, 2, 3, 4) to Source-Destination Markers (&, é, ", ')
and 5 Make S/D Edit by ( Make S/D Edit.
I will now familiarize myself with your application and come back to ask you more questions. Thanks again

[chmaha]

Originally Posted by theorbe

Apparently everything works now.
After testing I preferred to keep my keyboard in AZERTY because it was easier for me.
I simply changed Source-Destination Markers (1, 2, 3, 4) to Source-Destination Markers (&, é, ", ')
and 5 Make S/D Edit by ( Make S/D Edit.
I will now familiarize myself with your application and come back to ask you more questions. Thanks again

Perfect! Glad you have it configured.

[chmaha]

New: ReaClassical v23.20pre1

• Create CD Markers: Add default 200ms marker/region offset

Based on a user's feedback, I've defaulted to using a 200ms offset for placement of CD markers, pregaps and region starts. This means you don't have to build in any offset at the start of the media item itself (unless, for example, you need the room tone to fade in naturally) This seems to be a good default mastering value but I'm also keen to make this user-defined too as people may have differing needs. I'll think about a good way to do it. Perhaps I will create a general ReaClassical options dialog box for any and all things that can/could be user-defined.

Anyway, if you have thoughts on this please let me know them!

[theorbe]

Hello. I would like to contact you again to show you by video a problem that often occurs when I do tests. I record the sound on tracks by pressing the record key in turn. I do in order what you recommend to make a recording.
When playing back, using the A key, sometimes the sound is played back correctly and sometimes several different tracks are played back at the same time.
I enclose a video file which allows you to see that all the tracks start to sound at the same time.
Have you already had this problem or is it a handling error on my part?
I don't know how to put a video file in this forum... I am posting this message anyway, hoping to be understood. Thanks

[chmaha]

Originally Posted by theorbe

Hello. I would like to contact you again to show you by video a problem that often occurs when I do tests. I record the sound on tracks by pressing the record key in turn. I do in order what you recommend to make a recording.
When playing back, using the A key, sometimes the sound is played back correctly and sometimes several different tracks are played back at the same time.
I enclose a video file which allows you to see that all the tracks start to sound at the same time.
Have you already had this problem or is it a handling error on my part?
I don't know how to put a video file in this forum... I am posting this message anyway, hoping to be understood. Thanks

The A audition shortcut is dependent on where your mouse is at the time of pressing. Hover over a folder panel and the audition will start from the beginning. Hover over a media item on the folder track and it will playback from there (in both cases also soloing all the other tracks in the folder). If you want to audition a spot microphone just hover over that track panel or an item on that track and press A.

If this doesn't answer your question, maybe share the video file via a website like https://www.swisstransfer.com/ or turn it into a GIF?