Home | ER-101 | ER-102 | ER-301 | Wiki | Contact

Sample editing, lost my way

ER-301
#1

I never got the hang of editing samples on the 301, and think I need some pointers. Where can I read about the sample editing possibilities on the 301? Including what edits are possible where and which button combos to use. Sorry if this is stupid and documented to death, but I’m lost…

I’m currently floating round firmware 0.4.2x…

3 Likes
#2

ya know, i’m pretty new to the ER-301 but i feel exactly the same. probably haven’t done enough digging in the forums/reading around the wiki but i’d love a nice concise answer to this as well.

#3

I’m not sure there’s any documentation in the wiki about this yet. I go through some examples in these tutorials:

http://wiki.orthogonaldevices.com/index.php/How_to_resample_a_single_cycle_waveform
http://wiki.orthogonaldevices.com/index.php/Solo_Trumpet_Performance

Probably the main thing that would be confusing is that some of the operations expect you to have part of the waveform selected before you can perform the operation. So place the cursor at the start or end point, hold down shift and then move the cursor to make a selection, which will be highlighted brighter than the rest of the waveform. Maybe that will help as a starting point?

3 Likes
#4

Thanks, Joe, that looks very helpful!

  1. When do I know if an operation is destructive?

  2. Is there a way to copy the original sample when doing destructive edits, either before or as a part of the edit operation?

1 Like
#5

They are all destructive: trim, cut, normalize, silence, fade in, fade out, and remove DC. They’re destructive in the sense that they actually modify the waveform. There’s no single undo. There is a revert option that undoes everything you’ve done at once and restores it back to the original buffer state.

These operations are just affecting the buffer in RAM, and not being auto-committed to disk. So when you’re finished you can just do a save as from the file operations further down in the menu if you want to make a new file with your changes, while preserving the original. Possibly you can do a save as before you start editing if you want to make an identical copy of the original.

I’d recommend experimenting on some throw-away wave file, just to get comfortable with the workflow.

2 Likes
V0.4.x Firmware Workout: Goofing off never felt this hard
#6

Thanks, that makes sense!

So actually I could just have the edits only live in quick saves…

#7

Got it, thanks @joe!

1 Like
#8

can someone walk me through the steps in v.0.4.27 to save a normalized file? I had a buffer from my sample lib folder which I loaded into manual loops, then I found that the file did not get loaded properly when I booted back up. The buffer that is now associated with the manual loops module is blank.

I am able to relink the buffer from the previous file without issues (settings intact), but it’s not normalized as I would expect.

EDIT: nevermind, I figured it out.

  1. select manual loops
  2. press config
  3. select edit buffer
  4. select menu
  5. scroll to normalize and press enter
  6. select yes
  7. select menu
  8. scroll down to file operations and select save
1 Like
#9

I think it’s worth mention here that a file operation doesn’t have to be destructive, since you can always select save as...

1 Like
#10

Agreed. Excellent, sounds like you’ve mastered it!

1 Like