Update: New Roland SH-101 and now MC-202 for Nanostudio 2

gusgranite

@d4d0ug said:

@gusgranite said:
Sorry, how do you import these into NS2? Ta.

With the obsidian patches, download then ‘send’ or ‘share’ the .zip files with NS2. NS2 does the rest (puts them in the user patches directory). HTH, and was what you were after....

Weird. It doesn’t give me NS2 as an option.

dendy

@gusgranite said:

@rs2000 said:

@gusgranite said:
Sorry, how do you import these into NS2? Ta.

Which?

The 101 and 202 patches.

Just download file from patchstorage directly on device and then use "open in nanostudio" (or it is "save to nanostudio" ? can't remember) standard apple dialogue .. NS unpacks zip file and places patches into Obsidian patch library

@rs2000
Have you watched the vid above?

Watched minute or two but didn't get completely how it is related to discussion we have here )))

Except of having 3 velocity layers multisampled Rhodes as Obsidian patches, with various settings would be cool )

I have them but I'd have to talk to @analog_matt if it's OK to release them, I did it specifically for D1.
Other than that, I think I'll follow your suggestion and play with FM sampling

cool.. looking forward .. i remember when i had borrowed NL3 for a while, i was amazed by complexity of FM modulation ... best FM mod i ever heard on any synth ..

rs2000

@gusgranite said:

@rs2000 said:

@gusgranite said:
Sorry, how do you import these into NS2? Ta.

Which?

The 101 and 202 patches.

You can just tap on the "Download" button of the patchstorage page using Safari, wait until it's downloaded, then tap "More..." on the bottom and choose Nanostudio 2. You may have to scroll sideways if you have many apps installed.

gusgranite

@rs2000 @dendy i don’t mean to clutter this thread but it’s the weirdest thing. NS2 is no longer showing as an available app when I click more. Have rebooted the iPad. Strange.

dendy

hm that is strange .. not even in advanced list ??

gusgranite

@dendy no. It has gone. NS2 opens fine as an app though. iOS 13.2.2

cretakano

@rs2000 said:
And new versions of the six SH-101 patches are up on patchstorage with different names so you can keep both versions:
https://patchstorage.com/sh-101-red-patches/

They're much more punchy now and gel better with cretakano's great MC-202 set.
Still no FX used

New red patches sound great, impressed how close you have got with Obsidian!

@gusgranite If you can't get "open in" working, try copying the zips to Nanostudio 2/Instruments/Obsidian/User in Files app and unzipping them there. They should show up in the the Obsidian browser, but if not go to "manage" and press refresh.

dendy

@gusgranite said:
@dendy no. It has gone. NS2 opens fine as an app though. iOS 13.2.2

Hm, now i'm remembering i already heard from someone about similiar issue with some other app. It was for sure on iOS 13 too, just other app not NS. I remember that deleting app and installing it again solved this issue.

Anyway what @creatakano said - you can unzip it manually directly in Apple Files app. Every obsidian patch is basically just folder with patch name which contains some text (xml) file with patch definition + used samples.

rs2000

@dendy said:

@rs2000
Have you watched the vid above?

Watched minute or two but didn't get completely how it is related to discussion we have here )))

Except of having 3 velocity layers multisampled Rhodes as Obsidian patches, with various settings would be cool )

You guessed right man! That's exactly what I'm working on.
And I can tell you, it's a lot of work (especially looping every single damn sample)

dendy

And I can tell you, it's a lot of work (especially looping every single damn sample)

i can imagine it ! ... last half of year i made probably 200 patches based on multisamples of short waveforms (usually 4 - 40 cycles) from various HW analog synths ... spend hours and hours by cutting them and finding perfect loops

btw, one small tip - when you are creating samples for patches, think twice if your samples needs to be stereo..

because if you don't need that, you can save a lot of space by using mono samples..

if you are using stereo samples, basically you need to use stereo routing of obsidian filter to take advantage of stereo sample (by default obsidian filter is routed as "paralel")

And regarding macro knobs - my strategy is always map XYpad (usually X cutoff and Y resonance - in case it makes sense in patch context) and knobs 1,2,3,4,5,6. Knobs 7,8 i leave always free for users to assign .. and in most cases i assign to knob 5 or 6 reverb/delay of Obsidian build in FX unit (because, usually when you are browing patches, you want to hear it with some reverb/delay, but on other side often you want quickly put it to zero to hear patch without FX - that's why i think it's handy to have direct access to rev/delay from macro kbobs screen)

Of course that are just my personal "rules" for building patches Not mandatory for anybody

looking forward to your Rhodes madness !

btw. did you try already "spectral looping" mode of obsidian ? It's sometimes pretty magic thing, you don't need to set sustain loop in audio editor for that mode

rs2000

@dendy said:
you don't need tell me, i know this pretty good :-D ... in last half of year i made probably 200 patches based on multisamples of short waveforms (usually 4 - 40 cycles) from various HW analog synths ... spend hours and hours by cutting them and finding perfect loops

Really? Didn't know that. Cool.

btw, one small tip - when you are creating samples for patches, think twice if your samples must be stereo.. because if you don't need that, you can save a lot of space by using mono samples.. if you are using stereo samples, basically you need to use stereo routing of obsidian filter to take advantage of stereo sample (by default obsidian filter is routed as "paralel")

Yeah, I have done lots of sample library editing on desktop OS and my aim was always to reduce the lib size to the minimum required to achieve good sound. This is subjective of course but in a song context, samples don't always have to be 24bit, 192kHz, 7.1 surround

And regarding macro knobs - my strategy is always map XYpad (usually X cutoff and Y resonance - in case it makes sense in patch context) and knobs 1,2,3,4,5,6. Knobs 7,8 i leave always free for users to assign .. and in most cases i assign to knob 5 or 6 reverb/delay of Obsidian build in FX unit (because, usually when you are browing patches, you want to hear it with some reverb/delay, but on other side often you want quickly put it to zero to hear patch without FX - that's why i think it's handy to have direct access to rev/delay from macro kbobs screen)

Good point. And being able to map them to multiple destinations simultaneously is gold.

looking forward to your Rhodes madness !

Soon boy, soon

ipadbeatmaking

@dendy u just need to put out an extensive hour or longer course on obsidian. U know it so well

rs2000

Here's a short rendered preview of a known piece by Lee Ritenour:
Bass: SH-101 B
Pads: P6-SoftLead
Keys: 3x Rhodes Mk2 alpha version
Drums: Slate default kit

dendy

wim

@dendy said:
btw, one small tip - when you are creating samples for patches, think twice if your samples needs to be stereo..

because if you don't need that, you can save a lot of space by using mono samples..

Wisdom of the day right there.
It's also much, much easier to find glitch free loop points with mono samples.

I have to say, setting loop points is the most discouraging aspect of sampling for me. If someone came up with an effective tool in an audio editor for doing that, it would sure change a lot. The spectral thing in Obsidian is pretty nice, but still doesn't do the job like I'd like it to.

rs2000

@wim said:

@dendy said:
btw, one small tip - when you are creating samples for patches, think twice if your samples needs to be stereo..

because if you don't need that, you can save a lot of space by using mono samples..

Wisdom of the day right there.
It's also much, much easier to find glitch free loop points with mono samples.

I have to say, setting loop points is the most discouraging aspect of sampling for me. If someone came up with an effective tool in an audio editor for doing that, it would sure change a lot. The spectral thing in Obsidian is pretty nice, but still doesn't do the job like I'd like it to.

If you can somehow get hold of the old Redmatica apps for Mac then grab them. I've never seen a more sophisticated set of tools for creating seamless loops.

wim

Thanks, good tip. I'm not that much of a sampler kinda guy and don't have a Mac. But if I was and I did then I would.

rs2000

@wim said:
But if I was and I did then I would.

That's a great phrase to remember for those special moments

wim

I probably picked it up in a bar from a conversation with some girl.

espiegel123

@wim said:

@dendy said:
btw, one small tip - when you are creating samples for patches, think twice if your samples needs to be stereo..

because if you don't need that, you can save a lot of space by using mono samples..

Wisdom of the day right there.
It's also much, much easier to find glitch free loop points with mono samples.

I have to say, setting loop points is the most discouraging aspect of sampling for me. If someone came up with an effective tool in an audio editor for doing that, it would sure change a lot. The spectral thing in Obsidian is pretty nice, but still doesn't do the job like I'd like it to.

I find that it is pretty easy in Twisted Wave and Auditor. The new end-to-end looper in Auditor gives a zoomed in view of the start and end points.

wim

Indeed, Auditor seems really promising for this.

To be clear, I'm talking about setting sustain loop points within a sample, not looping for the entire sample. Can auditor export with loop points embedded in the file? If it can then it could be perfect for this.

rs2000

@espiegel123 said:

@wim said:

@dendy said:
btw, one small tip - when you are creating samples for patches, think twice if your samples needs to be stereo..

because if you don't need that, you can save a lot of space by using mono samples..

Wisdom of the day right there.
It's also much, much easier to find glitch free loop points with mono samples.

I have to say, setting loop points is the most discouraging aspect of sampling for me. If someone came up with an effective tool in an audio editor for doing that, it would sure change a lot. The spectral thing in Obsidian is pretty nice, but still doesn't do the job like I'd like it to.

I find that it is pretty easy in Twisted Wave and Auditor. The new end-to-end looper in Auditor gives a zoomed in view of the start and end points.

The point isn't so much finding the points, it's rather about finding a way to loop the un-loopable (i.e. samples containing non-periodic audio).

wim

Auditor has the wonderful loop tool though that cross-fades the selected region. At granular enough settings, this could be totally perfect for "forcing" a smooth mid-sample loop. I'm not sure the loop points could be saved in the sample though. If not, a destructive edit, combined with writing down the sample position of the start and endpoints would still do the job, but not as easily.

rs2000

@wim said:
Auditor has the wonderful loop tool though that cross-fades the selected region. At granular enough settings, this could be totally perfect for "forcing" a smooth mid-sample loop. I'm not sure the loop points could be saved in the sample though. If not, a destructive edit, combined with writing down the sample position of the start and endpoints would still do the job, but not as easily.

Sounds interesting. So in other words, Auditor can X-fade-loop and save the resulting audio file including sustain loop markers?
Would you mind trying to load such a sample in Obsidian to see if it works?

wim

@rs2000 said:

@wim said:
Auditor has the wonderful loop tool though that cross-fades the selected region. At granular enough settings, this could be totally perfect for "forcing" a smooth mid-sample loop. I'm not sure the loop points could be saved in the sample though. If not, a destructive edit, combined with writing down the sample position of the start and endpoints would still do the job, but not as easily.

Sounds interesting. So in other words, Auditor can X-fade-loop and save the resulting audio file including sustain loop markers?
Would you mind trying to load such a sample in Obsidian to see if it works?

That's the part I don't know about. I don't know if it can save the loop marks or even if it does whether Obsidian can read them. However, I suppose if it can't, one could write down the start and end sample positions, load the edited sample into Obsidian, then set the loop points to the noted positions. Tedious.

I've worked with audio editors that can save loop and slice points, and I've worked with samplers that can read them. I just don't know what we're workin' with here.

I'll try to do some tests today some time.

rs2000

@wim said:

@rs2000 said:

@wim said:
Auditor has the wonderful loop tool though that cross-fades the selected region. At granular enough settings, this could be totally perfect for "forcing" a smooth mid-sample loop. I'm not sure the loop points could be saved in the sample though. If not, a destructive edit, combined with writing down the sample position of the start and endpoints would still do the job, but not as easily.

Sounds interesting. So in other words, Auditor can X-fade-loop and save the resulting audio file including sustain loop markers?
Would you mind trying to load such a sample in Obsidian to see if it works?

That's the part I don't know about. I don't know if it can save the loop marks or even if it does whether Obsidian can read them. However, I suppose if it can't, one could write down the start and end sample positions, load the edited sample into Obsidian, then set the loop points to the noted positions. Tedious.

I've worked with audio editors that can save loop and slice points, and I've worked with samplers that can read them. I just don't know what we're workin' with here.

I'll try to do some tests today some time.

Thanks a lot!

ipadbeatmaking

@rs2000 said:

@wim said:

@dendy said:
btw, one small tip - when you are creating samples for patches, think twice if your samples needs to be stereo..

because if you don't need that, you can save a lot of space by using mono samples..

Wisdom of the day right there.
It's also much, much easier to find glitch free loop points with mono samples.

I have to say, setting loop points is the most discouraging aspect of sampling for me. If someone came up with an effective tool in an audio editor for doing that, it would sure change a lot. The spectral thing in Obsidian is pretty nice, but still doesn't do the job like I'd like it to.

If you can somehow get hold of the old Redmatica apps for Mac then grab them. I've never seen a more sophisticated set of tools for creating seamless loops.

I’d pay anyone who has it cash money right now for it! Sample Robot is as good as it gets for now it seems, and the sampler in mainstage (which is built from redmatica I hear)

rs2000

@wim Surprise!
BM3 can do all that, I've just tried with a crossfaded loop. Obsidian reads BM3's sustain loop points perfectly, and the sample looped without clicks.

wim

Cool! Once again BM3 sampler rulz. Man, an AU fork of the sampler would be a thing now, wouldn't it?

wim

G> @rs2000 said:

@wim said:

@rs2000 said:

@wim said:
Auditor has the wonderful loop tool though that cross-fades the selected region. At granular enough settings, this could be totally perfect for "forcing" a smooth mid-sample loop. I'm not sure the loop points could be saved in the sample though. If not, a destructive edit, combined with writing down the sample position of the start and endpoints would still do the job, but not as easily.

Sounds interesting. So in other words, Auditor can X-fade-loop and save the resulting audio file including sustain loop markers?
Would you mind trying to load such a sample in Obsidian to see if it works?

That's the part I don't know about. I don't know if it can save the loop marks or even if it does whether Obsidian can read them. However, I suppose if it can't, one could write down the start and end sample positions, load the edited sample into Obsidian, then set the loop points to the noted positions. Tedious.

I've worked with audio editors that can save loop and slice points, and I've worked with samplers that can read them. I just don't know what we're workin' with here.

I'll try to do some tests today some time.

Thanks a lot!

Auditor works perfectly for this! Load the sample, eyeball a likely sustain loop, open the loop tool, adjust in just a little bit of loop crossfade and start playing back the loop. You can then live-tweak the start and end points and the crossfade until it sounds smooth. Export and open in Obsidian. The sustain loop is ready to go with no need to do anything else.

This changes a lot for me!

It works with AudioLayer too!