File path length. Problem loading aif files.

[andreTSV]

Hi

1/ Problem loading aif files. Drag and drop from Live's browser gives random results. Sometimes it works, other times it doesn't load the file, or the correct file is indicated in the DCO Player but the wave and sound pattern corresponds to a previously loaded file(!). No problem with wav or mp3 files.

2/ When a file is loaded into the DCO, its path is displayed, which is excellent. However, when the path is long, the middle characters disappear and are replaced by suspension points, so that the file cannot be found. It can be very annoying (for copyright reasons) not to know exactly where the sample you've loaded came from. Wouldn't it be possible to access the full path by right-clicking?

3/ When a file is loaded into the Grain Buffer, its path appears in the Grain View, which is also very good. Unfortunately, when another program is opened, this information is not available. So you don't know which sound it is, which is a shame if you want to study how the Glitcher works by browsing all the factory presets.

4/ When I create a preset, I sometimes give it a very long name as I note the behavior and add tags. The full name doesn't fit in the program window, as only a little over twenty characters can fit. What's great, however, is that when you click in this window, the program list appears so wide that the full name appears (whereas if you want to access programs via Ableton Live's device bar, the names are considerably truncated (25 characters maximum)).
Unfortunately, this vertical list (from Crusher-X), sometimes containing 240 programs (!), can only be scrolled with the down arrow (which seems to me to be a Windows limitation, as it's something we often encounter), without being able to use the “page down” arrow. MeldaProduction has solved the problem: when you click on “Presets” in MGranularMB, you're taken to a resizable page that lets you navigate easily through the presets.

Best

[freq]

Hi,

thanks for reporting.
1/ Origin Live Samples that are e.g. part of a package are often encrypted for copyright reasons. 3rd party programs like crusher-X can't decrypt them and it results in a read error.
2/ Good point. Thanks for the request - issue filed!
3/ Understand your idea. But the presets using internal links to internal stored preset sample ressources. There is no possibility to access these files from extern
4/ Yes, agreed - we're using the OS Menus for displaying the files. They have limited ways to control (e.g. Keyboard shortcuts) We may reconsider in the future.

Best
accSone