AU SC Editor Issue????
Re: AU SC Editor Issue????
Have you spoke to a roland tech?
Re: AU SC Editor Issue????
I'm wondering if, by using the standalone SCEditor, i'll still manage to get things done somehow.
Here would be my take on this:
Example.........
Launch the DAW and the Standalone Editor,
Select Piano on 1, bass on 2, Dist Gtr on 3 and so on on SCEditor
Record on to the DAW midi tracks Piano on 1, bass on 2 an so forth, so that it matches what's on the sceditor.
Then apply EFFX and panning and what not.
Save/export all changes made in the sceditor to a midi file. Then reopen the midi file with the DAW, copy all the sysex messages and paste them into the the first measure of the sequence recorded earlier. I think that would work.
Any comments?
Here would be my take on this:
Example.........
Launch the DAW and the Standalone Editor,
Select Piano on 1, bass on 2, Dist Gtr on 3 and so on on SCEditor
Record on to the DAW midi tracks Piano on 1, bass on 2 an so forth, so that it matches what's on the sceditor.
Then apply EFFX and panning and what not.
Save/export all changes made in the sceditor to a midi file. Then reopen the midi file with the DAW, copy all the sysex messages and paste them into the the first measure of the sequence recorded earlier. I think that would work.
Any comments?
Re: AU SC Editor Issue????
Hi GSPro,
I don't like being cynical about this situation but if you read the now closed thread over at rolandforums.co.uk you will see that an "official" thread has not yet been opened in its' place.
I don't like being cynical about this situation but if you read the now closed thread over at rolandforums.co.uk you will see that an "official" thread has not yet been opened in its' place.
Re: AU SC Editor Issue????
Mystery, you're fine. You are not imposing in any ways. That's what a forum it's for. I'm here to try and solve some of the issues mentioned in this thread and I will help someone else if I do know the answer to any issues.
Is there a closed thread about this? Can you copy and past the link here? I couldn't find anything there.
Is the new thread about the AU plugin?
I thank you for getting involved with this and I hope you'll get some answers to your issues too.
I'll help if I know the answers.
Is there a closed thread about this? Can you copy and past the link here? I couldn't find anything there.
Is the new thread about the AU plugin?
I thank you for getting involved with this and I hope you'll get some answers to your issues too.
I'll help if I know the answers.
Re: AU SC Editor Issue????
There were some vague references in the above about Digital Performer but only in the sense that there was no confirmation about whether or not it worked.
HTH's
HTH's
Re: AU SC Editor Issue????
Sorry about the multiple postings, but I think the situation is such that if there is not a VST editor available, can the unit still be edited "standalone" eg via the non-DAW application using the 5 pin MIDI port while still being able to trigger sounds in the normal way via USB (midi).
If the above can be done, then providing there is a commitment from Roland Corp. then the VST/AU/RTAS/DXI situation can be addressed at a later time.
There was a patch script or something, a simple text file that you could use in some way to change presets, but it's a bit meaningless since that can be done quite easily via the front panel so I'm sure anyone with this particular device would agree that being able to edit sound parameters (in realtime) in a convenient and non-convoluted way whether or not self-contained is the most desirable situation to have come about.
Of course, who knows if this would require a firmware upgrade.
Best regards
If the above can be done, then providing there is a commitment from Roland Corp. then the VST/AU/RTAS/DXI situation can be addressed at a later time.
There was a patch script or something, a simple text file that you could use in some way to change presets, but it's a bit meaningless since that can be done quite easily via the front panel so I'm sure anyone with this particular device would agree that being able to edit sound parameters (in realtime) in a convenient and non-convoluted way whether or not self-contained is the most desirable situation to have come about.
Of course, who knows if this would require a firmware upgrade.
Best regards
Re: AU SC Editor Issue????
Yes! You can do all editing (everything) directly from the hardware (SonicCell), but the screen being so small, will start to make things a bit harder to look at, after a while. After all settings/mixes are done, just dump all the data at the very start of the sequence (before your music starts).
Again though, read what I said earlier today about the standalone. I haven't got around that yet, but I think it should work. You can try it out and it sure beats working off the little screen. I'll test it out later and post back with good or bad news.
Again though, read what I said earlier today about the standalone. I haven't got around that yet, but I think it should work. You can try it out and it sure beats working off the little screen. I'll test it out later and post back with good or bad news.
Re: AU SC Editor Issue????
Good point.
I'm sure you could do this, since the editor (whether plugin or standalone) can produce sysex information... no problem there .. but I do believe the problem to be much greater as what you are talking about isn't in real-time, hence is not really a meaningful proposition if you know what I mean but sure if you have some presets as starting points then use them as I believe this is what the forum is for
Anyway, what is really needed is a genuine "workaround" hence what I keep saying here with respect to using the standalone to send out MIDI data via the 5 PIN DIN plug to the SC, then just trigger the module via the sequencer.
In fact if the above can be done (my suggestion not yours) no offence but that would be a much more workable solution as who would want to go back to the bad old days of sysex dumps and so on?
We must be serious if we want it to perform properly and that means independent MIDI streams via both ports, so that real-time sysex data can be sent along with General MIDI whichever port is in use, either standalone, plugin or both.
I hope you understand.
I'm sure you could do this, since the editor (whether plugin or standalone) can produce sysex information... no problem there .. but I do believe the problem to be much greater as what you are talking about isn't in real-time, hence is not really a meaningful proposition if you know what I mean but sure if you have some presets as starting points then use them as I believe this is what the forum is for
Anyway, what is really needed is a genuine "workaround" hence what I keep saying here with respect to using the standalone to send out MIDI data via the 5 PIN DIN plug to the SC, then just trigger the module via the sequencer.
In fact if the above can be done (my suggestion not yours) no offence but that would be a much more workable solution as who would want to go back to the bad old days of sysex dumps and so on?
We must be serious if we want it to perform properly and that means independent MIDI streams via both ports, so that real-time sysex data can be sent along with General MIDI whichever port is in use, either standalone, plugin or both.
I hope you understand.
Re: AU SC Editor Issue????
Hi mystery, first, I don't know how to quote so, I'll place what you said in brackets:
[[Anyway, what is really needed is a genuine "workaround" hence what I keep saying here with respect to using the standalone to send out MIDI data via the 5 PIN DIN plug to the SC, then just trigger the module via the sequencer]]
When you say [[via sequencer]], you do mean a DAW or standalone sequencer, right?
And [[trigger the module]] you mean, to get it to play selected sounds via sequencer with a key controller? If yes give me some time and will get back. I've done this very similar thing before but, drawing a little blank right at this minute. Just keep an eye on this thread.
Yes, about the method that I'm going to test later, I think it should work. And yes, it does defeats the purpose of realtime and it really sucks, but it's better then nothing right now. I have so many projects lined up and have to get them done, that I have no time to wait for tech support. They said they'll call later today 5 days ago, but did not specify what year they were talking about. See that sucks too.
Stand by and I will try to help if I can.
If your way works, I guess we're both set.
Thanks a million for your inputs and ideas.
Adriano
[[Anyway, what is really needed is a genuine "workaround" hence what I keep saying here with respect to using the standalone to send out MIDI data via the 5 PIN DIN plug to the SC, then just trigger the module via the sequencer]]
When you say [[via sequencer]], you do mean a DAW or standalone sequencer, right?
And [[trigger the module]] you mean, to get it to play selected sounds via sequencer with a key controller? If yes give me some time and will get back. I've done this very similar thing before but, drawing a little blank right at this minute. Just keep an eye on this thread.
Yes, about the method that I'm going to test later, I think it should work. And yes, it does defeats the purpose of realtime and it really sucks, but it's better then nothing right now. I have so many projects lined up and have to get them done, that I have no time to wait for tech support. They said they'll call later today 5 days ago, but did not specify what year they were talking about. See that sucks too.
Stand by and I will try to help if I can.
If your way works, I guess we're both set.
Thanks a million for your inputs and ideas.
Adriano
Re: AU SC Editor Issue????
Ok, Not your last post but, the one prior you said:
[but I think the situation is such that if there is not a VST editor available, can the unit still be edited "standalone" eg via the non-DAW application using the 5 pin MIDI port while still being able to trigger sounds in the normal way via USB (midi)]
If I understand this question correctly, yes! it works via usb and/or via midi. To transmit changes in realtime with the SoniCell module itself, you need to turn on TX Edit Data....Go to "System" scroll all the way down to "System MIDI" and select TX Edit Data and turn it ON.
Once that's done and you'll start recording, anything you'll move on the SC, from patch changing to rev, cho, Effx and whatnot, Sysex get dumped in realtime to the DAW/Sequencer
Does that answer your question?
[but I think the situation is such that if there is not a VST editor available, can the unit still be edited "standalone" eg via the non-DAW application using the 5 pin MIDI port while still being able to trigger sounds in the normal way via USB (midi)]
If I understand this question correctly, yes! it works via usb and/or via midi. To transmit changes in realtime with the SoniCell module itself, you need to turn on TX Edit Data....Go to "System" scroll all the way down to "System MIDI" and select TX Edit Data and turn it ON.
Once that's done and you'll start recording, anything you'll move on the SC, from patch changing to rev, cho, Effx and whatnot, Sysex get dumped in realtime to the DAW/Sequencer
Does that answer your question?
Re: AU SC Editor Issue????
Hey,
Good that you wrote back as this is a serious issue for those (poor) people with a Roland Sonic Cell.
What I am trying to say by Standalone is the non-plugin editor, so bearing that in mind what I'm hoping for is that it (the standalone soniccell editor) will allow you to set it up to operate via a 3rd party MIDI interface in order so that any and all functions in relation to patch changes, sound modifications and effects can all be worked with in this way while at the same time using the built-in USB port of the SC itself (hardware) for both audio and other MIDI related functions; even if they (the midi datas) are ultimately performing the same function, ie sysex but generally in the latter case GM only.
Basically if it is possible what I'm saying, then that would mean there would be in effect two independent midi i/o ports on the unit, one via USB and the other via MIDI.
I know that many audio interfaces even if needing a specialised driver to work, ie ASIO, that at a class level all MIDI functions are supported and I'm hoping this to be the case with the Roland SonicCell.
Let me know if that is any closer to what you are talking about.
Good that you wrote back as this is a serious issue for those (poor) people with a Roland Sonic Cell.
What I am trying to say by Standalone is the non-plugin editor, so bearing that in mind what I'm hoping for is that it (the standalone soniccell editor) will allow you to set it up to operate via a 3rd party MIDI interface in order so that any and all functions in relation to patch changes, sound modifications and effects can all be worked with in this way while at the same time using the built-in USB port of the SC itself (hardware) for both audio and other MIDI related functions; even if they (the midi datas) are ultimately performing the same function, ie sysex but generally in the latter case GM only.
Basically if it is possible what I'm saying, then that would mean there would be in effect two independent midi i/o ports on the unit, one via USB and the other via MIDI.
I know that many audio interfaces even if needing a specialised driver to work, ie ASIO, that at a class level all MIDI functions are supported and I'm hoping this to be the case with the Roland SonicCell.
Let me know if that is any closer to what you are talking about.
Re: AU SC Editor Issue????
UPDATE:
I just loaded the Standalone SC editor and interfaced it to a software MIDI port after which I used a midi monitoring program to verify operation and success!
So that means the Editor in and of itself can send data (sysex) out via any OS assigned port.
Whether or not you can go back into the SC from outside the machine is anyones' guess but one thing I did not look at was the thru mode since I dont' really know what it does at present, however for the purpose of this test it may not be necessary.
I think in relation to the Plugin version of the SC editor, the problem starts whence it tries to assign midi ports of its' own volition, which by rights it should NOT be allowed to even contemplate no matter the application (DAW) in use so therein lies the issue, as what happens at least on the Cubase side is for example the Editor loads but the GUI isn't visible, however this is not the only application (plugin) which suffers from this phenomena so at the end of the day no plugin can be allowed to operate outside of a parent process unless of course they implement the Steinberg SKI but that's another story....
Maybe when you talk to the engineers you could ask them about this.
Best regards
I just loaded the Standalone SC editor and interfaced it to a software MIDI port after which I used a midi monitoring program to verify operation and success!
So that means the Editor in and of itself can send data (sysex) out via any OS assigned port.
Whether or not you can go back into the SC from outside the machine is anyones' guess but one thing I did not look at was the thru mode since I dont' really know what it does at present, however for the purpose of this test it may not be necessary.
I think in relation to the Plugin version of the SC editor, the problem starts whence it tries to assign midi ports of its' own volition, which by rights it should NOT be allowed to even contemplate no matter the application (DAW) in use so therein lies the issue, as what happens at least on the Cubase side is for example the Editor loads but the GUI isn't visible, however this is not the only application (plugin) which suffers from this phenomena so at the end of the day no plugin can be allowed to operate outside of a parent process unless of course they implement the Steinberg SKI but that's another story....
Maybe when you talk to the engineers you could ask them about this.
Best regards
Re: AU SC Editor Issue????
Oooohhh! Now I see what you mean. I finally saw the light.
Hang in there and let me check this out. I need to install the drivers for the SC and then I may need to reroute things around.
Please bare with me a bit longer
GSpro
Hang in there and let me check this out. I need to install the drivers for the SC and then I may need to reroute things around.
Please bare with me a bit longer
GSpro
Re: AU SC Editor Issue????
P.S. I have updated some of my original posts on this page.
Best of luck
Best of luck