Hi,
Yes, Mixdown of m4a in 256k is already possible.
The mp3 320k format sounds better and is 1 million times more compatible than the m4a 256k format.
(Even in your own app)
Don’t believe me, do this test.
Email yourself a CUBASIS Mixdown in the m4a 256k format.
Now download the file
After it has fully downloaded, press and hold the file.
Now you will get the option to “open In” several apps.
(CUBASIS will be one of them.)
Tap on CUBASIS and see what happens…
Nothing.
Now Email yourself a mp3 file (created from a different app)
Repeat the above steps…
It will work every time.
So, since saving in the mp3 format is not being addressed in this release, maybe allow the m4a format to “open in” CUBASIS from emai?
sorry, I somewhat thought I had already answered you. Yes, we are aware of this problem. Can you try whether you are able to open the m4a file with other apps?
thanks for trying it out. This is consistent to the feedback that I got from development. It seems that iOS changes the extension of the file in between. However, we might be able to provide a fix in the future.
Thanks so much for checking with your development team. I use CUBASIS everyday. i will be on the look out for a fix for this issue.
(I see that saving in the FLAC Format was added to version1.3, maybe add saving to the MP3 320k format will be in version 1.4’s future???)
hi, apologies in advance, if this has already been answered. I have tried reviewing the doc, and it is not clear to me.
With the new flac import/export into cubasis1.3 … (q) does cubasis operate natively in flac, or does it have to always convert the flac files t .wav in order for them to be accessible in MediaBay so that they can be utilised?
(my flac files seem to alway get converted to .wav …)
thanks in advance
regards,
/Stef
Hi Frieder,
The workaround link that you attached to this thread only takes you to the top of this page.
Could you please insert the link that will take us to the workaround?
yes, I can. Below is my reply from the other thread.
Kind regards,
Frieder
Hello,
we know of this issue and it will be fixed in the next update. As a workaround, I can only recommend to import the files from your library using another technique, for instance iTunes File Sharing. If you have further questions let me know.