Maybe this is an android issue. I encounter the problem when trying to copy a midi file to a different location. The midi file was exported via the mediabay in cubasis. I am also unable to transfer the midi file via USB to another computer. Android 13 on a Samsung tablet and cubasis 3.5.2 is my basic setup. Copying/moving audio files being exported the same way via cubasis mediabay does work though. Can anyone reproduce this? I want that midi file to be exported to another device.
The “Permission denied” is coming from your Android file system. It appears that wherever you’re copying that file from, you’re not the owner of that file at that location. That’s a common issue when someone shares files from their Google Drive and they haven’t changed the permissions for anyone to read and write that file.
The other possibility is: the file was copied from Google Drive, but all Google Drive actually shared was a link to the file, not the actual file. Google Drive never makes that distinction clear. So, the lesson I learned the hard way from that is to always open files backed up from Google Drive BEFORE deleting them on Google Drive. The workaround for this issue is Send/Share the file to Dropbox. Then you have to copy the file from Dropbox to your other device or storage location.
I came to the conclusion that Google tries to lockdown your files and they want you to use their Backup app, which can incur you storage fees. Just like they offer to back up all your Photos, so you use more storage and they can make more money off of charging you for storage. They don’t make any of this clear to end-users. IMO, not only is it not user-friendly, I feel it’s a downright dishonest strategy to try and trap you into paying for more storage. Because of the permissions and storage issues associated with Google Drive, I divorced myself from Google Drive long ago. I used to use and like Google Docs and Sheets until I discovered that I had to use Dropbox to actually copy them out of Google Drive, since all Google would copy was links to the actual files. After losing some Google Office files this way, I dropped using their Office apps, too.
More info than you asked for, but I’m betting that the permissions denied message is a result of you being burned, thinking you copied files from Google Drive, when in fact, all you copied was links back to the actual files still residing on Google Drive.
I’ve not seen anyone ever post this info before but users should be aware of what they’re dealing with.
CORRECTION: If all you copied was a link to the file, then most likely nothing would open, but that shouldn’t cause a “Permissions denied” message. So, my original statement that you’re not the Owner of the file OR weren’t granted permission to Read from and Write to that file, is very likely the issue in this case.
Now that’s what I call a well informed reply:+1:
Thanks! Nice to know it was appreciated and not considered overkill.
What is the source of that MIDI file? Your Samsung Tablet? How are you trying to copy this MIDI file, with the Android Files app? Make sure your Files app settings are set to show file extensions. What extension is on this file? If you’re able to see all your file settings of other files and the exported file doesn’t have a .mid extension, I would rename it with that extension tacked on the far right.
Will your Files app show you file permissions? I know there are some good Android File managers in the Google Play store, in case you need to get one to see exactly what permissions the file has and to be certain of the file extension. I seem to recall one called Midnight Commander when I was still in the Android world. There are some good BASH shell tools available, too, but unless you have experience with Shell programming, I don’t recommend going down that route. If you do choose to delve deep, make sure you get one that doesn’t require breaking your device’s security. I have used one very popular one on Android to get low level access to the file system. I would never, though, give it permission to break the Root securiy of the device.
Some Shell apps will want to break your device security to give you Root permission. Never a good idea because you’re opening up your Android device to a 3rd party app and giving it Root permission and full authority over your device. It may tell you that you have Root access, but I’d be willing to bet that the 3rd party app has taken the Root access and given you temporary SuperUser (SU) rights without making you Root. Remember, the core of Android is a Linux kernel with Google Android code running on top, running: the graphical interface, window manager, menu system, file system, etc.
Giving any app or person Root permission is akin to giving someone you don’t know the front door key to your house!!
Thanks for your effort and your reply. — The midi file is product of working with Cubasis. I just exported it via MediaBay from Cubasis. As written above, exporting an Audio file from Cubasis MediaBay leaves me with a movable and copyable file in the filesystem. The exported midi file though is neither movable nor copyable in the file system. So the file permissions might be product of the export from Cubasis. I am not willing to root my Samsung/Android device due to technical and warranty reasons. It might be helpful having the question answered by a Steinberg Official knowing what file permissions are applied in the file-export process. I was not able to find an official bug report tracker here. Is there any?
When ever I transfer a midi file from Cubase to Cubasis and vice versa, I always perform a Midi mixdown, then I export THAT file, I’m not sure if that has different results to just exporting from Media Bay🤔
That’s exactly what i do. It’s the only way to create a midi-file from within Cubasis. So maybe the Mixdown operation sets restricted and rigid access rights to the midi-file (since mixing down an audio file does not show the issue) or there’s a problem in android 13.
I did a Test Project in Cubasis on my iPad Air 3, with 2 tracks: 1 audio and 1 Midi track. I did a Mixdown with MIDI file type selected. I was able to use Cubasis Share in MediaBay and save the Midi file to a folder in iCloud. I then imported that file into AudioShare on my iPad where the Midi track played correctly.
CONCLUSION: My educated guess is that the Android version of Cubasis is not setting the exported file Owner to you with Read and Write permissions.
Thanks for your report which has been shared with the team.
The upcoming Cubasis for Android update will set the read and write permissions accordingly, for all files that are saved.
Awesome, Thank you very much!
Good News. Thank you very much!