If we are given 32mb of Internal memory, why can't we access it after we've loaded a Project? It makes no sense. In the Fantom X, you could load up to 512mb (or more) of samples and STILL be able to use the 32mb of Internal memory for samples, etc.
A Project 'wipes out' the samples, drum kits etc. in the Internal memory when you load it. The internal memory returns only if you power-on without the USB stick.
And if I'm not mistaken, a Project also overrides some of the System settings. Whats the point? This could force you to just use one Project for fear that some of the system settings have changed in another.
I should be able to access my Patches, drum samples, drum kits, and all of the other stuff that the 32mb Internal Memory stores - EVEN AFTER LOADING A PROJECT.
Does anyone here agree with me?
Project vs Internal Memory
-
The Audacity Works
- Posts: 1012
- Joined: 19:02, 15 November 2007
- Location: Hollywood, CA
Re: Project vs Internal Memory
I don't—sorry. That's how the X did it, and it was a huge PITA. In fact, the X's file management garnered more complaints than almost anything.
If you want access to the internal project's patches, samples, drum kits, and other stuff, perform a "Save As Project", and they're included in the new one. Once the new project is up and running, delete the stuff you don't want and keep going.
And you don't have to power up without the USB key to access the internal project. Simply perform a "Load Project" and choose the internal one.
However, I will say it'd be nice to be able to import specific elements from one project into the current (temporary) project—Say, import one sample or group of samples. I'm suspecting this isn't too difficult with a computer. Maybe a future file utility will make this easier?
If you want access to the internal project's patches, samples, drum kits, and other stuff, perform a "Save As Project", and they're included in the new one. Once the new project is up and running, delete the stuff you don't want and keep going.
And you don't have to power up without the USB key to access the internal project. Simply perform a "Load Project" and choose the internal one.
However, I will say it'd be nice to be able to import specific elements from one project into the current (temporary) project—Say, import one sample or group of samples. I'm suspecting this isn't too difficult with a computer. Maybe a future file utility will make this easier?
-
dasinsasion
- Posts: 127
- Joined: 22:49, 25 February 2008
- Location: Central, VA
Re: Project vs Internal Memory
I can still access the samples and patches saved to the internal user memory on my X after a song is loaded. Song and Project is different though. The X doesn't have projects. That seems like it would suck though? If you complain enough someone at Roland will fix it.
Re: Project vs Internal Memory
I liked how the X was able to load all samples in memory at startup. Yes it took 20+ minutes to load but after loading, you had access to all of your Kits at any time. I don't like the new workflow. I think it works best for live performers. Another reason why I'm returning my G6 next week and going back to my Fantom X.
Re: Project vs Internal Memory
And with me it's just the other way round: I *hated* the X kind of sample loading startup and never want to see anything of it in my life again. I'm really thankful that with the G I can use different scenarios with reasonable loading times.
To each his/her own...
To each his/her own...
-
Igglethorpe
- Posts: 592
- Joined: 09:27, 23 January 2005
- Location: Arizona, USA
Re: Project vs Internal Memory
I absolutely love the new "project format" as I came from the V-Synth land. It makes far more sense. One of my favorite features is when I create a new project it is completely empty along with default system settings. Brilliant.
I'm with Audacity and Jimknopf on this one. Love the new workflow and file system saves.
Btw, you still have access to 544 MB of memory for samples. You just can't save your project to internal memory. Who wants to anyway? 32mb is no room at all.
I'm with Audacity and Jimknopf on this one. Love the new workflow and file system saves.
Btw, you still have access to 544 MB of memory for samples. You just can't save your project to internal memory. Who wants to anyway? 32mb is no room at all.
Re: Project vs Internal Memory
No matter how you look at it, project-base patch and sample banks make way more sense.
- No longer you have to worry about doing even small changes which would have made some songs playing wrong sounds.
- No longer you need to wait for minutes when all you need for this or that song is just a dozen small samples.
- No longer you need to connect your Fantom to the computer to arrange sounds, the Librarian can operate on sound banks on your USB drive directly.
- And more.
The only thing that is lacking is an ability to import a patch and samples that it uses from one project into another, V-Synth-style. I would really love if Roland implement this one day.
- No longer you have to worry about doing even small changes which would have made some songs playing wrong sounds.
- No longer you need to wait for minutes when all you need for this or that song is just a dozen small samples.
- No longer you need to connect your Fantom to the computer to arrange sounds, the Librarian can operate on sound banks on your USB drive directly.
- And more.
The only thing that is lacking is an ability to import a patch and samples that it uses from one project into another, V-Synth-style. I would really love if Roland implement this one day.
Re: Project vs Internal Memory
Yes, Projects are a definite improvement.
But what I was saying is that we should have access to ALL of the ram at once (which we can do on the X).
When a Project is loaded it uses the dimm ram, the same way loading up to 512mb of samples from the Card does in the X. (please correct me if I'm wrong)
In the X you always have access to the internal ram (32mb) as well; which I use for one-shot drum samples (kicks, snares, hats etc).
In the G, we have no access to the Internal ram after a Project is loaded. What happens to the 32 (or 50)mb?
I think we need this, and also a way to move material between Projects, as Artemiy, Audacity and others have suggested.
But what I was saying is that we should have access to ALL of the ram at once (which we can do on the X).
When a Project is loaded it uses the dimm ram, the same way loading up to 512mb of samples from the Card does in the X. (please correct me if I'm wrong)
In the X you always have access to the internal ram (32mb) as well; which I use for one-shot drum samples (kicks, snares, hats etc).
In the G, we have no access to the Internal ram after a Project is loaded. What happens to the 32 (or 50)mb?
I think we need this, and also a way to move material between Projects, as Artemiy, Audacity and others have suggested.
-
Igglethorpe
- Posts: 592
- Joined: 09:27, 23 January 2005
- Location: Arizona, USA
Re: Project vs Internal Memory
We DO have access to the internal RAM. 512mb + 32 = 544mb. When I load an empty project, that is what I see available for samples. As far as saving projects go, I have a 2 gig memory stick. I do not see the limitations you are talking about.
The only memory we "loose" is the 32mb of flash memory for internal storage. Considering my projects use more than 32mb of memory, I do not consider this a problem since I use memory sticks.
The only memory we "loose" is the 32mb of flash memory for internal storage. Considering my projects use more than 32mb of memory, I do not consider this a problem since I use memory sticks.
-
The Audacity Works
- Posts: 1012
- Joined: 19:02, 15 November 2007
- Location: Hollywood, CA
Re: Project vs Internal Memory
Artemiy:
Thanks!
Really? Wow, I didn't notice that. You're telling me I can use the librarian to set up banks for clients without even having a G handy? That's gonna save me a TON of hassle...- No longer you need to connect your Fantom to the computer to arrange sounds, the Librarian can operate on sound banks on your USB drive directly.
Thanks!
Re: Project vs Internal Memory
cgreene: on the G everything is working around the "project" concept. So the "banks" in the internal and card memory on the Fantom-X do not translate to this concept, you need to understand this.
Audacity: yes, the Librarian works without the actual G, by operating the SVD files directly from your computer. This totally rocks!
Audacity: yes, the Librarian works without the actual G, by operating the SVD files directly from your computer. This totally rocks!
Re: Project vs Internal Memory
One thing that alway caught people out on the X was when they did not have a card installed and had 512mb ram installed..
They are happily creating song and samples and then they want to save everything...
USER MEMORY FULL! Ooops!
Insert a card try save everything..
USER MEMORY FULL!!
why?
the fantom x without a card installed assigned the label USER: to all samples
where as if you had started your project with card inserted all samples would have been assigned CARD:
when you press Save all it saw USER and tryed to save to user ram and you got his error..
The Fantom G you will notice it ALWAYS assigns USER to all samples but it now allows you to choose where you want to save to.
The V synth 1 and 2 had Patch import but for some reason they dropped this on the V GT.
This is what is needed to resolve the problem.
They are happily creating song and samples and then they want to save everything...
USER MEMORY FULL! Ooops!
Insert a card try save everything..
USER MEMORY FULL!!
why?
the fantom x without a card installed assigned the label USER: to all samples
where as if you had started your project with card inserted all samples would have been assigned CARD:
when you press Save all it saw USER and tryed to save to user ram and you got his error..
The Fantom G you will notice it ALWAYS assigns USER to all samples but it now allows you to choose where you want to save to.
The V synth 1 and 2 had Patch import but for some reason they dropped this on the V GT.
This is what is needed to resolve the problem.
Re: Project vs Internal Memory
My problem is that I've gotten very comfortable with the X.
The G comes along and 'flips the script', especially in the sequencer and storage options.
I'll keep using the X for the one-man-band gigs because I have 300+ songs in svq format and the G wont read them and I'm too lazy to convert them to smf's.
The G is gonna be the centerpiece of the studio because everything will go into or through it to my DAW. Also, It's a great board for playing with bands, thanks to Live Mode.
I just have to quit trying to make it replace the X.
The G comes along and 'flips the script', especially in the sequencer and storage options.
I'll keep using the X for the one-man-band gigs because I have 300+ songs in svq format and the G wont read them and I'm too lazy to convert them to smf's.
The G is gonna be the centerpiece of the studio because everything will go into or through it to my DAW. Also, It's a great board for playing with bands, thanks to Live Mode.
I just have to quit trying to make it replace the X.
-
dasinsasion
- Posts: 127
- Joined: 22:49, 25 February 2008
- Location: Central, VA
Re: Project vs Internal Memory
cgreene it is not a "problem" to be comfortable with the X (as some would try and convince you different?). Everyone has their own opinion and preferences. Let people say what they wish, no one has the time to argue about which is better and who should use what. Most of us are not profiting off of these synths, "the big 3" are. I will say it again and I am done with it, "I am satisfied with my X and all of its shortcomings".