 |
|  |
| |||||||
| Register | Search | Today's Posts | Mark Forums Read |
|
| Thread Tools | Display Modes |
 06-16-2024, 11:53 AM | #81 |
bapu Human being with feelings Join Date: Mar 2009 Posts: 41 |
Hey Moss, I have some new info for you. I took the working project in Studio One which plays the MIDI at 90bpm which is what the project is set to. I converted it to a DAWProject file. Ran that through Project Converter to create a brand new .rpp file. I received numerous errors: Parsing source project: F:\DAWproject Files\CO - Orch - Lasse - from Studio One.dawproject I received quite a few of that exact error but I only listed one here. Opened that .rpp in Reaper and the project bpm is 90 but the MIDI starts earlier than Measure 2 Beat 1 and plays back at a fater speed than 90bpm. Reminder: the MIDI tracks all have a C0 note at Measre 1 Beat 1 and are each a fully contiguous clip. __________________ |
 |
| 06-16-2024, 12:34 PM | #82 |
bapu Human being with feelings Join Date: Mar 2009 Posts: 41 |
Quote: Originally Posted by bapu Hey Moss, I have some new info for you. I took the working project in Studio One which plays the MIDI at 90bpm which is what the project is set to. I converted it to a DAWProject file. Ran that through Project Converter to create a brand new .rpp file. I received numerous errors: Parsing source project: F:\DAWproject Files\CO - Orch - Lasse - from Studio One.dawproject I received quite a few of that exact error but I only listed one here. Opened that .rpp in Reaper and the project bpm is 90 but the MIDI starts earlier than Measure 2 Beat 1 and plays back at a fater speed than 90bpm. Reminder: the MIDI tracks all have a C0 note at Measre 1 Beat 1 and are each a fully contiguous clip. Update: Loading the DAWProject export from Studio One and opening that in Bitwig reults in the project playing correctly at 90bpm. __________________ |
|
| 06-16-2024, 01:40 PM | #83 |
moss Human being with feelings Join Date: Mar 2007 Location: Germany Posts: 1,602 |
Quote: Originally Posted by bapu Hey Moss, I have some new info for you. I took the working project in Studio One which plays the MIDI at 90bpm which is what the project is set to. I converted it to a DAWProject file. Ran that through Project Converter to create a brand new .rpp file. I received numerous errors: Parsing source project: F:\DAWproject Files\CO - Orch - Lasse - from Studio One.dawproject I received quite a few of that exact error but I only listed one here. Opened that .rpp in Reaper and the project bpm is 90 but the MIDI starts earlier than Measure 2 Beat 1 and plays back at a fater speed than 90bpm. Reminder: the MIDI tracks all have a C0 note at Measre 1 Beat 1 and are each a fully contiguous clip. I compared the dawproject file with how it opens in Bitwig with my conversion in Reaper and they look pretty identical. So, maybe there is something wrong with the export from Studio One. But I cannot play the project since I am missing all the plugins/sounds from it. The errors you get in the conversion are simply from the so far unsupported MIDI automation. __________________ |
|
| 06-16-2024, 03:18 PM | #84 |
bapu Human being with feelings Join Date: Mar 2009 Posts: 41 |
Quote: Originally Posted by moss I compared the dawproject file with how it opens in Bitwig with my conversion in Reaper and they look pretty identical. So, maybe there is something wrong with the export from Studio One. But I cannot play the project since I am missing all the plugins/sounds from it. The errors you get in the conversion are simply from the so far unsupported MIDI automation. Actually, I was wrong. The Bitwig version of the Studio One Project does not seem to play back at the same 90bpm but the project is 90bpm but it's as fast as the .rpp created form the same Studio One created DAWproject file. At this point are you asking only for a simple Studio One conversion to DAWProject that opens in Bitwig? Or do you alos want the same simple .rpp (via ReaCWP from Cakewalk) converted to DAWProject too? __________________ |
|
| 06-17-2024, 01:26 AM | #85 |
moss Human being with feelings Join Date: Mar 2007 Location: Germany Posts: 1,602 |
Quote: Originally Posted by bapu Actually, I was wrong. The Bitwig version of the Studio One Project does not seem to play back at the same 90bpm but the project is 90bpm but it's as fast as the .rpp created form the same Studio One created DAWproject file. At this point are you asking only for a simple Studio One conversion to DAWProject that opens in Bitwig? Or do you alos want the same simple .rpp (via ReaCWP from Cakewalk) converted to DAWProject too? An original Studio One project which shows the issue when converted to DAWproject. Because then I can also send it to Presonus for testing. __________________ |
|
| 06-17-2024, 08:08 AM | #86 |
BPBaker Human being with feelings Join Date: Oct 2013 Location: Brooklyn, NY Posts: 225 |
Has anyone heard more rumors or rumblings about other DAWs adding support for this? I so badly want to live in a world where this exists and is available to more people! __________________ |
|
| 06-17-2024, 02:42 PM | #87 |
bapu Human being with feelings Join Date: Mar 2009 Posts: 41 |
Quote: Originally Posted by moss An original Studio One project which shows the issue when converted to DAWproject. Because then I can also send it to Presonus for testing. I'm away from my studio until Wednesday. I'll get you that then. __________________ |
|
| 06-18-2024, 01:02 AM | #88 |
moss Human being with feelings Join Date: Mar 2007 Location: Germany Posts: 1,602 |
Quote: Originally Posted by BPBaker Has anyone heard more rumors or rumblings about other DAWs adding support for this? I so badly want to live in a world where this exists and is available to more people! Yes, I heard something :-) __________________ |
|
| 06-18-2024, 11:15 AM | #89 |
bapu Human being with feelings Join Date: Mar 2009 Posts: 41 |
Quote: Originally Posted by moss An original Studio One project which shows the issue when converted to DAWproject. Because then I can also send it to Presonus for testing. Here you go. __________________ |
|
| 06-18-2024, 11:51 AM | #90 |
bapu Human being with feelings Join Date: Mar 2009 Posts: 41 |
@moss here are the things wrong in the 1. The tempo is 120 not 90 (I included renders from Cakewalk and Reaper as evidence of how the audio should sound) __________________ |
|
| 06-19-2024, 02:01 PM | #91 |
moss Human being with feelings Join Date: Mar 2007 Location: Germany Posts: 1,602 |
Quote: Originally Posted by bapu @moss here are the things wrong in the 1. The tempo is 120 not 90 (I included renders from Cakewalk and Reaper as evidence of how the audio should sound) Will ask Presonus about it. It is correct in Bitwig. Edit: I had a second look and it is actually a bug on my side. The unit of tempo needs to be set to bpm not linear, Bitwig seems to ignore this setting. Will be fixed in the next update! Quote: Originally Posted by bapu 2. Kontakt 7 was created as an insert on an audio track not in the Instrument Rack and thus the Instrument Track which does contain the MIDI is not pointing to a real instrument. Which follows that nothing plays. NOTE: if I load any old piano in the Instrument Rack and point the Instrument Track with the MIDI to it it plays but at a much faster speed than 90bpm (probably 120 as that is what the project is set at. That's not surprising. Since I only implement the straight forward routing in Bitwig, not all other crazy possibilities of Reaper ;-) Quote: Originally Posted by bapu 3. FabFilter Pro C-2 is nowhere to be found. Cannot test this one since I do not own it. Therefore, it is missing on my system anyway. Did you check that Studio One can load it at all (the VST3 version?)? __________________ Last edited by moss; 06-19-2024 at 02:18 PM. |
|
| 06-20-2024, 02:35 AM | #92 |
moss Human being with feelings Join Date: Mar 2007 Location: Germany Posts: 1,602 |
I just release ProjectConverter 1.2.3 with 1 important fix: Tempo unit was set to linear but needs to bpm. Bitwig ignores this setting but Studio One does not. Get it from https://mossgrabers.de __________________ |
|
| 06-20-2024, 07:42 AM | #93 |
bapu Human being with feelings Join Date: Mar 2009 Posts: 41 |
@moss v1.2.3 fixes the tempo for me in Studio One. I retested the .rpp puting NI's Solid Bus Compressor in place of FabFilter Pro C-2 and it too does not come across to Studio One. Also, Spaces II is coming into Studio One on an audio track where I'd expect it to be on an FX track with a send on the (not yet created by Project Converter) Instrument Channel in the mixer. This has always been the case I've just not mentioned it earlier. Have you looked at why your .dawproject file does not send the correct information on Kontakt 7 VST3i (or Opus as in the original larger project earlier) to create an entry in the Instrument Rack vs. how it gets created on an audio track? I'm guessing that Fabfilter Pro C-2 (or NI Solid Bus Compressor) is missing is because the Instrument Rack (hence the Instrument channel in the mixer) is not created to contain the FX send. __________________ Last edited by bapu; 06-20-2024 at 09:37 AM. |
|
| 06-21-2024, 07:18 AM | #94 |
moss Human being with feelings Join Date: Mar 2007 Location: Germany Posts: 1,602 |
Quote: Originally Posted by bapu @moss v1.2.3 fixes the tempo for me in Studio One. I retested the .rpp puting NI's Solid Bus Compressor in place of FabFilter Pro C-2 and it too does not come across to Studio One. Also, Spaces II is coming into Studio One on an audio track where I'd expect it to be on an FX track with a send on the (not yet created by Project Converter) Instrument Channel in the mixer. This has always been the case I've just not mentioned it earlier. Have you looked at why your .dawproject file does not send the correct information on Kontakt 7 VST3i (or Opus as in the original larger project earlier) to create an entry in the Instrument Rack vs. how it gets created on an audio track? I'm guessing that Fabfilter Pro C-2 (or NI Solid Bus Compressor) is missing is because the Instrument Rack (hence the Instrument channel in the mixer) is not created to contain the FX send. The FX are all showing up in Bitwig, so this might be a Studio One issue. __________________ |
|
| 06-21-2024, 11:13 AM | #95 |
bapu Human being with feelings Join Date: Mar 2009 Posts: 41 |
Quote: Originally Posted by moss The FX are all showing up in Bitwig, so this might be a Studio One issue. Well, yes and no. The (Spaces II and Solid Bus Compressor) FXs are in Bitwig and so is Kontakt 7, but Kontakt 7 does not have the instrument loaded into it but if I load any available piano sound (Giant for example) and press play, the project does "play" but no sound is coming out of Kontakt 7 and thus not hitting the FXs. But if I play the keys in Kontakt 7 after Giant is loaded, I do hear the sound. What I notice is that Kontakt 7 is loaded on a Bitwig folder. Should Bitwig be playong a VST3i on a folder like Reaper can? Clearly that's not happening. __________________ |
|
| 06-22-2024, 02:39 AM | #96 |
moss Human being with feelings Join Date: Mar 2007 Location: Germany Posts: 1,602 |
Quote: Originally Posted by bapu Well, yes and no. The (Spaces II and Solid Bus Compressor) FXs are in Bitwig and so is Kontakt 7, but Kontakt 7 does not have the instrument loaded into it but if I load any available piano sound (Giant for example) and press play, the project does "play" but no sound is coming out of Kontakt 7 and thus not hitting the FXs. But if I play the keys in Kontakt 7 after Giant is loaded, I do hear the sound. What I notice is that Kontakt 7 is loaded on a Bitwig folder. Should Bitwig be playong a VST3i on a folder like Reaper can? Clearly that's not happening. The original Reaper file is a bit weird. The channel with the MIDI data sends its MIDI data via a Send channel (I didn't even know that this is even possible) to another channel which contains the Kontakt instance. This cannot be replicated on Bitwig or Studio One. Simply move the Kontakt instance in the original file on the track with the MIDI data and it will work. __________________ |
|
| 06-22-2024, 08:19 AM | #97 |
bapu Human being with feelings Join Date: Mar 2009 Posts: 41 |
Quote: Originally Posted by moss The original Reaper file is a bit weird. The channel with the MIDI data sends its MIDI data via a Send channel (I didn't even know that this is even possible) to another channel which contains the Kontakt instance. This cannot be replicated on Bitwig or Studio One. Simply move the Kontakt instance in the original file on the track with the MIDI data and it will work. If you mean like the attached .rpp, that did not work in Studio One. So maybe I'm not understanding what you mean. The other thing to remember about a VST3i like Kontakt or Opus is that one instance can contain multiple instruments and thus have multiple MIDI feeds. That was the case in the origianl .rpp I sent for the four instances of Opus. So if I'm understanding your fix for this test correctly, it did not work in Studio One, as there was no instance of Kontakt in the Instrument Rack. It almost worked in Bitwig, but it did not have the Spaces II Reverb anywhere in the project. __________________ |
|
|
«Previous Thread|Next Thread»
| Thread Tools | |
| |
| Display Modes | |
|
Linear Mode
|
All times are GMT -7. The time now is 04:39 PM.
