Drambo - this was just posted on Facebook

Gravitas

@gregsmith said:

@mistercharlie said:

@gregsmith said:

What about if you move the original sample file? Sounds like a lot to keep up with to me

Then it won’t be in the folder any more. If you take a sample out of a folder, it's no longer in that folder.

I’d rather it was stored in Drambo with the song in case I forget about it but I understand why people with well organised sample libraries will be all good.

You can save the samples within the Drambo project.
Use “Save as” and the option is there.

Fingolfinzz

@echoopera said:

@Fingolfinzz said:
Would it be a waste of time to do a big set up based around Drambo right now? I’m wanting to make my live setup centered around Drambo with a lot of midi mapping and whatnot so will the update change that drastically to where I’d need to rethink everything all over? I’ve been holding off waiting for the update but it’s starting to get to a point where I need to get going

I would get going and not wait. Midi mappings should open just fine in the new version.

The reason i say this is that using Drambo now will help you identify what you’re trying to accomplish now.

Don’t build a setup for the future when you can setup now. Drambo is great as a midi sequencer and brains for any setup NOW and will be in the future.

No one knows when the update will be released except the developer of Drambo. The wait will be worth it i am sure.

Yeah I might as well get something going on it. I have a few templates saved so far but ended up getting a lot of new gear I wanted to bring into the mix with it. The sequencing is phenomenal and the update will probably blow my mind. I have a cvpal with my euro that pairs up really well with Drambo as well giving me lots of sequencing or cv options for my euro modules and it has saved me a shit load of money in modules I don’t have to buy now

auxmux

So, I checked, Import Folder for me imported the files into Drambo itself, vs just references. I didn't have external storage connected, and my imported files were present.

I didn't try it but the +Folder option might be the way to reference a folder, that's outside of Drambo.

Gravitas

@Fingolfinzz said:

@echoopera said:

@Fingolfinzz said:
Would it be a waste of time to do a big set up based around Drambo right now? I’m wanting to make my live setup centered around Drambo with a lot of midi mapping and whatnot so will the update change that drastically to where I’d need to rethink everything all over? I’ve been holding off waiting for the update but it’s starting to get to a point where I need to get going

I would get going and not wait. Midi mappings should open just fine in the new version.

The reason i say this is that using Drambo now will help you identify what you’re trying to accomplish now.

Don’t build a setup for the future when you can setup now. Drambo is great as a midi sequencer and brains for any setup NOW and will be in the future.

No one knows when the update will be released except the developer of Drambo. The wait will be worth it i am sure.

Yeah I might as well get something going on it. I have a few templates saved so far but ended up getting a lot of new gear I wanted to bring into the mix with it. The sequencing is phenomenal and the update will probably blow my mind. I have a cvpal with my euro that pairs up really well with Drambo as well giving me lots of sequencing or cv options for my euro modules and it has saved me a shit load of money in modules I don’t have to buy now

Similar to what Echoopera has stated.

Get your flow happening now.
Why wait for an update to get creative.

Whatever you can do using the sequencer now you will be able
to build upon with ease with the upcoming update.
It’s that fluid and yeah, it’s saved me a load of money as well.
I love effects processors.

echoopera

@Fingolfinzz said:

@echoopera said:

@Fingolfinzz said:
Would it be a waste of time to do a big set up based around Drambo right now? I’m wanting to make my live setup centered around Drambo with a lot of midi mapping and whatnot so will the update change that drastically to where I’d need to rethink everything all over? I’ve been holding off waiting for the update but it’s starting to get to a point where I need to get going

I would get going and not wait. Midi mappings should open just fine in the new version.

The reason i say this is that using Drambo now will help you identify what you’re trying to accomplish now.

Don’t build a setup for the future when you can setup now. Drambo is great as a midi sequencer and brains for any setup NOW and will be in the future.

No one knows when the update will be released except the developer of Drambo. The wait will be worth it i am sure.

Yeah I might as well get something going on it. I have a few templates saved so far but ended up getting a lot of new gear I wanted to bring into the mix with it. The sequencing is phenomenal and the update will probably blow my mind. I have a cvpal with my euro that pairs up really well with Drambo as well giving me lots of sequencing or cv options for my euro modules and it has saved me a shit load of money in modules I don’t have to buy now

That’s the spirit. Drambo by itself should save a person at least $2500 if you add up the kind of hardware it replaces.

Frank303

@Paa89 said:

@mistercharlie said:

@Paa89 said:

@auxmux said:

@mistercharlie said:

@auxmux said:

@mistercharlie said:
@tahiche Drambo is already pretty good at this. You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.

How do you do this?

Choose "Import Folder" in any Drambo's file import dialog:

Ah got it, I thought that imported files to Drambo itself, so if I import from a flash drive, are the files not in drambo?

This does copy the folder into Drambo ecosystem. When I do this, I can see Drambo memory increasing.

It doesn’t import anything—that’s the point. You can leave samples in any folder, and Drambo keeps a reference to that folder. No duplicates, no imports. Very handy.

Not sure how this works with external storage though. Why not test it and tell us what happens?

@Frank303 said:

@Paa89 said:

@auxmux said:

@mistercharlie said:

@auxmux said:

@mistercharlie said:
@tahiche Drambo is already pretty good at this. You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.

How do you do this?

Choose "Import Folder" in any Drambo's file import dialog:

Ah got it, I thought that imported files to Drambo itself, so if I import from a flash drive, are the files not in drambo?

This does copy the folder into Drambo ecosystem. When I do this, I can see Drambo memory increasing.

Confusing, I know, but if you check your iPad storage space, that won't increase. The os simply makes a link to the file, not a copy. You can check this (I did) by noting the iPad space left, adding a 2gb folder to the iPad, note storage again, then import the folder into Drambo and check the total storage again. Same for say, Audioshare and more apps.

This is interesting. i just tried again and you guys are right. Drambo size stays the same.
But if i delete the folder or move it from Files APP, that folder is still present in Drambo.
iOS file management is confusing.

Yes it’s confusing. The thing is, you can remove ‘the file’ anywhere but in Drambo, and it will still be available in Drambo. Or, for example with Launchpad and Blockswaves, I add samples from laptop, import into blockswave, then delete from files app, storage stays the same. So if you delete the ‘original ‘ file, but it’s referenced somewhere, the file is still there. Quite ingenious I might say, you just need to wrap your head around it. And there are a lot of ways it could be improved.

rs2000

Good point @Frank303. Some way to show all locations of the same file in Files.app would be a useful thing.

tahiche

@gregsmith said:

@mistercharlie said:

@Paa89 said:

@auxmux said:

@mistercharlie said:

@auxmux said:

@mistercharlie said:
@tahiche Drambo is already pretty good at this. You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.

How do you do this?

Choose "Import Folder" in any Drambo's file import dialog:

Ah got it, I thought that imported files to Drambo itself, so if I import from a flash drive, are the files not in drambo?

This does copy the folder into Drambo ecosystem. When I do this, I can see Drambo memory increasing.

It doesn’t import anything—that’s the point. You can leave samples in any folder, and Drambo keeps a reference to that folder. No duplicates, no imports. Very handy.

Not sure how this works with external storage though. Why not test it and tell us what happens?

What about if you move the original sample file? Sounds like a lot to keep up with to me

iOS file system is very confusing. It’s certainly not as straightforward as a simple file reference (link to the original).
If you delete the original file, it’s not deleted from the imported Drambo’s library. So in that vein I assume if you move the original file the space is duplicated.
Also it might not take up space on your iPad, but I believe it does on backups.

Actually what I’m wanting is precisely this “ You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.”. Point to a folder is not importing a folder.
Pointing to a folder would mean you tell Drambo to use folder XX on your iPad/SSD as a source for sample browsing. No duplicates, no hanging files, nicely centralized. Downside?. If you made an instrument using a sample that has been moved or deleted it’d break. But you can also delete stuff within Drambo…

Anyhow, it’s very messy and confusing. Made even worse by Apple not giving numbers properly. I’ve done tests with this in the past.
If you add say a 10GB sample lib to your iPad. The “on my iPad” is increased by 10GB. The iPad storage reading is increased by 10. All ok.
Now you import that lib to Drambo. iPad storage stays the same but the Drambo storage tab is increased by 10GB. So you have 10gb on the “on my iPad” + 10gb on Drambo. Numbers don’t add up. But hey, apparently that’s not real. By all means it’s messy and hard to maintain.

Paa89

@Frank303 said:

@Paa89 said:

@mistercharlie said:

@Paa89 said:

@auxmux said:

@mistercharlie said:

@auxmux said:

@mistercharlie said:
@tahiche Drambo is already pretty good at this. You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.

How do you do this?

Choose "Import Folder" in any Drambo's file import dialog:

Ah got it, I thought that imported files to Drambo itself, so if I import from a flash drive, are the files not in drambo?

This does copy the folder into Drambo ecosystem. When I do this, I can see Drambo memory increasing.

It doesn’t import anything—that’s the point. You can leave samples in any folder, and Drambo keeps a reference to that folder. No duplicates, no imports. Very handy.

Not sure how this works with external storage though. Why not test it and tell us what happens?

@Frank303 said:

@Paa89 said:

@auxmux said:

@mistercharlie said:

@auxmux said:

@mistercharlie said:
@tahiche Drambo is already pretty good at this. You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.

How do you do this?

Choose "Import Folder" in any Drambo's file import dialog:

Ah got it, I thought that imported files to Drambo itself, so if I import from a flash drive, are the files not in drambo?

This does copy the folder into Drambo ecosystem. When I do this, I can see Drambo memory increasing.

Confusing, I know, but if you check your iPad storage space, that won't increase. The os simply makes a link to the file, not a copy. You can check this (I did) by noting the iPad space left, adding a 2gb folder to the iPad, note storage again, then import the folder into Drambo and check the total storage again. Same for say, Audioshare and more apps.

This is interesting. i just tried again and you guys are right. Drambo size stays the same.
But if i delete the folder or move it from Files APP, that folder is still present in Drambo.
iOS file management is confusing.

Yes it’s confusing. The thing is, you can remove ‘the file’ anywhere but in Drambo, and it will still be available in Drambo. Or, for example with Launchpad and Blockswaves, I add samples from laptop, import into blockswave, then delete from files app, storage stays the same. So if you delete the ‘original ‘ file, but it’s referenced somewhere, the file is still there. Quite ingenious I might say, you just need to wrap your head around it. And there are a lot of ways it could be improved.

Apple needs to fix this especially to make it easy on developers.

RajahP

Wow.. such a nice day for a Drambo update.. Piano-roll, Improved StepSeq, and who knows what else..
edit.. so can you add your own CCs on the SS’s bar? I’m seeing a ‘+’ sign there…

0tolerance4silence

@RajahP said:
Wow.. such a nice day for a Drambo update.. Piano-roll, Improved StepSeq, and who knows what else..
edit.. so can you add your own CCs on the SS’s bar? I’m seeing a ‘+’ sign there…

The ‘+’ is for quick drawing... enable ‘+’ swipe from left to right to draw note velocities in the sequence. Works for several editor pages.
Custom CCs were discussed and will be added later, not in this update, though a module based ‘workaround’ will be coming now until proper implementation is ready.

Grandbear

@0tolerance4silence said:

@RajahP said:
Wow.. such a nice day for a Drambo update.. Piano-roll, Improved StepSeq, and who knows what else..
edit.. so can you add your own CCs on the SS’s bar? I’m seeing a ‘+’ sign there…

The ‘+’ is for quick drawing... enable ‘+’ swipe from left to right to draw note velocities in the sequence. Works for several editor pages.
Custom CCs were discussed and will be added later, not in this update, though a module based ‘workaround’ will be coming now until proper implementation is ready.

That workaround would be something like p-locking/modulating a Slider module that's connected to a MIDI CC Generator module, right?

0tolerance4silence

@Grandbear said:

@0tolerance4silence said:

@RajahP said:
Wow.. such a nice day for a Drambo update.. Piano-roll, Improved StepSeq, and who knows what else..
edit.. so can you add your own CCs on the SS’s bar? I’m seeing a ‘+’ sign there…

The ‘+’ is for quick drawing... enable ‘+’ swipe from left to right to draw note velocities in the sequence. Works for several editor pages.
Custom CCs were discussed and will be added later, not in this update, though a module based ‘workaround’ will be coming now until proper implementation is ready.

That workaround would be something like p-locking/modulating a Slider module that's connected to a MIDI CC Generator module, right?

It’s an additional module ‘CC controller’ that converts incoming CC to CV (just like CC modulator does currently) but it has an additional knob that represents the CC value.
Effectively it allows you to record CC as automation (until a dedicated CC editor is ready). Also can be p-locked, modulated or the recorded automation sent out as CC for external uses via CC generator.

Grandbear

@0tolerance4silence said:

@Grandbear said:

@0tolerance4silence said:

@RajahP said:
Wow.. such a nice day for a Drambo update.. Piano-roll, Improved StepSeq, and who knows what else..
edit.. so can you add your own CCs on the SS’s bar? I’m seeing a ‘+’ sign there…

The ‘+’ is for quick drawing... enable ‘+’ swipe from left to right to draw note velocities in the sequence. Works for several editor pages.
Custom CCs were discussed and will be added later, not in this update, though a module based ‘workaround’ will be coming now until proper implementation is ready.

That workaround would be something like p-locking/modulating a Slider module that's connected to a MIDI CC Generator module, right?

It’s an additional module ‘CC controller’ that converts incoming CC to CV (just like CC modulator does currently) but it has an additional knob that represents the CC value.
Effectively it allows you to record CC as automation (until a dedicated CC editor is ready). Also can be p-locked, modulated or the recorded automation sent out as CC for external uses via CC generator.

I think I understand, thanks!

aaa

@tahiche said:

Anyhow, it’s very messy and confusing. Made even worse by Apple not giving numbers properly. I’ve done tests with this in the past.
If you add say a 10GB sample lib to your iPad. The “on my iPad” is increased by 10GB. The iPad storage reading is increased by 10. All ok.
Now you import that lib to Drambo. iPad storage stays the same but the Drambo storage tab is increased by 10GB. So you have 10gb on the “on my iPad” + 10gb on Drambo. Numbers don’t add up. But hey, apparently that’s not real. By all means it’s messy and hard to maintain.

I don’t know about iOS/iPadOS, but on macOS running APFS, it’s well documented that the storage size readings are not accurate. This is because duplicate files do not actually duplicate the files. It just creates an alias - but it doesn’t tell the file system that it’s an alias, so it reads the storage size as if both files are taking up space when in fact all the duplicates refer to the same data. Which is to say, this is how Apple storage works and it’s not unique to Drambo. However other apps often “break” this smart storage-saving trick by not properly following the process that Apple recommends for creating these smart duplicates. Many apps really do increase the storage used by creating real duplicates. It’s impossible to know which is happening without looking at the code or asking the devs, afaik.

EDIT: Here’s a blog post about this “cloning” feature. Their site has lots of good posts on related topics, too. https://eclecticlight.co/2021/04/02/how-can-you-tell-whether-a-file-has-been-cloned-in-apfs/

RajahP

@0tolerance4silence said:

@RajahP said:
Wow.. such a nice day for a Drambo update.. Piano-roll, Improved StepSeq, and who knows what else..
edit.. so can you add your own CCs on the SS’s bar? I’m seeing a ‘+’ sign there…

The ‘+’ is for quick drawing... enable ‘+’ swipe from left to right to draw note velocities in the sequence. Works for several editor pages.
Custom CCs were discussed and will be added later, not in this update, though a module based ‘workaround’ will be coming now until proper implementation is ready.

Thanks for the info.. Don’t intend to get you into any hot NDA water, now.. Thanks..😎

gregsmith

Anyone know if there’s a Drambo discord server?

ohwell

I love the look of that new step sliders workflow! My favorite kind of interface for step sequencing on touch screen. Drambo is such a wonderful environment, that will definitely expand how i use it.

auxmux

@gregsmith said:
Anyone know if there’s a Drambo discord server?

Agreed, this would be great, esp for beta discussion.

wim

@tahiche said:

@gregsmith said:

@mistercharlie said:

@Paa89 said:

@auxmux said:

@mistercharlie said:

@auxmux said:

@mistercharlie said:
@tahiche Drambo is already pretty good at this. You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.

How do you do this?

Choose "Import Folder" in any Drambo's file import dialog:

Ah got it, I thought that imported files to Drambo itself, so if I import from a flash drive, are the files not in drambo?

This does copy the folder into Drambo ecosystem. When I do this, I can see Drambo memory increasing.

It doesn’t import anything—that’s the point. You can leave samples in any folder, and Drambo keeps a reference to that folder. No duplicates, no imports. Very handy.

Not sure how this works with external storage though. Why not test it and tell us what happens?

What about if you move the original sample file? Sounds like a lot to keep up with to me

iOS file system is very confusing. It’s certainly not as straightforward as a simple file reference (link to the original).
If you delete the original file, it’s not deleted from the imported Drambo’s library. So in that vein I assume if you move the original file the space is duplicated.
Also it might not take up space on your iPad, but I believe it does on backups.

Actually what I’m wanting is precisely this “ You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.”. Point to a folder is not importing a folder.
Pointing to a folder would mean you tell Drambo to use folder XX on your iPad/SSD as a source for sample browsing. No duplicates, no hanging files, nicely centralized. Downside?. If you made an instrument using a sample that has been moved or deleted it’d break. But you can also delete stuff within Drambo…

Anyhow, it’s very messy and confusing. Made even worse by Apple not giving numbers properly. I’ve done tests with this in the past.
If you add say a 10GB sample lib to your iPad. The “on my iPad” is increased by 10GB. The iPad storage reading is increased by 10. All ok.
Now you import that lib to Drambo. iPad storage stays the same but the Drambo storage tab is increased by 10GB. So you have 10gb on the “on my iPad” + 10gb on Drambo. Numbers don’t add up. But hey, apparently that’s not real. By all means it’s messy and hard to maintain.

It begins to make some sense if you can get your head around it.

• It isn't like a *nix symbolic link where all the links point to a file and if you delete the original all the links break.
• It is a different kind of pointer to a storage location that persists until the very last reference is gone. Every instance of the file, including the original is just a pointer to this abstracted storage.
• This is great, because if you do delete the original or another clone of it, you never break other apps or songs using it.
• It has properties where if one of the clones is changed, it still points to the original, but keeps track of the changes. It doesn't copy the file even though the clone is now different than the other clones.

• This does not apply to files on external storage. Think about it. The external storage isn't an APFS device. The OS can't keep track of the abstracted storage.

  • Apps can either copy the file from the external drive, at which point it begins to be treated like an APFS object, or ...
  • Apps can create a symbolic link to the external file, which will fail if the drive isn't present or the file is removed.

• I believe files copied into or out of Drambo using the WebDAV server do take up duplicate space since those files exit and are put back into the APFS.

As for the reporting, it isn't wrong, it just needs to be the way it is to accommodate the ambiguities this abstraction introduces. Let's say app A, B, and C all reference the file "foo.wav". It's obviously incorrect to triple the storage in overall storage. What are A, B, and C supposed to report? If the initial file was imported by app A, should B and C report zero since they didn't increase storage by referencing the file? If they did report zero and then app A deleted its reference, should B or C now report it? Which one? There's no way to reconcile all this until every last reference to the file is removed and the actual storage is freed up.

If there's a better way to report file usage under this system, I'd be interested in hearing it. I certainly wouldn't want to give up the storage efficiency of APFS just to make the reporting easier to understand though.

It would be nice if there was a way to look up all the clones of a file with info about the apps that use it. Personally I don't see any use-case where that would be helpful, but I suppose it could make people feel more in control.

Jumpercollins

My only wish is that a lighter skin for Drambo be made available.

gregsmith

@wim said:

@tahiche said:

@gregsmith said:

@mistercharlie said:

@Paa89 said:

@auxmux said:

@mistercharlie said:

@auxmux said:

@mistercharlie said:
@tahiche Drambo is already pretty good at this. You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.

How do you do this?

Choose "Import Folder" in any Drambo's file import dialog:

Ah got it, I thought that imported files to Drambo itself, so if I import from a flash drive, are the files not in drambo?

This does copy the folder into Drambo ecosystem. When I do this, I can see Drambo memory increasing.

It doesn’t import anything—that’s the point. You can leave samples in any folder, and Drambo keeps a reference to that folder. No duplicates, no imports. Very handy.

Not sure how this works with external storage though. Why not test it and tell us what happens?

What about if you move the original sample file? Sounds like a lot to keep up with to me

iOS file system is very confusing. It’s certainly not as straightforward as a simple file reference (link to the original).
If you delete the original file, it’s not deleted from the imported Drambo’s library. So in that vein I assume if you move the original file the space is duplicated.
Also it might not take up space on your iPad, but I believe it does on backups.

Actually what I’m wanting is precisely this “ You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.”. Point to a folder is not importing a folder.
Pointing to a folder would mean you tell Drambo to use folder XX on your iPad/SSD as a source for sample browsing. No duplicates, no hanging files, nicely centralized. Downside?. If you made an instrument using a sample that has been moved or deleted it’d break. But you can also delete stuff within Drambo…

Anyhow, it’s very messy and confusing. Made even worse by Apple not giving numbers properly. I’ve done tests with this in the past.
If you add say a 10GB sample lib to your iPad. The “on my iPad” is increased by 10GB. The iPad storage reading is increased by 10. All ok.
Now you import that lib to Drambo. iPad storage stays the same but the Drambo storage tab is increased by 10GB. So you have 10gb on the “on my iPad” + 10gb on Drambo. Numbers don’t add up. But hey, apparently that’s not real. By all means it’s messy and hard to maintain.

It begins to make some sense if you can get your head around it.

• It isn't like a *nix symbolic link where all the links point to a file and if you delete the original all the links break.
• It is a different kind of pointer to a storage location that persists until the very last reference is gone. Every instance of the file, including the original is just a pointer to this abstracted storage.
• This is great, because if you do delete the original or another clone of it, you never break other apps or songs using it.
• It has properties where if one of the clones is changed, it still points to the original, but keeps track of the changes. It doesn't copy the file even though the clone is now different than the other clones.

• This does not apply to files on external storage. Think about it. The external storage isn't an APFS device. The OS can't keep track of the abstracted storage.

  • Apps can either copy the file from the external drive, at which point it begins to be treated like an APFS object, or ...
  • Apps can create a symbolic link to the external file, which will fail if the drive isn't present or the file is removed.

• I believe files copied into or out of Drambo using the WebDAV server do take up duplicate space since those files exit and are put back into the APFS.

As for the reporting, it isn't wrong, it just needs to be the way it is to accommodate the ambiguities this abstraction introduces. Let's say app A, B, and C all reference the file "foo.wav". It's obviously incorrect to triple the storage in overall storage. What are A, B, and C supposed to report? If the initial file was imported by app A, should B and C report zero since they didn't increase storage by referencing the file? If they did, report zero and then app A deleted its reference, should B or C now report it? Which one? There's no way to reconcile all this until every last reference to the file is removed and the actual storage is freed up.

If there's a better way to report file usage under this system, I'd be interested in hearing it. I certainly wouldn't want to give up the storage efficiency of APFS just to make the reporting easier to understand though.

It would be nice if there was a way to look up all the clones of a file with info about the apps that use it. Personally I don't see any use-case where that would be helpful, but I suppose it could make people feel more in control.

Thanks for this @wim . I get it now.

Samu

@Jumpercollins said:
My only wish is that a lighter skin for Drambo be made available.

I agree and also some kind of UI Zoom considering that my eye-sight is getting worse faster than I would like...
@giku_beepstreet Is the one in charge

I'm not expecting full 'theme control' like in Renoise or SunVox...

Michael_R_Grant

@RajahP said:
Wow.. such a nice day for a Drambo update.. Piano-roll, Improved StepSeq, and who knows what else..
edit.. so can you add your own CCs on the SS’s bar? I’m seeing a ‘+’ sign there…

You ain’t seen nothing yet!

Jumpercollins

@Samu said:

@Jumpercollins said:
My only wish is that a lighter skin for Drambo be made available.

I agree and also some kind of UI Zoom considering that my eye-sight is getting worse faster than I would like...
@giku_beepstreet Is the one in charge

I'm not expecting full 'theme control' like in Renoise or SunVox...

A lighter skin especially with the new piano roll would make seeing between the lines better.

RajahP

@Michael_R_Grant said:

@RajahP said:
Wow.. such a nice day for a Drambo update.. Piano-roll, Improved StepSeq, and who knows what else..
edit.. so can you add your own CCs on the SS’s bar? I’m seeing a ‘+’ sign there…

You ain’t seen nothing yet!

Ohh..

Looking at another pic.. I am hoping that midi import has been reconsidered.. Been recording midi into Drambo (current release), it is nice, the piano-roll will take it to an new level… but sometimes you may just want to import a midi clip and ‘process’ it in the SS (Probability, Skip, Etc) and see what that clip turns into.. keeping the creative flow on.. seem like a natural to implement midi import after looking at this pic..

Looking forward…

[Deleted User]

The user and all related content has been deleted.

Frank303

@wim said:

@tahiche said:

@gregsmith said:

@mistercharlie said:

@Paa89 said:

@auxmux said:

@mistercharlie said:

@auxmux said:

@mistercharlie said:
@tahiche Drambo is already pretty good at this. You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.

How do you do this?

Choose "Import Folder" in any Drambo's file import dialog:

Ah got it, I thought that imported files to Drambo itself, so if I import from a flash drive, are the files not in drambo?

This does copy the folder into Drambo ecosystem. When I do this, I can see Drambo memory increasing.

It doesn’t import anything—that’s the point. You can leave samples in any folder, and Drambo keeps a reference to that folder. No duplicates, no imports. Very handy.

Not sure how this works with external storage though. Why not test it and tell us what happens?

What about if you move the original sample file? Sounds like a lot to keep up with to me

iOS file system is very confusing. It’s certainly not as straightforward as a simple file reference (link to the original).
If you delete the original file, it’s not deleted from the imported Drambo’s library. So in that vein I assume if you move the original file the space is duplicated.
Also it might not take up space on your iPad, but I believe it does on backups.

Actually what I’m wanting is precisely this “ You can point it at a folder anywhere on your iPad, and it will keep an “alias” to it inside Drambo’s own file browser.”. Point to a folder is not importing a folder.
Pointing to a folder would mean you tell Drambo to use folder XX on your iPad/SSD as a source for sample browsing. No duplicates, no hanging files, nicely centralized. Downside?. If you made an instrument using a sample that has been moved or deleted it’d break. But you can also delete stuff within Drambo…

Anyhow, it’s very messy and confusing. Made even worse by Apple not giving numbers properly. I’ve done tests with this in the past.
If you add say a 10GB sample lib to your iPad. The “on my iPad” is increased by 10GB. The iPad storage reading is increased by 10. All ok.
Now you import that lib to Drambo. iPad storage stays the same but the Drambo storage tab is increased by 10GB. So you have 10gb on the “on my iPad” + 10gb on Drambo. Numbers don’t add up. But hey, apparently that’s not real. By all means it’s messy and hard to maintain.

It begins to make some sense if you can get your head around it.

• It isn't like a *nix symbolic link where all the links point to a file and if you delete the original all the links break.
• It is a different kind of pointer to a storage location that persists until the very last reference is gone. Every instance of the file, including the original is just a pointer to this abstracted storage.
• This is great, because if you do delete the original or another clone of it, you never break other apps or songs using it.
• It has properties where if one of the clones is changed, it still points to the original, but keeps track of the changes. It doesn't copy the file even though the clone is now different than the other clones.

• This does not apply to files on external storage. Think about it. The external storage isn't an APFS device. The OS can't keep track of the abstracted storage.

  • Apps can either copy the file from the external drive, at which point it begins to be treated like an APFS object, or ...
  • Apps can create a symbolic link to the external file, which will fail if the drive isn't present or the file is removed.

• I believe files copied into or out of Drambo using the WebDAV server do take up duplicate space since those files exit and are put back into the APFS.

As for the reporting, it isn't wrong, it just needs to be the way it is to accommodate the ambiguities this abstraction introduces. Let's say app A, B, and C all reference the file "foo.wav". It's obviously incorrect to triple the storage in overall storage. What are A, B, and C supposed to report? If the initial file was imported by app A, should B and C report zero since they didn't increase storage by referencing the file? If they did report zero and then app A deleted its reference, should B or C now report it? Which one? There's no way to reconcile all this until every last reference to the file is removed and the actual storage is freed up.

If there's a better way to report file usage under this system, I'd be interested in hearing it. I certainly wouldn't want to give up the storage efficiency of APFS just to make the reporting easier to understand though.

It would be nice if there was a way to look up all the clones of a file with info about the apps that use it. Personally I don't see any use-case where that would be helpful, but I suppose it could make people feel more in control.

Excellently explained!

RajahP

Has anyone seen Drambo, or did he go to war?

RajahP

.